Security and data handling

How Uspeech protects call recordings: encryption, team isolation, retention and deletion, our subprocessors, and how we handle HIPAA and BAA requests.

Where we stand on HIPAA

Our HIPAA program is in progress. Pilots run on calls that contain no protected health information (PHI). We sign a Business Associate Agreement (BAA) before any PHI is processed.

If your calls include PHI, talk to us first. We’ll agree the scope of a BAA before a single recording is uploaded.

What is in place today

  • Encryption. Data is encrypted in transit. Call recordings and files are encrypted at rest.
  • Isolation. Each team’s data is kept separate from every other team’s.
  • Retention. You choose how long recordings are kept. When the window expires, they are deleted automatically.
  • Deletion on request. Deleting a recording or a project removes it permanently, and each deletion leaves an audit record.
  • Clean logs. Our application logs don’t contain transcript text.
  • No training on your data. Our AI providers process your data under paid or enterprise terms that don’t allow them to train models on it.
  • Private transcription. Optionally, call audio is transcribed on infrastructure operated by Uspeech instead of a third-party speech service.

Subprocessors

These providers process data on our behalf.

Provider Data
Amazon Web Services Customer content and account data
Google Customer content and account data
Microsoft Azure Customer content
Mailgun Account data (email delivery)
Paddle Account and billing data

Security questionnaires

We answer security questionnaires and review requests on request, under NDA.

Contact

For a security review, a BAA discussion or a questionnaire, contact us and choose Security & BAA review.