Last updated August 12, 2026

Privacy Policy

aimusicdetect.com processes the minimum data needed to provide an AI music detection result. This policy describes the current beta service.

Audio files

Audio you upload is used to perform the detection you requested. The current production workflow sends the audio to ACRCloud for analysis. We do not use submitted audio to train our own models.

Temporary storage and deletion

Files are uploaded to a temporary, hard-to-guess public Vercel Blob URL so the detection service can retrieve them. Our application attempts to delete that temporary Blob immediately after detection succeeds or fails. Deletion is best-effort, so service failures may delay cleanup.

ACRCloud's own processing and retention terms apply while it handles the file. We may cache the derived detection result for up to 24 hours to avoid charging twice for the same file. The cache expires after 24 hours, uses a server-keyed audio fingerprint, and stores result metadata without the submitted filename, not another copy of the audio.

Technical data and analytics

Hosting infrastructure may process IP addresses, request timestamps, device information, and error logs for security and reliability. With your consent, we use Google Analytics 4 to measure visits and whether a detector request starts, succeeds, or fails, and whether checkout or license activation succeeds. These events do not include order IDs, license keys, customer IDs, or card data. Google may process device and usage information and set analytics storage under its terms.

Purchases and license keys

Creem processes checkout, payment, tax, receipt, and customer details under its own privacy terms. We receive purchase events and store the order reference, product, remaining credit balance, and a keyed hash of the license key. We do not store the full license key or payment-card details. A signed browser cookie keeps an activated credit balance connected to your browser.

Cloudflare Turnstile processes browser and network signals to prevent automated abuse. Daily limits use keyed hashes of the network address and a signed random device identifier; the daily counters expire after the UTC day ends.

We keep advertising storage and personalization disabled. We do not send uploaded audio, filenames, probability scores, verdicts, likely-source labels, or error messages to Google Analytics. You can decline analytics in the consent notice. We do not sell personal data.

Your responsibility

Submit only audio you own or are authorized to process. Do not submit confidential recordings or personal information that is not needed for the detection.

Contact

For privacy questions or deletion concerns, email support@aimusicdetect.com or use our contact page.