Skip to app details
Back to app library
APPNEURAL APP FAMILYIdentity & Security

Consents

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.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
Consent settings
Cookie categoriesIllustrative configuration
01NecessaryExample
02AnalyticsExample
03MarketingExample
02 / CAPABILITIES

Built around the work you do.

What Consents does for you.

01

Banner

A banner and settings panel in the brand's colours, with region rules and policy versions.

02

Consent records

Each choice is logged with a consent ID and a salted address hash, never the address.

03

Site scan

Finds third-party scripts and cookies and matches them to 107 known services.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Consents. What you can do depends on your access in the app.

01

Scan the website

See which services and cookies it uses.

02

Set up the banner

Choose the look, texts and categories, then publish.

03

Install the tag

Put one tag first in the page head and mark the tags that need consent.

YOUR NEXT MOVE

Make Consents part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2PARTIALLY VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

Cookie consent for a connected domain's websites: a banner with categories and Google Consent Mode, consent records as proof, a cookie policy and a site scan.

Newsletter opt-in belongs to Subscriptions; site traffic belongs to Analytics.

Priority
P2
Portfolio
Identity & Security
Capability
Identity & Security
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T05:18:53.831Z
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

consent schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

consents.appneural.com DEPLOYED

consents.appneural.com

Worker
consent-catalog
Health
HEALTHY
Last deployment
2026-11-10 19:33:57
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

Repository provider is not connected. Existing references remain unverified.

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is partially verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app