Privacy
How this site handles your information
This site takes signups so a city's community leads can welcome you, and gives those leads simple tools to run their community — a contact list and records of how events went. Here is what that involves, in plain words. Last updated 6 September 2026.
What the signup form collects
When you join a community you're asked for your name, WhatsApp number, and email; where you work and your role; how you heard about us; and what you hope the community can do for you. Some questions are optional — a LinkedIn profile, a church affiliation, a short self-introduction — and the form works fine without them. Event signups may add a few questions specific to that gathering. The form also records that you accepted the community guidelines (and which version), and whether you ticked the box saying the community may contact you.
Browsing the site asks for nothing: no account, and no analytics or advertising trackers of our own.
The AI helpers, if you use them
Two parts of the form use AI, and both run only on what you typed into the form. The follow-up questions step sends your answer about your hopes — along with where you work and how you heard about us, if you filled those in — to Anthropic's Claude to pick one or two gentle follow-up questions; the optional “draft it for me” button sends your name, work, hopes and how you heard about us to draft a short introduction you can edit or discard. Nothing is looked up about you elsewhere, and skipping the draft button skips that request entirely.
Where it's kept, and who sees it
Signups are stored in the site's database (hosted on Supabase). Where a city has enabled the Google Sheets mirror, new signups are also copied to a Google Sheet its leads work from. The people who work with your details are your city's volunteer leads and the regional leads who support them — they use the site to welcome you, keep their contact list current (which can include bringing in records from lists kept before this site, and taking out reports of how events went), and understand how the community is going. Your details are not sold. Like any website, this one also runs on ordinary hosting infrastructure, which handles the traffic needed to serve pages and keep the service running.
The WhatsApp community itself runs on WhatsApp, so what you post there is handled under WhatsApp's own terms — and under the community's guidelines, which ask everyone to keep prayer requests and stories inside the group.
Keeping bots out
The form is public, so submissions are rate-limited by IP address and may be checked by Cloudflare Turnstile, which verifies you're a person without a puzzle. The rate limiter holds addresses briefly in memory and your IP is not stored with your signup.
Cookies
The app itself sets no cookies on the public pages. The only cookies our own code sets belong to the lead sign-in — session cookies that keep a community lead logged in to the admin, which nothing on the public pages touches. Two third parties can appear: the resource library is an Airtable page embedded only when you ask for it, under Airtable's own cookies and privacy policy; and on forms where the bot check is switched on, that check is served by Cloudflare.
Corrections and removal
If you want your details corrected or removed, tell your city's leads — message them in the WhatsApp community, or reach the community through the contact page and they'll sort it out.
You can also go straight to FaithTech: its privacy policy (opens in a new tab) names privacy@faithtech.com for questions about accessing, correcting, or removing your information, or about consent.