Stewardship of data is stewardship of people.
A church database holds stories people trusted you with. This page says, specifically, how we protect them. No badges, no vague reassurance: just the actual behavior of the platform, in plain language.
How your data is protected.
Encrypted, both directions
Every church, strictly separate
Permissions per person
Abuse kept out
Backups that are actually tested.
- Backed up nightly, every night, automatically.
- Encrypted before leaving the server, then stored off-site in a separate location from production.
- Multiple restore points retained: daily, weekly and monthly generations.
- Backup integrity is verified on a weekly schedule, not assumed.
- Monitoring alerts us if a backup run is ever missed, and documented restore procedures exist for the day we hope never comes.
Your church's data, on your instructions.
Under POPIA, your church remains the responsible party for its congregation's personal information, and Church Flow acts as an operator: we process it on your instructions, to provide the service, and for nothing else. We do not sell, mine or advertise against your data.
What happens if you leave.
Your records belong to your church. While your workspace is open, you can export your people, contacts, giving, events, forms and website content at any time, as CSV and JSON. Check-in and group reports download separately, from their own pages. If you cancel, your workspace stays open to the end of your paid period, so you can export your records first. Then it is suspended with nothing deleted, and for 90 days our team can export everything for you or switch it back on.
No certification theater.
We do not hold SOC 2 or ISO 27001 certification, and we will not imply otherwise with borrowed badges. What you get instead is this page: specific, verifiable behaviour, kept current. Found something that worries you? Write to us and a real person will answer.