In plain words
Your church’s information lives in a database in Australia. A few providers help us send email, host the app, catch errors and deliver notifications. Here is each one, what it gets, and where.
This summary helps you read the document. The full text below is what applies.
1. Providers we always use
These providers help us run Shep for every church. Discipleship and care information is stored only in the Australian database. Other providers receive only what their job needs.
| Provider | What for | Information | Location |
|---|---|---|---|
| Supabase | Database, file storage and sign-in | All account and church data | Australia (Sydney) |
| Vercel | Application hosting and scheduled jobs | Requests in transit, server logs (including IP address) | Australia (Sydney); requests first reach Vercel’s nearest edge location |
| MailerSend | Sending emails (invitations, reminders, summaries) | Name, email address, email content | European Union and United States |
| Sentry (Functional Software Inc.) | Error monitoring and masked session replay | Error details, device and browser information, user ID; replays have all text masked and media blocked | United States |
| PostHog Inc. | Product analytics, masked session replay and in-app surveys | User and church IDs, role, pages viewed, features used, device and browser information; replays have all text and inputs masked and images blocked | European Union (Frankfurt) |
| Google (Tag Manager and Analytics) | Website and product usage analytics | Pseudonymous identifiers, pages viewed, device and browser information | United States and global |
| Adobe Fonts (Adobe Inc.) | Serving the heading typeface on Shep’s pages | IP address and browser details sent with each font request; no cookies | United States and global |
| Push services (Google, Apple, Mozilla, Microsoft; Apple Push Notification service for the iPhone app) | Delivering push notifications a person has switched on | Notification title and body, device push endpoint or device token | United States and global |
2. Services your church chooses to connect
These are only used if your church connects them. Your church decides what is shared and is responsible for its own agreement with each provider.
| Provider | What for | Information | Location |
|---|---|---|---|
| Elvanto (Tithe.ly) | Sync people, groups and visitor connect cards | Names, contact details, group membership | Per the church’s Elvanto account |
| Planning Center | Sync people and groups | Names, contact details, group membership | United States |
| Breeze ChMS | Sync people and groups | Names, contact details, group membership | United States |
| Mailchimp (Intuit) | Sync contacts to the church’s mailing lists | Names, email addresses | United States |
| Slack | Post notifications into the church’s workspace | Notification content the church configures | United States |
| Zapier | Send events to tools the church chooses | Event data the church configures | United States |
3. Changes to this list
We email church admins at least 30 days before adding or replacing a provider in the first table, as our data processing terms describe. To ask for a provider’s data protection terms, email privacy@shephub.com.
Version history
| Version | In force from | What changed |
|---|---|---|
| 2.1 | 27 October 2026 | Added PostHog (EU) for product analytics. |
| 2.0 | 23 October 2026 | First published. |
Earlier versions are available on request from privacy@shephub.com.
Questions about this document
Write to us and a real person will reply, usually within two business days.
privacy@shephub.com