SendFlo

Data Processing Agreement

Last updated: November 16, 2026

This Data Processing Agreement (“DPA”) is part of the Terms of Service between SendFlo LLC (“SendFlo”, “we”) and the customer using SendFlo for a business (“you”). It applies when the files and details you send, request or store through SendFlo include personal data protected by the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection or US state privacy laws such as the CCPA. It takes effect when you accept the Terms — no signature is needed. For a countersigned copy, write to support@sendflo.app.

Our own use of account data (your sign-in, billing and how you use the service) is described in the Privacy Policy; for that we are a controller, and this DPA does not apply to it.

1. Roles and scope

For the personal data contained in what you and the people you invite put into SendFlo — files, recipients' and uploaders' details, messages and feedback on your transfers (“Customer Personal Data”) — you are the controller (or a processor acting for your own client) and we are your processor (or sub-processor). Annex I describes the processing.

2. Our commitments

  • Instructions. We process Customer Personal Data only to provide the service, on your documented instructions — the Terms, this DPA and the way you set up and use the service — unless the law requires otherwise, in which case we tell you first unless the law forbids it. We tell you if we believe an instruction breaks data-protection law.
  • Confidentiality. Everyone we authorise to process Customer Personal Data is bound by confidentiality. No person reads your files: staged content passes only automated processing (malware scanning, previews and, on plans that include them, search indexing and reading text in images).
  • Security. We maintain the technical and organisational measures in Annex II and keep them at least as protective as described there.
  • Sub-processors. As in section 6.
  • Your data subjects. The service lets you find, export and delete what you sent and received; we help with any request you can't answer that way, and forward to you any request we receive about Customer Personal Data instead of answering it ourselves.
  • Assessments. We give you the information you reasonably need for a data protection impact assessment or a prior consultation with a supervisory authority about the service.

3. Personal data breaches

We notify you without undue delay, and no later than 72 hours after we become aware of a personal data breach affecting Customer Personal Data, by email to your account's owner. We tell you what we know — what happened, the kinds and approximate amount of data and people concerned, the likely consequences and what we are doing about it — and follow up as we learn more. Notifying a breach is not an admission of fault.

4. Deletion at the end

Staged files are deleted on the schedule you set. When you delete a file a link shared with each viewer's identity, what is needed to trace a leaked copy of it (the two marked versions of its video or audio and which mix each viewer was given, never the file) is kept for your team's period — 30 days unless your team chose up to 360 — or deleted at once if you choose “Delete everything now”. When you delete your account or your team, Customer Personal Data is permanently deleted within 14 days, except what the law requires us to keep; daily database backups expire within 30 days (file contents are not backed up). Before then you can download your files, and a copy of your account data from Settings → Sign In & Security → Your data.

5. Audits

We make available the information needed to show we meet this DPA: on request, written answers to a reasonable security questionnaire and our current technical documentation. If that is not enough, or a supervisory authority requires it, you (or an independent auditor bound by confidentiality) may audit our compliance once a year, on 30 days' notice, during business hours, at your cost, without access to other customers' data.

6. Sub-processors

You authorise the sub-processors listed at sendflo.app/legal/subprocessors. We bind each by written terms giving at least the protection of this DPA and remain responsible for them. We add a new one to that list at least 30 days before it processes Customer Personal Data (and email you if you asked to be told). If you object on reasonable data-protection grounds within that time, we will try to address it; if we can't, you may end the affected service and receive a pro-rata refund of prepaid fees for it.

7. International transfers

Where Customer Personal Data is transferred from the EEA to a country without an adequacy decision, the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 apply and are incorporated by reference: Module 2 (controller to processor) where you are a controller, Module 3 (processor to processor) where you are a processor. For them: clause 7 (docking) applies; under clause 9 option 2 (general authorisation, with the notice in section 6) applies; the optional wording in clause 11 does not; clauses 17 and 18 choose the law and courts of Ireland; Annexes I–III of this DPA complete their annexes.

For transfers from the United Kingdom, the International Data Transfer Addendum to those clauses issued by the UK Information Commissioner (version B1.0) applies, completed with the information in this DPA; either party may end it as its section 19 allows. For transfers from Switzerland, the clauses apply with the Swiss Federal Data Protection and Information Commissioner as the competent authority and Swiss law's references in place of the GDPR's where the Swiss FADP governs the transfer. If an EU-US Data Privacy Framework certification or another lawful mechanism covers a transfer, it may be relied on instead.

8. US state privacy laws (including the CCPA)

For personal information covered by the California Consumer Privacy Act and similar laws we act as your service provider (or processor). We will not sell or share it, retain, use or disclose it outside our direct business relationship with you or for any purpose other than providing the service, or combine it with personal information we receive from others except as those laws allow. We comply with those laws, give the same level of protection they require, and tell you if we can no longer meet them; you may then take reasonable steps to stop unauthorised use. We certify that we understand these restrictions.

9. Precedence and liability

If this DPA conflicts with the Terms, this DPA wins; if the standard contractual clauses conflict with either, the clauses win. Each party's liability under this DPA is subject to the limits in the Terms, except where the law or the clauses do not allow it.

10. Annex I — the processing

  • Parties. Data exporter: you (the customer named on the account), as controller or processor. Data importer: SendFlo LLC, support@sendflo.app, as processor; activities: providing SendFlo.
  • People concerned. Anyone whose personal data you send, request or store — for example your staff, clients, recipients and uploaders, and people who appear in your files.
  • Kinds of data. Whatever your files contain, which we don't inspect beyond automated processing (malware scanning, previews and, on plans that include them, search indexing and reading text in images); names and email addresses of recipients, uploaders and reviewers; their opens, downloads and feedback (time, country, kind of device, the IP address and its network); and your own users' sign-ins and actions, in your audit log. Special categories only if you put them in files; SendFlo is not certified for health data (Privacy Policy §8).
  • Frequency and nature. Continuous, while you use the service: receiving, storing, scanning, previewing, indexing for search, relaying and delivering files and notifications; and, only when your users use Ask, sending a question and the passages it needs to the provider of the model they choose.
  • Purpose. Providing the service under the Terms.
  • Duration. As section 4 describes.
  • Competent supervisory authority. The one determined by clause 13 of the clauses for the data exporter.

11. Annex II — technical and organisational measures

  • Encryption in transit (TLS) everywhere; encrypted peer-to-peer connections for direct transfers.
  • Staged content encrypted at rest; relayed transfers encrypted on the sender's device by default; optional end-to-end encrypted links whose key never reaches our servers.
  • Access: least privilege for staff; two-factor and passkey sign-in for customers; teams can require two-factor; a fresh emailed code before sensitive account changes; sessions listed and revocable.
  • Data minimisation: IP addresses are kept as they are only in the audit log (90 days; 1 year on Team Pro, 2 years on Team Enterprise, then deleted) and as each device's last address (shown to its owner, cleared 90 days after the device was last used); everywhere else as salted, keyed one-way hashes, cleared after 90 days.
  • Logging: an append-only audit log of sign-ins, security and account changes, access to your links, uploads, billing, API use and staff actions on your account; the database refuses edits to it and a daily seal of each account's entries is written to write-once storage. You can read and export it (Pro, Team Pro, Team Enterprise), receive access events by webhook (Team Pro, Team Enterprise) and send it to your own storage (Team Enterprise).
  • Automated malware scanning of staged uploads, with account standing, rate limits and abuse reporting.
  • Availability: managed databases with daily backups kept 30 days; zero-downtime deploys; monitoring and alerting.
  • Deletion: account and team deletion pipelines that remove data from storage and every database within 14 days, with an auditable record.
  • Pinned software versions, dependency and secret scanning in every build, and a written incident runbook.

12. Annex III — sub-processors

The list at sendflo.app/legal/subprocessors, as updated under section 6.

Questions about this document: support@sendflo.app · Terms · Privacy · Refunds & Cancellation · Service providers · DPA