Skip to content

Security

How we protect your school’s data

School records, results and payments deserve serious care. Here is what we do, in plain language.

Each school is kept apart

Every record belongs to one school, and the database itself enforces it with PostgreSQL row-level security. Even if a request were mistaken, the database refuses to return another school’s rows. Automated tests check this on every change.

People only see what their role allows

Teachers see score sheets for their own subjects and classes, bursars see fees, parents see only their own children, and students see only their own work. Schools choose who gets which role.

Encryption and passwords

  • HTTPS everywhere, with HSTS so browsers never fall back to an unencrypted connection.
  • Passwords are stored as salted hashes, never in plain text. New accounts must change their one-time password at first sign-in.
  • Sign-in attempts are rate-limited to slow down password guessing.

Payments

Card and bank details are entered on Paystack’s secure checkout, never on ComfortEdu. Fees settle directly into each school’s own bank account; ComfortEdu never holds school money.

Web security

  • A strict Content Security Policy with per-request nonces blocks injected scripts.
  • Pages can’t be framed by other sites (clickjacking protection), and browser features like camera and location are switched off.
  • School portals are kept out of search engines.

Hosting

ComfortEdu runs on Vercel, Render and Supabase, with servers and the database in Frankfurt, Germany. Large institutions can choose a private, self-hosted installation.

Report a vulnerability

If you believe you have found a security issue, please email security@comfortedu.app with the details. Please don’t access other people’s data, disrupt the service or share the issue publicly before we have fixed it. We will acknowledge your report within 3 working days. Our security.txt has the same details.