DPDP Removal of Difficulties Order, 2026: What Changed on 5 October, What Did Not, and a Rollout Plan for Small Businesses
General | RegisCorp Team

Reviewed by Indrajeet Sharma, Founder, RegisCorp Consultancy LLP.
Information current as on 18 November 2026. First written for the 5 October 2026 daily post and re-checked on 18 November 2026.
Picture a small online tutoring business run by two people from a spare room. They have a website, a sign-up form, a payment gateway, a WhatsApp number for parents, and a spreadsheet with the names, phone numbers and school grades of about eight hundred students. One evening a friend forwards a headline: "Government issues DPDP Order on consent and data audits." The founders feel a small jolt of panic. Is there a new rule? Do they now need an audit? Is the penalty really two hundred and fifty crore rupees?
This article is for that moment. On 5 October 2026 the Ministry of Electronics and Information Technology (MeitY) made the Digital Personal Data Protection (Removal of Difficulties) Order, 2026. The headlines made it sound like a big new compliance burden. When we read what the law firms and legal news portals reported about the Order, the picture was much smaller and much calmer. The Order corrects the wording of two provisions of the Digital Personal Data Protection Act, 2023. It does not add a new duty, does not change the Digital Personal Data Protection Rules, 2025, and does not move any deadline.
That is good news, but it is not a reason to relax. The real work for a business that collects customer data is still ahead, and the real date to plan around is 13 May 2027. This article does three things. First, it tells you exactly what the Order says, what we could confirm and what we could not. Second, it recaps the duties under the Act and the Rules that matter for a small business, using the correct dates and penalty ceilings. Third, and most important, it gives you a practical rollout plan that you can start this week and finish well before the main obligations begin. We have written it for founders, freelancers, clinics, coaching centres, online sellers and small professional firms, not for lawyers.
A note about our older article. RegisCorp already has a general explainer titled "DPDP Act compliance for small business India 2026". This article does not repeat that general explanation. It is focused on the 5 October Order, on what changed, and on a rollout plan. Where the Act or Rules need a short recap so that the Order makes sense, we give one, and we keep it short.
The short answer
If you have two minutes, this is what you need.
- What the Order is. A Removal of Difficulties Order made by MeitY on 5 October 2026 under Section 43(1) of the DPDP Act, 2023. Section 43 lets the Central Government issue an order, consistent with the Act, to remove a difficulty in giving effect to the Act.
- What it changes. Two small textual corrections. In Section 9(1), the words "a child or a person with disability" become "a child or of a person with disability" (the word "of" is added). In Section 10(2)(c)(ii), the words "periodic audit" become "periodic data audit."
- What it does not change. The consent duty for children's data, the guardian consent duty for persons with disability, the independent auditor requirement for Significant Data Fiduciaries, the DPDP Rules, the penalty amounts, and the commencement dates. Reports by several law firms describe the Order as editorial or textual and say it adds no new substantive obligation.
- The date that matters. Under the commencement notification for the Act and the Rules, most duties for a typical business, including notice, consent, security safeguards, breach intimation, children's data and the rights of individuals, start on 13 May 2027. A MeitY press release of 14 November 2026 repeats that date for the rights, fiduciary duties and the Board's inquiry and penalty processes.
- The penalty ceiling. The Schedule to the Act sets maximum penalties, the highest being up to Rs 250 crore for failing to take reasonable security safeguards. These are ceilings for the worst cases, not standard fines.
- What to do. Treat the Order as a reminder, not an emergency. Use the next six months to map your data, fix your consent notices, tidy your vendor contracts, write a breach plan, and be ready for requests from customers. The plan in this article shows how.
What we confirmed about the Order, and what we could not
A responsible article about a government order should be clear about its own evidence. Here is how we approached it.
We tried to read the Order in its original form. The reports we reviewed link to a copy on the e-Gazette portal. When we tried to open that file from our research tools, the portal refused automated access, so we could not read the Gazette PDF ourselves. We also did not obtain a MeitY web page carrying the Order text. What we did read were reports from several independent sources: a legal news portal (SCC Online blog, 15 October 2026), a business-information portal (India Briefing), a law-firm article on Mondaq, a law-firm article from King Stubb and Kasiva, a Chambers and Partners article, and a Lexorbis article. They agree on the substance of the Order, and the Mondaq article quotes the substituted phrases directly.
Here is what is consistent across those reports.
- Name. Digital Personal Data Protection (Removal of Difficulties) Order, 2026, issued by MeitY.
- Date of the Order. 5 October 2026.
- Power used. Section 43(1) of the DPDP Act, 2023.
- Change one. Section 9(1): "child or a person with disability" becomes "child or of a person with disability."
- Change two. Section 10(2)(c)(ii): "audit" becomes "data audit," so the clause reads "periodic data audit."
- Nature of the change. Described as editorial or textual. The Mondaq article reports that the recitals of the Order call the difficulties "textual, editorial in nature."
- No change to the Rules. The Mondaq article states that the Order does not amend the DPDP Rules, 2025.
Here is what the reports do not agree on, or do not say. We flag these so that you do not repeat them as facts.
- Notification number. One article (Mondaq) gives it as S.O. 5458(E), Gazette of India, Extraordinary, Part II, Section 3(ii), No. 5248, dated 6 October 2026. The other reports we read do not state a number. Because we could not read the Gazette copy, treat this number as reported by one source and unverified by us.
- Date of Gazette publication. The Lexorbis article says the Order was published in the Official Gazette on 6 October 2026. The India Briefing article says 7 October 2026. The Mondaq article gives a Gazette date line of 6 October 2026. Reports therefore differ by a day, and we could not settle it from the Gazette itself.
- Date from which the Order has effect. Several articles say the Order takes effect from the date of its publication in the Official Gazette. The SCC Online article says it came into effect on 6 October 2026. The India Briefing article says the Order took effect on publication but also gives a table line saying the amendments "apply from 5 October 2026," and does not reconcile the two. For a business, this one-day difference does not matter, because the provisions that were corrected are not yet in force (see below).
- When Sections 9 and 10 begin. The India Briefing article says "13 March 2027." The commencement notification and every other source we checked, including a press release of the Press Information Bureau (PIB) on 14 November 2026 about the later phase, point to 13 May 2027. We think the "March" in that one article is a typing error, but we are flagging it plainly instead of silently correcting it. Please use 13 May 2027 and check the notification for yourself.
In short: the content of the Order is well supported, while its number and exact gazette day are not confirmed by us from the original. If you need the Order for a legal filing or a contract, download it from the e-Gazette portal or MeitY and cite the number printed on it.
Why the Order was needed: what is a "Removal of Difficulties" Order?
Many Indian laws contain a clause that lets the government clear up a drafting problem during the early years of a law, without going back to Parliament. For the DPDP Act, that clause is Section 43. In plain words, it says that if any difficulty arises in giving effect to the provisions of the Act, the Central Government may, by a Gazette order consistent with the Act, do what is necessary to remove it. The version of the Act we read also says that no such order can be made after a limited number of years from the Act's commencement (three years, as we read the India Code copy through our research tool), and that every such order must be laid before both Houses of Parliament.
Two things follow. First, a Removal of Difficulties Order is a tool for fixing problems in how a law works, not for creating new obligations. If it tried to do that, it would be open to challenge for going beyond Section 43. Second, such orders are usually small and technical. They fix a missing word, a clashing cross-reference, or an unclear sentence. This Order is exactly that kind.
Why did these two sentences need fixing?
Section 9(1). The Act's text was read by commentators as saying that a Data Fiduciary must obtain verifiable consent of the parent or lawful guardian before processing any personal data "of a child or a person with disability who has a lawful guardian." Without the second "of", a reader could ask whether "who has a lawful guardian" applies only to the person with disability, or to the child as well. That is a grammar problem with legal consequences. It would affect, for example, whether a child's data can be processed on the strength of a guardian-consent rule written for persons with disability. The corrected wording, "a child or of a person with disability", makes it clear that these are two separate categories of people whose data needs guardian consent: children, and persons with disability who have a lawful guardian. Commentators describe this as a clarification and not a new category.
Section 10(2)(c)(ii). Section 10 deals with Significant Data Fiduciaries, a special class of larger or riskier data fiduciaries that the Central Government may designate. Section 10(2)(b) requires them to appoint an independent data auditor "to carry out data audit." Section 10(2)(c) lists other measures, including a periodic assessment of the impact on data protection and a periodic audit. The word "audit" on its own is a general word that could be read as a financial audit or an internal audit. The Order replaces it with "data audit," so that the clause matches Section 10(2)(b) and plainly refers to an audit of data protection and processing compliance. Law-firm commentary says the recitals describe the intended meaning as a "data protection audit" or "data audit."
Neither correction creates a new category of obligation. Both make an existing sentence read the way the drafters evidently meant it to read.
What the Order does not do
Because social media and some blogs have described this Order as "new consent and audit rules", it helps to list clearly what is not in it, based on what the reports say.
- It does not change any DPDP Rule. Rule 10 (verifiable parental consent), Rule 11 (guardians of persons with disability) and Rule 13 (extra obligations of Significant Data Fiduciaries) stand as they were notified in November 2025.
- It does not create any new audit requirement for ordinary businesses. The "data audit" language in Section 10 is about Significant Data Fiduciaries only. A typical small business is not a Significant Data Fiduciary unless the Central Government notifies it as one. We did not find any report of a general notification designating Significant Data Fiduciaries, but we could not confirm that none exists, so keep an eye on MeitY announcements.
- It does not change penalties. The Schedule to the Act is untouched.
- It does not change commencement dates. Sections 9 and 10 begin on the date fixed by the commencement notification, which for the sections in question is eighteen months after the date of publication of that notification.
- It does not exempt anyone. Nothing in the Order creates a small-business exemption.
- It does not add a consent form, template or format. Anyone selling you a "new Order-compliant consent form" is selling you a marketing line.
If you remember only one thing from this section, remember this: the Order is a proofreading correction with legal force. It tells you the drafters' intention more clearly, and that intention is useful to know when you design your consent flow for children and for persons with disability, and when you read audit obligations for a Significant Data Fiduciary.
The phased commencement dates, carefully
The most expensive mistake a small business can make is to use the wrong date. Some people believe the Act is already fully in force. Others believe nothing starts until 2027 and that nothing needs to be done before then. The truth is in between and is phased. Here is what the sources show.
On 13 November 2025, the Central Government notified the commencement of the Act in phases through notification G.S.R. 843(E), and notified the Digital Personal Data Protection Rules, 2025 through G.S.R. 846(E) (as corrected by a later notification, according to the Mondaq summary). A PIB press release of 14 November 2025 describes the Rules as having an 18-month phased compliance timeline. The Act and Rules were notified on 13 November 2025, as also recorded in a PIB release of 3 December 2025.
| Phase | Date | What starts |
|---|---|---|
| Phase 1 | 13 November 2025 | Short title and definitions, and the provisions that set up the Data Protection Board of India and its procedures (Sections 18 to 26 of the Act, and Rules 1, 2 and 17 to 21), among others |
| Phase 2 | 13 November 2026 | Consent Manager registration (Rule 4, with Section 6(9) and Section 27(1)(d) of the Act) |
| Phase 3 | 13 May 2027 | Sections 3 to 17 of the Act (apart from the Consent Manager piece), the Board's inquiry and penalty provisions, and Rules 3, 5 to 16, 22 and 23: notice, consent, security safeguards, breach intimation, erasure, children's data, Significant Data Fiduciary duties, rights of Data Principals, and calling for information |
Three notes on this table.
First, the exact day. All the one-year and eighteen-month dates are counted from the date of publication in the Official Gazette, which the sources give as 13 November 2025. One secondary source (Mondaq's "8 key takeaways") gives 14 November 2026 and 14 May 2027, one day later. The government's own press release of 14 November 2026 says the Consent Manager framework "came into effect on 13 November 2026" and that other provisions are scheduled for 13 May 2027, so we use 13 May 2027. If your plan depends on a single day, plan to be ready earlier, and check the original notification.
Second, what Phase 2 means for you. Phase 2 is about Consent Managers, which are special Indian companies that help individuals give, manage, review and withdraw consent across businesses. A PIB release of 14 November 2026 says that MeitY has launched a portal at dpbi.gov.in for eligible companies to apply, and that applicants must be Indian companies with a net worth of not less than Rs 2 crore. Unless you plan to become a Consent Manager, Phase 2 creates no duty for you.
Third, the proposal to shorten the timeline. A Business Standard report of 22 January 2026 said MeitY was considering cutting the eighteen-month window to twelve months for some provisions, reportedly for Significant Data Fiduciaries, based on anonymous sources. Other commentary says that MeitY invited industry feedback that closed on 4 February 2026. A compliance-timeline article (MirvoLegal, "as at September 2026") and an article published on 8 October 2026 both say no amendment to the commencement date had been published. The PIB release of 14 November 2026 still gives 13 May 2027. So as of 18 November 2026, we found no notified change, and the proposal remains a proposal. We cannot rule out that a later amendment may be notified, and a shortened timeline would move the date forward, so the sensible approach is to be ready early, not at the last minute.
On the Data Protection Board itself: it is legally established, but according to commentary we read (dpdpa.dcomply.in, checked as of 15 November 2026, and PPC Land on 12 November 2026), no Chairperson or Member had been notified as appointed. MeitY invited applications on 6 May 2026. This matters because the Board is the body that will hear complaints and impose penalties once the main provisions begin. A Board without members cannot yet do that work, but the law will still be in force on 13 May 2027, and delay in appointments is not a safe basis for delaying your own preparation.
What the Act and Rules require, in plain words, for a business that collects customer data
Before the plan, a brief recap of the duties that matter for a small business. This is a recap, not the general explainer. We reference the section or rule so that you can read the original.
Who is a Data Fiduciary, and does this apply to me?
The Act defines a Data Fiduciary as any person who, alone or together with others, decides the purpose and means of processing personal data. If you decide why and how customer, student, patient, subscriber or employee data is collected, you are a Data Fiduciary, whether you are a proprietor, a partnership, an LLP, a company or a trust. A vendor that handles data only on your instructions, such as a cloud service, an email tool or a payroll processor, is a Data Processor, and you remain responsible for what it does on your behalf.
There is no blanket exemption for small businesses. Section 17(3) of the Act allows the Central Government to notify certain Data Fiduciaries or classes of them, including startups, and to relieve them from some provisions, namely Sections 5, 8(3), 8(7), 10 and 11. That is a power, not an exemption that already exists. A King Stubb and Kasiva article of 15 September 2026 warns that MSME status does not by itself make a business exempt. We did not find a notification that actually grants a startup exemption. If you hear that you are exempt because you are small, ask for the notification number.
Notice (Section 5 and Rule 3)
Before or at the time of asking for consent, you must give the person a notice that tells them what personal data you will process and why, how they can exercise their rights and withdraw consent, and how to complain to the Data Protection Board. Under the Rules, the notice has to be clear, in plain language, stand on its own, and itemise the data and purposes. It must be available in English or any language listed in the Eighth Schedule to the Constitution. For consent given before the Act came into force, Section 5(2) requires a notice as soon as reasonably practicable, and processing may continue until the person withdraws consent.
Consent (Section 6)
Consent has to be free, specific, informed, unconditional and unambiguous, given through a clear affirmative action, and limited to the personal data necessary for the specified purpose. A pre-ticked box or a long "by using this site you agree" line does not meet that test. Consent can be withdrawn at any time, and withdrawing must be about as easy as giving it. When consent is withdrawn, you and your processors must stop processing within a reasonable time unless the law requires or permits otherwise. If a person disputes consent, the burden is on you to show that notice was given and valid consent was obtained. That last point is why record-keeping matters so much.
Legitimate uses without consent (Section 7)
Not every use of data needs consent. Section 7 lists certain legitimate uses, including where a person voluntarily provides data for a specified purpose and has not objected to its use for that purpose, certain government benefits, legal obligations, compliance with court orders, medical emergencies, and employment purposes. A small business will use the "voluntarily provided for a specified purpose" ground often: when a customer gives an address to receive a delivery, you can use it for the delivery. But you cannot stretch it to unrelated uses such as marketing.
Duties of a Data Fiduciary (Section 8)
Section 8 is the working heart of the Act for a small business. In summary: you are responsible for compliance, including for processing done by your processors, whatever your contract says; processors can be engaged only under a valid contract; where data may be used to make a decision about a person or shared with another fiduciary, you must make reasonable efforts to keep it complete, accurate and consistent; you must have appropriate technical and organisational measures; you must take reasonable security safeguards to prevent a personal data breach; you must intimate breaches to the Board and affected persons; you must erase data when consent is withdrawn or the purpose is no longer served, unless law requires you to keep it; you must publish contact details of a Data Protection Officer or another person who can answer questions; and you must have a grievance redressal system.
Security safeguards (Rule 6)
The Rules list minimum safeguards. Sources describe them as including encryption, obfuscation, masking or virtual tokens; access control; logs and monitoring and periodic review of access; backups to ensure continued processing; retention of relevant logs and personal data for one year unless another law requires otherwise; and security terms in your contracts with processors. Different summaries count the measures differently, so read Rule 6 in the notified text instead of relying on a number. For a small business the message is practical: use strong passwords and two-step login, give staff access only to the data they need, back up regularly, and keep logs.
Breach intimation (Section 8(6) and Rule 7)
If a personal data breach occurs, you must inform each affected person, without delay and in plain language, and you must inform the Board. Sources describing Rule 7 say the person's message must cover the nature, extent and timing of the breach, its likely consequences, what you have done to reduce the risk, what the person can do to protect themselves, and a contact point. For the Board, there is an initial intimation without delay, followed by a fuller report within 72 hours, or a longer period if the Board allows. The 72 hours is therefore the deadline for the fuller report to the Board, and is not the deadline to tell the affected people, who must be told without delay. A separate mandatory reporting duty of six hours to CERT-In under its 2022 directions is mentioned in one source we read (The Privacy Labs, October 2026) as continuing to apply. We did not verify the CERT-In direction ourselves in this review, so confirm it separately if you are an entity covered by it.
Erasure and retention (Section 8(7), 8(8) and Rule 8)
You must erase personal data when the person withdraws consent or when the purpose is no longer served, unless a law requires you to keep it. For certain large classes, namely e-commerce entities with 2 crore or more registered users, online gaming intermediaries with 50 lakh or more users, and social media intermediaries with 2 crore or more users, the Rules treat the purpose as no longer served after three years of inactivity, with 48 hours' notice before erasure (as described in the sources we reviewed). A small business is far below these thresholds. Separately, Rule 8(3), as described in the sources, requires every Data Fiduciary to keep personal data, traffic data and logs for at least one year for certain purposes of the State listed in the Seventh Schedule, which a typical small business meets by keeping basic logs.
Contact point and grievance redressal (Section 8(9), 8(10), Rule 9 and Rule 14)
You must publish the business contact details of a Data Protection Officer or of a person who can answer questions, and provide a grievance system. Under Rule 14, as summarised by the sources, you must publish how to make a request, and respond to rights requests and grievances within a reasonable period not exceeding ninety days. Section 13 says a person should use your grievance system before going to the Board.
Rights of Data Principals (Sections 11 to 14)
The person whose data you hold can ask for a summary of the data you process and the processing activities, correction, completion and updating of their data, erasure of their data, and redress of grievances. They can also nominate someone to exercise rights on their behalf if they die or become incapable. They also have duties under Section 15, and breaching those can attract a penalty of up to Rs 10,000.
Children's data and persons with disability (Section 9, Rules 10 to 12)
This is where the 5 October Order made its first correction, so it deserves a fuller explanation than the rest. We cover it in the next section.
Significant Data Fiduciaries (Section 10 and Rule 13)
This is where the second correction was made. We cover it after the next section.
Transfers outside India (Section 16 and Rule 15)
The Act allows transfers of personal data outside India, except to countries the Central Government restricts by notification. Rule 15, as summarised in the sources, permits transfers subject to requirements the Central Government may set by general or special order. If you use a cloud service or tool hosted abroad, you do not need to stop using it, but you should know where your data sits.
Penalties (Section 33 and the Schedule)
The Schedule sets these maximum penalties, which we cross-checked across two sources that reproduce the Schedule (dpdpa.com and the DPDP wiki by Mynd Solution) and a compliance article (MirvoLegal):
| Failure | Section | Maximum penalty |
|---|---|---|
| Reasonable security safeguards not taken to prevent a personal data breach | 8(5) | up to Rs 250 crore |
| Failure to notify the Board and affected persons of a breach | 8(6) | up to Rs 200 crore |
| Failure to meet obligations for children's data | 9 | up to Rs 200 crore |
| Failure to meet additional obligations of a Significant Data Fiduciary | 10 | up to Rs 150 crore |
| Failure of a Data Principal to perform duties | 15 | up to Rs 10,000 |
| Breach of a voluntary undertaking accepted by the Board | 32 | up to the amount applicable to the original breach |
| Breach of any other provision of the Act or Rules | residual | up to Rs 50 crore |
One of the sources we opened for the penalty table, a Grant Thornton flyer, listed the amounts in a way that did not clearly match each breach to its amount, and it marked the pairing as an inference. We therefore did not use that flyer for the pairing and relied on the sources that reproduce the Schedule row by row. As with all figures in this article, please check the Schedule in the official Act.
Two points about penalties. These are maximums, and a penalty is imposed after an inquiry by the Board, which has to consider the factors set out in Section 33(2). The Board's decisions can be appealed to the Appellate Tribunal, which the PIB release of 14 November 2025 names as the Telecom Disputes Settlement and Appellate Tribunal (TDSAT). A first small lapse by a small business is not likely to attract the ceiling. But the ceilings are not meaningless either, and the Rs 250 crore figure is for failing to protect data in a way that leads to a breach, which is the area where small businesses are most exposed because their systems are the least protected.
Change one in detail: Section 9(1), children and persons with disability
What the law requires
Under the Act, a "child" is anyone who has not completed eighteen years of age. That is higher than the age many online services assume, so it is worth saying clearly: a seventeen-year-old is a child under this law.
Section 9 sets the rules for children's data. As described by the sources we reviewed:
- Section 9(1). Before processing any personal data of a child, or of a person with disability who has a lawful guardian, a Data Fiduciary must obtain verifiable consent of the parent, or of the lawful guardian, in the manner prescribed by the Rules.
- Section 9(2). You must not process personal data in a way that is likely to cause a detrimental effect on the well-being of a child.
- Section 9(3). You must not undertake tracking or behavioural monitoring of children, or targeted advertising directed at children.
- Section 9(4). The Rules may exempt certain classes of Data Fiduciaries or certain purposes from Sections 9(1) and 9(3), under conditions.
- Section 9(5). The Central Government may, in certain cases, exempt a Data Fiduciary from some of these obligations above a specified age if its processing is verifiably safe.
The Rules add the detail. Rule 10 requires you to take due diligence to check that the person giving consent is an identifiable adult who is the child's parent. The sources say that this can use details you already hold, or details the person voluntarily provides, or a virtual token from an authorised entity such as a Digital Locker service provider. Rule 11 deals with persons with disability who have a lawful guardian, and, as the Mondaq article summarises it, requires due diligence to confirm that the guardian was appointed under the applicable guardianship law. Rule 12 and the Fourth Schedule switch off some of the child-data duties for certain classes (the sources mention healthcare and allied healthcare professionals, educational institutions, creches and day care, and transport engaged by them) and for certain purposes (they mention, among others, a legal function in the child's interest, an email account, real-time location tracking for safety, and age confirmation), always subject to the conditions in the Schedule. The Mondaq article adds that Section 9(3) does not mention persons with disability.
What the Order fixed
The missing "of" matters because of how a sentence like this is read. Without it, one reading is that the phrase "who has a lawful guardian" qualifies both "a child" and "a person with disability." The corrected sentence makes two separate categories: personal data of a child, and personal data of a person with disability who has a lawful guardian. The reports we read describe it as a clarification that parental or guardian consent applies separately to each. The India Briefing article is explicit that the change does not create a new consent category or alter the underlying parental or guardian consent requirement.
What this means for a small business
For most businesses the practical effect is close to nothing in terms of new work, and this is the honest answer. What the Order does is remove an argument. A business can no longer say, "my user is an adult with disability but has no guardian, so Section 9 does not apply," or read the rule in some other loose way, without being clear that the guardian-consent duty is tied to a person with disability who has a lawful guardian. And a business that serves children cannot read the guardian qualifier as something that might not apply to them.
The important work for you is not the missing word. It is these questions:
- Do we collect data from anyone under 18? If you run a tutoring, coaching, school-service, kids' apparel, toy, sports, gaming, photography, health or family-oriented business, the answer is almost certainly yes, even if the customer who pays is a parent.
- Is the child's data coming from the parent directly? If a parent fills in the form for the child, you still need to be able to show that you obtained verifiable consent from the parent for the processing of the child's data, and you must be able to show who the parent is in a way that meets Rule 10's due diligence idea.
- Do we track, profile or advertise to children? Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children, subject to exemptions. Many marketing tools do this by default. Turn those features off for any children's audience.
- Do we serve persons with disability who have a lawful guardian? Examples include special education centres, therapy providers, and some healthcare and assisted-living services. If yes, plan for guardian consent and for Rule 11 due diligence.
- Do we fit an exemption in the Fourth Schedule? If you are an educational institution or a healthcare provider, read the Schedule closely instead of assuming you are exempt. The exemption is limited to specified purposes and conditions.
Change two in detail: Section 10(2)(c)(ii), Significant Data Fiduciaries and the "data audit"
Who is a Significant Data Fiduciary?
Under Section 10(1), the Central Government may notify any Data Fiduciary or class of Data Fiduciaries as Significant Data Fiduciaries, having regard to factors such as the volume and sensitivity of personal data processed, the risk to the rights of Data Principals, the potential impact on India's sovereignty and integrity, risk to electoral democracy, security of the State and public order. The designation is by the Central Government. You do not become one by your own choice or by crossing a number you can calculate yourself. We did not find a report that a general designation has been issued, but we did not confirm this from the Gazette.
What Section 10(2) and Rule 13 require
A Significant Data Fiduciary has to appoint a Data Protection Officer based in India who is accountable to its board or governing body, appoint an independent data auditor to carry out a data audit, and take other measures, which include a periodic Data Protection Impact Assessment and a periodic audit. Rule 13, as summarised by the sources we read, requires an impact assessment and an audit once every twelve months from the date of being notified as a Significant Data Fiduciary, requires the person doing it to give the Board a report of significant observations, requires due diligence to confirm that technical measures including algorithmic software do not pose a risk to the rights of Data Principals, and requires the Significant Data Fiduciary to ensure that personal data specified by the Central Government, and traffic data connected with it, are not transferred outside India. The Mondaq article notes that Rule 13 does not refer to Section 10 by number, which is one reason the wording of Section 10 itself mattered.
What the Order fixed
The Act spoke of an independent "data auditor" carrying out a "data audit" in clause (b), and of a "periodic audit" in clause (c)(ii). The Order changes the second to "periodic data audit." The recitals, as reported, state that the intended meaning of both references is a data protection audit or data audit. This removes any doubt that Section 10(2)(c)(ii) refers to some different general audit. For a Significant Data Fiduciary, it means that the periodic audit should be a data audit by the independent data auditor, and that its terms of engagement, checklists and reports should use that language. The India Briefing article lists documents where this wording should be aligned: compliance policies, governance frameworks, internal audit procedures, auditor engagement documents, audit checklists and periodic audit records.
What this means for a small business
If you are not notified as a Significant Data Fiduciary, there is no statutory "data audit" obligation on you under Section 10. We want to be very clear about this, because the headline "data-audit obligations" has caused unnecessary worry. Two practical points still apply.
First, you may be a vendor to a Significant Data Fiduciary. If you supply software, analytics, payroll, call-centre, logistics or marketing services to a large company, expect that company to ask you for evidence of your security and your handling of data, and to put audit and breach clauses in your contracts. A business that has already done its own light review will answer those questions quickly.
Second, an internal review, which we recommend below, is not a statutory "data audit." It is a sensible habit that helps you meet Section 8's duties and Rule 6's requirement for logging, monitoring and periodic review. Call it a self-review and do not tell customers it is a legal audit.
So what does the Order change for you in practice?
Put plainly, almost nothing in your daily work. But the Order is useful as a prompt in three ways.
- It confirms that the government is actively tidying up the law before the main date. The corrections are small, but they show that MeitY is reading the Act closely ahead of the main provisions. More clarifications may follow. We found no evidence of other Removal of Difficulties Orders issued under this Act between 5 October and 18 November 2026, but our search was not exhaustive.
- It sharpens two areas: children and persons with disability, and audits. If you handle either, this is the moment to review.
- It tells you the clock is running. Sections 9 and 10 are not yet in force. The Order corrected them early so that they read properly when they start on 13 May 2027.
Developments between 5 October and 18 November 2026
This article was first written for the 5 October slot. Since then, these developments are relevant, and each is cited to the source we used.
- 6 to 7 October 2026. The Order was published in the Official Gazette (the exact day differs between sources, as explained above). Law-firm and news articles on it followed through October, for example SCC Online (15 October 2026) and King Stubb and Kasiva (8 October 2026).
- 8 October 2026. An article by The Privacy Labs said that 13 May 2027 remained the date in law because no amendment to Rule 1 had been published in the Gazette.
- 13 November 2026. The Consent Manager registration framework came into effect, as stated in the PIB release of 14 November 2026.
- 14 November 2026. MeitY launched the dpbi.gov.in portal for companies that want to register as Consent Managers. The release says the rights of Data Principals, the Data Fiduciary obligations and the Board's inquiry and penalty processes are scheduled to come into effect on 13 May 2027.
- 15 November 2026. According to dpdpa.dcomply.in, no Chairperson or Member of the Data Protection Board had been appointed.
- Shortening of the timeline. We found no notified amendment. The January 2026 proposal to cut the eighteen months to twelve months remained, as far as we could find, a proposal.
If a new notification has been issued after 18 November 2026, this article will not reflect it.
Four illustrative stories
These are invented examples to show how the law could apply. They are not real businesses or real cases.
Story 1: The online tutoring business
Two founders run an online maths tutoring service for students in Classes 6 to 12. They collect the student's name, school, class, marks, a phone number, and the parent's phone number and email. Payments go through a gateway. They use a marketing tool that tracks visitors and shows ads to people who visited the site.
What the law means for them. Their students are children, so Section 9 applies. They need verifiable consent from the parent before processing the child's data. Their marketing tool's behavioural tracking and retargeting ads directed at children could breach Section 9(3), so they should switch off tracking and ad retargeting for any pages or apps that children use. They should check whether they fit an exemption in the Fourth Schedule for educational institutions and read the conditions. They are not a Significant Data Fiduciary. The 5 October Order changes nothing about what they must do, except that it confirms the guardian-consent duty applies to children as one category.
Plan for them: put a parent consent step at registration, send a plain-language notice to the parent, keep a record of when and how the parent consented, delete marks and contact data when a student leaves and no legal need remains, and tell the marketing vendor to stop retargeting.
Story 2: The freelance designer
A freelance graphic designer in Kota works with about forty clients across India. She holds client names, phone numbers, emails, GST details and project files, some of which include photos of people.
What the law means for her. She is a Data Fiduciary for her clients' personal data. For most of what she does, Section 7's ground of data voluntarily provided for a specified purpose is enough, so she does not need to ask for separate consent for each project, but she needs to use the data only for that purpose. She should have a short privacy notice on her website and in her proposal. She needs a way to answer a client who asks her to delete their data. If a client's file includes photos of other people, she is handling their data too, in her client's name. Her biggest risk is a security lapse: a stolen laptop, a shared drive link left open, a compromised email account. She should use two-step login, keep an encrypted backup, and know what she would do if a breach happened.
Story 3: The small clinic
A two-doctor clinic keeps patient files, phone numbers, prescriptions and test results, partly on paper and partly in a billing application. Reception staff use one shared login.
What the law means for the clinic. Health data is sensitive in practice even though the Act does not create a separate "sensitive data" category in the way some other laws do (this is our reading of the Act, and we recommend you confirm it for your situation). The Fourth Schedule's exemptions for healthcare professionals apply to children's data in specified conditions, but not to everything the clinic does. The clinic must keep reasonable security safeguards: individual logins instead of a shared one, access limited to staff who need it, a backup, and a log of who opened which record. It should be able to give a patient a summary of data held and correct errors. If the clinic treats a person with disability who has a lawful guardian, guardian consent comes into play under Section 9(1), now plainly worded.
Story 4: The software vendor to a large company
A five-person software company builds an attendance app for a large retail chain. The retail chain's staff data flows through the vendor's servers. The chain later tells the vendor it has been notified by the Central Government as a Significant Data Fiduciary and asks for security evidence and audit rights in the contract.
What the law means for the vendor. The vendor is a Data Processor for the chain. The chain is responsible under Section 8(1) for the vendor's processing, whatever the contract says, and Section 8(2) requires a valid contract. The chain's independent data auditor under Section 10 may ask to see the vendor's controls. The vendor itself has no Section 10 duty because it is not designated, but it should be ready with a short security note, access logs, a breach contact, and clear data deletion at the end of the contract. This is a likely real-world path by which the "data audit" language reaches small companies.
A practical rollout plan: from today to 13 May 2027
We have counted the days. From 18 November 2026 to 13 May 2027 is about 176 days, a little over twenty-five weeks. Do not spend all of it. Aim to be ready by the end of March 2027, so that April and early May are spare time for testing and corrections. The plan below is in six phases. A solo freelancer can finish each phase in a day or two. A business with a team and several tools will need the full time.
Phase 1: Know what you hold (weeks 1 to 3, late November to mid December 2026)
Make a simple data map. A spreadsheet is enough. For each type of personal data, write down: what it is (name, phone, email, address, ID, photo, health detail, marks, location), who it belongs to (customer, student, patient, employee, visitor), where you collect it (website form, WhatsApp, phone, paper, app, walk-in), where it is stored (which tool, which folder, which cupboard), who inside your business can see it, which outside vendors receive it, and why you collect it. Then add a column that says whether any of it belongs to someone under eighteen or to a person with disability who has a guardian.
This one exercise answers most of the questions in the rest of the plan. If a column is hard to fill, you have found a gap.
Phase 2: Decide your purposes and cut what you do not need (weeks 3 to 6, December 2026)
For each row in the map, write a one-line purpose in plain language: "to deliver your order", "to send you your invoice", "to book your appointment." Section 6 says consent must be limited to personal data necessary for the specified purpose. So if a form asks for a date of birth, an address, an Aadhaar number or a photo that you never use, remove the field. Less data means less to protect and less to lose.
Then decide for each purpose whether you rely on consent or on a legitimate use under Section 7. Be careful with the legitimate use for data voluntarily provided: it covers the purpose for which the person gave it, not marketing, not sharing with partners, not new products.
Phase 3: Fix your notice and consent (weeks 6 to 10, late December 2026 to January 2027)
Write the notice (a template is below). Make it stand alone, in clear language, itemising the data and purposes, explaining how to withdraw consent and how to make a request, and how to complain to the Board. Offer it in English and, if your customers speak another Indian language, in that language too, because the Act requires English or an Eighth Schedule language.
Replace pre-ticked boxes and "by continuing you agree" banners with a clear tick or button that the person chooses. Keep each purpose separate: do not bundle consent for delivery with consent for marketing. Make withdrawal as easy as giving: if a person signed up by clicking a button, they should be able to withdraw by clicking a button or sending a message to a monitored address.
If you serve children or persons with disability who have a guardian, build the parent or guardian step: ask for the parent's or guardian's details, check them with a method you can justify under Rules 10 and 11, record how you did it, and keep tracking and targeted ads switched off for children.
Keep a consent record: who, when, what notice version, which purposes, how they agreed. Section 6(10) puts the burden on you.
Phase 4: Secure the data and tidy your vendors (weeks 10 to 15, late January to early March 2027)
Do the basic safeguards from Rule 6 in a way that suits your size.
- Turn on two-step login for email, cloud storage, accounting and any dashboard with customer data.
- Give each staff member their own login. End shared passwords.
- Limit access: only people who need a file should be able to open it.
- Encrypt laptops and phones that carry customer data, and encrypt backups.
- Back up regularly and test a restore once.
- Keep access logs where your tools allow it, and keep logs for at least one year, as Rule 6 and Rule 8 describe.
- Remove former staff and vendors from systems on the day they leave.
Then list every vendor that touches personal data: hosting, email marketing, payment, CRM, accounting, payroll, courier, call-centre, analytics. For each, check that you have a written contract or terms that cover security, confidentiality, breach notification to you, deletion at the end, and help with rights requests. Section 8(2) requires a valid contract, and Section 8(1) makes you responsible for their processing. If a vendor stores data outside India, note the country.
Phase 5: Build your response systems (weeks 15 to 20, March to mid-April 2027)
Prepare three things.
- A contact point and grievance route. Name a person, and publish an email address and a phone number on your website and in your privacy notice. Under Rule 9 you need to publish contact details of a Data Protection Officer or another person who can answer questions. Under Rule 14, plan to respond to requests and grievances within a reasonable time that does not exceed ninety days. We suggest you aim for fifteen to thirty days, which is more comfortable for customers and leaves you margin.
- A rights-request procedure. Write down how you will verify identity, find the person's data across your tools, give a summary, correct errors, erase when required, and record what you did. Test it by running a mock request on yourself.
- A breach plan. Write a one-page plan: who decides it is a breach, how to contain it, how to find out what data and which people are affected, who writes to the people (without delay, plain language), who reports to the Board (an initial report without delay, and a fuller one within 72 hours), and who talks to vendors, the bank and, where relevant, CERT-In. Keep a breach log (template below). Run a one-hour tabletop practice with your team.
Phase 6: Test, train and go live (weeks 20 to 25, mid-April to 13 May 2027)
Train everyone who touches data for an hour. Explain what personal data is, what not to do (sharing customer lists on WhatsApp groups, sending files to personal email, leaving screens unlocked), and who to tell if something goes wrong. Review your data map, notice and vendor list for changes. Run a final check against the checklist at the end of this article. Put a date in your calendar for the first quarterly review after 13 May 2027.
After 13 May 2027
Treat the law as part of normal operations. Review the data map each quarter, keep the consent log, update notices when you change purposes, and review vendor contracts when you change vendors. Watch for MeitY and Board announcements, including any notification of Significant Data Fiduciaries, any startup exemption under Section 17(3), any cross-border restrictions under Section 16 and any change in dates.
How the plan changes by type of business
Freelancers and solo consultants. You can compress Phases 1 to 3 into a weekend. Your main risks are your own devices and accounts. Focus on two-step login, a clean privacy notice, a backup and a deletion habit.
Online sellers and D2C brands. Your main risks are marketing, trackers and vendors. Review every plug-in and ad pixel, remove those you do not need, make sure promotional messages rest on a clear, separate consent, and check your courier, payment and CRM contracts.
Coaching, tutoring and education services. Your main risk is children's data. Build the parent consent step, switch off behavioural tracking and ad retargeting for children's audiences, and read the Fourth Schedule on educational institutions before you rely on an exemption.
Clinics, labs and wellness services. Your main risks are shared logins, paper files and informal sharing of reports on messaging apps. Use individual logins, send reports through secure channels, and plan guardian consent where it applies.
Professional firms (accountants, lawyers, consultants, recruiters). You hold identity documents, financial data and sometimes employee data of clients. Use legitimate-use grounds correctly, keep client files in controlled systems, and remember that employment purposes are a legitimate use under Section 7 but still need safeguards.
Startups. Do not wait for an exemption. Build the compliance into the product from the start: consent screens, a deletion function, a rights-request form, and a data map that grows with the product. If your product serves large companies, expect their questionnaires.
Businesses with employees. Section 7 treats employment purposes as a legitimate use, so you do not need separate consent for ordinary payroll and attendance. Keep employee data secure, limit who sees it, and make sure your payroll and HR software contracts meet Section 8(2).
Templates you can adapt
These are starting points, not finished legal documents. Have an adviser read them against your own facts and the notified text of the Rules before you rely on them.
A plain-language consent notice (general customers)
"How [Business name] uses your personal data
We collect the following personal data from you: your name, mobile number, email address and delivery address [add or remove items to match what you really collect].
We use it only for these purposes: (1) to confirm and deliver your order; (2) to send you your invoice and order updates; (3) [only if you tick the box] to send you offers by email or WhatsApp.
You can withdraw your consent at any time by writing to [email] or messaging [number]. Withdrawing is as easy as agreeing. If you withdraw, we will stop using your data for that purpose within [a stated reasonable time], except where the law requires us to keep it.
You can ask us for a summary of the data we hold about you, ask us to correct or update it, ask us to erase it, or nominate someone to act for you. Write to [name and role of contact person] at [email] or [phone]. We will reply within [number] days.
If you are not satisfied with our reply, you can complain to the Data Protection Board of India.
This notice is available in English and [language]. Version [number], dated [date]."
Why each part is there: the first lines itemise the data, the second lists specific purposes with marketing separated, the third and fourth cover withdrawal and rights, the fifth names the Board, and the last lines show language and version, which helps you prove later which notice a person saw.
A parent or guardian consent notice (children and persons with disability)
"Consent from a parent or guardian
[Business name] offers [service] to students and young people under 18. Before we collect any personal data about a child, we need a parent's or lawful guardian's consent.
We would collect the child's [name, class, school, contact details, learning progress]. We would use it only to [deliver the classes and report progress to you]. We do not track your child's behaviour for advertising, and we do not show targeted advertisements to children.
Please confirm that you are the child's [parent / lawful guardian], give your name and [the verification method you have chosen], and tick the box to consent. You can withdraw this consent at any time by writing to [email].
For a person with disability who has a lawful guardian, we ask for the guardian's details and for [the document you have chosen to check the guardian's appointment under the applicable law]."
Use the verification methods that Rules 10 and 11 allow and that you can justify. Do not invent a method. If you are unsure, ask an adviser to read Rule 10 and Rule 11 with you.
A consent record (keep one row per consent)
| Field | Example entry |
|---|---|
| Person (or child plus parent) | Name and a reference number, not more detail than needed |
| Date and time | 12 January 2027, 6:42 pm |
| Channel | Website form / app / paper / WhatsApp |
| Notice version shown | Notice v2, 5 January 2027 |
| Purposes agreed | Delivery: yes. Marketing: no |
| How consent was given | Ticked box at checkout |
| Parent or guardian check (if relevant) | Method used and result |
| Withdrawn on | Blank, or date and how |
A breach log
| Field | What to write |
|---|---|
| Incident reference | BR-2027-001 |
| Date and time you first became aware | Exact time |
| Who found it and how | Name and role |
| What happened | One or two plain sentences |
| Data involved | Types of data, such as phone numbers and addresses |
| People affected | Number and group, such as customers who ordered in March |
| Where the data was (system, vendor) | Name of system or vendor |
| Containment steps and time | What you did and when |
| People informed and time | When and how each person or group was told, without delay and in plain language |
| Board informed (initial) and time | Date and time |
| Board fuller report (within 72 hours or longer period allowed) | Date and time |
| Other reports (for example CERT-In, bank, police) | Date and reference |
| Cause and fix | What failed, what you changed |
| Review date | When you will check the fix |
A breach message to affected people
"Subject: Important: a security incident involving your personal data
Dear [Name],
On [date] we found that [short, plain description of what happened]. The personal data involved was [types of data]. It happened on or around [date and time] and affected [extent].
What this could mean for you: [likely consequences, honestly stated, such as an increase in spam or a risk of phishing messages].
What we have done: [containment and fix]. What you can do: [practical steps such as changing a password or being careful with calls asking for an OTP].
You can contact [name] at [email and phone] with any questions.
Regards, [Business name]"
The sources describing Rule 7 list these elements for the message to the person: the nature, extent and timing of the breach, its likely consequences, the measures taken, what the person can do, and a contact. Check the notified Rule 7 for the exact list before you finalise your template.
A rights-request response
"Dear [Name],
Thank you for your request dated [date] to [see a summary of / correct / update / erase] the personal data we hold about you. We have verified your identity by [method].
[Summary of data and processing / the correction made / confirmation of erasure and any data we must keep by law, with the reason.]
If you are not satisfied with this reply, please write to [grievance contact]. You may also complain to the Data Protection Board of India after using our grievance process.
Regards, [Name and role]"
A vendor data-protection clause (short form)
"The Vendor will process personal data only on the Customer's written instructions and only for the purpose of providing the services. The Vendor will keep the data secure using reasonable safeguards, including access control, encryption where appropriate, backups and activity logs, and will allow only authorised staff to access it. The Vendor will tell the Customer without delay, and in any case within [24] hours, after becoming aware of any personal data breach, with the details the Customer reasonably needs. The Vendor will help the Customer respond to requests from individuals. At the end of the services, or on written instruction, the Vendor will erase or return the data, subject to any retention required by law. The Vendor will not engage another processor without the Customer's written approval."
The 24-hour figure is only a suggestion. It is a commercial term, not a legal one. Choose a number that lets you meet your own duty to report to the Board.
Common mistakes to avoid
- Reading the Order as a new set of rules. It corrects two sentences. Do not rewrite your whole compliance programme because of it, and do not buy "Order-compliant" products.
- Using the wrong date. Some people say the Act is "already in force" and others say "nothing until 2027". The accurate answer is phased, and the main duties start on 13 May 2027, subject to any later notification.
- Assuming small means exempt. Section 17(3) is a power to exempt, not an exemption. We did not find a notification granting one.
- Collecting too much. Every extra field is extra risk and extra work. Remove fields you do not use.
- Pre-ticked boxes and bundled consent. Consent has to be a clear affirmative action and specific to a purpose.
- Forgetting that "child" means under 18. A teenager is a child under the Act.
- Leaving tracking tools on for children. Retargeting pixels and behavioural analytics on a children's page can run into Section 9(3).
- Shared logins. If everyone uses one password, you cannot show who accessed what, and you cannot protect against a leaver.
- No vendor contracts. Section 8(2) requires a valid contract for processors, and Section 8(1) keeps you responsible for them.
- Treating 72 hours as the only breach deadline. The people affected must be told without delay. The 72 hours relates to the fuller report to the Board.
- Keeping data forever. Data should be erased when the purpose is served or consent is withdrawn, unless a law says you must keep it.
- Calling an internal review a legal audit. The statutory data audit in Section 10 applies to Significant Data Fiduciaries. An internal review is useful, but describe it honestly.
- No record of consent. If a customer disputes consent, the burden is on you under Section 6(10).
- Relying on a vendor's promise. The law holds you responsible for what your processors do, whatever the contract says about blame.
- Waiting for the Board to be fully set up. The Board's membership is pending as far as we could find, but the law will apply from the commencement date and complaints can follow after it starts working.
What to watch for next
- Any notification that shortens or changes the 13 May 2027 date. Check MeitY and the Gazette. The January 2026 proposal to compress the timeline was not, in what we found, notified.
- Notification of Significant Data Fiduciaries. This decides who gets the data-audit duty.
- Notification under Section 17(3) for startups or classes of Data Fiduciaries. Until it appears, assume there is no exemption.
- Appointment of the Data Protection Board's Chairperson and Members. The Board needs members to hear matters.
- Registered Consent Managers. The Board is to publish a list on its website once it registers any. As a business, you may be asked to work with them in future.
- Cross-border restrictions under Section 16 and Rule 15. Watch for any country or data restrictions.
- Any further Removal of Difficulties Order. If one is made, it should be laid before Parliament as Section 43 requires.
A short glossary
- Data Principal: the individual whose personal data is processed. For a child, this includes the parent or lawful guardian acting for the child, and for a person with disability, the lawful guardian.
- Data Fiduciary: the person who decides why and how personal data is processed. That is usually you.
- Data Processor: a person who processes personal data on behalf of a Data Fiduciary, such as a cloud, payroll or email service.
- Significant Data Fiduciary (SDF): a Data Fiduciary notified by the Central Government as significant, based on factors such as the volume and sensitivity of data and risk to rights. It has extra duties under Section 10 and Rule 13.
- Data audit: the independent audit of data protection compliance by an independent data auditor, for Significant Data Fiduciaries. The Order changed "audit" to "data audit" in Section 10(2)(c)(ii).
- Data Protection Impact Assessment: a structured review of the risks of a type of processing, required periodically from Significant Data Fiduciaries.
- Consent Manager: an Indian company registered with the Data Protection Board that lets individuals give, manage, review and withdraw consent through an interoperable platform.
- Verifiable consent: consent given by a parent or guardian in a way the Data Fiduciary can check and show, following Rules 10 and 11.
- Personal data breach: an incident in which personal data is accessed, disclosed, altered, lost or made unavailable without authority, in a way that affects its confidentiality, integrity or availability. Check the Act's exact definition.
- Removal of Difficulties Order: an order under Section 43 of the Act that clears a difficulty in giving effect to the Act without going back to Parliament.
- Data Protection Board of India: the body that receives complaints, conducts inquiries and imposes penalties. Its decisions can be appealed to the Appellate Tribunal.
- Commencement notification: the Gazette notification that fixes the dates from which different parts of the Act begin.
Final thoughts
The 5 October Order is a good example of how a legal headline can be much bigger than the legal text. Two small corrections made a sentence about guardian consent and a sentence about audits mean what the drafters evidently intended. That is helpful, because ambiguity in a law that carries penalties of up to Rs 250 crore is something everyone wants to be removed early. But it does not make your life harder, and it does not make it easier.
What does make a difference is how you use the months that remain. The businesses that will find 13 May 2027 easy are the ones that know what data they hold, ask for it in a clear way, protect it with simple habits, keep a few records, and have a plan for the day something goes wrong. None of this needs a large budget. It needs a few hours every week and a person who owns the task.
We will update this article if the Order's original text, a notified timeline change, a Significant Data Fiduciary designation or an exemption notification changes what we have said.
Frequently asked questions
What exactly did the DPDP Removal of Difficulties Order, 2026 change? Two wordings. In Section 9(1) of the DPDP Act, "a child or a person with disability" became "a child or of a person with disability." In Section 10(2)(c)(ii), "periodic audit" became "periodic data audit." Reports describe both as textual or editorial.
Does the Order create new consent rules for my business? No. The reports we read say it adds no new substantive obligation. Parental or guardian consent for children, and guardian consent for persons with disability who have a lawful guardian, are as they were. The Order only makes the sentence clearer.
Does the Order require every business to do a data audit? No. The "data audit" wording is in Section 10, which applies to Significant Data Fiduciaries designated by the Central Government. A business that is not designated has no statutory data-audit duty under Section 10, although a self-review is good practice.
Is the DPDP Act in force now? In phases. Parts of the Act and Rules started on 13 November 2025, the Consent Manager provisions started on 13 November 2026, and most duties for ordinary businesses, including notice, consent, security, breach intimation, children's data and rights, are scheduled for 13 May 2027, according to the commencement notification and a MeitY press release of 14 November 2026.
Are Sections 9 and 10 in force yet? No. They are in the third phase. One article gave "13 March 2027," but the notification and other sources, including the PIB release of 14 November 2026, point to 13 May 2027. We believe the "March" was a typing error.
Can the Order be read in the Gazette? It was published in the Official Gazette, reportedly on 6 or 7 October 2026, depending on the source. One law-firm article gives the number S.O. 5458(E). We could not open the Gazette copy ourselves, so please check the number and date on the original.
Does my small business have to comply, or am I exempt? You have to comply if you decide why and how personal data is processed. Section 17(3) lets the government notify exemptions for certain Data Fiduciaries, including startups, but we did not find a notification granting one. Do not assume you are exempt.
What is the maximum penalty, and will I really be fined Rs 250 crore? The Schedule sets maximums: up to Rs 250 crore for failing to take reasonable security safeguards, up to Rs 200 crore for failing to notify a breach or for failing in children's data duties, up to Rs 150 crore for Significant Data Fiduciary duties, and up to Rs 50 crore for other breaches. These are ceilings, and the Board decides the amount after an inquiry, considering the factors in the Act. A fine at the ceiling for a small business is not what the law is aimed at, but you should not ignore the risk.
Who is a child under the Act? Anyone who has not completed eighteen years.
Do I need parental consent for a seventeen-year-old customer? Yes, under Section 9(1), unless an exemption in the Fourth Schedule applies to your class and purpose. Read the Schedule carefully before relying on an exemption.
Can I use targeted ads on a website used by children? Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children, subject to the exemptions the Rules allow. Switch these off for children's audiences.
What is the deadline for reporting a breach? For the Board, as described by the sources on Rule 7, an initial intimation without delay and a fuller report within 72 hours, or a longer period the Board allows. For affected people, without delay and in plain language. Read the notified Rule 7 to confirm the details.
Do I also have to report to CERT-In? One source we read says CERT-In's six-hour incident reporting direction of 2022 still applies separately. We did not verify it in this review. If your business is covered by CERT-In directions, check them separately.
What is a Significant Data Fiduciary, and might I become one? It is a Data Fiduciary notified by the Central Government based on factors such as the volume and sensitivity of data and risk to rights. Most small businesses are unlikely to be notified, but we cannot give a threshold because none is fixed in the Act. Watch for notifications.
How long do I have to answer a customer's request? Under Rule 14, as summarised by the sources, you must respond to rights requests and grievances within a reasonable period not exceeding ninety days. Aim to respond much faster.
Do I need a Data Protection Officer? Every Data Fiduciary must publish the business contact details of a Data Protection Officer or of a person who can answer questions about processing (Section 8(9) and Rule 9). A Significant Data Fiduciary must appoint a Data Protection Officer based in India under Section 10.
What do I do with the data I already hold from before the Act? Section 5(2) says that for consent given before the Act came into force, you should give a notice as soon as reasonably practicable, and you may continue processing until the person withdraws consent. Map the old data and plan to send the notice.
Is my cloud tool hosted abroad a problem? The Act allows transfers outside India except to countries the Central Government restricts. Know where your data sits and check any notification under Section 16.
Is the 13 May 2027 date certain? It is the date in the commencement notification and in the MeitY release of 14 November 2026. A January 2026 report said MeitY considered shortening it, but we found no notified change. Watch for updates.
Where do I get the text of the Order, the Act and the Rules? From the e-Gazette portal, MeitY, and India Code. The links we used are at the end of this article.
A short checklist you can use today
- [ ] Data map completed: what personal data, whose, where collected, where stored, who can see it, which vendors
- [ ] Marked every record that belongs to someone under 18, or to a person with disability who has a lawful guardian
- [ ] Removed form fields and data you do not need
- [ ] Written a one-line purpose for each use of data
- [ ] Notice drafted in plain language, itemised, in English and your customers' language
- [ ] Consent boxes are un-ticked, specific and separate from other terms
- [ ] Withdrawal of consent is as easy as giving it
- [ ] Parent or guardian consent step built for children and for persons with disability, with a verification method you can justify
- [ ] Behavioural tracking and targeted ads switched off for children
- [ ] Consent record kept for each person
- [ ] Two-step login on email, cloud, accounting and customer dashboards
- [ ] Individual logins for every staff member, no shared passwords
- [ ] Encrypted devices and backups, with a tested restore
- [ ] Access logs kept for at least one year where your tools allow
- [ ] Written contract or terms with every vendor that handles personal data
- [ ] Contact person and grievance route published on website and notice
- [ ] Rights-request procedure written and tested
- [ ] Breach plan, breach log and message template ready, with a practice run
- [ ] Staff trained for one hour
- [ ] Reminder set to check MeitY and the Gazette for changes before 13 May 2027
How RegisCorp can help
RegisCorp is a digital-first legal compliance firm based in Kota, Rajasthan, serving businesses across India. We help small businesses with company, LLP and proprietorship registration, GST, ROC and trademark filings, and the policies and contracts that sit alongside them. If you would like help with a privacy notice, a consent flow, a vendor data clause or a simple readiness review before 13 May 2027, you can reach us at sales@regiscorp.co.in, or on WhatsApp and phone at 9251044653.
This article is general information, not legal advice. Your facts, your sector and the final notified texts decide what applies to you.
Official sources reviewed
We list what we actually opened, and say where we could not reach the original.
- Digital Personal Data Protection Act, 2023 (Act 22 of 2023), India Code copy: https://www.indiacode.nic.in/bitstream/123456789/22037/2/a2023-22.pdf (read through a research tool; sections 2, 5 to 14, 17 and 43 as summarised there)
- Digital Personal Data Protection (Removal of Difficulties) Order, 2026, e-Gazette copy linked by Lexorbis: https://egazette.gov.in/WriteReadData/2026/276885.pdf (could not be opened; the e-Gazette portal refused automated access, so the Order's wording is taken from the reports below)
- SCC Online blog, "Centre issues Digital Personal Data Protection (Removal of Difficulties) Order, 2026 to clarify consent and audit provisions", 15 October 2026: https://www.scconline.com/blog/post/2026/10/15/dpdp-removal-of-difficulties-order-2026/
- Mondaq, "DPDP (Removal Of Difficulties) Order, 2026: What Changes In Sections 9 And 10 Of The DPDP Act": https://www.mondaq.com/india/data-protection/1857872/dpdp-removal-of-difficulties-order-2026-what-changes-in-sections-9-and-10-of-the-dpdp-act (source of the reported S.O. 5458(E) number, quoted phrases and the reading of Rules 10, 11 and 13)
- India Briefing, "DPDP (Removal of Difficulties) Order 2026 Clarifies Consent and Data Audit Requirements in India": https://www.india-briefing.com/news/dpdp-removal-of-difficulties-order-2026-consent-data-audit-47274.html (source of the "13 March 2027" and "7 October 2026" statements that conflict with other sources)
- Chambers and Partners, "DPDP Act: Govt Issues Removal of Difficulties Order 2026 on Consent and Data Audits": https://chambers.com/articles/dpdp-act-govt-issues-removal-of-difficulties-order-2026-on-consent-and-data-audits
- Lexorbis, "MeitY Clarifies Consent and Audit Requirements Under the DPDP Act Through the Removal of Difficulties Order, 2026": https://www.lexorbis.com/meity-clarifies-consent-and-audit-requirements-under-the-dpdp-act-through-the-removal-of-difficulties-order-2026/
- King Stubb and Kasiva, "DPDP Removal of Difficulties Order 2026": https://ksandk.com/md/data-protection-and-data-privacy/dpdp-removal-of-difficulties-order-2026/
- King Stubb and Kasiva, "DPDP compliance for startups and MSMEs" (15 September 2026): https://ksandk.com/md/data-protection-and-data-privacy/dpdp-compliance-for-startups-msmes/
- Press Information Bureau, MeitY, "DPDP Rules, 2025 Notified", 14 November 2025 (release ID 2190014): https://www.pib.gov.in/PressReleasePage.aspx?PRID=2190014®=3&lang=2
- Press Information Bureau, "Simplified compliance framework for start-ups and certain data fiduciaries under DPDP Act and Rules", 3 December 2025 (release ID 2198217): https://www.pib.gov.in/PressReleasePage.aspx?PRID=2198217®=3&lang=1
- Press Information Bureau, MeitY, Consent Manager registration framework, 14 November 2026 (release ID 2336151): https://www.pib.gov.in/PressReleasePage.aspx?PRID=2336151
- DPDP Wiki (Mynd Solution), commencement notification G.S.R. 843(E): https://dpdp.myndsolution.com/wiki/notifications/gsr-843e-2025-commencement/ ; rules index: https://dpdp.myndsolution.com/wiki/rules/index.md ; guide to the Rules: https://dpdp.myndsolution.com/wiki/guides/the-dpdp-rules-2025-explained/ ; Schedule: https://dpdp.myndsolution.com/wiki/act/schedule/ (secondary sources reproducing official texts)
- DPDPA.com, the Schedule to the Act: https://dpdpa.com/theschedule.html ; Rule 13: https://www.dpdpa.com/dpdparules/rule13.html
- S.S. Rana and Co., "MeitY Notifies Final Digital Personal Data Protection Rules 2025": https://ssrana.in/articles/meity-notifies-final-digital-personal-data-protection-rules-2025/
- SCC Online blog, "Digital Personal Data Protection Rules 2025: key highlights", 26 December 2025: https://www.scconline.com/blog/post/2025/12/26/digital-personal-data-protection-rules-2025-key-highlights/
- Mondaq, "8 key takeaways: the Digital Personal Data Protection Rules 2025": https://www.mondaq.com/india/privacy-protection/1709084/8-key-takeaways-the-digital-personal-data-protection-rules-2025 (gives 14 November dates, one day later than other sources)
- Grant Thornton Bharat, DPDP Rules flyer, November 2025: https://www.grantthornton.in/globalassets/1.-member-firms/india/assets/pdfs/flyers/dpdp-rules-nov-2025.pdf (not relied on for the penalty pairing)
- Business Standard, "Meity may cut compliance timeline for key DPDP rules to 12 months", 22 January 2026: https://www.business-standard.com/technology/tech-news/meity-may-cut-compliance-timeline-for-key-dpdp-rules-to-12-months-126012201293_1.html (anonymous sources, unconfirmed)
- MirvoLegal, "DPDP Rules, 2025: Compliance Timeline for Data Fiduciaries (as at September 2026)": https://www.mirvolegal.com/insights/dpdp-rules-2025-compliance-timeline/
- The Privacy Labs, "DPDP 13 November 2026: What Actually Starts (and What Does Not)": https://theprivacylabs.com/blogs/dpdp-13-november-2026-what-starts (source of the CERT-In remark)
- PPC Land, "India opens consent manager registration with a 2 crore net worth floor": https://ppc.land/india-opens-consent-manager-registration-with-a-2-crore-net-worth-floor/
- dpdpa.dcomply.in, Data Protection Board status: https://dpdpa.dcomply.in/board/
Published by RegisCorp Consultancy LLP. Reviewed by Indrajeet Sharma, Founder.