Banner
A banner and settings panel in the brand's colours, with region rules and policy versions.
Cookies only after a yes, with proof
Add a cookie banner to the website with one tag, honour each visitor's choice, and keep proof of it.
One tag (/embed.js) shows a banner (bar, box or modal) in the brand's colours with Accept all, Reject all and Choose given equal weight, a settings panel per category with its services and cookies, English and Hindi, a first-party cookie and a floating "Cookie settings" button. Scripts marked type="text/plain" data-consent run only after consent; Google Consent Mode v2 defaults are set before any tag and updated on each choice; withdrawing a category deletes its cookies. Each website sets its layout, texts, categories (necessary always on) and services from a list of 107 known services, region rules by country (opt-in, notice or off) and a policy version; publishing a new version asks everyone again. Every choice is logged through POST /api/v1/consents with a random consent ID, the categories, version, time, country and a salted address hash, never the address itself; a consent ID opens a proof page with the exact banner wording of that moment. Stats by day, country and category, CSV, a daily retention cron, a server-side site scan that maps scripts and Set-Cookie headers to known services, /cookie-policy and /preferences pages, webhooks, and Claude for banner texts and Hindi translation.
What Consents does for you.
A banner and settings panel in the brand's colours, with region rules and policy versions.
Each choice is logged with a consent ID and a salted address hash, never the address.
Finds third-party scripts and cookies and matches them to 107 known services.
A suggested path for Consents. What you can do depends on your access in the app.
See which services and cookies it uses.
Choose the look, texts and categories, then publish.
Put one tag first in the page head and mark the tags that need consent.
Live host, inventory, governance, health checks, verification, dependencies and history.
One tag (/embed.js) shows a banner (bar, box or modal) in the brand's colours with Accept all, Reject all and Choose given equal weight, a settings panel per category with its services and cookies, English and Hindi, a first-party cookie and a floating "Cookie settings" button. Scripts marked type="text/plain" data-consent run only after consent; Google Consent Mode v2 defaults are set before any tag and updated on each choice; withdrawing a category deletes its cookies. Each website sets its layout, texts, categories (necessary always on) and services from a list of 107 known services, region rules by country (opt-in, notice or off) and a policy version; publishing a new version asks everyone again. Every choice is logged through POST /api/v1/consents with a random consent ID, the categories, version, time, country and a salted address hash, never the address itself; a consent ID opens a proof page with the exact banner wording of that moment. Stats by day, country and category, CSV, a daily retention cron, a server-side site scan that maps scripts and Set-Cookie headers to known services, /cookie-policy and /preferences pages, webhooks, and Claude for banner texts and Hindi translation.
Newsletter opt-in belongs to Subscriptions; site traffic belongs to Analytics.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
consents.appneural.com
Verification is partially verified. Run verification to store check-level evidence, confidence, expiry and remediation.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.