Digital Personal Data Protection Act (DPDPA) of 2023

DPDP Act: What Gujarat Businesses Should Do Before 13 November 2026

November 3, 2026 Amit Patel & Associates 9 min read

DPDP Act: What Gujarat Businesses Should Do Before 13 November 2026

Why 13 November 2026 matters

On 13 November 2026, the Consent Manager framework under the Digital Personal Data Protection Rules, 2025 becomes operative, one year after the Rules were notified. It is the second of three phases that end with full compliance on 13 May 2027. For most Gujarat businesses it is not a personal deadline, but it is a clear signal: the DPDP regime is moving from paper to practice, and the clock on the 2027 obligations is already running.

This post explains what changes on 13 November, why a gap in the enforcement machinery makes that date legally interesting, and what a business holding customer data should do now rather than in April 2027. It is written for directors, in-house teams and fellow practitioners advising clients across Ahmedabad, Surat, Vadodara and Rajkot.

The three-phase timeline

The government chose staggered commencement instead of a single switch-on date. The Rules were notified on 13 November 2025 (G.S.R. 846(E)), and commentary on the notification describes an 18-month runway to substantive implementation.

Phase Date What takes effect
One 13 November 2025 Rules 1, 2 and 17 to 21, and the provisions establishing the Data Protection Board
Two 13 November 2026 Rule 4: registration and obligations of Consent Managers
Three 13 May 2027 Rules 3, 5 to 16, 22 and 23: notice, consent, security, breach reporting, children’s data, data principal rights, Significant Data Fiduciary duties

Phase three is where almost every business is affected. Some commentary quotes 12 or 14 May 2027, depending on how the 18 months is counted, so confirm the date against the Gazette notification before you advise a client on it. The King Stubb & Kasiva analysis makes a useful point: treating 13 May 2027 as the only date that matters is a mistake, because the rollout is phased and November 2026 is an important intermediate step.

What a Consent Manager is, and what Rule 4 requires

Section 2(g) of the DPDP Act defines a Consent Manager as a person registered with the Data Protection Board of India. In practice it is an intermediary that gives a data principal one accessible, interoperable place to give, review, manage and withdraw consent across many data fiduciaries. Think of it as a regulated dashboard for consent, sitting between individuals and the businesses that hold their data.

Rule 4, read with the First Schedule, sets the conditions for registration. The text of Part A and the Maheshwari & Co. analysis show that an applicant must:

  • be a company incorporated in India;
  • have sufficient technical, operational and financial capacity;
  • have a sound financial condition and management of sound general character;
  • have a net worth of at least ₹2 crore; and
  • have its platform independently certified.

The ₹2 crore floor is deliberately modest compared with other regulated intermediaries, which suggests the rule-makers expect relatively young technology companies to enter the field. Once registered, a Consent Manager carries the Part B obligations on a continuing basis. These include periodic audit reports, disclosure of its shareholding structure and prior Board approval for any change of control. An applicant must also confirm that it will not act as a data fiduciary for the personal data flowing through its platform.

One distinction will matter commercially. A statutory Consent Manager is a registered entity; a consent management platform is simply software that a business uses to collect consent. Until registration is possible, any vendor describing its product as a “DPDP-certified Consent Manager” is describing an aspiration. Your clients should ask hard questions before signing such contracts.

The Board that exists in law but not yet in fact

Here is the legal gap. Consent Managers must register with the Data Protection Board, and the Board has no members.

It would be inaccurate to say the regulator does not exist. The Board was established on 13 November 2025 under Section 18 of the Act, and Rules 17 to 21 on its constitution and procedure took effect the same day. But as a LiveLaw analysis published on 1 August 2026 put it, the Board “exists, in the strict sense, only as a statutory possibility”. MeitY invited applications for one Chairperson and four Members on 6 May 2026. One tracker found no appointment notification as of 21 September 2026, and another reported none as of early October. A Board without members cannot form a quorum, hear a party or sign an order.

The consequences are practical. Registering Consent Managers is the Board’s first operational task from 13 November. Yet one commentary notes that nobody can complete registration until the Board is operational and the technical standards for the required independent certification are published in detail. The fee structure is also not specified. So Rule 4 will be in force on 13 November, but there may be no one to receive an application.

The litigation signal

The gap has already reached the courts. According to the LiveLaw analysis, in Parth Sharma v. Union of India the Madhya Pradesh High Court’s Indore Bench considered an Article 226 challenge to Instagram’s proposed discontinuation of end-to-end encrypted messaging. The Union objected that the petitioner had not used the remedy before the Board under Section 18. The Division Bench accepted the objection, directed the petitioner to represent to the Board within seven days, and directed the Board to decide by a reasoned order within fifteen days.

That is a conventional application of the rule against bypassing an efficacious statutory remedy. Its unstated premise is that a Board capable of deciding within a fortnight exists. For practitioners, the lesson is practical: if a client’s data grievance meets an “alternate remedy” objection, argue that the forum is not yet efficacious, and ask the court to preserve a right to return if the Board does not act.

Is 13 November a deadline for my client?

Usually not. The King Stubb & Kasiva analysis notes that November 2026 is not a universal compliance deadline for every data fiduciary. The date mainly concerns entities that want to operate as Consent Managers, such as fintechs, account aggregators and technology start-ups.

The core duties on data fiduciaries, including notice, consent, security safeguards and the penalty provision in Section 33, commence only around May 2027. Until then there is little for the Board to penalise, even once it is staffed.

That is exactly why the milestone deserves attention. A client who reads “no deadline” as “no work” will meet the May 2027 date with six months of lost preparation, and the Board will begin life with a backlog of Consent Manager applications, breach intimations and complaints.

Seven steps for Gujarat businesses holding customer data

Whether the client is a textile trader in Surat, a pharma manufacturer in Ahmedabad, a hospital group, an ed-tech start-up or a lender, the same sequence applies. Use the six months between now and May 2027 for the following.

  1. Map your personal data. List what you collect, from whom, where it is stored, which vendors touch it and how long you keep it. Every later step depends on this inventory, and most clients discover data they had forgotten.
  2. Rebuild notices and consent flows. Rule 3 requires a clear notice at the time of collection. Review sign-up forms, apps, WhatsApp onboarding and paper forms, and check that consent is specific and as easy to withdraw as to give.
  3. Paper your processors. Update contracts with payroll providers, cloud hosts, marketing agencies and CRM vendors so that they carry security, breach-cooperation and deletion obligations. A fiduciary remains answerable for its processors.
  4. Prepare for breaches. Section 8(6) requires a personal data breach to be intimated to the Board. Draft an incident response plan with named owners, a logging approach and a notification template now, not during an incident.
  5. Handle children’s data deliberately. If you serve anyone under 18, from coaching classes to gaming and retail, plan for verifiable parental consent and age-gating.
  6. Check whether you could be a Significant Data Fiduciary. Large volumes or sensitive categories of data attract additional duties, including impact assessments and audits. Establish early whether the designation could apply to you.
  7. Decide your consent-management approach, and verify claims. You may eventually route consent through a registered Consent Manager, or run your own platform. In either case, do not rely on any vendor’s “DPDP-certified” label until registration is actually possible.

A board-level owner and a grievance contact should sit above all seven steps. Regulators and courts will first ask who was responsible, and a named person is the simplest answer.

Penalties, challenges and the cost of waiting

Sections 27 and 33 of the Act empower the Board to inquire into non-compliance and impose penalties of up to ₹250 crore. That ceiling gets the headlines, but the realistic early risk for a mid-sized business is a data breach that must be reported to a Board with a backlog and no track record. Early enforcement is likely to be breach-driven, and a client with no logging, no processor contracts and no named owner will have little to show.

Commentary also refers to constitutional challenges to the DPDP framework before the Supreme Court, and the King Stubb & Kasiva article on consent managers lists them among the sources of legal uncertainty. Check the current status of those proceedings before relying on them in advice. A pending challenge is not a stay, and a prudent client should not plan on one.

The cost of waiting is therefore asymmetric. Early preparation costs some legal and engineering time. Late preparation costs a compressed project, rushed vendor negotiations and a first breach handled without a plan.

Conclusion

The 13 November milestone is quiet on its face and revealing in substance. It brings Rule 4 into force while the body that must register Consent Managers still has no members, which shows how much of the DPDP framework depends on institutions that are not yet running. That should not tempt anyone to wait. The obligations that matter to ordinary businesses arrive on 13 May 2027, and the work behind them, from data mapping to processor contracts and breach plans, takes months.

If you hold customer data in Gujarat, use November as your cue. Start the inventory this month, fix your notices and vendor contracts by the new year, and treat the Board’s eventual appointments as the start of enforcement, not the start of preparation.

This post is general information on a fast-moving subject, not legal advice. Please confirm dates and the status of the Board against the Gazette and MeitY notifications before acting.

 

Need Legal Assistance?

If you need help with legal matters, our experienced team can guide you through the process and protect your rights.

Contact Us
Call Us For Consultation