What meaningful consent looks like
Consent should be direct, informed, specific, and voluntary. The person should understand which photo will be used, that an AI will create a clothes-removal edit, who will see the result, and whether it might be shared. Silence, past relationships, public posting, or general permission to edit photos is not enough.
- Direct: permission comes from the person, not an assumption.
- Specific: it covers this type of clothing edit.
- Informed: the person knows AI may change body and facial details.
- Revocable: they can withdraw before distribution.
Image suitability is mandatory
Only use photos that clearly meet all suitability requirements and whose subjects can independently give valid, informed consent to this specific edit. If that cannot be established, do not upload.
Suspected serious safety abuse should be reported to the appropriate authority. Do not download, copy, or email the suspected material.
Public photos and public figures still require permission
A search result, profile photo, press image, or social post may be easy to access, but it remains subject to copyright, privacy, publicity, platform, and personal-consent rules. Do not create body or clothing edits of celebrities, politicians, creators, strangers, former partners, coworkers, or acquaintances without direct permission.
Minimize the data in the image
Crop out bystanders, addresses, vehicle plates, documents, computer screens, unrelated personal photos, and other details that are not needed. Use a private device, avoid shared browser sessions, and close the result when finished.
Ask not only “Is this allowed?” but also “Would the person reasonably expect this processing?” If the answer is uncertain, do not upload.
Label and share synthetic images carefully
An AI result should not be used to imply that the person actually wore a garment, attended an event, endorsed a product, or approved a post. Add a visible “AI-edited” label when context could confuse an ordinary viewer. Never use an edit for blackmail, humiliation, fake evidence, fraud, or a harmful portrayal.
When someone asks you to remove their image, act quickly—even if you believe the original permission was valid.
Safety needs product controls, not just a policy
A responsible service fixes the model instruction on the server, enables provider safety checking, validates image formats, states permission requirements at the point of use, limits requests, keeps credentials off the browser, avoids public galleries, and makes result links short-lived and non-indexable. No single control independently proves image suitability or consent, so the system also needs reporting and enforcement.
A decision check before uploading
Pause if you cannot answer four questions clearly: Who owns the image? Did every identifiable person agree to this exact outfit edit? Where will the result be stored? Who may see or receive it? A vague answer to any one of these questions is a reason not to proceed.
Permission to take or post a photo is not automatically permission to transform clothing. Likewise, permission for a private experiment is not permission to publish the result. Keep the agreed purpose and audience narrow, and ask again before expanding either.
Responsibilities continue after generation
Review the output for misleading identity changes and add context before sharing. Keep the result off public pages if the subject agreed only to private use. Delete local copies when they are no longer needed, and respond promptly if the subject changes their mind.
If a synthetic image is used in a design mockup, presentation, or creative portfolio, label it in a way that an ordinary viewer can understand. The label should describe the edit without implying that it documents a real event.
How to report misuse
Send a result URL or request ID and a short explanation to safety@removeclothes.pro. Do not attach suspected illegal material. We prioritize reports involving serious safety violations, non-consensual imagery, threats, blackmail, and impersonation. Read the full Acceptable Use & Safety Policy.