Live 20 practitioner certifications live · Free preview lessons on most courses Back to main site →

Why you can trust this course

We don't ask you to take our word for it. Every claim in every lesson is anchored to a Section, Rule, or judgment. This page is the master register of every authority we cite.

Legal basis snapshot: DPDP Act 2023 (No. 22 of 2023, assented 11 August 2023). DPDP Rules 2025 notified 13 November 2025 via Gazette Notifications G.S.R. 843(E), 844(E), 845(E) and 846(E). Sectoral overlays as in force on 5 October 2026: CERT-In Directions No. 20(3)/2022-CERT-In (28 April 2022); RBI Draft Data Governance Framework (15 July 2026, consultation closed 17 August 2026); SEBI CSCRF (20 August 2024, SEBI AI Vulnerability Detection Advisory 5 May 2026); IRDAI Information and Cyber Security Guidelines 2026 (6 April 2026); Telecom Cyber Security Rules 2024 (21 November 2024); Aadhaar Data Security Regulations 2016. Constitutional context: Puttaswamy v. Union of India (2017) 10 SCC 1.

How this DPDP Implementation Practitioner — 90 Days to Audit-Ready register is built

This trust page is the citation register for the DPDP Implementation Practitioner — 90 Days to Audit-Ready course. It cites 39 authorities across 7 statutory instruments, drawn from the legal basis snapshot above (DPDP Act 2023 (No. 22 of 2023, assented 11 August 2023). DPDP Rules 2025 notified 13 November 2025 via Gazette Notifications G.S.R. 843(E), 844(E), 845(E) and 846(E). Sectoral overlays as in force on 5 October 2026: CERT-In Directions No. 20(3)/2022-CERT-In (28 April 2022); RBI Draft Data Governance Framework (15 July 2026, consultation closed 17 August 2026); SEBI CSCRF (20 August 2024, SEBI AI Vulnerability Detection Advisory 5 May 2026); IRDAI Information and Cyber Security Guidelines 2026 (6 April 2026); Telecom Cyber Security Rules 2024 (21 November 2024); Aadhaar Data Security Regulations 2016. Constitutional context: Puttaswamy v. Union of India (2017) 10 SCC 1.).

Primary sources: DPDP Act 2023 (22 entries), DPDP Rules 2025 (10 entries), CERT-In Directions 2022 (2 entries).

Every claim in every DPDP Implementation Practitioner — 90 Days to Audit-Ready lesson traces back to a Section, Rule, or judgment listed below. If a lesson references a specific obligation, click the [Lx-Cy] marker in that lesson to jump to the verbatim text in the register.

Our verification promise

  1. Every factual claim has a source. If we say "Section 9 allows a three-month limitation period", you can click the [Lx-Cy] marker next to it and read the verbatim text of Section 9 of the Sexual Harassment of Women at Workplace Act, 2013.
  2. Every source is on this page. Below you will find every Section, Rule and judgment we have relied on, grouped by category, with the verbatim text we hold in our register.
  3. Every source has a public link. Wherever an authoritative public link exists (India Code, the official court website, a reputable law-reports portal), we link to it.
  4. Bug bounty for errors. If you find a factual error in any lesson, write to [email protected] with the lesson, the claim and the corrected source. We will credit your account ₹1,000 for the first report of any verifiable error, ₹5,000 for a substantial error.
12
modules
63
lessons
39
cited authorities
recent
last reviewed

The full citation register

Every authority used in any lesson appears below. Click a row to expand the verbatim text.

CERT-In 6-hour Rule , CERT-In Directions 2022 six-hour incident reporting 28 Apr 2022
Plain summary: CERT-In Directions No. 20(3)/2022-CERT-In dated 28 April 2022, effective 27 June 2022. Direction (ii): every service provider, intermediary, data centre, body corporate and Government organisation must mandatorily report cyber incidents of the type specified in Annexure I to CERT-In within six hours of noticing or being brought to notice about such incidents. For an Indian entity handling EU personal data, the 6-hour CERT-In clock runs from detection in parallel with the 72-hour DPDP Rule 7 clock and the 72-hour GDPR Art 33 clock. All three are separate obligations; the incident-response runbook fires all three from a single incident record.
CERT-In Directions No. 20(3)/2022-CERT-In dated 28 April 2022. Direction (ii): Any service provider, intermediary, data centre, body corporate and Government organisation shall mandatorily report cyber incidents as mentioned in Annexure I to CERT-In within six hours of noticing such incidents or being brought to notice about such incidents. Direction (iii): Enable logs of all their ICT systems and maintain them securely for a rolling period of 180 days within the Indian jurisdiction.
Direction (ii) , CERT-In 6-hour cyber incident reporting 28 Apr 2022
Plain summary: Any service provider, intermediary, data centre, body corporate or Government organisation must mandatorily report cyber incidents to CERT-In within 6 hours of noticing them. Runs in parallel with DPDP Rule 7 breach notification (72-hour DPB report). A single incident affecting personal data triggers both clocks.
Any service provider, intermediary, data centre, body corporate and Government organisation shall mandatorily report cyber incidents as mentioned in Annexure I to CERT-In within 6 hours of noticing such incidents or being brought to notice about such incidents.

Section 17 , Exemptions
Plain summary: Section 17(1) switches off Chapter II (except 8(1) and 8(5)), Chapter III and section 16 for six listed cases. Section 17(2): the Act does not apply to notified State instrumentalities, or to research, archiving or statistics if no decision specific to a Data Principal is taken.
Section 27 , Functions of Data Protection Board
Plain summary: On a breach intimation the Board directs urgent remedial measures and inquires. On complaints, references or court directions it inquires into breaches by Data Fiduciaries or Consent Managers and imposes penalty. It may issue directions after a hearing and reasons. Digital office is section 28.
Section 29 , Appeal to Appellate Tribunal
Plain summary: Any person aggrieved by an order or direction of the Board may prefer an appeal to the Telecom Disputes Settlement and Appellate Tribunal (designated as the Appellate Tribunal). Appeal must be filed within 60 days from the receipt of the Board order.
Section 36 , Power to call for information
Plain summary: The Central Government may, for the purposes of the Act, require the Board and any Data Fiduciary or intermediary to furnish information it calls for. Commences 13 May 2027. Purposes and the non-disclosure power are in rule 23 and the Seventh Schedule.
Schedule , Penalty matrix 11 Aug 2023
Plain summary: Sets out maximum penalties: up to Rs 250 crore for failing to take reasonable security safeguards to prevent breach; up to Rs 200 crore for failing to intimate breach; up to Rs 200 crore for failing to fulfil children's data obligations; up to Rs 150 crore for SDF additional obligation breaches; up to Rs 10,000 for Data Principal duty breaches (Item 5); breach of a Board-accepted voluntary undertaking, up to the penalty for the original breach (Item 6); up to Rs 50 crore for any other breach (Item 7).
THE SCHEDULE [See section 33(1)] Penalties for breaches: 1. Breach in observing the obligation of Data Fiduciary to take reasonable security safeguards to prevent personal data breach under sub-section (5) of section 8: may extend to two hundred and fifty crore rupees. 2. Breach in observing the obligation to give the Board or affected Data Principal notice of a personal data breach under sub-section (6) of section 8: may extend to two hundred crore rupees. 3. Breach in observance of additional obligations in relation to children under section 9: may extend to two hundred crore rupees. 4. Breach in observance of additional obligations of Significant Data Fiduciary under section 10: may extend to one hundred and fifty crore rupees. 5. Breach in observance of the duties under section 15: may extend to ten thousand rupees. 6. Breach of any term of voluntary undertaking accepted by the Board under section 32: up to the extent applicable for the breach in respect of which the proceedings under section 28 were instituted. 7. Breach of any other provision of this Act or the rules made thereunder: may extend to fifty crore rupees.
Section 10 , Additional obligations of Significant Data Fiduciary 11 Aug 2023
Plain summary: Central Government may notify a Data Fiduciary as a Significant Data Fiduciary based on volume and sensitivity of data, risk, electoral democracy, security, and public order. SDF must appoint a Data Protection Officer in India, an independent data auditor, and conduct periodic DPIAs and audits.
10. (1) The Central Government may notify any Data Fiduciary or class of Data Fiduciaries as Significant Data Fiduciary, on the basis of an assessment of such relevant factors as it may determine, including, (a) the volume and sensitivity of personal data processed; (b) risk to the rights of Data Principal; (c) potential impact on the sovereignty and integrity of India; (d) risk to electoral democracy; (e) security of the State; and (f) public order. (2) The Significant Data Fiduciary shall, (a) appoint a Data Protection Officer who shall represent the Significant Data Fiduciary under the provisions of this Act. The Data Protection Officer shall, (i) be based in India; (ii) be an individual responsible to the Board of Directors or similar governing body of the Significant Data Fiduciary; and (iii) be the point of contact for the grievance redressal mechanism under the provisions of this Act; (b) appoint an independent data auditor to carry out data audit, who shall evaluate the compliance of the Significant Data Fiduciary in accordance with the provisions of this Act; and (c) undertake the following other measures, namely:, (i) periodic Data Protection Impact Assessment, which shall be 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 the rights of the Data Principals, and such other matters regarding such process as may be prescribed; (ii) periodic audit; and (iii) such other measures, consistent with the provisions of this Act, as may be prescribed.
Section 11 , Right to access information about personal data 11 Aug 2023
Plain summary: Data Principal has the right to obtain from the Data Fiduciary a summary of personal data being processed, the processing activities, and the identities of Data Fiduciaries and Data Processors with whom personal data has been shared. Clauses (b) and (c) do not apply to sharing with a Data Fiduciary authorised by law, on a written request for prevention, detection or investigation of offences or cyber incidents, or for prosecution or punishment of offences.
11. (1) The Data Principal shall have the right to obtain from the Data Fiduciary to whom she has previously given consent, including consent as referred to in clause (a) of section 7, for processing of personal data, upon making to it a request in such manner as may be prescribed,, (a) a summary of personal data which is being processed by such Data Fiduciary and the processing activities undertaken by that Data Fiduciary with respect to such personal data; (b) the identities of all other Data Fiduciaries and Data Processors with whom the personal data has been shared by such Data Fiduciary, along with a description of the personal data so shared; and (c) any other information related to the personal data of such Data Principal and its processing, as may be prescribed. (2) Nothing contained in clause (b) or clause (c) of sub-section (1) shall apply in respect of the sharing of any personal data by the Data Fiduciary with any other Data Fiduciary authorised by law to obtain such personal data, where such sharing is pursuant to a request made in writing by such other Data Fiduciary for the purpose of prevention or detection or investigation of offences or cyber incidents, or for prosecution or punishment of offences.
Section 12 , Right to correction and erasure of personal data 11 Aug 2023
Plain summary: Data Principal has the right to correction, completion, updating, and erasure of personal data for the processing of which she has previously given consent. The Data Fiduciary shall erase personal data unless retention is required by law.
12. (1) The Data Principal shall have the right to correction, completion, updating and erasure of her personal data for the processing of which she has previously given consent, including consent as referred to in clause (a) of section 7, in accordance with any requirement or procedure under any law for the time being in force. (2) A Data Fiduciary shall, upon receiving a request for correction, completion or updating from a Data Principal,, (a) correct the inaccurate or misleading personal data; (b) complete the incomplete personal data; and (c) update the personal data. (3) The Data Principal shall make a request in such manner as may be prescribed for erasure of her personal data to the Data Fiduciary, who shall, upon receipt of such request, erase her personal data unless retention of the same is necessary for the specified purpose or for compliance with any law for the time being in force.
Section 13 , Right of grievance redressal 11 Aug 2023
Plain summary: Data Principal has the right of readily available means of grievance redressal provided by a Data Fiduciary or Consent Manager. The Data Fiduciary must respond within the prescribed time. The Data Principal shall exhaust this remedy before approaching the Board.
13. (1) A Data Principal shall have the right to have readily available means of grievance redressal provided by a Data Fiduciary or Consent Manager in respect of any act or omission of such Data Fiduciary or Consent Manager regarding the performance of its obligations in relation to the personal data of such Data Principal or the exercise of her rights under the provisions of this Act and the rules made thereunder. (2) The Data Fiduciary or Consent Manager shall respond to any grievances referred to in sub-section (1) within such period as may be prescribed from the date of its receipt for all or any class of Data Fiduciaries. (3) The Data Principal shall exhaust the opportunity of redressing her grievance under this section before approaching the Board.
Section 15 , Duties of Data Principal 11 Aug 2023
Plain summary: Data Principal shall comply with applicable law; not impersonate; not suppress material information; not register false or frivolous grievances; and furnish only authentic information when exercising the right to correction or erasure.
15. A Data Principal shall, (a) comply with the provisions of all applicable laws for the time being in force while exercising rights under the provisions of this Act; (b) ensure not to impersonate another person while providing her personal data for a specified purpose; (c) ensure not to suppress any material information while providing her personal data for any document, unique identifier, proof of identity or proof of address issued by the State or any of its instrumentalities; (d) ensure not to register a false or frivolous grievance or complaint with a Data Fiduciary or the Board; and (e) furnish only such information as is verifiably authentic, while exercising the right to correction or erasure under the provisions of this Act or the rules made thereunder.
Section 16 , Processing of personal data outside India 11 Aug 2023
Plain summary: Central Government may by notification restrict the transfer of personal data by a Data Fiduciary for processing to a country or territory outside India.
16. (1) The Central Government may, by notification, restrict the transfer of personal data by a Data Fiduciary for processing to such country or territory outside India as may be so notified. (2) Nothing contained in this section shall restrict the applicability of any law for the time being in force in India that provides for a higher degree of protection for or restriction on transfer of personal data by a Data Fiduciary outside India in relation to any personal data or Data Fiduciary or class thereof.
Section 2 , Definitions 11 Aug 2023
Plain summary: Defines key terms including Data Principal, Data Fiduciary, Data Processor, personal data, processing, consent, child, gain, harm, Significant Data Fiduciary, and the Board.
2. In this Act, unless the context otherwise requires, the following definitions apply (selected, abridged for reference; consult the Act for the complete list): (f) "child" means an individual who has not completed the age of eighteen years; (i) "Data Fiduciary" means any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data; (j) "Data Principal" means the individual to whom the personal data relates and where such individual is, (i) a child, includes the parents or lawful guardian of such a child; (ii) a person with disability, includes her lawful guardian, acting on her behalf; (k) "Data Processor" means any person who processes personal data on behalf of a Data Fiduciary; (t) "personal data" means any data about an individual who is identifiable by or in relation to such data; (x) "processing" in relation to personal data, means a wholly or partly automated operation or set of operations performed on digital personal data, and includes operations such as collection, recording, organisation, structuring, storage, adaptation, retrieval, use, alignment or combination, indexing, sharing, disclosure by transmission, dissemination or otherwise making available, restriction, erasure or destruction; (y) "she" in relation to an individual includes the reference to such individual irrespective of gender; (z) "Significant Data Fiduciary" means any Data Fiduciary or class of Data Fiduciaries as may be notified by the Central Government under section 10.
Section 2(u) , Definition of personal data breach 11 Aug 2023
Plain summary: A personal data breach is any unauthorised processing, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability.
2. (u) "personal data breach" means any unauthorised processing of personal data or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises the confidentiality, integrity or availability of personal data;
Section 3 , Application of the Act 11 Aug 2023
Plain summary: Applies to processing of digital personal data within India, and to processing outside India in connection with offering goods or services to Data Principals in India. Excludes personal/domestic use and certain other cases.
3. Subject to the provisions of this Act, it shall, (a) apply to the processing of digital personal data within the territory of India where the personal data is collected, (i) in digital form; or (ii) in non-digital form and digitised subsequently; (b) also apply to processing of digital personal data outside the territory of India, if such processing is in connection with any activity related to offering of goods or services to Data Principals within the territory of India; (c) not apply to, (i) personal data processed by an individual for any personal or domestic purpose; and (ii) personal data that is made or caused to be made publicly available by, (A) the Data Principal to whom such personal data relates; or (B) any other person who is under an obligation under any law for the time being in force in India to make such personal data publicly available.
Section 33 , Penalty for breach of provisions 11 Aug 2023
Plain summary: After an inquiry finds a breach significant, the Board may impose the Schedule penalty after giving an opportunity of being heard. It weighs the seven factors in Section 33(2): nature, gravity and duration; type of data; repetition; gain or loss avoided; mitigation; proportionality; and impact on the person.
33. (1) If the Board determines on conclusion of an inquiry that breach of the provisions of this Act or the rules made thereunder by a person is significant, it may, after giving the person an opportunity of being heard, impose such monetary penalty specified in the Schedule. (2) While determining the amount of monetary penalty to be imposed under sub-section (1), the Board shall have regard to the following matters, namely:, (a) the nature, gravity and duration of the breach; (b) the type and nature of the personal data affected by the breach; (c) repetitive nature of the breach; (d) whether the person, as a result of the breach, has realised a gain or avoided any loss; (e) whether the person took any action to mitigate the effects and consequences of the breach, and the timeliness and effectiveness of such action; (f) whether the monetary penalty to be imposed is proportionate and effective, having regard to the need to secure observance of and deter breach of the provisions of this Act; and (g) the likely impact of the imposition of the monetary penalty on the person.
Section 4 , Grounds for processing personal data 11 Aug 2023
Plain summary: Personal data may be processed only for a lawful purpose, either with the Data Principal's consent or for certain legitimate uses listed in Section 7.
4. (1) A person may process the personal data of a Data Principal only in accordance with the provisions of this Act and for a lawful purpose,, (a) for which the Data Principal has given her consent; or (b) for certain legitimate uses. (2) For the purposes of this section, the expression "lawful purpose" means any purpose which is not expressly forbidden by law.
Section 5 , Notice 11 Aug 2023
Plain summary: Before or at the time of seeking consent, the Data Fiduciary must give the Data Principal a notice describing the personal data, the purpose of processing, how to exercise rights, and how to complain to the Board.
5. (1) Every request made to a Data Principal under section 6 for consent shall be accompanied or preceded by a notice given by the Data Fiduciary to the Data Principal, informing her,, (i) the personal data and the purpose for which the same is proposed to be processed; (ii) the manner in which she may exercise her rights under sub-section (4) of section 6 and section 13; and (iii) the manner in which the Data Principal may make a complaint to the Board, in such manner and as may be prescribed. (2) Where a Data Principal has given her consent to the processing of her personal data before the commencement of this Act, the Data Fiduciary shall, as soon as it is reasonably practicable, give to the Data Principal a notice informing her,, (i) the personal data and the purpose for which the same has been processed; (ii) the manner in which she may exercise her rights under sub-section (4) of section 6 and section 13; and (iii) the manner in which the Data Principal may make a complaint to the Board. (3) The Data Fiduciary shall give the Data Principal the option to access the contents of the notice referred to in sub-sections (1) and (2) in English or any language specified in the Eighth Schedule to the Constitution of India.
Section 6 , Consent 11 Aug 2023
Plain summary: Consent must be free, specific, informed, unconditional, unambiguous, and limited to the personal data necessary for the specified purpose. The Data Principal can withdraw consent at any time with comparable ease.
6. (1) The consent given by the Data Principal shall be free, specific, informed, unconditional and unambiguous with a clear affirmative action, and shall signify an agreement to the processing of her personal data for the specified purpose and be limited to such personal data as is necessary for such specified purpose. (2) Any part of consent referred in sub-section (1) which constitutes an infringement of the provisions of this Act or the rules made thereunder or any other law for the time being in force shall be invalid to the extent of such infringement. (3) Every request for consent under the provisions of this Act or the rules made thereunder shall be presented to the Data Principal in a clear and plain language, giving her the option to access such request in English or any language specified in the Eighth Schedule to the Constitution and providing the contact details of a Data Protection Officer, where applicable, or of any other person authorised by the Data Fiduciary to respond to any communication from the Data Principal for the purpose of exercise of her rights under the provisions of this Act. (4) Where consent given by the Data Principal is the basis of processing of personal data, such Data Principal shall have the right to withdraw her consent at any time, with the ease of doing so being comparable to the ease with which such consent was given. (5) The consequences of the withdrawal referred to in sub-section (4) shall be borne by the Data Principal, and such withdrawal shall not affect the legality of processing of the personal data based on consent before its withdrawal. (6) If a Data Principal withdraws her consent to the processing of personal data under sub-section (5), the Data Fiduciary shall, within a reasonable time, cease and cause its Data Processors to cease processing the personal data of such Data Principal unless such processing without her consent is required or authorised under the provisions of this Act or the rules made thereunder or any other law for the time being in force in India. (7) The Data Principal may give, manage, review or withdraw her consent to the Data Fiduciary through a Consent Manager. (8) The Consent Manager shall be accountable to the Data Principal and shall act on her behalf in such manner and subject to such obligations as may be prescribed. (9) Every Consent Manager shall be registered with the Board in such manner and subject to such technical, operational, financial and other conditions as may be prescribed. (10) Where, for the processing of personal data, the consent given by the Data Principal is the subject matter of a dispute or question relating to compliance with the provisions of this Act, it shall be for the Data Fiduciary to prove that a notice was given by it to such Data Principal and consent was given by such Data Principal to the Data Fiduciary in accordance with the provisions of this Act and the rules made thereunder.
Section 7 , Certain legitimate uses 11 Aug 2023
Plain summary: Lists situations where personal data may be processed without explicit consent, including for purposes voluntarily provided by the Data Principal, by the State for benefits and services, in medical emergencies, during disasters, and for employment-related purposes.
7. A Data Fiduciary may process personal data of a Data Principal for any of the following uses, namely:, (a) for the specified purpose for which the Data Principal has voluntarily provided her personal data to the Data Fiduciary, and in respect of which she has not indicated to the Data Fiduciary that she does not consent to the use of her personal data; (b) for the State and any of its instrumentalities to provide or issue to the Data Principal such subsidy, benefit, service, certificate, licence or permit as may be prescribed; (c) for the performance by the State or any of its instrumentalities of any function under any law for the time being in force in India or in the interest of sovereignty and integrity of India or security of the State; (d) for fulfilling any obligation under any law for the time being in force in India on any person to disclose any information to the State or any of its instrumentalities, subject to such processing being in accordance with the provisions regarding disclosure of such information in any other law for the time being in force; (e) for compliance with any judgment or decree or order issued under any law for the time being in force in India, or any judgment or order relating to claims of a contractual or civil nature under any law for the time being in force outside India; (f) for responding to a medical emergency involving a threat to the life or immediate threat to the health of the Data Principal or any other individual; (g) for taking measures to provide medical treatment or health services to any individual during an epidemic, outbreak of disease, or any other threat to public health; (h) for taking measures to ensure safety of, or provide assistance or services to, any individual during any disaster, or any breakdown of public order; (i) for the purposes of employment or those related to safeguarding the employer from loss or liability.
Section 8 , General obligations of Data Fiduciary 11 Aug 2023
Plain summary: Data Fiduciary is responsible for compliance, including by its Data Processors, with respect to processing for or on its behalf. Requires accuracy, security safeguards, breach notification, erasure when purpose served or consent withdrawn, and a grievance redressal mechanism.
8. (1) A Data Fiduciary shall, irrespective of any agreement to the contrary or failure of a Data Principal to carry out the duties provided under this Act, be responsible for complying with the provisions of this Act and the rules made thereunder in respect of any processing undertaken by it or on its behalf by a Data Processor. (2) A Data Fiduciary may engage, appoint, use or otherwise involve a Data Processor to process personal data on its behalf for any activity related to offering of goods or services to Data Principals only under a valid contract. (3) Where personal data processed by a Data Fiduciary is, (a) likely to be used to make a decision that affects the Data Principal; or (b) likely to be disclosed to another Data Fiduciary, the Data Fiduciary shall ensure its completeness, accuracy and consistency. (4) A Data Fiduciary shall implement appropriate technical and organisational measures to ensure effective observance of the provisions of this Act and the rules made thereunder. (5) A Data Fiduciary shall 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. (6) In the event of a personal data breach, the Data Fiduciary shall give the Board and each affected Data Principal, intimation of such breach in such form and manner as may be prescribed. (7) A Data Fiduciary shall, unless retention is necessary for compliance with any law for the time being in force, erase personal data, upon the Data Principal withdrawing her consent or as soon as it is reasonable to assume that the specified purpose is no longer being served, whichever is earlier, and cause its Data Processor to erase any personal data that was made available by the Data Fiduciary for processing to such Data Processor. (8) A Data Fiduciary shall publish, in such manner as may be prescribed, the business contact information of a Data Protection Officer, if applicable, or a person who is able to answer on behalf of the Data Fiduciary, the questions, if any, raised by the Data Principal about the processing of her personal data. (9) A Data Fiduciary shall establish an effective mechanism to redress the grievances of Data Principals. (10) For the purposes of this section, it is hereby clarified that a Data Fiduciary's responsibility for compliance with the provisions of this Act in respect of processing undertaken by it or on its behalf is irrespective of any contractual arrangement to the contrary between the Data Fiduciary and the Data Processor.
Section 8(7) , Erasure, unless retention is required by law 11 Aug 2023
Plain summary: A Data Fiduciary must erase personal data when consent is withdrawn or the purpose is no longer served, unless retention is necessary for compliance with any law in force, and must make its Data Processor erase it too.
8. (7) A Data Fiduciary shall, unless retention is necessary for compliance with any law for the time being in force, erase personal data, upon the Data Principal withdrawing her consent or as soon as it is reasonable to assume that the specified purpose is no longer being served, whichever is earlier, and cause its Data Processor to erase any personal data that was made available by the Data Fiduciary for processing to such Data Processor.
Section 9 , Processing of personal data of children 11 Aug 2023
Plain summary: Before processing a child's personal data, the Data Fiduciary must obtain verifiable consent of the parent or lawful guardian. Tracking, behavioural monitoring, and targeted advertising at children are prohibited unless exempted. Section 9(2) separately bars processing likely to harm a child's well-being.
9. (1) The Data Fiduciary shall, before processing any personal data of a child or a person with disability who has a lawful guardian, obtain verifiable consent of the parent of such child or the lawful guardian, as the case may be, in such manner as may be prescribed. (2) A Data Fiduciary shall not undertake such processing of personal data that is likely to cause any detrimental effect on the well-being of a child. (3) A Data Fiduciary shall not undertake tracking or behavioural monitoring of children or targeted advertising directed at children. (4) The provisions of sub-sections (1) and (3) shall not be applicable to processing of personal data of a child by such classes of Data Fiduciaries or for such purposes, and subject to such conditions, as may be prescribed. (5) The Central Government may, if satisfied that a Data Fiduciary has ensured that its processing of personal data of children is done in a manner that is verifiably safe, by notification, notify for such processing by such Data Fiduciary the age above which that Data Fiduciary shall be exempt from the applicability of all or any of the obligations under sub-sections (1) and (3) in respect of processing by that Data Fiduciary as the notification may specify.

G.S.R. 843(E) , Commencement of specific Sections of the DPDP Act 13 Nov 2025
Plain summary: Fixes dates: on publication ss.1(2), 2, 18 to 26, 35, 38 to 43, 44(1) and (3); after one year ss.6(9) and 27(1)(d); after eighteen months ss.3 to 5, 6(1) to (8) and (10), 7 to 17, 27 (rest), 28 to 34, 36, 37 and 44(2).

Fourth Schedule , Exemptions from section 9(1) and (3) 13 Nov 2025
Plain summary: Part A: health establishments and professionals, allied healthcare professionals, educational institutions, crèche operators and their transport providers, each for narrow stated processing. Part B: six purposes such as email-only accounts, real-time safety location and age confirmation.
Rule 13 , Additional obligations of Significant Data Fiduciary 13 Nov 2025
Plain summary: An SDF must do a DPIA and audit every 12 months, have the findings reported to the Board, verify that its algorithmic software is not likely to risk Data Principal rights, and keep Government-specified personal data and its traffic data in India.
13. Additional obligations of Significant Data Fiduciary. -- (1) A Significant Data Fiduciary shall, once in every period of twelve months from the date on which it is notified as such or is included in the class of Data Fiduciaries notified as such, undertake a Data Protection Impact Assessment and an audit to ensure effective observance of the provisions of this Act and the rules made thereunder. (2) A Significant Data Fiduciary shall cause the person carrying out the Data Protection Impact Assessment and audit to furnish to the Board a report containing significant observations in the Data Protection Impact Assessment and audit. (3) A Significant Data Fiduciary shall observe due diligence to verify that technical measures including algorithmic software adopted by it for hosting, display, uploading, modification, publishing, transmission, storage, updating or sharing of personal data processed by it are not likely to pose a risk to the rights of Data Principals. (4) A Significant Data Fiduciary shall undertake measures to ensure that personal data specified by the Central Government, on the basis of the recommendations of a committee constituted by it, is processed subject to the restriction that the personal data and the traffic data pertaining to its flow is not transferred outside the territory of India. (5) In this rule, "committee" means a committee constituted by the Central Government for the purpose of this rule, which shall include officials from the Ministry of Electronics and Technology and may include officials from other Ministries or Department of the Central Government.
Rule 14 , Rights of Data Principals 13 Nov 2025
Plain summary: Fiduciaries and Consent Managers must publish how to make rights requests and what identifiers are needed, publish a grievance response period of not more than 90 days, and allow nomination of one or more individuals under their terms of service.
14. Rights of Data Principals. -- (1) For enabling Data Principals to exercise their rights under the Act, the Data Fiduciary and, where applicable, the Consent Manager, shall prominently publish on its website or app, or both, as the case may be, -- (a) the details of the means using which a Data Principal may make a request for the exercise of such rights; and (b) the particulars, if any, such as the username or other identifier of such a Data Principal, which may be required to identify her under its terms of service. (2) To exercise the rights of the Data Principal under the Act, she may make a request to the Data Fiduciary to whom she has previously given consent for processing of her personal data, using the means and furnishing the particulars required by such Data Fiduciary for the exercise of such rights. (3) Every Data Fiduciary and Consent Manager shall 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 shall, for ensuring the effectiveness of the system in responding within such period, implement appropriate technical and organisational measures. (4) To exercise the rights of the Data Principal under the Act, she may, in accordance with the terms of service of the Data Fiduciary and such law as may be applicable, nominate one or more individuals, using the means and furnishing the particulars required by such Data Fiduciary for the exercise of such right. (5) In this rule, the expression "identifier" shall mean any sequence of characters issued by the Data Fiduciary to identify the Data Principal and includes a customer identification file number, customer acquisition form number, application reference number, enrolment ID, email address, mobile number or licence number that enables such identification.
Rule 15 , Transfer of personal data outside India 13 Nov 2025
Plain summary: Personal data may be transferred abroad subject to requirements the Central Government specifies by general or special order for making data available to any foreign State, or to any person or entity under its control or any agency of such a State.
15. Transfer of personal data outside the territory of India. -- Any personal data processed by a Data Fiduciary under the Act may be transferred outside the territory of India subject to the restriction that the Data Fiduciary shall meet such requirements as the Central Government may, by general or special order, specify in respect of making such personal data available to any foreign State, or to any person or entity under the control of or any agency of such a State.
Rule 3 , Notice given by Data Fiduciary to Data Principal 13 Nov 2025
Plain summary: The notice must stand alone and use clear, plain language. It must give an itemised description of the personal data, the specified purposes, and a specific description of the goods, services or uses enabled. It must give a link and the means to withdraw consent, exercise rights and complain to the Board.
3. Notice given by Data Fiduciary to Data Principal. -- The notice given by the Data Fiduciary to the Data Principal shall-- (a) be presented and be understandable independently of any other information that has been, is or may be made available by such Data Fiduciary; (b) give, in clear and plain language, a fair account of the details necessary to enable the Data Principal to give specific and informed consent for the processing of her personal data, which shall include, at the minimum, -- (i) an itemised description of such personal data; and (ii) the specified purpose or purposes of, and specific description of the goods or services to be provided or uses to be enabled by, such processing; and (c) give, the particular communication link for accessing the website or app, or both, of such Data Fiduciary, and a description of other means, if any, using which such Data Principal may-- (i) withdraw her consent, with the ease of doing so being comparable to that with which such consent was given; (ii) exercise her rights under the Act; and (iii) make a complaint to the Board.
Rule 4 , Registration and obligations of Consent Manager 13 Nov 2025
Plain summary: An Indian company with net worth of at least Rs 2 crore and sound management may apply to the Board under Part A of the First Schedule. Obligations are in Part B. The Board may suspend or cancel registration after a hearing. Rule 4 applies from one year after publication.
4. Registration and obligations of Consent Manager. -- (1) A person who fulfils the conditions for registration of Consent Managers set out in Part A of First Schedule may apply to the Board for registration as a Consent Manager by furnishing such particulars and such other information and documents as the Board may publish in this behalf on its website. (2) On receipt of such application, the Board may make such inquiry as it may deem fit to satisfy itself regarding fulfilment of the conditions set out in Part A of First Schedule, and if it-- (a) is satisfied, register the applicant as a Consent Manager, under intimation to the applicant, and publish on its website the particulars of such Consent Manager; or (b) is not satisfied, reject the application and communicate the reasons for the rejection to the applicant. (3) The Consent Manager shall have obligations as specified in Part B of First Schedule. (4) If the Board is of the opinion that a Consent Manager is not adhering to the conditions and obligations under this rule, it may, after giving an opportunity of being heard, inform the Consent Manager of such non-adherence and direct the Consent Manager to take measures to ensure adherence. (5) The Board may, if it is satisfied that it is necessary so to do in the interests of Data Principals, after giving the Consent Manager an opportunity of being heard, by order, for reasons to be recorded in writing, -- (a) suspend or cancel the registration of such Consent Manager; and (b) give such directions as it may deem fit to that Consent Manager, to protect the interests of the Data Principals. (6) The Board may, for the purposes of this rule, require the Consent Manager to furnish such information as the Board may call for.
Rule 7 , Intimation of personal data breach 13 Nov 2025
Plain summary: Tell each affected Data Principal without delay (nature, extent, timing, consequences, mitigation, safety steps, contact). Tell the Board without delay, then within 72 hours (or longer if allowed) give detailed facts, findings on who caused it, remedial measures and a report on intimations given.
7. Intimation of personal data breach. -- (1) On becoming aware of any personal data breach, the Data Fiduciary shall, to the best of its knowledge, intimate to each affected Data Principal, in a concise, clear and plain manner and without delay, through her user account or any mode of communication registered by her with the Data Fiduciary, -- (a) a description of the breach, including its nature, extent and the timing of its occurrence; (b) the consequences relevant to her, that are likely to arise from the breach; (c) the measures implemented and being implemented by the Data Fiduciary, if any, to mitigate risk; (d) the safety measures that she may take to protect her interests; and (e) business contact information of a person who is able to respond on behalf of the Data Fiduciary, to queries, if any, of the Data Principal. (2) On becoming aware of any personal data breach, the Data Fiduciary shall intimate to the Board, -- (a) without delay, a description of the breach, including its nature, extent, timing and location of occurrence and the likely impact; (b) within seventy-two hours of becoming aware of the breach, or within such longer period as the Board may allow on a request made in writing in this behalf, -- (i) updated and detailed information in respect of such description; (ii) the broad facts related to the events, circumstances and reasons leading to the breach; (iii) measures implemented or proposed, if any, to mitigate risk; (iv) any findings regarding the person who caused the breach; (v) remedial measures taken to prevent recurrence of such breach; and (vi) a report regarding the intimations given to affected Data Principals.
Rule 8 , Time period for specified purpose to be deemed as no longer being served 13 Nov 2025
Plain summary: Third Schedule classes (e-commerce and social media with 2 crore or more users, online gaming with 50 lakh or more) must erase data after 3 years without approach, with 48 hours notice. Rule 8(3): every fiduciary keeps data and logs for at least one year for Seventh Schedule purposes.
8. Time period for specified purpose to be deemed as no longer being served. -- (1) A Data Fiduciary, who is of such class and is processing personal data for such corresponding purposes as are specified in Third Schedule, shall erase such personal data, unless its retention is necessary for compliance with any law for the time being in force, or, for the corresponding time period specified in the Third Schedule, if the Data Principal neither approaches such Data Fiduciary for the performance of the specified purpose nor exercises her rights in relation to such processing. (2) At least forty-eight hours before completion of the time period for erasure of personal data under this rule, the Data Fiduciary shall inform the Data Principal that such personal data shall be erased upon completion of such period, unless she logs into her user account or otherwise initiates contact with the Data Fiduciary for the performance of the specified purpose or exercises her rights in relation to the processing of such personal data. (3) Without prejudice to sub-rules (1) and (2), a Data Fiduciary shall retain, in respect of any processing of personal data undertaken by it or on its behalf by a Data Processor, such personal data, associated traffic data and other logs of the processing for a minimum period of one year from the date of such processing, for the purposes as specified in the Seventh Schedule, after which the Data Fiduciary shall cause such personal data and logs to be erased, unless further retention is required for compliance with any other law for the time being in force or notified by the Government. [Illustrations omitted. The Third Schedule sets three years from the last approach or the commencement of the Rules, whichever is latest.]
Seventh Schedule , Purposes and authorised persons for rule 23 and rule 8(3) 13 Nov 2025
Plain summary: (1) Sovereignty, integrity or State security, by a designated officer. (2) State functions or disclosure duties under law, by a person authorised by law. (3) Assessment for Significant Data Fiduciary notification, by a designated MeitY officer.
Third Schedule , Retention default periods 13 Nov 2025
Plain summary: E-commerce (2 crore plus users), online gaming intermediaries (50 lakh plus) and social media intermediaries (2 crore plus): for all purposes except account access and virtual tokens, erase after 3 years from last approach or Rules commencement, whichever is latest.

April 2026 Guidelines , IRDAI information and cyber security guidelines (reported April 2026) 06 Apr 2026
Plain summary: Secondary sources report IRDAI information and cyber security guidelines issued in April 2026. Primary text not checked, and sources conflict on details such as VAPT cadence. Check the IRDAI website before relying on any detail.

Draft July 2026 , RBI draft data governance guidance (reported July 2026) 15 Jul 2026
Plain summary: Secondary sources report an RBI draft guidance on data governance expectations for regulated entities in July 2026. Primary text not checked. Check the RBI website for status, scope and any final version before relying on it.

Cyber Audit , Cyber audit cadence and scope 20 Aug 2024
Plain summary: Twice a year for MIIs, Qualified REs and Mid/Small REs with IBT or Algo; once a year for others; Self-cert REs do VAPT only. Cover 100% critical and 25% sampled non-critical systems. Report in 1 month, close in 3, follow-on audit in 5. CERT-In empanelled auditor mandatory.
Cyber audit (section 4.4): cyber audit shall cover 100% of the critical systems and 25% non-critical systems (chosen on a sample basis). Periodicity: at least twice in a year for MIIs and Qualified REs and for Mid-size and Small-size REs providing IBT or Algo trading facility; at least once in a year for the rest of the REs (self-certification REs are exempt from periodic cyber audit and undertake VAPT). Table 22: the final cyber audit report shall be submitted after approval from the IT Committee for REs within 1 month of completion of cyber audit; closure of findings within 3 months of cyber audit report submission, with a graded approach based on criticality; follow-on audit completed within 5 months of completion of cyber audit. Annexure-D: auditors must mandatorily be CERT-In empanelled; the auditor must preferably have a minimum 3 years of experience in IT audit of Banking and Financial services, preferably in the Securities Market; certifications such as CISA, CISM, GSNA and CISSP are recommended; the auditor shall not have been engaged over the last two years in any consulting engagement with any department or unit of the RE. A CERT-In empanelled IS auditing organisation can audit an RE for a maximum period of three consecutive years, then only after a cooling off period of two years.
Master Circular 2024/113 , Cybersecurity and Cyber Resilience Framework for SEBI Regulated Entities 20 Aug 2024
Plain summary: SEBI Circular SEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 dated 20 August 2024. The 205-page master framework that supersedes all prior SEBI cyber circulars (2015 MIIs, 2016 depositories, 2018 stockbrokers/DPs, 2019 MFs/RTAs). Applies to all SEBI Regulated Entities across five categories: MIIs, Qualified REs, Mid-size REs, Small-size REs and Self-Certification REs. Structured around 5 cyber-resilience goals (Anticipate, Withstand, Contain, Recover, Evolve) mapped to 6 NIST CSF 2.0 functions (Governance, Identify, Protect, Detect, Respond, Recover). Cross-references NIST CSF 2.0, ISO/IEC 27001:2022, CIS Controls v8, ISO 22301.
SEBI Circular SEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 dated August 20, 2024. Subject: Cybersecurity and Cyber Resilience Framework (CSCRF) for SEBI Regulated Entities (REs). This framework is applicable to all SEBI Regulated Entities and consolidates all prior cybersecurity guidelines. The framework is structured around five cyber-resilience goals: Anticipate, Withstand, Contain, Recover and Evolve. These goals are implemented through six functional domains aligned to NIST CSF 2.0: Govern, Identify, Protect, Detect, Respond and Recover.

Found an error? We pay for it.

If you find a factual error in any lesson, write to [email protected] with the lesson title, the specific claim, and the corrected source.

  • ₹1,000 credit for the first report of any verifiable factual error.
  • ₹5,000 credit for a substantial error (e.g. a wrong section number, an obsolete ruling, a misrepresented holding).
  • Credit on your dcomply Academy account usable against any future course.

We pay because we'd rather know than not know. If the law changes (and it will), we want to be the first to fix our lessons.

On this page
  • 🟢 Our verification promise
  • 📊 Course statistics
  • 📚 Full citation register
  • 🐛 Bug bounty for errors

Maintained by the dcomply Academy editorial team. Last reviewed recently.