Security

Security, in detail

A phone system holds your conversations with your customers and your company’s money. This is how both are protected.

Protecting calls

So nobody else can listen.

TLS signalling
Who is calling whom travels over an encrypted channel. Plain SIP is not supported.
SRTP audio
The audio itself is encrypted. Intercepting it in transit yields nothing anyone can listen to.
Encryption is mandatory
Not a setting to turn on. A call that cannot negotiate encryption is not established at all.
Separate SIP identities
Every company gets its own SIP realm, so extension 101 at one company and 101 at another are two entirely different principals.

There is no route from one customer’s data to another’s.

Enforced in the database
Separation is not left to application code remembering to filter. Row-level security policies sit on every table, so even a bug in the application cannot return another company’s rows.
And tested
Whether one company can read another’s data is checked by an automated suite on every change, not assumed.
Passwords cannot be read back
Passwords are hashed with Argon2id. We cannot see yours either.
The least data we can run on
We ask for no company documents and no identity documents, and your card number never reaches us — it is entered on Stripe’s page. Data that was never collected cannot leak.

A stolen trunk is somebody else’s bill. It is stopped, not noticed later.

Trunk passwords cannot be read back
Your carrier credentials are stored as a digest, which authenticates the trunk without keeping the password. Nobody can display it again — not you, and not us.
Perimeter filtering
Addresses that repeatedly try bad credentials are blocked automatically, before they reach the switch.
A limit that ends the call
Where an account has a monthly allowance, the call in progress is cut at the last second it covers. A limit that only refuses the next call is not a limit.
Encryption cannot be turned off
There is no plain-SIP fallback to be downgraded onto. A call that cannot negotiate TLS and SRTP is not placed at all.

A security page listing only the good parts is advertising rather than information. As things stand today:

No independent security audit and no ISO or SOC certification — neither has been carried out yet.
There is no call recording, and therefore no recording retention policy yet.
Two-factor authentication has not been added.
A full audit log is still being built; today only platform-administrator actions are recorded.

If you find a weakness, tell us directly. We will investigate and reply, and we ask that you hold off publishing until it is fixed.

Two seats and a hundred minutes, without a card. Upgrade when the phone system has earned it.