Privacy notice
Updated 15 November 2026. This notice describes how FiloFocus processes personal data for the local timer, the account, sync and the Premium subscription.
Data controller: Marcello Guida, sole proprietorship, via Cappella 4c, 81021 Arienzo (Italy), VAT number (partita IVA) 04970390615. Contact for privacy and requests: mguida2604@gmail.com.
Data processed and where it is stored
Local use, no account. In the browser, the filo-space-v1 localStorage entry contains activities (title and status), free-text thoughts, selected activity, timer state and durations, preferences and history (at most 500 sessions; the interface shows the latest 30). The filo-storage-notice-v1 and filo-sync-baseline-v1 entries remember dismissal of the notice and the local baseline of the last sync, including user ID, activities and thoughts. This data stays on your device and is not sent to us, except through the sync described below. Filo does not require a diagnosis: avoid entering sensitive data or unnecessary information about other people.
Account. To register and sign in we process your name, email and a password credential (stored as a hash by the Better Auth authentication system), plus the email verification status. For sessions we store a session token, expiry, creation and update times, IP address and user-agent. For security and request limiting we store request counters associated with the IP address. This data is kept in the Cloudflare D1 database, configured with EU jurisdiction.
Sync. Sync is optional and not automatic: after you sign in, a preview screen merges local and remote activities and thoughts, and sending requires your confirmation. On the server we keep, for each account, a snapshot of activities (title and completion status) and thoughts (text) with a revision number. Timer, history and preferences are not synced.
Premium subscription. When you buy Premium we redirect you to Stripe Checkout: card and billing details are entered on Stripe-hosted pages, not in Filo fields. The Stripe customer is created when you start a Premium purchase or open the subscription management portal, not at registration. We send Stripe your email and a Filo identifier; we store the Stripe customer ID, the Premium status, technical checkout data and the IDs of the Stripe events received. We do not store your card number. If you exercise the right of withdrawal, we keep a technical record (subscription, payment and refund identifiers, amount, status and dates) and send you a confirmation email.
Technical data and communications. Requests to the site and API go through Cloudflare, which may process technical data such as IP, user-agent, URL and time. The Worker logs only a fixed event, stage and error category, without request contents. If you write to mguida2604@gmail.com we process the content of your email to reply.
Purposes and legal bases
We process data for these purposes and on these legal bases (Art. 6(1) GDPR): (a) creating and managing the account, authenticating you and providing the sync you request: performance of the service contract, point (b); (b) selling and managing the Premium subscription, recognising the plan and handling payment, cancellation, withdrawal and refunds: performance of the contract, point (b); (c) keeping records and meeting the controller’s tax and accounting obligations: legal obligation, point (c); (d) service security, abuse prevention, request limiting and defence of legal claims: the controller’s legitimate interest, point (f); (e) replying to your emails: performance of a contract or pre-contractual steps you request, or legitimate interest in replying. Local processing in the browser stays on your device.
Providing name, email and password is necessary to create an account; providing payment details to Stripe is necessary to buy Premium. Without them you can keep using the timer locally. We do not profile you or take automated decisions with legal effects, and the code includes no analytics, advertising or artificial-intelligence services.
Recipients and providers
Cloudflare provides hosting, code execution (Workers), the D1 database and transactional email sending (Cloudflare Email Sending, for verification and password-reset messages and for the withdrawal confirmation). In its data processing agreement Cloudflare states that it acts as a processor for customer data.
Stripe handles checkout, payments, the customer portal and subscription billing. In its data processing agreement Stripe states that it acts as a processor for some activities and as an independent controller for others (for example fraud prevention and legal obligations); for the latter, Stripe’s privacy notice applies.
We do not sell your data and do not share it for advertising. We may disclose it to authorities where the law requires.
Transfers outside the European Economic Area
Cloudflare and Stripe are international groups and may process data outside the EU. In their agreements they indicate standard contractual clauses and, where applicable, the EU-U.S. Data Privacy Framework as safeguards (Cloudflare agreement, Stripe agreement). The D1 database is configured with EU jurisdiction: account and sync data are stored there. This does not rule out that other processing, such as running the Worker, technical data processed by Cloudflare or data processed by Stripe, also takes place outside the EU.
Retention
Local data: stays in the browser until you delete it (“Manage data”) or the browser removes it. Account and synced snapshot: while the account exists or until you ask for deletion. Sessions: the authentication system’s default lifetime is 7 days, renewed with use; verification and reset tokens have a short expiry. Subscription and payment records: the documents and data needed for the controller’s tax and accounting obligations are kept for the period required by law, in general until the time limits within which the tax authority may carry out assessments for the relevant tax year have expired; after that period they are deleted or anonymised, unless a dispute is pending. Stripe keeps its own data under its own notice. Cloudflare logs and backups: the configuration uses sampled application logs and no invocation logs; log retention and database restore periods depend on Cloudflare and the plan and are not set by us. Emails sent to us: for as long as needed to reply and handle any disputes.
Deletion and controls
From Manage data you can export local content as JSON (unencrypted) or delete it; this does not delete the account or server data. You can delete remote activities or thoughts by choosing to remove items present only on the server and confirming the preview. Signing out closes the session without deleting data. The interface does not offer self-service account deletion: to request it, write to mguida2604@gmail.com from the account’s address. We reply within one month of the request. The procedure is manual: the operator cancels any subscription, asks Stripe to delete the customer and deletes the account and synced data from the database; only data the operator must keep for tax and accounting obligations is retained. Cancelling the subscription in the Stripe portal is not the same as deleting the Filo account.
Your rights and contact
You may ask for access, rectification, erasure and restriction of your data, object to processing based on legitimate interest, and ask for portability where the conditions apply. Write to mguida2604@gmail.com stating “Filo privacy”; do not send passwords or tokens. You may lodge a complaint with a supervisory authority (Art. 77 GDPR); in Italy, the Garante per la protezione dei dati personali.
The service is for adults only; it does not verify users’ age. Filo does not diagnose or create clinical profiles.
Cookies and device storage · Terms of service · Back to Filo
Language
Your IT/EN choice is remembered by the functional cookie filo-language for 180 days, HttpOnly, SameSite=Lax and Secure over HTTPS. The country of access is taken from Cloudflare request metadata; no GPS is requested. See the Cookie policy.