Cookie and Storage Notice

Version and effective date: September 15, 2026

Separalo uses browser storage to operate the service. Authentication cookies/tokens maintain sessions and security. The exact authentication cookie names and lifetime depend on secure hosting and session configuration; some authentication state may also use browser storage.

separalo_locale stores your language preference for up to one year. Older visits may have legal_locale. The c15t cookie and local storage entry remember your privacy choice for up to one year. Older cookie_notice, cookie_consent and marketing_consent values are no longer read and expire on their own. Interface preferences and temporary booking-management state may use local or session storage.

We use self-hosted Umami for cookieless site analytics and Sentry for diagnostics. Umami measures public marketing/legal page visits and predefined signup, setup, booking-step, sharing and subscription-checkout events. Custom event properties use limited categories rather than form contents. We retain browser-provided referrer URLs and URL query parameters, with access-token fields, URL credentials and fragments excluded, to measure traffic sources and campaigns. These URLs may include identifiers or other information present in their paths and parameters. Page URL fragments are excluded. Private event paths are replaced with generic paths. Internal business retention and billing reports remain in our application backend. Cookieless does not mean no information is processed; see the Privacy Policy. We do not use session replay. Advertising measurement with Meta is optional and described below.

You can clear or restrict storage through your browser. Blocking authentication storage can prevent sign-in or other essential functions. Contact [email protected] about privacy choices. You can change your choice at any time through “Do Not Sell or Share My Personal Information” in the site footer or on this page.

Optional advertising measurement

We use your approximate country and region, supplied by our network provider with each request, to apply the choice your location requires. We do not store that location. Where the law requires prior consent (for example, in the European Economic Area, the United Kingdom, Switzerland and Quebec), we ask first and nothing below happens until you accept. Elsewhere, advertising measurement may be active by default and you can opt out at any time. A Global Privacy Control signal is treated as an opt-out in those regions, including over an earlier acceptance.

When measurement is allowed, we load the Meta pixel on our public pages and on the sign-up and sign-in pages to measure visits and successful contact-form submissions. It does not send events from the dashboard, booking or account pages. Conversions API also measures verified registrations, trial starts and first membership payments. Meta may receive page and browser information, advertising identifiers, and the registration email and account identifier transformed using SHA-256 (hashing, not anonymization) for ad attribution, optimization and audiences. We do not send contact-form fields, card details or customer booking information. Meta may use cookies such as _fbp and _fbc; when you arrive from a Meta ad, we may store its click identifier in _fbc for up to 90 days.

A new business account keeps these browser identifiers for up to 180 days to connect the ad click to later milestones. Opting out while signed in, or signing in after opting out on that browser, deletes them and records the opt-out on your account, so a default on another device does not resume measurement; only an explicit acceptance does. We retain milestone status without email or browser identifiers to prevent duplicates until account deletion. Opting out stops new events; it does not delete previously transmitted data or necessarily remove existing cookies, which you can clear in your browser. See also Meta’s Privacy Policy.