Privacy policy

This policy describes how Gaston Media SAS (18 rue de Copenhague, 67610 La Wantzenau, France) handles data within the ConsentLift service and the consentlift.com site. Our principle: collect the strict minimum, and say for each piece of data what is kept, where, and for how long.

1. Controller and processor roles

For site and user-account data, Gaston Media SAS acts as data controller. For consent data measured on our customers' sites, Gaston Media SAS acts as a processor, under a data processing agreement. DPA: contact us at hello@consentlift.com.

2. Data measured on customer sites

The ConsentLift SDK measures consent events (banner display, acceptance, rejection, categories). Here is what it records, and what it does not:

• Two values, and only two, are written to your device, both in the tab's sessionStorage and erased when the tab closes: cl_sid, a random session identifier, and cl_buffer, a temporary store of at most 20 events that could not be transmitted, emptied as soon as they are sent. No cookie is set, no localStorage, no browser fingerprinting.
• cl_sid is tied to no person, is not reused from one visit to the next, and is never shared across sites or with a third party. Its value is sent with each event and kept on our side for 24 months (§5).
• A random technical identifier per page view, regenerated on every load and never written to the device. It is sent with the event and retained alongside it; despite its technical name (visitor_id), it cannot link two page views, two visits or two sites.
• No IP address in our measurement data: our collection code does not read it; country and region are computed at the edge by our host before the event reaches us, and of your location, only that country and region are recorded.
• Of your device, only the browser family, operating system and device type are recorded. The full user agent is read in memory just long enough to recognise a bot, then dropped: it is not retained in our measurement data.
• Our server logs: downloading the ConsentLift script (cl.js) is logged by our server, with the IP address, the full user agent and the address of the page loading the script, kept for about 15 days. This log is not linked to any consent event.
• When an event is classified as coming from a bot, we retain the reason for that classification, which may contain the name of the network operator or hosting provider it came from. That is what lets us keep automated traffic out of our customers' rates, and show them why it was excluded.
• Of the page visited, only the path and the site's domain are recorded, along with the referring site's domain name. The query string is not retained: five campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) are extracted from it when present and retained on their own, to the exclusion of any other parameter. The path is recorded as the site builds it: if it contains an identifier (an order number, for example), that identifier is recorded with it.
• No email address, no name, no data entered by the visitor
• No third-party cookies read, no browser storage accessed outside our namespace: our detectors go exclusively through the CMP's programmatic interface (window.Didomi, window.__tcfapi, window.Cookiebot…). They read neither consent cookies, nor the CMP's localStorage, nor its sessionStorage.
• The event also carries what constitutes the measurement itself: the action type (banner shown, acceptance, rejection, categories chosen), the detected CMP, the time to decision and a timestamp.

3. Site and account data

On consentlift.com we measure the audience with PostHog, on its European instance (in Frankfurt, Germany, according to PostHog). On the public site, PostHog receives page views, page leaves and clicks, with no session recording, and writes nothing to your device: no cookie, no localStorage, no sessionStorage (measured on 13 October 2026). It collects nothing if your browser sends the "Do Not Track" signal.

In the signed-in dashboard, PostHog writes nothing to your device either, and we send it, for usage measurement, the identity of the signed-in user: account identifier, email address, role, organization identifier and name, and administrator status.

For dashboard accounts, we process strictly necessary information (email, organization, role) via our authentication provider, Auth0 (§4).

4. Providers and processing locations

For each category of data, the provider that processes it and where, as recorded on 13 October 2026. Where we could not establish a location, we say so.

• Consent events — storage: Tinybird, Google Cloud region europe-west2, in London (United Kingdom). Transfer basis: the European Commission's adequacy decision for the United Kingdom, Implementing Decision (EU) 2021/1772, amended and extended by Implementing Decision (EU) 2025/2574 of 19 December 2025, applicable until 27 December 2031.
• Consent events — reception: Cloudflare (Workers), on the node closest to the visitor — therefore outside the European Union for a visitor located outside the Union. The event is processed there in memory, without being stored there, then forwarded to storage.
• Application, site and configuration database (organizations, domains, accounts, alerts): a Hetzner Online GmbH server in Nuremberg (Germany).
• Configuration database backups: Cloudflare R2, under European Union jurisdiction, daily, kept for 30 days.
• Account authentication (email, sign-in identity): Auth0, United States region. Transfer basis: the provider's contractual safeguards, to be confirmed.
• Site and dashboard audience measurement: PostHog, European instance, in Frankfurt (Germany) according to PostHog — see §3.
• Error tracking for the site and the dashboard: Sentry, "DE" data region, in Frankfurt (Germany) according to Sentry. Sentry receives a report only when an error occurs. From your browser: the error message and stack, the page address (query parameters included), the browser (user agent), language and time zone, and a log of the page's latest technical events (network requests, clicks, navigation, console messages), and the site's content security policy reports (page address, blocked resource, browser). Our Sentry organisation prevents the storage of IP addresses and applies its default data scrubbers; nothing is written to your device. From our server, for a server error: the request address and headers, without cookies or IP address, and the account identifier and email address of the signed-in user, their organisation identifier and their role. Errors are kept for 30 days (free "Developer" plan, according to Sentry). Recorded on 21 October 2026.
• Alert emails and reports (recipient address, message content): Resend. Location: not established as of this record.
• Demo booking (name, email, time slot): Cal.com. Location: not established as of this record.
• Contact mailbox (hello@consentlift.com): OVH. Location: not established as of this record.
• Slack alerts: only if the customer configures a webhook; Slack is then the destination the customer chose.
• Google BigQuery: only as part of a consulting engagement, on the customer's own Google account.

5. Retention

Consent events are kept for 24 months, then deleted automatically; so is the daily count per session, which carries the session identifier. Daily aggregates, which carry neither a session identifier nor a page-view identifier, are kept with no time limit. Events from the former Page views and Sessions modules, removed from the product and which have received nothing since 22 September 2026, are kept for 12 months, then deleted automatically. Our server logs are kept for about 15 days. Account data is kept for the duration of the contractual relationship; the dashboard security log, which records the IP address of signed-in users for certain actions, has no time limit at this date.

6. Your rights

Under the GDPR, you have rights of access, rectification, erasure, objection and portability. The identifiers we keep about visitors are random, and none of our tables links them to a name, an email address or an IP address. To exercise your rights, over this data or your account data, write to us at hello@consentlift.com.

7. Changes

This policy may evolve. The last-updated date is shown at the top of the page.