Cookie notice
What can run in your browser on veyrareach.com, what each part is for, and how to change your mind. Nothing beyond what the site strictly needs starts until you accept it.
Last updated 19 October 2026
The short version
The cookie banner offers three categories. Strictly necessary covers what the site needs to work and is always on. Analytics turns on Google Analytics, so we can see how the site is used and which sources and campaigns bring visitors. Marketing turns on the LinkedIn Insight Tag, the Google Ads tag and the Meta Pixel, so we can measure our advertising and reach visitors again on those platforms. Analytics and Marketing stay off until you accept them, and you can change your choice at any time with Cookie choices in the site footer.
There is no session recording and no social embed anywhere on veyrareach.com. Typefaces are served from our own domain. Next.js self-hosts them as static assets at build time, so your browser never calls a font provider while you read this page.
What actually runs, and when
The table below is taken from the code rather than from a template. If a script is not listed here, it is not on the site.
| Who | When it runs | What it is for | What it stores |
|---|---|---|---|
| Veyra | Every page | Serving the site itself, and remembering your cookie choice | No cookie of its own: there is no login or session on the public site. Your cookie choice is kept in your browser's local storage, so the banner does not ask again on every page; clearing the site's data removes it. |
| Google Analytics | Every page, only after you accept Analytics | Shows us how the site is used, where visits come from and which campaigns lead to a demo request or a purchase | _ga and _ga_ followed by an identifier, on this domain, for up to two years, to recognise a returning visit. Not set if you reject Analytics. |
| LinkedIn Insight Tag | Every page, only after you accept Marketing | Measures conversions from our LinkedIn campaigns, builds retargeting audiences, and shows us visitor demographics in aggregate | Cookies such as li_sugr, bcookie, lidc, UserMatchHistory, AnalyticsSyncHistory and li_fat_id, lasting from one day to two years. Loaded from snap.licdn.com, reporting to px.ads.linkedin.com. |
| Google Ads | Every page, only after you accept Marketing | Measures conversions from our Google Ads campaigns and builds remarketing audiences | _gcl_au on this domain for 90 days, and Google advertising cookies on doubleclick.net and google.com for up to 13 months. Consent Mode signals pass on the choice you made. |
| Meta Pixel | Every page, only after you accept Marketing | Measures conversions from our Facebook and Instagram campaigns and builds retargeting audiences | _fbp on this domain and fr on facebook.com, each for 90 days. |
| Cloudflare Turnstile | Only when you open the checkout email step or the Fall Sweep claim box | Proves the request comes from a person rather than a script, before an email address is accepted | Turnstile sets cf_clearance, which records that a challenge was passed so you are not asked again on every step, and __cf_bm, Cloudflare's bot management cookie, which expires after about 30 minutes. It also keeps short-lived values in browser storage while a challenge is running. None of it identifies you, none of it follows you to other sites, and Turnstile is built specifically not to profile the visitor. |
| Stripe | Only on the checkout page, once you reach the payment step | Takes the payment and screens it for fraud | Stripe sets __stripe_mid, a machine identifier lasting about a year, and __stripe_sid, a session identifier lasting about 30 minutes. Both exist to spot card fraud, and Stripe describes them as necessary for that purpose. Worth knowing: Stripe.js is not loaded on the pricing page at all. It arrives only when you open the checkout, so these are not set by browsing the site and comparing plans. |
The three categories in the banner
- Strictly necessary. Always active, because the site cannot work without it, so no consent is asked. It covers the record of your cookie choice, kept in your browser's local storage rather than in a cookie, Cloudflare Turnstile when you request a code or start checkout, and Stripe during a payment.
- Analytics. Google Analytics 4, provided by Google Ireland Limited. It sets _ga and _ga_ followed by an identifier, which last up to two years, and records the pages viewed, the referrer and traffic source, the campaign parameters (UTM tags) in the link you arrived by, device and browser, and an approximate location derived from a truncated IP address. It also receives the conversion events described below.
- Marketing. The LinkedIn Insight Tag (LinkedIn Ireland Unlimited Company), the Google Ads tag (Google Ireland Limited) and the Meta Pixel (Meta Platforms Ireland Limited). They measure which of our campaigns lead to visits and conversions, build audiences so our ads can reach visitors again on LinkedIn, Google, Facebook and Instagram, and, on LinkedIn, show us the companies, industries and job functions of our visitors in aggregate only. Each loads only after you accept Marketing.
What the tags are told
When something happens on the site that matters to us, an event is sent to Google Analytics and to whichever marketing tags you allowed: a demo request, when you click the email link to book a demo; a sales enquiry, when you click an email link to talk to sales; a Fall Sweep code request; a waitlist signup; a checkout started, with the plan and billing period; and a completed purchase, with the plan, billing period, amount and currency, and the Stripe session reference as the transaction identifier.
No names, email addresses or other contact details are sent to Google, LinkedIn or Meta. Google Ads receives Google Consent Mode signals that reflect the choice you made in the banner.
For the collection and transmission of data through the Meta Pixel, Veyra and Meta Platforms Ireland Limited are joint controllers, as the Court of Justice of the EU held in Fashion ID (C-40/17); what Meta does with the data afterwards is Meta's own responsibility. Google, LinkedIn and Meta may process this data in the United States; each is certified under the EU-U.S. Data Privacy Framework, with standard contractual clauses as the fallback.
What we do not do
- No analytics or marketing unless you accept it. Nothing counts your visit or reports a conversion until you say yes to that category, and a refusal is remembered.
- No session recording or heatmaps.
- No social network embeds, no comment widgets, no chat widget.
- No third-party video. The trailer on the home page is a video file served from our own domain and played by your browser's own player, and it sets no cookies.
- No selling of personal data. Ad platforms receive only the events described above, and only from visitors who accepted Marketing.
Why there is a cookie banner
Consent is required before a cookie that is not strictly necessary is set or read (Article 6(1)(a) GDPR, and Article 5(3) of the ePrivacy Directive as each country implements it). Analytics and Marketing are genuinely optional, so they are asked for rather than assumed: nothing from Google, LinkedIn or Meta is loaded, and none of their cookies exists, until you accept the category it belongs to. Reject all is as easy as Accept all, a refusal is remembered, and the site works the same either way.
You can change your mind at any time. Cookie choices in the site footer reopens your preferences; switch a category off and nothing from it runs from then on.
Cloudflare Turnstile and Stripe are treated differently because they are not optional. Our assessment is that both qualify as strictly necessary: the Turnstile values exist only to establish that a request came from a person, and the Stripe values exist only to detect card fraud during a payment you asked to make. Neither is used for advertising or profiling. Asking permission for cookies you cannot decline and still buy anything would be theatre, so the banner asks only about what you can genuinely refuse, and it appears before any of that is stored, not after.
How to control cookies yourself
Every browser lets you see what a site has stored, delete it, and block future storage, usually under Settings and then Privacy. Blocking storage for veyrareach.com costs you nothing while you read the site. It will, however, break the checkout: Stripe cannot complete a payment or run its fraud checks without it, and the Turnstile challenge cannot record that you passed. Clearing the site's data also clears your cookie choice, so the banner asks again on your next visit.
Changes to this notice
If we add a script that stores anything, this page changes on the same day and the date at the top changes with it. If that script is not strictly necessary, it joins a category in the banner and stays off until you accept it.
Questions
Write to hello@veyrareach.com. The privacy policy explains what happens to the data behind all of this, and the sub-processors page names every vendor involved.
The rest of the legal set
Nothing measures you until you say yes
See what Veyra does with the data that matters instead: your pipeline, on your market.