Consent definitions
Versioned definitions with legal basis, required state, parent relationships, and scope type.
Consent has become product infrastructure
-
One governed consent record
Every grant, denial, expiry, and reconsent sits in a structured model instead of scattered product logs.
-
Privacy controls that match product reality
Applications, channels, legal bases, purposes, and scope context are managed together.
-
Audit evidence on demand
Versioned definitions and user decisions make review work predictable for legal, security, and product owners.
An operating surface for consent definitions and decisions
Dashboard
Coverage, expiry, and reconsent in one view.
Leadership sees the posture. Operators can drill into definitions, applications, channels, and user decisions.
Enough structure for legal, product, security, and engineering
Application coverage
Link consent rules to products, channels, legal entities, recipients, and business purposes.
Reconsent operations
Find expiring, outdated, and policy-changed consents before they become customer or compliance work.
Evidence trail
A clear history for who consented, to what, when, from where, and against which version.
Admin workflows
Bulk operations, exports, and review surfaces for the people accountable for consent operations.
Ready for integrations
Designed to sit beside CIAM, portals, CRMs, data platforms, and Agent-assisted workflows.
Simple enough to govern. Specific enough to integrate.
- Model
- Definition, purpose, scope, channel, recipient, legal basis, version.
- Capture
- Grant, deny, revoke, expire, replace, and reconsent events.
- Operate
- Dashboards for coverage, gaps, expiry, outdated versions, and adoption.
- Prove
- Queryable history for audits, incidents, DSARs, and governance reviews.
Built beside identity, customer portals, and data workflows
Questions before a pilot
-
Is ConsentHub a CMP for cookie banners?
No. It can receive decisions from a banner, but it is built as the governed consent system behind applications and business processes.
-
Where does it fit in the identity stack?
Next to CIAM and federation. Identity tells you who the user is. ConsentHub records what the user has allowed and which version applies.
-
Can it support machine and account-level consent?
Yes. The model supports user, account, product, application, and contextual scopes where the business process needs them.
-
How technical is the rollout?
Start with one consent domain and one application. Then connect additional channels, exports, and APIs as the operating model matures.
Ready to scope ConsentHub?