One owner
A waiting item belongs to a person, by name. Not to "accounts", not to a shared inbox, and not to a rota. If that person is away, it is reassigned to another named person, and the handover is recorded.

Trust
Nothing that sends, pays, changes or contacts happens without a named person's yes.
Lexi Prepares the work and shows the working.
Person The approval is explicit.
This page is the one place on the site where we would rather be dull than reassuring. Everything below is either something we can evidence, or an admission that we cannot yet.
The gate
Prepared
Lexi shows the working.
Approved
A named person says yes.
The boundary
Named people
Recorded handover
A waiting item belongs to a person, by name. Not to "accounts", not to a shared inbox, and not to a rota. If that person is away, it is reassigned to another named person, and the handover is recorded.
Your data
It is yours. We do not sell it, and we do not train shared models on it.
It is kept separate from every other client's, at the storage layer, not by convention.
Credentials for your systems are encrypted with your key. Nobody here can read them, and they never appear in a log or an error message.
You can export it, and you can leave with it. Ending an engagement does not mean losing your history.
What we do not hold
We hold no SOC 2 and no ISO certification, and we do not imply one. There is no badge on this page, because there is nothing to put on it.
We also do not claim compliance with a mandatory AI regime, because Australia does not have one. As at August 2026 there is no binding AI-specific law here. The National AI Plan of December 2025 relies on existing law, and the Voluntary AI Safety Standard was replaced on 21 October 2025 by the Department of Industry's Guidance for AI Adoption, which is voluntary.
If a certification matters to your decision, say so early and we will tell you plainly where we are.
Access and audit
The record
Every action is attributable: what ran, when, on whose authority, and what it used to decide. You can see the log. So can we, which is how support works.
Questions
Read the answer before deciding.
Most of the time you catch it, because it was waiting for you to approve it. You edit it, and the edit is the instruction. It cannot send without a person. That is the answer to most versions of who is liable. Where nobody was asked, it is in the log, and fixing it is our job.
Your data is exportable at any time and you leave with it, including the history. The tools your business already ran on are still your tools. You can turn it off. The business keeps working, because nothing was taken away from anyone. What you would lose is the automation and the people who maintain it.
From 10 December 2026 the Privacy Act requires a privacy policy to disclose the kinds of personal information used in computer programs that make decisions, and the kinds of decisions made substantially by them. A human in the loop does not automatically put you outside that obligation. It can text customers only with consent that meets the Spam Act, with the sender identified and a working unsubscribe. Health service providers are covered whatever their size.
A few questions, and the hours a week your business puts into work that repeats. Built from your answers, with the workings shown. No cost, and no obligation at the end of it.