Who can open the account, and who cannot.
Signup does not take a card. The password is stored as a hash. Another company's record is not in your login.
A password we cannot read back
Signup asks for an email, a name, a company name, and a password. It does not ask for a card.
The password is stored as a one-way hash. A person with the database cannot open it and type it back in. Signing in compares the password you type with that hash. An account created another way, with no password set, cannot be signed into by guessing a blank one.
The browser keeps a session, not the password. Signing out ends that session on this device.
One org sees one org
A colleague is invited into the company. They do not get a second, quieter copy of it.
Every user belongs to one organisation. The plan, the company record, the tools, the leads, and the assistant thread belong to that organisation. A teammate on the same plan sees the thread, because the thread is about the plan.
An invite is for one email address, expires after 14 days, and works once. Accepting it on a different address does not succeed.
Staff access is a flag on the user, set in the database. There is no screen in the product that turns a customer into staff. The admin queue checks that flag on every request and answers as if the page does not exist when it is absent.
A hosted database, not the web server's disk
The site can be served without the database. The account cannot.
Account records live in hosted Postgres. The application is served over HTTPS. We do not keep the database file on the machine that serves the pages, because that machine's disk is not a place to keep a customer.
Do not put passwords, API keys, or one-time codes in the company form. It asks which tools you use. It does not ask for the secret that opens them. The accounts you already pay for, the phone carrier and the ledger included, stay in your name and under your login.
Write, and say it is security
There is no separate bounty programme, and we will not invent one on this page.
Email hello@betr.agency with Security in the subject and enough detail for us to see the issue. Do not include a customer's own data if you can describe the issue without it.
We will acknowledge a report we can reproduce. We do not promise a public write-up or a payment.
The matching pages are safety, privacy, and the terms.
Security is who can open the account. Safety is what the account is allowed to do.
The short version
The long version is above. These are the lines people look for.
Do you store my password?
No. We store a one-way hash. We cannot read the password back.
Can I become staff from inside the product?
No. That flag is set in the database, and the admin queue refuses anyone without it.
Where do I report a problem?
hello@betr.agency, with Security in the subject.