Trackstack Music Limited · Last updated: 1 October 2026
1.1 Trackstack is built for professional artists, labels and studios, and the people reviewing music on the Trackstack platform (the Platform) need to trust that what they receive was made by artists. Fully AI-generated tracks can't be sent on Trackstack.
1.2 This policy explains how our AI Track Detection works, who we use to provide it, what happens when a track is detected as fully AI-generated, and how you can appeal a detection you believe is wrong. It forms part of, and should be read with, our Terms of Service and our Privacy Notice.
1.3 AI Track Detection is being rolled out progressively, so some of what is described here may not yet apply to every workspace or inbox.
2.1 We use ACRCloud, a specialist audio recognition company, as our provider for AI music detection. ACRCloud analyses a track's audio and reports whether it reads as AI-generated, how confident it is, and, where it can tell, which AI music generator the track most likely came from.
2.2 ACRCloud is used only for AI music detection under this policy. It does not decide what happens to your track — the rules in section 4 are applied by Trackstack.
2.3 How your audio is shared. When a track is scanned, we give ACRCloud a private, time-limited link (valid for one hour) to the audio file so it can fetch and analyse it. Once ACRCloud has returned its result, we delete the file from ACRCloud's scanning workspace. We keep the result on our side so that we can apply this policy, handle appeals and improve the accuracy of our checks. We process this data in accordance with our Privacy Notice.
3.1 Every track uploaded to Trackstack is checked automatically after upload, in the background. You don't need to do anything, and it does not slow down your upload.
3.2 We check each unique audio file once. If you upload exactly the same audio again, we reuse the earlier result rather than scanning it a second time.
3.3 Analysis usually completes within a few minutes. While a track is still being analysed, it may show as “Analysing…” to the people reviewing it. If you send a track before its analysis has finished, the policy is applied as soon as the result comes in (see section 5.3).
4.1 How the audio is analysed. ACRCloud separates each track into its vocals and its instrumental (accompaniment), and analyses each part as well as the full mix. Each part gets a prediction (AI-generated, human, or no vocals) and a probability that it is AI-generated.
4.2 From these predictions, the track is given one of four results:
4.3 When we act. We only take action when a track is classified as fully generated AND the detection is at least 90% confident that it is AI-generated. We set this high bar deliberately, to keep the chance of a wrong decision about a human-made track as low as possible.
4.4 When we don't act. Tracks classified as AI vocals or AI instrumental, and fully generated results below the 90% confidence threshold, are treated as not AI-generated everywhere on the Platform: they are not labelled, not blocked and not cancelled. You can use AI tools as part of your creative process; this policy is about tracks that are generated by AI in their entirety.
5.1 The track is labelled. The track shows an “AI Generated” label in your uploads and library.
5.2 The track can't be sent. You won't be able to select the track when sending music, and the Send option for it is disabled. If a send is attempted anyway (including through a public submission form), it is rejected with the message: “AI-generated tracks can't be sent on Trackstack. To appeal, contact support@trackstack.app.”
5.3 Pending submissions are cancelled. If the track has already been sent and is still waiting to be reviewed, it is automatically cancelled from every inbox it was sent to, and removed from that inbox's review queue. Tracks that have already been reviewed are not affected. The rest of your submission is unaffected and stays with the label; if the AI-generated track was the only track left in a submission, the whole submission is cancelled.
5.4 You are notified by email. We email you to tell you which tracks were removed and from which submissions. Because it concerns your submissions directly, we send this email even if you have turned off other cancellation emails. The cancelled track is marked “Cancelled: AI generated” on your submission, both in the Sent area of Trackstack and on the public submission page, with an Appeal link next to it.
5.5 What receivers see. Labels and other inboxes reviewing music may see an “AI Generated” label on a track in their pending queue, together with the detection result (for example the confidence and the likely AI generator).
5.6 What doesn't happen. A detection does not delete your track or its audio file, and it does not on its own suspend or restrict your account or your other tracks.
6.1 Automated detection is not perfect. If you believe your track was wrongly detected as fully AI-generated, you can appeal. Appeals are free.
6.2 Every appeal is reviewed by a member of the Trackstack team — not by the automated system. We look at the detection result together with the information you give us about how the track was made.
6.3 We will reply by email with the outcome, and with the next steps for your track if we agree the detection was wrong. We do not commit to a fixed timeframe but aim to respond promptly.
6.4 Please only appeal where you genuinely believe the detection is wrong. Knowingly giving us false information about how a track was made is a breach of our Terms of Service.
7.1 From your submission (recommended). Open the submission containing the cancelled track — in Trackstack, go to Sent and open the submission, or use the “View your submission” button in the email we sent you. Next to the track marked “Cancelled: AI generated”, select Appeal.
7.2 This opens an email to support@trackstack.app that is already filled in with what we need to find the track: the track title, the inbox it was sent to, the submission ID, the submission track ID and the date it was cancelled. Please keep these details as they are.
7.3 Tell us how the track was made. At the end of the email, describe how you made the track — for example the DAW, instruments, samples and any AI tools you used, and what for. The more detail you give, the faster we can review it. You may also include supporting material such as project files, stems or session screenshots, or links to them.
7.4 By email. If you can't use the Appeal link — for example because the track was blocked before you sent it — email support@trackstack.app with the subject “AI detection appeal: [track title]”, including the track title, the email address of your Trackstack account, and the information described in section 7.3.
8.1 We continue to improve our AI Track Detection and may update this policy from time to time, including the provider we use and the threshold at which we act. The current version is the one published on the Platform, and the date above shows when it was last updated.
9.1 Questions about this policy and appeals can be sent to support@trackstack.app.