Draft — pending legal review
This page has not been reviewed by counsel and is not yet in force. Text in [[double brackets]] is a placeholder for a decision the business still has to make.
Subprocessors
Last updated: [[LAST UPDATED DATE]]
A subprocessor is a third party that processes personal data, about our customers’ end users or about developers, on Livqeno’s behalf. This list comes from the services our code and deployment actually call.
1.Infrastructure subprocessors
These providers host and operate the Services, and process customer personal data on our behalf.
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Supabase, Inc. | Managed Postgres database, the system of record | Developer accounts, projects, chat messages, identities, telemetry, audit logs | [[SUPABASE PROJECT REGION]] (runs on AWS) |
| [[INFRASTRUCTURE PROVIDER]] | Servers running the API, signaling, media server (SFU), TURN relay, Redis, live-stream egress and ingest | Audio and video in transit, chat in transit, short-lived state (presence, message fan-out, token revocations), application logs including IP addresses and identities | [[DATA CENTRE LOCATION]] |
| Vercel Inc. | Hosting for the dashboard, documentation and this website | The dashboard session cookie, developer data passing through the dashboard’s server routes, request logs | Global edge network; [[FUNCTION REGION]] |
| Resend | Transactional email to developers: verification, password reset, notifications | Developer email address and name, email content. Never end users | Appears to be Tokyo, Japan (ap-northeast-1) [[VERIFY]] |
| [[OBJECT STORAGE PROVIDER]] | Chat attachments; live-stream HLS segments and recordings | Files end users upload; broadcast video | [[REGION]] |
| Cloudflare, Inc. | Authoritative DNS. [[CONFIRM: if Cloudflare proxies api. and ingest., add “TLS termination of API and ingest traffic”]] | DNS queries; if proxied, API and WHIP ingest HTTP traffic | Global |
2.Destinations you turn on
These receive data only when a customer configures the feature. They act on the customer’s instructions and are the customer’s own recipients, not Livqeno subprocessors. They are listed so the data flow is clear.
| Recipient | Purpose | Data | Turned on when |
|---|---|---|---|
| Apple Inc. (APNs) | iOS push notifications for chat | Device token, notification payload | You upload APNs credentials |
| Google LLC (Firebase Cloud Messaging) | Android and web push notifications for chat | Device token, notification payload | You upload FCM credentials |
| Restream destinations (YouTube, Twitch or any RTMP URL) | Rebroadcasting a live stream | The stream’s audio and video | You add a restream destination with your own stream key |
| Your webhook and moderation-hook endpoints | Event delivery; checking messages before they are sent | Event payloads; message content for the moderation hook | You configure the endpoint |
3.Sign-in providers
Used only if a developer chooses to sign in to the dashboard with them.
| Provider | Purpose | Data Livqeno receives |
|---|---|---|
| GitHub, Inc. | OAuth sign-in to the dashboard | Provider account ID, email, name |
| Google LLC | OAuth sign-in to the dashboard | Provider account ID, email, name |
4.Not subprocessors
- MaxMind GeoLite2. A database file we read on our own servers to pick a nearby region. No data is sent to MaxMind.
- GitHub (source code and CI). Holds our code and build logs, not customer data.
- Payment providers. None are integrated yet. We will add one here, with notice, before billing starts.
5.Changes to this list
We will give customers at least [[30]] days’ notice before a new or replacement subprocessor starts processing their data. Customers may object on reasonable data protection grounds during that period, as set out in the DPA.
To be notified of changes: [[SUBSCRIPTION MECHANISM, e.g. email list or RSS feed]].
Status of each provider’s data processing agreement: [[DPA ON FILE — confirm for every vendor]].