How SchoolPilot handles school data

Who we are

SchoolPilot is a school management platform operated at https://school-pilot.org. Contact: WhatsApp support.

Public website

The marketing site may record technical logs (IP address, browser, pages requested) needed to operate HTTPS, prevent abuse and understand aggregate traffic. If you enable Google Analytics via your own measurement ID in deployment, that product processes usage data under Google’s terms. We do not require analytics to use the marketing pages.

School accounts

When a school registers, we store account, billing and tenant configuration needed to provide the ERP. Student, parent, teacher and fee records entered by the school belong to that school’s tenant. They are not published on marketing pages and are not intended for search-engine indexing. Access is authenticated and role-based.

A parent who signs in should see their children, not the whole campus. A teacher should see assigned classes. An accountant should see dues. That isolation is both a product requirement and a safeguarding requirement. The school decides who receives which role.

Cookies and analytics

Essential cookies keep you signed in to the school application. Marketing pages do not require an account. If a deployment enables Google Analytics, that tool may set its own cookies under Google’s policy. You can use the public site without creating a SchoolPilot login.

Sharing

We use hosting, email, and payment processors only as needed to run the product. We do not sell student lists. Schools remain responsible for the personal data they enter and for any consent their jurisdiction requires.

Retention and security

We use HTTPS, role-based access, backups and audit logging as described in the product. Schools control what they enter. You may request account-related questions via WhatsApp. Statutory rights depend on your jurisdiction. If you need a copy or deletion of account data, say so clearly and include the registered school name.