Pick what you need. Run them together for full coverage. Each module anchors to the specific section of the Act it implements, and each has its own page covering what it does, where it breaks, and what it will not do for you.
DPDP §6 · §6(4) · §7
The full consent lifecycle: capture, store, refresh, withdraw. ProtectComply ships three surfaces — a hosted preference centre, a cookie banner, and an embeddable widget.js — all wired into the same audit trail. Per-purpose granular consent is enforced; bundled consent flags are rejected at write time. Returning-principal recognition uses a per-tenant cookie plus SHA-256 fingerprint, so an Indian user who already granted consent on the same device doesn't see the banner again. Withdrawal is offered on every capture surface and is code-verified wherever the original grant was, so it is as easy as granting — the explicit §6(4) mandate. Every record carries provenance: capture IP, user-agent, fingerprint, and principal cookie. Machine-translates notice and purpose text into the Eighth Schedule languages.
Highlights
DPDP §5(3) · 8(1)
A 33-document catalogue across ten groups — Privacy Notice, Consent Management, Data Retention & Deletion, Breach Response, Data Processing Addendum, Children's Data, and 27 more — drafted by AI from your organisation profile and the live DPDP spec. Each section records the provisions it was drafted against, so when the Act is amended (and it will be), regeneration is one click. Policies are version-controlled, signed-off by named roles, and exportable as PDF. Public publication via a hosted URL means your principals get the latest notice without you redeploying anything. Built-in AI gap analysis flags clauses that are missing or contradict the Act. Regulator response drafter pre-writes replies to common Board queries.
Highlights
DPDP §8 obligations
A free 35-question readiness check plus a deep-dive tier whose question bank is selected by your industry and by whether you act as a Data Fiduciary, a Data Processor or both — from around a hundred questions for a processor to several hundred for a fiduciary. Healthcare, fintech and real estate ship with their own specialised banks; everything else runs on the generic bank. Questions flagged as requiring evidence accept an upload, and AI validation reads the document against the exact question and the relevant sections. Per-question and per-module legal references point to the exact §s being tested. Section-level assignments push whole modules to named team members with deadlines.
Highlights
DPDP §11–§14 · Rule 14
Honours the DPDP data-principal rights — access (§11), correction and erasure (§12), grievance redressal (§13) and nomination (§14) — through five request types and a public principal-facing portal at /rights/[org]. Intake is verified with a one-time code, routing rules assign each request to a named owner in priority order, an AI response-letter drafter pre-fills a reply, and a response clock starting at verification shows what is overdue. A refusal records its reason on the request and emails that same reason to the principal in the closure notice. Every transition is written to an event timeline with its actor.
Highlights
DPDP §13 · Rule 14
Sections 8(9), 8(10) and 13 require every Fiduciary to publish a contact, run a grievance mechanism and respond within the period it publishes — no more than ninety days under Rule 14. ProtectComply gives you a principal-facing form at /grievance/[org], a per-org DPO inbox, twelve routable categories, an acknowledgement flag and a configurable resolution clock. The audit-event trail captures every state transition — submitted, acknowledged, in-review, refused-with-reason, resolved — so the grievance register is always one export away. Refusal is blocked without a written basis, and the reason stored is the reason the complainant receives. Principal satisfaction is captured post-resolution, and a dissatisfied response alerts the grievance officer.
Highlights
DPDP §8(6)
§8(6) and Rule 7 require a Data Fiduciary, on becoming aware of a breach, to intimate the Board and each affected principal without delay and to send the Board a detailed report within 72 hours. ProtectComply's breach lifecycle runs that 72-hour clock from the detection timestamp, with a structured workflow for containment and root cause. Each record moves open → contained → notifying → notified → closed, carries attached evidence and the regulator-notification reference, and cannot be closed without root-cause notes. Principal notices go out per recipient — a tenant-wide broadcast is refused — and drafts can be generated for seven audiences at once. A standing register answers the audit questions.
Highlights
DPDP §8(7) · §8(2)
Automated personal data discovery that feeds the register, rather than a catalogue someone maintains by hand. Discovery connects to eighteen source types — PostgreSQL, MySQL, SQL Server, Oracle, Db2 and managed relational instances, MongoDB, Amazon S3, Salesforce, SAP, a generic REST source, and shared filesystems and log files reached through an outbound-only on-premises agent, plus the Microsoft Purview and OpenMetadata catalogues for existing classification tags. Mailboxes are scanned separately, bodies and attachments included. Findings then propose RoPA entries: a resolver reads your declared consent purposes alongside what discovery actually found and derives the data categories, the systems the data sits in, the recipients and a suggested retention rule — so the register is built from live metadata instead of typed up, and discovered data matching no activity opens its own task rather than being quietly absorbed. Records of Processing Activities (Article 30-equivalent), data-flow diagrams, vendor / processor catalog, and a cross-module risks aggregator. RoPA entries link to the consent purposes they're collected under and the retention policy they're disposed against — so if anyone changes one, the others light up red. The vendor catalog covers due-diligence questionnaires, DPA tracking, and sub-processor disclosures (the §8(2) processor-contract and §8(5) security-safeguard obligations extend down your supply chain). Risk aggregator rolls everything up into one heatmap for the DPO's weekly review.
Highlights
DPDP §5 · §6 · §13
Point the scanner at a URL — your site or a vendor's — and it runs 56 DPDP-specific checks across 10 weighted domains: Privacy Notice, Cookie Consent & Banner, Consent Mechanism, Forms & Data Collection, Data Principal Rights, Third-Party Trackers, SSL / TLS Security, Children's Data Signals, DPO / Grievance Contact, and Cross-Border Transfer. Each finding is severity-tagged and section-anchored. The output is a scored report ranging from 0 to 100, with deltas across re-runs so you can prove improvement over time. Hub at /dashboard/scanner.
Highlights
Every plan includes the same audit trail, so you can add modules later without re-onboarding. See what each plan costs.