// privacy
Privacy Policy
Last updated: June 11, 2026
The short version
Your audio files are never uploaded to us — it's architecturally impossible. Every tool on MyFreeAudioTool processes your files locally, inside your own browser, and that's worth explaining properly because it's the whole point of this site.
How client-side processing actually works
When you drop a file onto one of our tools, your browser reads it directly into your device's memory using the JavaScript File API. The processing — trimming, converting, equalizing, analyzing — is done by code running in your browser tab: the Web Audio API (your browser's built-in audio engine) and WebAssembly modules like FFmpeg and the LAME encoder, which are downloaded as program code the same way images and stylesheets are. The finished result is written back to your device by your browser's download mechanism.
At no point in that pipeline does your audio touch a network connection. There is no upload endpoint on our servers — nothing for your file to be sent to. You can verify this yourself: open your browser's developer tools, watch the Network tab while using any tool, and you'll see no audio data leaving your machine. The Web Audio tools even keep working if you disconnect from the internet after the page loads.
This applies equally to microphone recordings made with the voice recorder: audio is captured and held in your browser's memory only, and is gone when you close the tab.
What we do collect
Analytics. We use Google Analytics to understand aggregate site usage — which pages are visited, roughly where visitors come from, what devices they use. Google Analytics uses cookies and collects standard technical information such as IP address and browser type. It never has access to your audio files. You can block analytics with any standard tracker blocker without affecting how the tools work.
Local storage. We store one small preference in your browser's localStorage: your light/dark theme choice. It never leaves your browser.
Advertising
The site may display advertising to keep the tools free. Ad providers may use cookies to serve relevant ads. Ads have no access whatsoever to your files or recordings.
Third-party CDN resources
Some tools load open-source processing libraries (FFmpeg.wasm, LAME MP3 encoder) and web fonts from public CDNs the first time you use them. These are standard downloads of program code and assets — none of your data is sent in the process.
Children's privacy
The site is a general-audience utility and does not knowingly collect personal information from anyone, including children under 13.
Changes to this policy
If we change this policy we will update this page and its date. Material changes will be noted prominently.
Contact
Questions about privacy? Reach us via the contact page.