Last updated: July 1, 2026
EduPilot ("we," "our," "us") provides school management software to educational institutions across India. This policy explains what data we collect from schools, parents, teachers and students (referred to here as "wards"), how we use it, and the choices available to you.
In most cases, your school is the primary data controller for its students' records, and EduPilot acts as the data processor operating the platform on the school's behalf. Where you're a parent or staff member, your school administrator is typically your first point of contact for data requests specific to your ward.
Account & identity data: name, email, phone number, role (parent, teacher, administrator) and school affiliation, collected when a school onboards or a parent/staff account is created.
Ward (student) data: name, date of birth, class/section, attendance, academic performance, exam results, diary entries and, where a school opts in, medical or behavioral notes entered by school staff.
Payment data: fee amounts, transaction status and payment method type. Full card or bank details are handled directly by our payment gateway partners and are never stored on EduPilot servers.
Usage data: device type, IP address, app/browser version and interaction logs, collected automatically to keep the platform secure and reliable.
To operate core features: attendance, academics, exam results, digital diaries, fee invoicing and the AI-based learning path for each ward.
To personalize the AI learning engine's recommendations using a ward's own exam and diary history — never using another student's data to personalize a different student's path.
To send transactional notifications: fee reminders, diary entries, exam results and event calendar updates.
To maintain platform security, detect abuse, and meet our audit and compliance obligations to partner schools.
Your school: the partner institution that owns the account retains administrative access to its own students' data, as the data controller for that relationship.
Payment gateway partners: processors we integrate with to handle fee transactions, bound by their own PCI-DSS compliance obligations.
Infrastructure providers: cloud hosting and storage vendors that process data on our behalf under contractual confidentiality terms — never sold, and never shared with advertisers.
Law enforcement or regulators, only when legally compelled, and limited to what's specifically requested.
Most ward (student) data on EduPilot belongs to minors. Accounts and consent for a ward's data are managed through the parent or guardian account, or through the partner school acting on behalf of parents under its own enrollment agreements.
We do not knowingly allow a minor to create an independent account without a linked parent or school-administrator relationship.
Ward data is used strictly for the educational purposes described in this policy — never for behavioral advertising or resale.
Active ward and school records are retained for as long as the school's subscription is active, plus a limited retention window after termination to allow data export or transfer.
Financial records are retained as required under applicable Indian tax and accounting regulations.
A school or parent may request earlier deletion of specific records, subject to any academic record-keeping obligations the school itself is subject to.
Encryption in transit (TLS) and at rest for stored data.
Role-based access control, so a teacher, parent or administrator only sees data relevant to their role and linked wards.
Regular backups and audit logging across production systems.
No security system is infallible — if we identify a breach affecting your data, we will notify affected schools and, where required by law, affected individuals, without undue delay.
Parents and staff may request access to, correction of, or deletion of the personal data associated with their account, subject to the school's own record-retention policies for academic data.
Requests can be made through your school administrator or directly to us at the contact below; we will route school-owned data requests through the relevant school where required.
You may withdraw consent for optional features (such as certain AI personalization signals) without losing access to core school-management functionality.
We use strictly necessary cookies to keep you signed in and to remember basic preferences.
We use limited analytics to understand feature usage and improve the product — this data is aggregated and is not used to build advertising profiles of students or parents.
We may update this policy as our features or legal obligations evolve. Material changes will be communicated to partner schools in advance, and the "last updated" date below will reflect the latest revision.
Reach out to our team and we'll respond within one business day.
hello@edupilot.io