Sub-processors and Connected Data Sources
Last updated 19 August 2026This is Relae's Sub-processor and Data Source page. The Data Processing Agreement incorporates it by reference as the authoritative, current list of Relae's Sub-processors and available Connected Data Sources. In the DPA's own words (clause 5):
“The Customer authorizes Relae to engage the Sub-processors listed on Relae's Sub-processor and Data Source page, maintained at relae.ai/subprocessors and incorporated into this DPA by reference. That page is the authoritative, current list; Relae keeps it accurate as Sub-processors and available Connected Data Sources change, and the snapshot in Schedule 2 below is provided for convenience as of this DPA's date and does not override the page.”
| Function | Provider | Region | Data and purpose |
|---|---|---|---|
Cloud database, auth, storage Sub-processor | Supabase | ca-central-1 (Canada) | Primary data store, authentication, file storage for the Canadian Region. |
Application hosting Sub-processor | Vercel | Compute pinned to Montreal (yul1); global edge for content delivery | Application hosting. Request compute for the Canadian Region runs in Canada; no Donor Data is stored at the edge. |
Interactive AI and document signing infrastructure Sub-processor | Amazon Web Services (Bedrock for AI; ECS Fargate, EFS and RDS for the self-hosted signing service) | Canada (ca-central-1) | Interactive AI: donor-capture assistance, coaching, thank-you drafting, and the Ask Relae assistant. Identifier redaction applied before calls; prompts are not used to train models and are not retained by the model service. Signing infrastructure: Relae's self-hosted DocuSeal runs on AWS compute and storage in Canada and holds executed agreements, being a signer's name, email, signature image and completion certificate. No Donor Data passes through the signing service. |
AI and web research (consented / entitlement-gated only) Sub-processor | Anthropic API and web-search services | United States | Used only for the opt-in donor-research feature (name and public identifying context, never the private record) and the entitlement-gated funder research (organization names only). Contractual no-training and no-retention terms apply. |
Connected event data source (optional, at the Customer's direction) Connected Data Source | Eventbrite | United States | Where a Customer connects its Eventbrite account, the Platform reads event and attendance data, which can include donor personal information, into the Customer's workspace. Read-only; nothing is written back. |
Public registry lookups Public registry | CRA / open.canada.ca | Canada (government) | Charity-registry and public-filing lookups. Relae sends only a charity business number; no donor personal information. |
How changes are notified
During our Beta phase, this page is Relae's mechanism for notifying you of Sub-processor changes. Relae keeps this register current as services are added or replaced. Once Relae reaches general availability, you will receive at least thirty (30) days' advance notice by email and in-app notification before adding or replacing a Sub-processor.
You can object to a new Sub-processor on reasonable data-protection grounds. If an objection cannot be resolved, you may terminate the affected Services and receive a pro-rata refund of unused fees. Relae imposes data-protection obligations on each Sub-processor materially equivalent to the DPA and remains responsible for their performance.
Connected Data Sources are engaged at your direction: each one operates only for a customer that chooses to connect it, and the connection surface in the product describes the data involved, the direction of the flow, and the source's region before you connect.