No consent?
No content.

Consent is not a formality on fetish.haus — it is the precondition for every piece of Content that appears anywhere on the Service. Every person depicted must: be 18 or older (or the local age of majority, if higher) and age-verified consistent with our Age Verification Policy and 2257 record-keeping; have known they were being recorded in a sexual, intimate, nude, or fetish context; and have given documented, informed consent to being recorded and to the Content being distributed on the Platform.

If consent for any depicted person cannot be documented, the Content does not belong on fetish.haus. When consent is unverifiable or in dispute, we resolve doubt in favor of removal. Because all Content is reviewed before publication, with a prohibited-keyword filter as part of moderation, our goal is to stop non-consensual content from ever going live — not merely to remove it afterward.

"Non-Consensual Content" (NCC) means any Content that depicts, identifies, or sexualizes a real person without documented consent, or that was created, captured, or distributed without a depicted person's consent. It is strictly prohibited, including:

NCII and "revenge porn". Sexual, nude, or intimate images or video of an identifiable person shared without consent — including imagery created consensually within a relationship but distributed without consent, and imagery shared to harass, coerce, extort, shame, or punish.

Hidden-camera, upskirt, and voyeur content. Content recorded covertly or of a person with a reasonable expectation of privacy who did not consent — "spycam" footage, upskirt/downblouse imagery, recordings in bathrooms, changing rooms, bedrooms, hotel rooms, and other voyeuristic capture of non-consenting people. Staged, clearly fictional roleplay by consenting, verified Creators is treated differently — see Section 4.

Deepfakes and AI-generated or "nudified" content. Any AI-generated, digitally manipulated, face-swapped, or "nudified" sexual depiction of a real, identifiable person made without consent — deepfake sexual imagery mapping a real face onto sexual Content, AI tools used to undress or sexualize a real person from a non-sexual source, and synthetic voice or likeness making a real person appear to participate. A depiction does not have to be "real" footage to be prohibited. (Sexual depictions appearing to involve minors are categorically prohibited under the CSAM Policy, however produced.)

Doxxing. Publishing or threatening to publish a person's private or identifying information — including attaching it to sexual Content or using it to "out", locate, threaten, or extort — whether the target is a Creator, a Member, or a non-user.

Coerced, deceptive, or withdrawn consent. Content where "consent" was obtained through coercion, threats, fraud, impersonation, intoxication-based incapacity, or deception about use — or where consent has been withdrawn. Consent to record is not consent to publish; consent to publish in one area is not consent to publish everywhere.

Before publication and as a condition of upload, the uploading Creator must: confirm every depicted person has been identified and age-verified with records maintained under our 2257 / consent-records practices; capture and retain a signed consent / model release from each depicted person tying consent to the specific Content and its distribution (including likeness and any AI-assisted depiction); and warrant that no depicted person has withdrawn consent. These records are maintained internally and never published — they exist so our removal and enforcement commitments are backed by evidence, supporting our 18 U.S.C. § 2257/2257A obligations and the Custodian of Records function. Capture, format, and retention specifics live in the Creator Agreement and Age Verification Policy.

Some fetish and roleplay scenarios are designed to depict loss of control, restraint, or non-consent as part of a performance. These are permitted only when the performance is consensual and verifiable. For bondage, restraint, and BDSM scenes depicting struggle or simulated non-consent ("consensual non-consent" roleplay), and for surprise, "caught", or hidden-camera-style roleplay, documented written consent alone may not be sufficient — we may require visible and/or audible on-camera consent from each participant, a safeword or check-in, and/or a separate signed acknowledgment that the scenario is staged. Where Content looks non-consensual, we require extra evidence that it was, in fact, consensual — and reviewers may decline to publish if consent is not adequately evidenced.

Altered-state scenarios are a categorical no-go. Content portraying a participant as hypnotized, asleep, drugged, or otherwise intoxicated or incapacitated — depicted as unable to consent in the moment — is strictly prohibited and will not be published, regardless of any on-camera statement, signed release, or other consent documentation. Card-network rules treat a person depicted in an altered or incapacitated state as unable to consent; no amount of consent evidence overrides this.

If you believe Content depicts you or someone else without consent, report it — no account needed. Use the in-product report button, email [email protected], or use the Complaints process — NCC reports are prioritized for urgent review.

A useful report includes: a link or identifier of the Content; who is depicted (you, or your relationship to the person); why the Content is non-consensual (recorded covertly, shared without consent, an AI/deepfake of an identifiable person); and how we can reach you. You do not have to send us the intimate image itself. If the report involves a person under 18, do not upload, copy, or send the image — report immediately to [email protected] so we can act under the CSAM Policy. We do not penalize good-faith reporters, including the depicted person, for coming forward.

• Triage and prioritize — NCC reports (especially intimate-imagery and deepfake reports) move to the front of the moderation queue.
• Remove or restrict — we promptly remove or disable access while we review; where consent cannot be verified, the Content stays down.
• Account action — we may suspend the uploading Creator, withhold related payouts, and terminate accounts that upload NCC; uploading NCC can mean immediate, permanent removal from the Platform.
• Preserve evidence — to comply with law, respond to law enforcement, and support the depicted person, consistent with the Privacy Policy and Law Enforcement Request Policy.
• Decisions and appeals — removal decisions are communicated through the Complaints process; affected parties may use the Appeals Policy, and a depicted person contesting consent obtains removal where consent is unverifiable.
• For intimate imagery covered by the federal TAKE IT DOWN Act, the stricter 48-hour statutory timeline applies (Section 8).

Removing one copy is not enough. We generate a digital fingerprint / hash of removed NCC and add it to an internal blocklist; use automated hash-matching to detect and block identical or near-identical copies at upload and, where feasible, across the existing library; and combine this with pre-publication review and the prohibited-keyword filter so re-upload attempts are caught before going live. This applies platform-wide across Raw, Vault, and Private Access. For known CSAM, separate legally governed hash-matching and reporting obligations apply under the CSAM Policy.

This Policy works with our TAKE IT DOWN Act Policy, which implements the federal notice-and-removal requirement for non-consensual intimate imagery, including AI-generated deepfakes: a clear, conspicuous, easy-to-use removal request process for identifiable individuals (or authorized representatives), with removal of the reported imagery — and reasonable efforts to remove identical copies — within 48 hours of a valid request. That statutory duty is tighter than the general timelines here and controls where it applies. If you are the depicted person, the TAKE IT DOWN route is the fastest; any channel in Section 5 also works, and we route covered requests into that workflow.

Our enforcement is backed by the per-content consent / model release and identity records required under these policies. Where those records do not establish that every depicted person consented and is an adult, the Content does not stay up.

• Terms of Service
• Acceptable Use Policy
• TAKE IT DOWN Act Policy
• CSAM Policy
• Complaints Policy
• Appeals Policy
• DMCA / Copyright Takedown Policy
• Age Verification Policy
• 2257 Compliance Statement

• Non-consensual content, abuse, NCII/CSAM reports — [email protected]
• Appeals (including depicted-person consent disputes) — [email protected]
• Copyright / DMCA — [email protected] · Privacy — [email protected]
• General support — [email protected] · Legal process — [email protected]
• This Policy is governed by Delaware law; disputes are subject to the arbitration provisions of the Terms of Service.