Cookies and Tracking
Draft under review by counsel. This document is published for transparency while it is finalized and is not yet in force. The version that governs will say so plainly, with its effective date.
What we use
Strictly necessary technologies only: the authentication and session cookies that keep you signed in and carry your authorization token, anti-forgery protection, and the minimum local storage the application needs to work, such as a remembered preference. Sign-in and session management run on Supabase authentication. That is the current inventory.
What we do not use
No advertising cookies, no cross-site trackers, no advertising pixels inside the signed-in application, and no sale of browsing data.
Operational logs
Limited application, server, security and performance logs are generated to diagnose errors, measure latency, keep the service available and secure, and improve internal processing queues. They are not advertising data.
If analytics is ever added
It will be listed here first, with what it collects, and any consent mechanism the law requires will be in place before it runs.
Your browser
You can restrict cookies in your browser settings. Blocking the strictly necessary ones will prevent sign-in and core functions from working.
To be completed with counsel
Consent mechanics where required by applicable law, and the formal cookie table.