A careful workflow for documenting suspected unauthorized copies of subscription content and choosing the appropriate official reporting route.
Published ; updated
Finding a copy of your paid content online can be distressing. Start by preserving evidence and checking the context before deciding whether a copyright, privacy, impersonation, or platform-policy report is appropriate.
1. Treat search results as candidates
Search your creator name, work titles, distinctive captions, and a small set of representative images. A visual or text match is only a lead: previews can be misleading, licensed uses may exist, and one page may point to another host.
2. Preserve reviewable evidence
- Record the exact page or post URL, not only a homepage or search-results page
- Capture the date, account or channel identifier, and enough surrounding context to identify the material
- Keep a reference to the original work and records showing that you own it or are authorized to act
- Avoid downloading suspicious files or sharing intimate material more widely while documenting it
3. Confirm the reporting basis
Copyright does not apply to every unwanted mention or copy. Review ownership, licenses, permissions, possible exceptions, and whether a privacy or non-consensual-intimate-image process is more suitable. Seek qualified legal advice when the position is uncertain.
4. Use the current official process
Use the reporting instructions published by the service hosting the material. If a search engine lists the page, its legal-removal process is separate from removal at the source. A submitted report is a request for review, not a guaranteed removal.
5. Track decisions and later candidates
Keep the submitted URLs, evidence, case reference, decision, and any follow-up together. Periodic searches may reveal new candidates, but no search method can establish complete coverage of the public internet.
Build a calm first-response checklist
When a subscriber or follower sends you a suspected leak, ask for the live URL and where they found it rather than requesting copies of the material. Save the report time, the page or account, and the minimum screenshot needed to identify the candidate. Then stop and verify. Acting quickly does not require accusing an account before you understand whether the page is live, what it contains, and which service controls it.
For sensitive material, keep evidence access narrow. A screenshot can create another copy, and sending it through group chats or ordinary support threads may increase exposure. Prefer a case reference and protected storage. If the page involves intimate imagery, threats, doxxing, or impersonation, check whether the host provides a dedicated safety or privacy process instead of forcing every issue into a copyright form.
Map the locations before choosing a report
One discovery can involve several locations: a social post advertising the leak, a link-shortener, a file host, and a search result. Write each location on its own line with the material it controls. A report to the social service may address the promotional post; a request to the file host concerns the stored file; a search-engine request concerns an eligible result. Success at one layer does not prove that the others changed.
Use an evidence log you can revisit
- Candidate URL, service, account or uploader, and capture date
- Protected-work reference and the specific image, clip, or text being compared
- Known licences, collaborators, agencies, previews, or promotional permissions checked
- Reviewer decision, uncertainty, selected report route, and exact requested action
- Submission reference, provider response, appeal, and later availability check
This log prevents the same candidate from being reported repeatedly and lets a second reviewer understand the decision without reopening sensitive material. It also makes it easier to correct a mistake when a collaborator, licensee, or authorised promotion is discovered later.
Ask for a proportionate outcome
Identify the exact post, page, file, or account behaviour that the provider should review. Avoid asking for an entire domain or account to disappear when the evidence concerns one item. Precise requests reduce ambiguity and make correction easier. Keep submitted, acknowledged, limited, removed, declined, restored, and no-longer-accessible as different states; none of them should be silently converted into a guaranteed success claim.
AISentinela is intended to help organize possible matches and supporting evidence for human review. It does not determine infringement, promise complete coverage, or guarantee a platform response. General information only, not legal advice. Review the current official platform process before acting.