How it works
From the first scan to documented consent
Six steps, one chain. Each one builds on the one before, so your banner, your policy and your records always describe the same website — the one you actually have.
Start free 101-day trialThe scan finds your cookies. You decide on the ones it cannot place.
Step by step
What happens, and when
1. A real browser scans your website
Our scanner opens your pages in a real browser and lets your scripts run, just as a visitor's browser would. It visits them as someone who has not answered the banner and as someone who has accepted, and records every cookie, who set it and on which page — third-party ones included. Scans run again on a schedule, so a new tool on your site does not go unnoticed.
2. Every cookie gets a category
Known cookies are recognised from a curated catalogue and from the tags that set them. The ones nobody recognises go on a list for you, so a person decides — never a guess that quietly becomes the answer.
3. Your cookie policy is written from the scan
The policy lists the cookies that are actually on your site, in the categories you approved. Every version is kept with a timestamp, so you can always show what it said, and when. It is hosted for you and can be linked or embedded.
4. Scripts wait for a yes
A small blocker runs first on your pages and holds back the tags it recognises — from our library of trackers and your own rules — until their category is granted. When consent is given, the tags load; when it is withdrawn, the cookies they set are cleared. Google Consent Mode signals follow the same choice, and the Global Privacy Control signal can be honoured.
5. Every choice is recorded
Each answer to the banner is stored with a timestamp and the banner version it was given on. That is the record a regulator asks for, ready the day someone asks.
6. Visitors stay in control
Your cookie policy shows each visitor their consent ID and choices, so they can change or withdraw them at any time — and withdrawing clears the cookies that consent allowed.
Setup
What runs automatically, and what you do
You create your account and verify your domain. The scan finds your cookies and classifies the known ones; you decide on the rest and place one snippet.
<script>
window.CookieForeverConfig = {
"apiBaseUrl": "https://cdn.cookieforever.com",
"domain": "yourcompany.com",
"siteId": "your-site-id",
"language": "en",
"autoInit": true
};
</script>
<script src="https://cdn.cookieforever.com/cookieforever-blocker.js?site=your-site-id"></script>
<script src="https://cdn.cookieforever.com/cookieforever.js" data-site-key="your-site-key" async defer></script>Automatic You
-
Create your account You
Your domains and their settings stay in one place.
-
Verify your domain You
By DNS, a file or a meta tag — whichever is easiest for you.
-
Your website is scanned Automatic
Cookies are found and the known ones are classified. You decide on the rest, and your cookie policy follows.
-
Place one snippet You
From then on, your visitors' choices are enforced automatically.