Transparency report

What happens to a file you analyse

The file is read by the browser, decoded with the Web Audio API and measured locally. No upload request carries the audio. When the analysis finishes, the temporary object URL is revoked and the decoded buffer is released. Closing or reloading the page destroys the result, which is also why there is no shareable result link anywhere on this site.

What data exists at all

• No audio. Not during analysis, not after, not in a queue, not in a cache.
• No results. Scores are React state in your tab, never a database row.
• No accounts. There is no signup, so there is no email list, no password hash and no profile.
• Standard web serving. The host processes ordinary request data such as IP address and user agent to deliver pages and resist abuse.
• Advertising. Ad slots, when served, are provided by Google and can set cookies or read device identifiers under Google’s own terms. See the cookie policy.

Government and legal requests received

As of August 2026: zero requests for user data from any government, law enforcement agency, rights holder or private party. If a request arrived, the honest response would be that there is no user audio, no result history and no account data to produce. This line is reviewed whenever this page is updated.

Takedown and correction requests

As of August 2026: zero takedown requests. Corrections to published technical content are handled openly — if a claim on this site is wrong, the page is edited and, when the change affects a factual claim, the changelog records it.

What we would refuse

• Building an audio retention pipeline in order to train on user uploads.
• Selling or brokering analysis results, since producing them would require collecting something that is currently never collected.
• Issuing a certificate, verdict or attestation that a specific track is AI-generated. The tool produces an estimate; see limitations.
• Publishing an accuracy percentage before a benchmark run exists to support it.

How to verify these claims yourself

1. Open your browser developer tools and select the Network tab.
2. Analyse a track on the detector.
3. Filter by request type. You will see page, script and ad requests, and no request whose payload contains your audio file.
4. Reload the page. The result is gone, because it was never stored anywhere but the tab.

Related pages

• Privacy policy — the formal version of this report.
• Methodology — what is measured locally.
• Benchmark — the evaluation protocol, with unmeasured cells left null.