What this means
When you submit a release, our system automatically scans song titles, lyrics, and audio for signals that may indicate explicit content. In some cases this scan flags a track as Explicit even though you did not choose that label yourself. This is a known edge case, not a system glitch, and the team can correct it.
Common reasons the Explicit tag is applied automatically
- The song title or lyrics triggered a keyword match. Certain words cause the scanner to add the tag as a precaution, even if the context is not explicit.
- A previous version of the same song was marked Explicit. If you re-submitted a release that was once flagged, the tag can carry over.
- Audio analysis detected content the scanner considered explicit. This can happen with spoken-word sections, outro skits, or samples.
How to get the tag corrected
- If the release is still Under Review or in Changes Requested, open a support ticket and state that the Explicit tag was applied incorrectly. Include the release title, your artist name, and a short explanation of why the content is not explicit (for example: "This is a gospel track with no profanity or mature language").
- If the release is already live on streaming platforms, open a support ticket with the same information. The team will request a metadata correction from the affected platforms. Note that platform processing time varies and changes can take 2 to 5 business days to appear.
What the team needs from you
- Release title
- Artist name
- A brief statement confirming the content is not explicit
- Optional: lyrics or timestamp of the section you believe triggered the flag
What happens next
Once the team confirms the content is not explicit, the Explicit label is removed from your dashboard and a metadata update is sent to all affected platforms. This correction is free and does not affect your release date or delivery status.
Note on deliberate explicit content
If your track genuinely contains profanity, graphic language, or mature themes, the Explicit label is required by platform rules. Removing it from non-explicit tracks is the team's priority, but applying it correctly on tracks that need it protects your distribution.