Protect student and parent data through age design, guardian controls, school contracts, learning analytics, advertising limits, access, safety and deletion.
Edtech systems often combine identity, behaviour, performance, family and payment data about children.
Design separate controls for students, parents, teachers, schools and direct consumers before collecting learning telemetry.
Map child and parent journeys.
School and parent agreements.
Using 13 as the Indian child threshold.
The Digital Personal Data Protection Act, 2023 and the final Rules notified in November 2025 follow phased commencement. As of 25 June 2026, organisations should separate duties already operative from consent, grievance, rights, children, Significant Data Fiduciary and other operational provisions scheduled for later commencement, while continuing to comply with the IT Act, CERT-In directions and sector-specific rules already in force.
The DPDP Act defines a child as an individual under eighteen and includes restrictions relating to detrimental processing, tracking, behavioural monitoring and targeted advertising when the relevant provisions commence.
School-authorised use, direct-to-parent subscriptions, classroom monitoring and marketing are different processing contexts and should not be collapsed into one consent.
| Area | What to establish | Operating rule |
|---|---|---|
| User | Student, parent, teacher or school administrator. | Assign role. |
| Purpose | Learning, safety, assessment or marketing. | Separate. |
| Analytics | Progress, attention, behaviour and profiling. | Limit and explain. |
| Exit | School change, course end and account closure. | Delete or restrict. |
A reliable control should connect the individual, data field, purpose, notice or sector disclosure, system, employee access, vendor access, retention rule and closure evidence. A policy statement that cannot be traced through this chain is difficult to operate.
Maintain a legal-timing matrix. Record the DPDP provision, phased commencement status, current IT Act or sectoral duty, business owner, system dependency and implementation deadline. Avoid one blanket label such as compliant or not compliant.
Build controls into technology and workflow. A written instruction cannot stop an SDK from collecting contacts, a campaign tool from re-importing suppressed users or an agent from downloading medical records unless the system enforces the decision.
Use proportionate verification. Weak checks can expose another person’s information; excessive checks create more Aadhaar, health, payroll or bank data that must be protected and deleted later.
Generate evidence during ordinary operations: versioned screens, event logs, access approvals, vendor tickets, complaint chronology, deletion reports, test recordings and management decisions.
Segment access by role and lifecycle. Sales, support, teachers, clinicians, claims staff and external agents do not need the same information.
High-risk data should not move through personal messaging, unprotected links or shared credentials merely because those channels are convenient.
Select one real user or transaction journey and trace it from collection through sharing, access, retention, withdrawal, complaint or closure. Capture the evidence at each stage.
Test the control on production-like systems rather than screenshots alone. Review network traffic, event logs, suppression status, vendor responses, role access and deletion output.
Run an adverse scenario: the vendor is breached, the user is a child, the borrower alleges harassment, the employee leaves or the app permission is revoked. Record the response and gaps.
Compare public wording with actual behaviour. Product forms, call scripts, privacy notices, contracts, SDKs and support tools should tell the same story.
Assign a named owner, funded action and closure date to each gap. Retain the reason when management accepts residual risk or chooses a less intrusive alternative.
Start with the privacy, security, product or regulated-business owner and preserve system evidence before changing configuration or deleting records. Separate current sector and CERT-In obligations from future DPDP readiness.
For serious complaints, children’s data, financial harassment, medical exposure or suspected cybercrime, involve qualified legal, privacy, cyber, banking, insurance or healthcare specialists and use the applicable official channel.