A cookie declaration that keeps itself current
Your privacy page should list the cookies your site uses. Paste one script tag and the list stays in step with every scan, so you never edit it by hand again.
Your privacy page, after a weekly scan
- Monday's scan finds _clck (Microsoft Clarity) You confirm it as analytics
- Your privacy page Analytics table now lists _clck, purpose and 1 year
- A cookie disappears from the site It drops off the list after the next scan
How it works
Three steps, most of them done for you.
- 1
Scan your site
The scanner finds your cookies and sorts the known ones into categories. You pick categories for the rest.
- 2
Paste the embed
Add <script src="https://allowedit.com/d/<siteId>.js"></script> where the table should appear on your privacy or cookie policy page.
- 3
Leave it alone
When the scanner finds a new cookie and you categorise it, the table updates. There's nothing to copy and paste.
What the declaration shows
What visitors and regulators expect a cookie policy to cover.
Cookies by category
Necessary, preferences, analytics and marketing, each with your description of what the category is for.
Name, provider and purpose
Each cookie's name, the domain that sets it, the vendor where we know it, and a plain description of what it does.
How long it lasts
Session, hours, days, months or years, taken from what the scanner saw.
A hosted page
No privacy page yet, or a builder that won't run scripts? Link to the declaration's hosted page on allowedit.com instead.
Matches the banner
The preferences panel lists the same cookies under each category, so the banner and your policy never disagree.
Only reviewed cookies
Unclassified cookies stay off the public list until you choose a category, so visitors never see an unexplained entry.
Do I need a cookie declaration?
Under the GDPR and the ePrivacy rules, consent only counts if it's informed. Regulators expect visitors to be able to find which cookies you use, who sets them, what they're for and how long they last. A cookie declaration on your privacy page is the usual way to do that.
It isn't a whole privacy policy. You still need one that explains what personal data you collect, why and the visitor's rights. We don't generate privacy policies.
Can it carry my agency's name?
On the Agency plan, yes. White label puts your agency's name on the declaration and the client reports instead of ours, so it reads as part of the service you provide.
What each plan gets
Pro is $10 a month for 3 sites. Agency is $39 a month for every site you run. Cancel any time. Your banners keep working if you do.
Free
- Embeddable declaration and hosted page
- Updated after every scan
- Monthly scans of up to 25 pages
Agency
- Your agency's name on the declaration (white label)
- A declaration for every client site
What it doesn't do
- It lists cookies, not a full privacy policy. We don't write privacy policies or terms.
- It only knows what the scanner has found, so cookies on pages the scan can't reach won't be listed.
- The embed needs a page that can run a script tag. If yours can't, link to the hosted page.
- Purposes for cookies outside our database are whatever you write for them.
Questions
Is the cookie declaration free?
Yes, on every plan, both the embed and the hosted page.
Can I style the table?
It takes your page's font, so it reads as part of the page. There are no other style settings yet; if it doesn't fit your design, link to the hosted page instead.
How often does it update?
Whenever your cookie list changes: after a scan (monthly on Free, weekly on Pro and Agency), a manual scan, or a category you change by hand.