Purpose-wise consent, in every Indian language.
Build layered notices that itemise every purpose, collect consent through an embeddable widget, honour withdrawals on time and keep proof that can't be quietly edited.
From the first notice to the last withdrawal.
Layered notice builder
Itemise each purpose you collect data for, with the data used for each one.
Embeddable consent widget
Drop it into any page or flow, in 22 languages with auto-translation.
Notice versioning
Material changes are detected automatically and fresh consent is requested.
Consent withdrawal
Public withdrawal page, confirmation email, DPO alert and a 7-day cease task.
SHA-256 proof vault
Write-once records of every consent. Nothing can be edited or backdated.
Proof and analytics
Single-record proof PDFs, plus filterable consent analytics with XLSX export.
44 data categories
Standard categories in 8 groups, with special-category and children's-data warnings.
Itemised by purpose. Versioned automatically.
Write the notice once, list every purpose and the data behind it, and publish it in all 22 scheduled languages. If you change something material, ConsentArc spots it and asks for fresh consent.
- Layered notice builder
- Automatic detection of material changes
Sensitive data gets flagged as you build.
Pick from 44 standard data categories across 8 groups. When a purpose touches special-category or children's data, you see a warning before the notice goes live.
Data collected for this purpose
44 categories · 8 groups
Special-category data selected. Check the purpose truly needs it.
Children's data selected. Verifiable parental consent is required.
Withdrawing is as easy as consenting.
People withdraw on a public page. They get a confirmation email, your DPO is notified, and an automatic task makes sure processing stops within seven days.
- Public withdrawal page
- DPO notification and 7-day cease-processing task
Evidence that cannot be quietly edited.
Every consent and withdrawal is stored with a SHA-256 hash in write-once storage. Pull a proof PDF for any single record, or filter and export everything to XLSX.
- Single-record compliance proof PDF
- Filterable analytics with XLSX export
Each record sealed to the one before it.
Records are chained by hash, so a changed or backdated entry would stand out immediately. What you hand a regulator is a record, not a database export.
- record #1042sealed
Correction request closed
region IN-KAnotice v3.2sha256 19be185e…prev 93d24de7… - record #1041
Withdrawal · marketing
region IN-MHnotice v3.2sha256 93d24de7…prev 0de68370… - record #1040
Consent · 3 purposes · हिन्दी
region IN-UPnotice v3.2sha256 0de68370…prev 87fab8f9…
Mapped to the clauses that apply.
Every workflow in this module traces back to a specific obligation, so you can show an auditor why each step exists.
- DPDP Act S5A notice must accompany or precede every request for consent.
- DPDP Act S6Consent must be free, specific, informed and unambiguous, and withdrawing it must be as easy as giving it.
- DPDP Rules, Rule 3Notices must be clear, stand on their own and itemise the data and each purpose.
Ready to move forward?
Confirm your tier and we'll provision your tenant and walk you through setup.
hello@consentarc.com+91-9532453200Data stored in India