Security

One company cannot see another

Isolation is enforced in the database, not in application code. Every table carries the company it belongs to and a row-level policy that the database applies to every query, so a bug in a screen or an API route cannot leak one customer’s calls into another’s. There is a test suite written from the attacker’s side — a real token, a direct query, no application in the path — that runs on every change.

Credentials

Carrier keys, mailbox passwords and payment keys are sealed with AES-256-GCM before they are stored, with the key held only in the server’s environment. A copy of the database on its own opens none of them.

Your team’s SIP passwords are never readable by your own staff: the column is withheld at the database level, not hidden by a screen.

In transit

The application and its API are HTTPS only, with HSTS. Calls from the browser run over encrypted WebRTC, and signalling to the switch over TLS. Certificates renew themselves.

Money and records

The billing ledger is append-only, enforced by the database — nothing in the application, including a compromised one, can rewrite what a customer was charged. Closing a company retires it and keeps its ledger and audit trail rather than deleting them.

Payments

Cards are handled by Stripe on Stripe’s own pages. No card number reaches our servers, and a payment only credits an account when Stripe’s signed notification says it happened.

The server

One machine, firewalled to the ports the service needs, with automatic security updates, failed-login banning, and recordings backed up encrypted to storage in a different place.

What we do not claim

We are not SOC 2 or ISO 27001 certified, and we will say so rather than imply otherwise. If you need a signed questionnaire or a penetration-test report before you can buy, write to us and we will tell you honestly what we can and cannot provide today.

Telling us about a problem

If you find a vulnerability, send it to security@togodial.com. We will confirm we have it within two working days. Please give us a reasonable chance to fix it before publishing, and please do not test against other customers’ data.