EzSchoola

Privacy Policy

Last updated: 1 November 2026. This policy is a beta-stage draft — it will be reviewed by counsel before any public launch, and schools using this beta will be notified of material changes.

1. Who this applies to

This policy covers school staff, parents/guardians, and — where a school enrolls a student on the platform — the student data entered by that school's staff. If you are a parent or guardian, your school's administration is the primary controller of your child's data; EzSchoola (operated by Raudhah Tech) is the processor acting on the school's instructions.

2. What we collect

  • Account data: name, email, role, and school/campus affiliation for staff and parents.
  • Student records entered by school staff: enrollment, guardians, attendance, grades and report cards, behavior/merit records, Islamic studies (hifz/Quran) progress, and fee/invoice history.
  • Admissions data submitted through a public apply form: applicant and parent contact details, requested level, and application status.
  • Communications sent through the platform: announcements and messages between staff and parents.
  • Basic technical data: sign-in timestamps and an audit log of administrative actions, for security and troubleshooting.

3. How it's used

Data is used only to operate the school-management features you see in the product: running admissions, attendance, academics, fees, communications, and the AI features (daily briefs, at-risk detection, hifz coaching, message drafting) that summarize a school's own data back to its own staff. We do not sell student or parent data, and we do not use it to train third-party AI models beyond the single request needed to generate that feature's response.

4. Who can see what

Access is role-based and scoped to campus: a teacher sees their own classes, a principal sees their campus, a parent sees only their own child(ren). This is enforced at the database level (row-level security), not just in the app's UI.

5. Where data is stored

Application data is stored in Supabase (PostgreSQL). The application itself runs on Cloudflare Workers. AI features route requests through OpenRouter. Payment processing, once enabled, will be handled by Stripe — card details are never stored by EzSchoola directly.

6. Children's data

Student records are entered and managed by school staff acting on behalf of the school, not collected directly from children. Parents/guardians should direct questions about their child's specific data to their school's administration in the first instance.

7. Retention & deletion

Data is retained for as long as a school's account is active, plus a reasonable period after to allow for account recovery. A school administrator can request deletion of their school's data by contacting us at the email below.

8. Contact

Questions about this policy or a data request: hello@ezschool.app.