CVRLanding
Get started

Legal

Cookie policy

The cookies and browser storage that cvrlanding.com and the CVRLanding app use, and how consent works on the landing pages our customers publish.

Draft — pending legal reviewLast updated October 14, 2026

This document is a draft

We wrote it for the CVRLanding preview build. It has not yet been reviewed by legal counsel for the countries we serve, and it will change before launch. It is not legal advice.

On this page

What this policy covers

Cookies and similar technologies are used in two different places, and different people decide what is stored in each:

  • cvrlanding.com and the CVRLanding app, which we run. This policy lists everything they store in your browser.

  • Landing pages our customers publish with CVRLanding, at cvrlanding.com/ld/… or on their own domains. Each customer configures the consent banner on its pages and decides which tracking to turn on.

In this policy, “cookies” also includes similar technologies such as localStorage, which save small pieces of data in your browser.

Consent categories

CVRLanding sorts storage and tracking into four consent categories. The consent banner on landing pages offers the same choices.

  • Essential

    What it covers

    Storage a site needs to work, such as security, sign-in, forms, a language preference and the visitor’s consent choice

  • Analytics

    What it covers

    First-party measurement of page views, sections seen, scroll depth and form steps

  • Advertising

    What it covers

    Meta, Google and TikTok pixels, and the ad click IDs used to measure campaigns

  • Session replay

    What it covers

    Masked recordings of how a visitor uses a page; where a page adapts to earlier visits, that personalization belongs here too

Essential storage always runs. For analytics and advertising, the business that runs a page chooses a default for each region: ask first, or allow with an opt-out where the law permits that. Pages always ask first in the EEA and the UK. Session replay stays off until the business turns it on, and then runs only for visitors who agree.

What cvrlanding.com and the app use

These are all the cookies and browser storage entries that cvrlanding.com and the CVRLanding app set today. Each one is essential or remembers a choice you made, and none is used to follow you across other websites.

  • NEXT_LOCALE cookie

    Purpose

    Remembers your language, English or Vietnamese

    Duration

    1 year

  • cvr-theme in localStorage

    Purpose

    Remembers your light, dark or system theme

    Duration

    Until you clear it

  • cvr_ws cookie

    Purpose

    Remembers which workspace the app shows. HttpOnly.

    Duration

    180 days

  • Sign-in session cookie

    Purpose

    Keeps you signed in. HttpOnly and Secure. Set only once accounts are live.

    Duration

    Until you sign out or the session expires

No analytics or advertising cookies

In this build, cvrlanding.com sets no analytics or advertising cookies and loads no third-party tracking scripts. If that changes, we will ask for your consent first where it is required and list the new entries here.

On landing pages built with CVRLanding

On a landing page published with CVRLanding, the business that runs the page is responsible for its consent banner and privacy notice. What the page may store depends on which categories are allowed:

  • The visitor’s consent choice is saved in localStorage (cvr_consent:…) so the banner does not ask on every visit. It asks again if the page’s consent policy changes. This entry is essential.

  • First-party analytics identifiers for visits and sessions are set only when Analytics is allowed.

  • Ad click IDs such as gclid, fbclid and ttclid are kept only when Advertising is allowed.

  • Meta, Google and TikTok pixels load, and set their own cookies, only if the business connected them and Advertising is allowed.

  • Session replay runs only if the business turned it on and the visitor agreed. Form inputs and personal data are masked.

Analytics from a landing page belong to the business that runs it; CVRLanding processes them on that business’s behalf and does not use them for its own advertising. Cookies set by ad platform pixels are governed by those platforms’ own policies.

Google Consent Mode v2

When a page uses Google tags, CVRLanding passes the visitor’s choices to Google through Consent Mode v2 before any tag loads:

  • analytics_storage

    Granted when

    Analytics is allowed

  • ad_storage

    Granted when

    Advertising is allowed

  • ad_user_data

    Granted when

    Advertising is allowed

  • ad_personalization

    Granted when

    Advertising is allowed

If a category is not allowed, the tags and events that depend on it do not fire. Google explains these signals in its Consent Mode documentation.

Managing your choices

On a landing page, use its consent banner or its cookie settings link to change your choice at any time. Withdrawing consent stops further tracking in that category. For data already collected, contact the business that runs the page.

The cvrlanding.com site shows no consent banner because it sets nothing optional. To change your language or theme there, use the switches in the page header, or clear the site’s data in your browser.

You can also block or delete cookies and site data in your browser settings. On cvrlanding.com, blocking essential cookies may stop language, workspace or sign-in from working.

Changes to this policy

We update this policy whenever the cookies or storage we use change, and we add any new entry here before we start using it.

Contact

For questions about cookies on cvrlanding.com, write to support@cvrlanding.com. For a landing page, contact the business that runs it; the Privacy policy explains our role.

Questions about this document? Email support@cvrlanding.com.