Cookie and similar-technology notice
A data-minimised inventory and consent boundary for website and application storage.
Draft v0.2 · implemented necessary-cookie inventory; deployment read-back pending
Strictly necessary technology
The public website does not require a cookie. The authenticated application uses only security, session, active-organisation and invitation-handoff storage needed for the requested secure function. Staff access uses Google IAP's authentication state. These items are not used to build an advertising profile and cannot be disabled while retaining the related authenticated function.
Optional technology
Analytics, replay, advertising or cross-site technologies remain disabled until the operator records the provider, purpose, information, duration, country, lawful ground and consent/opt-out implementation. A consent-dependent item loads only after the user chooses it, and withdrawal is as easy as consent.
Production inventory
| Name/category | Purpose and duration | Launch state |
|---|---|---|
| Supabase SSR auth cookie(s) (provider-generated sb-… name) | Customer login, refresh and MFA assurance; bounded by the 12-hour absolute and 30-minute inactivity session policy | Necessary; dedicated production project pending |
| cc_active_organisation | HTTP-only, Secure in HTTPS and SameSite=Lax active-tenant selector; browser session | Necessary; implemented |
| cc_accountant_invitation_claim | HTTP-only, Secure in HTTPS and SameSite=Lax invitation handoff; maximum seven days and removed after use | Necessary; implemented |
| Google IAP authentication state | Staff-only ops authentication; Google-controlled name and session duration | Necessary for ops; production IAP pending |
| Analytics | Product/public-site measurement | Disabled; no analytics cookie or SDK |
| Replay/advertising | Behavioural analysis or campaigns | Disabled; no replay or advertising cookie/SDK |
Controls and changes
Local/test-only fixture cookies are not production technologies and production configuration rejects fixture authentication. Browser controls may remove session storage but can affect secure features. No consent banner is used merely for necessary cookies. Before any optional analytics, replay or advertising technology is activated, ChainClose will publish the exact provider/name/purpose/country/duration, implement prior consent and easy withdrawal, and test that refusal leaves the public and core authenticated service usable.