Security Overview
Last updated 21 October 2026
A plain-language summary of how we protect the information churches trust us with. It describes what is in place today, not aspirations.
Access control
- Four fixed roles (Administrator, Service Planner, Ministry Leader, Volunteer), scoped by department.
- Every request is checked against the signed-in user's church and role on the server.
- Each church's data is separated from every other church's data.
Accounts
- Passwords are stored as salted hashes, never in plain text.
- Sign-in attempts and sensitive endpoints are rate limited.
Children's ministry
- Check-out is limited to recorded parents or guardians. A leader releasing a child to anyone else must state a reason, which is audit-logged. Children are never contacted directly; messages go to their responsible adults.
- Messages to families are logged.
Infrastructure
- Traffic is encrypted in transit (HTTPS).
- The database is on dedicated storage separate from the application, with regular backups.
- We run internal security reviews covering authentication, tenant isolation, uploads and public pages.
Reporting a problem
If you believe you have found a security issue, please contact us with details. Do not access data that is not yours. See also our Privacy Policy.
Questions? Contact us.