Privacy Policy

This Privacy Policy explains how EduSphere ("EduSphere", "we", "us") collects, uses and protects information when a School and its staff, students and parents ("Users") use the platform. Schools are the data controller for the student, guardian and staff records they enter into EduSphere; we act as a data processor, handling that data solely to provide the service. This policy should be read together with our Terms & Conditions.

Strictly to operate the platform: authenticating logins; showing each user the records their role permits (a parent only ever sees their own child's data); fee billing and receipts; attendance, academic and exam reporting; in-app announcements and messages between staff and parents; and security logging to detect abuse (failed logins, rate-limited requests). We do not use School or student data for advertising, and we do not sell it to third parties.

EduSphere is multi-tenant: every school's data is logically separated from every other school's at three layers — application-level query scoping, PostgreSQL Row-Level Security policies enforced by the database itself, and an audit trail of who accessed or changed what. No school can see another school's records through normal use of the product.

Records live in a managed PostgreSQL database (Supabase); uploaded files (photos, admission documents) are stored in Cloudflare R2 object storage. Both are accessed only over encrypted connections and only by the application on the school's behalf — never made publicly browsable. Files are served back through an access-controlled endpoint that checks the requesting user's school and role before returning anything.

EduSphere sets one essential session cookie on login to keep a user signed in; it is required for the product to function and cannot be disabled while remaining logged in. We do not use advertising or third-party tracking cookies.

We share data only where necessary to run the service: the hosting, database and storage providers named above (bound by their own security and processing terms), and — only for the specific transaction — the bank, JazzCash or Kuickpay/1LINK payment processor a School has enabled for fee collection. We do not share data with data brokers or advertisers.

Data is retained for as long as a School's subscription is active, so the school year's records stay available. On cancellation, a School may request an export of its data before deletion, subject to any legal retention obligations (for example, financial records a school may be required to keep). Audit logs are append-only and kept for security accountability.

Parents, students and staff who want to review, correct or request deletion of their personal data should contact their School's administration first — Schools control their own records and can action most requests directly from EduSphere. Where a School cannot resolve a request, they may escalate it to us via the contact below.

EduSphere is built for schools, so student records necessarily include minors' data. That data is entered and controlled by the School (the child's guardian relationship is verified by the School at admission), visible only to that student's own guardians and the school's staff, and is never used for marketing or shared outside the purposes described in this policy.

We may update this Privacy Policy from time to time. Material changes will be highlighted in-app or by email to School administrators ahead of taking effect.

Questions about this policy can be sent to your School's administration contact listed on your School's EduSphere account, or via the contact details published on your School's subdomain.