Subprocessors.
Emito Consulting Service LLC uses the third parties below to deliver Holy. Each one is bound by a written agreement, processes data only on our instructions, and receives no more than its function requires.
Core infrastructure
These services are required to deliver Holy and process customer data on our instructions.
| Subprocessor | Purpose | Data processed | Processing location |
|---|---|---|---|
| Amazon Web Services (AWS) | Application hosting, CDN, file-backup storage, encryption key management, logging, and speech-to-text for optional sermon transcription (Amazon Transcribe) | All customer data in transit and at rest; application logs | United States |
| Supabase | Managed PostgreSQL database, authentication, file storage | All customer data; user credentials and session records | United States (on AWS) |
| Stripe | Payment processing for church subscriptions and online giving | Donor and payer name, email, billing address, payment details (entered directly into Stripe), transaction records | United States (global processing) |
| Amazon SES | Transactional and bulk email delivery | Recipient name and email address, message content, delivery events | United States |
| AWS End User Messaging | SMS and MMS delivery | Recipient phone number, message content, delivery events | United States |
| Expo (Expo Application Services) | Push-notification delivery to the mobile apps | Device push tokens, notification title and body | United States |
Supporting services
These services support operations, safety or optional features and receive limited data.
| Subprocessor | Purpose | Data processed | Processing location |
|---|---|---|---|
| Sentry | Application error and performance monitoring | Error diagnostics with identifiers (user ID, church ID, request ID). Payloads are scrubbed of credentials and message bodies before they are sent. | United States |
| Cloudflare (Turnstile) | Bot protection on public forms (registration, giving, contact) | Visitor IP address and a verification token | Global edge network |
| Anthropic | Optional AI assistance features (sermon assistance, natural-language list building, dashboard questions, person summaries). A church can switch all of them off from one setting, and while it is off nothing is sent here at all. Customer data is not used to train any model. | The text of the request. Dashboard questions send aggregate statistics only — never member names, contact details or individual gifts. List building sends the church’s own tag and category names, never person records. Sermon assistance sends the one sermon chosen. A person summary sends one person’s first name, attendance and serving figures, giving totals (only for a user allowed to see giving) and shared notes — never a surname, contact details, birth date, medical or household records, or pastoral notes. It is never run for anyone recorded as under 18, or whose age isn’t on file — judged by the date of birth on file or, when none is recorded, by a child record, a school grade from pre-K to 12th, or a household role of child or dependent; someone with no date of birth, no school grade and no household role has no age on file. | United States |
| Checkr | Background checks for volunteers, where a church enables the integration | Volunteer name, date of birth and identifiers required to run the check, submitted by the church | United States |
| Cal.com | Demo scheduling on this marketing site only | Name and email of the prospect booking a demo. No church member data. | United States / EU |
Your church’s own integrations
A church may connect Holy to services we do not control — for example by creating an API key, subscribing a webhook endpoint, or connecting its own Stripe account. Data sent to those destinations is processed under the church’s own agreement with that provider, not this list.
Changes to this list
We will publish an update here, and notify customers by email, at least 30 days before a new subprocessor begins processing customer personal data. To receive those notices, email privacy@holyplatform.com and ask to be added to the subprocessor notification list. Our Data Processing Addendum sets out the objection process.