Skip to content
FilesUp
How it worksTrustAppsQuestions
PTEN
Open FilesUp
Home/Cookies and local storage

On-device technologies

Cookies and local storage

FilesUp uses technologies needed to provide the service and, only with your permission, Google Analytics to analyse visits and usage.

Effective from 14 August 2026

On this page
  1. 1. Your analytics choice
  2. 2. Strictly necessary cookies
  3. 3. Local Storage and Session Storage
  4. 4. Optional Google Analytics
  5. 5. Cache Storage and service worker
  6. 6. How to manage these technologies
  7. 7. Contact and changes

Contacts

Privacy and rightsprivacy@filesup.appContent and abuseabuse@filesup.app
TermsPrivacyCookiesAcceptable useDelete accountReport

1. Your analytics choice

On your first visit to each domain, we ask you to allow or reject Google Analytics. The Google tag is not loaded and no request is sent to Google before you allow it. Rejecting analytics does not restrict any FilesUp feature.

Your choice is stored only in Local Storage for the relevant domain. You can change it at any time through “Cookie preferences”; withdrawing consent does not affect processing that was lawful before withdrawal.

2. Strictly necessary cookies

Names without the __Host- prefix may appear only in local environments without HTTPS. In secure production, the session cookie uses that prefix plus Secure, HttpOnly and SameSite=Lax attributes.

NamePurposeDuration
__Host-filesup_session / filesup_sessionKeeps you signed in after OTP verification. It is HttpOnly, limited to the service and used to authorise requests.Until the session expires, you sign out or it is revoked.
filesup_public_tokenExchanges a public-link token for an HttpOnly cookie scoped to that conversation/transfer path, so the credential need not remain in the URL or accompany every request manually.No more than 10 days, limited by share expiry or earlier revocation.

3. Local Storage and Session Storage

A modern link token starts in the URL fragment (#), which is not sent to the web server. The app then submits it in a protected header to obtain the resource-scoped public cookie.

KeyLocationPurpose and duration
filesup.locale / filesup-marketing-localeLocal StorageStores PT or EN to show your chosen language. Remains until changed or site data is cleared.
filesup.analytics-consent.v1Local StorageStores whether you allowed or rejected Google Analytics and the choice date. Remains until you change it or clear site data.
filesup.link-conversation.<id>Local StorageOn the sender's device, keeps the stable conversation URL for reuse. It may contain a bearer credential and remains until replaced or site data is cleared.
filesup.pending-link-claimSession StorageTemporarily stores a link identifier and token while you sign in and claim the conversation. Removed after the operation or when the tab/browser session ends.

4. Optional Google Analytics

When allowed, Google Analytics may receive the visited page, date and time, referrer, approximate location derived from IP, browser, device, screen resolution and measurement identifiers. FilesUp removes URL query parameters and fragments before sending the page location and does not configure the transmission of content, contacts, file names, messages, account identifiers or link tokens.

The provider is Google Ireland Limited and Google affiliates. Processing may involve transfers outside the European Economic Area under the mechanisms and safeguards stated by Google. We disable advertising-personalisation signals and Google Signals in this implementation.

TechnologyPurposeDuration
Google Analytics 4 (G-1DXZ1SYG3R)Measures page views and aggregate access patterns to understand and improve the website and app.Loaded only while the saved choice is “allowed”.
_gaDistinguishes browsers to produce usage statistics.Up to 2 years, subject to browser limits or earlier deletion.
_ga_<container-id>Persists measurement session state.Up to 2 years, subject to browser limits or earlier deletion.

5. Cache Storage and service worker

The app uses browser Cache Storage through a service worker to store the app shell, manifests, logos and other static resources needed for fast loading and basic offline operation. Old cache versions are removed when the service worker updates.

API requests are excluded from this cache. Shared-file binaries are not deliberately stored by the service worker, although the browser or operating system may manage its own cache and downloads outside FilesUp's direct control.

6. How to manage these technologies

Use “Cookie preferences” in the website footer or app to allow or reject analytics. Because Local Storage is scoped by origin, filesup.app and drop.filesup.app keep separate choices and may each ask once.

You can also clear cookies and site data in browser settings and sign out of FilesUp. Blocking cookies, Local Storage, Session Storage or service workers may prevent sign-in, opening links, claiming a conversation, remembering language or offline operation.

Clearing local data does not necessarily delete account data on our servers. For that request, see the Privacy Policy or contact privacy@filesup.app.

7. Contact and changes

Questions about these technologies can be sent to privacy@filesup.app. Material measurement or marketing changes will appear here and be accompanied by the legally required choice mechanism.

FilesUp

Files, sent like a message.

How it worksTrustAppsSend large files onlineShare files online securelyFilesUp vs WeTransfer, SwissTransfer, Smash and TransferNow | ComparisonContact
TermsPrivacyCookiesAcceptable useDelete accountReport

© 2026 FilesUp. Made in Portugal for sharing without complications.

Help us improve FilesUp

With your permission, we use Google Analytics to understand visits and usage. We do not send content, contacts or link tokens. Learn more