What changed. Spotify announced three things at once, per Spotify Newsroom: support for an industry AI-disclosure standard developed through DDEX, an impersonation policy, and a music spam filter. Disclosure is optional and travels to Spotify through your label or distributor, not through an artist-facing form. Spotify states plainly that this is "not about punishing artists who use AI responsibly or down-ranking tracks for disclosing information", and that the absence of a disclosure does not indicate anything either way. The impersonation rule is stricter: vocal impersonation is permitted only where the impersonated artist has authorised it. From April 2026 the disclosure surfaces to listeners in song credits, populated from what the distributor submitted.
Why it matters. The instinct is to keep quiet, on the theory that admitting AI invites a penalty. The published policy says the opposite, and the real exposure runs the other way: the thing that actually hurts an AI-assisted catalog is a content-mismatch or impersonation flag arriving with no record attached to the release. A disclosure filed through the distributor is that record. It costs nothing and it is the only thing standing between "this artist declared their process" and "this artist got caught".
What to do. Turn it on, and be specific. Set the AI-disclosure field in DistroKid on every release, and where the form allows it, say which element was AI-assisted — vocals, instrumentation, or post-production — because the standard carries separate fields and a blanket yes carries far less signal than an accurate breakdown. Backfill the existing catalog rather than only tagging new releases; a catalog where the last few releases are disclosed and the earlier hundred are silent looks worse than one that is consistent. Then handle the impersonation exposure as a separate job, because it is the part with actual teeth: audit every saved style prompt for a real artist's name and rewrite each one into genre, era, tempo, instrument and vocal descriptors instead. That rule was already in the guide as good practice. What changed is that it now has an enforcement surface attached to it, and a policy with an enforcement surface is a deadline, not advice.
Primary source: Spotify Newsroom