Why We Built DPDPA Shield Instead of Recommending OneTrust to Indian Companies
The inside story of why legacy global GRC platforms fail Indian engineering realities, and why DPDPA 2023 demanded a purpose-built, client-side compliance architecture.
When India's Digital Personal Data Protection Act (DPDPA 2023) was officially passed, the immediate impulse of many enterprise CISOs was to call their existing global vendor: OneTrust.
As cybersecurity engineers at DPDPA Shield, we spent months testing whether these global platforms could genuinely protect Indian high-growth tech companies and BFSI firms against the Act's staggering ₹250 Crore penalty thresholds.
What we discovered was deeply alarming: global enterprise privacy tools were engineered for a fundamentally different legal and architectural paradigm.
1. Generalist Scale vs. Indian Statutory Depth
OneTrust is built to satisfy 40+ diverse global regulations: GDPR in Europe, CCPA/CPRA in California, LGPD in Brazil, and PIPL in China. To accomplish this, it treats privacy as an abstract, multi-jurisdiction workflow.
Under India's DPDPA 2023, however, the statutory rules are uniquely rigorous:
- Section 9 Absolute Ban on Tracking Minors: Under Indian law, you cannot merely request consent for tracking children—tracking, behavioral monitoring, and targeted advertising to minors are unconditionally banned under threat of a ₹200 Crore fine. Global tools built on GDPR's age-of-digital-consent models simply do not have native Indian age-gating primitives.
- Section 14 Right to Nominate: India is the only major jurisdiction with a statutory Right to Nominate, allowing citizens to designate an individual to exercise their privacy rights upon death or incapacity. A generic GDPR tool has no database schema for post-mortem privacy nominees.
- 22 Constitutional Languages: Section 5 explicitly guarantees the citizen's right to access privacy notices in English or any of the 22 Eighth Schedule Indian languages. A tool with English and Hindi drop-downs fails the statutory standard.
2. The Danger of the "Point-in-Time" Data Map
In traditional enterprise GRC, data mapping is an administrative exercise. Consultants send questionnaires to department heads, hold dozens of meetings, and eventually produce a handsome PDF data map.
That map is accurate for exactly 48 hours. The moment a software engineer creates a new PostgreSQL table for a festive flash sale or connects a new analytics microservice, the compliance map silently shatters. When a breach occurs, the CISO discovers that the breached database was never on the inventory.
We realized that compliance cannot be static. It must be continuous, code-level, and automated.
3. Client-Side PII Scanner: Zero Data Exfiltration
When we evaluated cloud-based privacy scanners, our engineering team refused to accept their architecture. Most SaaS scanners ask for read access to your production database, stream table samples over the public internet to US/EU multitenant cloud servers, and run classifications abroad.
This directly violates Section 16 data sovereignty guidelines and creates a massive secondary attack vector.
That is why we built our Automated PII Scanner. The scanner runs entirely in-memory inside your private VPC or browser session. It inspects schemas, classifies Indian identifiers (Verhoeff-verified Aadhaar, PAN, UPI IDs, Driving Licenses), and never transmits a single row of raw customer data out of your boundary.
4. Dual Regulatory Clocks: The Indian Operational Reality
In India, a cybersecurity breach is governed by two simultaneous, unforgiving clocks:
- CERT-In's 6-Hour Clock: Mandatory intimation of cybersecurity incidents within 6 hours of detection.
- DPDPA's 72-Hour Clock: Mandatory statutory notification to the Data Protection Board and every affected citizen.
A generic global tool leaves your legal and engineering teams scrambling across disconnected spreadsheets. DPDPA Shield's Dual-Clock Incident Commander synchronizes both timelines the microsecond an incident is logged, generating pre-formatted regulatory intimations automatically.
Summary
We built DPDPA Shield not because we wanted another SaaS company, but because Indian founders, CISOs, and engineers deserve compliance infrastructure built for their speed, their legal reality, and their sovereign data.