Last updated
July 28, 2026
Audio Compressor
Privacy Policy
How audio-compressor.org handles browser-based audio compression, Google Analytics, Google Fonts, cookies, and local storage.
Browser-based audio compression
audio-compressor.org is designed to let you compress audio files directly in your browser. The core audio compression process runs locally on your device. This means the audio files you select for compression are not uploaded to our server for processing.
Information we do not collect
- We do not require you to create an account.
- We do not ask for your name, address, phone number, or payment information to use the audio compressor.
- We do not upload, store, listen to, review, or share the audio files you process with the tool.
Browser-based file processing
When you choose an audio file, your browser may read the file so the tool can display details such as file name, file size, duration, and output settings. The compression task runs locally in your browser. The resulting file is generated on your device and can be downloaded by you.
Website analytics
In the production build, the site loads Google Analytics with measurement ID G-03KST9TQSB. Google Analytics may receive information such as page URL, browser or device information, referrer, approximate region, and interaction data, and may set or read cookies under Google’s own terms. This website code does not attach your selected audio, its file name, tags, artwork, or audio bytes to analytics requests.
Other third-party requests
Pages load the Inter typeface from Google Fonts. Your browser therefore makes requests to Google-hosted font domains. The current reviewed build does not contain Google AdSense code or an ad-serving integration.
Local storage
The site uses browser local storage for the theme preference only. Language is represented in the page URL. Tool settings and selected-file history are not persisted by the reviewed build. Local storage remains on your device unless you clear site data.
Children's privacy
audio-compressor.org is a general-purpose utility website and is not directed to children under the age required by applicable law. We do not knowingly collect personal information from children.
Data security
Because audio compression runs locally in your browser, your selected audio files are not transmitted to our server for compression. However, no website, browser, or internet transmission method can be guaranteed to be completely secure.
Your choices
- You can block or clear cookies and site data in your browser settings.
- You can clear the saved theme preference from local storage.
- You can leave the site without selecting a file.
- You can contact us if you have privacy-related questions.
Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date on this page.
Contact
If you have questions about this Privacy Policy, please contact us through the Contact page.
FAQ
Are my audio files uploaded to audio-compressor.org?
No. The compressor is designed to process audio files locally in your browser. Your selected audio files are not uploaded to our server for compression.
Can audio-compressor.org listen to or review my audio files?
No. Because the compression process runs in your browser, we do not receive, listen to, review, or store the audio files you process with the tool.
Does the website use cookies?
The production build loads Google Analytics, which may set or read cookies under Google’s terms. The reviewed build has no ad-serving integration.
Do Analytics or Fonts receive my audio file?
The site code does not attach selected audio, file names, tags, artwork, or audio bytes to Analytics or Google Fonts requests. Those website requests are separate from the local audio pipeline.
What is stored in my browser?
The reviewed build stores the theme preference in browser local storage. Language is in the URL, and selected-file history or tool settings are not persisted.
Can I use the tool with sensitive audio?
The tool is designed for local browser processing, but you should still avoid processing files on shared or untrusted devices if the audio is highly sensitive.