Privacy Policy
Last updated
This page explains what happens to a file after you upload it to mp3totext.xyz: what is stored, how long it stays, who else processes it, and how to have it removed.
Who runs this site
mp3totext.xyz is an independent service run by one person. There is no company behind it and no staff beyond the operator. You can reach the operator at support@mp3totext.xyz.
What we collect
Everything below exists because the service cannot work without it, or because we need to know how the site is being used. We do not collect anything for advertising, profiling or resale.
- The files you upload. Audio and video files, including whatever is spoken in them, stored until they are deleted.
- The transcripts we produce. The text, the per-word timestamps and the speaker labels generated from your file.
- File details. File name, size, format, duration, detected language, and counts of words, lines and speakers.
- Account details. If you sign in, we store what Google tells us about the account you chose: your email address, your display name and the URL of your profile picture. Signing in with Google is the only way to create an account here, so we never receive or store a password. You can transcribe files under 30 minutes without signing in; in that case we create an anonymous identity that exists only to hold your transcripts and your free allowance together. Longer files and AI summaries need a signed-in account.
- Session details. Each session record stores the IP address and browser user agent it was created from, so a session can be recognised and expired.
- Usage records. The number of seconds of audio each transcription used, which is how your free allowance and paid hours are counted.
- Payment records. If you buy hours, the payment itself is handled by Creem (see below). At checkout Creem collects your email address, billing address and payment method. We never see or store your card number. What we keep is Creem's customer ID for you, the order and subscription IDs, what you bought and when, and any refunds.
- Server logs. Technical events such as job identifiers, timings and errors. They exist for debugging, not for storing your content.
- Analytics data. Information about how the site is used — pages opened, how you arrived, device and browser type, an approximate location derived from your IP address, and how you move around a page: clicks, scrolling and mouse movement. See Analytics below.
Analytics
We use two third-party analytics services to understand how the site is used: which pages get opened, how people find us, what browsers and devices they arrive on, and roughly where in the world they are. They work from the ordinary technical details a browser sends with any request, and they set cookies so one visit can be told apart from another.
One of the two also records the interaction itself — clicks, scrolling, mouse movement and the layout of the screen — and replays it as an anonymous session, which is how we find the places where the interface confuses people. The parts of a page that carry your own content are blanked out before anything leaves your browser: transcript text, summaries, file names, and your account name and email address are all replaced with grey shapes in a recording, and text typed into a field is not captured either. We see that you scrolled through a transcript, not what the transcript said.
Analytics is about the site, not about your recordings. Neither service is given your audio files, your transcript text or your account details, and we read the results as aggregate reports about traffic rather than as profiles of individuals. None of it is used for advertising, and there are no advertising tags on this site.
If you would rather not be measured, blocking or clearing cookies in your browser, or using a content blocker, stops it. Transcription works exactly the same either way.
What we do not do
We do not sell or rent your data. We do not use your recordings or transcripts to train models — they are used only to produce and show you the transcript you asked for. We do not show advertising and we do not build advertising profiles. Web fonts are served from our own domain rather than fetched from a font provider.
Who else processes your files
These providers are involved in delivering the service. Nobody else receives your audio or your transcripts.
- Cloudflare hosts the site and stores uploaded files and transcripts in private storage on its global network.
- Replicate (United States) runs the speech recognition model that produces your transcript. When transcription starts, we give it a short-lived signed link so it can read that one file, and it returns the transcript to us.
- A PostgreSQL database we operate holds account records, file details and the usage records described above. Your audio and transcript text are not stored there.
Google is involved only if you choose to sign in. That happens in a separate window that talks to Google directly; Google then tells us which account you picked. It is not given your files, your transcripts or anything else you do here.
Creem processes payments and is the merchant of record for every purchase. It is involved only if you buy hours. It collects the payment and billing details it needs to take the payment, issue a receipt and handle tax, and tells us what was bought. It is not given your files or your transcripts.
Our two analytics providers receive the usage data described in Analytics above. They see how the site is used, not what you upload.
How long things are kept
- Audio and transcripts: deleted 24 hours after upload. Both the audio file and the transcript generated from it are removed automatically once 24 hours have passed. Export anything you want to keep before then.
- Deleting a transcript yourself removes the files immediately. You do not have to wait for the 24-hour mark.
- A record of the job survives deletion. After the files are gone we keep the description of the job — file name, size, duration, language, the counts, and the times it was created and deleted — so your history shows what expired instead of silently losing entries, and so your usage stays countable. The audio and the transcript text are no longer there.
- Account records are kept until you ask us to delete the account.
- Payment records are kept for as long as tax and accounting law requires. Deleting your account does not delete the transaction records we are required to keep.
- Anonymous identities last as long as the session cookie in your browser. Clear your cookies and that identity, along with access to any transcripts under it, is gone for good.
Cookies
Two kinds of cookie are used here.
- An essential session cookie. A signed cookie that identifies you — anonymously, if you have not signed in — so your transcripts and your remaining free allowance follow you between page loads. The service cannot work without it.
- Analytics cookies. Set by the analytics services described above so that visits can be counted and told apart. They are not used for advertising.
You can block or clear cookies in your browser at any time. Clearing them ends an anonymous session, and any transcripts held under it become unreachable.
Recordings that include other people
A recording usually contains someone other than you. You are responsible for having the right to upload it, including any consent required where it was recorded. Because this service is run by one person, keeps files for only 24 hours and offers no formal support agreement, we would not choose it for material that is highly sensitive — medical records, legal privilege, or anything similar.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to how it is processed. Most of this you can do yourself: delete a transcript from your history and its files are removed at once, and exporting a transcript as TXT, SRT or VTT is a button on the result page.
For anything else — including deleting your account and everything attached to it, apart from the payment records the law requires us to keep — email support@mp3totext.xyz. We will respond within 30 days. If you used the service anonymously, we may not be able to identify your data without the session it was created under.
Where processing happens
The site runs on Cloudflare's global network and transcription runs on Replicate in the United States, so your file may be processed outside the country you are in.
Security
Uploads and downloads run over encrypted connections. Stored files sit in private storage that is not publicly readable; playback and download go through short-lived signed links tied to your session. We never handle a password — signing in goes through Google — and we never handle card details, which go to Creem. No service can promise perfect security, and this one is no exception.
Children
This service is not directed at children under 16, and we do not knowingly collect their personal data. If you believe a child has used the service, email us and we will remove the data.
Changes to this policy
If this policy changes, the date at the top of the page changes with it. Continuing to use the service after that means you accept the updated policy.
Contact
Questions about this policy, or about data we hold: support@mp3totext.xyz.