An Image Is Labelled ClothOff: Where Should You Report It?
Identify the hosting location of an unwanted image, separate a software accusation from an observed fact, and route a report without spreading the content.
Start with the platform or website hosting the known copy. A ClothOff label does not independently establish how the image was made. Record the location and explain the harm through the host’s official reporting route. If a search result also appears, treat its removal as a separate request.
Report the known location of an unwanted image before trying to prove a software label. A post mentioning ClothOff may contain an accusation, a misleading caption or a claim you cannot verify. That uncertainty does not prevent you from recording where the content appears and seeking the appropriate reporting route.
This guide concerns image abuse and reporting. It does not explain how to create or alter images of another person.
Identify who controls the copy
A software name in a caption and the website displaying the image answer different questions. The useful first question is which service can act on the particular post you know about.
| Observation | Appropriate scope of the next question |
|---|---|
| A forum post displays the image | How does that forum receive abuse reports? |
| A search result points to the post | What does the search service’s removal policy cover? |
| A caption names an AI tool | What evidence, if any, supports that attribution? |
Do not turn the third row into an obstacle to the first two. Nor should a familiar product name lead you to send sensitive material to an unrelated support account.
Preserve the location carefully
The eSafety evidence guide identifies URLs, account identifiers and dates as useful context, and warns against copying illegal material. Follow the receiving service’s requirements. In particular, do not download or screenshot illegal sexual material involving minors.
Keep a private location note instead of reposting the content to ask where it came from. If the platform has a copy-link function, the resulting post location is more useful than a broad homepage URL. Never publish a private case reference as part of a public complaint.
Write a bounded report
An illustrative report structure is: “This post at [location] contains an unwanted manipulated image depicting me. I observed it at [time]. Please assess it under the applicable image-abuse policy.” Add the context the official form requests, using only claims you can support.
If a caption names ClothOff, describe that as a caption claim rather than a proven production history. If you do not know who operated an account, leave that question open. A factual report is useful without a complete forensic investigation.
Track the decision’s actual scope
Google’s personal-content removal policy distinguishes search visibility from the source copy. Record a search response separately from a hosting-platform response.
For a fictional forum-and-search case, the forum may confirm removal while the search request remains pending. Your log should show those two outcomes, rather than compressing both into “resolved.” Equally, an approved search request does not establish that the forum removed its file.
End each record with a concrete next question: whether a named URL was assessed, whether more context is required, or which official review option applies. This keeps follow-up focused on a decision the recipient can actually make.
Sources and verification
This guide distinguishes published documentation from examples and observations. Feature access, policies and account screens can change; the linked source governs its own terms.