Skip to main content

The 3rd and main DPDP commencement date is computed as 13 May 2027, which is interpretation until officially confirmed.

Sources last verified on 28 October 2026. Methodology

Reference

DPDP frequently asked questions

Direct answers to the questions organisations and individuals ask most about the DPDP Act 2023 and the DPDP Rules 2025. Search or browse by category, click a question to see the short answer, and follow through to the full article with official sources.

Applicability

How does the DPDP Act apply to ecommerce businesses?

Ecommerce is not a special DPDP role. A platform that determines the purpose and means of a processing activity is the Data Fiduciary for that activity. A delivery, cloud or payment provider acting on its behalf is a Data Processor, while a provider choosing its own purpose may be a separate Data Fiduciary. At checkout, section 4 requires consent or a particular use in section 7, and section 5 requires a notice when consent is requested under section 6. The Act's shopping illustration lets a platform finish supplying goods already ordered and paid for after consent is withdrawn, but not keep enabling new orders on that consent. Section 8 and Rule 8 contain 3 distinct retention rules: the section 8(7) purpose test; a 3 year inactivity timer under Rule 8(1) that, for ecommerce, reaches an ecommerce entity with at least 2 crore registered users in India; and the separate Rule 8(3) floor requiring personal data, traffic data and processing logs for at least 1 year for the Seventh Schedule purposes. Processor contracts do not shift the Data Fiduciary's responsibility, and security and breach duties reach processing done on its behalf. The main duties discussed here sit in the 18 month groups, computed as 13 May 2027 and potentially as late as 15 May 2027. Both dates are interpretation until officially confirmed.

Full answer with sources →

How does the DPDP Act apply to fintech companies?

Fintech is a market label. Under the Act, roles turn on who determines the purpose and means of a processing activity and who acts on that person's behalf. The Act contains 4 financial services illustrations: a bank account opened through video KYC, an insurance policy bought through an app, a savings account closed while another law requires records to stay, and a defaulted bank loan. Customer processing must have a section 4 ground: consent or a particular use in section 7. A section 5 notice is required when the Data Fiduciary requests consent under section 6. Calling a product a consent platform does not make it a Consent Manager: section 6(9) requires Board registration, and Rule 4 supplies the scheme. Section 17(1)(f) is narrow. It covers processing to ascertain the financial information, assets and liabilities of a person who has defaulted on a loan or advance from a financial institution, subject to disclosure law; it does not exempt a fintech company or its ordinary customer journey. Sector rules continue alongside the Act. IRDAI's 2026 cyber security Guidelines bind the insurance entities named by its circular and require appropriate measures for DPDP compliance. RBI's July 2026 data governance text is still a draft and binds no regulated entity. Section 6(9) and Rule 4 commence on a computed 13 November 2026; the main duties discussed here commence on a computed 13 May 2027. Both dates are interpretation until officially confirmed.

Full answer with sources →

How does the DPDP Act apply to hospitals and health apps?

A hospital, clinic, laboratory or health app that determines the purpose and means of processing digital personal data is a Data Fiduciary under the DPDP Act 2023, and health data is ordinary personal data under section 2(t): the Act has no sensitive or health category. Section 4 allows processing only on consent or a legitimate use in section 7, and 3 of its 9 clauses matter most here: 7(f), a medical emergency involving a threat to life or an immediate threat to health; 7(g), treatment or health services during an epidemic, outbreak or other threat to public health; and 7(a), data the patient voluntarily provided for a specified purpose, illustrated in the Act by a pharmacy. No clause of section 7 names routine treatment; on this site's reading, everyday care rests on consent or clause (a). For child patients, Rule 12 and Part A of the Fourth Schedule lift the parental consent and tracking duties for clinical establishments, mental health establishments and healthcare professionals, only so far as necessary to protect the child's health; that relief does not reach adults with a lawful guardian, for whom, on this site's reading, the guardian's verifiable consent under section 9(1) and the Rule 11 due diligence still apply. These duties commence on a computed 13 May 2027, interpretation until officially confirmed; until section 44(2) commences, section 43A and the SPDI Rules 2011, which list medical records and health condition as sensitive personal data, remain in force as at 18 October 2026.

Full answer with sources →

Does the DPDP Act apply to AI training data?

Not yet under the main processing provisions, but AI training data can fall within the Act once they commence. The English text of the Act and Rules does not use the phrases artificial intelligence, machine learning or profiling. Section 2(b) defines automated broadly, and section 2(x) includes collection, recording, organisation, storage, retrieval, use, combination and indexing in processing. Training is not itself a listed term, but those operations are processing when performed on digital personal data, whatever the system is called. Public availability alone is insufficient for section 3(c)(ii). The data must have been made or caused to be made public by the Data Principal, or made public by another person under an obligation in a law in force in India. A third party post qualifies only if one of those limbs is met. Section 17(2)(b) separately covers processing necessary for research, archiving or statistical purposes only where the data is not to be used to take a decision specific to a Data Principal and the prescribed standards are met. Rule 13(3) expressly addresses algorithmic software but applies only to a Significant Data Fiduciary. Section 9(3) separately addresses children's tracking, behavioural monitoring and targeted advertising. The Act contains no express right against automated decision making. Section 2 is in force. Sections 3, 9 and 17 and Rules 13 and 16 are in 18 month groups, computed as 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

What does section 17 of the DPDP Act exempt?

Once section 17 is in force, section 17(1) disapplies Chapter III, section 16 and Chapter II other than sections 8(1) and 8(5) in 6 named situations: enforcing a legal right or claim, judicial and regulatory functions, offence prevention and investigation, offshore contracts for Data Principals outside India, approved mergers and other corporate restructurings, and loan default checks. Section 17(2) removes the whole Act for notified State instrumentalities and for research, archiving or statistical processing that is not used to take any decision specific to a Data Principal and follows the Second Schedule standards. Section 17(3) and section 17(5) add relief that waits on a Central Government notification, while section 17(4) applies to State processing by force of the text. Section 17 commences on the computed date 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

Does the DPDP Act apply to B2B SaaS companies?

Not yet as an operative DPDP obligation; once the relevant provisions commence, the Act can apply in different roles for different processing flows. Section 2's role definitions are in force, but sections 3, 4 and 8 and Rule 6 are not. When a B2B SaaS provider determines the purpose and means of processing personal data about its own site visitors, trial users or account holders, it is a Data Fiduciary for that processing. When it processes personal data on a customer's behalf, it is a Data Processor for that processing. The words Data Processor appear 9 times in the Act and 6 times in the English Rules. Section 2(k) is a definition, not a duty; the operative duties among those mentions are placed on Data Fiduciaries rather than directly on Data Processors. Section 4(1) is framed more broadly around a person who processes personal data, so its direct effect on a processor is an interpretation, not an express processor duty. Section 8(2) permits a Data Fiduciary to engage a processor for an activity related to offering goods or services to Data Principals only under a valid contract. Rule 6(1)(f) requires the Data Fiduciary, wherever applicable, to have an appropriate provision in that contract for taking reasonable security safeguards. The 18 month group is computed to 13 May 2027. This date is an interpretation until officially confirmed.

Full answer with sources →

Does the DPDP Act apply to companies outside India?

Yes, once it commences. Section 3(a) covers processing of digital personal data within India and section 3(b) processing outside India in connection with any activity related to offering of goods or services to Data Principals within India; on this site's reading, offshore the test is what is offered to people in India, not merely having Indian users. Section 3 commences 18 months after publication of G.S.R. 843(E), computed as 13 May 2027, interpretation until officially confirmed. On this site's reading the Act sets no general local presence duty: representative, subsidiary and branch each appear 0 times in it. The India specific exceptions are narrow: once section 10 commences, a notified Significant Data Fiduciary must appoint a Data Protection Officer based in India, and once Rule 4 commences on the computed date of 13 November 2026, interpretation until officially confirmed, an applicant to register as a Consent Manager must be a company incorporated in India. Section 8(9) will require published contact details of a person able to answer questions, not that the person be in India. On this site's reading, the lever against a company with no Indian assets is section 37, in the same group: once in force, on a Board reference intimating monetary penalty in 2 or more instances and advising blocking in the public interest, and after a hearing, the Central Government may order blocking of public access to information in any computer resource enabling it to offer goods or services in India.

Full answer with sources →

Does the DPDP Act apply to startups?

On the text, yes, and no size test stands between a startup and the Act. Section 3 and every provision cited below commence on the computed date of 13 May 2027, interpretation until officially confirmed, so none is in force yet. Section 3 will reach processing within India and offshore processing in connection with any activity related to offering goods or services to Data Principals in India. Its exclusions, for personal or domestic purposes of an individual and for data made public by the Data Principal or under a legal duty, never turn on size. Turnover, revenue, headcount, small, micro, MSME and threshold appear 0 times in the Act and the English Rules. Size can still matter: the Third Schedule attaches the Rule 8(1) erasure timer to 3 classes of e commerce, online gaming and social media platforms defined by registered user thresholds in India, section 10(1)(a) makes volume and sensitivity of personal data 1 of an open list of Significant Data Fiduciary factors, and section 33(2)(g) makes a penalty's likely impact on the person a matter the Board weighs. Falling outside the Third Schedule is not relief: the section 8(7) erasure duty remains, and this site reads the Rule 8(3) minimum of 1 year as reaching a Data Fiduciary of any size. Section 17(3) names startups, but only as a power to notify relief from 5 provisions, and no such notification had been located as at 9 October 2026.

Full answer with sources →

Current status

Are the SPDI Rules 2011 still in force after the DPDP Act 2023?

On this site's scoped reading of the official source set checked on 28 October 2026, yes. G.S.R. 313(E), dated 11 April 2011, states that the Rules were made under section 87(2)(ob) read with section 43A of the Information Technology Act, 2000, and Rule 1(2) commenced them on publication. The current India Code PDF is byte identical to this site's archived copy, and sections 43A and 87(2)(ob) still appear in the consolidated print as on 27 June 2025. Section 44(2) of the DPDP Act 2023 directs their omission, but paragraph (c) of G.S.R. 843(E) places section 44(2) in the 18 month group. This site computes 13 May 2027 from the printed publication date, which is interpretation until officially confirmed. No rescinding instrument was located in the official sources checked, but that search result is not a Gazette wide certified negative. A 24 August 2011 Press Information Bureau note records the Department's explanation that Rules 5 and 6 do not apply to the listed service activity performed under contractual obligation to a legal entity, but do apply where the body corporate contracts directly with the provider of information. The Press Note is an explanatory record, not an amendment to the Gazette Rules.

Full answer with sources →

Has the DPDP compliance deadline been cut from 18 months to 12 months?

No. As at the 12 October 2026 review, no instrument changing the commencement periods has been located: this site's source registry and timeline record none, and MeitY's published document library, enumerated on 9 October 2026, lists none. The only instrument among the 7 records in that capture dated 2026 is S.O. 5458(E), the Removal of Difficulties Order made on 5 October 2026 and published in Gazette issue No. 5248, whose printed masthead is dated 6 October 2026, which substitutes words in sections 9(1) and 10(2)(c)(ii) of the Act and amends neither G.S.R. 843(E) nor Rule 1. So the 3 phase commencement set by G.S.R. 843(E) and Rule 1 of the DPDP Rules 2025, as corrected by corrigenda G.S.R. 892(E), still runs on the same 3 periods, whose calendar dates are computed and are interpretation until officially confirmed. What exists is reporting: Business Standard reported on 22 January 2026, on unnamed sources, that MeitY had proposed at a stakeholder meeting to shorten the window for Significant Data Fiduciaries, on certain provisions, from 18 months to 12. No MeitY document about the proposal has been located in its whole published document library, enumerated on 1 September 2026 and again on 9 October 2026.

Full answer with sources →

Are the DPDP compliance deadlines 13 or 14 May 2027?

Both dates circulate because the notification date itself is recorded 2 ways. The masthead of Gazette issue No. 760 is printed 13 November 2025, while the eGazette file code stamped on that same issue, CG-DL-E-14112025-267650, and a Press Information Bureau release of 17 November 2025 state 14 November 2025. PIB then published 13 November 2025 for both the Act and the Rules on 3 December 2025, so the Government has stated both dates and cannot be cited in the singular for either. The Rules and the commencement notification set periods, not calendar dates: 1 year and 18 months from publication. Rule 1(3) and Rule 1(4), as corrected by corrigenda G.S.R. 892(E), run from the date of publication in the Official Gazette. So the main compliance date computes to 13 May 2027 from the printed date and 14 May 2027 from the file code. MeitY's own document library dates those instruments 14 November 2025 too, but on our reading it is not a consistent record of any document's date. A Press Information Bureau release of 16 May 2026 reports the Secretary, MeitY, noting that the Act becomes fully enforceable from 13 May 2027: reported speech, not an instrument, so it corroborates the printed date without confirming it. This site computes from the printed Gazette date and treats every computed date as interpretation until officially confirmed. Plan to the earlier date, because a 1 day ambiguity is not a reason to file late.

Full answer with sources →

Is the DPDP Act being challenged in the Supreme Court?

Yes. Since February 2026 the Supreme Court of India has been hearing writ petitions challenging parts of the DPDP Act 2023 and the DPDP Rules 2025, led by Venkatesh Nayak v Union of India, W.P.(C) 177/2026. The petitions target sections 17(1)(c), 17(2), 33(1), 36 and 44(3) of the Act and Rules 17 and 23(2) of the Rules, on grounds under Articles 14, 19(1)(a) and 21 of the Constitution, with the substitution of the personal information clause in section 8(1)(j) of the RTI Act at the centre. On 16 February 2026 a bench led by Chief Justice Surya Kant issued notice but refused an interim stay, and on 7 August 2026 the court gave the Central Government 2 weeks to respond. No order striking down or suspending any provision had been reported as of 15 October 2026, so the commencement schedule stands: the main obligations still arrive on the computed date of 13 May 2027, which is interpretation until officially confirmed.

Full answer with sources →

What is in force under the DPDP framework in 2026?

The DPDP Act 2023 was enacted on 11 August 2023 and its commencement was notified as G.S.R. 843(E) on 13 November 2025: the definitions, the sections establishing and constituting the Data Protection Board (sections 18 to 26) and certain other sections, including the rule making power, operate now, while the main obligations, the rights and the Board's inquiry and penalty powers follow 18 months after publication. The DPDP Rules 2025 were notified the same day, and Rules 1, 2 and 17 to 21 took effect at once. The main operational obligations in Rules 3, 5 to 16, 22 and 23 and the core Act sections follow 18 months after publication, which computes to 13 May 2027, and Rule 4 on Consent Manager registration and obligations, and sections 6(9) and 27(1)(d) of the Act, follow 1 year after publication, which computes to 13 November 2026. The computed dates are interpretation until officially confirmed. The Board has been established, but as at 21 October 2026 no appointment of its Chairperson or Members has been located, in a search of official channels on 28 August 2026 or in MeitY's published document library as enumerated on 21 October 2026, and on 7 October 2026 the Union's counsel told the High Court of Kerala that the Board has yet to be made functional.

Full answer with sources →

Definitions

Does the DPDP Act classify sensitive personal data separately?

No. The DPDP Act creates no separate sensitive personal data category. Section 2(t) defines personal data as any data about an individual who is identifiable by or in relation to that data. The exact word sensitive does not appear in the Act. Sensitivity appears in section 10(1)(a), but only as one factor the Central Government may assess when deciding whether to notify a Data Fiduciary or class as a Significant Data Fiduciary. Section 3 contains clauses (a), (b) and (c), so section 3(d) does not exist. Additional obligations can arise from notified Significant Data Fiduciary status under section 10, from processing personal data of children or persons with disability who have a lawful guardian under section 9, and from Rule 8 read with the Third Schedule for specified classes and user thresholds. Those mechanisms do not create a sensitive data tier. Sections 9 and 10 are in the Act's 18 month group. Rule 8 is in the Rules' 18 month group, and the Third Schedule operates through Rule 8. The common date is computed as 13 May 2027, interpretation until officially confirmed. Section 2 is already in force.

Full answer with sources →

DPDP Act क्या है और कब से लागू होगा?

DPDP का फुल फॉर्म है Digital Personal Data Protection। The Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023) भारत का data protection law है; इसे 11 अगस्त 2023 को राष्ट्रपति की स्वीकृति मिली। इस वेबसाइट के पास Act का आधिकारिक हिंदी पाठ उपलब्ध नहीं है; लेख की हिंदी व्याख्या वेबसाइट की अपनी है। DPDP Rules 2025 बताते हैं कि यह law कैसे काम करेगा; Gazette print में notification की तारीख 13 नवम्बर 2025 है। Law चरणों में लागू हो रहा है और पहला group नवम्बर 2025 से लागू है। Consent Manager registration से जुड़ी section 6(9) और Rule 4 के लिए इस वेबसाइट की गणना 13 नवम्बर 2026 है, लेकिन प्रकाशन तारीख और अवधि गिनने की 2 अनिश्चितताओं के कारण यह 15 नवम्बर 2026 तक हो सकती है। Notice, consent, security safeguards और personal data breach intimation जैसी मुख्य duties के लिए गणना 13 मई 2027 है, जो उन्हीं कारणों से 15 मई 2027 तक हो सकती है। ये तारीखें आधिकारिक पुष्टि तक व्याख्या हैं। Schedule में कुछ breaches के लिए monetary penalty अधिकतम 250 करोड़ रुपये तक है, लेकिन Board को penalty लगाने की power देने वाली section 33 भी तीसरे group में है और 28 अक्टूबर 2026 को लागू नहीं थी।

Full answer with sources →

What is DPDP and what is its full form?

DPDP stands for Digital Personal Data Protection. The Digital Personal Data Protection Act 2023, Act No. 22 of 2023, is India's law for processing digital personal data; it received the President's assent on 11 August 2023 and recognises both the individual's right to protect personal data and the need to process it for lawful purposes. The DPDP Rules 2025, notified on 13 November 2025, operationalise the Act. Both commence in phases: some provisions have been in force since 13 November 2025, Consent Manager registration is due on a computed date of 13 November 2026, and the main obligations are due on a computed date of 13 May 2027, both interpretation until officially confirmed. Once section 3 is in force with the main obligations, the law applies to digital personal data processed in India, and to processing abroad in connection with any activity related to offering goods or services to people in India, but not to personal or domestic processing or to data made publicly available by the individual or under a legal duty (section 3(c)).

Full answer with sources →

Is a name or email address personal data under the DPDP Act?

Usually yes in ordinary business records, on this site's reading. The Act defines personal data as any data about an individual who is identifiable by or in relation to such data, so the test is identifiability, not a list of categories; that section 2(t) definition is already in force. This site reads customer, employee and account records containing names or email addresses as ordinarily meeting that test. Handled digitally, they are digital personal data, which section 3 brings within the Act, subject to its exclusions for an individual's personal or domestic purposes and for data made public by the Data Principal or under a legal duty, once it commences on the computed date of 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

Notice

Does the DPDP notice have to be in 22 languages?

No; section 5(3) is not in force and does not say to publish 22 notice versions up front. It says the Data Fiduciary must give the Data Principal the option to access the notice in English or any language specified in the Eighth Schedule to the Constitution. On this site's reading, that means readiness to provide the notice in the listed language the individual chooses; the Data Fiduciary cannot replace the individual's option with its own language choice. Section 6(3) gives the same option for each consent request, and Rule 3 sets the notice quality requirements. These duties are not universal. Section 17 can disapply section 5 and section 6(3) for particular processing, remove the Act for listed processing, or support a notification removing named provisions. Neither instrument expressly makes consent automatically invalid solely because the person could not read the notice. Where the option applies, this site interprets a breach of section 5(3) or section 6(3) as falling within residual Schedule entry 7, not the 250 crore entry for section 8(5). A penalty still requires the section 33 process. Section 5, section 6(3), section 17 and Rule 3 are not in force. The first computed date is 13 May 2027 and official publication records plus counting uncertainty could move it as late as 15 May 2027. Both dates are interpretation until officially confirmed.

Full answer with sources →

What must a privacy notice contain under the DPDP Act and Rules?

Section 5 of the Act and Rule 3 of the Rules govern it, and neither is in force yet. Section 5(1) says every consent request must be accompanied or preceded by a notice informing the individual of the personal data and the purpose for which it is proposed to be processed, the manner of exercising her rights under section 6(4) and section 13, and the manner of complaining to the Board; section 5(3) adds the option to access the notice in English or any language specified in the Eighth Schedule to the Constitution. Rule 3 then sets the shape: the notice must be presented and understandable independently of any other information that has been, is or may be made available by the fiduciary, must give in clear and plain language a fair account enabling specific and informed consent including at minimum an itemised description of the personal data and the specified purpose or purposes with a specific description of the goods, services or uses, and must give the particular communication link and a description of other means, if any, through which the person can withdraw consent with ease comparable to the ease with which she gave it, exercise her rights and complain to the Board. Section 5 sits in the 18 month commencement group of notification G.S.R. 843(E) and Rule 3 in the 18 month group of Rule 1(4).

Full answer with sources →

Rights

Can I sue a company under the DPDP Act for a data breach?

Not under the DPDP Act itself, on this site's reading of the Gazette prints as at 7 September 2026. The Act gives a Data Principal no right of action and no compensation: none of compensation, compensate, damages or damage appears in the Act or the English DPDP Rules 2025. Once in force, it offers a complaint to the Data Protection Board under section 27(1)(b), after exhausting the company's grievance redressal under section 13(3), and penalties go to the Consolidated Fund of India under section 34. Section 39, already in force, bars civil courts from any suit or proceeding on a matter for which the Board is empowered under the Act. The complaint route is not open yet: sections 13, 27(1)(b) and 28 to 34 are computed to commence 13 May 2027, interpretation until officially confirmed. Information Technology Act section 43A stands until its omission by section 44(2) commences in that same group: a body corporate negligent in implementing and maintaining reasonable security practices and procedures for sensitive personal data or information, thereby causing wrongful loss or wrongful gain, is liable to pay damages by way of compensation. On the India Code print as on 27 June 2025, claims up to Rs 5 crore go to an adjudicating officer under section 46, with section 61 barring a civil suit, and larger ones to the competent court. Other laws, kept running by section 38(1), are not assessed here.

Full answer with sources →

How does grievance redressal work under the DPDP framework?

Once section 13 is in force, a Data Principal has a right to readily available means of grievance redressal from a Data Fiduciary or Consent Manager for its acts or omissions regarding its obligations in relation to her personal data or the exercise of her rights, subject to the section 17 exemptions, and must exhaust that opportunity before approaching the Data Protection Board. Section 13(2) leaves the response period to be prescribed. Rule 14(3), the only place a period appears in Rule 14, requires every Data Fiduciary and Consent Manager to "prominently publish on its website or app, or both, as the case may be, within a reasonable period not exceeding ninety days under its grievance redressal system for responding to the grievances of Data Principals" and to implement appropriate technical and organisational measures for the system's effectiveness. As printed, the sentence has no object for "publish", so what the 90 days cap is not stated. 2 readings are open: a cap on the response period to be published, or a time limit on the publishing itself. This site takes the first, because the same sub rule then requires effectiveness "in responding within such period", which the earlier words can only supply if they are a response period; that is this site's reading, not what the text states. Section 13 and Rule 14 are both in the 18 month commencement group, computed at 13 May 2027 and interpretation until officially confirmed.

Full answer with sources →

What rights do individuals have under the DPDP Act?

Once Chapter III of the Act is in force, it carries 4 rights, and section 6(4) carries a fifth that sits outside the chapter. Section 11 is the right to obtain a summary of your personal data and of the processing, the identities of all other Data Fiduciaries and Data Processors it was shared with, and a description of what was shared, except, under section 11(2), sharing on a written request with a Data Fiduciary authorised by law for the prevention, detection or investigation of offences or cyber incidents, or prosecution or punishment of offences. Section 12 is the right to correction, completion, updating and erasure, but under section 12(3) erasure yields where retention is necessary for the specified purpose or for compliance with law. Section 13 is the right to readily available grievance redressal from the Data Fiduciary or Consent Manager, which must be exhausted before approaching the Board. Section 14 is the right to nominate another individual to exercise the rights on death or incapacity. Section 6(4) is the right to withdraw consent at any time, with ease comparable to the ease with which it was given. Sections 11 to 15 and section 6(4) all sit in the 18 month commencement group of notification G.S.R. 843(E), so none of them binds anyone as at 29 September 2026. Sections 11 and 12 are written with a consent gate, and whether they reach processing on the section 7 legitimate uses other than clause (a) is unsettled.

Full answer with sources →

Children

What does the Supreme Court's APAAR order of 20 July 2026 mean for parents and schools?

On 20 July 2026 a 3 judge bench of the Supreme Court of India disposed of W.P.(C) 832/2026, Abhishek Baxi v Union of India, a challenge by parents to the APAAR Scheme. Paragraph 7 directs that paragraph 19 of the Orissa High Court's judgment of 12 December 2025 in Rohit Anand Das v State of Odisha, which directed the authorities "to consider amendment of the model consent form to include an opt out/refusal of consent option therein", be given effect across India. Paragraph 8 says processing of personal information under the Scheme shall be strictly governed by the Digital Personal Data Protection Act, 2023. Paragraph 9 says personal information cannot be disclosed to any private entity or third party except in accordance with law. The order names the Act 1 time, cites 0 sections and says nothing about commencement. For a parent, the Court called an option to refuse "essential" to meaningful consent; the order does not say what follows a refusal. For a school, paragraph 7 gives effect to the direction "by the concerned authorities implementing the APAAR Scheme"; on this site's reading the amendment is not for each school to draft. Section 2 of the Act, with the definitions of child and Data Fiduciary, has been in force since 13 November 2025; sections 4, 5, 7 to 10 and section 6 except sub section (9), and Rule 10, commence 18 months after publication, computed 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

What does the DPDP Act require from schools and edtech companies?

Once section 9 is in force: verifiable parental consent before processing a child's data, no processing likely to harm a child's wellbeing, and no tracking, behavioural monitoring or targeted advertising directed at children. Rule 12 and the Fourth Schedule lift only sections 9(1) and 9(3), only for listed classes and purposes, and only on the printed condition: an educational institution is covered for tracking and behavioural monitoring for educational activities or enrolled child safety. On this site's reading, admissions, fees and photographs keep the consent duty, fees subject to Part B item 2 where the State provides a benefit under section 7(b). Section 9(2) is never lifted by Rule 12 or the Fourth Schedule. Section 9 and Rules 10 and 12 are not in force and commence 18 months after publication, computed 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

What does the DPDP Act require for processing children's data?

A child is an individual who has not completed the age of eighteen years; that definition is in force, but section 9 and Rules 10 to 12 commence on the computed date of 13 May 2027, interpretation until officially confirmed. Once in force, section 9 sets 3 duties: obtain verifiable consent of the parent or lawful guardian before processing any personal data of a child, not undertake processing likely to cause any detrimental effect on a child's wellbeing, and not undertake tracking or behavioural monitoring of children or targeted advertising directed at children. Section 9(1) also covers a person with disability who has a lawful guardian, with Rule 11 guardian checks. Rule 10 requires technical and organisational measures and due diligence that the individual identifying herself as the parent is an adult who is identifiable if required in connection with compliance with any law in India, by reference to reliable identity and age details the Data Fiduciary already holds or details voluntarily provided, directly or through a virtual token issued by an authorised entity. Rule 12 and the Fourth Schedule lift only sections 9(1) and 9(3), for listed classes, such as clinical establishments and educational institutions, and listed purposes, each on the Schedule's conditions; Rule 12 does not lift the wellbeing duty in section 9(2); section 17 exemptions are separate. Section 9(5) also allows a notified age above which a Data Fiduciary with verifiably safe processing is exempt from all or any of the 9(1) and 9(3) obligations.

Full answer with sources →

Security

What security safeguards does DPDP Rule 6 require?

Once Rule 6 is in force, a Data Fiduciary must protect personal data in its possession or under its control, including in respect of any processing undertaken by it or on its behalf by a Data Processor, by taking reasonable security safeguards to prevent personal data breach, which shall include, at the minimum: appropriate data security measures, such as securing of personal data through encryption, obfuscation, masking or the use of virtual tokens mapped to that personal data; appropriate measures to control access to the computer resources used by the Data Fiduciary or the Data Processor, wherever applicable; visibility on the accessing of the data through appropriate logs, monitoring and review, for enabling detection of unauthorised access, its investigation and remediation to prevent recurrence; reasonable measures, such as data backups, for continued processing if the confidentiality, integrity or availability of the data is compromised; retention of such logs and personal data for 1 year, for detection, investigation, remediation and continued processing, unless compliance with any law for the time being in force requires otherwise; appropriate provision in the contract with a Data Processor, wherever applicable, for taking reasonable security safeguards; and appropriate technical and organisational measures to ensure effective observance of the safeguards. As at 2 October 2026, Rule 6 is not in force: Rule 1(4) places it in the group commencing 18 months after publication, computed as 13 May 2027, which is interpretation until officially confirmed.

Full answer with sources →

Breach response

डेटा ब्रीच हो जाए तो DPDP के तहत क्या करना होगा?

28 अक्टूबर 2026 की समीक्षा के अनुसार, यदि संस्था CERT In निदेश में बताई गई श्रेणियों में आती है और घटना Annexure I की Data Breach या Data Leak श्रेणी में है, तो घटना का पता चलने या उसकी सूचना मिलने के 6 घंटे के भीतर CERT In को रिपोर्ट करना लागू है; DPDP Rule 7 की सूचना लागू नहीं थी। Rule 7 लागू होने पर Data Fiduciary को उल्लंघन की जानकारी मिलने पर, अपनी सर्वोत्तम जानकारी के अनुसार, हर प्रभावित Data Principal को बिना देरी के सूचित करना होगा। Board को पहले बिना देरी के उल्लंघन की प्रकृति, सीमा, समय, स्थान और संभावित प्रभाव बताना होगा; फिर जानकारी मिलने के 72 घंटे के भीतर, या लिखित अनुरोध पर Board द्वारा दी गई अधिक अवधि में, Rule 7(2)(ख) की विस्तृत जानकारी देनी होगी। Rule 7 और अधिनियम की धारा 8(6) 18 महीने वाले समूह में हैं। इस साइट की गणना 13 मई 2027 है, लेकिन प्रकाशन तारीख और अवधि गिनने की अनिश्चितताओं के कारण यह 15 मई 2027 तक हो सकती है; यह आधिकारिक पुष्टि तक व्याख्या है।

Full answer with sources →

What should my organisation do after a personal data breach?

Once Rule 7 of the DPDP Rules 2025 is in force, 2 legal clocks start the moment your organisation becomes aware of a personal data breach. As a matter of practice rather than of Rule 7, start containment, awareness recording and Data Processor instructions while running 2 duties in parallel, both without delay: intimate each affected Data Principal in plain language with 5 required contents, and send the Data Protection Board a description of the breach. Within 72 hours of awareness, file the detailed Board submission with its 6 required contents; a longer period needs the Board's permission on a written request. Afterwards, again as practice rather than as a requirement of Rule 7, verify the fix, preserve the record, and be ready for a possible Board inquiry. This assumes the processing is within the Act and no section 17 exemption disapplies section 8(6). Rule 7 sits in the commencement group computed to 13 May 2027, interpretation until officially confirmed, and building the workflow before the duty begins is the practical move.

Full answer with sources →

Is the data breach reporting deadline in India 72 hours or 6 hours?

Both, because they are 2 separate legal regimes with different recipients. Under Rule 7 of the DPDP Rules 2025, once it is in force, a Data Fiduciary must intimate each affected Data Principal and send the Data Protection Board a description of the breach without delay, then file detailed information with the Board within 72 hours of becoming aware, or any longer period the Board allows on a written request. Separately, under the CERT In directions of 28 April 2022 issued under the IT Act, service providers, intermediaries, data centres, body corporates and government organisations must report cyber incidents listed in Annexure I, which includes data breach and data leak, to CERT In within 6 hours of noticing them. The DPDP duty is in the commencement group computed to 13 May 2027, interpretation until officially confirmed; the CERT In duty is already in effect: the directions took effect 60 days after issue, and on 25 September 2022 for MSMEs.

Full answer with sources →

What does DPDP Rule 7 require after a personal data breach?

Once Rule 7 of the DPDP Rules 2025 is in force, a Data Fiduciary that becomes aware of any personal data breach must, to the best of its knowledge, intimate each affected Data Principal in a concise, clear and plain manner and without delay, through her user account or a mode of communication she registered with it. The intimation must cover a description of the breach, including its nature, extent and timing; the consequences relevant to her that are likely to arise; the measures implemented and being implemented, if any, to mitigate risk; the safety measures she may take; and business contact information of a person able to respond to her queries. It must also intimate the Data Protection Board: without delay, a description of the breach, including its nature, extent, timing and location of occurrence and the likely impact; then, within 72 hours of becoming aware, or within such longer period as the Board may allow on a written request, updated and detailed information on that description, the broad facts on the events, circumstances and reasons leading to the breach, mitigation measures implemented or proposed, if any, any findings regarding the person who caused it, remedial measures taken to prevent recurrence, and a report on the intimations given to affected Data Principals. Rule 7 is in the group that Rule 1(4) brings into force 18 months after publication in the Official Gazette, which computes to 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

Retention

How long can you keep personal data under the DPDP Act?

No single general DPDP retention period exists. As at 25 October 2026, the erasure and minimum retention duties below are not in force; their common commencement is computed as 13 May 2027 and potentially as late as 15 May 2027, interpretation until officially confirmed. The exact English phrases retention period, retention policy, retention schedule and data retention appear 0 times in either instrument. Where section 8(7) applies, it requires erasure on withdrawal of consent or when the specified purpose is reasonably assumed to have ended, whichever is earlier, unless another law requires retention. Rule 8(1) deems that purpose no longer served after 3 years from the latest of the Data Principal's last approach, exercise of rights, or the Rules' commencement. It applies only to the Third Schedule's 3 threshold classes and corresponding purposes. Rule 8(2) requires notice at least 48 hours before completion of the erasure period under Rule 8. Rule 6(1)(e) requires specified security logs and personal data to be kept for 1 year. On this site's interpretation, Rule 8(3) generally requires Data Fiduciaries to keep personal data, associated traffic data and processing logs for at least 1 year for Seventh Schedule purposes. A registered Consent Manager separately keeps its Part B record for at least 7 years. Rule 4 and its First Schedule duties commence on a separate computed date of 13 November 2026 and potentially 15 November 2026, also interpretation until officially confirmed.

Full answer with sources →

Transfers

What is the difference between DPDP and GDPR?

The DPDP Act 2023 and the GDPR solve the same problem with different machinery. DPDP covers digital personal data with 2 grounds for processing, consent or certain legitimate uses, while the GDPR lists its lawful bases in Article 6(1). DPDP caps penalties per breach category at fixed rupee amounts up to Rs 250 crore, while GDPR fines scale with global turnover. DPDP treats everyone under 18 as a child and requires verifiable parental consent, subject to the exemptions under section 9(4) and Rule 12; the GDPR Article 8 baseline for consent to information society services is 16, which member states may lower to 13. DPDP has a registered Consent Manager institution with no GDPR equivalent, notifies every affected person of any breach without a risk threshold, and channels complaints through the Data Protection Board after the fiduciary's own grievance process. None of the DPDP obligations compared here is in force as at 29 September 2026: Consent Manager registration under Rule 4 and section 6(9) is computed to commence 13 November 2026 and the rest 13 May 2027, interpretation until officially confirmed, and the GDPR positions are orientation pointers to the official EUR Lex text rather than claims to rely on. A GDPR programme is a strong starting point, but it does not satisfy DPDP by default.

Full answer with sources →

Does the DPDP framework require data localisation, and can personal data be transferred outside India?

Once Rule 15 commences, transfer is permitted by default on this site's reading. Rule 15 says personal data processed under the Act may be transferred outside the territory of India, subject to meeting requirements the Central Government may specify by general or special order about making that data available to a foreign State, or to any person or entity under the control of or any agency of such a State. Section 16(1), once in force, is a separate power to restrict transfer to notified countries, which this site reads as a negative list rather than an approved list; no such notification appears in MeitY's document library as enumerated on 7 October 2026. The common claim that the framework contains no localisation requirement is wrong on 1 point: once in force, Rule 13(4) will require a Significant Data Fiduciary to undertake measures to ensure that personal data specified by the Central Government, on a committee's recommendation, and the traffic data pertaining to its flow, is not transferred outside the territory of India. No such specification appears there either. Section 16(2) separately preserves any Indian law giving a higher degree of protection for, or restriction on, transfer outside India. Section 16 and Rules 13 and 15 are all in the group due 18 months after publication, computed as 13 May 2027, which is interpretation until officially confirmed.

Full answer with sources →

Roles

What are my obligations if I am a Data Processor under the DPDP Act?

DPDP does not expressly say A Data Processor shall. Data Processor appears 9 times in the DPDP Act 2023 and 6 times in the English text of the DPDP Rules 2025, plurals included. Section 2(k) is a definition, not a duty. Among the other occurrences, the operative duties are framed on the Data Fiduciary. Section 4(1), not yet in force, uses the wider word person, and section 2(s) includes a company, so whether it directly binds a processor acting on instructions is an interpretation question rather than an express processor duty. Current CERT In and SPDI obligations depend on their own entity, incident and data scope. When section 8(2) commences, its valid contract rule applies only where the processor is involved in an activity related to offering goods or services to Data Principals. Rule 6(1)(f) will require an appropriate security safeguards provision wherever applicable. The 18 month groups compute to 13 May 2027. Government records disagree between a 13 and 14 November 2025 publication basis, and the instruments do not state how to count the period, so the date may fall as late as 15 May 2027. These dates remain interpretation until officially confirmed.

Full answer with sources →

What is the difference between a Data Fiduciary and a Data Processor?

A Data Fiduciary is any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data. A Data Processor is any person who processes personal data on behalf of a Data Fiduciary. That is the test, and it turns on decision rather than possession: nothing in either definition asks who holds the data, whose servers it sits on, who signed the contract or who is larger. On our reading, the roles attach to a processing activity and not to a company, so one organisation can be a Data Fiduciary for its own customers and a Data Processor for its clients' data at the same time. Once in force, section 8(1) makes the Data Fiduciary responsible for complying with the Act in respect of any processing undertaken by it or on its behalf by a Data Processor, irrespective of any agreement to the contrary, so the label decides who answers for the processing but never moves the responsibility. Section 2, which carries both definitions, has been in force since 13 November 2025. Section 8, which carries the duties that make the distinction bite, sits in the 18 month commencement group, computed as 13 May 2027, which is interpretation until officially confirmed.

Full answer with sources →

Vendors

What clauses need to be included in a Data Processing Agreement (DPA) under the DPDP Act?

Not yet. When the relevant provisions commence, section 8(2) will permit a Data Fiduciary to involve a Data Processor only under a valid contract when the processing is on its behalf for an activity related to offering goods or services to Data Principals. Rule 6(1)(f) is the only express content requirement found for that fiduciary to processor contract: wherever applicable, it must contain an appropriate provision for taking reasonable security safeguards. Sections 6(6), 8(1) and 8(7) place duties on the fiduciary; contract terms can operationalise them, but those sections do not prescribe clauses. Instructions, confidentiality, subprocessor approval, processor audit rights, return, indemnity and a processor notice window are recommendations, not express DPA terms. Neither instrument fixes a processor to fiduciary breach deadline. Rule 7 instead places the without delay and 72 hour Board duties on the fiduciary. Section 17 can disapply some Act duties, while sections 8(1) and 8(5) survive a section 17(1) route. The operative contract conditions and fiduciary duties discussed are in 18 month groups. This site computes 13 May 2027 and treats 15 May 2027 as the outer date because official publication records and counting can each move the date by a day. Both dates are interpretation until officially confirmed.

Full answer with sources →

Do I need a contract before engaging a Data Processor under DPDP?

Not yet. When section 8(2) commences, a Data Fiduciary may involve a Data Processor only under a valid contract where the processing is on its behalf for an activity related to offering goods or services to Data Principals. Section 17 can change whether that condition applies. Rule 6(1)(f) is the 1 express contract content requirement found in the Act and English Rules: wherever applicable, the contract must contain an appropriate provision for taking reasonable security safeguards. Section 8(1) keeps the fiduciary responsible for processing undertaken on its behalf, and section 8(5) remains applicable under a section 17(1) route. Erasure, retention, breach support, instructions, audit, return and liability can be sensible contract topics, but the Act and Rules do not prescribe them as those Data Processor contract terms. No processor to fiduciary breach deadline is fixed; Rule 7 instead places its clocks on the fiduciary. The operative condition and duties discussed sit in 18 month commencement groups. This site computes 13 May 2027 and treats 15 May 2027 as the outer date because publication records and counting can each move the date by 1 day. Both dates are interpretation until officially confirmed.

Full answer with sources →

Compliance

Is there an official DPDP certification?

No. The word certification appears 0 times in the DPDP Act 2023 and 0 times in the DPDP Rules 2025, and no provision in either lets a certificate stand in for compliance. The 1 place the Rules use the word certified is paragraph 9 of Part A of the First Schedule, which requires an applicant for registration as a Consent Manager to have its consent platform independently certified against standards the Data Protection Board may publish. The Act's own uses of certificate, in section 7(b) and section 40(2)(e), mean certificates the State issues to a person. What the Rules require instead is a Data Protection Impact Assessment and an audit once in every period of 12 months for a Significant Data Fiduciary under Rule 13, and audit mechanisms for a Consent Manager under Part B of the First Schedule. The 1 Indian data protection instrument that does name certification is rule 8(4) of the SPDI Rules 2011, still in force as at 18 October 2026, which works with IS/ISO/IEC 27001. Verified against the Gazette texts on 18 October 2026.

Full answer with sources →

Who must appoint a Data Protection Officer under the DPDP Act?

Once section 10 is in force and subject to section 17, a Data Fiduciary or class notified as significant must appoint a Data Protection Officer. Section 10(2)(a) requires the individual to represent the Significant Data Fiduciary under the Act, be based in India, be responsible to its Board of Directors or similar governing body, and be the contact point for grievance redressal. Section 8(9) and Rule 9 separately require a Data Fiduciary, subject to section 17, to publish the business contact information of the officer, if applicable, or an alternative person who can answer processing questions, prominently on its website or app and in every rights response. Reading "if applicable" as the section 10 officer is this site's interpretation. Sections 17(1) and 17(2) disapply both duties for covered processing, but the text does not explain how relief tied to particular processing affects the appointment duty for the whole organisation where the same fiduciary also conducts other processing. Section 17(3) can disapply section 10 for notified Data Fiduciaries or classes; section 17(5) can temporarily disapply any provision for specified Data Fiduciaries or classes. At 26 October 2026, no designation notification was located in this site's registry, timeline or the 19 DPDP records within MeitY's 1,615 record enumeration. The eGazette was not checked, so this is not a certified negative. The duties commence on a computed 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

What are the essential compliance requirements for a business under the DPDP Act?

A business that determines why and how digital personal data is processed is a Data Fiduciary. Its core duties: process only on consent or a section 7 legitimate use (section 4), give a Rule 3 notice with every consent request (section 5), meet the section 6 consent standard, and carry the section 8 obligations, including valid processor contracts, completeness, accuracy and consistency where data is likely to feed a decision that affects the individual or be disclosed to another Data Fiduciary, security safeguards detailed by Rule 6, breach intimation to affected individuals and the Board with detailed Board information within 72 hours, or such longer period as the Board allows on a written request, under Rule 7, and erasure when consent is withdrawn or the purpose is spent, unless retention is necessary for compliance with law. Add the section 8(9) duty to publish a contact, with the Rule 9 mechanics, rights handling under Rule 14, whose sub rule (3), on our reading printed with a word missing, ties a reasonable period not exceeding 90 days to responding to grievances, section 9 children's duties, section 10 Significant Data Fiduciary duties where notified, and the section 16 and Rule 15 position on transfers outside India. Not 1 of these duties is in force: read as at 29 September 2026, they all sit in 18 month commencement groups computed at 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

Who needs a data protection audit under the DPDP Act and what must it cover?

Once section 10 and Rule 13 are in force, only a Significant Data Fiduciary, meaning a Data Fiduciary or class notified by the Central Government under section 10, must be audited. Section 10(2)(b) requires it to appoint an independent data auditor who shall evaluate its compliance in accordance with the provisions of the Act, and section 10(2)(c) adds a periodic data audit alongside the periodic Data Protection Impact Assessment, the words data audit having replaced audit in sub clause (ii) by the Removal of Difficulties Order, S.O. 5458(E), in Gazette issue No. 5248, whose printed masthead is dated 6 October 2026. Rule 13 sets the cadence: a DPIA and an audit once in every period of 12 months from notification, with a report containing significant observations furnished to the Data Protection Board. The report carries significant observations and not material observations: the word material appears in neither instrument in connection with it. Neither section 10 nor Rule 13, as published on 13 November 2025, prescribes auditor qualifications, an audit standard or a report format. Section 10 and Rule 13 commence on the computed date of 13 May 2027, interpretation until officially confirmed, and no notification of a Significant Data Fiduciary has been located in MeitY's published document library or this site's source registry as of 7 October 2026.

Full answer with sources →

What are the additional obligations of a Significant Data Fiduciary under the DPDP Act?

Once section 10 is in force, section 10(2) adds 3 duties for a Data Fiduciary or class the Central Government notifies as significant. First, appoint a Data Protection Officer who represents the organisation, is based in India, is responsible to the board of directors or similar governing body, and is the contact point for grievance redressal. Second, appoint an independent data auditor to evaluate compliance with the Act. Third, undertake periodic Data Protection Impact Assessments and periodic data audits, the wording since the Removal of Difficulties Order, S.O. 5458(E), in Gazette issue No. 5248, whose printed masthead is dated 6 October 2026. Rule 13 turns periodic into a cycle of once every 12 months from notification, requires the person conducting the DPIA and audit to report significant observations to the Data Protection Board, adds due diligence over algorithmic software, and enables localisation of specified personal data. No notification of a Significant Data Fiduciary has been located in MeitY's published document library or this site's source registry as of 7 October 2026, and section 10 and Rule 13 commence on the computed date 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

Who must conduct a Data Protection Impact Assessment (DPIA) under the DPDP Act?

Once section 10 and Rule 13 are in force, only a Significant Data Fiduciary, meaning a Data Fiduciary or class of Data Fiduciaries notified by the Central Government under section 10, must conduct a Data Protection Impact Assessment. Section 10(2)(c)(i) defines the DPIA as a process comprising a description of the rights of Data Principals and the purpose of processing of their personal data, assessment and management of the risk to those rights, and such other matters as may be prescribed. Rule 13 requires the DPIA and an audit once in every period of 12 months from notification, and a report containing significant observations must be furnished to the Data Protection Board of India. There is no high risk trigger for other Data Fiduciaries: an organisation that has not been notified has no DPIA duty under the DPDP Act. Section 10 and Rule 13 commence on 13 May 2027, a computed date that is interpretation until officially confirmed, and no notification of a Significant Data Fiduciary has been located in MeitY's published document library or this site's source registry as of 7 October 2026.

Full answer with sources →

Does the DPDP Act require employee consent for HR data processing?

No DPDP consent requirement is operative today. Once section 7(i) commences, a Data Fiduciary may process personal data without consent where the purpose fits its employment ground. The clause covers purposes of employment and purposes related to safeguarding the employer from loss or liability, followed by the examples it prints. Payroll, attendance, leave and similar core administration are not listed; treating them as employment purposes is this site's interpretation. The ground is purpose based, not a blanket for every staff record. Processing must first fall within section 3, and other section 7 uses, section 17 routes and applicable laws can change the analysis. Section 7(i) does not itself disapply section 8. Section 17(1), however, can disapply most of Chapter II for the cases it names; sections 8(1) and 8(5) survive that route. Sections 7, 8 and 17 are in the 18 month group. This site computes 13 May 2027; the publication date and counting uncertainties could move it to 15 May 2027. These dates are interpretation until officially confirmed.

Full answer with sources →

How can a small business comply with the DPDP Act?

Work 10 steps before the main obligations commence on the computed date of 13 May 2027, interpretation until officially confirmed: check the Act applies to you under section 3, map what personal data you hold and why, assign each purpose a ground under section 4 (consent or a section 7 legitimate use), build the Rule 3 notice, make consent meet section 6, set security safeguards per Rule 6, prepare the Rule 7 breach workflow, set retention and erasure under section 8(7) and Rule 8, stand up rights handling and grievance redressal, where Rule 14(3) names 90 days without stating what they cap, and put a valid contract behind every Data Processor that processes personal data on your behalf, under section 8(2). There is no small business exemption in the Act's application section, though section 17(3), in the group computed to commence 13 May 2027, interpretation until officially confirmed, lets the Central Government notify certain Data Fiduciaries or classes, including startups, to whom section 5, sections 8(3) and 8(7), and sections 10 and 11 shall not apply.

Full answer with sources →

What does a CTO need to build for DPDP compliance?

The obligations belong to your organisation, not to the CTO, but engineering usually leads the security safeguards, the retention and erasure timers with the 48 hour warning where the Third Schedule applies, the minimum 1 year log retention, breach detection, and the product surfaces for consent withdrawal and rights requests. Most CTO owned work depends on inputs from legal and compliance, so run it as one company plan with explicit dependencies rather than an engineering side quest. None of the rules behind this list is in force as at 29 September 2026: Rules 3, 6, 7, 8 and 14 sit in the group computed to commence 13 May 2027, interpretation until officially confirmed.

Full answer with sources →

How should a startup approach DPDP compliance?

Start with applicability and role, not company size. Section 17(3) lets the Central Government, having regard to the volume and nature of personal data processed, notify certain Data Fiduciaries or classes, including qualifying startups, to whom section 5, sections 8(3) and 8(7), and sections 10 and 11 shall not apply, but it grants none of that relief by itself. Map data flows, purposes, systems, processors and owners, then prepare the controls that apply. Rule 8(1)'s fixed 3 year periods apply only to the Third Schedule classes, purposes and thresholds. This site reads Rule 8(2)'s 48 hour warning as following those periods, but Rule 8(3) also ends in erasure, so a wider reading remains open. The principal operational provisions in sections 3 to 17, apart from section 6(9), are in the 18 month group. Rules 3 and 5 to 16 are in the corresponding Rules group. Both dates are computed as 13 May 2027, interpretation until officially confirmed. Until then, treat this as preparation rather than duties already in force.

Full answer with sources →

What is a Significant Data Fiduciary and is there a user or revenue threshold?

A Significant Data Fiduciary is a Data Fiduciary or class the Central Government may notify under section 10 once it is in force. Section 10 prints no automatic user count, revenue figure or employee number. Instead, its open assessment includes 6 named factors: data volume and sensitivity, risk to Data Principal rights, potential impact on India's sovereignty and integrity, risk to electoral democracy, security of the State, and public order. The Government may consider other relevant factors too, so the list is not a self assessment formula. Section 10 commences on a computed 13 May 2027, interpretation until officially confirmed. No designation notification was located in this site's registry or timeline or among the 19 DPDP records in MeitY's 1,615 record library enumeration on 26 October 2026; the eGazette was not checked, so this is not a certified negative. A notified fiduciary would face additional obligations under section 10 and Rule 13.

Full answer with sources →

Penalties

What did the Jan Vishwas (Amendment of Provisions) Act, 2023 change in the Information Technology Act, 2000?

On the Gazette prints on file, read as at 6 September 2026: entry 32 of the Schedule to the Jan Vishwas (Amendment of Provisions) Act, 2023 amends the Information Technology Act, 2000 in 11 lettered limbs carrying 16 directions, which the India Code consolidated print of that Act records as taking effect on 30 November 2023. In 5 provisions the sanction stops being imprisonment and becomes a monetary penalty, but in 2 of those 5, section 33(2) and section 68(2), the words shall be guilty of an offence survive untouched, so on this site's reading decriminalisation is exact for 3 of the 5 and an approximation for the other 2. All 3 money figures in section 44 are multiplied by 10, the section 70B(7) fine ceiling for failing to comply with a CERT In direction goes from one lakh to one crore while its imprisonment limb is untouched, and section 66A, struck down by the Supreme Court in 2015, is omitted from the Act. Entry 32 does not name section 43A, section 43 or the SPDI Rules 2011, and the Jan Vishwas Act 2023 does not mention the Digital Personal Data Protection Act, 2023 anywhere in its 72 pages. A second Jan Vishwas Act, Act No. 8 of 2026, does not amend the Information Technology Act, 2000 either: the strings Information Technology and 21 of 2000 appear 0 times across its whole 186 page print, searched on 6 September 2026.

Full answer with sources →

How does the Data Protection Board handle complaints and impose penalties?

Section 27, which is not in force yet, lists 5 triggers, including a Data Principal's complaint. Under section 28 the Board is, as far as practicable, a digital office, decides whether there are sufficient grounds, then inquires following the principles of natural justice. Rule 19(9), in force since 13 November 2025 under Rule 1(2) though the Board inquiries it times have not commenced, allows 6 months, extendable by 3 months at a time. Section 33(2) lists 7 matters for sizing a penalty. Appeal lies to the TDSAT within 60 days; neither text requires a deposit, checked 24 August 2026. Read as at 3 September 2026 not 1 step of this pipeline under the Act is in force: section 13, section 27 except clause (1)(d) and sections 28 to 34 all sit in the 18 month group of notification G.S.R. 843(E), computed 13 May 2027, interpretation until officially confirmed. Clause (1)(d) is in the 1 year group, computed 13 November 2026, likewise interpretation until officially confirmed.

Full answer with sources →

What are the penalties under the DPDP Act 2023?

Once section 33 is in force, the Data Protection Board may impose a monetary penalty specified in the Act's Schedule if, on concluding an inquiry, it determines a breach of the Act or Rules is significant, after giving the person an opportunity of being heard. Each figure is a maximum: 250 crore rupees for the section 8(5) obligation to take reasonable security safeguards; 200 crore rupees each for the section 8(6) breach intimation obligation and for the additional obligations relating to children under section 9; 150 crore rupees for a Significant Data Fiduciary's additional obligations under section 10; 10,000 rupees for the duties under section 15; 50 crore rupees for any other provision of the Act or Rules; and, for breach of a voluntary undertaking accepted under section 32, up to the cap for the breach whose section 28 proceedings were instituted. Sections 8 to 10, 15 and 28 to 34 are in the 18 month group of G.S.R. 843(E), computed at 13 May 2027, interpretation until officially confirmed; the Schedule commencing with section 33 is this site's reading. At 24 October 2026 no penalty can be imposed because section 33 has not commenced. Separately, no appointment of a Chairperson or Member was located in MeitY's published document library through 24 October 2026. The wider 28 August 2026 search of official channels was not repeated and the eGazette search was not queried, so the appointment finding is not a certified negative.

Full answer with sources →

What is a voluntary undertaking under the DPDP Act?

A voluntary undertaking is a commitment that, once section 32 is in force, the Data Protection Board may accept from any person at any stage of a proceeding under section 28. It can commit the person to take an action within a set time, to refrain from an action, or to publicise the undertaking, and the Board can vary its terms with the person's consent. Acceptance bars proceedings under the Act as regards the contents of the undertaking. If the person then fails to adhere to any term, the failure is deemed a breach of the Act and the Board may, after giving the person an opportunity of being heard, proceed in accordance with section 33; the Schedule caps that penalty at the amount applicable to the breach for which the original proceedings were instituted. Section 32 sits in the commencement group due 18 months from the notification gazette, computed as 13 May 2027, which is interpretation until officially confirmed.

Full answer with sources →

Official documents

What did the DPDP Removal of Difficulties Order, 2026 change?

The Digital Personal Data Protection (Removal of Difficulties) Order, 2026, S.O. 5458(E), is dated 5 October 2026 and printed in Gazette issue No. 5248, whose printed masthead is dated 6 October 2026. The Central Government made it under section 43(1) of the DPDP Act, and paragraph 1(2) brings it into force on the date of its publication in the Official Gazette. It makes 2 substitutions in the Act. Paragraph 2(i) adds the word of to section 9(1), which as modified by S.O. 5458(E) reads any personal data of a child or of a person with disability who has a lawful guardian. Paragraph 2(ii) changes periodic audit in section 10(2)(c)(ii) to periodic data audit, the words clause (b) already used. Its recitals call the difficulties textual, editorial in nature. The Order does not change when sections 9 and 10 come into force: both are in the 18 month group, which on the printed Gazette date computes to 13 May 2027, an interpretation until officially confirmed. It names no rule, so the DPDP Rules 2025 are untouched by it. Under section 43(2) no such order may be made after 3 years from commencement, and every order must be laid before each House of Parliament under section 43(3); no record of this one being laid is held in this site's source registry as at 10 October 2026.

Full answer with sources →

What did corrigenda G.S.R. 892(E) change in the DPDP Rules 2025?

Corrigenda G.S.R. 892(E), notified 10 December 2025 and published in Gazette issue No. 806 of 11 December 2025, corrects notification G.S.R. 846(E) at 5 places: Gazette pages 24, 29, 32, 34 and 38. Those 5 items carry 8 separate corrections. The corrigenda names pages and lines and never names a rule; read against the Gazette print they land on Rule 1(3), Rule 1(4), Rule 13(5), Rule 23(1), the First Schedule and the Fourth Schedule. 7 of the 8 are substitutions, a named string replaced by another. The 8th, item (v)(b), names a range of lines and a range of labels rather than a string, and this site reads it as a renumbering instruction: the Fourth Schedule Note as printed lists 2 items lettered (a), and on that reading it runs (a) to (g) after the corrigenda, which is an interpretation until officially confirmed. No period in Rule 1 changes, and on the same reading no obligation is added or removed.

Full answer with sources →

Enforcement

Is the Data Protection Board of India operational for DPDP complaints?

On the official record tracked here, no. The Board exists in law, but 2 separate gaps prevent it from operating as the Act's complaint and enforcement body. First, no appointment of a Chairperson or Member has been located. G.S.R. 844(E) established the Board on 13 November 2025, MeitY invited applications on 6 May 2026, and the Lok Sabha answer of 12 August 2026 named no appointee when asked about appointments. On 7 October 2026, the Union's counsel told the High Court of Kerala that the Board had been constituted but had yet to be made functional. MeitY's published document library, enumerated on 21 October 2026 and rechecked on 24 October 2026, contains the same 19 DPDP records as the archived baseline, and no record title names an appointment made. This is a scoped search result, not a certified statement that no appointment exists. Second, most of the Board's statutory powers are not in force. G.S.R. 843(E) commenced sections 18 to 26 on publication, but placed section 27, apart from section 27(1)(d), and sections 28 to 34 in the 18 month group, computed as 13 May 2027, interpretation until officially confirmed. Section 27(1)(d) and Rule 4 are in the 1 year group, computed as 13 November 2026, interpretation until officially confirmed. Neither is an individual complaint route. Appointing members alone would therefore not open the complaint routes in section 27(1)(b) and (c).

Full answer with sources →

Every answer links to an article whose legal claims carry exact official source references. If your question is missing, the site search covers the Act, the Rules and every tool, and the corrections page is the fastest way to tell us what to add.