Sub-processor list

This list names the third-party service providers (sub-processors) that Orravo Web Technologies engages to help provide the EcclesiaOne platform, and that may process personal data on Orravo's behalf. It forms part of the Data Processing Agreement.

We require each sub-processor by contract to protect personal data and to process it only as needed to provide its service to us. We update this list when we add or change a sub-processor, and we notify tenant administrators by email at least 30 days before the change takes effect.

How to read this list

For each sub-processor we give the service it provides, the type of data involved, and the processing location.

Some entries are used by every institution because they are part of the platform itself. Others are optional, and an institution turns them on for its own use, sometimes with its own account and credentials. The table says which is which.

Orravo's own application and database run in Ireland. The EcclesiaOne application runs on Vercel in its Dublin region, and the primary database is a managed Postgres instance in AWS eu-west-1. For the remaining providers, the processing location is the one set out in that provider's current data-processing terms; the exceptions we know and state below are the AI provider used for register recognition, which processes in the United States. If you need the detail of a particular transfer, ask us at [email protected].

Payments

Provider	Service	Data involved	Location	Used by
Paystack	Payment processing for donations, school fees, and subscription billing	Payment and card data (tokenized by the provider), payer name and contact, transaction details, and the bank code and account number of a parish settlement account	Per the provider's terms	The platform, for all institutions that take payments
Stripe	Alternative payment processing for donations, in currencies Paystack does not serve	Payment and card data (tokenized by the provider), payer name and contact, transaction details	Per the provider's terms	Optional, switched on by an institution using its own Stripe credentials

Card details are collected and stored by the payment provider. Orravo does not store full card numbers.

Messaging and email

Provider	Service	Data involved	Location	Used by
Termii	SMS delivery	Recipient phone number, message content, delivery status	Nigeria	The platform default for SMS
Twilio	SMS delivery	Recipient phone number, message content, delivery status	Per the provider's terms	Optional, using the institution's own Twilio account
Africa's Talking	SMS delivery	Recipient phone number, message content, delivery status	Per the provider's terms	Optional, using the institution's own account
Resend	Transactional and broadcast email delivery	Recipient email address, message content, delivery status	Per the provider's terms	The platform default for email
Amazon SES	Bulk and broadcast email delivery	Recipient email address, message content, delivery status	Per the provider's terms	Optional, where the operator configures it for bulk sending
An SMTP relay of the institution's choosing	Email delivery from an institution's own address	Recipient email address, message content	Set by the institution	Optional, configured by a diocese or parish
Meta Platforms (WhatsApp Business Platform)	WhatsApp message delivery	Recipient phone number, message content, delivery status	Per the provider's terms	Optional, where WhatsApp messaging is configured
Expo (Expo Application Services)	Push notification delivery to the mobile app	Device push token, notification title and body	Per the provider's terms	The platform, where the mobile app is used
Browser push services (Google, Mozilla, Apple, depending on the visitor's browser)	Push notification delivery to a web browser	Browser push endpoint, notification title and body	Set by the browser vendor	The platform, where a visitor has enabled browser notifications

We do not use Firebase Cloud Messaging directly. Mobile push goes through Expo, and browser push goes to whichever push service the visitor's own browser uses.

Hosting, storage, and media

Provider	Service	Data involved	Location	Used by
Vercel	Application hosting; every request to the platform is served by it	All categories, in transit and in function memory, plus request logs and IP addresses	Application functions run in Vercel's Dublin (Ireland) region	The platform
Supabase	Managed Postgres, the primary database	All categories	AWS eu-west-1 (Ireland)	The platform
Cloudflare (R2 storage, and Stream where a video is hosted there)	File, image, and video storage and delivery	Uploaded images and media, including photographs of members and of children, documents, and recordings of services	Per the provider's terms	The platform
Amazon S3	Storage of register page images awaiting recognition	Images of sacramental register pages	Per the operator's configured AWS region	Optional, where the operator configures object storage for the register-scanning feature
Cloudflare (Turnstile)	Bot and spam protection on public forms and sign-up	Visitor IP address and browser signals, on every public form submission	Per the provider's terms	The platform
Google (Fonts)	Delivery of the typefaces used across the platform	Visitor IP address and browser user agent, on page load	Per the provider's terms	The platform
Sentry	Error and crash reporting	Error messages and stack traces, request URL, browser and device information, IP address	Per the provider's terms	Optional, only when the operator configures a reporting endpoint

Where an institution adds a map or a video embed to its published site, the visitor's IP address and browser information also reach the provider of that embed (Google Maps or YouTube) when the page loads.

Sentry is off unless a reporting endpoint is configured. The platform's own error records are stored in the primary database described above, and are covered by the Data Retention and Deletion Schedule.

Artificial intelligence

Provider	Service	Data involved	Location	Used by
Anthropic	Reading sacramental register pages, where enabled by a diocese	Images of register pages and the text extracted from them, including names, dates of birth and baptism, and the names of parents, sponsors, and the minister	United States	Optional, per diocese
Google (Cloud Vision)	Alternative text recognition engine for register pages	Images of register pages and the text extracted from them	Per the provider's terms	Optional, where the operator selects this engine

The register-scanning feature is off by default and is enabled per diocese only after an attestation. Where no recognition provider is configured, the platform does not send register images anywhere. See the AI and Automated Processing Notice.

We do not use an AI provider for translation.

Analytics

Orravo runs no analytics tooling of its own. The platform does not load Google Analytics, Plausible, PostHog, Segment, Hotjar, or any comparable product, and does not build behavioural profiles of visitors.

Institutions that publish websites through EcclesiaOne have a field for adding custom markup to their pages, but that field strips script tags, embedded frames, and event handlers before anything is stored or shown. An analytics snippet placed there does not run. Whatever the field does hold is rendered only where the visitor has accepted non-essential cookies, and it remains the institution's responsibility as controller of its own site.

Changes

When we add, remove, or replace a sub-processor, we update this list and notify tenant administrators as described in the Data Processing Agreement.