Security

How sign-in and call data are handled.

Accounts use hashed passwords. An owner uses a sign-in code from an authenticator app. Call records stay with the company that opened the account.

01

What is in place today.

  • Sign-in

    Passwords are hashed. An owner confirms sign-in with a code from an authenticator app. Recovery codes are issued once and each code works one time.

  • Forms and sessions

    Form posts carry a CSRF token. A session is tied to the signed-in account and ends when you sign out.

  • Carrier webhooks

    Inbound call events are accepted only when the webhook is signed and the timestamp is within the allowed window.

  • Roles

    Work is scoped to the owner, a company, or a department. A viewer can look, not change.

  • Call records

    The account, the schedule, and the call log are stored for the company that opened the account. A recording is stored only when recording consent is recorded on the call.

  • Secrets

    Secrets and sign-in codes are encrypted. This page is a draft until counsel reviews it. The details are also on the privacy page.

Read the privacy page