SendFlo

Privacy Policy

Last updated: November 16, 2026

This policy explains what SendFlo LLC ("SendFlo", "we") collects when you use SendFlo, why, and what your rights are. The short version: your email is your identity, your files are yours, direct transfers are never stored on our servers, and we don't sell data — to anyone, ever.

1. What we collect

  • Account data — your email address (every account has one; it anchors your sign-in methods: a password — stored only as a salted hash by our authentication service — a Google account you connect, your organisation's single sign-on, and the passkeys and authenticator app you add to confirm it's you), plan and team membership, the preferences you set, and your home storage region, derived once from the country you signed up from.
  • Device data — the devices you register (name, platform, app version), their activity heartbeats, and the IP address each device last connected from, which we show you in Settings → Network & Devices so you can recognise your own devices (cleared 90 days after the device was last used). The audit log (below) records IP addresses as they are; for nearby-device discovery, abuse prevention and rate limiting we use salted, one-way hashes of them instead.
  • Where your backed-up computers are, if you turn it on — off unless you turn it on for a computer on its Backup page. Then we keep where its backups check in from: the town or city of its internet address (about 25 km), or only the country, never GPS — a new place when it has moved or hours have passed, the newest 50. You see it; your team's owner and admins see it only if you also choose to share that computer with them and your team has turned that on, and every look is in your team's audit log. SendFlo staff don't see it. Turning it off, or removing the computer from Backup, deletes every place kept.
  • Security signals — network and device information used for security. When you sign up, sign in, reset a password, share, open or unlock a link, report something or create an API key, automated checks look at the network address and the kind of network it belongs to (for example a hosting provider, VPN or proxy), the browser and device it reports, how quickly the connection answers, and how many accounts or attempts came from the same device or network recently (counted with salted, one-way hashes). Each check keeps what it looked at, its result and the step it asked for, if any. When a download from our storage is flagged (a download address used more times than allowed, or from a second network), the IP addresses that fetched it are kept with the flag.
  • The audit log — an append-only record of who did what: sign-ins and security changes, changes to your account and team, your links and every open, preview and download of them, uploads to your requests, billing and API use, and anything SendFlo staff did on your account. Each entry keeps the time, the IP address and the network it belongs to (looked up in public registries), the country, the kind of browser and system, and what happened. You can read your own on Pro, Team Pro and Team Enterprise (Settings → Audit log): the addresses of your own sign-ins, and — on Team Pro and Team Enterprise — the addresses of the people who opened your links. A Team Enterprise team can also send its log to its own storage, and Team Pro and Team Enterprise can receive access events by webhook.
  • Transfer data — metadata about your transfers (file names, sizes, recipients, timestamps) for your history; and, for staged transfers only (links, relays, file requests), the file content itself while it awaits delivery or expiry. Files sent directly device-to-device travel over an encrypted peer-to-peer connection — sometimes forwarded, still encrypted, by our live relay — and are never stored on our servers.
  • When you download from a link — the sender sees when you opened, previewed and downloaded each file, the country you were in (worked out from your network address), the kind of browser and system you used (for example “Chrome on Windows”), and whether the download was confirmed complete. They see your email address only if the link asked you to verify it; if SendFlo emailed the link to you, they see that it was opened through the link sent to your address. Otherwise you appear as “Someone” — even if you're signed in to SendFlo or typed your email into the page. If the sender is on Team Pro or Team Enterprise, their team also sees your IP address and the network it belongs to, in their audit log; on other plans they never see it. If you choose to view a link as a guest instead of verifying an email, your IP address, the time and a view number are printed on every image and page you open or download, and the sender sees them. When a link adds the viewer's identity, each copy you open or download also carries an invisible mark unique to you, and the sender can upload a copy found elsewhere for SendFlo to read whose copy it was. A video you watch or download on such a link is a mix of two invisibly different versions, in an order unique to you, and SendFlo records that you were given it; audio you play or download carries an inaudible mark unique to you. The page tells you before you open the files. Nobody sees your city or your full browser details. SendFlo records each visit, with its IP address, in the sender's audit log for security (kept as in section 6). Every download page says this at the bottom.
  • Payment data — handled entirely by Paddle.com, our reseller and merchant of record, which processes your payment details under its own privacy policy; we receive plan, status, and receipt metadata, never your card number.
  • Support & service data — messages you send us by email or through the support chat, copies of the service emails we send you, and minimal operational logs. The support chat (Crisp) loads only when you open it; until then nothing about your visit reaches it.
  • Usage analytics — which pages are visited, how visitors arrived (for example from a search engine, an email, or an ad or other link carrying campaign tags), the type of device and browser, approximate location (country and city, worked out from the IP address, which Google Analytics does not store), and whether actions such as downloads, sign-ups and purchases succeeded. Collected with Google Analytics on our website and in our iPhone and Android apps; section 10 explains what it never receives.
  • Feedback on a transfer — when you comment on, rate, favorite or approve files someone sent you, the name and email address you give, what you wrote, and the kind of device and country you wrote from (shown in the confirmation email so you can recognise the request). Your email is visible only to the sender; your comments are visible to the sender and, unless the sender keeps comments private, to anyone with access to the link. We use your email only to confirm it's you, and — if you turn it on — to tell you when the sender replies. A device you confirm on keeps a random credential in its browser storage for 30 days so you aren't asked again — the same holds when you confirm your email to open a protected link (the page then offers “Continue as” that address on that device; “Not you?” forgets it). To tell whether the device you wrote on and the one you confirm on share a network (then both are confirmed), we compare a salted, one-way hash of their network addresses — never the addresses themselves; the same hash is what a “This wasn't me” report pauses.
  • Ask — when you ask a question about your files, your question and the passages of your files it needs go to the provider of the model you choose (section 4). Your name and email address aren't sent with them, and they are never used for training. Questions and answers are saved encrypted so you can come back to them, unless you turn that off. For billing and support we keep the details of each question (the model, the time, the credits used), never its text.

2. How we use it

To run the service you asked for: delivering transfers, syncing your devices, showing your history, sending the notifications you enabled, billing your plan, preventing abuse (staged content passes automated abuse scanning — no human reads your files), and meeting legal obligations. To prevent abuse we also keep a record of malware found in what each account or guest uploads and of abuse reports about what they send — with the number of uploads it is weighed against — which can lead to a warning, a restriction or a suspension; while we start this, every such step is approved by a person first. We use automated security checks, including network and device signals and proxy detection, to protect the integrity and security of our platform and our users. A check can ask for an extra step (a verification challenge, an emailed code, a short pause on sign-ins from one network) or withhold an introductory offer. Anything stronger, such as restricting a Free plan or an API key, is approved by a person first while we start this, and you are always told why in plain words and can appeal. We send product email only per your notification preferences, and marketing email only with consent you can withdraw in one click. And, with Google Analytics, to understand how the site is used and which campaigns bring visitors, so we can improve it (section 10).

3. Legal bases (EU/UK)

Where GDPR applies: performing our contract with you (the service itself, billing — and, when you give feedback on a transfer, the step you asked us to take), legitimate interests (abuse prevention, service security, minimal logs, confirming that feedback comes from the address it names, counting visits without cookies, and the audit log: knowing who signed in, changed, opened or downloaded what, from where — which keeps accounts safe and gives senders the record of delivery and access they rely on), consent (marketing email and analytics cookies), and legal obligation (tax and accounting records).

4. Who we share with

The recipients you choose receive what you send them — that is the product. Beyond that, data is processed only by the infrastructure providers the service runs on — hosting, content delivery and relay, cloud storage, email delivery, customer-support chat, payment processing (Paddle.com, our merchant of record) and, only when you use Ask, the provider of the model you choose — each bound by data-processing agreements and used only to operate the service. They are named, with what each receives, on our list of service providers. Business customers who send other people's personal data through SendFlo can rely on our Data Processing Agreement. We do not sell or rent personal data, and we disclose it to authorities only when legally compelled.

We also use Google Analytics (Google LLC) to measure how the site and our phone apps are used; it receives only the usage data described in section 10 — nothing from your files — and its advertising features and data sharing are turned off. When you buy a plan with analytics allowed, our servers send Google Analytics the plan, the amount and an order number — never your name, email or payment details.

5. International transfers

Our providers operate globally; where personal data leaves the EU, the UK or Switzerland it travels under the European Commission's standard contractual clauses (with the UK Addendum and the Swiss adaptations), or another lawful mechanism such as the EU-US Data Privacy Framework where a provider is certified under it. The Data Processing Agreement sets this out for business customers.

6. Retention and deletion

While your account exists:

  • Staged files: deleted on their expiry schedule, or when File Restore lapses.
  • Transfer history, device records (including each device's last IP address), copies of the emails we send you, and support conversations: kept while your account exists — for a team, while the team exists.
  • Text read from a file and its search entries: kept only for your search, and deleted after the file leaves your Drive for good, or 30 days after your Drive moves to a plan without search inside files. File names stay searchable on every Drive plan.
  • Ask conversations: kept encrypted until you delete them, or for the 30, 90 or 365 days you choose. The usage details of each question stay with your billing records.
  • The audit log, IP addresses included: 90 days on personal plans and Team Lite and Plus, 1 year on Team Pro, 2 years on Team Enterprise — then deleted, a whole month at a time (an entry lives at most a month longer). What a Team Enterprise team sends to its own storage is kept there under its own rules.
  • Other network data — salted, one-way hashes of IP addresses (kept with sign-ins, downloads from your links, reports and similar records) and the last IP address of each of your devices: cleared automatically after 90 days. The records themselves stay, without it. Abuse-prevention records keep theirs longer, as below.
  • Security-check records (what each check looked at — the network address included, seen only by our security staff — its result and the step it asked for): 90 days, then deleted a whole month at a time. A decision that followed from one, such as a restriction and the reasons you were told, is kept with the abuse-prevention records below.
  • The IP addresses kept with a flagged download (seen only by our security staff): removed after 90 days. The flag itself stays with the security-check records.
  • Operational logs: kept for up to 30 days.
  • A copy of your data you asked for (“Download your data”): kept 7 days, then deleted.
  • A copy a sender uploads to trace a leak: kept 30 days, then deleted. The result (whose copy it was) stays with the link, and the trace is recorded in the sender's audit log.
  • When a sender deletes a file that a link shared with each viewer's identity, what is needed to trace a leaked copy of it is kept for 30 days, or up to 360 days if the sender's team chose longer: the two invisibly different versions of its video or audio, and the record of which mix each viewer was given (a viewer appears in it only as a one-way hash). Never the file itself. Then it is deleted. It goes at once if the sender chooses “Delete everything now”, or when the sender's account or team is deleted.
  • Usage analytics: kept by Google Analytics for 14 months, then deleted automatically.
  • Abuse-prevention records (malware found in uploads, reports about sends, the steps taken, and daily upload counts): kept 24 months (upload counts and the record of who uploaded each file, 13 months). A guest is identified only by salted, one-way hashes of the email, device and network they used — never the addresses themselves. If an account is banned, hashed fingerprints of it are kept to stop it re-joining — those of its networks for 12 months. A report someone files keeps who filed it for 2 years; after that only the report remains. The email that asks a reporter to confirm their address, and the hashes of the network and browser that asked, are deleted after 90 days.
  • Feedback on a transfer (above): a comment waiting for its email confirmation for up to 30 days, then discarded; published feedback for 90 days after the transfer ends, unless the sender or you delete it sooner (“Delete my feedback on this transfer”, or ask support to remove everything sent from your address).
  • Database backups: taken daily and kept for 30 days, used only to recover from failures. File contents are not backed up.

When you delete your account (Settings → Sign In & Security → Delete account — see how it works), it is disabled on every device at once, your share links and upload pages stop working, and everything — files and their copies (including File Restore copies), links, collections, history, devices, settings, sign-in methods, copies of our emails to you and your support conversations — is permanently deleted no later than 14 days after your request. Until then you can restore the account by signing in. We keep only:

  • Payment and refund records, for 7 years, because tax and accounting law requires it.
  • Security and audit records, with your email replaced by an anonymous identifier.
  • Abuse reports, with your email replaced by an anonymous identifier, for up to 2 years.
  • If your account is banned or awaiting a ban decision: that decision and its trail, under an anonymous identifier, for up to 2 years. Otherwise your abuse-prevention record is deleted with the account.
  • Support conversations only while a refund dispute, chargeback or abuse case about the account is open.
  • A bounce or complaint record for your address, if one exists, so we never email it again.
  • This month's usage totals, linked to a hashed form of your email until the month ends plus 35 days, so limits can't be reset by deleting and re-creating an account.
  • A deletion record (a hashed form of your email and the dates) for 37 days. Backups expire within 30 days and are never used for anything else; if we ever restore one, your deletion is applied again before the service resumes.

Files other people already downloaded, and their own records of what you shared with them, stay with them. Teams: files shared in a team workspace belong to the team. When a member leaves, the team keeps them; the team's owner or an admin can instead delete a member's data (it is gone within 14 days), and only the owner can delete the whole team (everything is deleted within 14 days; members are told first and can download their files meanwhile).

7. Security

All traffic is encrypted in transit (TLS; direct transfers use encrypted peer-to-peer connections). Relayed transfers are encrypted on your device by default, and staged content is encrypted at rest on access-controlled infrastructure; internal access follows least privilege. The full account — what each kind of transfer is protected by, and the known limits — is on How SendFlo encrypts. No service can promise absolute security — see the Terms for our liability framework — but security decisions here consistently favor storing less: passwords only as salted hashes, no card data, and IP addresses as they are only in the audit log and each device's last one, for the times above. The audit log can't be edited: the database refuses changes to it, and a daily seal of each account's entries is written to storage nobody can alter or delete, us included.

8. Compliance posture (incl. health data)

Plain statements, so nobody has to guess: GDPR and CCPA rights apply as described below. SendFlo is not HDS-certified (France's certification for hosting personal health data) and is not certified under ISO 27001 — please do not use SendFlo to store personal health data subject to HDS. We publish an internal readiness roadmap and will only ever claim a certification after an accredited audit, with the certificate to show for it. End-to-end encrypted links keep the decryption key in the link fragment, which never reaches our servers — for those transfers we cannot read the content we host.

9. Your rights

You can access, correct, export, or delete your data — most of it directly in the app: history and devices; a copy of the data we keep about your account from Settings → Sign In & Security → Your data (a zip of machine-readable JSON files, ready within minutes, once a day — it leaves out the records of our security checks, which we keep to prevent fraud and abuse; ask us about a decision that affects you and a person answers); and deleting your whole account from Settings → Sign In & Security → Delete account. For anything else, write to support@sendflo.app from your account email. EU/UK residents additionally have GDPR rights (objection, restriction, portability, and complaint to a supervisory authority); California residents have the corresponding CCPA rights. We do not discriminate for exercising them.

10. Cookies and analytics

We use functional cookies and local storage to run the service: your session, your preferences, and service state. We also use Google Analytics to understand how people find and use SendFlo — which pages are visited, where visitors come from (including the campaign tags of an ad or link that brought them), and whether downloads, sign-ups and purchases work — so we can improve it. When analytics cookies are allowed, Google Analytics sets two cookies of its own (_ga and _ga_G26N4BDHD9), which we set to expire after 13 months. Our iPhone and Android apps measure the same things through Google Analytics for Firebase, which keeps a random app-instance identifier on the device instead of cookies and never collects the advertising identifier. The desktop app sends nothing to Google Analytics.

On pages that show a transfer — download links, file requests and shared collections — analytics records only the kind of page and general facts about the transfer: how many files, their combined size and general type (video, document, image…), how the link is set up (for example preview-only or encrypted), the sender's plan, and whether the download worked. In place of the link it records coded references that only SendFlo can match: one for the transfer, one for the account that sent it, and — when someone opens the copy of a link that was emailed to them — one for that recipient. It never receives file names, link addresses, names, email addresses, or the decryption key of an end-to-end encrypted link, so Google cannot use our analytics to find, open or identify anyone's transfer.

When you are signed in and analytics is allowed, we also give Google Analytics a coded reference for your account — never your name or email address — so your visits from different devices count as one person. A coded reference opens nothing. SendFlo can match these references to its own records to understand how the service is used; Google cannot.

In the EU, the EEA, the UK and Switzerland, analytics cookies (and, in our apps, the app-instance identifier) stay off until you accept them in the cookie banner. Until then our pages send Google Analytics only cookieless signals — the cleaned page details above, with no cookies and no identifier that lasts beyond the page — which Google uses to estimate overall visitor numbers. Anyone can change their choice at any time with “Cookie settings” — here, or in the footer of the app and of download pages. Google's advertising features and data sharing are turned off: no advertising cookies and no cross-site tracking.

11. Children

The service is not directed at children under 13, and we do not knowingly collect their data; if you believe a child has an account, contact us and we will delete it.

12. Changes

We will update this policy as the service evolves and give notice of material changes by email or in the app before they take effect.

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