Cookie Notice
Staging draft · pending legal review · Version 1
1. What this Notice covers
This Notice explains how Klinora uses cookies and similar technologies on its public website and workspaces.
A cookie or similar technology may store information on, or gain access to information from, a browser or device.
2. Categories
Strictly necessary
These support sign in, security, session continuity, booking, payment, consent choices and other core functions.
They may be used without optional consent only where a current legal exception genuinely applies.
Preferences
These remember choices requested by the user.
Where a preference technology is not strictly necessary for a requested service, Klinora will obtain the required consent.
Analytics
These help Klinora understand how people use the website and improve performance.
Optional analytics must remain off until the required consent is given, unless a documented current exception applies.
Marketing
These support advertising, campaign measurement or cross service tracking.
Marketing technologies must remain off until the required consent is given.
3. Your choices
The consent interface must offer clear choices:
- Accept optional technologies.
- Reject optional technologies.
- Manage preferences.
You can change your choice later through Cookie settings in the footer.
Withdrawing consent should be as easy as giving it.
4. Current cookie and storage register
The final register must be generated from an actual scan of the production code and configured providers.
Do not publish an invented list.
The register must show:
- Name.
- Provider.
- Purpose.
- Category.
- First party or third party status.
- Duration.
- Legal basis or exception.
Current production register: Pending confirmation: codex to generate after actual cookie and storage audit
5. Third party services
The final register must identify relevant technologies used by configured authentication, payment, analytics, marketing, support and media providers.
A provider that is not active must not be listed as active.
6. Browser settings
Browser controls may also block or delete cookies.
Blocking necessary storage may prevent sign in, booking, payment or preferences from working.
7. Contact and updates
Questions: Pending confirmation: privacy contact email.
Klinora will update this Notice when the use or purpose of device technologies changes.
Current first-party browser storage inventory
Verified from the staging code. A live third-party provider scan is still required before this Notice can be published as final.
| Name or pattern | Purpose | Category | Duration |
|---|---|---|---|
| cleanly.customer.token | Customer sign-in session | Essential | Until sign-out or browser data cleared; token expires server-side |
| cleanly.provider.token | Klinora Pro sign-in session | Essential | Until sign-out or browser data cleared; token expires server-side |
| cleanly.admin.token | Admin sign-in session | Essential | Until sign-out or browser data cleared; token expires server-side |
| klinora.cookie.preferences.v1 | Remember optional storage choices | Essential | Until changed or browser data cleared |
| klinora.provider.acknowledged-booking-update | Remember a Pro booking update already seen | Essential service state | Until updated or browser data cleared |
| klinora.booking.journey | Resume an in-progress booking in this tab | Essential | Until tab closes or journey cleared |
| klinora-payment-consent:* | Carry payment-method consent across secure return | Essential | Until tab closes or payment setup completes |
| klinora.customer.message.* | Unsent message draft in this tab | Requested service feature | Until tab closes or message sent |
Google sign-in and Stripe payment components load only in their relevant journeys. Any storage they set must be confirmed in the live provider audit; no analytics or marketing script was found in the current first-party code scan.