Sub-processors

1. What a sub-processor is

A sub-processor is a company Sebairo engages to process personal data on its behalf, under a contract, for a purpose Sebairo sets. Sebairo remains the controller and remains answerable for what they do with it.

A service that your own device contacts directly to do a job — the server that draws the map, the speech service built into your phone — is a slightly different relationship: Sebairo does not hold your data there, and each is marked as such below.

2. The list

Supabase — data storage, authentication and file storage

The core of the platform. It holds your account record, every item of content you create and the files you upload — it is where your content actually lives. Signing in happens here too; passwords are never stored in a readable form and nobody at Sebairo can read one. Your data and files are stored in the London region, in the United Kingdom.

Google Play (Google LLC) — credit purchases

The only place a credit purchase is paid. Google receives what Play Billing needs to take the payment — your Google account, the payment method you keep with Google, the product and its price — under Google's own terms and privacy policy; Google is the merchant for that charge and handles its refunds. Sebairo receives the purchase token and the product identifier, which is enough to confirm the purchase and add the credits, and nothing about your payment method.

Stripe — saved cards only, when a card rail is active

Holds a card you choose to save, entered on Stripe's own hosted page; Sebairo receives back a reference to the saved card and never sees or stores the number. Stripe takes no payment from the app: credits are bought through Google Play, and plans and advertising are paid from credits. A Marketplace sale is arranged between two people and never passes through Stripe or through Sebairo; see Commerce Terms.

LiveKit — real-time voice and video, and live-stream replay recording

Carries the audio and video of calls and live streams while they are happening, along with the identifiers needed to route them to the right people. Calls are never recorded. A live stream can be recorded into a replay, and that replay is held by Sebairo rather than by LiveKit. Otherwise LiveKit receives the media stream in transit only, and is not a content archive.

Firebase Cloud Messaging (Google) — push notifications

Receives a device push token and the notification payload, so an alert reaches your device and not someone else's. It gets a token and a short message, not your content library and not your message history.

Twilio — one-time sign-in codes by SMS

Sending a one-time code to your phone requires a delivery provider. Twilio receives the destination phone number and the code being sent, and nothing else. Account emails — confirmation and password reset — are sent by the delivery provider configured inside the authentication platform, which receives the destination email address and the message only.

Vercel — hosting for the public websites

sebairo.com and help.sebairo.com are static public sites hosted by Vercel. It receives the ordinary request records any web server keeps — IP address, user agent, the URL requested. The marketing and legal pages create no session and read only publicly visible data, so no personal content passes through them.

OpenStreetMap Foundation — map tiles for Memories (contacted by your device)

The map in Memories is drawn from tiles served by the OpenStreetMap Foundation, which your device requests directly. It receives your IP address, your user agent and the area of the map you are looking at — no account data, and nothing about the memory itself. Sebairo sends it nothing.

Platform speech recognition — dictation (runs on your device where it can)

Dictation is recognised on your device on iOS, and on Android 12 and later where an on-device model is installed; the audio never leaves the phone. On older Android, or where no on-device model exists, the phone's built-in speech service — Google's, on most Android phones — receives the audio to transcribe it, under Google's terms. Sebairo receives only the text you dictated, as part of whatever you then send or save.

Zoho Mail — the support mailbox

support@sebairo.com is a mailbox hosted by Zoho. When you write to support — from the contact form on the help site or from your own email — your name, your email address and the text of your message are delivered to that mailbox, and a reply from support is sent back through it. Zoho receives nothing else: no account data, no content from the app and nothing from your conversations. That mail may be processed outside the United Kingdom; section 4 applies.

Google ML Kit — on-device detectors for barcode scanning and LIVE effects (runs on your device)

Three detectors from Google's ML Kit library are bundled inside the Android app: barcode scanning, face contours and selfie segmentation — the last two behind the LIVE effects that follow a face or separate a person from the background. All three run entirely on your phone: each camera frame is processed there and discarded, and no image, frame or face ever leaves the device or is stored by anyone. The library reports usage metrics to Google — the device model and operating system version, the app's package name and version, a per-install identifier, latency and error codes, and the format and size of the images processed — and never the image itself or anything detected in it. Sebairo receives only the result you then act on: a scanned code, or the effect drawn on your stream.

3. What they are not permitted to do

• No sub-processor is permitted to use Sebairo data for its own advertising, or to sell it.
• None is given access beyond what its function requires.
• None is engaged to build a profile of you across services.

4. Where the data is

Your data and files are stored in the London region, in the United Kingdom. Other sub-processors operate globally distributed infrastructure and may process data outside the UK — a push notification or a call route may be served from another region.

Where personal data is transferred internationally, Sebairo relies on appropriate safeguards: UK adequacy regulations where they apply, or the applicable standard contractual clauses together with the UK International Data Transfer Addendum. See section 8 of the Privacy Policy.

5. Adding or changing a sub-processor

This page is updated when a sub-processor is added, removed or replaced, and the change is logged with its date on the changes page. Where a new sub-processor would receive a materially different category of data than the list above describes, that is announced rather than only recorded.

If you believe this list is incomplete — that Sebairo data reaches a service not named here — say so at support@sebairo.com and the page is corrected. A sub-processor list that is quietly out of date is worse than none, because it is trusted.