No hidden tracking.

Sada Files primarily uses local browser storage rather than advertising cookies. We use the word “cookies” here broadly so the policy also covers localStorage and similar device storage.

sadafiles:privacy-preferences:v1 records your analytics choice and timestamp. Theme and language preferences make the interface consistent. Device history keeps job names and status on your device. Developer sign-in state is needed to manage API keys.

This storage supports features you request and cannot be disabled inside the site. You can remove it using your browser controls; doing so resets those features.

The public counter records page loads and navigation. Without analytics consent, it stores only an aggregate count and a random event ID for retry deduplication. This event ID expires after 90 days and is not a persistent browser identity. No page path, device details, referrer, location, or raw network address is included.

With analytics consent, sadafiles:visitor:v1 holds a random first-party visitor token for up to one year. sadafiles:visit-session:v1 in session storage identifies a visit, renewing after 30 minutes of inactivity. The server stores hashes of these tokens, page paths without queries, referrer host, language, browser, operating system and screen size. A heartbeat every 45 seconds while the page is visible updates online presence; it does not add a page view. Optional browser-permitted location is rounded to two decimal places. Sessions and page events expire after 90 days, and inactive profiles after one year. sadafiles:visitor-stats:v2 caches public totals, not your identity.

We do not load advertising pixels, cross-site tracking scripts, or social-media tracking cookies. Links to third-party sites are governed by those sites after you choose to open them.

Use Privacy choices in the footer at any time. Necessary only stops optional tracking, clears the browser visitor/session tokens and requests deletion of the associated profile, sessions and page events. If offline, sadafiles:visitor-withdrawal:v1 temporarily queues the token until the server confirms deletion. Anonymous aggregate totals remain.