Features · only what ships today

Scan. Score. Publish. Prove.

Every screen in the workspace exists for one of those four verbs. This page shows what each one does, with the limits stated.

Start 7-day demoTour the screens

Consent overview

The numbers that say whether the banner works

Impressions, decisions, accept rate and consent rate for the range you pick. Server timestamps are the source of truth, so a visitor with a wrong clock cannot skew a day.

  • Accept, reject and custom split, plus opt-in per category
  • Country breakdown from the CDN geo header
  • Zero-filled hourly or daily series, so gaps show as gaps
  • Activity feed: scans finished, banners published, domains added

Domains & scanner

Prove you own it, then see what it sets

Four ways to verify a domain: a DNS TXT record, a meta tag, a well-known file, or the tag itself reporting in from a page on that domain. A failed check stores the reason, so the list shows why without you re-running it.

  • Headless Chromium loads the site, waits for deferred and third-party scripts, and collects every cookie with party and expiry
  • A curated rule set names the vendor: _ga to Google Analytics, _fbp to Meta, __stripe_ to Stripe
  • Anything unmatched is marked unknown for a manual category
  • Cookie declaration generated as JSON or an HTML table

Compliance engine

14 rules, ranked by severity, scored 0 to 100

Every banner config runs through the same pure, unit-tested checker. The workspace view rolls the results up per domain and adds alerts for unverified domains, failed scans and banners that stopped reporting.

  • GDPR on means a Reject button is required. The API returns 400 if you try to publish without one
  • Findings link to the builder screen that clears them
  • Rule set is per workspace: GDPR, CCPA and consent behaviour

Consent log

A receipt for every decision

Consent events are inserted and aggregated, never updated. Each one stores the banner version, title, description and policy URL the visitor saw at that moment, because the config is overwritten on publish and nothing else remembers.

  • Per-category grants, country, salted SHA-256 of the IP, truncated user agent
  • Filter by action, country, date and domain
  • Export CSV or PDF
  • Rows written before snapshots existed say “not captured” rather than a guess

Users & access

Five roles, one permission matrix

Permissions are a typed module by action matrix, returned with the session and enforced twice: the panel hides what you cannot do and the API rejects it anyway. Only owners manage billing.

  • Owner, admin, editor, analyst, viewer
  • Invite by email; seat limits and last-owner checks are server side
  • Suspend a member from one workspace without touching their other workspaces
  • Every member gets an email when their access changes, so a lockout is never silent

See it on a client domain.

Add a domain, run the first scan and publish a banner. Seven days, every feature, no card.

Start the 7-day demo

GDPR · UK-GDPR · CCPA · Google Consent Mode v2