Valid process in.
Minimal data out.

This Policy is addressed primarily to law enforcement officials, government agencies, and legal professionals seeking information from the Company, and it informs our Users how we handle requests for their information. It is provided for transparency and operational guidance — it does not create contractual obligations, waive any right or objection, or expand the scope of any legal process; we reserve all rights and defenses available under applicable law.

Our guiding principles: good-faith cooperation with legitimate investigations — particularly protecting children and victims of exploitation; respect for user privacy, requiring valid legal process before disclosing non-public information; minimal, lawful disclosure — only the specific information valid process requires, never more, never volunteered; and due diligence — every request is reviewed for legal sufficiency, validity, and scope, and we may object to, narrow, or seek to quash requests that are overbroad, defective, or unlawful.

Submit requests, legal process, and correspondence to [email protected] (or by mail to FetishHaus Ltd., Attn: Legal / Law Enforcement Response). To help us respond, include:

• The requesting agency, the officer's name and badge/ID number, and an official agency email address or letterhead.
• A direct return contact (phone and email) for the assigned official.
• The specific legal process supporting the request — subpoena, court order, or warrant — attached as a copy.
• Precise identifiers for the account(s) at issue: username, account email, Creator handle, transaction or billing reference, or the URL of specific Content.
• The specific categories of records sought and the relevant date range.
• Any response deadline, and whether a non-disclosure or notification-delay order accompanies the request.
• Requests lacking sufficient detail may be delayed or unable to be processed; we may ask for clarification.

• Subpoena — generally required for basic subscriber or account-identifying information: name on the account, account email, creation date, and IP addresses associated with creation or login, to the extent retained.
• Court order (e.g., under the Stored Communications Act, 18 U.S.C. § 2703(d), or an equivalent state order) — generally required for non-content transactional records such as connection logs and account-activity records, to the extent retained.
• Search warrant — issued on probable cause by a court of competent jurisdiction, generally required for the contents of communications or stored Content, and anything else for which a warrant is legally required.
• We may decline, or produce only in part, where the process cited is legally insufficient for the category of data sought.
• Jurisdiction and service — process must issue from a court or authority with jurisdiction over the Company and be validly served. Non-U.S. requests should come through an MLAT, letter rogatory, or other recognized channel unless law provides otherwise.
• Authentication — we may take reasonable steps to verify the authenticity of a request and the requester's authority, and are not responsible for responding to requests we cannot reasonably authenticate.

Where we believe in good faith that an emergency involving danger of death or serious physical injury requires disclosure without delay, we may voluntarily disclose information to law enforcement to the extent permitted by law (18 U.S.C. § 2702(b)(8), § 2702(c)(4)).

Email [email protected] with subject "EMERGENCY DISCLOSURE REQUEST", including: the nature of the emergency and the specific imminent threat; the person(s) in danger; why the information is needed to prevent the harm and cannot await formal process; the specific information requested; and the requesting official's name, agency, and direct contact. Each request is evaluated individually; disclosure is discretionary and limited to what we believe necessary to address the emergency, and does not relieve law enforcement of obtaining proper process where otherwise required.

We honor valid preservation requests under 18 U.S.C. § 2703(f) or comparable authority. On receipt of a proper request reasonably identifying the account(s) and records, we take reasonable steps to preserve responsive records in our possession, pending valid legal process compelling disclosure. Preservation does not result in disclosure — we snapshot but do not produce absent valid process or an applicable emergency basis. Preservations are maintained for the legally required period (generally up to 90 days, renewable under § 2703(f)). We can only preserve records that exist and that we retain at the time the request is processed.

Our default practice is to make reasonable efforts to notify the affected User before disclosing their information in response to legal process, and to provide a copy or description of the request where practicable — so Users can assert their rights.

We will not provide advance notice, or may delay it, where: we are legally prohibited (sealing order, statutory non-disclosure, or court-ordered delay); the request carries a valid order prohibiting notification; we believe in good faith that notice would create risk of harm — death or serious injury, harm to a child, evidence destruction, witness intimidation, flight, or interference with an active investigation; or the matter involves an emergency, CSAM, or human trafficking where notice could endanger a victim. Where notice is delayed by order or statute, we provide it after the prohibition expires, to the extent permitted. Requesters seeking non-disclosure should specify its legal basis and duration.

• We can only produce or preserve what we possess when a request is processed. Potentially available: account-registration information, creation and activity dates, billing and transaction references from our payment processors (we store no full card numbers), creator payout records, Content metadata, moderation and reporting records, and certain log/IP data — each only to the extent and for the period retained.
• Creator identity and age records (2257 / KYC) — retained for the periods required by 18 U.S.C. § 2257; see the 2257 Compliance Statement and Age Verification Policy.
• Consumer age-verification data — we do not retain consumer government-ID documents after verification, consistent with state law; that underlying identity data is generally not available to produce.
• CSAM preservation — where we report to NCMEC, the report and associated material are preserved as 18 U.S.C. § 2258A requires.
• Legal holds — on a valid preservation request or anticipated litigation, affected records are held beyond ordinary retention as required.

We maintain zero tolerance for CSAM and trafficking, reflected in review-then-publish moderation and prohibited-keyword filtering. On actual knowledge of apparent CSAM we report to NCMEC's CyberTipline and preserve as required; child-safety requests are handled as a priority. We cooperate in good faith with trafficking investigations consistent with our Anti-Slavery Policy and FOSTA-SESTA. The public can report CSAM, non-consensual content, or trafficking to [email protected]; NCII removal runs under the TAKE IT DOWN Act Policy. In CSAM, trafficking, and child-safety matters we generally do not give advance notice to an affected account holder where doing so could endanger a victim or compromise an investigation.

• We disclose only what valid process requires and produce only reasonably responsive records — no bulk or open-ended access, and no direct law-enforcement searches of our systems.
• We may object to, narrow, or move to quash requests that are overbroad, unduly burdensome, vague, or legally defective.
• We are not the records custodian for third-party payment processors, acquiring banks, or independent vendors — direct requests for their records to them; we will identify what we hold versus what a processor holds where we reasonably can.
• To the extent permitted by law, we may seek reimbursement of reasonable costs of retrieval, review, and production.
• Nothing here waives any objection, privilege, or defense available to the Company or any affected User.

• Law enforcement / legal process — [email protected] (mail: FetishHaus Ltd., Attn: Legal / Law Enforcement Response)
• Emergency disclosure — [email protected], subject "EMERGENCY DISCLOSURE REQUEST"
• Abuse, content reports, NCC, CSAM — [email protected] · General support — [email protected]
• Copyright — [email protected] under the DMCA Policy · 2257 inquiries — see the 2257 Compliance Statement.
• If and when we serve EU/UK users, additional authority-request obligations (GDPR, DSA) will be addressed as part of that rollout.