Developers

The consent cookie

What the allowedit_consent cookie stores, how long it lasts, why it counts as strictly necessary, and how a new banner version asks visitors again.

allowedit remembers each visitor's choice in one first-party cookie on your domain, named allowedit_consent. This page explains what's in it, how long it lasts and when the banner asks again.

What it stores

The cookie holds a small JSON object, encoded so it's safe in a cookie:

{
  "id": "k3v9x2qa7m1d",
  "v": 3,
  "t": 1763560931000,
  "c": { "p": 1, "a": 1, "m": 0 },
  "a": "c"
}
KeyMeaning
idThe random consent id. It matches the record in your consent log, and the visitor can see it in the preferences panel
vThe consent version the choice was made under
tWhen the choice was made, in milliseconds since 1970
cOne flag per optional category: p preferences, a analytics, m marketing. 1 is allowed, 0 is refused
aHow the choice was made: a accept all, r reject all, c custom, o the opt-out link, g Global Privacy Control

It holds nothing else: no name, no email, no IP address, no list of pages visited.

Don't read the cookie directly in your code. Its format can change. Use window.allowedit.getConsent() from the JavaScript API, which returns the same information in a stable shape.

The cookie exists only to remember the visitor's privacy choice. Without it, the banner would ask on every page. Regulators treat a cookie like this as strictly necessary, so it's set even when the visitor rejects everything. It's listed under Necessary in your preferences panel and cookie declaration.

How long it lasts

The cookie lasts as long as your consent expiry setting: 365 days by default. You can set anything from 30 to 395 days in your dashboard, under Banner, then Behaviour.

When the cookie expires, the banner asks again. Some regulators expect consent to be renewed at least every 13 months, which is why the longest setting is 395 days.

When the banner asks again

The banner shows again when:

  • There's no cookie, because it's a new visitor, a new browser, or they cleared their cookies.
  • The cookie expired.
  • You asked everyone to choose again. When you publish from the Banner tab, ticking Ask visitors again raises the consent version. Every stored choice with an older version is ignored on the next visit, and the visitor chooses again.

Ordinary edits, like changing colours or fixing a typo, don't make visitors choose again. Ask again when something material changes, such as adding a new marketing tool to a category people already agreed to.

Domains and subdomains

The cookie is set on your main domain, so it's shared across its subdomains: a choice on www.example.com also applies on shop.example.com. Separate domains (for example example.com and example.co.uk) each have their own cookie, and visitors choose on each.

  • First-party: set on your domain, not allowedit's.
  • SameSite=Lax, so it's sent on normal navigation.
  • Secure on HTTPS sites.
  • Not HttpOnly, because the script needs to read it in the browser.

Your own server can read the cookie if it needs to know a visitor's choice before the page loads, but the format may change. If you rely on it, check this page when you update.

Still stuck? Email support@allowedit.com with your site's address and what you see.