Privacy Policy
Last updated: 8 November 2026
HarvestFlow is a web platform that helps churches follow up new converts, first-time visitors and members. This policy explains what information we handle, why, who helps us handle it, and the choices you have. If anything here is unclear, write to adeniyi.tosin@harvestflows.com.
1. Two roles: our own data and your church's data
- Our own data is information about people who visit our website, register a church, subscribe to our blog or message our support assistant. For this, HarvestFlow decides how the information is used.
- Church data is information a church puts into its workspace: converts, first-time visitors, members, workers, attendance, follow-up notes and messages. For this, the church decides why and how it is used, and HarvestFlow processes it on the church's behalf and on its instructions.
If you are a convert, visitor or member of a church that uses HarvestFlow, your church is the best contact for questions about your record, including requests to see, correct or delete it. We will help the church respond.
2. What we collect
When you visit www.harvestflows.com
- Standard technical data our hosting provider receives with every request (such as IP address, browser and pages requested).
- Anonymous visit statistics from Vercel Web Analytics: which pages are viewed, the site that linked to us, and broad details such as country and device type. It uses no cookies and does not identify you.
- If you accept it in the banner, the Meta (Facebook) Pixel, which sets cookies and sends page-view information to Meta so we can measure our advertising. It does not load if you decline.
- A small note in your browser's storage recording your cookie choice and whether you dismissed our announcement bar.
When you register a church
- Church name, your name, phone number, email address, church location and country, church size, outreaches per year, and any note you add.
- How you found us: your answer to "How did you hear about HarvestFlow?" if you give one, the website that linked you to us (for example a search engine), and the first page of our site you visited. Nothing is stored on your device to do this.
- We use these to create your workspace, email you a login link, and contact you about setup and support. We also receive an alert about each new registration.
When you subscribe to our blog
- Your email address. The page also embeds a Substack sign-up form, which Substack handles under its own policy.
When you use the support chat
- The messages you type. They are sent to our AI provider (Anthropic) to produce a reply. Please do not put sensitive personal details in the chat.
Inside a church workspace (entered by the church and its team)
- Details of converts, visitors and members such as name, phone number, gender, age, location, decision type and discipleship milestones, and notes, call logs and attendance.
- This can reveal religious belief or practice, which is sensitive information in many countries. Churches are responsible for having a proper basis, and where required consent, for recording it.
- Login details for the church's team members.
3. How we use information
- To provide and secure the service, including sign-in, follow-up tracking, reports and messaging.
- To send service emails such as login links and notices.
- To answer support requests and improve the product.
- To measure our advertising, only if you accept the Meta Pixel.
- To meet legal obligations.
We do not sell personal information, and we do not use church data for advertising.
4. Who helps us run HarvestFlow
We share information with these service providers only as needed to provide the service:
| Provider | What it does | Information involved |
|---|---|---|
| Supabase | Database and sign-in | All church data and account details |
| Vercel | Website and application hosting, and anonymous visit statistics for www.harvestflows.com | Requests to our sites |
| Resend | Sends our emails | Recipient email addresses and message content |
| EbulkSMS | Delivers SMS and WhatsApp messages a church chooses to send | Recipient phone numbers and message text |
| OpenAI | Turns spoken details into text for voice registration | The audio a worker records |
| Anthropic | Powers Barnabas, the in-app guide, and the support chat, and reads files and photos a leader uploads (a ministers' rota, convert cards, a paper attendance register) | The questions asked, the church records Barnabas reads to answer them, and the uploaded file or photo with the names it is matched against |
| Meta | Advertising measurement (Meta Pixel), only with your consent | Page views and browser identifiers |
| Substack | Newsletter sign-up form | Email address you enter there |
We may also disclose information if the law requires it, or to protect people from harm or fraud.
5. Barnabas and other AI features
Barnabas answers questions using the records the signed-in person is allowed to see. To do this, the relevant records and the question are sent to Anthropic. Barnabas can also prepare a change, such as marking people present, which is made only if the leader presses Confirm. When a leader uploads a rota file or a photo of convert cards or a paper register, it is sent to Anthropic to be read, together with the church's list of names it should be matched to; the leader checks the result before anything is saved. Voice registration sends the recording to OpenAI to transcribe it. AI output can be wrong, so check anything important before acting on it.
6. Messaging
When a church sends SMS or WhatsApp messages through HarvestFlow, the church is the sender. The church is responsible for having permission to contact each person and for following the messaging rules that apply where its contacts live.
7. International transfers
Our providers may process information in countries other than yours, including outside the UK, the European Economic Area and Nigeria. Where the law requires safeguards for such transfers, we rely on the safeguards our providers offer, such as standard contractual clauses.
8. How long we keep information
- Church data is kept while the church's workspace is active. Churches can export their data as CSV at any time.
- When a church asks us to delete its workspace, we delete its data, except anything we must keep to meet a legal obligation. Backups are overwritten on the provider's normal schedule.
- Registration and support records are kept for as long as needed to run the service and handle any disputes.
9. Security
Each church's data is kept separate from every other church's, and a worker only sees the records their role allows. Data is encrypted in transit, and our database provider encrypts stored data. Access to production systems is limited to what is needed to run and support the service. No system is perfectly secure, so please choose strong passwords and keep login links private.
10. Your rights
Depending on where you live, you may have the right to access, correct, delete or export your information, to object to or restrict how it is used, to withdraw consent, and to complain to your data protection authority (in the UK, the Information Commissioner's Office). For information about you in our own records, email us. For information in a church workspace, contact the church; we will assist it.
11. Children
HarvestFlow is for adult church workers and leaders. Churches may record information about young people they minister to, and are responsible for having the permission of a parent or guardian where the law requires it.
12. Cookies and similar technologies
Our website uses browser storage for your preferences. The Meta Pixel sets cookies only after you accept. The application at app.harvestflows.com uses browser storage to keep you signed in and to work offline, and it does not use the Meta Pixel or any advertising cookies. You can change your cookie choice at any time with the "Cookie choices" link in the site footer. Some pages show our videos from YouTube in its privacy-enhanced mode: nothing is loaded from YouTube until you press play, and from then YouTube (Google) may set cookies under its own policy.
13. Changes to this policy
We will update this page when our practices change and show the new date at the top. For significant changes, we will also tell registered churches by email.
14. Contact
HarvestFlow, adeniyi.tosin@harvestflows.com