Security
Your church's information, kept safe
Churches trust us with staff details, volunteer schedules and plans for the year. Here's how we protect them.
Every church kept separate
Each church's data is walled off by the database itself (row-level security), not just by what the screens show. Every permission is checked on the server for every request.
Tested on every change
Automated security tests try to cross from one church into another and to go beyond each role's rights. Every change must pass them before it ships.
Protected sign-in
Sign in with a password, an emailed sign-in link or Google. Sign-in forms have bot protection, and invites and emails are rate-limited.
Backed up and tested
Daily database backups, plus a weekly encrypted copy kept with a separate provider. Every month we restore that copy into a fresh database and check every table.
Payments by Stripe
Cards are entered on Stripe's secure checkout. Nehemiah never sees or stores card numbers.
Connections stay on the server
Planning Center and Google connection keys are stored encrypted on the server and never reach a browser. Nehemiah only writes to Planning Center what your church turns on.
In practice
The everyday details
- All traffic is encrypted (HTTPS), and data is encrypted at rest by our database provider.
- When our team helps inside your account, it's because you asked, and every support visit and change is recorded in an audit log.
- Error reports strip personal details before they leave your browser.
- Giving reports are seen only by Super Admins and the people your church marks as Finance.
- Canceling keeps your data; you can ask us to export or delete it.
Who runs what
See the Privacy Policy for what each one handles.
Found a security problem?
Please tell us privately at security@nehemiahos.com. We'll reply quickly and keep you posted while we fix it.