FOR SERVICE BUSINESSESBack to Rella

Rella service providers

Updated November 10, 2026. Rella is operated by Rellatech Inc. in Canada.

These are the companies that handle information for us to run Rella, what each one sees, where and under which contract. Rella's server and database are in Montréal, Canada. Read this with our privacy notice and terms of service.

Used for every business

Amazon Web Services

Hosts Rella's server and database, and sends and receives Rella's email through Amazon Simple Email Service (Amazon SES).

What it sees
Everything stored in Rella: accounts, business records, client records, notes, forms, files and backups. The emails Rella sends, and the email replies clients send to Rella addresses, which arrive through Amazon SES and are passed to Rella in the same region.
Where
Canada (Central) region, Montréal (ca-central-1).
Contract
AWS Customer Agreement with the AWS data processing addendum, and the AWS Business Associate Addendum.

Cloudflare

Runs the domain name system (DNS) for rella.ca, hosts the public website at rella.ca, and forwards email sent to rella.ca addresses such as hello@rella.ca.

What it sees
Visits to the rella.ca website (address, browser details and the page asked for) and emails sent to rella.ca addresses. app.rella.ca is DNS only: Cloudflare answers the address lookup, but the app's traffic goes straight to our server at Amazon Web Services and does not pass through Cloudflare.
Where
Cloudflare's global network.
Contract
Cloudflare Self-Serve Subscription Agreement with its data processing addendum.

Stripe

Takes card payments: Rella plans and phone credit paid by businesses, and invoices a business's clients pay by card.

What it sees
The payer's name, email and card details, the amount and the invoice description. For a business in health privacy mode, the description is only "Invoice" and its number, never the service. Card details stay with Stripe and are never stored in Rella.
Where
United States and Canada.
Contract
Stripe Services Agreement with the Stripe data processing agreement.

Twilio

Texts and calls for businesses that get a Rella phone number, and the registration US carriers require for business texting.

What it sees
Phone numbers, the words of each text, call audio, and voicemails and recorded calls when the business uses them, which Twilio keeps for Rella. For registration, the business's name, address, business number and contact person.
Where
United States.
Contract
Twilio Terms of Service with the Twilio data protection addendum. We have not signed Twilio's HIPAA addendum yet, so health privacy mode is not open to US businesses yet.

Used when you choose a feature

These only receive information when a business connects them or a person uses that feature.

Meta (optional business connections)

Connects a business's Facebook lead forms and, where the private beta is enabled, its WhatsApp Business conversations.

What it sees
The Facebook Pages and forms the owner authorizes. For WhatsApp: authorized business accounts and phone numbers, recipient numbers, message content, templates and delivery events. Rella stores connected data on AWS; WhatsApp content is not sent to the help assistant.
Where
Meta's global infrastructure; processing may occur outside Canada.
Contract
Meta Platform Terms and applicable WhatsApp Business Platform and Cloud terms.

Google

Sign in with Google, Google Calendar when a coach connects it, and Google Ads spending in Reports where it is offered. Each browser in a Rella video call also asks Google's public STUN server for its own network address. When a business picks a font for its pages, visitors' browsers load it from Google Fonts.

What it sees
For sign-in: name, email and Google account ID. For Calendar: the times we ask about, and Rella appointment times titled "Rella appointment" with no client names or details. For Google Ads: the business's ad accounts and spending, which we only read. For video calls and fonts: the browser's network address. Never notes, form answers or client records.
Where
United States and Google's global network.
Contract
Google APIs Terms of Service and the Google API Services User Data Policy, including its Limited Use rules.

Anthropic

Writes answers in Rella's help assistant.

What it sees
Rella's own help guides and what the person types in the assistant, with email addresses and phone numbers removed first. Never business or client records. The assistant is off for businesses in health privacy mode.
Where
United States.
Contract
Anthropic Commercial Terms of Service with its data processing addendum. Anthropic does not train its models on what we send.

Intuit QuickBooks Online

Keeps a business's books in step with Rella, only when an owner or administrator connects QuickBooks.

What it sees
Client names and emails as QuickBooks customers, invoices and payments recorded after connecting, and the business's QuickBooks transactions that Rella reads for Money. For a business in health privacy mode, invoice lines say only "Invoice" and its number.
Where
United States.
Contract
Intuit Developer Terms of Service, and the business's own agreement with Intuit.

Rella also has Microsoft calendar connections and PayPal payments built in. Neither is switched on yet. We will add them to this page before they are.

Our own website and sign-up

These help us measure our own marketing. They never see business or client records.

Meta

The Meta Pixel on Rella's sign-up pages measures our own advertising.

What it sees
The page address, browser and device details, network address, Meta cookies and whether a sign-up finished. Not your name, email, phone number or business details. It is not used inside the app or on pages for clients, bookings, forms or payments.
Where
United States.
Contract
Meta Business Tools Terms.

Supabase

Stores visit reports for the rella.ca website, only after a visitor allows it.

What it sees
The page path, a random session ID, the referring site or campaign, country and region, and device and browser type. It does not keep network addresses.
Where
Supabase's hosted service.
Contract
Supabase Terms of Service with its data processing addendum.

Places you choose to send to

Some features send information to a service the business picks and has its own agreement with. These are not our providers: a Slack channel or webhook added in Connections, a Zapier key, the business's own Google tag or Google Analytics on its pages, videos it embeds from YouTube, Vimeo or Loom, and calendar links from services like iCloud or Outlook.com. For a business in health privacy mode, Slack and webhooks receive only record IDs, never names or contact details.

Changes and breaches

We update this page when we add or change a provider. We tell business owners at least 30 days before adding a provider that would handle their health information, so they can decide whether to continue.

If we confirm that information we or one of these providers hold for a business was lost, stolen, or used or disclosed without authorization, we tell that business within 24 hours of confirming it.