Cookie
notice.
How the Velo website uses cookies, and how Velo handles consent records on the sites that run it.
This notice explains how this website uses cookies and similar storage, and how Velo handles cookies on the sites that run it. You can change your choice on this site at any time using the cookie button in the corner of the page.
1. What cookies are
Cookies and similar storage are small pieces of data a site keeps in your browser. Some are needed for the page to work. Others measure how the site is used or help with advertising, and those run only if you allow them.
2. Cookies on this website
In the EU, the EEA, the UK, Switzerland, Brazil, Peru, Colombia and Argentina, nothing but the items marked Necessary is stored before you choose. Elsewhere analytics and advertising are on by default: you can switch them off at any time from the cookie button, and a Global Privacy Control signal from your browser turns advertising off. Analytics and advertising items are set only while that category is allowed. If you withdraw it, the banner deletes the analytics and advertising cookies it can reach, and our server expires FPID and velo_gacid on your next page view. Our pages load no fonts or scripts from other domains, and our server counts visits from our ads without any cookie (see the privacy notice). What this site can store:
| Name | Purpose | Type · lifespan | Category |
|---|---|---|---|
| velo_consent | Remembers the choice you made in the cookie banner. | First-party cookie · 1 year; browser storage · until cleared | Necessary |
| velo_receipt | Links a later change to your last recorded consent choice. | First-party cookie · 1 year | Necessary |
| velo_subject | A random identifier, created when you make a choice, that ties your consent choices together in our consent log. If you allow analytics, PostHog also uses it as your analytics ID so that one visitor counts once. | Browser storage · until cleared | Necessary |
| FPID | An ID set by our server, which page scripts cannot read. Google Analytics uses it to recognise you on your next visit. | First-party cookie · 395 days | Analytics |
| velo_gacid | The Google Analytics ID derived from FPID, so a purchase in the console can be matched to your visit. | First-party cookie · 395 days | Analytics |
| _ga, _ga_* | Set by Google Analytics to tell visits and sessions apart. | First-party cookie · 2 years | Analytics |
| ph_* | Set by PostHog to keep your analytics ID and session, including for session recordings. | First-party cookie · 1 year; browser storage · until cleared | Analytics |
| velo_src, velo_cta | Remember the campaign or link that first brought you here, so a sign up can be credited to it. | Session storage · until the tab closes | Analytics |
"Only with consent" in the table below applies in the regions listed above; elsewhere Analytics and Advertising are on until you switch them off. When analytics or advertising is not allowed, Google's tags still send cookieless pings that tell Google your choice. They set no cookie, use no lasting ID, and our server forwards them without your IP address.
The categories the banner offers are:
| Category | Purpose | Runs by default |
|---|---|---|
| Necessary | Keeps the site working and remembers your consent choice. | Always on |
| Analytics | Google Analytics 4 and PostHog, including session recordings with form inputs masked. | Only with consent |
| Advertising | Google Ads conversion measurement, lists of past visitors to show our ads again, and a hashed email for enhanced conversions. | Only with consent |
| Functional and personalization | Offered by the banner. Nothing on this website uses them today. | Only with consent |
In the Velo console
The console at app.veloconsent.com uses the same consent items as this site, and velo_src there is kept in browser storage until cleared, once analytics is allowed. It also sets the items below, all needed for signing in. Its product analytics run only when analytics is allowed, and even then only in memory, so they store nothing on your device.
| Name | Purpose | Type · lifespan | Category |
|---|---|---|---|
| velo_session | Keeps you signed in. | First-party cookie · 30 days | Necessary |
| velo_oauth, velo_oauth_next | Protect a sign in with Google and bring you back to the right page. | First-party cookie · 10 minutes | Necessary |
| velo_ref | Set only when you follow an agency partner's referral link, so the partner is credited when you sign up. | First-party cookie · 30 days | Partner referral |
3. How Velo handles cookies on customer sites
Velo is a consent layer, not a tracker. It sets no marketing cookies of its own. Instead it decides when other tags are allowed to load, based on the visitor's choice, and passes the matching Google Consent Mode v2 signals. The only thing Velo stores for itself is a pseudonymised record of the consent choice.
On a customer's website the Velo banner stores the items below. All are strictly necessary: they remember the visitor's choice and link it to its record, and none is used for tracking or advertising. velo_receipt and velo_subject are set when the banner records choices in Velo, which is the default. Customers who list their cookies by hand can copy these rows into their own cookie notice.
When a visitor withdraws analytics or advertising after allowing it, the banner also deletes the common cookies and browser storage of that category that it can reach, such as those of Google Analytics, Google Ads, Meta, Microsoft Ads, TikTok, LinkedIn, PostHog, Clarity and Hotjar.
| Name | Purpose | Type · lifespan | Category |
|---|---|---|---|
| velo_consent | Remembers the visitor's consent choice. The cookie is set on the site's main domain, so the choice also applies on its subdomains. It holds the choice, when it was made, the visitor's country, whether Global Privacy Control was on, and the site's Velo ID. | First-party cookie · 1 year (7 days in Safari); browser storage · until cleared | Necessary |
| velo_receipt | Holds the reference of the visitor's last recorded consent choice, so a later change or withdrawal links to it. | First-party cookie · 1 year | Necessary |
| velo_subject | A random identifier that ties the visitor's consent choices together in the site's consent log. It is created when the visitor makes a choice, or on arrival when the site runs a banner test, so the visitor keeps seeing the same version. | Browser storage · until cleared | Necessary |
4. Managing your choices
On this site, open the cookie button in the bottom corner at any time to review or change your choice. In the console, use Cookie preferences in the account menu. In your browser settings you can also block or delete cookies, though some parts of sites may then work less well.
5. Changes to this notice
If the cookies or storage we use change, we will update this page and the date at the top. If we change this policy, we will ask you again.
Want the detail on data?
Read the privacy notice or email support@veloconsent.com.
