On 8 August, help.sebairo.com opened as its own site with 12 categories and 30 bilingual articles. On 10 August it grew into the full thing: 124 articles across 24 categories, all cross-linked, plus 11 legal documents — from 158 built pages to 342, every one written in English and Arabic.
Built for the app to point at
Article addresses are permanent from the day they publish — a deep-link contract, not a filing habit. That is what lets the app's '?' buttons open the exact article for the screen you are on (the Wallet, the Marketplace and Live carry them first), and Settings carries Help & Support. Support itself is real tickets: chat-style threads inside the app, and a staff reply also lands in your Activity feed. The language you choose follows you between Sebairo's sites.
One honest engineering note from the launch: the articles live as code and ship through version control — reviewed, versioned and auto-deploying. A content-management system was deliberately not built yet; the change log records the deferral with its reason, the way it records every other one.
The encryption answer, unsoftened
The Help Centre's most pointed article is titled 'Is Sebairo end-to-end encrypted?' and it opens like this: 'No. Sebairo is not end-to-end encrypted, and we would rather tell you that here than let you assume otherwise.' What is encrypted is the ordinary expected standard — the connection between your phone and the service, and the database and file storage at rest — and the article says exactly that, no more.
It then states the consequences instead of hiding them: moderation can actually read and judge a message you report — which is only possible because the service can read it — and a lawful order could compel disclosure of content. And it closes with advice few products print about themselves: Sebairo 'is not the right tool for something that would genuinely harm you if the service could read it.'
The same page lists what is missing, plainly: no independent security audit yet, no paid bug bounty, no app-based two-step verification yet. Not because those gaps are fine — because you should not have to discover them yourself.
Legal that describes mechanisms
The Legal Centre holds 11 documents — UK GDPR framing, the law of England and Wales, Arabic summaries throughout, and a solicitor review that is still pending and is stated as pending rather than hidden. The commerce terms state plainly how money moves today: payments land in Sebairo's own Stripe account, and seller payout is a manual step.
Even the uncomfortable pages follow the rule. The marketing site's accessibility page was measured against the source code before it was written: the app currently ships without screen-reader labels, and the page tells TalkBack users not to install expecting it to work. Publishing that sentence is the fastest route to making it false.
'Every link works' is a test, not a slogan
The claim that every link on Sebairo's sites resolves is enforced by a build-time audit that reads what the sites actually emitted and checks every internal link — 12,845 of them at last count, 0 dead — and fails the build if a regression appears.
The pattern across all 342 pages is the same: answer as the system actually behaves, record deferrals with their reasons, and never write the reassuring sentence the record cannot back. If a page here ever disagrees with the product, the product is the truth — and the page gets fixed, in both languages.