What we will say, and what we will not put a logo on.
Four pages. They match the software. They do not borrow a compliance mark from a company we are not.
Four pages, and the claims we will not make
A trust page that invents a certificate is worse than none.
We have not published a SOC 2 report, an ISO certificate, or a penetration-test letter. If that is a requirement for your procurement, say so in the company record and we will tell you plainly whether we can meet it. We will not put a badge on this site to get past the question.
We are not a law firm and not a hospital vendor. The privacy page describes what this software stores. It is not a privacy impact assessment for your industry.
Who can see the account
Passwords, sessions, the boundary between companies, and what staff can open.
What is allowed to run
The assistant, the review queue, and the line between a plan and a job that sends or spends.
What we hold, and why
The account, the company record, messages, and the one outside service the assistant uses.
The free account, in writing
What opening an account does and does not buy. Paid work is a separate agreement.
The same facts, in the product
The policies are not a PDF that the software ignores.
Security is the account model: one company, hashed passwords, invites that expire, and a staff flag that the product itself cannot grant.
Safety is the company form's never-automate answer, the assistant's refusal to invent a build, and the review queue's refusal to bill you.
Privacy is the list of fields on that form, plus the fact that a reply is shown inside the account and not emailed.
If something here is wrong, write to us.
hello@betr.agency. A security report goes to the same address, with Security in the subject.