Cookies and device storage
Updated 15 November 2026. This page describes the storage entries and cookies FiloFocus uses. Cookies and localStorage are distinct tools: the latter is browser storage, not a cookie.
Controller: Marcello Guida, sole proprietorship, via Cappella 4c, 81021 Arienzo (Italy), VAT no. (P.IVA) 04970390615 · mguida2604@gmail.com.
App local storage
- filo-space-v1 — localStorage
- Activities and completion status, free-text thoughts, selected activity, timer and durations, preferences and history. No automatic expiry set by the code; history is capped at 500 sessions and the screen shows at most 30.
- filo-storage-notice-v1 — localStorage
- Remembers dismissal of the local-data notice. It is not consent to analytics, advertising or profiling. No automatic expiry.
- filo-sync-baseline-v1 — localStorage
- After a successful sync it may keep the account ID and the comparison baseline of activities and thoughts, for the next merge. No automatic expiry.
The three entries stay in the browser profile until changed, removed or deleted by the browser. Data is separate per domain and profile.
Functional and session cookies
filo-language: when you choose IT or EN, the server sets this cookie (value it/en) for 180 days, with Path=/, HttpOnly, SameSite=Lax and Secure over HTTPS. It remembers the language and holds no activities, thoughts or advertising identifiers.
Account session: if you sign in, the Better Auth authentication system sets a session cookie (named better-auth.session_token, with a __Secure- prefix over HTTPS) to keep you signed in; on HTTPS sites the project enables the Secure attribute. The default session lifetime is 7 days, renewed with use. Without an account no session cookie is set.
These cookies are technical, needed to provide the function you request (language, sign-in). The code sets no analytics, advertising or profiling cookies and asks for no consent for them. The Italian Garante’s Guidelines distinguish technical cookies from tracking ones: text and FAQ.
Hosting, email and Stripe
Pages and APIs go through Cloudflare, which may use technical security tools on the domain: see the Cloudflare cookies documentation. Filo’s code loads no Stripe scripts or analytics tools: for checkout and subscription management you are redirected to a Stripe domain, which may use its own cookies under its privacy notice. Verification, reset and withdrawal-confirmation emails, sent through Cloudflare Email Sending, are not cookies.
The list above reflects what the code and the providers’ documentation show; it is not the result of a production cookie scan.
Deletion and choice
“Manage data” deletes the app’s local content and the sync baseline, but not the notice or the language cookie, and does not delete the account or the remote copy. To remove those too, clear the site’s data in your browser settings; you may need to pick the language again and see the notice again. Signing out removes the session cookie. For server data see the privacy notice.