Last updated: October 12, 2026
This policy explains how Big File Sharing handles information for guest transfers, signed-in storage, online tools, contacts, messages and billing. It also explains optional email and browser notifications. The service operates under the Big File Sharing brand; privacy requests can be sent to info@bigfilesharing.com or our contact form.
Private means your files are not published in a searchable public gallery. It does not mean the service is anonymous, end-to-end encrypted or unable to process stored files. Authorized support, security and operational access may be needed to deliver the service or investigate abuse.
1. Information we process
- Accounts: your name, email, password hash, role, plan, storage usage and settings. If you use Google sign-in, the configured sign-in flow processes identity information such as email and profile name; we do not receive your Google password.
- Transfers: file contents, names, sizes, types, storage references, timestamps, owner or recipient details, download counters, expiry and link-control settings. A recipient email is used for the transfer workflow, not permission to subscribe that person to campaigns.
- Contacts and messages: saved contact details, invitations, conversation membership, message text, attachment references, timestamps and read information. Other conversation participants can read information shared with them.
- Tools: selected input, operation and output. Browser-only tools may process data locally; server-backed operations send inputs to our processing service. If you enable history, successful activity and output references may be stored.
- Payments: selected plan, amount, method, subscription reference, status, invoices and receipts submitted for manual review. Stripe or Safepay handles enabled card checkout and recurring collection. Do not send us full card numbers or card security codes.
- Support: contact messages, ratings, feature requests and replies, with account or contact details needed to respond.
- Technical records: IP address, browser information, request timestamps, error or security logs, cookies and local preferences. Optional push registration includes an endpoint and subscription keys used to send notifications to that browser.
2. Why we use information
We use information to authenticate accounts, deliver files, apply plan limits, operate conversations and tools, verify payments, issue invoices, provide support, prevent abuse and maintain the service. Where data-protection law applies, the relevant basis may be service performance, legal obligations, legitimate security or operational interests, or consent for optional uses.
We do not sell uploaded file contents or use them to build advertising profiles. Analytics and advertising systems may process device or browsing information as described below; they do not need your uploaded file contents, message bodies or payment receipts.
3. Files, expiry and storage
Guest temporary transfers expire after approximately 24 hours by default; the interface and administrator settings determine the current period. Signed-in temporary transfers follow the plan and link expiry shown in your workspace. Permanent storage means storage without the temporary-link expiry, subject to account status, quota and service rules; it is not a lifetime or backup guarantee.
Unsaved tool inputs and temporary outputs expire according to the tool's stated retention period, normally 2 hours. Turning on history records future successful activity. Choosing to keep or download an output through the history workflow can preserve it in account storage and consume permanent storage. Turning history off does not delete previously saved entries.
Files may be stored on the configured provider, including Backblaze B2, Wasabi or local infrastructure. Expiry and deletion require cleanup jobs and storage operations, not an exact-second promise. Failed cleanup may need retry. Successful deletion of a saved history item removes its retained output and releases quota; deleting your copy cannot remove copies already downloaded by someone else.
4. Other retention and deletion requests
Contacts, messages, preferences and saved activity may remain while needed for your account or conversations. Deleting a file does not automatically remove every message, transaction or support record referring to it. Payment and invoice records may be retained for accounting, disputes, fraud prevention or legal obligations after an account-deletion request.
Technical logs, operational backups and support records are retained according to their security, recovery and legal purpose. We do not promise instant erasure from every backup or a fixed period that the system does not enforce. Contact us for criteria relevant to a specific record or to request account deletion; this policy does not promise an automatic account-deletion button.
5. Who receives information
Recipients and conversation members receive what you share with them. Download links may be forwarded. Optional passwords, expiry and download limits reduce access but do not prevent copying of downloaded files. Share passwords through a separate channel.
Hosting and storage providers process stored data; configured Maileroo or Brevo services may deliver emails; Stripe and Safepay process enabled card payments and subscription billing; browser push services route opted-in notifications. Google services may provide sign-in, analytics or advertising when configured. Providers process information necessary for their function under their terms and applicable arrangements. We may disclose information when legally required or necessary to address fraud, abuse or safety issues.
6. Email, marketing and browser push
Security, account, receipt-review and requested transfer messages are separate from optional campaigns. Account campaign-email and campaign-push preferences default off. Uploading or receiving a file, creating an account or reading this policy is not marketing consent.
Change campaign preferences in Account & Billing. Campaign emails include an unsubscribe route. Browser push requires explicit browser permission as well as applicable workspace preferences and plan availability. Disable a browser in notification preferences or revoke permission in browser settings. Essential account messages can continue independently of campaign preferences.
Campaign reporting may include delivery, failures and an open-tracking request when an email image loads. Image blocking, privacy proxies and bots affect these counts; they are not proof that a human read a message. A public campaign landing link does not grant access to private files.
7. Cookies, analytics and advertising
Cookies, local storage and similar technologies support sign-in, theme and UI preferences, and security. Enabled Google Analytics can measure page activity. Google AdSense and configured advertising providers may use browsing history and identifiers to select, measure or limit advertisements.
Google and other advertising vendors may set cookies based on visits to this or other websites. Manage Google's personalized advertising through My Ad Center; participating vendors provide choices through AboutAds. See Google's partner-site disclosures and our Cookie Policy.
A configured consent manager may present regional choices. If no consent controls appear or they do not work, contact support; this text alone does not establish that every non-essential script is consent-gated. Browser controls can also restrict tracking. Refusing marketing does not remove essential account or security processing.
8. Security and international processing
We use HTTPS/TLS and access controls. Share passwords are not end-to-end encryption. We cannot guarantee a file, link, conversation or provider will never be compromised. Avoid regulated sensitive data unless you have confirmed the service meets your requirements.
Providers may process information outside your country. Using the service is not a blanket waiver of international-transfer protections. Required contractual or other safeguards depend on the providers and jurisdictions involved; ask support about a specific requirement before sending regulated information.
9. Your privacy rights
Depending on applicable law, you may request access, correction, deletion, restriction or portability, object to processing, withdraw optional consent, or complain to the appropriate supervisory authority. Contact info@bigfilesharing.com or our contact form; we may request proportionate identity verification. Requests are handled within applicable legal timeframes, with an explanation of lawful retention or access restrictions.
We do not intentionally seek information from children under 13. If a child has supplied personal information, contact us to investigate and handle deletion as required. Local rules may require a higher age or guardian permission.
10. Changes and contact
Material changes may be announced in the workspace or by email where appropriate. The date above records this revision. New consent will be requested where required; a policy update does not opt you into marketing. Contact info@bigfilesharing.com or our contact form for privacy concerns.
Related policies: Terms of Service · Privacy Policy · Refund & Cancellation Policy · Cookie Policy · Acceptable Use · Security · Disclaimer.