Security & Data Protection
This page explains, in plain language, how Shepherd's Hook protects the information your church puts into the app — your people, your care notes, your files. It's written so your leadership and your attorney can see exactly what we do and, just as important, what we don't. Where a protection comes from the companies that host us rather than from our own code, we say so.
For the full list of what we collect and why, read the Privacy Policy. For the outside companies that help run the service, read Sub-processors.
1. Your church's data is walled off from every other church
Shepherd's Hook serves many churches from one system, but no church can see another church's data. Every record — every person, note, file, message — is stamped with the church it belongs to. The database itself enforces the rule, on every single read and write, using what's called row-level security: the database checks who you are and which church you belong to before it returns a single row. This isn't a filter in the app that could be bypassed by a clever request; it's enforced one layer below the app, at the database.
A signed-in user only ever reaches data for a church they are a member of. If someone belongs to more than one church (say a pastor who helps two congregations), they switch between them explicitly and only ever see one church's data at a time.
2. Inside your church, it's need-to-know
Being a member of a church in the app does not mean seeing everything. Access is layered:
- Roles. Each person is an executive, an admin, or a member. Sensitive actions (managing the church, editing other people's roles, running the most sensitive reports) are limited to the higher roles.
- Care assignments. A leader generally sees the people assigned to their care, not the whole congregation's private history.
- Private care notes. The most sensitive notes — why someone is being stepped back from a list, a pastoral reason for pausing follow-up — are held in a separate, locked-down place that only your lead team and the people directly responsible for that person can open. They are not visible to ordinary members.
- Module-level limits. Add-on areas (Check-In, Expenses, Team Room, Documents) carry their own roles, so, for example, a volunteer helping with child check-in doesn't thereby get access to the care lists.
The short version: a leak inside a church is just as much a concern as a leak between churches, and the app is built so that most people see only what their role and their assignments call for.
3. Encryption
In transit. Everything between the app and our servers travels over encrypted connections (HTTPS/TLS). The app is configured to refuse plain, unencrypted connections, so data isn't sent in the clear.
At rest. The databases and file storage that hold your data are encrypted on disk (AES-256) by the infrastructure providers we build on (see Sub-processors). This at-rest encryption is provided and managed by those hosting providers as a standard part of their platform. Uploaded files (photos, receipts, documents, check-in attachments) are kept in private storage — they are not public on the open web, and reaching one requires a signed, time-limited link issued only to someone whose role allows it.
4. A record of who changed what
Shepherd's Hook keeps an audit log of sensitive changes to people's records — who made the change, what changed, and when. This is how your leadership can answer questions like "who moved this person off the list, and when?" The audit log is readable only by the platform administrator, and audit entries are kept for 12 months. Several newer areas of the app (Tasks, Documents, Team Room) additionally keep their own history of changes.
One practical note: the audit log records changes from the point it was introduced onward, so changes made before then aren't included in it.
5. Signing in
Accounts are handled by our authentication provider (see Sub-processors). Passwords are stored only in the one-way hashed form the provider keeps — we never see or store a readable password. Sign-up and sign-in pages are protected against automated abuse by a bot-check (Cloudflare Turnstile). On a personal device, members can add Face ID / Touch ID or a device passcode as a lock on the app.
A couple of specifics worth noting:
- Two-factor authentication (2FA). A second-factor login is required for the platform administrator account. Church members secure their own accounts with a password and, on a personal device, Face ID / Touch ID or a device passcode.
- Roles within a church are not separate logins. Each person has their own account; roles (executive, admin, member, and the care and module roles) simply control what that signed-in person can see.
6. When Shepherd's Hook staff can see your data
To provide support, investigate a problem you report, or keep the service running, a member of Shepherd's Hook's own staff may need to access a church's data or view the app as it appears to your church. We limit this access to what support and operations genuinely require, and we never sell your data or use your church's private information for anything other than running the service for you.
This kind of operator access is a normal part of running a hosted service. If your church needs a stricter arrangement — for example, access only with your per-request approval, or a detailed log of each access — we can set that out in a written agreement with you. Just ask.
7. How long we keep things, and getting your data out
We keep data for as long as your church uses the service, and apply shorter limits to specific operational records (for example, child check-in activity and certain logs age out on their own). The Privacy Policy lists the specific retention periods.
- Export. Your church can export its lists and records from inside the app. Your data is not locked in.
- Delete your account. An individual can delete their own account from the app.
- Close a church. A church can be closed and its data deleted. When that happens we keep a minimal record that the deletion occurred (for about 90 days) and then remove it.
8. If something goes wrong (data breach)
If we discover a security breach that affects your church's personal data, we will notify your church without undue delay after confirming it, tell you what we know about what happened and what data was involved, and explain the steps we're taking and what we recommend you do. We maintain a written internal incident-response procedure for detecting, containing, and recovering from such events.
9. The companies we rely on
Shepherd's Hook is built on established cloud providers for hosting, the database, file storage, email, and optional features like text messaging and AI. Each one only receives the specific data its job requires, and we choose providers that offer their own strong security. The full list, and what each one handles, is on the Sub-processors page. Our use of AI, and the strict limits on it, is described on the AI & Your Data page.
10. Questions, or a review by your attorney
We welcome a review by your church's counsel. Email support@shepherdshook.org with questions, to request our Data Processing Agreement, or to set up a stricter data-handling arrangement for your church.
Shepherd's Hook