HarvestFlow / Security and data protection
Security

How HarvestFlow protects the people your church cares for

A church's records say who came to faith, who is struggling and who asked for prayer. That is trust you have been given. Here is how HarvestFlow looks after it, in plain words.

Each church is kept separate

Every church has its own private workspace. The separation is enforced by the database itself, not only by the app: a person signed in to one church cannot read another church's records, whatever they try.

Everyone sees only what their role allows

  • Follow-up workers see only the converts given to them.
  • Cell leaders, undershepherds and department heads see the people in their care.
  • Pastors, admins and coordinators see the whole church, and decide who joins the team.
  • Members never sign in, so there are no member accounts to break into.

Encrypted, backed up and carefully accessed

  • Encrypted in transit: every connection to HarvestFlow uses HTTPS.
  • Encrypted at rest: our database provider encrypts stored data.
  • Backed up daily by our database provider.
  • Limited access: access to the live systems is limited to what is needed to run and support the service.
  • Sign-in protection: team members sign in with their own email and password, can reset a forgotten password themselves, and attempts are rate-limited.

Messages only to people who agreed

Welcome messages to first-time visitors go only to people who gave permission when they checked in. The church is the sender of every message and is responsible for having permission to contact each person. Children recorded in a family are counted at services but never messaged; anything for them goes to their parent or guardian.

AI features that never act on their own

Some features use AI providers to help your team: Barnabas, the in-app guide, answers questions about records the leader can already see; uploaded rotas and photos of convert cards or paper registers are read so nobody has to type them in; and spoken details are turned into text for voice registration.

  • Nothing is saved without a person. What is read from a photo or file is shown to the leader to check, and saved only when they confirm.
  • Barnabas can't change records by himself. He can prepare a change, such as marking people present, which happens only if the leader presses Confirm.
  • Only what is needed is sent, and the providers are named in our privacy policy.

Your data stays yours

  • Export at any time: download your records as CSV files.
  • Deletion on request: if your church asks us to delete its workspace, we delete its data, except anything the law requires us to keep. Backups are overwritten on our provider's normal schedule.
  • Never sold: we do not sell personal information and never use church data for advertising.

Data protection law

Records about faith and church life are sensitive information in many countries, including under UK GDPR and Nigeria's Data Protection Act. Your church decides why and how it records people, so it is the controller; HarvestFlow processes that data on the church's behalf and on its instructions. Churches are responsible for having a proper basis, and where required consent, for what they record. Our providers may process data outside your country, using the safeguards they offer, such as standard contractual clauses. The full details are in our privacy policy and terms.

Frequently asked questions

Can another church see our data?

No. Every church has its own workspace, and the database itself refuses to return one church's records to anyone signed in to another church.

Do you sell or advertise with church data?

No. We never sell personal information and never use church data for advertising.

Can we take our data with us, or delete it?

Yes. Churches can download their records as CSV files at any time. If a church asks us to delete its workspace, we delete its data, except anything the law requires us to keep.

Who is responsible for the data under data protection law?

The church decides why and how it records the people it cares for, so it is the controller. HarvestFlow processes that data on the church's behalf and on its instructions.

Found a problem?

If you think you have found a security issue, or have a question about how your church's data is handled, email adeniyi.tosin@harvestflows.com. We will look into it straight away.

Care for every person, safely

Register your church free and have your workspace ready within 24 hours.

Register your church free