Self-assessment
Fourteen working assessments
One page per part of a data-protection programme. Each starts with a twelve-question self-assessment across four sections, scores you against four readiness bands, and hands you a template to run the work.
Finding out where you stand: the gap assessment
Before you fix anything, find out where you stand. A gap assessment compares how your enterprise actually handles personal data today against what the DPDP Act and Rules expect, and ends in a prioritised, evidence-backed fix list. Most DPDP obligations are not yet in force, which is exactly why this is the right time to assess: you can still fix things in the order you choose, instead of the order a deadline forces on you. The dates and timeline page carries the verified dates.
Open the assessmentMaking data protection someone's job: governance and the DPO office
Programmes fail quietly when nobody owns them. Governance is the structure that makes data protection somebody's job: a Data Protection Officer function with real authority, and the working apparatus around it. This page helps you test whether your governance is real or decoration, and build the pieces that are missing.
Open the assessmentPolicies, notices and consent: the paper and the machinery of permission
Consent is the part of data protection most likely to be tested by a real dispute, and the part where implementations quietly fail. In a dispute, the first question is "show me what the person was told". This page helps you test whether your notices and consent journeys would survive that question, on every channel you run.
Open the assessmentAnswering people: data principal rights and grievance redressal
People can ask you what data you hold on them, ask you to correct or erase it, withdraw consent, and complain when they are not heard. Rights requests are the part of the law the public actually touches. A working process turns a potential complaint to the Data Protection Board into a closed ticket, with the evidence to show it was handled. The duties attach once the relevant provisions commence; the dates and timeline page carries the verified position.
Open the assessmentThe record of processing and the impact assessment
Two linked instruments sit at the centre of a data protection programme: the record of processing activities, the living register of what you do with personal data, and the Data Protection Impact Assessment, the structured thinking you do before processing that could harm people. If the register is wrong, everything built on it is wrong.
Open the assessmentKnow your data: discovery, classification and mapping
You cannot protect data you have not found. Notices, consent, rights requests, breach response, retention, audits: every one of them starts from a single question. What personal data do we actually hold, and where.
Open the assessmentPreparing for a personal data breach
When personal data is breached, the reporting clocks are short and unforgiving, and they start when the incident starts, not when you find the plan. In an incident, the hard part is not the filing; it is knowing fast enough what happened, whom it affects and which clocks started.
Open the assessmentEveryone else who touches your data: third-party and vendor risk
You remain responsible for personal data in your vendors' hands, in law and in reputation. Processors, outsourced providers and partners handle your customers' data every day, and the Act binds you, the data fiduciary, not them. Vendor risk is governed, not hoped away: a register, the contracts, working consent enforcement at partners, and evidence the ecosystem behaves.
Open the assessmentHow long data stays, how it goes, and where it lives
Data that is deleted on time cannot leak, cannot be breached and does not inflate your audit effort. This page covers three connected disciplines: deciding how long personal data stays (retention), actually deleting it when time is up (erasure), and controlling where in the world it sits (localisation).
Open the assessmentSecurity controls that make protection real
The DPDP Act requires reasonable security safeguards for personal data, and failure here carries the highest penalty class in the Act's Schedule. But safeguards only count when they are technical fact, with test evidence, not policy language on a wall.
Open the assessmentMaking privacy work inside your systems
Integration is where privacy programmes quietly fail: consent captured on the website that never reaches the marketing platform, a deletion request that cannot reach the backup policy. Privacy tooling has to execute inside your real estate, not beside it. When consent changes, the change must reach every system that acts on it. When a right is exercised, the request must reach the systems where the data lives. When retention ends, deletion must reach archives and backups.
Open the assessmentTraining the people who touch personal data
Systems do not leak data on their own; people using systems do. Training is the cheapest control with the widest reach, and its completion records are audit evidence that the enterprise takes its duties seriously. Different roles carry different duties, so one generic deck for everyone does not work.
Open the assessmentSeeing it and proving it: reporting, dashboards and audit evidence
Leadership cannot govern what it cannot see, and an enterprise cannot defend what it cannot evidence. When an inspection arrives, the difference between a routine week and a crisis is whether the evidence already exists in retrievable form. Audit support means answering with records, not explanations.
Open the assessmentStaying compliant as everything changes
Compliance decays by default. New products, new vendors, new systems and new notifications erode it every quarter, quietly. Sustenance is the discipline that keeps the rest of the investment true. The gap assessment got you to a point in time; this is what keeps you there.
Open the assessmentHow scoring works
A total is a summary. A single "No" is a finding.
Yes scores 2, Partly scores 1, No scores 0. The total runs from 0 to 24. Every page uses the same four bands, so scores mean the same thing across the programme.
| Score | Band | What it means |
|---|---|---|
| 0 to 8 | Exposed | The basics are missing or undocumented. Fix the foundation before buying tools. |
| 9 to 16 | Halfway | Something works, but the weakest section decides the result. Close the named gaps. |
| 17 to 21 | Strong base | The structure exists. Prove it with evidence and rehearsal, not assertion. |
| 22 to 24 | Leading | Keep it alive as the business, vendors and systems change. |