A cookie policy short enough to actually finish.

A cookie is a small text file that a website asks your browser to store on your device. When you return, the browser sends it back, so the site can recognise the same browser and remember something about it — a language choice, a login, or the fact that a visit is continuing rather than starting fresh.

Cookies cannot read your hard drive, run programs, or carry viruses. What makes them worth a policy is not the file itself but what a site chooses to record in it, and who else gets to read it.

The distinctions that matter

• First-party vs third-party. First-party cookies are set by the site you are visiting. Third-party cookies are set by another domain altogether, which is how tracking across unrelated websites usually works.
• Session vs persistent. Session cookies are deleted when you close the browser. Persistent cookies survive until they expire or you delete them.
• Essential vs optional. Essential cookies are needed for the site to do what you asked. Everything else — analytics, personalisation, advertising — is optional, and in many jurisdictions requires your consent.

Related technologies

Local storage serves a similar purpose but is not a cookie: it lives in your browser and is never automatically transmitted with requests. We use it for the AI assistant, and because people reasonably expect to find it on a page like this, we document ours in section 2 alongside the cookies.

This policy covers zyverralabs.com. It sits alongside our Privacy Policy, which explains everything else we do with personal data, and our Terms & Conditions.

Essential cookies make the site do what you asked it to. They set no advertising profile, follow you nowhere, and under UK and EU rules they are exempt from consent precisely because they are strictly necessary. There are two.

NEXT_LOCALEis written only when you actively pick a language from the selector in the navigation bar. Until you do, we work out a sensible default from your browser’s own language setting and store nothing.

zyverra_admin is an internal staff cookie. It is issued only after a successful login to our admin dashboard, it is HttpOnly so no JavaScript can read it, it is marked Secure in production, it uses SameSite=Lax, and it expires after 8 hours. If you are a visitor rather than a member of our team, your browser will never receive it.

Browser local storage

The AI assistant stores two entries in your browser’s local storage. Neither is a cookie, and neither is attached automatically to any request.

The session key is a random identifier generated in your browser. It is not linked to your identity unless you tell the assistant who you are, and clearing your browser storage removes it permanently — the only consequence is that the assistant no longer remembers your earlier thread.

We use Google Analytics 4 to understand which pages people read, how they arrive, and where the experience is slow. It is the only analytics tool on this site, and it is opt-in: the script is not requested at all until you accept it in the consent banner, so none of the cookies below exist before then. It also runs only on the live production site — development and preview builds send nothing regardless.

These are set as first-party cookies on our own domain. The data behind them is pseudonymous: we see sessions, page views, approximate location at country or city level, device and browser type, and the referring site. We do not see who you are, we do not try to reverse the identifier into an identity, and we never join analytics data to an enquiry you send us.

Google Analytics 4 does not store full IP addresses in its reports. We use no Google Signals, no demographic or interest reporting, and no advertising features, so this data never becomes an ad audience.

Turning analytics off

• Decline in the banner, or change your mind at any time from section 5. Declining also deletes any analytics cookies already set in this browser.
• Install Google’s official opt-out browser add-on at tools.google.com/dlpage/gaoptout, which blocks measurement on every site you visit.
• Block analytics cookies or scripts in your browser settings or a content blocker — see section 5.
• Use a browser with tracking prevention enabled, or send a Global Privacy Control signal.

To be specific about what that rules out, this site carries none of the following:

• Advertising or conversion pixels — no Meta pixel, no LinkedIn Insight Tag, no Google Ads remarketing tag, no TikTok or X pixel.
• Retargeting cookies — nothing that follows you to another site to show you an advertisement for us.
• Cross-site tracking or data brokers — we do not build behavioural profiles, and we do not buy, sell, or enrich visitor data.
• Affiliate or ad-network tags — we run no advertising on this site and host no third-party ad code.

Because we neither sell nor share personal information for cross-context behavioural advertising, a Global Privacy Control signal changes nothing about how this site behaves — we already act as though it were always on.

If this ever changes, we will update this page before any such cookie is set, ask for your consent first where the law requires it, and give you a way to withdraw it just as easily.

You are in control. Analytics cookies are set only if you accept them in the consent banner, you can change that decision at any time right here, and every cookie on this page can also be blocked or deleted from your own browser.

Your analytics consent

We ask once, on your first visit, and we remember the answer so we do not ask again. Declining is a single click and carries no penalty — nothing on this site is gated behind accepting.

In your browser settings

Every major browser lets you view stored cookies, delete them individually or in bulk, block third-party cookies, or refuse all cookies from a specific site. Current instructions from each vendor:

Clearing local storage

Local storage is cleared separately from cookies in most browsers, usually under a “cookies and site data” or “clear browsing data” option. Clearing it removes your AI assistant session and saved project threads from this device.

Private browsing and content blockers

A private or incognito window discards cookies and site data when you close it. A content blocker or privacy-focused browser will typically block the analytics script before it ever runs.

What you lose by blocking

• Analytics cookies — nothing at all. The site is identical without them.
• NEXT_LOCALE— the site stops remembering your chosen language and falls back to your browser’s setting on each visit. You can still switch language manually every time.
• Local storage — the AI assistant starts a fresh conversation instead of restoring your previous thread.

No page, form, or feature on this site is gated behind accepting a cookie.

How our banner behaves

Our consent banner has no pre-ticked boxes, no “legitimate interest” toggles left on by default, and no dark patterns making refusal harder than agreement — accept and decline are one click each, side by side, with equal weight. Until you choose, nothing optional runs.

If we ever add a non-essential cookie beyond the ones listed on this page, we will document it here and ask for your consent again before it is set.

A third-party cookie is one set by a domain other than the site you are on. This site sets none for advertising. The only external party involved in cookies here is Google, through Analytics.

Google Analytics

The _ga cookies described in section 3 are written as first-party cookies on our domain, but the data is processed by Google as our analytics provider. Their handling is governed by Google’s Privacy Policy and their business data terms.

Other services we use, which set no cookies here

Several providers support this site without placing anything in your browser. They are listed in full, with what each one processes, in our Privacy Policy.

• Vercel hosts the site and keeps operational request logs server-side.
• OpenAIpowers the AI assistant’s replies via a server-side API call — the request goes from our server, not from your browser.
• Resend delivers enquiry notifications to our own inbox. It sets nothing on this site, and we use no tracking pixels in the emails we send you.
• Neon / PostgreSQL stores enquiries and assistant conversations. It is reachable only from our server.

Links to other sites

Our footer links to profiles such as LinkedIn, and articles may link to external sites. Once you follow a link you are on someone else’s domain, under their cookie policy, and we have no control over what they set. We suggest reading the policy of any site you are not familiar with.

Client products we build

This policy covers zyverralabs.com only. Software we design and build for clients runs under the client’s own cookie and privacy policies, and they decide what those products set.

Questions about a specific cookie, a request to delete data associated with one, or a correction to this page — all go to the same place, and a person reads every one.

Updates to this policy

We will update this page whenever the cookies on this site change. The effective date at the top always reflects the current version, and any new non-essential cookie will be documented here before it is set.

To exercise a data access, correction, or deletion right, see the Privacy Policy. To talk about a project instead, start from the contact section.