Your audio is processed in your browser, not uploaded
Every Audio Lab tool decodes and processes audio using your browser's own capabilities — the Web Audio API, WebAssembly, and, for a few AI tools, WebGPU. That processing happens on your device. Your audio file is never sent to a server for a tool to work on it, and we have no server-side copy of anything you open, record, or export.
No accounts, no advertising
There is no account system on Audio Lab, so we don't hold a profile, an email address, or a password for you. We don't serve advertising, and we don't use advertising or cross-site tracking cookies.
Analytics: how we count visits
We use Google Analytics 4 to understand which pages and tools people use, so we know what to improve. When a page loads, your browser sends Google standard visit data: the page address and title, the referring page, your browser, device type and screen size, and an approximate location that Google derives from your IP address. Google Analytics 4 does not log or store IP addresses.
To tell new visits from returning ones, Google Analytics sets first-party cookies on this site (named _ga and _ga_ followed by an ID) that last up to two years. Google processes this data under its own terms; see how Google uses information from sites that use its services at policies.google.com/technologies/partner-sites.
Analytics never receives your audio, the names or contents of files you open, recordings, or text you type into a tool: all of that stays in your browser. You can opt out at any time by blocking cookies for this site, using a content blocker, or installing Google's Analytics opt-out browser add-on from tools.google.com/dlpage/gaoptout.
What's stored on your device, and how to remove it
A few kinds of data live in your browser, on your device only, so that tools can remember your preferences and pass audio between each other without asking you to upload it twice. None of this is visible to us, and none of it leaves your device on its own.
You can clear all of it at once from Studio settings, using the clear local data or clear model cache options there, or manage it yourself through your browser's own site-data settings for this site.
| Data type | Where it lives | How to remove it |
|---|---|---|
| Favorites, presets, and tool settings | Local storage (in your browser) | Studio settings → clear local data, or your browser's site-data settings |
| Audio passed between tools with Continue in another tool | IndexedDB (in your browser) | Studio settings → clear local data, or your browser's site-data settings |
| Saved soundboards | IndexedDB (in your browser) | Studio settings → clear local data, or your browser's site-data settings |
| Downloaded AI model files and the FFmpeg codec core | Cache Storage (in your browser) | Studio settings → clear model cache, or your browser's site-data settings |
Third-party network requests
A couple of tools need files that aren't practical to bundle with the page itself, so your browser fetches them directly from third-party content delivery networks: jsDelivr, for the FFmpeg WebAssembly codec core and some ONNX Runtime files, and Hugging Face, for the AI model files used by tools like stem splitter, voice cloning, text to speech, and speech to text.
Those requests work like loading any other resource on the web: the third-party service sees standard request data such as your IP address and user agent, in line with its own systems for serving files. They never receive your audio file or any text you've typed into a tool, because those requests only ever ask for the model or codec file itself, not your content.
Fonts
Fonts used on Audio Lab are self-hosted rather than loaded from a third-party font service, so loading a page doesn't send a request to an external font provider.
Microphone access
Several tools can record from your microphone — voice cloning, vocal tuner, voice to instrument, speech to text, speech to song, voice changer, soundboard, and noise remover. Your browser only accesses the microphone after you explicitly press record and grant permission when prompted, and any recording is processed and stored the same way as an uploaded file: locally, on your device.
Children's privacy
Audio Lab has no accounts and doesn't ask anyone, including children, for personal information. The only visit data collected is the pseudonymous usage statistics described in the analytics section above. The site isn't directed at children.
Changes to this policy
If this policy changes, we'll update the "Last updated" date at the top of this page to reflect it. Since there are no accounts, we have no way to notify individual users directly, so check back here if you want to know what's changed.
Contact
Questions about this policy, or a privacy concern you'd like to report, can go to the contact address published on this page. For privacy or security reports specifically, start the subject line with "Privacy" or "Security" so it reaches the right place quickly.