Legal navigation

Terms & use

Privacy & data

Content & AI

Cookie Policy

Last updated: October 21, 2026

This policy explains how Zliding uses cookies and similar browser storage, including local and session storage. It applies to zliding.com and the Zliding app.

1. Essential cookies and storage

These items are necessary for the service to work securely. They do not enable advertising or retargeting, and cannot be switched off from our cookie preferences.

  • Consent choice. zliding_cookie_consent is a signed, HttpOnly, first-party cookie that records a guest’s consent choice and the applicable policy version. It lasts up to one year and lets us honor that choice before the user signs in. Once you are signed in, your consent decision and its history are stored server-side against your account rather than only in this cookie.
  • Authentication. Clerk, our authentication provider, sets __session (the signed-in session token) and __client_uat (tracks when your session last changed, so every open tab stays in sync) to keep you signed in securely.
  • Theme preference. zliding-landing-theme is local storage on our website and app that records, only if you use the light/dark switch, whether you chose the light or the dark theme. It stays on your device until you clear your browser data, and is never sent to us.
  • Display currency. display_currency is a first-party cookie that holds only a currency code (for example eur), picked from the approximate country of your connection so our prices appear in your local currency. It does not contain your country, your IP address or any identifier, is readable by our page scripts, and lasts up to 30 days.

2. Optional browser telemetry

We enable PostHog only after you accept optional cookies and browser telemetry. It helps us understand how the product is used.

Analytics

  • PostHog. Product analytics such as page views, feature usage, and interactions. PostHog can use cookies or local storage, typically with names beginning ph_.

3. Reliability monitoring

Sentry processes browser and server error reports and performance traces to detect, diagnose and resolve errors and to keep the Service secure and reliable. This is legitimate-interest processing and does not depend on the optional analytics choice or on Global Privacy Control. Session Replay is not recorded continuously: its normal sampling rate is 0%, and it records at a 100% rate only after an error. Replay masks all text and form inputs and blocks media, so it shows the structure of the page rather than its content. The Privacy Policy describes this processing, its safeguards and the right to object.

4. Your choices and Global Privacy Control

You can accept or reject PostHog analytics in the consent banner. You can change that choice at any time from the cookie preferences control in the marketing footer, or, when signed in, from Account > Preferences. Withdrawing consent stops future PostHog analytics on that browser; it does not undo processing that took place before the withdrawal.

When Zliding receives a Sec-GPC: 1 Global Privacy Control signal from a device, we actively treat it as a device-level opt-out: PostHog analytics remains blocked on that device even if your saved choice is “accepted.” We still show and save your consent choice. If you later remove the GPC signal, an accepted choice can take effect again on that device.

Your browser also lets you block or delete cookies. Blocking essential cookies can prevent sign-in or saved interface preferences from working as intended.

5. Third parties and contact

PostHog processes optional analytics data and Sentry processes reliability-monitoring data on our behalf. We do not use advertising, retargeting, or data-broker cookies, and we do not sell data collected through cookies. If our use of cookies changes, we will update this page. Questions: .

When you open a booking option by clicking or pressing it (the Enterprise contact option on our pricing section, or the call offer in the app), we load Calendly’s scheduling widget from calendly.com; pointing at that option or moving to it with the keyboard only loads Calendly’s script. Calendly is an independent controller: inside the widget it may set its own cookies and similar storage, for example to keep your booking session working and to protect against bots, and, with your permission, cookies for preferences and analytics. Calendly asks for that permission with its own cookie choices, separate from ours. Depending on its settings, your browser may block or isolate these cookies. Calendly’s Privacy Notice explains how it uses them.