Cookie Policy
Last updated: 25 October 2026
What are cookies
Cookies are small text files saved by your browser when you visit a website. They can be used to remember your preferences or to analyse how you use the site.
Technical cookies and data (always active)
Some information is needed for the site to work and requires no consent. `vp_consent` (in your browser, no expiry) stores your cookie choice. `vp_locale` (cookie, 1 year) remembers the language you chose. `vp_utms` (in the browser session, until you close the tab) keeps the UTM parameters of the address you arrived from, i.e. the campaign that brought you here, so we can link them to the request you send. Before you make a choice in the banner we only store UTMs. Campaign click identifiers (`fbclid`, `gclid`, `gbraid`, `wbraid`) are stored only if you accept Marketing, and deleted if you withdraw.
| Cookie | Duration | Purpose |
|---|---|---|
| vp_consent | Persistent (localStorage) | Stores user cookie consent choice |
| vp_locale | 1 year | Remembers the user's chosen language, so it doesn't revert to the browser-detected one |
| vp_utms | Session (sessionStorage) | Keeps the UTM parameters of the campaign you come from, to link them to the request you send. Campaign click identifiers are stored here only with Marketing consent |
Analytics tools (consent required)
If you consent to Analytics we use: Google Analytics 4, loaded via Google Tag Manager, to measure traffic (cookies `_ga` and `_ga_*`); Vercel Web Analytics and Speed Insights, for visits and page speed (no cookies); Reviy, a visit analytics service, which may store a technical signal in the browser session; PostHog, on servers in the European Union, to which our server sends anonymous measurement events when you visit the Party Box page and fill in its form (the visit, the form steps and the submission, no contact data, no cookies). After our CRM has confirmed your request, the server also sends a confirmation event to Google Analytics. Data is pseudonymised. Google Analytics keeps it for 14 months; the other tools according to the settings of their respective services.
| Cookie | Duration | Purpose |
|---|---|---|
| _ga | 2 years | Distinguishes unique users (Google Analytics 4) |
| _ga_* | 2 years | Maintains GA4 session state |
| reviy:heartbeat:* | Session (sessionStorage) | Technical signal of the Reviy visit analytics service; deleted if you withdraw Analytics consent |
Marketing cookies (consent required)
If you consent to Marketing we use: the Meta Pixel (cookies `_fbp` and `_fbc`), which tells Meta about your interactions with the site; Google Ads tags loaded via Google Tag Manager (cookies `_gcl_au` and `_gcl_aw`), to link conversions to campaigns, also with encrypted contact data for enhanced conversions. With Marketing consent our server also tells Meta, through the Conversions API, that you submitted a request (with your contact data in hashed form, IP address, browser and click identifier). If you do not consent to Marketing in the banner, the Meta Pixel is not loaded and Google tags do not write advertising cookies; our server sends Meta the data of your request only if you authorise it with the optional checkbox in the form (described in the Privacy Policy), with no Pixel and no cookies.
| Cookie | Duration | Purpose |
|---|---|---|
| _fbp | 90 days | Identifies the browser for Meta Pixel, for advertising and remarketing purposes |
| _fbc | 90 days | Remembers the click on a Meta ad, to attribute conversions to the campaign |
| lastExternalReferrer | Persistent (localStorage) | Stores the last external site you came from, for Meta Pixel (advertising and remarketing) |
| lastExternalReferrerTime | Persistent (localStorage) | Stores when you visited the last external referring site, for Meta Pixel |
| _gcl_au | 90 days | Links conversions to Google Ads campaigns |
| _gcl_aw | 90 days | Remembers the click on a Google Ads ad, to attribute conversions to the campaign |
| _gcl_ls | Persistent (localStorage) | Links conversions to Google Ads campaigns (conversion linker, localStorage copy) |
Google Tag Manager and Consent Mode
Google Tag Manager loads on every visit. Before you choose, and if you decline, Google tags do not write analytics or advertising cookies, but through Consent Mode they may send Google technical signals without cookies and without identifying you (for example that a page was viewed), which Google uses to estimate conversions. With Consent Mode, Google click identifiers may be passed in page addresses, without cookies.
How to manage cookies
You can change or withdraw your choices at any time via "Manage cookies" in the footer of every page of the site (including campaign pages): it reopens the banner. Withdrawal stops future transmissions and deletes the data we store in your browser. You can also delete cookies in your browser settings (settings → privacy → cookies).