DISTROBOLT

DISTROBOLT ARTIST GUIDES

An uncleared sample is discovered after release: first steps

If potentially uncleared material is discovered after release, preserve the evidence and obtain a qualified review promptly. Do not assume that changing credits, altering a split or deleting the production session resolves the underlying rights question.

Identify the material precisely

Record the released master, affected passage, source recording or work, source files and any permissions already held. Keep the delivery identifiers and actual public links. Use factual wording: a suspected gap in the permission record is not yet a final legal finding of infringement.

Notify the authorised project contacts

Give the release owner and appropriate rights adviser the evidence through a private route. Ask DistroBolt about the supported operational options for the actual release. Do not send admissions, settlement offers or legal demands on behalf of collaborators without authority. Keep any received notice and deadline intact.

Review action against the actual situation

A qualified review may consider clearance, a supported correction, replacement, removal or other measures. None is a universal remedy, and a takedown does not automatically settle historical use or financial claims. Do not upload a slightly altered version to evade detection or represent an unresolved permission as complete.

Keep the outcome traceable

Document decisions, authority, affected territories, approved changes and the treatment of any existing claims. Preserve the original record and subsequent delivery outcome. Update the rights checklist for future projects. This guide does not provide a legal defence, negotiate clearance or promise that any particular distribution action ends liability.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

Continue your release planning

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.