Security & data
What we do today, and what we're honest about not having yet.
Student and family data deserves a straight answer, not a compliance-badge wall. Here's what's actually built, and what's still in progress.
What's built today
Role-based access
Teacher, admin, principal/director and platform-admin roles each see only what their role is meant to see — a teacher's access to a class or student is tied to a real assignment, not inferred from being in the same school.
School data stays scoped to that school
Every school's records — students, staff, marks, fees — are scoped to that school. Staff and parents on the platform only ever see data belonging to their own school.
Parent access scoped to their own children
A parent account is linked to specific children through the school's records — never to another family's data, by design.
Activity logging on sensitive records
Changes to student, staff, fee, and other sensitive records are logged with who made the change and what changed — visibility that's itself role-gated.
Automated protection against repeated login attempts
Accounts are automatically protected against repeated failed login attempts from the same source.
Data hosted in India
All data is hosted on infrastructure in India (Mumbai region), encrypted in transit and at rest via our cloud provider's managed database.
Automated backups
Regular automated backups, with restore procedures we've actually exercised, not just documented.
Monitoring on scheduled jobs
Background jobs (daily syncs, alerts, report generation) are monitored, with our team alerted automatically if one fails.
What we're still building
We'd rather list these plainly than let a gap surface later after a school has already committed.
- Formal Privacy Policy, Terms of Service and a Data Processing Agreement — being finalized ahead of onboarding paying schools.
- Compliance work under India's DPDP Act 2023, including a documented consent and retention framework.
- Self-service data export and deletion tools for a school that wants to leave the platform. We don't have this built yet, and we're not going to claim otherwise.
- Independent third-party security review, planned as we take on more schools.
- Multi-factor authentication for staff accounts.
Whose data is it
A school owns its own data. A teacher owns content they create, unless otherwise agreed. We don't sell, and we don't use a school's student or family data to train models for other customers.
FAQ
Straight answers
Are you SOC 2, ISO 27001, or GDPR certified?
No, and we won't claim otherwise. We're an early-stage product without paying schools yet; formal certifications aren't in place. If that's a hard requirement for your school, we want to know that upfront, not after a demo.
Where is our data physically stored?
On cloud infrastructure in India (Mumbai region).
Can we get our data out if we decide to stop using Edtrack?
Not yet as a self-service tool — this is on our roadmap and we've named it above rather than leaving it unaddressed. Today, this would be a manual conversation with us.
Do you have a bug bounty or way to report a security issue?
Email us and we'll respond directly — see the Contact page.