Sub-processors
Sebairo is one app, but it does not pretend to run on air. Every third party below touches some Sebairo data on its way to doing a job, and each entry says what it actually receives rather than describing a category.
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 company that receives data because you chose to send it there — a provider whose API key you supplied yourself — is a slightly different relationship, and it is marked as such below.
2. The list
- Supabase — database, authentication, file storage, server functions
- The core of the platform. It holds your account record, every row of content you create, uploaded files, and it runs the server-side functions the app calls. It is where your content actually lives. Sign-in, password hashing and session issuing happen here; passwords are stored only as a hash and nobody at Sebairo can read one. The primary database and storage are hosted in the London region, in the United Kingdom.
- Stripe — card payments, checkout and subscriptions
- Receives what a payment needs: the card details you type on Stripe's own hosted page, the amount, the currency and an order or checkout reference. Sebairo receives back only the outcome and that reference — it never sees or stores a card number. Stripe is a PCI-certified payment processor, which is precisely why the card step happens there and not here. Note that Marketplace payments are currently collected into Sebairo's own Stripe account; 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 room and participant identifiers needed to route them. Calls are never recorded. A live stream can be recorded into a replay: LiveKit's server-side recorder composites the room and uploads the finished file into Sebairo's own storage, so the 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.
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.
Sebairo does not sell personal data, and does not engage any advertising network, data broker or cross-site tracking service as a sub-processor. There is no analytics vendor on the public websites.
4. Where the data is
The primary database and file storage are hosted 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 9 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.
ملخص بالعربية
المعالِج الفرعي شركة يستعين بها سيبايرو لمعالجة بيانات نيابةً عنه بعقد ولغرض يحدده سيبايرو، ويبقى سيبايرو هو المتحكم والمسؤول. والقائمة: Supabase لقاعدة البيانات والمصادقة وتخزين الملفات والدوال الخادمية — وفيها يعيش محتواك، والاستضافة الأساسية في منطقة لندن بالمملكة المتحدة؛ وStripe للمدفوعات وتستلم بيانات بطاقتك في صفحتها هي بينما لا يستلم سيبايرو إلا النتيجة ومرجعًا؛ وLiveKit لنقل صوت وفيديو المكالمات والبث أثناء حدوثها، والمكالمات لا تُسجَّل أبدًا، أما البث المباشر فقد يُسجَّل في إعادة يرفعها مسجِّل LiveKit إلى تخزين سيبايرو نفسه فتبقى الإعادة لدى سيبايرو؛ وFirebase Cloud Messaging لإيصال الإشعارات وتستلم رمز الجهاز ونص الإشعار فقط؛ وTwilio لإرسال رموز الدخول عبر الرسائل القصيرة ويستلم رقم الوجهة والرمز فقط، بينما تُرسَل رسائل الحساب عبر مزوّد الإرسال المهيّأ داخل منصة المصادقة؛ وVercel لاستضافة الموقعين العامين ويستلم سجلات الطلبات المعتادة. ولا يُسمح لأي منهم باستخدام البيانات لإعلاناته أو بيعها أو بناء ملف عنك، ولا نتعامل مع أي شبكة إعلانات أو وسيط بيانات أو خدمة تتبّع، ولا يوجد مزوّد تحليلات على المواقع العامة. وأي نقل دولي يخضع لضمانات مناسبة. وتُحدَّث هذه الصفحة عند أي إضافة أو تغيير ويُسجَّل ذلك بتاريخه. هذا الملخص للتوضيح فقط، والنص الإنجليزي هو المعتمد.