How we keep your data safe.

Encryption

• All traffic is encrypted in transit with TLS 1.2 or higher.
• Data at rest is encrypted by our managed database provider.
• Safeguarding chat content is encrypted at column level so that even privileged database operators do not see plaintext.

Access control

• Row-Level Security on every public-schema table.
• Authenticated reads are scoped to the user's own school.
• The Designated Safeguarding Lead is the only role allowed to read safeguarding chat content.
• Engineering access to production data is logged, least-privilege, and limited to those who need it for support or incident response.

Authentication

• Email and password (with Have-I-Been-Pwned breach check) and Google single sign-on for staff.
• Per-class login code for pupils - no surname, date of birth or contact details are collected.
• Session tokens are short-lived JWTs stored in the browser; we do not store passwords ourselves.

Retention and deletion

Soft-deleted accounts are permanently purged by a nightly database job 30 days after deletion. Safeguarding flags are capped at 7 years from creation. Pastoral-context audit rows are kept for 90 days. Email send logs are kept for 12 months. See the privacy notice for the full retention schedule.

Backups

Our database provider performs daily managed backups with point-in-time recovery. The recovery window is set by the provider and reviewed annually.

Incident response

We follow a documented breach procedure. On confirming a personal-data breach we will notify the affected school's nominated contact within 24 hours, with rolling updates, and assist the school with its Information Commissioner's Office notification within the 72-hour statutory window. To report a vulnerability, email security@classprayer.app.

More for compliance teams

School DPOs can request our Data Processing Agreement, DPIA, retention schedule and breach procedure by emailing info@classprayer.app. The current list of sub-processors is at classprayer.app/subprocessors.