For the reviewer
When Siteleon is having a bad day, your customers should not be able to tell.
Your customers reach a version of your site that was finished before they arrived, so nothing they open is waiting on us. When the editor is unavailable, the assistant is offline or the analytics engine is hours behind, your pages still load and your emergency number is still on them — which is what matters at six on a Sunday evening when a hotel's cooling has failed. Enquiry submissions are accepted at the edge and queued, then delivered once the control plane returns, so a form filled in during an incident reaches you late rather than never. Degradation is deliberately partial: a connector that cannot reach an advertising account marks those figures stale rather than showing you a wrong number. We report status per component and describe incidents in plain language, and we do not publish an uptime percentage, because a number we have not had time to earn is not evidence.
Publishing is a release, and releases roll back
Every publish keeps its version, its changes, who or what made them, the previous release, the rollback target and any redirect changes. Restoring last week's site is one action, not a support ticket. Redirects and canonical URLs travel with the release, so a rollback does not quietly break the links other people have already published.
Failures are scoped to the thing that failed
A degraded advertising connector affects advertising figures, and a slow analytics pipeline affects how recent your numbers are. Neither touches what a visitor sees. The one thing your live site needs from us is publishing a change — and while that is degraded, the last published version keeps serving.
We tell you what is affected
Status is reported per component — editor, assistant, publishing, analytics, connectors, and site serving — with what is affected, what is not, and what we are doing. Incidents that touched your data get a direct notification rather than a status page you had to think to check. Maintenance with any customer-visible effect is announced before it happens.
Trust Centre
The rest of this area.
For the reviewer, not the owner: how AI uses your data, where it runs, what stays up, and how to report a flaw.
AI & Data Use
What the assistant can read, whose permissions it borrows, which actions need approval, and what it never learns from.
Infrastructure
Where your pages are built, stored and served, how one workspace is kept apart from another, and what you choose.
Responsible Disclosure
How to report a vulnerability, what we do with it, and what you can expect from us while we fix it.
Your business online. Built to adapt.
Start with the site you already have, or create something new. Siteleon helps you build it, understand it and keep improving it as the business changes.
No technical setup · Keep your existing site if you want to · [email protected]