Taking a release down

A live release can be pulled from the stores from its own page in the workspace. The request goes out to every store the release was delivered to, and each one confirms the removal separately.

Treat it as permanent. There is no button that puts a taken-down release back on the stores, so it is worth being sure before you confirm.

Requesting one

1. Open the release from your releases. The action appears while the release is Live.
2. Choose Request takedown and confirm.
3. The release moves to Takedown requested and you get an email confirming it is underway.
4. We pass the request to the stores. As each one confirms, its line in the Store availability list changes to Removed.
5. The release reads Taken down as soon as removals start confirming, and an email says so. The remaining store lines keep filling in afterwards, which is why a store can still show the release for a while after that.

Asking twice changes nothing: a repeated request is the same request.

It is not instant

Removal usually completes within a few days, store by store, because each store processes it on its own schedule in the same way it processed the delivery. Some platforms also keep cached pages for a short while after they have removed the release, so a page that is still reachable straight after the confirmation is normal rather than a failed takedown.

If a store still has the release well after the release reads Taken down, open a support request and name the store.

What a takedown does not do

• It does not delete the release from Run. The release, its tracks and its history stay in your account so the record and the reporting still make sense.
• It does not erase earnings from the time it was live. Streams that happened before the removal are still reported to us afterwards, and they still show up in your earnings for those periods, arriving on the usual reporting delay. See how earnings work.
• It does not give back a release from your plan allowance. The allowance is counted when a release is first submitted.
• It does not touch your subscription. Billing is separate, and cancelling a plan is a different action in Settings.
• It cannot be reversed. Taken down is the end of that release. Putting the music out again means creating a new release, which needs its own barcode. The recordings can keep the ISRCs they already have, and a reviewer confirms that they really are the same recordings.

Before a release is live

Takedown is for releases that already reached the stores. Anything earlier has a cleaner exit:

• Still a draft, in checks, in review, refused or failed: delete it, or withdraw and delete it, from the release page. Nothing was ever sent to a store. See editing, reopening and resubmitting.
• Approved or delivering: that option is closed, because the release is already moving. Open a support request instead and say you want it stopped.

Urgent copyright, impersonation and DMCA

If something has to come down urgently, do not wait for the normal route. Open a support request, pick the Takedown help category, name the release and say plainly what the urgency is: someone else’s recording, a voice or likeness used without consent, an impersonation of another artist, or a formal notice you have received. Attach whatever evidence you have.

If the release is not yours, or you do not have a Run account, use the route in reporting infringement instead.

When a takedown starts somewhere else

A takedown does not always begin with you. A store can remove a release under its own policies, a content claim against your release can be upheld, or a review of an already-delivered release can find something that has to come off. In each of those cases the release moves to Taken down the same way, and we email you rather than leaving you to notice it.