DPDP Guide for EdTech Platforms
EdTech firms handle student data and minor records. Learn how DPDP impacts parental consent, student tracking, and learning analytics for Indian EdTech.
Discuss this page with an LLM
DPDP Action Sheet
Use this before your next workflow goes live. It keeps the useful parts visible and turns DPDP into checks your team can actually answer.
For DPDP Guide for EdTech Platforms, the DPDP question is how personal data enters the workflow, where it is stored, which tools touch it, what purpose was explained, and how deletion or withdrawal will work.
1. Lead Forms
Check:
- What data are you collecting?
- Is the purpose clear at the point of collection?
- Is marketing consent separate from service communication?
- Can the user withdraw consent later?
Common mistake: one checkbox that silently covers newsletters, sales calls, partner sharing and remarketing.
2. Email and WhatsApp
Check:
- Who is on the list?
- Where did consent come from?
- Is the list imported from a vendor, event, webinar, scrape or old CRM?
- Can you prove the source of consent?
Common mistake: treating every lead as permanently marketable.
3. Ads and Retargeting
Check:
- Are pixels or ad platforms receiving identifiable user behavior?
- Are audiences built from customer lists?
- Are lookalike or remarketing audiences using personal data?
Common mistake: assuming "the ad platform handles it" means your company has no DPDP responsibility.
4. Website Analytics
Check:
- Which tools run on the site?
- Are IP address, device identifiers, session IDs or form fields being captured?
- Is analytics used only for measurement, or also for profiling and targeting?
Common mistake: installing tools first and asking privacy questions later.
5. Vendor List
Make a quick list:
- CRM
- Email platform
- WhatsApp provider
- Analytics
- Ad pixels
- Form tool
- Landing page builder
- Webinar tool
For each vendor, answer: what data goes there, why, who can access it and how deletion works.
6. This Week's Action
Map one campaign from first click to final follow-up. Mark every place personal data is collected, enriched, shared, uploaded or used for targeting.
If your team cannot answer where the data came from and where it goes next, start with a data flow map before rewriting policy copy.
Book a DPDP clarity callWant all of this handled, end to end? Sanctum is the all-in-one DPDP compliance programme behind this site: legal position, data map, gap analysis, implementation, tooling, training, readiness opinion, and breach cover under one accountable owner. How all-in-one DPDP compliance works or see the Sanctum programme.
Verifiable Parental Consent for Minors
EdTech platforms serving K-12 students process data belonging to children. The DPDP Act requires verifiable parental consent for any user under the age of 18. A simple checkbox stating “I am over 18” or “I have my parent’s permission” is not enough. You must implement a reliable method to confirm the person giving consent is the actual legal guardian. This requirement changes how you design your sign-up flow and onboarding screens.
Student Behavioral Tracking Risks
Learning Management Systems (LMS) often track how long a student stays on a page or where they click. This behavioral data creates a profile of a child’s cognitive abilities and learning speed. DPDP prohibits any data processing that causes a “detrimental effect” on a child’s well-being. Excessive tracking for the purpose of aggressive marketing or predictive profiling of a minor’s future career path carries high compliance risk.
Data Retention for Academic Records
EdTech firms often keep student data indefinitely for alumni verification or historical progress reports. DPDP requires you to delete personal data once the specific purpose for collecting it is over. You must separate essential academic records from non-essential data like session heatmaps, chat logs, and abandoned cart details. Storing technical logs and marketing profiles after a student has finished their subscription violates the principle of storage limitation.
EdTech Data Workflows and Risks
| Work Area | Data Involved | DPDP Risk Level |
|---|---|---|
| Onboarding | Guardian KYC, child’s age, school name | High |
| Live Classes | Video recordings, audio, student chat logs | Very High |
| Adaptive Learning | Error patterns, completion speed, AI logs | High |
| Online Exams | Proctoring photos, ID scans, test scores | Very High |
| Performance Reports | Grade history, teacher feedback, certificates | Medium |
This week
Review your user registration database to identify every account where the user is under 18 years old. Document the specific technical method you currently use to verify that the person providing consent for these accounts is the legal guardian.
Now think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Do we need parental consent for students in college?
DPDP defines a child as anyone under the age of 18. For students 18 and older, you can obtain consent directly from the student without involving a parent or guardian.
Can we use student performance data to suggest new courses?
You can only use data for suggestions if your consent notice explicitly listed course recommendations as a purpose. For users under 18, you must ensure this tracking does not cause a detrimental effect on the child.
How long can we keep recorded video sessions of students?
You must delete recordings once the student completes the course or the evaluation period ends. If you want to keep them for teacher training, you must get specific consent for that secondary purpose.