Rule 4 of the DPDP Rules, 2025 starts on 13 November 2026, and with it the route to becoming a registered Consent Manager. There is one awkward fact. In our check on 10 November, we could not find a published application form or portal. The Rule says the Board will specify what an application needs on its own website.
So, the useful work this week is preparation. Here is what the law already settles, the order to do things in, and where applicants tend to come unstuck.
Quick answer: To register as a Consent Manager, a company incorporated in India that meets Part A of the First Schedule applies to the Data Protection Board with the particulars the Board specifies on its website. The Board may inquire, then registers the applicant or rejects it with reasons. Rule 4 sets no decision deadline.
Part A: what you must show
Section 6(9) of the DPDP Act, 2023 says every Consent Manager must be registered with the Board, subject to prescribed technical, operational, financial and other conditions. Those conditions sit in Part A of the First Schedule to the Rules, and Rule 4(1) lets a person who meets them apply. PIB’s note on the notified Rules sums up the first one: Consent Managers must be companies based in India. The left column below is the Schedule. The right column is our suggestion for evidence, since the Board has not yet listed its own. For the wider legal picture, see our explainer on the Consent Manager under the DPDP Act.
Part A condition
Evidence to gather (our suggestion)
Company incorporated in India
Certificate of incorporation, memorandum and articles
Technical, operational and financial capacity
Architecture note, staffing plan, funded budget
Sound finances and management
Audited financial statements
Net worth of at least ₹2 crore
Audited balance sheet plus a CA’s working
Adequate business volume, capital structure, earning prospects
Business plan, cap table, projections
Fairness and integrity of directors, key managerial personnel, senior management
Declarations and verification records
Articles require adherence to Part B items 9 and 10, amendable only with Board approval
Independent certification of the platform against the Board’s published standards
Certifier’s report (standards not yet seen)
Part A conditions mapped to the evidence an applicant can start gathering now.
Seven steps, in order
Test the basics first. Indian company, ₹2 crore net worth, clean management record. If any of these fails, nothing else matters yet.
Amend your articles before you file. Part A requires them to bind you to Part B items 9 and 10 (conflicts of interest), and later changes need Board approval. Get the wording right now, while it is still free to change.
Design to Part B. The platform must keep data contents unreadable to you, store consent and notice records for at least seven years, and give users access to them. Our 13 November explainer lists the Part B duties.
Plan the certification but wait for the standards. The certificate must be against standards and an assurance framework the Board publishes. Part A does not name ISO 27001 or SOC 2. They help as supporting evidence, not as a substitute.
Assemble the pack. Use the table above, then compare it with the Board’s list the day it appears.
File as the Board directs. Rule 4(1) points to the Board’s website for the particulars, information and documents required.
Answer the inquiry. The Board may ask for more. Reply fast and in writing.
The seven steps in order. Amend the articles before you file.
Net worth: where startups slip
Part A says net worth of not less than ₹2 crore. How to count it is where applicants slip, and our guide to the ₹2 crore net worth test works through what counts. Settle the basis with your CA and check the Board’s particulars.
Here is the trap, using a hypothetical company. A startup has raised ₹3 crore, so it feels comfortable. But it has booked ₹2.2 crore of accumulated losses. Its net worth is ₹0.8 crore, well short. Funding rounds do not help if the losses keep eating the balance sheet. Work the number from audited accounts, not from the bank balance.
What the Board can do after you apply
Run whatever inquiry it considers appropriate and ask you for information (Rule 4(2) and 4(6)).
Register you and publish your particulars on its website or reject you and give reasons.
After a hearing, direct you to fix a breach of conditions or obligations (Rule 4(4)).
Suspend or cancel registration by a reasoned order where that protects Data Principals (Rule 4(5)).
On an intimation of breach of a registration condition, inquire and impose a penalty under Section 27(1)(d) of the Act.
What Rule 4 lets the Board do once you have applied.
Buying a generic security certificate before the Board’s standards exist.
Forgetting that promoters and every shareholder above two per cent must be disclosed once you are registered.
Treating registration as the finish line. Audits and Board reporting follow.
Where RuleExpert fits
RuleExpert is not a registered Consent Manager, and it cannot file, certify or guarantee an application. If you are applying, one practical use is the evidence pack. RuleExpert describes its audit-ready documentation as a central evidence repository with activity logs and version history. Ask on a demo whether that suits your pack. If you are a business that will use Consent Managers rather than become one, the consent module and the free DPDP Scorecard are the better start. Book a RuleExpert Demo or see our DPDP compliance solution overview. Software supports the work. Legal advice is separate.
Frequently asked questions
How do I register as a Consent Manager under the DPDP Act?
Apply to the Data Protection Board under Rule 4(1) if you meet Part A of the First Schedule, filing the particulars and documents the Board specifies on its website. The Board may inquire, then registers you or rejects you with reasons.
When can I apply?
Rule 4 is scheduled to start on 13 November 2026, though some sources say 14 November. PIB’s own releases give both 13 and 14 November 2025 as the notification date, so confirm the commencement wording in Rule 1 of the Gazette notification. The application particulars depend on the Board publishing them.
Who is eligible to register?
A company incorporated in India that meets all nine Part A conditions, including capacity, sound finances, net worth, management integrity, binding articles and independent certification.
Rule 4 mentions none, and we found no fee published. The Board specifies application particulars on its website, so check there before budgeting.
How long does registration take?
No one can say yet. Rule 4 sets no deadline for the Board’s inquiry or decision. Plan for uncertainty and avoid fixed launch promises.
What documents will I need?
The Board decides. Expect incorporation papers, audited financials, platform architecture, governance documents and the certification report. The evidence table above is a sensible starting set.
What does independent certification involve?
Part A requires a certificate that your platform meets the data protection standards and assurance framework the Board publishes, and that your controls support Part B. We have not seen those standards yet.
Can the Board reject or cancel my registration?
Yes. Under Rule 4 it can reject with reasons at the start, and later direct fixes or suspend or cancel after a hearing, by a reasoned order. Section 27(1)(d) of the Act also lets it inquire into a breach of registration conditions and impose a penalty.
Can a company that is also a Data Fiduciary become a Consent Manager?
Part A does not bar it by name, but Part B requires avoiding conflicts of interest with Data Fiduciaries. Take legal advice. The complete guide to DPDP in India explains the roles.
I am a Compliance Manager at RuleExpert, focused on helping organizations navigate the evolving landscape of data protection and privacy regulations in India.
With the introduction of the Digital Personal Data Protection (DPDP) Act, businesses are facing new challenges in managing personal data, ensuring consent, and maintaining compliance across systems. My work revolves around simplifying these complexities and enabling organizations to adopt structured, scalable compliance practices.
I specialize in:
DPDP compliance and privacy frameworks
Data governance and risk management
Consent lifecycle and user rights handling
Compliance automation and operational workflows
At RuleExpert, I work closely with startups, SaaS companies, and enterprises to transform compliance from a manual, documentation-heavy process into an automated, infrastructure-driven system.
I am particularly interested in how AI and automation can reshape privacy operations and help businesses build trust in a data-driven world.
In their words
What compliance teams tell us
“We always thought DPDP compliance was the client’s responsibility
since we were only executing services. The evaluation made it clear that how we handle
client data creates risk on our side too. It changed how we work internally.”
DSFounderDigital services firm
“We had a basic understanding of DPDP requirements, but the scorecard
highlighted gaps we hadn’t identified internally — especially around consent handling
and data visibility. It gave us a much clearer starting point.”
BSFounderB2B SaaS company
“The DPDP score was surprisingly insightful. Within minutes we could see
where we stood and what needed immediate attention. It simplified something that initially
felt quite complex.”
FPProduct HeadFintech platform
“After reviewing our score we opted for a consultation. The discussion was
very practical — we got clear direction on what to fix first and how to approach DPDP
compliance in a structured way.”
LGFounderLogistics company
Real client quotes, attributed by role and sector — we never name a client.
Enquiry
Talk to the team
Your enquiry is with the team
Thank you — we have it. Someone will reply by email, usually within one working day.
Nothing else is needed from you. If it is urgent, email
tushar@ruleexpert.com and it will reach the same
people.
Allowing it lets Google Analytics and Google’s advertising measurement set an
identifier and receive your IP address, the pages you view and how you reached them
— used only to see which pages work and whether a campaign led to an enquiry, never to
build a profile or to decide anything about you. Google processes this outside India, a
cross-border transfer under Section 16. Declining changes nothing about the site, and you
can change your mind any time from the footer.
An analytics identifier is personal data, so the DPDP Act applies to
it — though no Indian cookie statute requires this banner. We ask because we would
rather you chose. What we collect and why