1. What we use today
The reviewed application code sets one first-party functional cookie, sidebar_state. It stores whether the interface sidebar is open, applies to the site path and has a maximum age of seven days. It is used only to remember an interface preference.
The app also uses browser local storage, which is not a cookie. Supabase authentication is configured to persist a session in local storage. The application may also store a language preference and local drafts or interface state. Clearing browser storage may sign you out or remove an unsynchronised local draft.
2. Necessary storage
Necessary cookies and local storage are used to provide requested functions such as authentication, session continuity, security and remembering a preference. You can block or delete them in your browser, but some parts of the Service may no longer work correctly.
3. Payments and third parties
If you open a Stripe-hosted checkout or billing portal, Stripe may set or read its own cookies and similar technologies under Stripe's own notices. Those pages are not controlled by this site. Do not enter payment details until the live checkout has been reviewed and enabled by the owner.
4. Analytics and advertising
No analytics, advertising-pixel or cross-site tracking cookie is represented in this notice as active. If a non-essential technology is added, it must not be set until the required consent is collected, and this notice must state its provider, purpose, duration and how consent can be withdrawn.
5. Managing storage
You can manage cookies and local storage in browser settings. To request help with account data rather than device storage, use the privacy contact when it is published. The Privacy Notice explains how personal data is handled beyond device storage.