01
Consent Management
Capture valid consent per purpose, give people self-service control, and make it the authoritative signal everywhere.
Sec. 5, 6, 9
Data Privacy Platform
Privacy is no longer a policy
problem. It is an engineering one.
Know where every trace of personal data lives. Capture consent that actually holds. Enforce it across every system — and prove it on demand.
- Products
- Eight on one fabric
- DPDP obligations
- 18 owned, no gap column
- Regimes
- DPDP · GDPR · CCPA · LGPD · PIPEDA
- Readiness
- Phased over 26 weeks
- Products on one shared privacy fabric
8
Products on one shared privacy fabric
- DPDP obligations owned, with no gap column
18
DPDP obligations owned, with no gap column
- Regimes on one control library — DPDP, GDPR, CCPA/CPRA, LGPD, PIPEDA
5
Regimes on one control library — DPDP, GDPR, CCPA/CPRA, LGPD, PIPEDA
What breaks today
Consent sits in a banner tool. Personal data sits in forty systems.
Nothing reconciles the two, so consent is unenforceable the moment it is given. Nobody can answer “where is this person's data?” without a manual hunt — which does not fit inside a statutory clock.
One catalogue
One catalogue of personal data, one consent record of truth, one policy engine, one audit trail.
Eight products, one fabric
A rights request, an audit and a breach notification all resolve against the same records rather than three reconstructions.
Regulation as configuration
Each regime is expressed as configuration over a shared control library. DPDP is a mapping, not a rebuild.
The platform
Eight products. One privacy fabric.
Shared beneath every product: data catalogue, identity resolution, policy engine, AI classification and an immutable evidence trail.
01
Cookie Management
Continuous discovery, classification, prior blocking and drift monitoring — not a one-time banner project.
Sec. 6(1)
02
DSAR Management
Receive, verify, fulfil and audit every access, correction, erasure and grievance request inside the statutory clock.
Sec. 11–14
03
Intelligent Data Mapper
Replace stale inventories with a live, identity-resolved map of every place personal data actually lives.
Sec. 8(3), 8(7)
04
Data Anonymization & Masking
Keep data usable for analytics, testing and support while the individual behind it stops being exposed.
Sec. 8(4), 8(5)
05
PIA / DPIA Assessment
Find and price privacy risk at design time, and keep a defensible assessment record the auditor can read.
Sec. 10(2)
06
Data Breach Management
From detection to defensible intimation and closure — a structured workflow that beats the regulatory clock.
Sec. 8(6)
07
Audit & Evidence Management
Prove compliance from evidence rather than assert it from policy, at any depth, on demand.
Sec. 10(2)(b)
08
Privacy Program Governance
Run the whole privacy programme from one control plane, so the next regulation lands as configuration.
Sec. 4, 7, 10, 16
Worked example · Sec. 6(4)–(6)
One withdrawal, four products, a complete evidence chain
A single user action fires four products in sequence, and each hop is written to the trail.
T + 0s
Withdrawal captured
Consent Management records the withdrawal against the specific purpose and stamps it. Click-parity is enforced against the original give-flow.
Consent Management
T + 1s
Purpose revoked
The policy engine revokes the purpose and fans the event out to every processor that inherited that consent.
Privacy Program Governance
T + 2s
Stores located
Discovery returns every store holding that Principal's data; erasure executes against the list.
Intelligent Data Mapper
T + 3s
Evidence closed
Audit & Evidence Management closes the chain — withdrawal, cessation, erasure and processor acknowledgements, all timestamped.
Audit & Evidence
Without a shared fabric
The withdrawal lands in a banner tool. A ticket is raised. Someone emails four system owners. Two reply. Nobody can evidence cessation, and the erasure obligation quietly lapses.
With the fabric
Four seconds, four products, zero tickets — and an evidence chain that answers the Board’s question before it is asked.
Client value
Replace disconnected tools with one operating model
| Before · point tools and tickets | With one privacy fabric |
|---|---|
| Manual inventories and spreadsheets that go stale between releases | Continuous automated scans with drift detection on every change |
| Static, one-size-fits-all banners that ignore purpose and region | Adaptive consent by region, purpose, channel and age band |
| Siloed preferences with no enforcement past the banner | Real-time orchestration with an acknowledgement from every consumer |
| Evidence assembled after the fact, when the auditor is already waiting | Always-on searchable audit trail and board-ready dashboards |
| Incident response run over email threads and a shared spreadsheet | Structured assess, notify and remediate with the clock tracked |
| Every new law is a new vendor, a new project and a new budget | New regime maps onto controls that already run — configuration |
DPDP is not a project. It is a configuration.
The question is not whether you can comply with DPDP — it is whether the thing you build for DPDP still works when the next law lands.