Cookie & Tracking Compliance

Cookie policy, tracking technologies and consent mechanisms.

Last updated: 15 November 2026
Document revision: 2026.11-fc
CMP consent version (storage key): 2026.11 (legacy 2025.01 consents are invalidated and re-prompted)


Release status (read first)

This page describes the intended product rules for the public website CMP and on-device tracking, aligned with the repository after the R1 Meta prior-block code change.

Production caveat: as of the R2 documentation update (14 Nov 2026), R1 has been verified on local builds. Until R1 is deployed to production, the live site may still differ (historical audit showed Meta fbevents.js loading before Marketing consent). Do not treat this page as a certificate that production already matches every line below until deploy verification is completed.


Introduction

This page explains how Flowvenue uses cookies and similar tracking technologies (such as tracking pixels), used in compliance with applicable regulations, when you visit our website. Tracking pixels and tracked links in marketing emails are described in the Privacy Policy (Sec. 7-quinquies), not on this page. Server-side Conversion API events are described in the Privacy Policy and are not automatically the same as marketing cookie consent.


Data Controller

The Data Controller is:


Cookie Categories

We use the following cookie categories, aligned with our consent management platform (CMP):

1. Necessary technical cookies / storage

Essential for the website to function or to provide the requested service. They cannot be disabled via the banner.

Examples: authentication session cookies, language/theme preferences stored locally, security tokens, CMP choice (fv_consent in localStorage after the user chooses).

Legal basis: technical necessity / Art. 6(1)(b) GDPR and, where relevant, Art. 6(1)(f) for security, within ePrivacy strictly-necessary limits.

2. Preference Cookies (CMP)

We currently do not activate third-party preference cookies through this category. The category remains available for future use.

3. Statistics Cookies

We use Google Analytics 4 (GA4) to analyze how visitors use our website.

Prior-block: GA4 is loaded only after Statistics consent. Without consent, Consent Mode v2 keeps analytics storage denied and the script is not loaded.

Legal basis: Art. 6(1)(a) GDPR + ePrivacy Art. 5(3).

4. Marketing — on-device scripts and cookies

We may load, only after Marketing consent:

Prior-block: no Meta/LinkedIn/OpenAI Ads/Google Ads marketing scripts on the device before Marketing consent. Reject/revoke disables or removes scripts and clears Flowvenue first-party marketing cookies where technically possible (e.g. _fbp).

Out of scope of this CMP category: server-side Conversion API sends. Those are not declared here as always requiring Marketing cookie consent; see Privacy Policy and DPO review items.

Legal basis (on-device): Art. 6(1)(a) GDPR + ePrivacy Art. 5(3).

5. First-party site telemetry

Events to /api/telemetry and identifiers in sessionStorage/localStorage (session / attribution IDs). Not a third-party ad pixel. Legal basis may be legitimate interest, technical necessity, or consent depending on purpose — under Controller assessment (see Privacy Policy).

6. External resources (not marketing cookies)


Detailed Cookie List

Cookie Name Provider Purpose Duration Type CMP Category
_ga Google Unique visitor identifier (Client ID) 2 years First-party Statistics
_ga_G-4348WZL0BT Google GA4 property-specific identifier 2 years First-party Statistics
_gid Google Session identifier 24 hours First-party Statistics
_gat Google Request rate limiting 1 minute First-party Statistics
_fbp Meta (Facebook) Browser identifier for ads measurement 90 days First-party (often) Marketing
fr Meta (Facebook) Referrer / conversion (provider-controlled) 90 days Third-party Marketing
datr, sb, c_user Meta (Facebook) Facebook auth cookies (only if logged into Facebook) Variable Third-party Marketing
li_sugr, bcookie, lidc, liap LinkedIn Insight Tag identifiers Variable Third-party Marketing
__oppref / __obref OpenAI ChatGPT Ads attribution / browser ref Session / provider-defined First-party Marketing
_gcl_au Google Ads linker Variable First-party Marketing

Consent Management

First Visit

Revocation

Cookie settings in the footer → preference center. Revoking Statistics/Marketing disables scripts; Marketing revoke removes Meta Pixel script when present.

Document revision vs CMP version


Key Compliance Principles

Default Denied (CMP on-device trackers)

No non-essential CMP-gated tracking scripts (GA4, Meta Pixel, LinkedIn, OpenAI Ads pixel, Google Ads gtag) are loaded before the corresponding consent.

Verifiable with browser developer tools after the R1 release is live in the environment under test.

Related (documented separately): first-party /api/telemetry (session IDs under LIA; attribution IDs only after statistics/marketing consent), self-hosted fonts / static Product Hunt badge, server-side CAPI — see Privacy Policy / DPO list.

Granular Consent

Statistics and Marketing can be accepted or rejected independently.

Simple Revocation

Scripts disabled; first-party cookies cleared best-effort; third-party cookies may remain under provider control.


Data Transfers Outside the EU

Third parties (Google, Meta, LinkedIn, OpenAI Ads CDN, etc.) may process data outside the EEA. Safeguards under Arts. 44 et seq. GDPR (e.g. DPF / SCCs) where applicable are described at a high level in the Cookie/Privacy Policies; contract evidence is held separately.


Contacts

Note: Italian Cookie Policy page is authoritative for legal purposes where both languages exist.