Pricing
Data Principals under management. Never the number of consents they give.
Consent management platform pricing for India, priced on the people you hold data about — never on the consents they give.
Starter
One product, one country, a team working to 13 May 2027.
Contact for pilot pricing
Priced on Data Principals under management
- Notice generation in all 22 scheduled languages
- Purpose-scoped consent capture and withdrawal
- Hash-chained audit ledger
- Grievance inbox with the Sec. 13 clock
Growth
Several products or brands under one Data Fiduciary.
Contact for pilot pricing
Priced on Data Principals under management
- Everything in Starter
- Webhook propagation to downstream systems
- Evidence export for auditors
- SSO and role-based access
Enterprise
Significant Data Fiduciaries, and anyone carrying a DPO obligation.
Contact for pilot pricing
Unmetered
- Everything in Growth
- Cross-border transfer register
- Named DPO workspace and audit support
- Deployment in your own cloud account
What counts as a consent
One Data Principal, one purpose, one decision. A person who consents to payroll processing and to benefits sharing has created two records: Sec. 6(1) makes consent specific to a purpose, and Sec. 6(4) requires withdrawal from one to be as easy as giving it was.
We do not charge per consent. Not per record, not per capture, not per withdrawal, not per API call.
Counting those records for billing would price the correct design higher than the incorrect one: unbundle three purposes so a person can withdraw from one, and a per-consent meter has just tripled your invoice for improving your compliance position. Plans are priced on Data Principals under management, and the number of purposes is yours to decide on the merits.
What you get in every plan
All six duties, on every tier. There is no plan where the statute is an upgrade; the higher tiers add scale and support.
- Sec. 5 · Rule 3
Notice, in a language the person reads
Versioned templates per purpose, in English or any of the 22 scheduled languages, snapshotted into the record.
- Sec. 6(1)
One consent record per purpose
Nothing pre-ticked, with a diff trail whenever a purpose changes.
- Sec. 6(4)–6(6)
Withdrawal that reaches your systems
One action, propagated over webhooks, with a cessation timestamp per system that acknowledged it.
- Sec. 8(5)
An append-only, hash-chained trail
A record whose integrity can be checked by someone who does not trust the database it sits in.
- Sec. 13 · Rule 14
Grievance redressal with a clock
A named route, a response window, and the evidence that it was met.
- Sec. 16 · Rule 15
Cross-border, enforced at the write
A transfer register applied when data is written rather than audited afterwards.
Questions people ask
- How much does DPDP compliance cost?
- Less than the quotes suggest, and mostly not software. Four variables move it: how many Data Principals you hold records for; how many distinct purposes you process for; how much of your existing base needs re-noticing because the original notice did not meet Sec. 5; and how many downstream systems a withdrawal has to reach. The last two dominate the first year and neither is a licence fee. The platform is usually the smallest line on the invoice.
- Do you charge per consent?
- No. Not per record, not per capture, not per withdrawal, not per API call. The meter is Data Principals under management, so splitting a bundled consent into the separate purposes Sec. 6(1) requires costs nothing extra.
- Is there a free trial?
- There is a pilot rather than a self-serve trial: one purpose, your notice text, your data. What you evaluate is your own consent flow rather than a demo tenant. Length and scope are set when we scope the pilot with you.
- What counts as a consent?
- One Data Principal, one purpose, one decision. A person who agrees to payroll processing and to benefits sharing has created two records, because Sec. 6(1) makes consent specific to a purpose and Sec. 6(4) requires withdrawal from one to be as easy as giving it was.
- What happens if we exceed the plan?
- Nothing stops. Capture and withdrawal keep working, because an outage in the middle of a statutory obligation is not a billing lever. We reconcile at the end of the period.
- Do we need this before 13 May 2027?
- The duties commence then. Consent taken earlier does not lapse — Sec. 5(2) lets processing continue once you have given the Data Principal a notice, as soon as is reasonably practicable. What that means in practice is noticing an existing base, per person and per purpose, which is the part that takes months rather than weeks.
Or read what the platform does first, on the consent management platform page, and how it integrates in the developer guide.