Sub-processors
Who else handles your data.
The providers Folio uses, what each does, what it receives, where, and when.
Version 2026-10-25, effective
Related: Terms · Privacy · Data processing addendum · Cookies · Security
Providers
These providers handle personal data for Folio. The last column says when a church’s data reaches each one. Payment providers depend on the currency and country, so a church meets one or two of them.
| Provider | Role | What it does | What it receives | Where | When |
|---|---|---|---|---|---|
| Hetzner Online GmbH | Hosting | Servers that run Folio, its database, file storage and backups | Everything Folio stores, including church content | Falkenstein, Germany (EU) | Always |
| Cloudflare, Inc. | Network and CDN | Delivering and protecting the website and the app | Network address and request details of every visitor; page content in transit | Global network | Always |
| Resend | Email delivery | Sending sign-in codes, invitations, notices, notes and gift emails | Recipient address, first name if given, the message | [CONFIRM RESEND REGION] | Always |
| Deepgram, Inc. | Speech to text | Turning sermon audio and live services into transcripts and captions | Teaching audio and live audio a church sends to Folio | European Union endpoint by default (the exact country can change) [CONFIRM ENDPOINT AFTER DEPLOY] | Always |
| Google LLC (Gemini API) | Language model | Drafting notes, answering questions from approved teaching, matching questions to passages, screening for crisis wording | Transcript passages, the question asked, recent turns, the church’s voice and doctrine settings, facts a member chose to save | Google infrastructure, United States and elsewhere | Always |
| Stripe | Payments | Card payments for plans and gifts in US dollars, pounds and euros | Payer name, email, payment details entered on Stripe’s page, amount | United States and elsewhere | Where a church or giver is routed to it |
| Paystack | Payments | Card and bank payments in Nigerian naira and, where offered, other currencies | Payer name, email, payment details entered on Paystack’s page, amount | Nigeria and elsewhere | Where a church or giver is routed to it |
| Polar | Payments | Payments for plans and gifts | Payer name, email, payment details entered on Polar’s page, amount | [CONFIRM POLAR REGION] | Only if enabled for a church or giver |
| Lemon Squeezy | Payments | Payments for plans and gifts | Payer name, email, payment details entered on Lemon Squeezy’s page, amount | [CONFIRM LEMON SQUEEZY REGION] | Only if enabled for a church or giver |
| Sentry | Error reporting | Finding and fixing faults | Error details and request identifiers; no content is intended | [CONFIRM SENTRY REGION] | Only if enabled [CONFIRM] |
| PostHog | Website analytics | Counting page and button events on this website | Page and button events, network address | European Union by default | Only after you choose Allow analytics |
| Have I Been Pwned (Pwned Passwords) | Password safety check | Refusing passwords that appear in known breaches | The first five characters of a password hash; never the password or an email address | United States and elsewhere | When a password is set or changed |
| Google Fonts (Google LLC) | Typefaces | Loading the fonts used by this website and the app | Network address and browser details of every visitor | Google infrastructure | Always [REPLACE WITH SELF-HOSTED FONTS] |
| Langfuse | AI observability | Measuring model latency and token use | Flow name, model name, token counts, church identifier; no prompts or answers | [CONFIRM LANGFUSE HOST] | Only if enabled [CONFIRM] |
| Twilio, Termii, OneSignal, Expo | Text, WhatsApp and push messages | Delivering text, WhatsApp and push messages a church chooses to send, and care alerts to its team | Recipient number or device token and the message text | United States and elsewhere | Only if a church uses that channel and the provider is enabled [CONFIRM] |
Training and retention at vendors
Folio does not train models on church content. We send content to the speech and language-model providers only to get a result. We use plans under which they do not use that content to improve their own models, and which may keep it briefly for abuse monitoring. [OWNER TO CONFIRM BEFORE LAUNCH: Google Gemini API paid terms, and Deepgram’s Model Improvement Partnership setting]
Changes
We email church owners at least 30 days before adding or replacing a provider that handles church content, as the data processing addendum says. Questions or objections: [PRIVACY LEAD OR DPO NAME], [email protected].