Privacy

The short version: on this website your files never leave your device, and there is nothing here to sign up for. Using iHateAudio from ChatGPT, Claude or another AI assistant is the one exception, because the work runs on our server instead of in your browser.That is explained in full below.

What happens to your audio

When you drop a file onto any tool on this site, your browser reads it from your own disk into the memory of that tab. All decoding, editing and encoding happens there, using audio features built into the browser itself. The finished file is written back out by the same tab and saved straight to your downloads folder.

At no point is your audio transmitted anywhere. There is no upload step, no processing server, and no storage bucket, not because we delete files quickly, but because they are never sent in the first place. Closing the tab discards everything.

How to verify that yourself

Do not take our word for it. Two checks, either of which is conclusive:

• Open your browser's developer tools, switch to the Network tab, and use any tool normally. You will see the page and its code load, and then nothing further, no request carrying your file.
• Load a tool page, then disconnect from the internet entirely and use it. Everything still works, because there is nothing on the other end to talk to.

If you use iHateAudio from ChatGPT, Claude or another AI assistant

An AI assistant cannot run a tool inside your browser tab, so it reaches iHateAudio through our MCP server at ihateaudio.com/mcpinstead, and the work happens on our server. When you ask an assistant to use one of the tools:

• The assistant gives our server a link to the file. In ChatGPT that is a temporary link to the file you shared in the chat; in other assistants it is a public link that you or the assistant supply. Our server downloads the file from that link and stores it in Cloudflare R2, the storage this site already runs on.
• Our server opens the same tool page from this site in a browser run by Cloudflare, loads your file into it, and runs the tool with the settings the assistant chose. It is the same code that runs in your own browser here.
• The result is stored in R2, and the assistant gets a link to it. The link has a long random part that cannot be guessed, but anyone who has it can download the file. It stops working one hour after the result is made.
• Your original file is deleted as soon as the job finishes. Results are deleted automatically one day after they are made, and Cloudflare can take up to one more day to remove them.

So in this case your audio does leave your device. It goes to the assistant's company (OpenAI for ChatGPT, Anthropic for Claude) under that company's own privacy policy, and then to our server on Cloudflare for the time above. Cloudflare is the only other company that handles it, as our hosting provider. We do not listen to it, share it, sell it, or use it to train anything.

Cloudflare keeps our server's request logs for a few days. A log line records the time of a request and can include the IP address it came from, which for an assistant's request is usually the assistant's server rather than you, and the link path, which can include a file's name. It never includes the audio. And because the job runs on this site's own tool page, the page analytics below count it like a visit: a page view, that a file was accepted, and the output format. None of that identifies you.

What we do collect

Page analytics, through Google Analytics and PostHog: which pages were viewed, roughly which country from, and which site sent you. On a tool page we also record what happened, and only this: that a file was accepted, which output format you chose, whether the export used the smaller AAC encoder in place of the converter and why, and the error code if something failed. A failure also records the facts that tell one cause from another: the type of error, the browser's error message with anything that could be a file name removed, the step that failed, how much of the converter had downloaded, the kind of file (MP3 or OGG, for example), and the class of browser and its memory. It exists so we know which tools are worth more work and which ones are quietly broken.

What is deliberately switched off is worth more than what is on. There is no session recording, because a replay of a tool page would capture your filenames, and a filename is content. Nothing you type is captured. No file name, no file size and no audio ever reaches either service. We set no cookie of our own; Google Analytics sets its own, which is the honest cost of using it. Advertising and remarketing signals are turned off.

If your browser sends Do Not Track, PostHog collects nothing at all. Any blocker will stop both, and every tool keeps working exactly the same, because none of this is load bearing.

There are no accounts, so there is no email address, password, or profile to leak. There is no advertising, so no advertising network receives anything about you.

The one network request worth explaining

Most tools need nothing beyond the page itself. A few output formats (M4A, OGG, FLAC, WMA, AIFF and iPhone ringtones) require a converter that is too large to include in every page, so it downloads on demand the first time you use one, from this site's own servers. On a browser that cannot run the converter, M4A, AAC and ringtones use a smaller encoder instead, about 200 KB, from the same servers.

That download goes one way: code comes to you, and your audio still does not go anywhere. It is also the only third-party-free way to do it, the converter is hosted here rather than pulled from someone else's CDN, precisely so no other company sees that you requested it.

Local storage

If you use the "keep going" links after exporting a file, the result is held in memory and handed to the next tool so you do not have to select it again. A short-lived token in your browser's session storage links the two. It is cleared when you close the tab and contains no audio itself.

Installing the site as an app caches the pages so it works offline. That cache holds only the site's own code, never your files.

Changes

If this ever changes in a way that affects what happens to your files, it will be stated plainly on the affected tool page, not buried here.

Last updated 4 October 2026.