Legal

Copyright Policy

spotmp3 respects the intellectual property rights of others. It publishes no music library of its own. No page on this site is the page for a recording. An audio file exists on this server only because a visitor asked for it. A person reads and acts on every copyright notice. This policy is voluntary. A notice does not need to be styled as a formal DMCA notice before we act on it.

Last updated 2026-08-18

How to submit a copyright notice

Send your notice to support@spotmp3.net. To be actionable without follow-up questions, it should include:

1. Your name and signature, as the owner of the right or someone authorised to act on the owner’s behalf, and the rights holder you act for.
2. Identification of the copyrighted work you claim has been infringed — or, where one notice covers several works, a list of them.
3. Identification of the material complained of. Here that means the recording itself: title and artist, plus the Spotify link or spotify: URI a visitor would use to reach it — that id is what this service keys on. An ISRC or a catalogue number is welcome as corroboration but is not looked up. There is no library page on this site to cite.
4. Contact details — an email address we can reply to, and a postal address and telephone number if you want the notice treated as a formal one.
5. A statement that you have a good-faith belief the use complained of is not authorised by the copyright owner, its agent, or the law, and that the information in the notice is accurate.

What happens next

Complete notices are reviewed expeditiously — in practice within a few days of receipt. The acknowledgement comes from a person rather than an autoresponder, so allow for the time zones one inbox lives in. Where a notice is valid, every cached copy of the identified recording is deleted: from the shared cache on our own disk and from the object storage behind it. You receive written confirmation at the address you provided. An incomplete notice gets a reply describing exactly what is missing. You can complete it in the same thread rather than start again. The original receipt date still stands.

One limit needs to be clear. Deletion removes what is currently held. This service keeps no list of recordings it refuses to produce. It therefore cannot reject a link in advance. A takedown clears the copies in hand. If a recording must stay out, say so in the notice. We will handle that request directly.

If you think a removal was wrong

Reply to the confirmation email, or write to the same address with APPEAL in the subject line. An appeal is read by the same person who decided the original request and is checked against that request rather than re-argued from scratch. The takedown policy sets out the full process for both directions.

Repeat infringers

There is no sign-in here, so there is no account to close. The only handle this service has on a visitor is the network address their request arrives from — the same handle the daily track budget and the rate limits already use. Repeated valid notices may be traced to one address in the request logs. In that case, the address may be blocked at the edge for as long as it stays the same. A consumer address may change quickly. That is the limit of what terminating a repeat infringer can mean on a service that never asks who you are.

What this service does and does not do

A visitor supplies a Spotify link or searches by name. The public metadata behind the result is cached for about ten minutes. It may stay for up to a day longer while the source is unreachable. Matching audio comes from public sources, and the finished file goes to that visitor. The job folder is deleted twenty-four hours after the job ends. The finished track stays in a cache keyed by the recording, format and bitrate. This lets a popular song be fetched once rather than a thousand times. The object-storage copy behind that cache has no expiry of its own. No visitor id appears in those keys. A cached item is reachable only by asking for that exact recording again. The privacy policy carries the retention table, and what a visitor may do with a file is set out in the terms of service.