Cookie Policy
This policy describes the first-party cookies, localStorage and sessionStorage used by Clinilo during ordinary-data-only Managed Launch. Optional storage remains controlled by the booking consent centre.
- Status
- Published
- Version
- managed-launch-cookie-2026-08-17
- Effective date
- 2026-08-17
1. Scope, controller and consent centre
Clinilo FZE LLC is responsible for storage set through Clinilo pages; contact casper@swprlabs.com. The appointed EU representative is identified in section 1 of the Platform Terms. A clinic is responsible for technology it independently places around an embedded Clinilo flow.
The consent centre separates preferences and statistics, offers reject optional and save choices, and can be reopened to change or withdraw a choice. Core booking remains available after rejection. Withdrawal stops the optional use and clears the matching browser value. Strictly necessary credentials and the record remembering rejection or acceptance are used to provide security, a requested secure function and respect for the choice.
2. Staff authentication and reset cookies
| Name | Purpose and maximum |
|---|---|
| __Secure-better-auth.session_token | HttpOnly Secure staff-session credential; configured maximum seven days; cleared or invalidated on sign-out or revocation. |
| __Secure-better-auth.admin_session | Preserves the administrator’s signed session during controlled impersonation; browser maximum up to seven days, impersonated server session no more than one hour, cleared when impersonation stops. |
| __Host-clinilo_reset_token | Random password-reset credential for no more than one hour; cleared when consumed or rejected. |
These values contain credentials rather than clinic or clinical text. Blocking them prevents the corresponding secure account function.
3. Booking-management and private-calendar cookies
| Name | Purpose and maximum |
|---|---|
| __Host-clinilo_manage_{bookingId} | Random bearer credential for one booking-management page, up to 30 days. |
| __Host-clinilo_calendar_{calendarId} | Random bearer credential for one private calendar, up to 30 days. |
| __Secure-clinilo_manage_handoff_{bookingId} | Transfers a booking credential from the apex domain to the clinic host for at most 120 seconds and clears on redemption. |
These HttpOnly Secure first-party credentials do not contain appointment, service or health text, but possession can authorize the protected page. Policy ordinary-data-only-2026-08-16 prohibits health and other special-category content throughout the linked page.
4. Language and consent-choice storage
After an active English or Danish choice, the first-party clinilo-locale cookie stores only that language for up to one year. Necessary localStorage key clinilo:privacy-consent:v1 stores a random consent ID, notice version, locale, preferences/statistics choices and save time. It has no automatic expiry and remains until the person changes the choice, clears site data, or a notice-version or integrity check invalidates it.
5. Optional remembered details and statistics
With preferences consent and a separate unchecked remember-details choice, localStorage key clinilo:guest:v1 stores first name, last name, email and phone with consent ID, notice version and expiry. It expires after 30 days and is removed on expiry, withdrawal, notice mismatch or manual clearing. It must not contain health or other special-category data.
With statistics consent, sessionStorage key clinilo:funnel:v1 stores a random session UUID for the browser tab/session. It is removed when consent is withdrawn or the consent identity changes. The flow sends fixed step, screen, source, duration and error labels linked to consent/session IDs, discards service, practitioner and calendar identifiers, and prunes server funnel rows after 90 days. Statistics are not required for booking.
6. Technologies not active and changes
Managed Launch does not use third-party analytics or advertising storage, PostHog, online-payment cookies or card-storage technology. Public bookings are pay at clinic. A new optional purpose, third-party technology or material duration change requires an updated policy and prior granular consent where required. Browser settings can remove site data, but removing a necessary credential may sign the person out or disable a secure link.