Privacy Policy
Last updated 15 September 2026
Draft for review. Have this checked against the data protection law that applies to you — GDPR, UK GDPR, CCPA or otherwise — and complete every [bracketed] value before publishing.
Last updated: [date]
1. Who is responsible
[legal entity name], [address], is the controller of the personal data described here. You can reach us at [support email]. [If you have appointed a data protection officer or an EU/UK representative, name them here.]
2. The short version
We collect as little as we can get away with while still running a file transfer service. We do not sell personal data. We do not use advertising trackers. We do not read your files, and we do not use them to train anything.
3. What we collect, and why
If you send a transfer
| Data | Why | Lawful basis |
|---|---|---|
| The files themselves | To store and deliver them | Performing our contract with you |
| Filenames, sizes, file types | To show the transfer and build the download page | Performing our contract |
| Any title or message you write | To show it to your recipient | Performing our contract |
| Recipient addresses, if you send by email | To deliver your message | Performing our contract |
| A one-way hash of your IP address | To enforce limits and detect abuse | Our legitimate interest in keeping the service usable |
If you open a transfer someone sent you
| Data | Why | Lawful basis |
|---|---|---|
| A one-way hash of your IP address | To count downloads and limit abuse, without identifying you | Legitimate interest |
| Rough device type and browser family | To tell the sender their files arrived and to fix display problems | Legitimate interest |
| Country, when our hosting provider supplies it | Aggregate reporting to the sender | Legitimate interest |
| Time of the download and which file | To tell the sender the delivery landed | Legitimate interest |
We do not store your raw IP address for analytics. We hash it with a secret salt held only by this installation, which means it cannot be reversed and cannot be compared against another service's records.
If you create an account
Your name, email address, and a hash of your password. If you sign in with Google, we receive your Google account identifier, your email address, your name and your profile picture URL, and store the identifier and the first three. We never receive your Google password.
If you pay
Our payment provider handles card details. We never see or store a card number. We keep a record of what you were charged and when, because tax law requires it.
Support
If you write to us, we keep the message and our reply so we can follow up and improve.
4. What we do not do
- We do not sell or rent personal data.
- We do not use advertising or cross-site tracking cookies.
- We do not profile you or make automated decisions with legal effects about you.
- We do not open, index, read or scan your files to learn what is in them. Automated checks may look at file type and size to enforce limits; a person only looks at a file if we are required to by law, or to investigate a specific abuse report.
- We do not use your content to train machine learning models.
5. How long we keep things
| What | How long |
|---|---|
| Files in a transfer | Until the transfer expires or you delete it, then removed from storage permanently |
| Transfer titles, messages, recipient addresses | Deleted with the transfer |
| Download records (hashed) | [12] months, then deleted |
| Account details | While your account exists, then [30] days |
| Billing records | As long as tax law requires, typically [7] years |
| Technical logs | [60] days |
| Abuse reports and what we did about them | [24] months |
6. Who else is involved
We use a small number of companies to run the service. Each one only gets what it needs, is bound by contract to protect it, and may not use it for its own purposes. The current list is on the sub-processors page.
We may also disclose data where the law requires it, where a valid court order compels it, or to establish or defend a legal claim. Where we are permitted to tell you about such a request, we will.
If the business is sold or merged, data may transfer to the buyer, who would remain bound by this policy until they give you notice of any change.
7. Where data is held
Our servers and storage are located in [region]. Some providers may process data in other countries. Where data leaves [your region], we rely on [standard contractual clauses / an adequacy decision / another safeguard], and you can ask us for a copy of the safeguard.
8. Your rights
Depending on where you live, you may have the right to:
- ask what we hold about you and get a copy;
- have inaccurate details corrected;
- have your data deleted;
- object to processing we base on legitimate interest;
- ask us to restrict processing while a dispute is resolved;
- receive your data in a portable format;
- withdraw consent where we relied on it, without affecting what came before.
Write to [support email]. We reply within [30] days. We will ask you to confirm who you are first, so that a request cannot be used to extract someone else's data. There is no charge unless a request is clearly excessive or repetitive.
If you are unhappy with our answer you may complain to your data protection authority. In the EU this is the authority where you live or work; in the UK it is the Information Commissioner's Office.
9. Children
The service is not aimed at children and we do not knowingly collect data from anyone under 16. If you believe a child has given us data, tell us at [support email] and we will delete it.
10. Keeping data safe
Connections use HTTPS. Stored files are held under generated identifiers, are never publicly addressable, and are reachable only through a signed link that expires within minutes. Passwords are hashed with a modern algorithm and are never stored or logged readably. Stored credentials for our own providers are encrypted. Access to production systems is limited to people who need it.
No system is perfectly secure. If a breach affects your rights we will tell you and the relevant authority within the time the law requires.
11. Changes
If we change this policy in a way that matters, we will tell you by email or in the service before it takes effect. The date at the top always shows the current version.
12. Contact
[legal entity name], [address]. Email: [support email].