Why this needs to be declared
Stores and platforms increasingly require transparency about whether a track was created using AI tools, for a mix of legal, policy, and listener-trust reasons. Accurately declaring this up front avoids a release being flagged or pulled later for non-disclosure, which is a worse outcome than declaring it correctly from the start.
What counts as AI-generated
This generally applies to tracks where AI tools were used to generate substantial elements of the composition, vocals, or production — not simply using standard AI-assisted mixing/mastering tools or minor AI-based effects on an otherwise human-performed and human-written track. If you're unsure whether your specific use of AI tools crosses that line, err on the side of declaring it, or ask support before submitting.
How to declare it
During upload, mark the release as AI-generated in the release form. Depending on the extent of AI involvement, you may be asked to provide supporting documentation about the tools and process used — this helps us and downstream stores handle the release correctly under their own AI content policies, which vary by platform and continue to evolve.
What happens after declaring
An accurately declared AI-generated release is still distributed normally to your selected stores — declaring it is about correct disclosure and compliance with each platform's policies, not an automatic barrier to distribution. Some individual stores may have their own additional restrictions on AI-generated content that apply regardless of DistroVibe's own policy; these are set by each platform, not by us.
If you're not sure whether this applies to your release
When in doubt, disclose. Under-declaring carries real downstream risk (a release getting pulled after the fact for non-disclosure); there's no meaningful downside to accurately flagging AI involvement upfront.