Privacy Policy
What AudioIntoText collects when you transcribe audio, who processes it, how long it is kept, and how to delete it.
Last updated: 2026-11-19
This policy explains what AudioIntoText collects, why, who else handles it, how long we keep it, and how you can delete it. It covers the website and the transcription service.
Who we are. AudioIntoText is run by Owen, an independent developer based in Los Angeles, California, USA ("we", "us"). We are responsible for your data under this policy. Contact: hello@audiointotext.com.
What we collect
Your account. Your email address and name. If you sign in with Google, we also receive the name and profile picture on your Google account.
Your files. The audio or video you upload, its file name and length, the transcript we make from it, and any edits you make to the transcript. We also keep a record of how many minutes you have transcribed, so we can apply your plan's limits.
When you create an account. Your IP address, the country it comes from, your browser language, the page that referred you to us, and any campaign tags (UTM parameters) in the link you arrived from.
When you are signed in. Your login session stores your IP address and your browser's user agent. We also record what you do in your account (for example, files transcribed or plan changes) so we can support you and keep the service working.
When you use the site without an account. We give your browser an anonymous ID and store a scrambled version of your IP address. The scrambled value is a keyed hash, not your IP address itself. We use both only to apply the free limits for visitors without an account.
Server logs. Our hosting provider records requests and errors, such as the address requested, the time, and error messages. We use these logs to find and fix problems.
Cookies
We use these cookies the service needs:
- a login session cookie, when you sign in;
- an anonymous visitor ID, kept for up to one year, used for the free limits;
- your language preference;
- your color theme choice, if you pick one, kept for up to one year;
- your cookie choice, if we ask for consent, so we do not ask again;
- the page that referred you and any campaign tags, read when you create an account.
We also use two analytics tools to see how people find and use the site:
- Cloudflare Web Analytics counts page views without cookies and without building a profile of you. It runs for every visitor.
- Google Analytics loads only after you choose "Accept" in the cookie banner. It then sets its own cookies (named
_gaand_ga_<id>, kept for up to two years) to count visits and see which pages and links bring people here. If you choose "Reject", or make no choice, it does not load. You can change your choice at any time with "Cookie Settings" at the bottom of the home page and of this policy. If you withdraw consent, we delete these cookies from your browser and reload the page, and Google Analytics no longer loads.
We do not use advertising cookies.
How we use your data
- To transcribe your files and show you the results.
- To run your account, apply plan limits, and, once paid plans are available, bill you.
- To prevent abuse, for example limiting how many accounts can be created from one network in a day.
- To understand which pages and links bring people to the site.
- To answer you when you write to us.
We do not sell your data. We do not use your files to train any model of our own.
Who processes your data
We use these providers to run the service:
- Cloudflare hosts the website, keeps server logs, and stores your uploaded files. To transcribe a file, we give AssemblyAI a temporary link to fetch it from Cloudflare storage.
- Our database provider stores account details, transcripts, and usage records.
- AssemblyAI turns your audio into text. See below.
- Google signs you in, only if you choose "Continue with Google". Google also provides Google Analytics, only if you accept analytics cookies.
- Cloudflare also provides Cloudflare Web Analytics, which counts page views without cookies.
- Dodo Payments processes payments as our Merchant of Record (seller of record), including taxes and refunds. We never see or store your full card number.
About AssemblyAI. On our current AssemblyAI plan, AssemblyAI may use uploaded audio to improve its models, as its terms of service describe. When your transcript is finished, we ask AssemblyAI to delete it. AssemblyAI deletes its copy of the audio under its own rules, usually within 24 to 48 hours. Asking for deletion does not change what AssemblyAI's terms allow while it holds the file. We will update this section when we move to a plan where model training is switched off.
These providers may process data in the United States and other countries. Where the law requires it, we rely on the transfer safeguards these providers offer.
How long we keep it
- Files uploaded without an account: deleted automatically 24 hours after upload, with their transcripts.
- Files in an account: kept for 3 years so you can come back to them, or until you delete them sooner.
- Account details, login sessions, and usage records: kept while your account exists. They are not deleted automatically. To delete your account, email us and we will delete it.
- AssemblyAI's copy: see "About AssemblyAI" above.
- Server logs: kept for our hosting provider's standard log period, then deleted automatically.
Deleting your data
- To delete one file, open it in your account and choose Delete. This removes the audio and the transcript from our storage.
- To delete your account and everything in it, email hello@audiointotext.com from the address you signed up with.
Your rights
You can ask us to show you, correct, export, or delete the personal data we hold about you, or object to how we use it. Email hello@audiointotext.com. Depending on where you live, you may also have the right to complain to your local data protection authority.
Children
AudioIntoText is not meant for children under 13, and we do not knowingly collect their data. If you think a child has given us data, email us and we will delete it.
Security
Uploads and pages are sent over encrypted connections. Your files are stored privately, and the link we give AssemblyAI to fetch a file expires after a short time. No service is perfectly secure, but we limit who and what can reach your data.
Changes to this policy
If we change this policy, we will update the date at the top of this page. If the change matters, for example a new provider that handles your files, we will also say so on the site before it takes effect.
Contact
hello@audiointotext.com