Editorial standards

Who writes this

AI Music Detector is an independently operated site. Content is written and maintained by its operator rather than by a rotating pool of contributors, which means one person is accountable for every claim on it. Contact details are on the contact page, including the publisher identity disclosure.

How claims are sourced

• Claims about our own detector are verified against the running code before they are published. A single canonical description of how audio is handled lives in the codebase, and every page that describes processing, privacy or capability is written from it, so pages cannot quietly contradict each other.
• Claims about platform policy — streaming services, distributors, contest rules — are taken from the platform’s own published documentation and dated, because these change frequently.
• Claims about detection science are drawn from published work on synthetic-audio and deepfake-audio detection, and are described at the level of confidence that work supports. Where the field genuinely does not know something, the page says so rather than filling the gap.
• Claims about other products are limited to what those vendors state publicly. We do not publish comparative accuracy numbers for competitors, because we have not measured them.

What we refuse to publish

• An accuracy percentage for our own detector. No controlled evaluation has been completed, so precision, recall and error rates are unmeasured. See accuracy and limitations.
• Generator attribution. The system does not identify Suno, Udio or any other platform, and no page may imply otherwise.
• Forensic framing. A result is an automated estimate of resemblance, not proof of authorship, and never evidence for a copyright, employment or academic decision.
• Invented testimonials, ratings, user counts or credentials. Where a number is not measured, no number is given.
• Claims that the detector runs locally. It does not; the file is uploaded for classification, and the privacy policy describes exactly what that involves.

Review and maintenance

Every page carries a last-updated month. When the detection pipeline changes, the pages that describe it are revised in the same change, and the changelog records what moved. Changelog entries describe behaviour, never accuracy improvements, because an accuracy improvement can only be claimed from a measured benchmark run.

Pages that discuss platform rules or generator capabilities are the most perishable content on the site and are re-checked against source documentation on each revision. If a page looks stale to you, the fastest fix is to tell us which sentence.

Advertising and independence

The site carries advertising to cover the cost of running the detector, which is free and requires no account. Advertising is bought programmatically; advertisers have no input into what is written, no advance sight of it, and no ability to have content changed or removed. We publish no sponsored posts and no paid reviews. Where a page compares tools, the comparison is limited to publicly verifiable facts and states our own product’s limitations in the same terms as everyone else’s.

Corrections

If something here is wrong, we would rather know. Send the page URL and the specific sentence via the contact page. Factual errors are corrected directly, and where a correction changes the meaning of a page the update month is bumped so the change is visible. Requests to remove accurate, sourced information are declined.

Use of AI in producing this site

Drafting assistance is used, as it is almost everywhere now. It does not change accountability: every published page is read and edited by the operator, technical claims are checked against the code or the cited source, and anything that could not be verified is cut rather than softened. The same standard we ask of musicians disclosing AI use applies to us — see the disclosure guidance.