Look at the track itself before the profile summary. If the profile shows a song that belongs to someone else, treat it as redistribution unless the public track page and profile clearly establish credit. When an AI report describes displayed music as a career claim, resolve only the roles the public record supports and leave the rest explicitly unresolved.
Find public social profile clues with our TraceSeek app.
Start with the track, not the profile
The profile is the wrong first object. Open the individual track and see who is credited there, then return to the profile and note how the track appears. SoundCloud profiles can show both a person's own public uploads and tracks or playlists they have reposted, so a song sitting on a profile is not by itself evidence that the profile owner made it. If the track cannot be opened, is private, or its page does not identify who uploaded it, record that limit and stop. Do not substitute a guess about the profile owner. [SoundCloud: public uploads and reposts]
- Open the track page and note the credit shown there
- Return to the profile and note whether the track appears as an upload or as a shared item
- If the track page is unavailable, write 'attribution unresolved' instead of inferring
Name the three roles separately
Keep three labels apart. The uploader is whoever the public track page indicates put the file there. The reposting profile is the account that displayed the track to its followers. The stated artist is the name the track or profile text claims as the performer or creator. These may coincide, or any two may differ, or none may be clear. An AI summary that collapses them into one 'musician' identity has smoothed over a distinction the public record may not support. Write each role in its own line and mark any role the source does not address as undocumented.
| observation | limit | next step |
|---|---|---|
| A track appears on a profile | It may be a repost rather than an upload | Check the track page for the credited uploader |
| The track page names an artist | That name may be a display claim, not proof of who uploaded the file | Keep 'stated artist' separate from 'uploader' |
| The profile shares music by others | This does not establish the profile owner's own work | Avoid describing the profile as the creator of those tracks |
| The track or page cannot be opened | No attribution can be established from this source | Record the gap and stop the inference |
What an AI report adds and what it does not
An AI report may summarise a public profile and describe what it sees. OCR and image-similarity search can surface text or visually similar public sources, and AI-assisted analysis of public-profile content can propose themes. None of that converts a displayed track into a verified credit. Treat an AI statement about music on a profile as a pointer to a public page to check, not as a finding. If the AI report says the person 'makes music' because songs appear on the profile, that is exactly the collapse to resist. Label it as a summary claim awaiting the public track page.
- Use the AI report as a list of pages to inspect, not as a conclusion
- Quote the profile's own text separately from the AI summary's wording
Handle the absent and ambiguous cases cleanly
Failure here is ordinary and should be recorded, not patched over. If the relevant track is private, it will not appear on a public profile and cannot be found through in-platform search, which means the public record simply does not contain the answer. If a source is mismatched, for example a profile image or name that does not match the track page, note the mismatch as a mismatch rather than deciding which one is 'real'. Do not try to reach private accounts, identify a person from a photo, or contact strangers to settle credit. A precise limit is a usable result. [SoundCloud: public uploads and reposts]
Decide what you can say in writing
A defensible sentence stays inside the public record. Something like 'this profile displays a track credited to another name on its public page; whether the profile owner contributed is not stated' is supportable. Something like 'this person is an emerging artist' is not, even if an AI report phrased it that way. Keep observation, its limit and your next step visually separate. If the reader's purpose is something that requires verified credentials, such as a background check, hiring, credit, housing or insurance decision, this material is the wrong input regardless of how clean the worksheet looks.
- Write one sentence per verified observation
- Add a separate line headed 'Limit' for each unresolved role
- Do not let a profile badge, follower count or matching photo stand in for identity or employment
A short worksheet you can keep yourself
This is an editorial aid, not a platform feature. Make four columns: role, what the public page shows, what it does not show, and the next permitted check. Fill one row each for uploader, reposting profile and stated artist. Mark any row where the source is absent or private as closed rather than pending indefinitely. A hypothetical example: a profile displays a song with a different artist name on the track page; the worksheet would record 'uploader: shown as another name', 'reposting profile: displays it', 'stated artist: as named on the track', with the limit that no public source states the profile owner's role beyond display. That example is invented to show the shape of the note, not a real case.
- Keep the worksheet with the source you checked and the date
- Close rows that cannot be resolved publicly instead of guessing
A couple more questions
If a song appears on someone's SoundCloud profile, did they make it?
Not necessarily. Profiles can display both the person's own public uploads and tracks they have reposted, so presence on a profile does not by itself identify the original uploader or artist. Check the individual track page before attributing creation.
What should I do when the track page is private or missing?
Record that the public record does not establish attribution and stop there. Private tracks do not appear on public profiles and cannot be searched within the platform, so no public source can fill the gap; do not seek private access or identify anyone by other means.
Can an AI summary of a profile be treated as a credit?
No. AI analysis of public-profile content can describe what a page appears to show, but it does not verify who uploaded a track or who performed it. Use the summary to find the public track page, then separate the uploader, the reposting profile and any stated artist.
Is this material suitable for screening a person?
No. Public profile placement and display text are not reliable evidence of identity, credentials or employment, and should not be used for background-check, hiring, credit, housing or insurance decisions.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.