Privacy

Your file never leaves your browser. That is not a policy choice we could quietly reverse — it is how the tool is built.

What happens to your file

When you pick an audio or video file, your browser reads it locally, takes a 30 second excerpt, and runs the noise removal on your own device. The file is never sent to us. There is no upload step to opt out of, because there is no upload step.

The cleaned preview you download is also produced on your device. It does not pass through our servers on the way to your downloads folder.

Closing the tab discards everything. We have no copy to delete, because we never had one.

What we do receive

To use the tool your browser downloads this page and, once you pick a file, a noise removal engine of about 9 MB. Serving those files produces ordinary web server logs at our host, Cloudflare: the time of the request, which file was requested, your IP address, and your browser's user agent string. Cloudflare retains these for a limited period for security and troubleshooting.

Those logs tell us that someone loaded the tool. They cannot tell us what you cleaned, because your audio is never part of the request.

No accounts, no cookies, no analytics

There is no sign up and no account. We set no cookies, and we store nothing in your browser's local storage. There is no analytics script, no tag manager, no advertising pixel, and no third-party embed of any kind — the site loads no code from anyone else's domain.

One consequence worth stating plainly: we cannot tell how many people use this, or which features they use. That is a cost we accept for the above being true.

Your audio is not used for training

No model is trained here. The engine is a fixed, already-trained model that runs unchanged on your device and learns nothing from what you feed it. Since your audio never reaches us, we could not use it for training even if we wanted to.

What is not built yet

Today the tool does one thing: a free 30 second preview, processed locally. Cleaning a complete file, and paying for it, do not exist yet.

If we add paid full-file processing, it may require sending your file to a server. That would be a real change to everything above, so we will update this page before such a feature ships — not after — and it will be obvious in the interface which mode you are using.

Changes to this page

If we change how any of this works, we will change this page and update the date at the top.

Contact

Questions about this page: support@quiettake.com.