These documents have not been reviewed by a lawyer
Cookie Policy
MeshSail uses three cookies, all of them strictly necessary. There is no advertising, no cross-site tracking, and no third-party analytics enabled by default.
Last updated 27 July 2026
| Cookie | Purpose | Type | Lifetime |
|---|---|---|---|
| sb-*-auth-token | Keeps you signed in. Set by Supabase Auth. | Essential | Until you sign out, or 30 days |
| meshsail-rail-* | Remembers whether you collapsed the sidebar and which team conversations you left expanded. Stored in localStorage, never sent to our servers. | Essential | Until cleared |
| meshsail-consent | Remembers your answer to the consent banner, so we stop asking. | Essential | 12 months |
Why there is barely a banner
Consent requirements attach to non-essential cookies — analytics, advertising, personalisation trackers. MeshSail does not use any by default, so there is nothing to consent to beyond the cookies that make signing in work. If analytics are ever enabled by the operator of this deployment, they are strictly opt-in: off unless you say yes, and your answer is recorded so we can prove it.
What we do not use
- No advertising or retargeting pixels.
- No cross-site tracking.
- No session recording or heatmaps.
- No fingerprinting.
Controlling cookies
You can clear or block cookies in your browser settings. Blocking the authentication cookie will sign you out and prevent signing back in — it is not optional in the sense that the site can function without it.
Related reading: Privacy Policy.
Note for whoever operates this deployment: if you add an analytics provider, you must add it to the table above, wire it behind the consent banner's analytics flag, and default it to off. The consent_records table already stores each answer with a policy version and timestamp for exactly this purpose.