How Autrans protects your data

Last updated: October 22, 2026

Autrans understands African conversations the way they are actually spoken. To do that, it handles recordings, transcripts and the accounts behind them. This page says what we do to protect them. Each point is something the product does today, and a test in our code checks that the mechanism behind it exists. What we do not claim is at the end. For how we use your data, read our privacy policy.

Connections are encrypted

Autrans is served over HTTPS (TLS). We also tell browsers to use only HTTPS for our domain and its subdomains for two years (HSTS), and not to show Autrans inside another site's frame.

Sensitive fields are encrypted before they are stored

These are encrypted with AES-256-GCM, using a key that is kept outside the database. A copy of the database alone does not show them, and a value that has been changed is refused instead of read.

  • The tokens that keep your calendar and Zoom connections working.
  • The secrets behind staff two-factor codes.
  • The short-lived state used while you connect a calendar or Zoom.
  • The email addresses of meeting guests, read from a calendar invite so the meeting notes can be sent to them.
  • The record of who a meeting's notes were sent to.

Where we have to find a stored address again, for example so the same notes are not sent twice, we keep a keyed hash of it beside the encrypted value, not the address itself. The hash uses its own key, kept apart from the encryption key.

Passwords are hashed

We do not store your password. We store a bcrypt hash of it, with a cost factor of 12, which makes guessing slow on purpose.

  • Password reset links carry a random token. We store only a hash of the token, never the token.
  • Requests to reset or change a password, and to verify an email address, are rate limited.

Staff need a second factor

Autrans staff who open the admin tools must set up a second factor, a code from an authenticator app, and prove it again from time to time. Without it they are refused.

Staff reach only what their seat allows

Each staff seat has its own list of permissions. Every admin request is checked against that list on our servers, so hiding a link is never the only protection. An admin request that another website made the browser send is refused. Our automated checks fail if an admin route does not name the permission it needs.

Staff actions are logged

Changes staff make in the admin tools, such as to an account or to a staff seat, are written to an audit log: who did it, what changed, and when.

Private responses are not kept by shared caches

Responses that carry your account's data, such as your recordings, minutes balance and settings, are sent as private and no-store, so a CDN or other shared cache does not keep them. Share-link responses are marked the same way.

Meeting guests get extra care

When notes are emailed to the people invited to a meeting, their addresses are read from the calendar invite for that purpose only. They are stored encrypted, removed from the meeting record once the notes have gone out, and every notes email carries a link to stop receiving them.

A record that the notes were sent is kept, encrypted, for 90 days, or until the person who recorded the meeting deletes their account if that comes first.

You can export and delete your data

In Settings, under Privacy, you can download your account data and your transcripts, and delete your account. Deleting your account erases your recordings, transcripts, notes, calendar and Zoom connections, and the rest of your account's data.

A few records are kept on purpose, each for a reason written in our code: the do-not-email list, a small set of accounting records with you detached from them, and the log that a deletion or export was requested.

What we do not claim

  • We hold no security certification, such as SOC 2 or ISO 27001.
  • Autrans does not hide your content from us. To make a transcript, our systems have to read your audio, and transcripts are stored so that you can search them, so they are not encrypted field by field.
  • Email addresses of meeting guests that were stored before field encryption was added are encrypted by a one-off job that we run by hand. Until it has run on a site, those older rows are stored, and read, as they were.
  • No online service can promise that nothing will ever go wrong, and we do not.

Found a problem?

If you think you have found a security problem in Autrans, email hello@autrans.online and say what you found and how to see it. Please do not share it publicly first. Other questions are on the support page.