Security and data

This page describes what is designed into the product to protect your accounts, your keys and your communication data. It claims no certification: none has been obtained to date.

Updated on

Access rights by project and role

Each member of an organization gets a role, and each role applies to a scope: the organization, a sub-account or a project. Permission checks run on the server for every object requested. Hiding a button in the console is never treated as access control.

  • A member only sees the projects they are attached to.
  • Caller and callee numbers can be masked depending on permissions.
  • Exports are generated on the server, filtered by permissions, and expire.

API keys and secrets

API keys let your servers call the API. They are designed to limit the damage if one leaks.

  • A key can be limited to one project and to specific actions.
  • A key can be revoked at any time, with immediate effect.
  • A secret (an API key or a webhook secret) is shown once, when it is created. It cannot be displayed again: you generate a new one.
  • No provider key appears in the browser or in a URL.
Never place an API key in a mobile app or in code that runs on the user’s device.

Signed webhooks

Each notification sent to your server carries a signature computed with your endpoint’s secret and a timestamp. Your server verifies it before processing the event and rejects notifications that are too old. The event identifier lets you ignore a duplicate.

Fictional example of a signature header. The format is that of the demo API.
Telqio-Signature: t=1788000000,v1=<hexadecimal signature>

Logs and audit

  • Technical logs are redacted: no secrets, tokens or SMS content in operational traces.
  • Sensitive actions (ordering or cancelling a number, rotating a secret, changing permissions) leave a timestamped audit record.
  • Usage events are kept append-only. A correction creates a new event instead of overwriting an old one.

Isolation between organizations

One organization’s data is never readable by another. Isolation is checked on every request, including exports and attachments. Imported inputs (CSV files, callback URLs) are validated before being processed.

Call recording and retention

Call recording is off by default. When you turn it on, you define the purpose and the retention period. Informing recorded people and handling their access requests are your obligations, depending on the service and the country.

Hosting and subprocessors

Choices of hosting, telecom providers and subprocessors have not been finalized. They will be published on this page and in the privacy documents once decided.

No security certification is claimed today. Any future mention will be dated and come with its scope.

Frequently asked questions

Where is my data stored?

The hosting location has not been finalized. It will be published here as soon as it is decided.

Can I recover a lost secret?

No. A secret is shown only once. Revoke it and create a new one.