Privacy Policy
Last updated June 1, 2026
Most privacy policies are a long way of saying "trust us with your data." This one is different, because AudioDock is built so that we never receive your data in the first place.
When you use a tool on AudioDock, your audio is opened, processed, and saved back to you entirely inside your own browser. It is never uploaded, streamed, or copied to a server we control. That is not a promise about how carefully we handle your files — it is a description of an architecture in which your files never reach us at all.
The short version
We do not collect, receive, store, or transmit your audio. We do not require an account. We do not sell data, because we do not have data to sell. The handful of things we do collect — anonymous page views and the preferences you choose — are described plainly below, and you can switch most of them off or wipe them in one click.
What "local-first" actually means
AudioDock loads its code into your browser once, the way any website does. From that point on, the work happens on your device. When you drop in a file, the browser's File API hands the raw bytes to JavaScript running in your tab. The Web Audio API does the editing, and for codec conversions a copy of ffmpeg compiled to WebAssembly runs the encode — again, in your tab.
You do not have to take our word for it. Open your browser's developer tools, switch to the Network tab, and process a file. You will not see your audio being sent anywhere, because it is not. This verifiability is the whole point: privacy you can check beats privacy you are asked to believe.
Information we do not collect
We do not collect your audio files, their contents, their filenames, their metadata, or any derivative of them. We do not build a profile of you. We do not fingerprint your device to track you across the web. We do not ask for your name, email, or payment details to use the free tools, because none of that is necessary to run software on your own machine.
Information we may collect
To keep the site running and improve it, we may record aggregate, anonymous usage signals such as which pages are viewed and roughly how often. Where this is done, it is configured to avoid identifying individual users — no audio, no file data, and no attempt to single you out. If we ever introduce error reporting, it will capture technical diagnostics about the application, never the contents of your files.
Data stored on your own device
AudioDock can store small preferences in your browser's local storage — for example, whether you have opted into a local activity log on the Workspace page. This information lives on your device, under your control, and is never sent to us. It is not your audio; it is a short list of settings and, if you enable it, the names of tools you have run.
You can erase all of it at any moment. The Workspace page has a one-click "Clear local data" control, and clearing your browser's site data for AudioDock does the same thing.
Third-party services
The hosted version of AudioDock loads two things from third-party content-delivery networks: web fonts, and the ffmpeg.wasm module used by the codec tools. These requests fetch static assets and are subject to the providers' own logging of basic request metadata, such as IP address, as is normal for any asset served over the web. They never carry your audio. If you would rather avoid them entirely, the project can be self-hosted with the fonts and the ffmpeg core bundled locally.
Children's privacy
AudioDock is a general-purpose utility and is not directed at children. Because we do not collect personal information or require accounts, we do not knowingly gather data from anyone, including children.
Changes to this policy
If we change how AudioDock handles information, we will update this page and revise the date above. Material changes to the local-first model — the core of everything here — would be significant enough that we would call them out clearly rather than bury them in an update.
Contact
Questions about privacy are welcome. Reach us through the Contact page and we will respond as quickly as we can.