Legal and trust
No automated status page yet, so here is what actually happens.
A status page that nobody updates is worse than none. Until we have real monitoring published, this is how we handle and communicate problems.
How problems are communicated
- 1
You tell us, or we notice
Report it through the contact page with the screen and the time.
- 2
We confirm scope
Whether it affects one account, one feature or everyone.
- 3
We tell named contacts directly
By the channel we have agreed with you, not by a page you have to check.
- 4
We explain the cause afterwards
Plainly, including when the cause was our mistake.
What keeps working during an outage
- The installed phone app keeps accepting reports and checklist completions while offline.
- Queued work syncs when the connection returns, with retry and a clear record of anything that failed.
- Cached information from the last successful load stays readable, clearly marked as not live.
What we will not claim on this page
- We publish no uptime percentage, no response-time commitment and no maintenance-window schedule, because none is agreed.
- A monitored public status page is on the list of things being built, without a date.
How your data is handled
How access and records are handled
Each organisation's records are separated in the database, and people only see the branches they are assigned to. Status changes, approvals, rejections and verifications are recorded with who did them and when. We do not claim any external certification or audit at this stage; if you need a formal security review, ask us and we will tell you exactly what exists today.