Privacy Policy
Last updated: 3 November 2026
The quick version
- By design, files go straight between your browser and storage in the EU, not through our servers.
- We never sell your data, never show ads, never train AI with it.
- No third-party analytics, and no tracking of what you do.
- You sign in with Google or Microsoft, or with a one-time link sent to your e-mail, so we never see a password.
-
Signing in with Google gives us your name, e-mail address and profile picture, and nothing else from your Google account.
- Not end-to-end encrypted yet. The storage provider holds the keys, so we could technically retrieve your files.
- Ask us any time for a copy of your data, or to delete it. We answer.
This is just a summary. The full text below is what applies.
The BigFatFile web application is run by
Grupul pentru Consultanță și Arhitectură Software SRL (EUID: ROONRC.J40/20907/2004),
the data controller for the purposes of the GDPR. This document explains what we collect, why, where it is stored and who else
processes it.
If you have questions about this policy, or wish to exercise any of the rights described below, please
contact us.
This policy applies to the BigFatFile website and service only. It does not apply to information collected offline or through any
other channel.
Information we collect
-
Account information: the e-mail address and profile name supplied by Google or Microsoft when you sign in, or
the e-mail address you sign in with by one-time link and the name you type. Google also supplies your profile picture; what we
receive from Google is listed in full under "Data from your Google account" below. We never receive or store a password. You may
optionally add a display name and a brand logo. If you first arrived through a link we placed in an advertisement, we also keep
the campaign tags that link carried, so we can tell which advertisements bring sign-ups. That record stays with us and is never
shared with the advertising platform.
-
The files you transfer: the file contents themselves, along with file names, sizes and types, and the
recipients you choose to share a transfer with.
-
How often a transfer or drive is downloaded: a count of downloads, the dates of the first and the last one, and
an estimate of how many bytes they came to. The sender sees the count and the dates on their own transfers; the byte estimate is
for our own operations. We use these figures to apply the rule in our Terms against publishing links for
the general public for mass downloads. The count records how many separate people downloaded, not who they were: an anonymous
visitor is counted by the network address the request arrived from, which we do not store on the transfer or drive.
-
Billing information: if you buy a paid plan, the plan you are on and the subscription and customer identifiers
assigned by Stripe, our payment processor. Checkout happens on Stripe's own secure pages: what you enter there, including your
payment details, goes to Stripe directly, and we never receive or store card numbers or bank details.
-
Messages you send us: anything you include when you contact support through the in-app form or by e-mail, or
when you post on our feature-request site.
-
Technical log data: IP address, browser type, timestamps and the pages requested. This is ordinary web server
logging, retained for security and troubleshooting. While an upload is in progress, its record also notes the browser type and
the transfer speed, so we can investigate a transfer that stalls. These notes are discarded with the upload record, except that
an upload which fails keeps a note of the browser it failed in.
How we use it
- to provide the transfer service and store the files you upload;
- to authenticate you and secure your account;
- to operate your subscription and apply your plan's limits, if you buy a paid plan;
- to send service e-mails, such as transfer notifications;
- to send occasional product news by e-mail, if you keep that preference on;
- to respond when you contact us;
- to keep the service running reliably and to investigate abuse or technical faults.
Product news is optional. It starts switched on for new accounts, and you can untick it when you create your account. You can also
turn it off at any time with the "New product features and offers" switch in your profile settings, or with the unsubscribe link
every such e-mail carries. These e-mails contain no tracking: we do not record whether you open them or what you click in them.
We do not sell your personal data, we do not serve advertising, and we do not use your data to build advertising or marketing
profiles. We also do not use your data (your files, their metadata, or anything else we hold about you) to train
artificial-intelligence models, whether our own or anyone else's, and we do not pass it to any third party for that purpose. Our
business is storage and transfer; your data is never the product.
Data from your Google account
This section applies when you sign in with Google, either with the "Sign in with Google" button or with the Google sign-in prompt
shown on our pages.
-
What we access: we ask Google only for its basic sign-in permissions, the
openid,
email and profile scopes. With them, Google gives us your Google account identifier, your e-mail
address and whether Google has verified it, your name, the address of your profile picture and your language setting. We do not
ask for access to Gmail, Google Drive, Google Contacts, Google Calendar or any other Google service, and we never receive your
Google password.
-
How we use it: only to create your BigFatFile account, to sign you in, to keep your name and picture up to date
in the app, and to show your name and e-mail address where the service needs them, for example to the people you send a transfer
to. We use it for nothing else.
-
How we store it: in your account record, in our database on a server in the EU. When you sign in, Google also
issues short-lived sign-in tokens, which are kept with your account record. We do not use them to call any Google service on
your behalf.
-
Who we share it with: we do not sell, rent or hand over data from your Google account to anyone. Your name and
e-mail address can appear in e-mails we send for you, such as a transfer notification, so they pass through Postmark, our e-mail
delivery provider. Apart from that, we disclose this data only where the law requires us to.
-
How we protect it: all traffic between your browser, our servers and Google is encrypted with TLS, and only our
own administrators can access the database that holds it.
-
How long we keep it, and how to delete it: we keep it for as long as your account exists. If you ask us to
delete your account, by writing to [email protected], the data from your Google
account is deleted with it. You can also remove BigFatFile's access at any time on your
Google account permissions page. That stops future
sign-ins with Google, but it does not delete your BigFatFile account on its own.
BigFatFile's use and transfer of information received from Google APIs adheres to the
Google API Services User Data Policy, including the Limited Use requirements. We do not use data from your Google account for advertising, we do not sell it, and we do
not use it to develop, improve or train artificial-intelligence or machine-learning models.
Where your data is stored
Transferred files are stored on Cloudflare R2 object storage in buckets placed under R2's EU jurisdiction restriction, which
means the objects are stored and processed within European Union data centres. Account data and transfer metadata are held in a
database on a server located in the EU. All objects are encrypted at rest by the storage provider, and all traffic to and from the
service is encrypted in transit with TLS.
Your files travel directly between your browser and that storage, over links signed for the individual transfer. By design, their
contents do not pass through our own servers, and nothing we run inspects, scans or processes them there. Our systems hold only the
metadata: names, sizes, types and who a transfer is shared with. This describes how the service is built today. It is not a
commitment: if the design changes, this policy will be updated to say so.
Please note that we do not currently offer end-to-end encryption. Your files are encrypted in transit and at rest, but the
encryption keys are held by the storage provider rather than by you, which means we remain technically capable of retrieving the
content of your transfers from that storage, in the same way you do. We do so only where necessary to operate the service or where
we are legally required to.
How long we keep it
-
Files you delete are permanently removed from storage when your plan's Trash window ends, at least 30 days, or sooner if you
erase them yourself.
-
Previous versions of files you overwrite are removed when your plan's version history window ends, at least 30 days, or sooner
if you erase them.
- Uploads that fail or are abandoned part-way are discarded within about three days.
- Account data is kept until you ask us to delete your account.
- Server logs are kept only as long as needed for security and troubleshooting.
Cookies
BigFatFile uses cookies that are strictly necessary for the service to work, mainly to keep you signed in and to remember your
cookie preferences. We do not use advertising cookies, and there is no advertising or third-party analytics on any of our pages. The
only telemetry we run is technical error and performance monitoring of the application itself, which records how our software
behaves, NOT what you do, and never for profiling. Checkout for paid plans happens on Stripe's own payment pages rather than on our
site; cookies Stripe sets there are strictly necessary for taking the payment and preventing payment fraud.
A cookie consent dialog is presented on your first visit. You can view your choices at any time using the "Cookies" link in the
footer, or disable cookies entirely in your browser, but note that disabling strictly necessary cookies will prevent you from
signing in.
Who else processes your data
We use the following providers to operate the service. Each processes data only as needed for its function:
- Cloudflare: object storage for transferred files (EU jurisdiction), DNS and reverse proxy for the website.
-
Webdock ApS: server hosting in the EU for the application, its database, our support and feature-request tools,
and the newsletter tool that holds the subscriber list.
-
Google and Microsoft: sign-in, if you choose one of them instead of a one-time e-mail link. The provider you
choose receives the fact that you authenticate with us. We do not use either for advertising or analytics.
-
Stripe: payment processing for paid plans. Checkout happens on Stripe's payment pages: Stripe receives what you
enter there, such as your e-mail address, billing address and payment method, and also processes it as an independent controller
for payment fraud prevention and financial compliance. We receive confirmation of the subscription and billing identifiers,
never your card details.
-
Postmark: delivery of outgoing e-mail, including transfer notifications, messages sent through the in-app
support form, sign-in links for the feature-request site, and the product newsletter.
-
chroot.ro: hosting of our incoming e-mail, which receives and forwards messages you send to our published
addresses.
-
Monti APM: application performance monitoring, which records technical error and timing data from our servers
and from the application code running in your browser. It measures how our software behaves, not what you do with it.
Our support desk, feature-request site and newsletter tool run on our own servers rather than on a third-party platform, so what you
write there and who subscribes to the newsletter are not passed to another provider beyond the e-mail delivery described above.
These providers have their own privacy policies governing how they handle data. We do not share your personal data with anyone else
except where required by law.
GDPR data protection rights
If you are in the European Economic Area, you have the following rights over your personal data:
- Access: to request a copy of the personal data we hold about you.
- Rectification: to have inaccurate data corrected or incomplete data completed.
- Erasure: to have your personal data deleted, under certain conditions.
- Restriction: to have our processing of your data restricted, under certain conditions.
- Objection: to object to our processing of your data, under certain conditions.
- Portability: to receive your data in a portable format, or have it transferred to another organisation.
Exercising these rights is free of charge. To do so, please contact us; we will respond
within one month. You also have the right to lodge a complaint with your national data protection authority.
CCPA privacy rights
If you are a California resident, you have the right to request that we:
- disclose the categories and specific pieces of personal data we have collected about you;
- delete the personal data we have collected about you;
- do not sell your personal data, noting that we do not sell personal data to anyone.
To exercise these rights, please contact us; we will respond within one month.
Children's information
BigFatFile is not directed at children and we do not knowingly collect personal data from children under the age of 13. If you
believe a child has provided us with personal data, please contact us and we will remove
it promptly.
Changes to this policy
We may update this policy from time to time. Material changes will be reflected on this page. Please also read our
Terms and Conditions.