SchoolPilot Privacy Policy
Effective 13 August 2026
1. Who this policy covers and how SchoolPilot works
SchoolPilot is a school management platform used by schools across Nigeria to manage attendance, grades, fees, and communication with parents. Each school on SchoolPilot (“a participating school”) signs its own students, parents, teachers, and staff up under its own account — you sign in with a school code your school gives you.
SchoolPilot Technologies (“SchoolPilot,” “we,” “us”) operates the platform. For most of the personal data described below, the participating school is the data controller under the Nigeria Data Protection Regulation (NDPR) — the school decides what student and staff data to enter and who at the school can see it. SchoolPilot acts as a data processor for that relationship: we store and process the data on the school’s behalf, following the school’s instructions and this policy’s own security and retention commitments, but we do not decide what a school records about its own students or staff.
This is one policy covering every school on the platform, rather than a separate policy per school, so that the practices described here (what’s collected, how it’s protected, who it’s shared with) are consistent and easy to find in one place. If you have a question about a specific child’s or staff member’s record, your school is the right first point of contact — they hold the administrative relationship with you and can act on most requests directly inside SchoolPilot. If your school is unable to help, or your question is about SchoolPilot’s own handling of data rather than a specific school’s decision, contact us directly (§8).
2. What we collect, and why
Every category below is entered by a school (at enrollment or during ordinary use of the platform), not self-submitted through a public sign-up form — SchoolPilot has no consumer-facing registration.
| Category | About | Why we collect it |
|---|---|---|
| Name, email, phone number | Parents, teachers, and other staff who sign in to SchoolPilot | Account identity, signing in, and sending you attendance/fee/message notifications. |
| Student personal information (name, date of birth, gender, address, nationality, state of origin, religion) | Students, including minors | Enrollment record your school itself enters. Viewed by your child's linked parent/guardian account and the relevant school staff — never publicly visible. |
| Student medical and emergency information (blood group, genotype, allergies, medical notes, emergency contact) | Students, including minors | Recorded by your school at enrollment for the student's safety — for example, so staff know about a medical condition in an emergency. Shown only to the student's linked guardians and the relevant staff (e.g. a form teacher). |
| Academic records (attendance, grades, exam results, disciplinary records) | Students | The core purpose of the platform — so parents and teachers can see attendance, grades, and report cards. |
| Financial information (fee invoices, payment history, amounts owed) | Parents (as the paying party), tied to a student | Fee tracking and online payment. Card details themselves are never seen or stored by SchoolPilot — see §4. |
| Messages (between teachers, parents, and school staff) | Whoever sent or received the message | In-app communication about a specific child, class, or school-wide announcement. |
| Device push-notification token | The signed-in account holder's device | Delivering attendance, fee, and message alerts to your phone. |
| Photos you choose to upload (e.g. a homework photo, an admission document) | Whoever uploads it | Only the specific document/assignment feature you used it for — never collected automatically. |
We do not collect your device’s GPS location. A school transport feature can show a parent a school bus’s last reported position — that position is entered by a driver or admin, not read from your phone, and SchoolPilot never requests your device’s own location permission.
We do not run advertising or ad-tracking of any kind — there is no advertising SDK, no ad-tracking pixel, and no sale of personal data anywhere in SchoolPilot, to anyone, ever.
3. Children's data — read this section carefully
Nigeria’s NDPR does not have a separate children’s-data regime the way some other countries’ laws do, but SchoolPilot treats student data — including minors’ data — with the highest level of care in the platform, regardless of where a school is located.
- Students do not sign themselves up. A school enters a student’s bio-data, medical information, and academic record at enrollment. A parent or teacher — an adult — is who typically signs in to view it.
- Some students do have their own login. Where a school issues one, a student can sign in directly to take computerized tests or view their own practice results. This is a deliberately narrow, school-issued account, not a public student sign-up — and it means SchoolPilot’s own signed-in users legitimately include minors, not only adults viewing a child’s record on their behalf.
- Who can see a child’s record: only that child’s own linked parent/guardian account(s) and the school staff with a legitimate reason to see it (the child’s teachers, the school’s administrators) — enforced by the platform itself, not just by an interface choice. A parent at one school can never see another school’s students, and a parent can never see a child they are not linked to as a guardian.
- Requesting a child’s data be exported or deleted: contact your school first — see §7 for how this works in practice.
4. Who we share data with
We do not sell personal data. We share specific data with the following processors, strictly to provide the platform’s own features — each is bound to use the data only for that purpose:
- Payment processing — Paystack and/or Flutterwave. When you pay a fee online, you are redirected to that provider’s own secure payment page; SchoolPilot never sees or stores your card number, PIN, or bank credentials. The provider tells SchoolPilot only whether the payment succeeded and for how much.
- SMS delivery — Termii (primary) and Africa’s Talking (backup), to deliver attendance and fee alerts by text message to the phone number your school or account has on file.
- Email delivery — Resend, to deliver notifications and password-reset emails.
- Push notifications — Google Firebase Cloud Messaging (for the installed mobile app) and the standard Web Push protocol (for browser/installed-web-app notifications), to deliver alerts to your device.
- Hosting infrastructure — Fly.io, which runs the servers SchoolPilot operates on. See §5 for where your data is physically stored.
- AI features (where a school has this enabled) — Anthropic, to power features like AI-drafted lesson notes or an assistant that answers a teacher’s question about their own class’s attendance/grade/fee data. The assistant only ever answers using your school’s own real data, looked up through the same secure channels the rest of the app uses — it does not have open-ended database access, and it cannot send a message, email, or SMS on anyone’s behalf.
- Virtual classroom (where a school uses this feature) — Zoom, to host live online classes a teacher schedules.
We may also disclose information where required by law, or to protect the rights, property, or safety of SchoolPilot, a participating school, or any person.
5. Where your data is stored
SchoolPilot’s servers and database run on infrastructure in the region closest to Nigeria available to us at this time (Johannesburg, South Africa). This is a deliberate choice to keep your data as close to Nigeria as practically possible given current hosting options — it is not a claim that data is stored inside Nigeria itself. We will move to Nigeria-based or more local hosting if and when a suitable option becomes available.
6. How long we keep data
- Financial records (invoices, payments, payroll) and audit logs (a record of who changed what, and when) are retained indefinitely and are never deleted, even after an account is closed — this matches Nigerian statutory recordkeeping requirements for financial records and is necessary for security/compliance accountability.
- Academic and operational records not tied to a single identity (e.g. “this class had 94% attendance on this date”) are retained as part of the school’s own institutional record, even after a specific student’s personal details are removed following a deletion request.
- A closed or deleted account’s personal details (name, email, phone, address, medical/emergency-contact fields, bank details) are cleared immediately once a deletion request is processed — see §7.
7. Your rights and how to use them
Under the NDPR, you have the right to:
- Access/export your data. Any signed-in SchoolPilot user can export their own data at any time from inside the app — this produces a real, complete file of your own account’s data, generated on demand, not a promise to email it to you later.
- Request correction of inaccurate data — contact your school, since the school is who entered and controls most student/staff records (§1).
- Request deletion. Your school’s administrator (or SchoolPilot, on the school’s instruction) can initiate this from inside the app. It permanently clears your personal details from our systems (subject to §6’s retention exceptions for financial/audit records, which NDPR and Nigerian law require us to keep) and signs you out of every device.
- Object to certain processing or ask us questions about how your data is handled — contact us at privacy@schoolpilot.ng.
For a request about a specific child’s data, start with your school — they can act on most requests directly, and are best placed to verify who is authorized to make the request on a child’s behalf. If your school cannot help, or your request is about SchoolPilot’s own platform-level handling of data rather than a specific school’s record, email privacy@schoolpilot.ng and we will respond within a reasonable time.
8. How to reach us
For any question about this policy or how SchoolPilot handles your data, email privacy@schoolpilot.ng. For a question about a specific child’s or staff member’s record, please contact your school directly first (§1/§7).
9. Changes to this policy
We may update this policy as SchoolPilot’s features change. We’ll update the effective date at the top of this page when we do, and for any change that materially affects how we handle your personal data, we’ll take reasonable steps to make that change visible in the app, not just on this page.