Copyright & permissions · How we test and maintain this guide
Visibility answers a narrow question
A public link shows that a resource can be found or opened under some conditions. A successful technical request shows that particular bytes or metadata were returned. Neither observation, by itself, records what you may do with the work. Keep those facts separate so a convenient tool does not become an accidental substitute for a permission check.
The U.S. Copyright Office describes copying, distribution and other uses as distinct rights, subject to applicable limits and exceptions, in its copyright overview. That general explanation is not a ruling on a particular AI-assisted song or another jurisdiction. A specific use still needs an applicable basis rather than an inference from a visible play button.
| Observation | It can tell you | It does not establish by itself |
|---|---|---|
| A song appears in a public playlist | The list exposes that entry | Permission to redistribute the song |
| Audio preparation succeeds | The tool obtained a technically accepted result | Ownership or commercial clearance |
| The exported CSV contains a source URL | Where the recorded item came from | A licence for a future project |
| A written permission identifies a work and use | The stated scope of that permission | Every use outside that stated scope |
Apply the distinction to a playlist
Imagine a public playlist containing your own work, a collaborator's song and an unrelated creator's recording. The importer may list all three. That shared visibility does not make their permission histories identical. Your record should identify the basis for each selected track, and you can omit an unresolved entry while preparing material you are permitted to save.
This is a hypothetical decision example, not a verified playlist or a claim about the rights of any named creator. It illustrates why selection is useful: a collection can be assembled from the entries that fit your project without treating the entire source list as one licence. The tool's availability flag is a technical state, not a rights certificate.
The same distinction applies when somebody sends you a share link. It may be intended for listening or feedback. If you want to publish, edit, deliver or redistribute the file, make that proposed use explicit. A thumbs-up on a listening message may be too ambiguous to explain the wider plan later.
Ask a question tied to the actual work
A useful request identifies the song and version, describes the planned use, and asks about the relevant scope. For example: “I would like to use this identified recording in this project and publish the result through these channels. Does your permission cover that use, and are there conditions or credits I should preserve?” Adapt the request to your facts rather than treating the wording as a legal form.
- Confirm you are speaking with someone who can address the relevant rights or direct you to the right party.
- Provide the exact source identifier and the version you mean, especially where titles are repeated.
- Describe whether you need a private copy, a public use, a commercial use or redistribution of the raw file.
- Keep the response and its conditions with your project records.
- If the answer does not address an important part of the plan, leave that part unresolved and ask for clarification.
Do not invent an answer because the source remains online or another website offers a download button. Those observations can be relevant to technical availability, but they do not document the permission you asked about. Likewise, an attribution line is not a universal replacement for permission or another applicable basis.
Treat a concern as a specific review task
If somebody raises a concern, preserve the source identity, your records and the exact issue. Check whether the problem concerns the recording, lyrics, artwork, an inaccurate credit or a particular use. Avoid publishing private correspondence as a way to win an argument. The relevant evidence is easier to assess when it stays attached to a clear factual question.
For material or access through TuneBundle, use Copyright reports / DMCA. The process explains the information needed for review, possible restrictions and how to dispute a mistaken identification. It does not automatically remove a source from Suno, erase files already saved elsewhere or decide every ownership disagreement.
Keep permission records separate from technical manifests. A clean CSV, matching hash and playable file are valuable checks of an export. They remain different from evidence supporting how that work may be used.