Privacy Policy
Last Updated: May 26, 2026
TL;DR: FreeAudioTrim processes your audio in your browser. We do not receive your audio files. We do use limited browser storage for features like language preference, translation sessions, and transcription recovery, and some pages load third-party resources such as fonts, icons, translation tools, and contact form handling.
Who This Policy Covers
This policy explains how FreeAudioTrim handles information when you use our website and browser-based audio tools.
Audio Files Stay on Your Device
Our core editing tools are designed to process audio locally in your browser. In normal use, we do not upload your selected audio files to our servers for trimming, cutting, merging, normalization, speed changes, pitch changes, silence removal, conversion, or similar editing tasks.
- You choose a file from your device.
- Your browser reads the file locally.
- Processing happens in browser memory using web technologies such as the File API and Web Audio APIs.
- The output file is generated in your browser and saved back to your device.
What We Do Not Collect From Audio Editing
- Your audio content: We do not receive the content of audio files processed by the main browser-based tools.
- Your original file names for core editing: We do not receive the file names of files you process in the main browser-based editing flow.
- Accounts: You do not need an account to use the site.
- Routine analytics profiles: The current codebase does not include first-party analytics tags or ad tracking tags.
Browser Storage We Use
The site uses browser-side storage for certain features. This storage lives in your browser, not in our own application database.
Local Storage
- Language preference: We store your preferred site language so we can keep you on the language version you chose.
- Translation session data: When you open the transcript translation view, transcript text, segment data, language settings, and related metadata may be stored in
localStoragefor a limited period so the translation page can load. - Model and tool state: Some transcription-related state may be stored locally to support model handling and recovery behavior.
Session Storage
- Transcription recovery: We use
sessionStorageto help recover in-progress transcription state if the page refreshes during a session.
Browser Cache
- Cached model/runtime assets: Some transcription components may use your browser cache or Cache API so models or runtime files do not need to be downloaded again each time.
You can clear this locally stored information by clearing site data in your browser.
Third-Party Services and External Resources
Some parts of the site load files or services from third parties. Depending on the page and feature you use, your browser may connect directly to these providers.
- Google Fonts: Many pages load fonts from
fonts.googleapis.comandfonts.gstatic.com. - Lucide icon library: Some pages load icons from
unpkg.com. - Contact form delivery: The contact page submits form entries to Formspree. If you use the contact form, the information you enter, such as your name, email address, and message, is sent to Formspree for delivery.
- Google Translate: The transcript translation view can load Google Translate resources when you use that feature.
- AI transcription runtimes and models: Transcription features may fetch runtime or model assets from third-party CDNs or model hosts such as jsDelivr and Hugging Face so the model can run in your browser.
- Flag images: Some language UI elements load country flag images from
flagcdn.com. - External links you choose to open: Some buttons may open external services, such as ChatGPT, in a new tab only after you click them.
Those providers may receive technical request data that web servers normally receive, such as your IP address, browser information, and request headers, when your browser loads their resources.
Contact Form Data
If you contact us through the website form, the message is not processed purely locally. The information you submit is sent to Formspree so the message can be delivered to us. Please do not include sensitive personal information or confidential audio content in that form unless you are comfortable sending it through that third-party service.
What We Currently Do Not Use
- No account system
- No first-party advertising tags in the current codebase
- No first-party analytics tags in the current codebase
- No first-party cookie code in the current codebase for tracking or profiling
Your Choices
- Use the core editing tools without submitting a contact form.
- Clear your browser's site data to remove local storage, session storage, and cached assets.
- Block or limit third-party resources in your browser, understanding that some features may stop working properly.
- Use private browsing modes if you want less persistent local storage.
Data Security
Because the main editing flow runs locally, the security of your audio files depends heavily on your device and browser environment. We still use HTTPS so your browser loads the site over an encrypted connection.
Children's Privacy
We do not knowingly build profiles about children or require user accounts. However, if someone uses the contact form, the submitted information is transmitted through a third-party form provider. Children should use the site with appropriate supervision where required by local law.
International Users
Because some features load third-party resources directly in your browser, those requests may involve providers operating in multiple countries. The main audio editing workflow itself is still designed to run on your device.
Policy Changes
We may update this policy as the site changes. If we add analytics, advertising, accounts, server-side uploads, or additional third-party services, we will update this page to reflect those changes.
Contact
If you have questions about this privacy policy, you can reach us through the contact page.
- Contact Form: Visit our contact page