Storage needed for the app
FitArchive uses IndexedDB for your log and local storage for preferences such as appearance and the active account. An installed app caches its files for offline use. Google/Firebase sign-in uses browser authentication storage when you choose to sign in. These support the features you request and are separate from optional analytics.
Analytics preferences
The local-storage key fitarchive:traffic-consent:v2 remembers your Google Analytics choice for public-page and private-app visits. This expanded choice defaults off even if you allowed public-page tracking before; allowing it can set Google analytics cookies. The key fitarchive:analytics-consent:v1 remembers your separate choice for optional private-app feature events. This also defaults off and is not restored from account sync or imported backups. If feature events are enabled and configured, a random session ID is stored for the tab and expires after 30 minutes of inactivity or when that tab session ends. Turning feature analytics off clears that identifier. Cloudflare public traffic measurement is separate and does not use analytics cookies.
Managing browser data
You can clear website data and control cookies in your browser. This can reset preferences, sign you out or permanently remove records stored only on this device. Export anything you want to keep first. Browser storage controls are separate from deleting data already held on a server or in an exported file.