Shepherd's Hook

Sub-processors

Shepherd's Hook · Last updated October 25, 2026

To run Shepherd's Hook we rely on a small set of trusted outside companies ("sub-processors"). Each one handles only the specific data its job requires — not a copy of everything. This page lists them, what they do, and what data reaches them, so your church and its attorney can see the whole supply chain in one place.

Several of these are optional — they only come into play if your church turns on a feature that uses them (texting, calendar sync, AI, and so on). Those are marked below.

Core providers (always in use)

ProviderWhat it doesWhat data it handles
Supabase Hosts the database, account sign-in, and file storage — the heart of the app. Your church's records (people, notes, lists), uploaded files, and account credentials (passwords stored only as one-way hashes). Data is encrypted at rest.
Netlify Hosts and delivers the web app itself (the pages and code your browser loads). Standard web request information (such as IP address) needed to serve the app. The app's data lives in the database, not here.
Cloudflare Provides the sign-in bot-check (Turnstile) that blocks automated abuse of login and sign-up. A verification token and basic request signals at the moment someone signs in or signs up.
Resend Sends the app's email (sign-in confirmations, notifications, password resets). Recipient email address and the content of that email.
Apple (Push Notification service) Delivers push notifications to the iOS app. A device push token and the notification content.
Browser push services Deliver web push notifications to browsers that opt in (operated by the user's browser maker, e.g. Apple, Google, Mozilla). An anonymous push subscription and the notification content.

Optional providers (only if your church uses the feature)

ProviderFeatureWhat data it handles
Anthropic (Claude) Optional AI features (summaries, drafting help, receipt reading). Off until a church opts in. Only the specific text or image sent for that one task. Not used to train AI models. See AI & Your Data.
Stripe Subscription billing, if/when your church pays for the service. Billing contact and payment details — entered on Stripe's own pages. Card numbers never touch our servers.
Twilio Text messaging (SMS), where a church has it enabled with its own number. Recipient phone number and message content. SMS records are kept briefly; opt-out (STOP) records are kept to honor the opt-out.
Planning Center Optional link to a church's Planning Center account to bring in people data. Read-only access to the church's Planning Center records it chooses to connect. Minor/child details are filtered out on the way in.
Daily.co Voice and video calls in Team Room, where enabled, with optional transcription. Call audio/video between participants, and a transcript only if the church turns transcription on.
Google (Calendar & Sheets) Optional two-way calendar sync and an optional private data feed to a church's own Google Sheet. Only the calendar events or sheet rows the church chooses to sync. Sensitive care reasons are excluded from the sheet feed.

What they are not allowed to do

Changes to this list

We keep this page current. If we add or change a sub-processor that handles personal data, we'll update this page. Churches that have a Data Processing Agreement with us can ask to be notified of material changes.

Questions

Email support@shepherdshook.org.