Privacy Policy

Privacy Policy & Audio Handling

Last updated: 2026-11-22. This policy states exactly where uploaded audio travels, when it is deleted, how to remove a report immediately, and what infrastructure we use.

Uploaded audio is deleted immediately after screening

When you upload an audio file (MP3, WAV, FLAC, M4A, or MP4 up to 50 MB), the file is placed in a private transient Cloudflare R2 storage prefix (tmp/) only for the duration of the scan. Immediately after scoring finishes — whether the scan succeeds or fails — the transient object is deleted. A 1-hour bucket lifecycle rule acts as an automatic fallback for interrupted jobs.

AIS Music Detector does not keep a library of uploaded songs and does not use your uploaded audio to train internal models. Local playback during your active session uses your browser's in-memory object URL; we never stream uploaded audio back from our servers or expose audio on shared report pages.

Anonymous structured reports (30-day retention & instant delete)

Completed checks generate a shareable report at /r/<reportId> using a random unguessable ID. Reports store only structured screening metadata (verdict tier, probability, confidence, 10-second segment scores, model version, date, and a sanitized filename or short hash). Reports contain no audio, default to hiding artist names and cover art, output noindex, follow, and are automatically deleted after 30 days.

Delete immediately from the result screen: You do not have to wait 30 days. The browser session that created a report can click Delete report directly on the result screen to mark the report removed immediately and clear it from local history.

Local browser storage, cookies, and free daily quota

  • Local browser history: Your last 5 checks are saved only in your browser's localStorage so you can reopen recent report links without an account. Clearing your browser storage removes this list immediately.
  • Daily quota without sign-up: To enforce the 3-check daily limit and prevent abuse, we store a daily salted cryptographic hash (HMAC-SHA256) derived from request metadata and purge quota rows after 7 days.
  • No tracking ad cookies at launch: We do not set cross-site advertising cookies during M1. If advertising or analytics cookies are ever added in a future release, this policy and a consent notice will be updated first.
  • Non-PII product signals: Aggregate feature-interest clicks (such as Appeal Kit or Batch Screening interest) record only daily page totals with no email addresses or personal identifiers.

Infrastructure and detection provider disclosures

  • Cloudflare (Workers, D1, R2, Turnstile): Hosts web pages, transient audio transfer, rate-limiting hashes, and 30-day structured report storage.
  • External detection engine providers: Before live user audio is routed to any commercial third-party detection API, we require written confirmation of its retention period and model-training policy and publish the exact active provider name and verified terms on this page. We do not publish third-party “never used for training” claims unless backed by written provider confirmation.

Privacy requests & contact

To request immediate removal of a shared report or ask questions about data handling, contact support@aismusicdetector.com.