Privacy Policy

Last updated: 16 November 2026

This policy explains what personal data Disfile collects, why, who it is shared with, how long it is kept, and how you can exercise your rights over it. The controller of that data is the operator named under “Operator and contact details” at the end of this policy.

Data we collect

We collect the following categories of data:

  • Account data — your email address, a hashed password, and an optional display name
  • Terms acceptance — the version of the Terms of Service you accepted and when, and a record that we emailed you about a change to the Terms
  • File data — the files you upload (stored with Backblaze B2) and their metadata (name, size, type, folder location). Files may contain personal data about other people; see "Content you upload" below
  • Share links — the settings of each link you create, such as its expiry date and, if you set one, its password (stored only as a hash)
  • Discord link — if your Discord account is linked to your Disfile account, your Discord account’s numeric user id, so the bot’s /get and /list commands can find your files
  • API keys and webhooks — the keys you create (stored only as hashes), the URLs you register for webhooks, and a record of each webhook delivery attempt
  • Billing data — if you subscribe to a paid plan, Stripe collects your card details and billing address and processes your payment. We do not store them. We store your plan, subscription status, price and billing dates, the card brand and last four digits for display, and Stripe’s customer and subscription references
  • Order and refund records — for each paid order, the plan and price shown to you, the Terms version, your confirmations (18 or older, EU consumer, immediate start, loss of the withdrawal right) and when you gave them; and, for each withdrawal or refund, what was refunded and when. These records hold no IP address or browser details
  • Guest session — if you use Disfile without an account, a random session id (kept in a cookie on your device) and the temporary files you upload; the session record itself holds no IP address or browser details
  • Request logs — the IP address and browser user-agent of each request made to Disfile, with the time, the action requested, and your account if you are signed in. This includes people who only visit a share page, and guests
  • Reports about content — if you report content, what you write, your name, if you give one, the optional email address you give, and a keyed hash of your IP address used only to spot repeat reports (see "Reporting illegal content" below)
  • Moderation records — when we remove or restrict content or an account, the decision, the reason and the rule it relied on
  • Emails — the messages we send you (we keep only a delivery record, not the message text), and, if you write to one of our shared addresses (such as support), your email address and name, the message itself, and any attachments
  • Technical logs — warnings and errors from our servers, which do not include file contents or passwords
  • Backups — copies of our database
  • Advertising data — Google’s consent tool collects your IP address, browser details and consent choice on a public share page that shows ads, and on any page where you open "Cookie settings". Once you consent, Google’s ad code on a share page that shows ads also collects advertising identifiers and ad requests (see "Advertising" below)
  • Cookies and browser storage — see "Cookies" and "Your browser’s storage" below

Cookies

Disfile sets the following strictly-necessary, first-party cookies:

  • refresh_token — HttpOnly, keeps you signed in between visits for up to 30 days; removed when you sign out; never readable by page scripts
  • refresh_token_present — a non-secret, readable flag that mirrors whether the cookie above exists, so the app can avoid an unnecessary network request; same 30-day lifetime
  • guest_session — HttpOnly, keeps your guest session for up to 30 days so you can come back to your temporary files without an account; never readable by page scripts
  • guest_session_present — a non-secret, readable flag that says a guest session may be waiting on this device, so the app only asks to resume one when it could succeed; same 30-day lifetime
  • dfx — HttpOnly, an opaque, signed marker of whether your plan includes an ad-free share page, set when you sign in and valid for up to 30 days; carries no identifying information on its own
  • share_unlock — HttpOnly, keeps a password-protected share link unlocked during your visit; set only after you enter the link’s password, scoped to that one link, and expires within 1 hour

On a public share page that shows ads, or once you open "Cookie settings" (see below), Google Funding Choices also sets its own first-party consent cookies. These store the choice you make and let the same choice be honoured on your next visit.

Google may additionally set advertising cookies, but only on a public share page that shows ads, and only once you have consented via the consent message described under "Advertising" below.

You can review, change, or withdraw your cookie choice at any time through the "Cookie settings" link, available in the site footer and in the sidebar of the dashboard and every share page.

We do not use any other third-party tracking or analytics cookies.

Your browser’s storage

Disfile keeps a few functional items in your browser’s storage. They stay on your device and are never used to track you. The only one we ever receive is the upload reference below, which your browser sends back to us when you resume that upload.

In local storage, which lasts until it is removed:

  • The details of an upload still in progress (file name, size, and an upload reference), stored under your account or guest-session id, so an interrupted upload can be resumed after a reload. It is removed when the upload finishes or is cancelled, when you sign out, and when a guest session is claimed by a new account
  • disfile-color-scheme — whether you chose the light or dark theme
  • disfile:auth:pending-next — the page you were heading to when you created your account, so signing in after confirming your email takes you there. It is removed when you sign in, and is no longer used after 24 hours

In session storage, which your browser clears when you close the tab:

  • disfile:billing:pending-change-plan — the plan you are switching to while your bank confirms the payment, so the change can be shown when you come back
  • disfile-storage-banner-dismissed — that you closed the storage-usage banner
  • disfile-files-view — whether you view your files as a grid or a list
  • disfile:guest-signup-nudge-dismissed — that you closed the prompt to create an account
  • disfile-upload-upgrade-dismissed — that you closed the prompt to upgrade your plan

Who we share data with

  • Backblaze B2 — stores the files you upload (EU region, Amsterdam, Netherlands)
  • Amazon Web Services (AWS) — hosts the servers and databases that run Disfile, their backups, and our logs (EU region, Frankfurt, Germany)
  • Resend — sends our emails to you (such as account confirmation, billing and data-export emails, notices about changes to the Terms, and content-moderation notices telling you we removed or restricted something you own) and receives email sent to our shared addresses, so it processes your email address and the message content (United States)
  • Cloudflare — delivers file downloads from storage to the person downloading, so it processes the file content in transit and the downloader’s IP address (global network, United States company)
  • Discord — if you use the bot, receives the Discord id of the person who runs a command and the reply the bot sends, which contains file names and share links (United States)
  • Stripe — processes payment for paid plans, holds your payment method, and issues the invoices and credit notes for your subscription. Stripe contracts through its Irish company, and acts as an independent controller for its own fraud-prevention and legal compliance (United States parent)
  • Google (AdSense and Funding Choices) — shows the consent message, and serves ads on the public share page to visitors without an ad-free plan. We share responsibility with Google for collecting your data through the consent and ad code and sending it to Google. After that, Google alone decides how it uses the data, as an independent controller (United States)
  • Our accountant or tax adviser — where we use one, for bookkeeping and tax records

We do not sell personal data, and we do not share it with anyone outside this list except where required by law, and except to the webhook URLs you register yourself, which receive the event details you set them up for.

The Discord bot

We do not use Discord sign-in (OAuth) and we ask Discord for no account permissions. Linking connects your Discord numeric user id to your Disfile account.

The bot’s /get and /list replies are shown only to the person who ran the command. They contain file names and share links. /get also creates a public share link for the file if there is none yet. Discord processes what you type and what the bot replies under Discord’s own privacy policy.

Content you upload

The files you upload may contain personal data about other people. You are responsible for having the right to upload and share them. We store and deliver your files on your instructions and do not routinely review their content. When you upload a file, an automated check reads its name, its declared type and its first few kilobytes to identify the file type, and refuses executable files such as programs and installers, to keep them off the service. No person looks at the file for this check. We may look at specific content when someone reports it, to enforce our Terms, or when the law requires it.

Reporting illegal content

Anyone can report content they believe is illegal, using the Report link on a share page or by emailing us. A report holds what the reporter wrote, their name and an email address if they chose to give them, and a keyed hash of their IP address, which cannot be turned back into the address and is used only to recognise repeat reports. The name and email are used only to handle the report and follow up with the reporter, and are never shown to the owner of the content.

The reporter’s IP address also appears in the request logs like every other request, and is handled as described under "How long we keep data".

If you reported something and want to see, correct or delete your report, write to support@disfile.io from the address you gave and we will find it by that address.

Advertising

The public share page (the page a link you create resolves to) shows ads served by Google AdSense, unless the file or folder owner is on a plan that removes them. AdSense may use its own cookies and similar technologies to select and measure ads.

Because we place Google’s consent and ad code on our pages, we share responsibility with Google for collecting your data through that code and sending it to Google. After that, Google alone decides how it uses the data, and that processing is governed by Google’s own privacy policy, not this one.

Ads load only after you consent, wherever you are. On a share page that shows ads, Google’s consent tool loads when the page opens, before you choose, so Google receives your IP address and browser details at that point. The same happens on any page if you open "Cookie settings". The ad code itself loads only after you consent. The consent tool shows a message asking for your choice before any advertising cookie is set. It presents consenting and not consenting as equally prominent choices. If you do not consent, or Google does not show the message in your region, no advertising cookies are set and no ads load on that page.

How long we keep data

We keep each kind of data for the period below.

  • Account and file data — kept for as long as your account is active. Deleting a file or folder moves it to Trash for 14 days, during which you can restore it; after that it enters a further 30-day retention period — no longer visible or recoverable through the product — before it is permanently deleted
  • Deleted accounts — when you delete your account, you have 30 days to change your mind by signing in and restoring it. After that your account and files are permanently deleted
  • Unconfirmed email address — a new email address you ask to switch to but never confirm is cleared from your account 31 days after the request
  • Advertising data — what Google’s consent and ad code collects goes from your browser straight to Google, and we keep no copy. Google keeps it for as long as its own policy says. Our own request logs are a separate record, listed below
  • Terms records — we keep a record that we sent you a notice about a change to the Terms, and the version of the Terms you accepted, for as long as your account exists
  • Order and refund records — kept for as long as your account exists and for 3 years after it is deleted, as evidence in case of a consumer dispute. An order that was abandoned before reaching Stripe is deleted after 7 days. Stripe keeps its own invoices and payment records for as long as the law requires it to
  • Guest sessions — a guest session lasts 30 days from your last visit. The temporary files you upload as a guest are deleted automatically on their own timer, shown as a countdown on each file. Seven days after a guest session lapses, the session record and anything still left under it are permanently deleted. To limit abuse, the number of guest sessions started from one network address is counted in our servers’ memory for up to 24 hours; that count is not written to a database
  • Guest files after you sign up — if you create an account while you have a guest session, your temporary files move to your new account and the guest session ends. The files keep their original deletion schedule, and from then on the rules for your account apply to them
  • Records of the emails we send you — kept for 90 days from when they are sent, then permanently deleted. This covers emails such as "your export is ready", a notice about the Terms, or a content-moderation notice telling you we removed or restricted something you own. A record holds the recipient, the template and the subject, not the message text
  • Emails to our shared addresses — emails you send to our shared addresses (such as support) are kept for 12 months after the last message in the conversation, then permanently deleted together with any attachments
  • Data exports — a data export is available to download for 7 days after it is ready and is then removed
  • Failed data exports — a data export request that fails is deleted 30 days later, together with any partial export file it left behind
  • Request logs and the audit trail — IP addresses and user-agents in request logs and the account audit trail are removed after 6 months. The rest of the audit trail — including, when you change the email address on your account, the old and new addresses, and the records of our moderation decisions — is kept for 12 months and then permanently deleted, also after your account is deleted, so a disputed action can still be investigated
  • Reports about content — a report about content is kept for 12 months. The hashed IP address on it is deleted after 30 days
  • Server logs, webhooks, sessions and API keys — warnings and errors in our server logs are kept for 30 days. Records of webhook deliveries are kept for 30 days. A sign-in session record is kept for 30 days after it expires, and a revoked API key record for 90 days after you revoke it
  • Backups — copies of our database remain in backups for 90 days. A backup can therefore still hold data that was since deleted or scrubbed, such as a deleted account or an IP address removed from the logs, until the backup itself expires. If we ever have to restore a backup, we delete that data again before the service goes back online

Your data protection rights

You have the right to:

  • Access the personal data we hold about you
  • Correct inaccurate data
  • Request erasure of your data
  • Receive a portable copy of your data — you can download all of your data yourself from the data export in your settings
  • Request restriction of certain processing
  • Object to processing based on legitimate interest — see below
  • Withdraw a consent you gave, such as for advertising cookies, at any time, without affecting what was done before

Your right to object: where we rely on legitimate interest (such as request logs, technical logs, backups, content reports, moderation records, notices about Terms changes, and anything else we base on legitimate interest above) you can object at any time; we then stop unless we have compelling legitimate grounds or need the data for legal claims.

To exercise any of these rights, contact us at support@disfile.io. We answer within one month. Deleting your account exercises the erasure right for most of your data directly, subject to the retention periods above; some records we keep on purpose after deletion (order and refund records, the audit trail), for the reasons and periods stated there.

You can also complain to the Czech data protection authority, the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, ÚOOÚ, uoou.gov.cz), or to the authority where you live.

International transfers

Your files and the data held on our servers are stored in the EU: Backblaze B2 stores files in its Amsterdam region and AWS runs Disfile in its Frankfurt region.

Backblaze, AWS, Cloudflare, Resend, Discord, Stripe, and Google are based in the United States, so data can be accessed from or processed there — Cloudflare may serve a download from any location in its global network. For each of these transfers outside the EU we rely on the European Commission’s standard contractual clauses in the provider’s data processing terms and, where the provider is certified under it, the EU–US Data Privacy Framework.

Children’s privacy

Disfile is not directed at children under 16, and we do not knowingly collect personal data from them. You must be at least 16 to use it.

Changes to this policy

We may update this policy from time to time. The "Last updated" date at the top of this page shows when it last changed, and we tell you by email or in the app about a change that matters to you.

Operator and contact details

Disfile is operated by Andrés Paredes, a sole trader registered in the Czech trade register (IČO 14036614), with a registered address at Uralská 689/7, 160 00 Praha 6 – Bubeneč, Czech Republic. Andrés Paredes is the controller of the personal data described in this policy.

Questions about this policy, or requests to exercise your data rights, can be sent to support@disfile.io.