Skip to content

Privacy questions to ask before uploading audio

Checked October 26, 2026

Uploading a recording sends your audio to someone else's computers. Before that happens, find out where it goes, how long it stays and who can reach it. The answers sit in the maker's own documents, and they differ from tool to tool.

Questions along the audio's pathYour recordingSent to the maker's serversStored for some periodTranscript returned to you
Each step is a place to ask what the maker's documents say.

Where does the recording go?

Ask whether the tool runs on your device or on the maker's servers. Most web tools send audio away. Look for the country or region where data is processed. That can matter if your business has rules about keeping data inside a country.

Amazon's documents show the idea of sharing the job. They say that you are "responsible for maintaining control over your content that is hosted on this infrastructure"1. The maker secures its systems, and you manage your own account and content.

How long is it kept?

Check the retention period, which is how long audio and transcripts are stored. Some tools keep files until you delete them. Others delete them after a set time. Look for a delete option and for what happens to backups.

Don't assume. If the pages don't say, ask the maker, and keep the reply.

Is it used to train the tool?

Some makers may use customer content to improve their products. Others say they don't. Read the terms and the data page for this exact plan, since business and free plans can differ.

Who in your business can open it?

Amazon recommends that you "Use multi-factor authentication (MFA) with each account"1. Multi-factor authentication asks for a second proof of identity, like a code from a phone, on top of the password. Use individual logins instead of one shared account where the tool allows it.

What should stay out?

Keep secrets and customer data out of transcription tools unless your business's own policy allows them. That covers:

  • Passwords, API keys and access codes spoken aloud
  • Card numbers and bank details
  • Customer records and personal details
  • Health information

Amazon is blunt about a related case. For its custom word lists it says "Do not enter confidential information, personal information (PII), or protected health information (PHI) into a custom" vocabulary2. It also warns that "Any data that you enter into" tags or free-form name fields "may be used for billing or diagnostic logs"1.

Some tools offer to hide sensitive details in a transcript. Amazon lists "Automatic Content Redaction" as an extra feature for removing personal identifiable information3. Redaction is a safety net, not permission to upload anything.

Laws and consent

Rules on recording people and handling personal data differ by country, state and industry. Some places need everyone's consent to record a call. This site doesn't give legal advice. Check your own country's official privacy regulator and, if needed, a qualified adviser.

Finding these answers means reading the maker's pages with care. Reading a tool's docs shows where to look.

Notes and sources

  1. Data protection in Amazon Transcribe, Amazon Web Services
  2. Custom vocabularies, Amazon Web Services
  3. Amazon Transcribe pricing, Amazon Web Services