The audio you process never leaves your device. All six tools download what they need into your browser and run it there, so there is no upload step, no server-side processing and no copy of your file anywhere but your own machine. You can verify this yourself: open your browser's network tab before you start, and watch that nothing goes out.
The site does use Google Analytics and Yandex Metrica to count visits, shows advertising through Google AdSense, and its host keeps standard access logs. Those are the three places any data about you is collected, and all three are described below. None of them ever sees your audio — ads are chosen from the page you are on, never from the file you are working on, because the file never leaves your machine.
If you visit from the European Economic Area, the United Kingdom or Switzerland, analytics and advertising cookies are not set until you agree in the consent message, and you can change that choice at any time (section 5).
1. The audio and text you process
It is never transmitted. The vocal remover, the noise reducer, the audio converter, the voice changer, AI Speech to Text and the text-to-speech tool all work by fetching what they need to your browser and running it locally, on your own processor. Your file is read by the page, processed locally in memory or temporary browser storage, and handed back to you as a download. There is no endpoint it could be sent to.
This is a property of how the tools are built, not a promise about how we behave with data we receive. We do not receive it.
AI Speech to Text processes audio and transcripts locally. It caches verified model files in browser storage for later visits; audio and transcripts are not uploaded.
Microphone and voice samples
The tools can record from your microphone instead of taking a file, and the voice changer and the text-to-speech tool can use a short sample of a voice. Recording only starts after your browser asks you and you agree, and a recording or voice sample is treated exactly like any other file: processed locally, never transmitted. We never request microphone access on page load, only when you press record.
2. What is collected
Google Analytics
The site uses Google Analytics 4. With your consent (or, outside the
EEA, the UK and Switzerland, by default) it records, for each visit: the
pages you view, when, the referring page or search that brought you, and
information your browser reports such as approximate location derived from
your IP address, device type, screen size, operating system and browser
version. It sets cookies in your browser (names beginning _ga)
to recognise a returning visit. The tools also report a few coarse events,
such as that a conversion finished and roughly how long it took, in bands
rather than exact values — never a file name, file content or anything
derived from it.
Where consent is required and you have not given it, Google Analytics runs in Google's Consent Mode: it sets no cookies and sends only cookieless signals without a visitor identifier.
This is used to see which pages and tools are used, nothing more. We do not upload customer lists and we do not set user identifiers. See Google's privacy policy and how Google Analytics uses data.
To opt out: decline or withdraw consent
(section 5), use Google's
opt-out
browser add-on, or block googletagmanager.com with any
content blocker. Every tool on this site works normally with analytics
blocked — nothing here depends on it.
Yandex Metrica
Not loaded at all if you visit from the EEA, the UK or
Switzerland — the site removes it before the page reaches
you. Elsewhere, and on every page except the text-to-speech tool, the site
also uses Yandex Metrica to count visits. It records the same kind of
information as Google Analytics — pages viewed, the referring page,
approximate location from your IP address, device and browser details
— plus clicks and which links are followed, and it sets cookies whose
names begin _ym. Its session-recording feature (Webvisor) is
switched off, so it does not record what you type or what appears on the
page. See
Yandex's
privacy policy and
how
to opt out of Yandex Metrica.
Google AdSense
The site shows ads through Google AdSense on every page except the text-to-speech tool. Google and its partners use cookies and similar identifiers to serve these ads, including, where you allow it, ads based on your previous visits to this and other websites. In the EEA, the UK and Switzerland they do so only with your consent; if you decline, Google may still show non-personalised or limited ads, which are chosen from the page rather than from you. You can also turn off personalised ads in My Ad Center; see how Google uses information from sites that use its services.
Hosting logs
The site is served by Cloudflare Pages. Like every web host, it records requests: IP address, timestamp, the URL requested, response status and user-agent string. These logs exist to serve the site and to defend it from abuse and denial-of-service traffic. We do not use them to build any profile of a visitor. The same request is also used, without being stored by us, to pick the language version of the page from the country it comes from. See Cloudflare's privacy policy.
If you write to us
The contact address on this site is an email address. If you email it, we receive whatever you send — your address, your message and anything you attach — and keep it only as long as needed to answer you. That mailbox is hosted by Microsoft (Outlook.com), which processes the mail in transit and at rest. See Microsoft's privacy statement. There is no contact form, no newsletter, and no mailing list: we have no way to email you unless you email us first.
3. What is not collected
- No account, so no name, password or profile.
- No payment details — the tools are free and there is nothing to pay for.
- No mailing list and no marketing email.
- No tracking pixel of our own. The advertising cookies described in section 2 are Google's, set through its ad frames; we neither read them nor receive what is in them.
- We do not receive a copy of your audio, your text, your voice sample or your results.
4. Cookies and storage on your device
Everything the site or its providers keep in your browser:
| What | Set by | Purpose | Consent |
|---|---|---|---|
Analytics cookies (_ga, _ga_*) | Google Analytics | Distinguishing visits and returning visitors; up to 2 years | Required in the EEA, UK and Switzerland |
Yandex Metrica cookies (_ym_*) | Yandex | Distinguishing visits and returning visitors; up to 1 year | Not loaded in the EEA, UK and Switzerland |
| Advertising cookies and identifiers | Google AdSense and its partners | Serving ads, capping repeats, measuring views, and personalising where permitted | Required in the EEA, UK and Switzerland |
| Consent record | Google's consent message | Remembering the choice you made in it | Not required: it stores your choice |
Language cookie (af_lang) | This site | Set only when you pick a language in the menu, so you are not redirected by country again; 1 year | Not required: set at your request |
| Model files (IndexedDB and Cache Storage) | This site | Holding the downloaded models and engines so they are not fetched on every visit | Not required: needed to run the tool you asked for |
| Temporary workbench audio (IndexedDB) | This site | Keeping large input and stage results on your device instead of retaining all audio in memory. Unreferenced data is deleted; closing-page cleanup is best effort, with expired interrupted sessions removed on a later visit after 24 hours. | Used locally to run the workbench you requested |
| Tool settings and speed estimate (local storage) | This site | Remembering the settings you chose and how fast this device processed the last file, so the progress bar is accurate | Not required: stays on your device |
Workbench audio can be stored temporarily in this browser. Clearing processing results keeps source audio and undo history; those references are removed when no longer needed. Saved workbench settings may also contain text entered into speech synthesis modules. Audio and text are not sent to us. AI model caches are separate from temporary audio. You can delete all local data at any time by clearing site data for audiofilter.net in browser settings. Model files may then need to be downloaded again.
The advertising cookies are set by Google and its partners, not by this site, so the exact names vary by region and by which partners are in the auction. Google documents them under cookies used in advertising. None of them is readable by this site.
Embedded video. One article carries a walkthrough video.
The page shows a still image served from this site and contacts YouTube only
when you press play — until then no request leaves for youtube.com and
no cookie of theirs is set. Pressing play loads the player from
youtube-nocookie.com, which withholds cookies until playback
begins; from that point YouTube applies its own privacy policy, not this one.
Not pressing play is a complete opt-out, which is why the video is a still
image rather than a live player.
Embedded posts. The vocal remover, noise reducer and text-to-speech pages offer video demonstrations from our X account. They show a preview image served from this site. Only choosing to watch loads X's embedded player; before that, the video component makes no request to X. The karaoke article also links to a demonstration on X. Watching an embedded video or opening its X link may let X process data and use cookies or storage under its own privacy policy, not this one. If the embedded player is unavailable, the direct link remains available.
5. Legal basis and consent
Under the GDPR and the UK GDPR, each use of personal data needs a legal basis. These are ours:
| Processing | Legal basis |
|---|---|
| Analytics cookies and measurement | Your consent (Art. 6(1)(a) GDPR) |
| Advertising cookies and personalised ads | Your consent (Art. 6(1)(a) GDPR) |
| Hosting logs and security | Our legitimate interest in running the site and protecting it from abuse (Art. 6(1)(f) GDPR) |
| Answering your email | Our legitimate interest in replying to you, or steps you asked for (Art. 6(1)(b) and (f) GDPR) |
| Storage on your device listed as not requiring consent | Strictly necessary for a service you requested |
In the EEA, the UK and Switzerland, Google's consent message appears on your first visit. Declining is as easy as accepting, and every tool works the same either way. You can withdraw or change your consent at any time, with the same effect as never having given it for anything that happens afterwards:
We do not use your data for decisions that are made solely by automated means and have legal or similarly significant effects on you. Personalised advertising is a form of profiling carried out by Google, and only with your consent where that is required.
6. Recipients, transfers and retention
The providers above act for us, or alongside us, in processing this data: Google (analytics and advertising), Cloudflare (hosting), Microsoft (email) and, outside the EEA, the UK and Switzerland only, Yandex (analytics). Google, Cloudflare and Microsoft may process data outside the EEA and the UK, including in the United States. All three are certified under the EU–US Data Privacy Framework and its UK and Swiss extensions, and they also rely on the European Commission's standard contractual clauses.
- Analytics: event-level data is kept for 14 months and then deleted automatically.
- Yandex Metrica: kept by Yandex under its own retention rules; see its privacy policy.
- Advertising: kept by Google under its own retention rules; see its privacy policy.
- Hosting logs: kept by Cloudflare only as long as needed for delivery and security, under its privacy policy.
- Email: kept as long as the conversation needs it, and deleted within 12 months of the last message.
7. Your rights
If you are in the EEA, the UK or Switzerland — and in many other places too — you have the right to:
- access the personal data held about you, and get a copy of it;
- have it corrected if it is wrong, or erased;
- restrict or object to its processing, including processing based on legitimate interests;
- data portability, for data you provided to us;
- withdraw consent at any time (section 5);
- complain to a supervisory authority, in particular in the country where you live or work — in the EU, see the list of national authorities; in the UK, the ICO; in Switzerland, the FDPIC.
Because there is no account and no stored personal record, most requests have a simple answer: we hold little about you that we could look up. The analytics data is held by Google under pseudonymous identifiers and access logs by the host; neither is linked to your name. Write to the contact address and we will answer within one month. What you can do directly, without asking us:
- Stop analytics and ad cookies — decline in the consent message, change your choice above, or block them.
- Delete everything stored locally — clear site data for audiofilter.net.
8. Children
The tools are not directed at children under 13, or under 16 in the EEA, and we knowingly collect nothing from them. Since there is no signup, there is nothing for a child to submit.
9. Changes
If what the site collects ever changes — a different analytics tool, a new kind of advertising, or anything that moves processing off your device — this page will be updated before the change goes live, and the date at the top will change with it. When advertising was added on 22 September 2026, this page was updated first. A change of that kind is a change to the product, not a quiet edit to a policy.
10. Who is responsible, and contact
The controller responsible for the processing described here is the operator of audiofilter.net. Questions about this policy, requests about your data, or anything else the site does with data: audiofilternet@outlook.com.