Cookie Notice
Draft notice for the Chronix Health foundation build.
Draft for review
This page is a draft information notice for review. It is not a final cookie policy. Before any pilot or live deployment that adds analytics, advertising, or other consent-managed tracking, Chronix should obtain legal/privacy review and replace this notice with a reviewed version aligned with the chosen consent approach.
What this notice covers
The Chronix Health foundation build is intentionally minimal in its use of browser storage. This notice describes the current foundation only and is not a final policy.
No tracking pixels or analytics vendors
The current build does not add tracking pixels, advertising cookies, or third-party analytics vendors. There is no Google Analytics, no marketing tag manager, no Segment, no Hotjar, no session-replay tool, and no consent-management platform in this build.
Cookies and storage we may use
Cookies, local storage, and session storage may be used for essential, operational reasons such as:
- authentication and session continuity (so signed-in users stay signed in across page loads)
- security (for example, anti-forgery tokens and session-fingerprinting where supported by Supabase)
- user preferences inside the staff, patient, and carer portals (language, timezone, units)
- basic app operation (route state, last-viewed surface)
No advertising cookies
No advertising cookies are added in this build. Future advertising or remarketing use would require a reviewed consent approach and is not in scope of the foundation build.
No analytics vendor in this build
No external analytics vendor is added in this build. Future analytics use would require a documented consent approach (for example, opt-in cookies, anonymous aggregate metrics only, or a reviewed consent-management platform) and is not in scope of the foundation build.
Future cookie or analytics use
If analytics, advertising, or other consent-managed tracking is added in a future release, Chronix should:
- obtain legal and privacy review of the chosen approach
- publish an updated cookie notice that names the vendors
- provide a documented consent mechanism aligned with that approach
- update this page to reflect the reviewed policy
