This policy explains what Just Send Files stores, why, where, and for how long. The short version: we store your files only as long as the Room lives, we use no advertising services and no analytics that track you, and we do not sell or share your data. The controller is the person named in the legal notice; write to justsendfiles.dev@gmail.com for anything in this policy.
What we store
- Your files, exactly as uploaded, until the Room expires or is deleted. Files are stored byte for byte, including any photo metadata they carry (location, camera, date), and are delivered the same way to everyone who has access. For photos we also make a small thumbnail and, for iPhone HEIC photos, a JPEG copy, so they can be shown in a browser; both are deleted with the file.
- Room metadata: file names, sizes, content types, SHA-256 checksums, the title and description you typed, the mode, the expiry date, the date taken, camera, dimensions and whether location data is present (read from each photo’s or video’s own metadata, to sort and show them), and a hash of the PIN if you set one. PINs are never stored in clear text.
- Account data, only if you sign in: with Google, your Google account id, email address, display name and profile photo, as Google provides them; with an email code, your email address and an account id. When you ask for a code we keep, for 10 minutes, a keyed hash of the code (never the code itself) and an encrypted sign-in ticket for that address, deleted when the code is used, or once it has expired. We also keep your plan, the date of your last activity, your storage usage, how you sign in (Google or an email code) and, if we ever changed your plan or restricted your account by hand, a short internal note explaining why; that log of administrative changes is kept for one year. We count the Rooms you create and the data added to them in rolling 30-day windows, to apply your plan’s limits; the operator sees these counts and your sign-in method to administer accounts, never the files themselves. When you edit a document while signed in, the file you are working on and your edits are kept on your account for 24 hours after your last change, so you can continue on another device; then they are deleted. Without an account they stay on your device. Once a week we also write a backup of the account records (id, email, name, sign-up and last sign-in dates, plan and any internal note) and a list of live Rooms (title, owner, link code, dates and file counts, never the files) to our file storage, so that paid plans can be restored after a fault; the last four weekly copies are kept, so an account or Room you delete disappears from them within four weeks. Files are never part of any backup.
- Rooms you take part in: when you join, comment or upload in a Room, the host and other members see your name and photo; the host also sees your email address. If you have no account, you are shown under a generated name and your uploads are tied to a random device id that your browser keeps. Hosts may type a list of email addresses allowed into a Room; we store that list with the Room and use it only to check who may enter. Comments, replies and hearts stay with the Room until it is deleted.
- Notifications: an inbox per account or device with news about your Rooms (new files, requests, replies), kept 90 days.
- Room statistics: for each Room we count visits per day. To count unique visitors we store, for that day, a keyed hash of the visitor’s IP address that cannot be turned back into the address. Each day’s hashes are deleted after 90 days, or earlier with the Room; only the daily totals remain.
- Operational logs: IP addresses, timestamps and request details, kept for up to 30 days in Google Cloud Logging for security, rate limiting and abuse handling. Anonymous quotas are counted against a hash of the address, not the address itself.
- Abuse reports: the link, reason, text, the name and email you give, and a keyed hash of your IP address (used only to count one report per person per link). We use the email to confirm receipt and to send you our decision. A report is deleted 90 days after it is closed, or 180 days after it was made if it is still open by then.
- Site counters: how many Rooms are created and how many files are uploaded per day, and how many distinct visitors the site has per day, week, month and year. For the visitor count, the browser reports when a page loads, and we store, for each day, week, month and year, a keyed hash of the account id or, if you are not signed in, of your IP address and browser type; nothing is stored on your device for this; only we hold the key, and no page, address or other detail is attached. These rows are pseudonymous, not anonymous. Day rows are deleted after 90 days, week rows after 26 weeks, month rows after 13 months and year rows after 5 years.
We use Cloudflare Web Analytics to see how many pages are viewed: it sets no cookies, builds no profile of anyone and gives us only aggregated page views. We also count, in aggregate and without identifying anyone, which kind of site (for example a search engine or a social network) a new Room or account came from. The page keeps that in memory while it is open, nothing is written to your device, and we keep nothing but the daily totals.
Data about people who do not use the Service
Files and Rooms can contain data about people who never use the Service: faces and photo metadata in pictures, the email addresses a host types into a Room’s allowed list, or a person named in a report. Whoever uploads a file or types a list must have the right to share it. We hold that data only as part of the host’s Room, for as long as the Room lives, and we do not use it for anything else; we do not contact these people ourselves, because that would mean looking into the files (GDPR Art. 14(5)(b)). If you are such a person and want something removed, write to justsendfiles.dev@gmail.com or use the report form.
Why we may process this (legal bases)
Performing the service you asked for, including the contract for a paid plan (GDPR Art. 6(1)(b)); our legitimate interest in keeping the service secure, limiting abuse and handling reports (Art. 6(1)(f)); our legal obligations, for example to keep invoices or answer authorities (Art. 6(1)(c)). We do not use your data for advertising or profiling and make no automated decisions with legal effect about you; the only automatic actions are rate limits and PIN lock-outs.
What we do not do
- We do not open, scan, index, compress or analyse the content of your files, except automated steps needed to run the Service: integrity checks (checksums), reading the date, camera and dimensions from a photo’s or video’s metadata and whether it carries location data (we keep only that yes/no, never the location), small preview images of photos and videos, a JPEG copy of HEIC photos, and manual review when a Room is reported.
- We do not use advertising networks, tracking pixels or analytics that set cookies or follow you from site to site.
- We do not require an account to open a Room, download from it or add files to it where the host allows.
Cookies and local storage
We use no analytics or advertising cookies, so we show no cookie banner. We set one cookie, __session, which holds the passes you earned by entering a PIN or by owning a Room, so downloads work; it is kept for up to 400 days but each pass inside it expires on its own, and signing out clears it. Your browser also keeps, on this device only: your sign-in state (Firebase Auth), a random device id used to recognise your uploads and let you follow Rooms without an account, Rooms you visited, files you already downloaded, favourites, your theme, a cached avatar and, for Rooms made before accounts became required, the secret that let this browser manage them. All of this is needed for features you use; nothing is stored for statistics and nothing is shared with anyone. When you are not signed in and open the account menu or pick files to create a Room, we load Google’s sign-in script so it can offer you “Continue as …” with your Google account; Google may then set a small g_state cookie on this site (it remembers that you closed the prompt) and its own cookies on google.com, under Google’s privacy policy. Signing in with Google works the same way.
Providers and data processing agreements
We run on these providers, each bound by a data processing agreement that meets GDPR requirements:
- Backblaze (Backblaze, Inc.) stores the files themselves in B2 Cloud Storage, in its EU Central region (the Netherlands), encrypted at rest. Backblaze acts as our processor under the Backblaze Data Processing Agreement Addendum.
- Cloudflare (Cloudflare, Inc.) serves the site’s domain, delivers downloads and builds download archives. Files pass through it on their way to you; it does not keep them. Cloudflare acts as our processor under the Cloudflare Customer DPA.
- Google Firebase / Google Cloud (Google LLC) runs the website, stores metadata (Firestore, EU multi-region eur3: Belgium and the Netherlands), keeps the operational logs and handles sign-in (Google sign-in, the one-tap prompt and the email-code accounts, through Firebase Authentication). Google acts as our processor under the Google Cloud Data Processing Addendum.
- Resend (Resend, Inc.) delivers the emails this policy mentions: sign-in codes, new files in a Room you follow, a Room about to end or ended, report confirmations and decisions, account suspensions and other account notices, and changes to these terms. It sees the address and the text of each message and sends them from its EU region (Ireland), under the Resend Data Processing Agreement.
No other third party receives your data, except that Google serves the profile photos of signed-in users to whoever sees them in a Room, and that mail you write to our contact address is handled by Gmail (Google), under Google’s terms.
Where your data goes
Backblaze, Inc., Cloudflare, Inc., Google LLC and Resend, Inc. are US companies. Your files and metadata are stored in the European Union, but support and some account services can involve access from the United States. Backblaze, Cloudflare and Google are certified under the EU-US Data Privacy Framework, and their data processing agreements also include the EU Standard Contractual Clauses. Resend sends our emails from the European Union (Ireland); any access from the United States is covered by the Standard Contractual Clauses in its data processing agreement.
Encryption and protection
Files travel over HTTPS and are stored encrypted at rest by the storage provider. Direct download links are signed and expire within five minutes; upload links expire within 15 minutes. The signed passes that let a browser show previews and play videos inside a Room last longer — a few hours for originals, up to 14 days for thumbnails and videos — and every pass stops working the moment the Room’s PIN or link is changed. Links and admin tokens are generated with a cryptographic random generator and cannot be guessed. This is not end-to-end encryption: the operator can technically access stored files, for example to act on an abuse report.
Automatic deletion
Every Room has an end, set when it is made and changeable from its Settings within the plan: up to 3 days on Free, up to 30 days on Plus, and on Pro a Room may be kept for as long as the plan is paid (it is shortened to 30 days when the plan ends). The person who made it is told when it ends. When it passes, a scheduled job that runs every hour deletes the files and their metadata. Unfinished uploads are discarded after 2 days.
Deleting content quickly
Whoever created a Room can delete it with all its files from the screen that gave them the link, from the Room menu, from Settings, or from Your Rooms. Deletion is immediate in the Service and cannot be undone; the storage provider’s copy is purged within two days. Anyone can report a Room through the report form, and we remove reported content that breaks our rules.
Retention
Files are deleted when the Room expires, when the creator deletes them, or when we remove them for policy reasons. When a Room expires, its title and the names of the files it contained (never the files themselves) stay visible to the creator alone, in their account, for 30 days, and are then deleted too. A Room the creator deletes leaves nothing behind. You can delete your account yourself, from your account page: it removes the account, every Room you created with all its files, your membership in other people’s Rooms and your inbox, immediately and permanently. Comments you left in other people’s Rooms stay, shown under “Deleted user”. Files you added to other people’s Rooms stay in those Rooms (their host decides); the link to your account is kept only as an internal id. The weekly account backup is overwritten within four weeks. If you would rather write to us, we do the same within 30 days. Only the site counters described above remain.
Your rights
You can ask us to access, correct, delete or export your personal data, to restrict or object to its processing, and you can withdraw a consent at any time. The practical way to delete your content is the delete action on your Room; your account page has Download my data, which gives you a file with your account, your Rooms and their file lists, your memberships, comments and inbox (write to us for anything else we hold), and Delete account. For everything else write to justsendfiles.dev@gmail.com and we answer within one month. You can also complain to the Romanian supervisory authority, ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal), B-dul G-ral. Gheorghe Magheru 28-30, Bucharest, anspdcp@dataprotection.ro, dataprotection.ro, or to the authority of the country where you live.
Children
The Service is not directed at children under 16, and creating an account (with Google or by email code) requires confirming that you are 16 or older. If you believe a child has given us personal data, write to us and we delete it.
Changes
We will update this page if our practices change, and tell account holders by email and in their account inbox when the change matters to them.