Skip to content
Legal

Privacy Policy

Last updated 22 October 2026

Schools trust us with children’s records, and in some schools their faces. This page sets out exactly what we do with that data — in plain language, because a policy nobody can follow protects nobody.

1.Who we are and what this covers

SchoolOrbits (“we”, “us”) provides a school management system: the staff console on the web and desktop, the staff and parent mobile apps for iOS and Android, and this website. This policy explains what personal data passes through those products, why, and what control you have over it.

It is written for India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”) and the rules made under it.

Two roles, depending on whose data it is

  • Records a school keeps in SchoolOrbits — students, parents, staff, attendance, fees, exams. The school decides why and how this data is processed, so the school is the Data Fiduciary. We are its Data Processor: we handle that data only to run the service for that school, on its instructions.
  • Our own relationship with you — the person who signs a school up, anyone who contacts us, and visitors to this website. For this data we are the Data Fiduciary.

If you are a parent, student or staff member, your school is the right first contact for questions about your records. We will help the school answer them.

2.The data we handle

School records, entered by the school

  • Students: name, class, section and roll number, date of birth, gender, blood group, home address, contact numbers, and — only if the school chooses to record it — a national ID number such as Aadhaar.
  • Parents and guardians: names, phone numbers and email addresses held on the student record. The parent’s phone number is also how they sign in to the parent app.
  • Staff: name, contact details, role and the permissions that come with it, timetable and absences.
  • School activity: attendance, fee structures, invoices and payment status, exams, marks and report cards, timetables, notices and assignments.

Attendance marked on a device

When attendance is marked at a gate kiosk or from a phone, the record can include the time, the device, its IP address, and — where the school has set a campus geofence — the device’s location at that moment. If face recognition is on, it also includes a check-in photo and a match score. See Face recognition data.

Accounts

Email address, phone number and password for staff accounts, and the phone number for parent and student sign-in. Passwords are stored only as one-way hashes; we cannot read them. When a school signs up we verify an email address and a WhatsApp number with one-time codes.

Payments

Fee payments from parents go through the school’s own payment gateway account (for example Razorpay or Cashfree). The money moves from parent to school; it never passes through us, and we never see or store card numbers, UPI PINs or bank credentials. We record the payment’s status and reference so the invoice can be marked paid. Our own subscription charges to schools are processed by Razorpay.

This website

This website uses Google Analytics to understand how it is used — which pages are visited, how visitors arrive, roughly where they are (country and city, derived from the IP address), their device and browser, and which links they follow. Google does not log or store IP addresses for Google Analytics 4. We use these figures only in aggregate, to improve the site. Google Analytics runs on this website only, never in the staff console or the mobile apps, and the site runs no advertising. Our servers keep standard request logs (IP address, browser, pages requested) to keep the service secure. If you email, call or write to us, we keep what you send so we can reply.

3.Face recognition data

Face recognition is optional and switched on per school. Card, PIN and manual marking produce the same attendance record for any school, class or student that does not use it.

  • Consent comes first. The face of a child is sensitive personal data. Before enrolling a student’s face, the school must obtain verifiable consent from a parent or guardian, as the DPDP Act requires for anyone under 18.
  • What we store: the enrolment photos, a numerical template of the face (512 numbers computed from those photos), and, for each check-in, the photo taken and the match score.
  • How it is used: only to confirm that the student checking in at that school is who they say they are. A face is compared with that one student’s template, never searched against everyone else.
  • What we never do: sell face data, share it between schools, use it to identify people outside the school’s own attendance, or use it to train recognition models.
  • Removing it: when a school asks us to remove a student’s face data, or closes its account, we delete the template and photos within 30 days.

4.How we use data

  • To run the service for the school — the records, reports and apps it uses.
  • To send the messages the school has switched on, such as check-in alerts to parents, by WhatsApp or in the parent app.
  • To sign people in, verify contact details and protect accounts.
  • To bill schools for their plan and to provide support when asked.
  • To find and fix faults, prevent abuse, and meet our legal obligations.

We do not sell personal data, show advertising, or build profiles of students or parents.

5.Who we share it with

We share data only with service providers that help us run the product, and only what each needs:

  • Hosting and database — where the service and its records run.
  • Cloudinary — storage for photos, including face enrolment and check-in photos.
  • Email delivery (Zoho ZeptoMail, with Google as a fallback) — sign-in codes, account email, and demo requests from this website’s contact form.
  • A WhatsApp messaging provider — verification codes and the parent alerts a school enables.
  • Razorpay — our subscription billing. A school’s own gateway handles its fee collection under the school’s agreement with that gateway.
  • Google Analytics — visitor statistics for this website only, under Google’s privacy policy. No school records reach it.

We may also disclose data when the law requires it, or to a successor if SchoolOrbits is merged or sold, in which case this policy continues to apply to it.

6.Where data is stored

Data is stored with our hosting and storage providers. Some of them, such as our photo storage provider, may process data on servers outside India. Where data leaves India it goes only to countries the Government of India has not restricted under the DPDP Act, and it stays under the protections in this policy.

7.How long we keep it

School records are kept for as long as the school’s account is open, because the school needs them to run. A school can export its data at any time.

When a school closes its account, it has 30 days to export its data. We then delete the school’s records within 90 days of closure, except anything the law requires us to keep longer — for example, our own invoices for tax purposes.

Website analytics data is kept for 14 months, then deleted automatically.

8.How we protect it

  • All traffic to the service is encrypted in transit (HTTPS).
  • Passwords are stored as one-way hashes, never in readable form.
  • A school’s payment gateway credentials are encrypted before they are stored.
  • Every record belongs to one school, and one school’s staff cannot see another school’s data.
  • Within a school, staff roles limit who can see and change what.

9.Your rights

Under the DPDP Act you can:

  • ask what personal data is held about you and how it is being used;
  • have inaccurate or incomplete data corrected or updated;
  • have data erased once it is no longer needed, or withdraw consent you gave;
  • nominate someone to exercise these rights if you are unable to; and
  • have a grievance about how your data is handled addressed.

For school records, make your request to the school; it controls those records and we will act on its instructions. For anything else, contact us using the details in section 13.

10.Children’s data

Most of the people in a school’s records are under 18. We process their data only on behalf of their school, which is responsible for obtaining verifiable parental consent. We do not track children’s behaviour, monitor them beyond the attendance the school has switched on, or direct advertising at them.

11.Cookies and local storage

This website sets no advertising cookies. Google Analytics sets first-party cookies (named _ga and _ga_*) that tell repeat visits apart from new ones; they last up to two years. You can block or delete them in your browser settings, or opt out of Google Analytics on every site with Google’s opt-out browser add-on; the site works the same either way. The site also remembers your light or dark theme choice in your browser’s local storage. The staff console and apps set no analytics cookies; they store a sign-in token on your device so you stay signed in, and signing out removes it.

12.Changes to this policy

If we change how we handle personal data, we will update this page and its date. For significant changes we will also tell account holders by email or in the console before the change takes effect.

13.Contact and grievances

For any question, request or complaint about personal data, contact our Grievance Officer:

We will acknowledge a grievance promptly and respond within 30 days. If you are not satisfied with our response, you can complain to the Data Protection Board of India.

See also our Terms of Service.