Primary principle
Be explicit
If AI contributed, say so with concise, audience-facing language.
Guide
Disclose AI music in a way listeners can trust
Fans respond to clear and consistent notes. This guide keeps your AI messaging practical, fair, and easy to maintain across singles, EPs, and larger campaigns.
Release-level clarityPolicy alignmentTrust-first languageReusable templates
Primary benefit
Lower confusion
Clear notes reduce support questions and refund pressure after release.
Primary check
Consistency across catalog
Use the same wording structure for similar flow patterns.
Decide the boundary
Define what to disclose before drafting
Not every flow uses AI at the same depth. Decide your boundary by release type.
Keep wording tied to exactly what happened, without over-qualifying every track.
Write it plainly
Use one sentence, then optional detail
Your first sentence should answer the listener’s direct question: how much AI was used and where.
Add one extra line only if it changes buyer decisions.
Keep credits coherent
Align metadata and credits so there is one source of truth
If credits and disclosure disagree, trust declines quickly.
Use one phrasing pattern for credits and policy notes so updates remain fast.
Handle questions safely
Turn policy questions into transparent follow-up
When fans ask, point to the same policy language you already used in the release.
Avoid changing disclosure wording across pages after publishing unless you also update support references.
Trust is built in your release language
Clear disclosure is not marketing garnish. It is release quality check, and it compounds across every drop.