| **01** | [**DPDPA Basics & Definitions**](#bkmrk-digital-personal-data-protection-act-dpdpa-basics-definitions) | 9 questions |
| **02** | [**Consent & Notice Requirements**](#bkmrk-consent-notice-requirements) | 7 questions |
| **03** | [**Rights of Data Principals**](#bkmrk-rights-of-data-principals) | 3 questions |
| **04** | [**Penalties & Enforcement**](#bkmrk-penalties-enforcement) | 3 questions |
| **05** | [**Significant Data Fiduciaries**](#bkmrk-significant-data-fiduciaries) | 3 questions |
| **06** | [**Children’s Data Protection**](#bkmrk-childrens-data-protection) | 3 questions |
| **07** | [**Data Breach & Security**](#bkmrk-data-breach-security) | 2 questions |
| **08** | [**Cross-Border Data Transfer**](#bkmrk-cross-border-data-transfer) | 2 questions |
| **09** | [**Data Retention & Erasure**](#bkmrk-data-retention-erasure) | 3 questions |
| **10** | [**Data Protection Board of India**](#bkmrk-data-protection-board-of-india) | 2 questions |
| **11** | [**Exemptions & Special Provisions**](#bkmrk-exemptions-special-provisions) | 2 questions |
| **12** | [**Practical Scenarios**](#bkmrk-practical-scenarios) | 6 questions |
**NOTE** Unlike General Data Protection Regulation (GDPR), DPDPA does not have a separate category for "sensitive personal data" - all personal data is treated similarly.
#### Q3 What is a Data Fiduciary? A Data Fiduciary (Section 2(i)) is any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data. In simple terms: If your organization decides **WHY** and **HOW** personal data is collected and used, you are a Data Fiduciary.**EXAMPLE** An e-commerce company collecting customer data for order fulfillment is a Data Fiduciary. The cloud provider hosting that data is a Data Processor.
#### Q4 What are the key obligations of Data Fiduciaries under DPDPA? All obligations under DPDPA and its consequent liability lie with the Data Fiduciary. In addition to the core obligation of ensuring that processing is only for lawful purposes with a valid Processing Bases, some of the other key obligations for Data Fiduciaries include: - engaging Data Processors only through a valid contract; - ensuring the accuracy, completeness, and consistency of PD processed where PD is likely to be used for making a decision concerning the Data Principal or where PD is disclosed to another Data Fiduciary; - implementing appropriate technical and organizational measures for processing of PD in compliance with DPDPA; - implementing reasonable security measures for preventing Personal Data Breach; - notifying the DPB and Data Principals in case of a Personal Data Breach; - erasing PD and causing engaged Data Processors to erase PD processed by them for the Data Fiduciary, upon withdrawal of consent if consent is the Processing Basis, or once the processing purposes are achieved, whichever is earlier, except where extended retention period is necessary for compliance with applicable law. #### Q5 What is a Data Principal? A Data Principal (Section 2(j)) is the individual to whom the personal data relates. Simply put: If it's YOUR data, YOU are the Data Principal. **SPECIAL PROVISIONS** - For children (under 18): Parent/lawful guardian acts as Data Principal - For persons with disabilities with lawful guardian: The guardian acts as Data Principal #### Q6 What is a Data Processor? A Data Processor (Section 2(k)) is any person who processes personal data on behalf of a Data Fiduciary. **KEY DIFFERENCES FROM DATA FIDUCIARY** - Follows instructions from Data Fiduciary - Does not determine purpose or means of processing - Has contractual liability, not direct DPDPA liability**EXAMPLES** Cloud service providers, payroll processing companies, CRM service providers, data analytics vendors.
#### Q7 What does ‘Processing’ of personal data mean? Under Section 2(x), "Processing" means any automated operation on digital personal data, including: - Collection and recording - Organisation and structuring - Storage and adaptation - Retrieval and use - Sharing and disclosure - Restriction and erasure**IMPORTANT** Even viewing personal data on a screen constitutes "processing" - the definition is extremely broad.
#### Q8 Is processing of publicly available PD regulated under DPDPA? DPDPA excludes from coverage completely, all PD that is: - made publicly available (such as through public profiles) by the data principal, or - becomes public through the operation of law (such as public government records) While this is the broadest public data exception globally, it does not mean that all “publicly available” PD stands unregulated. Before relying on “public” data, it may be advisable to make sure that the PD is indeed public and meets one of the two tests above. #### Q9 What is the phased implementation timelines under DPDPA Phase 1 (13 November 2025): Immediate enforcement of definitions, the constitution and digital functioning of the Data Protection Board of India, and general institutional provisions. Phase 2 (13 November 2026): Activation of the Consent Manager Framework and opening of Consent Manager registrations. Phase 3 (13 May 2027): Full substantive compliance goes live, including mandatory privacy notices, affirmative consent, data fiduciary obligations, Data Principal rights, children's data protections, and Board enforcement/penalties ### 02 Consent & Notice Requirements #### Q1 What are the requirements for valid consent under DPDPA? Under Section 4, valid consent must be: - **Free:** Given voluntarily without coercion - **Specific:** Related to a particular purpose - **Informed:** Data Principal understands what they're consenting to - **Unconditional:** Cannot be bundled with unrelated services - **Unambiguous:** Clear affirmative action required**INVALID** Pre-ticked checkboxes, buried consent in T&C, forced bundling with unrelated services.
#### Q2 What must be included in Notice to a Data Principal? Under Section 6 and Rule 3, Notice must include: - Personal data being collected - Purpose of processing - How to exercise Data Principal rights - How to make complaints to Data Protection Board Language Requirements**:** Must be in English AND any of the 22 Scheduled languages as chosen by Data Principal. #### Q3 Can consent be withdrawn? Yes, under Section 4(6)-(7): - Data Principal may withdraw consent at any time - Withdrawal must be as easy as giving consent - Data Fiduciary must provide clear withdrawal mechanism - Upon withdrawal, processing must stop and data erased (unless legally required to retain)**GOOD PRACTICE** One-click unsubscribe, easily accessible settings, clear instructions, no penalties for withdrawal.
#### Q4 What are ‘Legitimate Uses’ for which consent is not required? Section 5 provides Legitimate Uses without explicit consent: - Voluntary provision: Data Principal provides for specified purpose - State functions: Subsidies, benefits, services, certificates, licenses - Legal obligations: Compliance with judgments or laws - Medical emergencies: Threat to life/health - Employment: Recruitment, verification, performance (with safeguards) - Public interest: Mergers, acquisitions, restructuring #### Q5 What are the compliances for processing PD to undertake research, archiving, and statistical activities? Processing of PD for research, archiving, and statistical purposes is exempted under the DPDPA, provided it is (i) necessary for the mentioned purposes; (ii) not used to take any decision specific to the Data Principal; and (iii) carried out as per prescribed standards. The following standards are prescribed under Second Schedule of DPDP Rules: - processing is carried out in a lawful manner and be limited to such PD as is necessary for the underlying purposes; - reasonable efforts are made to ensure the completeness, accuracy, and consistency of PD processed; - retention is limited to durations that are needed to achieve the purposes, or for compliance with applicable laws; - reasonable security safeguards are built in to prevent Personal Data Breach including one that involves Processor’s ecosystems; - there is allocation of responsibility and accountability on persons who are Data Fiduciaries; and - appropriate technical and organizational measures are implemented to effectively comply with the above stipulations. #### Q6 What is a Consent Manager? Consent Manager (Section 14) is a registered entity that enables Data Principals to: - Give consent to multiple Data Fiduciaries through one platform - Manage, modify, or withdraw consent easily - Track and maintain records of all consents Requirements (Rule 4): Must be registered with Data Protection Board, interoperable, no conflict of interest, maintain technical safeguards.**UNIQUE TO INDIA** Similar to Account Aggregators in financial services - no direct GDPR equivalent.
#### Q7 Is it mandatory for all organizations to appoint a consent manager? No, it is not mandatory for all Data Fiduciaries to appoint a consent manager. ### 03 Rights of Data Principals #### Q1 What are the rights of Data Principal under DPDPA? Under Section 11, Data Principals have: - Right to Access: Know what data is being processed - Right to Correction: Correct inaccurate data - Right to Erasure: Request deletion of data - Right to Grievance Redressal: Complain to Data Fiduciary - Right to Nominate: Designate someone to act on their behalf (Section 12)**NOTE** Unlike GDPR, DPDPA does NOT include right to data portability.
#### Q2 How long does a Data Fiduciary need to respond to a data access request? Under Rule 14, Data Fiduciaries must respond within 7 days of receiving a valid request. The response must include: - Summary of personal data processed - Processing purposes - Categories of data shared with third parties #### Q3 What are the duties of Data Principals? Under Section 13, Data Principals must: - Provide authentic information when exercising rights - Not file false or frivolous complaints - Not impersonate another person while providing data - Not suppress material information**PENALTY** Up to ₹10,000 for false complaints or frivolous applications.
### 04 Penalties & Enforcement #### Q1 What are the penalties for non compliance under DPDPA? Under Section 33 and The Schedule:| **MAXIMUM PENALTY** | **VIOLATION** |
|---|---|
| ₹250 Crore | Failure to take reasonable security safeguards leading to data breach |
| ₹200 Crore | Failure to notify Board and Data Principal of breach |
| ₹150 Crore | Non-compliance with children's data provisions |
| ₹50 Crore | Other violations (per instance) |
| ₹10,000 | False complaints by Data Principals |
**KEY POINT** These are maximum caps - actual penalty depends on nature, gravity, and circumstances of breach.
#### Q2 What factors are considered while imposing penalties? The Board considers: - Nature, gravity, and duration of breach - Type of personal data affected - Repetitive nature of breach - Number of Data Principals affected - Actions taken to mitigate effects - Whether intentional or negligent - Compliance history of the entity #### Q3 Is there criminal liability under DPDPA? No. Unlike earlier drafts (2019), DPDPA 2023 does NOT prescribe criminal penalties. Consequences are: - Monetary penalties only - Directions from Data Protection Board - Possible blocking of services in extreme cases**NOTE** This was a significant change from earlier drafts which included imprisonment provisions.
### 05 Significant Data Fiduciaries #### Q1 What is a Significant Data Fiduciary? A Significant Data Fiduciary is a Data Fiduciary notified by the Central Government based on: - Volume and sensitivity of personal data processed - Risk of harm to Data Principals - Potential impact on sovereignty, public order, security - Use of new technologies for processing #### Q2 What additional obligations apply to SDFs? Under Section 10 and Rule 13, SDFs must: - Appoint a DPO: Based in India, point of contact for Board - Appoint Independent Data Auditor: Evaluate compliance - Conduct DPIA: Before high-risk processing - Periodic Audits: Regular compliance reviews - Maintain records: For 7 years - Publish DPO contact: Business contact information #### Q3 What is Data Protection Impact Assessment (DPIA)? A DPIA is an assessment conducted before processing activities that may pose significant risk. It should assess: - Nature, scope, context of processing - Risks to Data Principal rights - Mitigation measures - Proportionality and necessity**TIP** Document DPIAs thoroughly - they're evidence of compliance and due diligence.
### 06 Children’s Data Protection #### Q1 How does DPDPA define a “child”? Under Section 2(f), a "Child" means an individual who has not completed **eighteen years of age**.**GDPR COMPARISON** GDPR defines child as under 16 (with flexibility down to 13). India's uniform 18-year threshold is more conservative.
#### Q2 What special protections exist for children’s data? Under Section 9: - Verifiable parental consent: Must obtain before processing - No behavioral monitoring: Tracking children is prohibited - No targeted advertising: Cannot target ads at children - No harmful processing: Processing likely to cause detrimental effect on child's well-being is prohibited**PENALTY** Up to ₹150 Crore for non-compliance with children's data provisions.
#### Q3 Are there exemptions for children’s data processing? Yes, Rule 12 provides exemptions from verifiable consent for: - Healthcare services for children - Educational institutions - Child safety and protection services - Other classes as notified by Government ### 07 Data Breach & Security #### Q1 What are the data breach requirements under DPDPA? Under Section 8(6) and Rule 7: **WHO TO NOTIFY** - Data Protection Board of India - Affected Data Principals Timeline: Within 72 hours of becoming aware of breach Contents: Nature of breach, data affected, consequences, remediation measures, DPO contact**PENALTY** Up to ₹200 Crore for failure to notify breach.
#### Q2 What security safeguards are required? Under Section 8(4) and Rule 6, Data Fiduciaries must implement **reasonable security safeguards**: **TECHNICAL MEASURES** - Encryption of data at rest and in transit - Access controls and authentication - Regular security testing - Incident detection systems **ORGANIZATIONAL MEASURES** - Security policies and procedures - Employee training - Vendor management - Incident response plans ### 08 Cross-Border Data Transfer #### Q1 Can personal data be transferred outside India? Yes, with conditions. Under Section 16 and Rule 15: - Default: Transfer permitted to all countries - Negative list: Government may notify restricted countries - Restricted countries: Transfer prohibited unless specific approval**GDPR COMPARISON** DPDPA takes permissive approach with blacklist; GDPR takes restrictive approach with whitelist (adequacy decisions).
#### Q2 What is data localisation under DPDPA? DPDPA does NOT mandate blanket data localization. However: - Government may notify countries where transfer is restricted - Sectoral regulations (RBI, SEBI) may require localization for specific data types - Critical personal data localization may be prescribed separately ### 09 Data Retention & Erasure #### Q1 With respect to retention and erasure, what are the specific stipulations under DPDPA? PD must be erased once the specified purpose is no longer being served or upon withdrawal of consent. Retention beyond the specified period is permitted only if it is required for compliance with applicable laws, and/or necessary for dispute resolution or regulatory investigations #### Q2 Is the 1-year retention period mandatory for all organizations? What happens when different retention timelines are mandated under other laws? Rule 8(3) of DPDP Rules obligate every Data Fiduciary and its Processors to retain PD processed along with associated traffic data and processing logs for a minimum period of 1 (one) year from the date of processing for the purposes mentioned in the Seventh Schedule of DPDP Rules i.e., use by the state or any of its instrumentalities for sovereignty, security, and integrity of India, or for performance of any function under law as directed by authorized person under such law, or for aiding state’s assessment for SDF notification by MeitY. After this duration, Data Fiduciary and its Processors must erase PD and its associated details unless prolonged retention is required under applicable laws. Hence, the 1-year retention is mandatory for all organizations. Where another applicable law (or the Third Schedule of DPDP Rules) requires longer retention, such longer period will prevail over the minimum 1 year duration. #### Q3 What is the mandatory retention requirement under Third Schedule of DPDP Rules? Section 8(7) of DPDPA obligates every Data Fiduciary to erase PD unless retention is required for compliance with applicable law, either upon withdrawal of consent by the Data Principal, or as soon as it is reasonable to assume that the specific purpose is no longer served, whichever is earlier Elaborating on when it is reasonable to assume that the specific purpose is no longer served, Section 8(8) of DPDPA states that such assumption is viable when the Data Principal has not approached the Data Fiduciary for performance of the specific purpose and has not exercised any rights in relation to such processing for the prescribed durations as notified for different classes of Data Fiduciaries (**Disengagement Criteria**). Rules 8(1) and (2) read with Third Schedule of DPDP Rules provide the Disengagement Criteria for certain kinds of Data Fiduciaries in relation to identified purposes and the corresponding retention period therein, after the expiry of which such Data Fiduciaries must assume disengagement and proceed with erasure by providing a 48 (forty-eight) hours’ notice to the concerned Data Principal as a confirmatory exercise before deletion, unless prolonged retention is required due to other applicable law. The covered Data Fiduciaries, identified purposes, and retention periods under Third Schedule are as follows: - Covered Data Fiduciaries are e-commerce entities and significant social media intermediaries with minimum 20 (twenty) million, and online gaming intermediaries with minimum 5 (five) million registered users in India; - Identified purposes are for enabling the user’s access to their account or to any virtual token that is issued by or on behalf of the Data Fiduciary and is stored on the platform of the covered Data Fiduciaries and can be used to get money, goods or services; and - PD that is required for the identified purposes must be retained for 3 (three) years from the date of commencement of DPDPA or the date on which the user last reached out to the covered Data Fiduciaries for the identified purposes, whichever is latest. ### 10 Data Protection Board of India #### Q1 What is Data Protection Board of India (DPBI)? The DPBI is the regulatory body established under Section 18 to enforce DPDPA. **KEY FEATURES** - Digital by design - functions as "digital office" - Composed of Chairperson and Members - Independent in exercising powers **POWERS** - Receive and handle complaints - Conduct inquiries - Impose penalties up to ₹250 crore - Issue directions to Data Fiduciaries - Register Consent Managers #### Q2 How can Board orders be appealed? Under Section 29: - Appeals lie to Telecom Disputes Settlement and Appellate Tribunal (TDSAT) - Must file within 60 days (extendable by 60 days) - TDSAT may confirm, modify, or set aside Board's order - Further appeal to Supreme Court on questions of law only ### 11 Exemptions & Special Provisions #### Q1 What exemptions are available under DPDPA? Under Section 17, exemptions include processing for: - National security: Sovereignty, integrity, security of India - Public order: Prevention of offenses - Legal proceedings: Enforcement of legal rights/claims - Research/archiving: Statistical, research purposes (with safeguards) - Startups: Notified startups may get relaxations #### Q2 What are the exclusions to scope of application of DPDPA? Under Section 3, DPDPA does NOT apply to: - Personal data processed by individuals for personal or domestic purposes - Personal data made publicly available by Data Principal - Data required by law to be made public**EXAMPLE** Your personal phone contacts or family photos are not covered by DPDPA.
### 12 Practical Scenarios #### Q1 How should organisations update their privacy policies for DPDPA? Privacy policies should be updated to include: - Clear statement of data collected and purposes - Data Principal rights under DPDPA - Consent withdrawal mechanism - Grievance redressal process - DPO contact information (if SDF) - Data retention periods - Cross-border transfer information - Complaint mechanism to Data Protection Board #### Q2 What records should organisations maintain for compliance under DPDPA? Organizations should maintain: - Consent records: When, how, what consent was obtained - Data inventory: What personal data is processed and why - Data Principal requests: Access, correction, erasure requests - Breach records: Incidents and response actions - Vendor contracts: Data processing agreements - Training records: Employee awareness programs - DPIA records: For SDFs - Audit reports: Internal and external compliance reviews**RETENTION** SDFs must maintain records for 7 years per Rule 13.
#### Q3 How does DPDPA apply to employee data? Under Section 5(b) and Rule 22, employee data processing is a **Legitimate Use** for: - Recruitment and onboarding - Attendance verification - Performance assessment - Salary processing - Termination procedures #### Q4 What is the relationship between DPDPA and Information Technology Act 2000? DPDPA supplements IT Act. Key interactions: - **Section 43A (IT Act):** Compensation provisions amended - **Section 72A (IT Act):** Breach of confidentiality provisions continue - **IT Rules 2011 (SPDI):** Effectively superseded by DPDPA - **Section 69A (Blocking):** Continues independently**KEY POINT** Section 38 establishes DPDPA supplements and doesn't derogate from other laws unless explicitly stated.
#### Q6 Who is responsible for collecting consent when PD is collected by the Processor for the Data Fiduciary? All obligations under DPDPA apply to Data Fiduciaries, and they are obligated to ensure that their engaged Processors remain compliant with DPDPA. Where a Data Fiduciary engages a Processor to directly collect PD from Data Principal such as collecting feedback of Data Principals through surveys and market studies, the Data Fiduciary must provide its Notice for Consent and obligate the Processor to obtain DPDPA compliant consent before collecting PD. Where Data Principal refuses to signify their consent, the Processor should not collect any PD, unless the Data Fiduciary has permitted collection on any other permissible Processing Bases.