Subprocessors
What this page is
To run Rellooma we rely on the third-party services listed below. Under data protection law these are subprocessors: they process data on our instructions, on behalf of the businesses that use our product.
Each entry states what that service actually receives. Where a service never sees the content of your customers’ messages, that is said explicitly, because it is usually the thing people want to know.
Supabase
- Purpose: the primary database, authentication and private file storage.
- Receives: everything the product stores — workspace and user accounts, customer records, conversations and message content, uploaded media, exports and audit logs.
- Processing region: South Korea (Seoul, ap-northeast-2).
Vercel
- Purpose: application hosting and serverless execution.
- Receives: HTTP request metadata, including IP addresses and request paths, and application logs. Message content passes through memory while a request is served but is not stored by the hosting layer.
- Processing region: functions run in the United States (Washington, D.C.); static content is served from Vercel’s global network.
Meta Platforms (WhatsApp Business, Instagram)
- Purpose: the messaging channels themselves.
- Receives: the messages sent to and from your customers, and the account identifiers Meta issues, such as phone numbers and Instagram account IDs. Meta is the origin of this data rather than only a recipient — the conversation happens on its platform, and its own terms govern it.
- Processing region: Meta’s global infrastructure.
Inngest
- Purpose: orchestration of background jobs such as webhook processing, retries, cleanup and billing tasks.
- Receives: identifiers only. Job payloads carry workspace, event and record IDs so a worker can fetch what it needs from the database; the text of a customer’s message is never placed in a job payload.
- Processing region: United States.
Resend
- Purpose: delivery of service emails — sign-in and recovery links and team invitations.
- Receives: the recipient’s email address and the content of that email. It never receives customer records or message content.
- Processing region: United States.
Cloudflare (Turnstile)
- Purpose: bot protection on the sign-up, sign-in and recovery forms.
- Receives: the visitor’s IP address, browser signals and a challenge token at the moment a form is submitted. It never receives customer records or message content.
- Processing region: global.
Paddle
- Purpose: subscription checkout, billing, tax and refunds, as our merchant of record.
- Receives: the billing contact’s name, email address, country and payment details, entered directly on Paddle’s checkout. We store only Paddle’s customer, subscription and transaction references and the subscription state.
- Processing region: Paddle’s own infrastructure (United Kingdom and United States).
AI model provider
- Purpose: generating suggested and automated replies.
- Receives: the conversation context needed to produce a reply, which includes customer message content: only recent turns and approved business knowledge, never a whole conversation history or a customer’s full record.
- Provider and region: the provider whose key the workspace supplies — Google (Gemini), OpenAI or Anthropic — under the business’s own agreement with that provider.
What is not on this list
We do not send customer records, message content, phone numbers, email addresses or attachments to any analytics or advertising service, and the app uses no third-party analytics.
Changes
This list changes when an integration is added or removed, and each change is published as a new version with a new date. Questions: privacy@rellooma.com.