Privacy Policy

1. Who we are

Sebairo is a “Digital Life OS” app operated from the United Kingdom (“Sebairo”, “we”, “us”). For the purposes of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018, Sebairo is the data controller for the personal data described in this policy.

Contact for privacy matters: support@sebairo.com, with [Data Rights] in the subject line if you are exercising a right under section 11.

Where you use a workspace to run a company, Sebairo is the processor and you are the controller for the customer, employee and applicant records you load into it. Section 8 of the Terms sets out what that means for your obligations.

2. What we collect

Account data

The phone number or email address you sign up with, your display name, profile details, a photo if you add one, your chosen language and your settings. Passwords are stored only as a hash by the authentication service; nobody at Sebairo can read yours.

Content you create

Posts, comments, messages, photos, videos, live streams and their replays, Marketplace listings, job posts and applications, notes, memories, workspace projects and records, and business pages.

Calls

Voice and video calls are carried in real time and are not recorded, unless the host of a live stream explicitly creates a replay, in which case that replay is stored as content.

Credits and purchase history

Your credits balance, your purchase history, your subscription status and your ad-spend records, each with a reference. A credit purchase is paid inside Google Play, which processes the payment; Sebairo receives the purchase token and the product bought, and never your card number. If a card rail is active and you choose to save a card, the card is held by Stripe and Sebairo holds only a reference to it.

Location

Only where you give it, and only on these surfaces: a city and country on your profile, and the private coordinates you can add when you complete sign-up or in your location settings; your presence on the Memories map, which is off until you switch it on; a place you share in a chat, a note or a memory; the places attached to your memories; and the location recorded with an attendance punch, when a workspace you work in requires it — that punch is visible to that workspace's managers. Each of these is optional except the attendance punch where the workspace requires it.

Technical data

A push token so a notification reaches your device and not someone else's, and the ordinary server records any hosted service keeps in order to stay up, fix faults and detect abuse.

Reports and moderation records

Reports you submit about content or accounts, and the moderation actions taken, kept with an audit trail that records who acted and why.

Diagnostics

When something goes wrong, the app records what was attempted and what happened: which screen, which operation, the class of the error and its machine code, how long it took, and — for a crash — the file and line numbers inside Sebairo's own code. It does not record the text of the error message, anything you were writing, or what you typed into a search box. A search is recorded only as a shape: how many words, roughly how long, which script, and how many results came back. We keep these records for fourteen days and then delete them; what survives is a daily count.

3. What we deliberately do not collect

Some of these took deliberate engineering. They are the ones worth holding us to.

Your address book is never uploaded

Finding which of your contacts already use Sebairo works the way it does in WhatsApp: your phone sends the numbers, the server matches them in memory and answers, and nothing from your address book is written down. No copy of your contacts exists on our side.

Your card number

There is no field for it in the app and no record of it on Sebairo's side. A credit purchase is paid inside Google Play; if a card rail is active, a card you choose to save is entered on Stripe's own page and stays with Stripe.

Your location, unless you give it

Location is collected only on the surfaces listed in section 2 — your profile, a place you share, your memories, and an attendance punch a workspace requires — and each of those is yours to use or not. Your presence on the Memories map starts switched off, and “off” is not “we hide the pin”: while it is off, your position is not released to anyone but you.

Your face, and what the camera sees during effects and scanning

Face detection and background segmentation for LIVE effects, and barcode scanning, run as on-device detectors bundled in the app. Each camera frame is processed on your phone and discarded as the next one arrives: no image, frame or face data is stored, and none is sent to Sebairo or to anyone else. The detector library reports only usage metrics to Google, never content — see the Sub-processors page.

What you typed into a search box

The diagnostics described in section 2 record that a search returned nothing; they never record the words you searched for. There is no field in that store a sentence could be written into — every field is constrained to a short machine token, so an error in our own code cannot put your words there. The record is refused instead of written.

An analytics company watching how you use the app

There is no analytics or crash-reporting company in Sebairo — no third-party SDK of any kind is built into the app. The diagnostics in section 2 are written to Sebairo's own database and read by nobody else; section 7 lists every party that receives anything, and no analytics provider appears on it because none exists. There is also no advertising identifier and no cross-app tracking.

4. Why we use your data, and our lawful bases

Performance of a contract

Providing the app you asked for: accounts, messaging, calls, the feed, the Marketplace, your credits, plans and advertising.

Legitimate interests

Keeping the platform safe and working: content moderation, fraud prevention, abuse detection, service diagnostics and security. The diagnostics are the ones described in section 2, and the balance rests on what they deliberately exclude: no message, no draft and no search text ever reaches them, the raw records are deleted after fourteen days, and what outlives that carries no link to any account. These interests are balanced against your rights, and you can object under section 11.

Consent

Where required — for example certain notifications, your presence on the Memories map, and a location you choose to share. You may withdraw consent at any time, and withdrawal takes effect from that point forward.

Legal obligation

Record-keeping and disclosures required by law, including financial and tax records connected to credit purchases and plans.

5. Who can see what

Visibility is settled by Sebairo's servers, not by what the app chooses to show you: when you are not allowed to see something, it is not sent to your device in the first place.

• Every post carries an audience — public, followers, contacts or private — and the rule is enforced in the read policy and in the ranked feed alike.
• A conversation is readable by the people in it. Direct chats, groups, business inboxes and client portals are separate surfaces on purpose.
• Blocking applies in both directions.
• Group, chat and contract links never render as a public web page; a stranger with the URL sees nothing and a search engine cannot index it.
• Business pages, Marketplace listings and job posts are public by design — that is what they are for.

6. Encryption, stated plainly

Everything between your device and Sebairo travels over TLS, and your data and files are encrypted at rest. That is the ordinary expected standard and Sebairo meets it.

Sebairo is not end-to-end encrypted, and we will not imply otherwise. Messages are stored in a form the service can read. In practice that means moderation can act on something you report, and that a lawful order could compel disclosure. If you need end-to-end encryption for a particular conversation, use a tool built for that and do not assume Sebairo is one.

7. Sharing and sub-processors

We do not sell your personal data. We share it with service providers who process it on our behalf under contractual safeguards. The full list, with what each one actually receives and why, is on its own page: Sub-processors.

• Supabase — authentication, data storage and file storage.
• Google Play (Google LLC) — credit purchases: Google receives what Play Billing needs to take the payment, and Sebairo receives the purchase token and the product bought.
• Stripe — saved cards only, when a card rail is active; Stripe takes no payment from the app.
• LiveKit — real-time voice and video for calls and live streams.
• Google / Firebase — push notification delivery (Firebase Cloud Messaging).
• Twilio — one-time sign-in codes sent by SMS.
• Vercel — hosting for the public websites sebairo.com and help.sebairo.com.
• OpenStreetMap Foundation — the map tiles behind the Memories map, requested by your device directly: it receives your IP address, your user agent and the area of the map you view, and no account data.
• Your phone's speech service — dictation: recognised on the device on iOS, and on Android 12 and later with an on-device model; on older Android, or without such a model, the phone's built-in speech service (Google's on most Android phones) receives the audio to transcribe it.
• Zoho Mail — the support mailbox: when you write to support, your name, your email address and the text of your message are delivered to support@sebairo.com, which is hosted at Zoho, and a reply from support goes back through the same mailbox.
• Google ML Kit — on-device detectors bundled in the app for barcode scanning and for the face-contour and background-segmentation effects in LIVE: no image, frame or face leaves your phone and none is stored; the library reports only usage metrics to Google (device model and operating system, the app's package name and version, a per-install identifier, timing and error codes, and the image format and size — never the image itself).

We may also disclose data where required by law, or to protect the rights, safety and security of Sebairo, our users or others. What that means in practice — what process is required, what we will refuse, and when you are told — is set out in the Law Enforcement Guidelines.

8. Where your data is, and international transfers

Your data and files are stored in the London region, in the United Kingdom.

Some sub-processors process data outside the United Kingdom — a push notification or a real-time call route may be served from another region. Where personal data is transferred internationally, we rely on appropriate safeguards such as UK adequacy regulations or the applicable standard contractual clauses together with the UK International Data Transfer Addendum.

9. Retention

We keep personal data for as long as your account is active and as long as needed to provide the service. When you delete your account, the following are erased: the account itself, your profile, the content you created, any saved card and the customer record that held it at Stripe, your conversations with support, the personal-finance books you kept in the app — your own ledger, its entries and invoices — and the reports you filed about other people.

Some things outlive the account, and the reasons are specific rather than general:

• Activity and moderation logs are kept with the link to you removed, so they no longer identify you.
• A few audit lines keep an opaque identifier in place of your account — moderation actions, bans, admin actions, job posts, and a staff reply on someone else's support ticket — because the record of who did what has to survive the person leaving.
• Reports made against you are kept, because they belong to the record of the reported content rather than to your account.
• Financial and tax records connected to credit purchases and plans, moderation records needed to enforce a suspension or answer a legal request, and content other people received and kept.
• Diagnostic records are deleted after fourteen days. What is kept beyond that is a daily count that carries no link to any account.

Each is kept only as long as its purpose requires.

10. Security

We use technical and organisational measures appropriate to the risk: encryption in transit and at rest, access controls that limit each account to its own data, restricted and recorded staff access, and an audit log for staff moderation actions.

Sebairo has not been through a third-party security audit and runs no paid bug-bounty programme. No system is perfectly secure and we cannot guarantee absolute security. Vulnerability reports are welcome at support@sebairo.com with SECURITY in the subject line.

11. Your rights

Under UK GDPR you have the right to:

• access the personal data we hold about you;
• have inaccurate data rectified;
• have your data erased — account deletion is permanent and available self-service from Settings in the app;
• receive a portable copy of data you provided;
• object to processing based on legitimate interests;
• restrict processing in certain circumstances;
• withdraw consent where processing is based on consent.

To exercise any of these, write to support@sebairo.com with [Data Rights] in the subject. You also have the right to complain to the UK Information Commissioner's Office at ico.org.uk.

Sebairo does not make decisions about you by automated means that produce legal effects or similarly significant effects on you. Ranking a feed is not that.

12. Children

Sebairo is for adults: it is not intended for anyone under 18, and you must be at least 18 years old to create an account. If we learn that an account belongs to someone under 18, we will delete it.

13. Changes to this policy

We may update this policy as the service evolves. If we make material changes, we will notify you through the app or by other reasonable means before the changes take effect, and every change is logged with its date on the changes page.