Roles
In plain words: Your church owns its congregation's data. Gather only handles it to provide the Service you asked for.
These terms form part of the Terms of Service between Andrew Bernadel, doing business as Gather (“Gather”) and each church using Gather (the “Church”). For personal information the Church adds to or collects through Gather about its members, volunteers, and visitors (“Church Data”), the Church is the controller (the “business” under U.S. state privacy laws) and Gather is the processor (“service provider”).
What we do with Church Data
In plain words: Only what's needed to run Gather for you. We never sell it or use it for anything else.
- We process Church Data only to provide, secure, and support the Service, and on the Church's documented instructions — which include its admins' actions in Gather.
- We don't sell or share Church Data, use it for advertising, combine it with data from other sources, or keep it for any purpose outside our relationship with the Church.
- If we believe an instruction breaks the law, we'll tell the Church.
Confidentiality
In plain words: Anyone at Gather who can access your data is bound to keep it confidential.
Everyone authorized to process Church Data is bound by confidentiality, and access is limited to what each person needs for their role.
Security measures
In plain words: Encryption, per-church isolation in the database, and least-privilege access.
- Encryption in transit (TLS 1.2+) and at rest.
- Row-level security in the database so one church can never read another's data, with privileged actions checked on the server.
- Passwords stored only as one-way hashes by our authentication provider.
- Least-privilege production access, with service credentials kept out of client apps.
- Error reporting configured not to collect user identities or request bodies, and to mask screen replays.
- Rolling backups retained for up to 30 days.
Subprocessors
In plain words: These are the only companies that touch your data. We'll give you notice before adding a new one.
The Church authorizes Gather to use the subprocessors below. Each is bound by written terms that protect Church Data at least as well as these. We'll update this page and email church admins at least 30 days before adding or replacing a subprocessor; a Church that reasonably objects may cancel and receive a pro-rated refund of prepaid fees.
| Provider | What they do for us | Data involved | Where |
|---|---|---|---|
| Supabase | Database, sign-in, and photo storage | All account, profile, and church data | United States |
| Vercel | Hosting for the website and web app, and anonymous page-visit counts (Vercel Web Analytics, no cookies) | Web requests, including IP address (not stored by the analytics) | United States |
| Brevo | Sending email (reminders, receipts, demo replies) | Name, email address, message content | European Union |
| Expo | Delivering push notifications to the mobile app | Push token, notification text | United States |
| Sentry | Crash and error reports | Device and app details, masked screen replays around an error | United States |
| Stripe | Subscription billing for churches | Billing contact and payment details (we never see full card numbers) | United States |
| OpenStreetMap (Nominatim) | Turning a church's street address into map coordinates | Church address only | United Kingdom / European Union |
| Apple and Google | App distribution and push delivery to devices | Push token, notification text | United States |
Helping with requests
In plain words: If one of your members asks to see or delete their data, we'll help you handle it.
Gather gives admins tools to view, edit, and remove members, and members can delete their own accounts. If we receive a request directly from one of the Church's members about Church Data, we'll point them to the Church or, where the request is clear, handle it and let the Church know. We'll reasonably help with data-protection assessments and regulator inquiries that relate to Gather.
If something goes wrong
In plain words: If there's a breach affecting your church's data, we tell you within 72 hours of confirming it.
We'll notify the Church's admins without undue delay, and no later than 72 hours after confirming a security incident that affects Church Data. We'll explain what happened, what data was involved, and what we're doing about it, and we'll help the Church meet its own notification duties.
When a church leaves
In plain words: Ask for a copy, then we delete everything within 30 days.
When a Church closes its account, it can ask for an export of its Church Data in a standard format by emailing support@gatherministry.online. We then delete Church Data within 30 days, including from backups as they expire, unless the law requires us to keep something.
Information and audits
In plain words: Ask us anything about how we protect your data, and we'll answer in writing.
On request, we'll provide the information reasonably needed to show we comply with these terms, including written answers to security questionnaires, once a year or after an incident.