aiundressapp.xyz The Consensus Brief · № 7
The Brief → Position Map
Reader's Guide · Positions

Every Position on the AI Undress App, Mapped

TMCompiled by Theo Marsh · Last updated: November 2026
Companion to the Consensus Brief · positions as stated by each community, in their own terms

The main brief measured how much agreement exists. This page is the map underneath: six constituencies, each with a distinct stake and a distinct vocabulary, arranged so you can see who is actually disagreeing with whom — and on what.

Bloc AThe users

Forum regulars · tool communities

"The tech works; the services don't."

The internal consensus of the tools' own communities is strikingly close to the outside critics' — minus the moral framing. Their documented grievances: upload retention that everyone knows about and proceeds anyway; domains that die mid-subscription; a scam rate high enough that forum wikis maintain "known fake" lists; and a shared understanding, increasingly stated outright, that the legal risk is real and personal.

Position: use is treated as a calculated vice, not a right — "know what you're risking" is the community's own standard advice. Fringe position ("it's just pixels") exists but is consistently shouted down as legally naive.

Bloc BThe researchers

Threat intelligence · academic HCI · psychology

"An image-based-abuse problem wearing a technology costume."

The literature's framing is uniform: this is the largest measured category of malicious synthetic media, the victim pool democratized when inpainting made any social-media photo sufficient input, and the harm attaches to the depicted person regardless of whether pixels were generated or photographed. Where researchers diverge is remedy design — model-layer governance vs. distribution-layer enforcement — not diagnosis.

Position: near-unanimous that non-consensual use is abuse; genuinely split on whether open-weight models can ever be governed.

Bloc CThe courts & legislators

US federal + ~45 states · UK · EU · KR · AU

"Decided."

Between the Take It Down Act's federal floor, the UK's creation offence, the EU directive, and Korea's production-and-possession regime, the legislative branch of this debate has largely adjourned. What remains in the courts is scope — penalties, platform duties, civil damages — not principle.

Position: sharing = criminal everywhere that matters; creation = criminal in the strictest jurisdictions and tightening; minors = the one absolute everywhere.

Bloc DVictims' advocates & support services

CCRI · Revenge Porn Helpline · national equivalents

"Treat it exactly like photographic NCII — because victims experience it that way."

The support community's contribution is procedural rather than rhetorical: they built the recourse infrastructure (StopNCII hashing, removal-request workflows, helplines) and their casework supplies the evidence base for the "harm is equivalent" position. Their consistent ask: stop asking victims to prove the image is fake before helping them.

Position: the synthetic origin is a technical detail; the consent violation is the harm. Unanimous.

Bloc EThe operators

Tool developers · service operators

"A neutral tool; responsibility sits with the user."

The industry's public position, where one is offered at all, is the classic intermediary defense: the software doesn't choose targets, self-use is legal, and abuse is a user problem. The community reads this position less charitably than the operators state it — retention-heavy data practices and victim-targeted marketing ("undress anyone") undercut the neutrality claim in the eyes of essentially every other bloc, including many of the tools' own users.

Position: the only bloc claiming the category is defensible as-is; also the bloc with direct financial interest in that claim.

Bloc FThe platforms & infrastructure

Registrars · hosts · CDNs · payment processors · app stores

"Not our content, but definitely our problem."

The infrastructure layer doesn't publish position papers; it publishes terms of service and then enforces them. The aggregate action — universal app-store bans, payment-processor ejections, registrar suspensions — constitutes the de facto position: this category is ejectable on sight at every infrastructure tier, which is the mechanism behind the churn the main brief's consensus meter records at 84%.

Position: expressed through enforcement rather than argument — treat the category as radioactive upstream of any legal test.

The MapWhere the blocs actually sit

QuestionUsersResearchersCourtsAdvocatesOperators
Does the tech work?yesyesn/ayesyes
Is non-consensual use abuse?mostly yesyesyes — unlawfulyesdisputed
Is private creation OK?splitsplitsplit by jurisdictionnoyes
Can it be governed?don't caresplitacting as if yesdistribution-layeropposes all
Legitimate use case exists?"self-use" onlymarginalconsent-verified onlynoyes (claimed)

The map's shape is the story: five blocs cluster tightly, one bloc holds the outlier positions, and that bloc is the one selling the product. That is what "consensus" means here — not unanimity, but the pattern of who dissents and why.