Cookie Notice
Effective 7 October 2026 · Version 1
This Notice explains browser storage used by Klinora's website and account areas.
Essential storage
We use browser storage to support sign in, account security, booking progress, unsent messages and saved cookie choices. Some information is removed when you close the browser tab or complete an action. Other information remains until you sign out, change your settings or clear your browser data, depending on its purpose.
When you use Google sign in or Stripe’s payment and payout services, their components may use cookies or similar technologies for authentication, fraud prevention and payment security.
Optional technologies that require consent remain disabled until you agree. You can change your choices through Cookie settings. Blocking essential storage may prevent some account, booking or payment features from working.
Current Klinora browser storage
The following first-party keys were verified in the customer, Pro and Admin application code on 7 October 2026. A key appears only when you use the relevant feature. The name “cleanly” is a legacy technical key, not another service.
| Name or pattern | Purpose | Storage and usual end point |
|---|---|---|
cleanly.customer.token, cleanly.provider.token, cleanly.admin.token | Keep the relevant account signed in | Local storage; removed at sign out or when browser data is cleared. The access token also expires server-side. |
klinora.cookie.preferences.v1 | Remember your optional storage choices | Local storage; until changed or browser data is cleared. |
klinora.provider.acknowledged-booking-update | Avoid repeating a Pro booking update already acknowledged | Local storage; until updated or browser data is cleared. |
klinora.booking.journey | Resume an unfinished customer booking | Session storage; until the tab closes or the booking journey is cleared. |
klinora-payment-consent:* | Carry payment-method consent across a secure return | Session storage; until the tab closes or payment setup completes. |
klinora.customer.message.* | Preserve an unsent customer message in this tab | Session storage; until the tab closes or the message is sent. |
klinora.pro.guided-setup-step:* | Resume the current Pro setup step | Session storage; until the tab closes or setup state is cleared. |
Optional choices
You can accept, reject or manage optional preferences, analytics and marketing storage through Cookie settings. Rejecting optional choices does not prevent core service access. The site will not activate optional analytics or marketing technologies merely because the controls exist. You can change your choice later in the footer.
Providers in specific journeys
Google sign-in and Stripe's secure payment or payout components load when you use those features. A provider's own notice may explain additional storage under that provider's control.
In a fresh staging browser check on 7 October 2026, the customer and Pro sign-in pages each set Google's g_state cookie on their respective Klinora domain, with an expiry approximately six months later. Google's sign-in component may use further storage depending on the sign-in flow. Stripe identifies security and fraud-prevention cookies including __stripe_mid (typically one year), __stripe_sid (typically 30 minutes) and m (typically two years); these are possible in relevant Stripe journeys, not a claim that each was observed on every Klinora page. Google and Stripe control their own component storage and may change it. No optional analytics or marketing script was found in the first-party application code during this review.
Browser controls can remove storage, but blocking essential storage may prevent sign-in or payment. Questions: [email protected].
Current first-party browser storage inventory
Verified from the first-party application code. The separate provider entries remain under review for the production sign-in and payment journeys.
| 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. This first-party table does not describe their own device storage; no optional analytics or marketing script was found in the first-party code.