Skip to main content

Legal

Cookie policy

This page describes which cookies Curalune uses, why they are used, and how you can manage them.

Last updated: 14 January 2026

Technical cookies keep essential site functions and preferences working correctly.

Measurement cookies, where used, serve to improve the platform without advertising profiling.

You can review consent choices and browser settings to manage cookie behavior.

1. What are cookies

Cookies are small text files that websites send to your device, such as a computer, smartphone or tablet, in order to store certain information useful for navigation or for specific features.

2. Cookies used by Curalune

On Curalune we mainly use:

  • Technical cookies, necessary for the basic functioning of the site, for example to remember that you have closed the cookie banner or to keep some navigation preferences.
  • Optional measurement cookies, which may be used to understand how the platform is used and to improve its usability, without tracking individual behaviour for advertising purposes.

4. How to manage or disable cookies

You can control and delete cookies also through your browser settings. Depending on the program you use, such as Chrome, Safari, Firefox or Edge, you will find a section dedicated to privacy and cookies.

Completely disabling technical cookies may compromise the proper functioning of Curalune and other websites.

Optional journey measurement

With consent, the journey report records language, service, visible sections, form stages, field names reached or changed, visible-page duration and broad error categories. It excludes answers, health information, names and contact details. It does not record screen sessions. Random identifiers are pseudonymous, not anonymous data.

On Studio pages, cl_journey_v1 in sessionStorage expires after 30 minutes of inactivity or when the tab closes. Events in the new report are removed after 30 days by the scheduled cleanup. cookie-consent in localStorage remembers the choice until changed or browser storage is cleared. The persistent privacy control lets you withdraw without preventing form submission.

The main site and family forms use cl_sid and cl_sid_ts in sessionStorage for visits, ending after 30 minutes of inactivity or when the tab closes. Existing consented analytics also use cl_vid in localStorage until consent is withdrawn or browser storage is cleared, and cl_utm for campaign attribution for up to 90 days. Privacy choices removes these identifiers on withdrawal. Only field names are measured, never their contents.