Consent Capture to Compliance Evidence — Govern Every Consent, Every Purpose, Every Change
ConsentHub helps Data Fiduciaries/Users collect, manage and protect the consent of Data Principals/Subjects under data protection laws — with a signed record for every decision.
- Stay compliant. Itemised notices and per-purpose consent in multilingual, country-specific and regional languages — never a pre-ticked box.
- Build trust. Withdrawal, rights and grievances handled end to end, tracked to the clock.
- Prove it. Digitally signed consent receipts that anyone can verify offline.
Built for India’s DPDP Act 2023, Hong Kong’s Personal Data (Privacy) Ordinance (Cap. 486), South Korea’s Personal Information Protection Act (PIPA), Thailand’s Personal Data Protection Act (PDPA), Singapore’s Personal Data Protection Regulations 2021 and many more.
Every obligation is a workflow.
Every data protection law attracts heavy penalties for failure to observe security safeguards. Evidence is the difference between a claim and a defence.
Notice, itemised
What data, which purpose, how to withdraw, how to complain — independently presented, versioned and sealed at publication before a single consent is asked.
Consent that qualifies
Free, specific, informed, unconditional and unambiguous, with a clear affirmative action for each purpose — never a pre-ticked box.
Withdrawal & change
Every change is a new signed event, propagated to the fiduciary by signed webhook and reflected in the consent register.
Rights & grievance
Access, correction, erasure and nomination tracked to a clock; grievances follow the procedure ladder.
Retention & erasure
Retention windows by purpose. Erasure by crypto-shredding: the personal data is gone, the audit evidence is not.
Security & evidence
An append-only, tamper-evident ledger with tenant isolation enforced in the database — not in application code alone.
One decision. Five verifiable steps.
The same loop serves a loan application, an insurance quote or a telecom onboarding.
Publish
Define the purpose and publish an itemised notice, versioned and sealed at publication.
Ask
The Data Principal (Subject) verifies identity by one-time code and decides each purpose separately.
Seal
The decision is appended to the tamper-evident ledger and digitally signed.
Return
The fiduciary (User) exchanges a 60-second, single-use code for the verified record.
Verify
Anyone checks the receipt — or the full ledger — offline with the public key.
From first notice to final proof.
Six capability groups cover the consent lifecycle — and the evidence that outlives it. Everything shown is built into the platform.
Purpose & notice registry
Define purposes, lawful basis and retention windows. Publish itemised, versioned notices with a diff before anything goes live.
Consent capture
A hosted consent surface with one-time-code identity, per-purpose affirmative decisions and a recorded assurance level.
Signed receipts
Every decision returns a receipt a third party can verify offline — no account, no database, no call to the platform.
Consent register
Current state and full history for every principal (Subject) and purpose. Withdrawal arrives as a signed webhook, not a poll.
Rights & grievances
Access, correction, erasure and nomination with SLA clocks, plus the grievance ladder and rule clocks as per the applicable data protection law.
Integration & operations
A three-call API with signed requests, exact redirect allow-list, audit search and ledger verification.
Evidence, not assertions.
Verify it yourself.
$ consenthub-verify --receipt receipt.json \
--pubkey consenthub-public.pem
receipt rcp_01a126… VERIFIED
purposes LOAN_UNDERWRITING:granted
KYC:granted
MARKETING:denied
payload hash matches
signature valid
Runs where your data lives.
On-premises or in your private cloud — runs entirely on your infrastructure, with no dependency on a Uqrypt-hosted service.
Three calls. Predictable edges.
Client credentials over TLS, then signed requests covering timestamp, method, path and body hash. Webhooks are signed, retried with exponential back-off, then dead-lettered — nothing is dropped silently.
Built for production load.
Signing adds about 0.2 ms per consent event, and a single core verifies 3,000+ signed events per second — so a full-ledger integrity check is routine, not a batch job.
From 100k to 50M+ principals.
Reference sizing from small to enterprise deployments, confirmed against your journey mix during implementation. Benchmark report and technical sheet available on request.
See it with your own notice.
Bring one purpose, one notice and one customer journey. We will run grant → receipt → withdrawal → rights request, then hand you the receipt to verify offline.