Short answer: pick the partner that reads your systems, ties every finding to a section of the Act or a Rule, names who gives the legal opinion, and builds the fixes. Be wary of anyone who sells a "DPDP certificate". As of 20 November 2026 there is no government list of approved DPDP consultants, no qualification rules for them, and no official certificate. You cannot choose from a register, so you have to test the people you talk to. This post gives 14 questions to ask, what a good answer sounds like, and the red flags. It also covers the other choice you face first: software, a consultant, or doing it yourself.
The core duties under the Digital Personal Data Protection Act, 2023 start on 13 May 2027. A partner chosen well saves months. A partner chosen on a polished deck can leave you with a folder of policies and the same unlisted systems you started with. This is an engineering view, not legal advice.
Is there an approved list of DPDP consultants in India?
No. On our reading of the Act and the Rules as notified, none of these exists:
- A list of approved or empanelled DPDP consultants or auditors. The Act and Rules name none. CERT-In keeps a panel of information security auditors, but that is for security audits and the DPDP texts do not refer to it.
- A DPDP compliance certificate. Nothing in the Act or Rules creates one, or a body to issue it. Our post on the DPDP compliance certificate explains what buyers can ask for instead.
- Qualification rules. There is no degree, licence or accreditation a DPDP consultant must hold.
- A definition of "independent". The only audit the law requires is the independent data auditor of a Significant Data Fiduciary (Section 10(2)(b), Rule 13), and only if the Government designates your company. No company has been designated as of 20 November 2026.
So anyone can call themselves a DPDP expert. That is why the questions below matter more than the logo on the pitch. For the roles that do exist, see who can do a DPDP audit in India.
DPDP compliance software, a consultant, or building it yourself?

Decide this before you shortlist anyone. The three options do different jobs, and many companies need a mix.
| Option | What it does well | What it cannot do | It fits when |
|---|---|---|---|
| Software tool | What it does well: Scans connected data stores, records consent, tracks rights requests, keeps dashboards | What it cannot do: See systems it is not connected to. Decide your legal basis. Judge a vendor contract. Change your code | It fits when: You already know your gaps and need to run one job at scale |
| Engineering-led consultant | What it does well: Finds the facts across systems, ties gaps to the Act and Rules, builds the fixes, and flags legal questions for a lawyer | What it cannot do: Replace your lawyer. Issue a certificate. Work without access to your systems | It fits when: You do not know where personal data is, or you lack engineering time to fix it |
| Build it yourself | What it does well: Uses people who know your systems. No outside cost | What it cannot do: Give an independent view. Free your roadmap. Fill gaps in DPDP knowledge | It fits when: You have a named owner, spare engineering capacity and a lawyer on call |
Two rules of thumb. First, a tool needs someone to read its output and act on it, so "we bought software" is not a plan. Second, a consultant who only writes policies has not touched the part that fails: consent logs, withdrawal across systems, erasure jobs, access control, logs, breach steps. The Rule 6 checklist lists what those safeguards look like in systems. If you are still comparing platforms against consultants for AI governance, see compliance platform vs consultant.
When is a DPDP data discovery tool enough, and when do you need a service?
Data discovery is the first job in any DPDP project, and the one buyers most often try to solve with a tool. A discovery tool connects to databases, warehouses and storage, and flags columns that look like personal data. That is useful. It answers one question: where is personal data in the systems I connected?
The Act asks more. For each use of personal data you need the purpose, the notice and consent or other basis, who else receives it, how long you keep it and how it is erased. A scan does not tell you why a column exists, whether anyone consented to it, or which vendor also holds a copy.
| Software alone may be enough if | You need a service or a skilled reviewer if |
|---|---|
| Personal data sits in a small number of well-known databases and storage buckets the tool can connect to | You need a service or a skilled reviewer if: Data also lives in spreadsheets, support attachments, chat exports, logs, mobile SDKs and the AI tools staff use |
| Someone on your team will review every finding and record the purpose and basis | You need a service or a skilled reviewer if: Nobody owns the data map, or the people who know the systems have left |
| You are building the first inventory, to be checked later by a person | You need a service or a skilled reviewer if: Vendors and processors hold copies you cannot scan, so you must read contracts and settings |
| The goal is an inventory, not proof for a buyer, investor or regulator | You need a service or a skilled reviewer if: You must show a customer or lender how each flow was found and checked |
In short, a tool finds data and a person decides what it means. Our post on why DPDP starts with a data map shows the fields a useful map holds, and they go well beyond column names.
What are the 14 questions to ask a DPDP compliance partner?

Use these on every shortlisted firm, including us. The questions run from how they work, to what you get, to who signs off, to what happens after. Good answers are specific. Weak answers are about "comprehensive frameworks".
Method: how do they find out what your systems do?
- 1. Which systems will you look at? Good: a list that names your databases, cloud accounts, apps, logs, vendors and AI tools. Red flag: "your main application" with nothing said about vendors, mobile SDKs or AI tools.
- 2. Will you read configs, schemas and code, or work from interviews? Good: they read the actual settings and trace personal data from collection to deletion. Red flag: a questionnaire sent to your team, and a report built from the answers.
- 3. Who does the work, and can I meet them? Good: named engineers who will be on your systems, and a short call with them before you sign. Red flag: seniors pitch, then the work goes to people you never meet.
- 4. Is each finding tied to a section or Rule, with the evidence that would close it? Good: "No record of withdrawal reaching the analytics vendor. Section 6(6). Close with a withdrawal log entry." Red flag: findings rated "high, medium, low" with no reference to the law.
Output: what do you get, and can you show it to others?
- 5. What files will I have at the end? Good: a data map, a gap register, an evidence list, an ordered fix list and a list of questions for your lawyer. Our post on what a DPDP technical audit delivers shows a sample of each. Red flag: one long report and a slide deck.
- 6. Do you offer a DPDP certificate or a "DPDP certified" badge? Good: "No. The law does not create one. We give you evidence." Red flag: any yes. A private badge is the firm's own mark. It is not a regulator's approval.
- 7. Can the output go to a customer, investor or lender? A buyer, investor or lender may ask what you hold and how you protect it. Good: the evidence is organised so you can hand over what each audience needs, such as processor terms, logs and deletion records. Red flag: a document marked internal, with no way to extract the parts a buyer will accept.
- 8. How will you treat our AI tools and our vendors? Under Section 8(1) you stay responsible for personal data your processors handle, and Section 8(2) needs a valid contract. Good: AI tools and processors are in scope by default, with a check on what each receives. Red flag: "AI is out of scope for DPDP." Staff may be pasting customer data into chat tools already.
Legal: who answers the legal questions?
- 9. Who gives the legal opinion, and will it be in writing? Good: a named law firm or lawyer reviews the flagged items and signs a written view. At Mono, engineers do the technical work and a partner law firm reviews it. Red flag: an engineering firm that tells you what the law requires, or a law firm that has never looked at your systems.
- 10. How do you keep finding gaps separate from signing them off? Good: a different person or firm checks the work. If you may be designated a Significant Data Fiduciary, independence matters more, since Section 10(2)(b) requires an independent data auditor. A firm that designed or built your controls should not also audit them as the independent auditor. Red flag: the same team finds the gaps, closes them and declares you compliant.
Delivery: will anything actually change in your systems?
- 11. Will you build the fixes, or hand over a report? Good: they can build or review the consent log, withdrawal flow, rights-request workflow, erasure jobs, access controls, logs and breach runbook, or they clearly say they will not and work with your team. Red flag: a report that says "implement a consent mechanism" and stops.
- 12. What dates do you work to, and what is still undecided? Test their knowledge. Rule 4 on Consent Managers has been in force since 13 November 2026. The core duties start on 13 May 2027. Rule 7 asks for a detailed breach report to the Board within 72 hours, and CERT-In asks for reports within 6 hours. As of 20 November 2026 no Significant Data Fiduciary is designated. Good: they separate what is law, what is unsettled and what is a guess. Red flag: dates from the January 2025 draft Rules, or scare talk about penalties that does not match the Act.
Terms: what do you give them, and what do you keep?
- 13. What access do you need, and how will you handle our data? A partner may touch personal data while testing, which can make it your processor, so Section 8(2) needs a contract. Good: read-only access where possible, test or masked data, a short access period, and written terms. Red flag: "just send us a database dump."
- 14. What does the price cover, and what do we own afterwards? Good: a written scope, what is excluded, how new findings are priced, and that you keep the data map, registers and code. Red flag: a price tied to the deadline, a lock-in on a proprietary dashboard, or no handover. Ask for the price per deliverable so you can compare firms.
What red flags should end a conversation early?
- A promise that you will be "fully compliant" or "certified" by a date.
- No named lawyer, or legal advice from people who are not lawyers.
- A fixed price quoted before anyone has seen your systems or your vendor list.
- Deliverables made of policies and templates, with no system changes or evidence.
- No answer to "what will you not do?" Every honest firm has limits.
Which route fits which company?
| Your situation | A sensible route |
|---|---|
| Early-stage company, few systems, one engineer with time | A sensible route: Run the DPDP self-check, build the basics yourself and pay for one legal review of the flagged items |
| B2B SaaS with customers already asking security and privacy questions | A sensible route: A technical gap assessment, then fixes, then evidence you can send to buyers |
| Many data stores, many teams, a regulated sector | A sensible route: A consultant for scope and legal flags, plus tools for discovery and consent at scale |
| You expect designation as a Significant Data Fiduciary | A sensible route: Ask your lawyers early. Use a separate independent data auditor from the firm that builds your controls |
Where does a gap assessment fit in the choice?
A short, scoped DPDP gap assessment is a good way to test a partner. You see the method, the quality of the findings and the files before you commit to a larger build. If a firm will not scope a small first step, that tells you something too.
Judge us on the same 14 questions. We do not issue certificates, and we are not a law firm. We check your systems, and our partner law firm reviews the items that are legal questions.
This article is general information, not legal advice. Whether a duty applies to you, and how, is a question for your lawyers.
Sources: Digital Personal Data Protection Act, 2023, Sections 6, 8 and 10. Digital Personal Data Protection Rules, 2025, Rules 4, 6, 7 and 13 (G.S.R. 846(E), Gazette of India, 13 November 2025), and the dates in Rule 1. Data Protection Board of India portal (dpbi.gov.in). CERT-In incident reporting directions. Last reviewed 20 November 2026.
FAQ
Is there a government list of approved DPDP consultants in India?
No. As of 20 November 2026 the DPDP Act and Rules do not set up an approved or empanelled list of consultants or auditors, set no qualification rules, and create no compliance certificate. Choose by testing method, evidence, who gives the legal opinion and what you own afterwards.
Should I buy DPDP compliance software or hire a consultant?
It depends on what you already know. Software suits a job you have already scoped, such as consent capture or request tracking at scale. A consultant suits the earlier job: finding where personal data sits, tying gaps to the Act and Rules, and building the fixes. Many companies use both, and software still needs someone to act on its output.
When is a data discovery tool enough for DPDP?
A tool can be enough when personal data sits in a few well-known stores it can connect to, and someone on your team reviews every finding and records the purpose and basis. It is not enough when data also sits in spreadsheets, support files, logs, SDKs, vendors and AI tools, or when you must show others how each flow was checked.
Can one firm do the audit and the implementation?
Yes, many do, and it can save time. Ask how they keep finding gaps separate from signing them off. If you are designated a Significant Data Fiduciary, Section 10(2)(b) requires an independent data auditor, and a firm that built your controls should not also be that auditor.
Do I need a law firm as well as a technical partner?
The Act does not require you to hire one, but some questions are legal: your role, the basis for each use of data, exemptions and contract terms. A good technical partner finds the facts and flags those questions, and a named lawyer or law firm answers them in writing.
