Data Processing Agreement
Version 1.1 (in effect from 24 October 2026) · Last updated 24 October 2026 · Versions and changes
What changed on 24 October 2026
- Section 10: when you remove a client, we delete their details, conversations, to-dos, notes and the recordings sent only to them straight away, and keep no copy to restore them from.
This is a new version, so account holders are asked to agree to it. Earlier versions
SureFrame (ABN 38 364 192 034) is a registered business name of a sole trader based in Queensland, Australia (“we”, “us”). This Data Processing Agreement (“DPA”) forms part of the SureFrame Terms of Service (the “Terms”) between us and the business that uses SureFrame (“you”). It applies when we process personal data for you that is protected by Data Protection Law. You accept it by accepting the Terms, so there’s nothing to sign. If you need a signed copy, email support@sureframe.app.
1. Definitions
- “Data Protection Law” means Regulation (EU) 2016/679 (the “EU GDPR”), the EU GDPR as it forms part of the law of the United Kingdom (the “UK GDPR”) with the UK Data Protection Act 2018, and the laws that supplement them, as far as they apply to the processing.
- “Customer Personal Data” means personal data that you or your team put into SureFrame, or that your clients give through it, and that we process for you.
- “Sub-processor” means a third party we use that processes Customer Personal Data.
- “SCCs” means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914.
- “UK Addendum” means the International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018.
- Controller, processor, personal data, processing, personal data breach, data subject and supervisory authority have the meanings given in Data Protection Law.
2. Roles
You’re the controller of Customer Personal Data and we’re your processor. If you act as a processor for someone else, you confirm they’ve authorised your instructions and this DPA, and we’re your sub-processor.
Information we handle for our own purposes isn’t covered by this DPA: your account, sign-in, billing and support information, the questions your clients type into the help chat on their pages (kept with your business’s name but not who asked, for 90 days, and listed in a weekly email to our support inbox, so we can find and fix problems), the information we use to keep SureFrame secure, records of agreement to the Terms and our privacy policy, and the records we keep when we act under section 9 of the Terms (which can include, for example, the name and email address of a client whose link we turned off). We’re the controller of that information, and our privacy policy covers it.
3. Details of the processing
This section also completes Annex I.B of the SCCs.
- Subject matter and purpose: providing SureFrame to you under the Terms.
- Duration: while you use SureFrame, plus the deletion periods in section 10.
- Nature:
- storing, relaying and deleting end-to-end encrypted content;
- storing client and team details and using them to send links, reminders and notifications;
- controlling who can access what, including pausing, suspending or turning off access as the Terms describe;
- only if you switch on the AI add-on, sending transcript text to our AI provider for a summary;
- and, only if you connect your own AI assistant (section 23 of the Terms), making the information it can read available to it on your instruction.
- Data subjects: your clients (and parents or guardians acting for them), your staff and team members, and anyone who appears in, or is mentioned in, content.
- Categories of personal data:
- Information we can read: client names and email addresses, link status (when a link was sent or first opened, and whether it’s paused, removed or turned off), reminder preferences and assignments; staff names, email addresses, roles, permissions and settings; video titles, reply author names, dates, sizes, lengths, view counts and emoji reactions; to-do due dates and repeat and reminder settings; reminder messages and staff reminders; and Team overview activity figures.
- Content that is end-to-end encrypted, which we can’t read: video and voice recordings, video stills, text replies, to-dos, notes, transcripts and summaries.
- Transcript text, while it’s sent for an AI summary.
- Special categories: we don’t ask for them, but content may contain them (for example health details). They stay end-to-end encrypted, except transcript text you choose to send for a summary.
- Frequency: continuous.
4. Your instructions
We process Customer Personal Data only on your documented instructions. These are the Terms (including section 9 on suspension, closure and legal hold), this DPA, and how you and your team set up and use SureFrame. We’ll tell you if we think an instruction breaks Data Protection Law. If the law requires us to process Customer Personal Data in another way, we’ll tell you first, unless that law forbids it.
5. Your responsibilities
You’re responsible for:
- having a lawful basis for the Customer Personal Data;
- giving your clients and staff the information the law requires, including about the Team page and the AI add-on;
- keeping your devices, recovery key and client links secure;
- and making sure your instructions comply with Data Protection Law.
6. Confidentiality
Everyone we allow to access Customer Personal Data is bound by confidentiality and accesses only what they need. Today that’s SureFrame’s owner and anyone they authorise to help run SureFrame.
7. Security
We use the measures in Annex 2 and keep them appropriate to the risk. We may change them, but not in a way that lowers the overall protection.
8. Sub-processors
You authorise the sub-processors in Annex 3. Each is bound by a written contract with data protection terms that protect Customer Personal Data at least as well as this DPA does, as far as they apply to its service. We remain responsible to you for their work. We’ll update Annex 3 and email the workspace’s owner and any admins a notice headed “New SureFrame sub-processor”, saying who it is, what it does for us, where it processes information and when it starts, at least 30 days before a new sub-processor starts processing Customer Personal Data. If you object on reasonable data protection grounds, email support@sureframe.app within that time and we’ll work with you in good faith. If we can’t resolve it, you may delete your account, and we’ll refund any fees you’ve prepaid for the period after that.
9. Helping you
- SureFrame lets you see, export, correct and delete Customer Personal Data yourself: on the Clients page, on each video, and in Settings > Account.
- If a data subject contacts us about Customer Personal Data, we’ll pass the request to you without undue delay and won’t answer it ourselves, except to direct them to you, unless you ask us to.
- We’ll give you reasonable help with your security obligations, breach notifications, data protection impact assessments and consultations with supervisory authorities, taking into account the nature of the processing and the information available to us. Because content is end-to-end encrypted, we can only help with the information we can read.
10. Deletion and return
- Without cloud backup, recordings are deleted from our servers 30 days after they’re recorded.
- A video or voice reply that was recorded but never sent is deleted 7 days after it was recorded, with or without cloud backup.
- When you remove a client, their link stops working straight away and we delete their details, conversations, to-dos and notes, and the recordings sent only to them, at the same time, even with cloud backup. We keep no copy to restore them from. Recordings you also sent to other clients stay with those clients.
- When you delete your account, we keep Customer Personal Data for 30 days so you can reactivate it, then delete it. If we close your account under section 9 of the Terms, we delete it 44 days after closure (the 30 days you have to ask for a review or a copy of your data, plus two weeks for us to act on it), or on the date already set, if you’d already deleted your account. Either way, a legal hold (below) can keep it longer.
- If we need to keep Customer Personal Data longer because the law requires it, or for a legal claim or a report to the authorities (a legal hold, as section 9 of the Terms describes), we keep only what we need, keep protecting it under this DPA, and delete it once it’s no longer needed.
- Before your account is deleted, you can download your data in Settings > Account, as a readable copy unlocked in your browser or as stored (encrypted, which only your keys can open), and save videos to your device (if you deleted your account, keep it first). If we close your account under section 9 of the Terms, you can’t sign in, so email support@sureframe.app within 30 days of the closure and we’ll send you your account data download, unless the law stops us. That download is as stored: encrypted content in it can be opened only with your keys.
- Deleted data may remain in our providers’ backups until those backups expire, and this DPA keeps applying to it until then.
11. Personal data breaches
We’ll notify the workspace owner by email without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, and we aim to do so within 48 hours of becoming aware of it. We’ll include what we know of its nature, the categories and approximate numbers of people and records affected, the likely consequences, the measures taken or proposed, and who to contact. We’ll add more as we learn it, and take reasonable steps to contain the breach. Notifying you isn’t an admission of fault.
12. Information and audits
We’ll give you the information you reasonably need to show we meet Article 28 of the EU GDPR (or the UK GDPR), including written answers to a reasonable security questionnaire once a year, or after a breach. If that isn’t enough to meet a requirement of Data Protection Law or a supervisory authority’s request:
- you, or an independent auditor bound by confidentiality who isn’t our competitor, may audit our processing;
- you give at least 30 days’ notice, and the audit happens during Queensland business hours, by document review and remote sessions;
- it happens no more than once a year, except after a breach or at an authority’s request;
- and it’s at your cost.
Our providers are audited through their own reports.
13. International transfers
We’re in Australia. Encrypted recordings are kept in Cloudflare's Oceania region (Australia, New Zealand and the Pacific), as far as Cloudflare allows us to choose, and our other sub-processors are mainly in the United States (Annex 3).
- EU and EEA: for transfers of Customer Personal Data from the European Economic Area, the SCCs are incorporated into this DPA by reference:
- Module 2 applies where you’re a controller, and Module 3 where you’re a processor.
- You’re the data exporter and we’re the data importer.
- Clause 7 applies.
- Clause 9(a) Option 2 applies, with the notice period in section 8.
- The optional wording in Clause 11 doesn’t apply.
- The supervisory authority under Clause 13 is the one that clause determines.
- Under Clause 17, the SCCs are governed by the laws of Ireland, and under Clause 18, disputes go to the courts of Ireland.
- Annexes I, II and III of the SCCs are completed by section 3 and Annexes 1, 2 and 3 of this DPA.
- UK: for transfers from the United Kingdom, the UK Addendum applies and is incorporated by reference:
- Table 1: the parties are as in Annex 1.
- Table 2: the SCCs, with the modules and options above.
- Table 3: section 3 and Annexes 1 to 3.
- Table 4: either party may end the UK Addendum as allowed by its Section 19.
- Onward transfers to sub-processors are made under contracts that include the SCCs or another safeguard Data Protection Law recognises.
- Order of precedence: if there’s a conflict, the SCCs and the UK Addendum prevail over this DPA, and this DPA prevails over the Terms.
14. Liability
Each party’s liability under this DPA is subject to section 16 of the Terms, except where Data Protection Law or the SCCs don’t allow it to be limited, such as liability to data subjects.
15. Term, changes and governing law
This DPA lasts while we process Customer Personal Data for you. We may update it to reflect changes in the law, the SCCs or our sub-processors. We won’t reduce its protection, and significant changes follow section 18 of the Terms. Apart from the SCCs and the UK Addendum, it’s governed by section 20 of the Terms.
16. Contact
SureFrame, support@sureframe.app, PO Box 717, Rochedale South QLD 4123, Australia. We haven’t appointed a data protection officer, or a representative in the EU or UK because the exemption in Article 27(2) of the GDPR and the UK GDPR applies (our privacy policy explains why).
Annex 1: Parties
- Data exporter: the business named in its SureFrame account. Contact: the workspace owner’s email address. Activities: using SureFrame as described in section 3. Role: controller (or processor).
- Data importer: SureFrame, the registered business name of a sole trader, ABN 38 364 192 034, PO Box 717, Rochedale South QLD 4123, Australia, support@sureframe.app. Activities: providing SureFrame as described in section 3. Role: processor. The sole trader’s full legal name is given on request for a signed copy of this agreement: email support@sureframe.app.
- Signature and date: both parties agree to this DPA, including the SCCs and the UK Addendum where they apply, when the data exporter accepts the Terms (by ticking the box we show, which we keep a record of), and that acceptance counts as signing it on that date.
- The rest of Annex I of the SCCs is completed by section 3 (description of the transfer) and section 13 (competent supervisory authority).
Annex 2: Security measures
- End-to-end encryption: recordings are encrypted on the recording device, chunk by chunk, with AES-256-GCM using the browser’s Web Crypto, before they’re uploaded; while recording, the encrypted recording is uploaded in pieces every few seconds. Video stills, text replies, to-dos, notes, transcripts and summaries are encrypted on the device the same way before they’re saved.
- Keys stay with you: keys are made on your team’s devices, and our servers store only encrypted (wrapped) copies of them. Each client’s key travels only in the part of their personal link after “#”, which browsers don’t send to servers. When an owner or admin removes a staff member, the team key and every client key and link are replaced.
- Encryption in transit: the website and app are served over HTTPS only, with HSTS (2 years, including subdomains). Our servers connect to our providers over encrypted connections.
- Browser protections: other sites can’t show our pages in a frame; content-type sniffing is blocked; referrers stay within our site; and camera, microphone and screen access is limited to our own site and our browser extension.
- Storage: browsers get signed, short-lived links to files. Upload links are valid for 15 minutes and limited to the exact size of the piece or part being uploaded. Playback links are valid for 1 hour.
- Access control: roles and permissions are checked by our servers on every request, and staff see only the clients assigned to them unless an owner or admin allows more. Clients get access only through their secret personal link, which stops working if the business removes them or its plan no longer covers them, or if we turn the link off or suspend or close the business’s account. Our support tools are limited to named accounts, and we record each action taken with them.
- Sign-in: passwordless sign-in links that work once and expire after 24 hours; when someone signs in to connect Claude, a 6-digit code instead, which works for 30 minutes and 5 tries and is kept only as a one-way fingerprint, with the email address, until it expires. Sessions usually end when the browser closes, and after 8 hours without use; someone who ticks “Keep me signed in” when signing in, or turns it on later in Settings, stays signed in on that device for 30 days from when it was turned on. We can sign a login out on every device. Repeated attempts are rate-limited, and scheduled jobs need a secret to run.
- Data minimisation: notification emails don’t include replies, messages or to-do text (they can name a video by its title). Copies of recordings are deleted from our servers automatically (see section 10). Recordings left unfinished are completed from their encrypted copy once untouched for at least 6 hours, leftover pieces are deleted after about a day, and uploads that can’t be completed are removed after a week. Expired sign-in links are deleted, and IP addresses counted for rate limits are deleted within about two days (the help chat’s limits for visitors and Free plans keep only a one-way fingerprint, for 31 days).
- AI add-on: transcripts are made on the team member’s device, from a speech model served from our own storage. Only transcript text is sent for a summary; we don’t log or store it in readable form, and the transcript and summary are saved end-to-end encrypted.
Annex 3: Sub-processors
We use these sub-processors for Customer Personal Data. List last changed 20 October 2026.
- Vercel (hosting the website and app): everything sent to or from the website and app passes through it, and it keeps request logs, including IP addresses. Location: United States.
- Neon (our database): account, team, client, billing and support details, details of videos we can read (such as titles), questions typed into the help chat on client pages, records of support actions and of agreement to our terms, encrypted video stills, and the encrypted text of replies, to-dos, notes, transcripts and summaries. Location: United States.
- Cloudflare R2 (file storage): encrypted video and voice recordings. Location: Oceania region (Australia, New Zealand and the Pacific), as far as Cloudflare allows us to choose.
- Resend (email delivery): names, email addresses and the emails we send, such as sign-in links, client links, reminders and team emails. Location: United States.
- Anthropic (the help chat’s AI assistant, and AI summaries for businesses that switch them on): help chat messages, and transcript text when a business uses AI summaries. Location: United States.
- Google Workspace (our support email): emails to and from our support inbox, including help chats passed to a person and a weekly list of the questions typed into the help chat on client pages, with the business each was asked about. Location: United States.