AI Music Detector / Reference
Privacy policy
In plain terms: the track you upload travels over an encrypted connection to a specialist third-party detection service for classification, and we never keep a copy of the audio itself.
Last updated 25 October 2026
This policy has not yet been reviewed by a qualified lawyer in every jurisdiction where the site is available. It describes the intended handling of information on this site, not legal review or regulatory certification.
Who is responsible
The operator of aimusicdetector.com is the data controller for this website. Contact: privacy@aimusicdetector.com. Full contact routes are on the contact page.
Your audio files
When you run an analysis, the complete file you selected is uploaded over an encrypted (HTTPS) connection to our server. It is not analysed inside your browser. Our server immediately forwards the audio to a specialist third-party AI music detection service, which performs the classification and returns a result.
The audio exists on our side only in memory, for the duration of that single request. We do not write it to disk, to object storage or to a database, we do not keep a copy after the result is returned, and we do not use your music to train anything. There is no account, no upload history and no shareable result link. Usage and cache records are described below; the absence of an account does not make these records necessarily anonymous.
Our server sends the audio to Modulate for classification, together with its media type and a sanitised filename. Sanitisation removes path components and restricts characters; a filename can still contain identifying information. Provider-side handling, retention and contractual safeguards require separate confirmation. Treat submission of confidential or unreleased material as a disclosure to that service.
What we keep after an analysis
- The result. The verdict, probabilities, confidence band and per-window values can be reused for 14 days, keyed by a SHA-256 hash of the file, so that an identical repeat upload can reuse the earlier result instead of being sent for analysis again. This reuse window is not a verified deletion deadline for database records or backups. The hash is not an audio copy.
- A rate-limiting fingerprint. A salted one-way hash of your network address, used to enforce a fair-use limit of 12 analyses per 24 hours. The address itself is not stored.
- The analysed duration of each request, for capacity reporting.
The application database does not intentionally store audio or filenames. Usage records contain an IP-derived fingerprint and duration; cached results contain a file-content-derived key. Sanitised filenames may appear in provider failure logs. These records are not necessarily anonymous. Files are limited to 25 MB and recordings between 5 seconds and 15 minutes.
Information we do process
- Server logs. Our hosting provider records standard request data — IP address, user agent, requested path, timestamp — for security and reliability. These logs are retained for a short operational period and are not used to build profiles.
- Local storage. Your light/dark theme choice is stored in your browser only. It never reaches us.
- Analytics. If privacy-configured analytics are enabled, they record aggregate page views and anonymous tool events (for example that an analysis started or finished). They never receive file names, file contents, file paths or result data linked to an identity.
- Email. If you write to us, we hold your message and address for as long as needed to handle the enquiry.
Legal basis
Where the GDPR applies: legitimate interests for security logging and site operation; your consent for any advertising or non-essential analytics storage; and contract or legitimate interests for handling correspondence you initiate.
Advertising and cookies
Google AdSense advertising technology is used on this website. The official AdSense tag is installed on every page as part of the site’s advertising integration and Google’s verification of the site. No display ad units have been placed in the site’s code yet, so the presence of this technology does not mean that a display advertisement appears on any given page. Whether an advertisement is ever shown depends on the site’s advertising configuration, page eligibility, your consent choices, geographic requirements and Google’s systems.
Google and its advertising partners may use cookies, device identifiers, IP addresses and similar technologies for purposes including ad delivery, measurement, frequency control, fraud prevention, security and — where permitted and consented to — advertising personalisation. Google acts as an independent controller for the data it collects in that way. Advertising may be personalised, non-personalised or limited depending on applicable requirements, your choices and Google’s configuration; not every visitor receives personalised advertising.
Advertising storage and personalisation are subject to applicable consent requirements, including in the EEA, UK and Switzerland. Regional consent, rejection and withdrawal behavior have not yet been verified. Google settings do not replace a site consent mechanism. You can review Google’s own controls at My Ad Center and read how Google uses data from partner sites at policies.google.com/technologies/partner-sites. Details are in the cookie policy.
Our application does not intentionally send uploaded audio, filenames or detection results to Google for advertising. Third-party advertising scripts run on the page; their handling is described in Google's policies. Analysis does not require advertising consent.
Manual advertising placements must remain outside uploads, analysis controls and results. No manual ad unit IDs are configured in the site code. Account-controlled Auto ads are independent and their placement settings require verification.
Subprocessors and international transfers
Two categories of processor are involved. Our hosting and CDN provider serves the site and runs the server that receives your upload; the third-party AI music detection service performs the classification itself. Processing locations and any required transfer safeguards need operator confirmation. Our database provider stores the cached result, the salted rate-limit hash and the analysed duration described above.
Security
The site and every upload are served over HTTPS only. Audio is held in memory for a single request and never written to storage by us, which limits exposure: there is no archive of user audio to breach, because none is kept.
Your rights
Depending on where you live, you may have rights of access, rectification, erasure, restriction, objection and portability, plus the right to complain to your supervisory authority. Write to privacy@aimusicdetector.com and we will respond within one month. Relevant records may include server logs, usage fingerprints, cached results and correspondence; identification and retention need case-by-case review.
Children
This site is not directed at children under 13 and we do not knowingly collect their personal data.
Changes
Material changes will be reflected in the “last updated” date above, and any change that affects how audio is handled will be announced on the site before it takes effect.