Cookies and browser storage
Finchoq sets no cookies. What it does keep in your browser, why, and how to remove it.
Last updated 12 August 2026
We do not use cookies
Not a technicality — the application never writes to document.cookie. There is no analytics script, no tag manager, no advertising pixel and no third-party embed on any public page, so there is nothing to consent to and no banner asking you to.
If that changes — if we ever add analytics — this page changes first, and you will be asked before anything is set.
What we do store
Signing in keeps a session in your browser's local storage. Unlike a cookie it is never attached to a request automatically and is never sent to another site; the app reads it to know you are signed in and to attach your token to the requests you make.
auth-storageSign-in sessionEssentialNot storedKeeps you signed in between visits. Holds your access token, your account name and email, and your role. Cleared when you sign out.
userLegacy session (older accounts)Not storedThe key an earlier version of the app used. Nothing writes to it any more; it is read once and removed when it is found to be stale.
Clearing it
Signing out removes the session. You can also clear it directly here, which signs you out on this device and leaves nothing behind. It does not delete your account or anything stored on our servers — for that, see the privacy notice.
Third parties
Two services can set cookies of their own, and only when you choose to involve them. Signing in with Google, or connecting Google Calendar as a mentor, happens on Google's own pages under Google's terms. Avatars and images are served from Cloudinary, which is a plain image request and sets nothing on our behalf.
Do Not Track
Respected by default, in the sense that there is nothing to switch off. We do not track visitors across sites, build advertising profiles, or share browsing behaviour with anyone.