Law Enforcement Guidelines

Effective 31 August 2026

These Law Enforcement and Government Request Guidelines explain how law-enforcement agencies, courts, regulators, and other competent government authorities may submit legal process, preservation requests, emergency requests, and other official requests concerning KinkzAI.

KinkzAI is operated by Nightcloud Interactive LLC (“Nightcloud,” “we,” “us,” or “our”).

These Guidelines are informational. They are not a contract, do not create rights beyond applicable law, and do not waive any jurisdictional, procedural, privacy, confidentiality, privilege, or other right, objection, defense, or protection available to Nightcloud or an affected person.

Nightcloud evaluates each request based on the request, the information reasonably available to us, the nature of the Service, and applicable law.

1. Scope

These Guidelines apply to official requests from law-enforcement, judicial, regulatory, and other competent government authorities seeking:

• information within Nightcloud’s possession or control;
• preservation of existing information;
• action concerning a KinkzAI account, feature, or content within Nightcloud’s control;
• information concerning suspected unlawful activity;
• an emergency disclosure relating to an imminent threat to life or serious physical safety; or
• other assistance that Nightcloud may be legally required or permitted to provide.

These Guidelines are not the general process for users, affected persons, rights holders, or members of the public to submit complaints concerning KinkzAI.

General complaints, safety reports, child-exploitation reports, trafficking reports, nonconsensual-intimate-imagery requests, billing complaints, and other user-facing reports should be submitted under our Complaints and Appeals Policy and other applicable KinkzAI policies.

2. Legal and Compliance Contact

Official law-enforcement and government requests may be submitted to Nightcloud’s Legal and Compliance Contact at:

admin@kinkzai.com

The subject line should identify the nature of the request, such as:

Law Enforcement Request Preservation Request Emergency Request

Requests should be submitted from an official government, agency, court, or regulatory email address where reasonably available.

Nightcloud may independently verify the identity, authority, agency affiliation, and contact information of a requesting person before preserving, disclosing, or taking action concerning information.

Submitting legal process by email does not constitute Nightcloud’s agreement to electronic service, waive any requirement for proper service, or waive any objection to jurisdiction, legal sufficiency, scope, or manner of service. Nightcloud may expressly accept electronic service in a particular matter where appropriate.

Formal legal process must otherwise be served in accordance with applicable law.

3. Information to Include in a Request

A request should provide enough information for Nightcloud to authenticate the request, identify the relevant account or records, determine the legal basis for the request, and locate responsive information without unnecessarily collecting or producing unrelated information.

Where applicable, please include:

• the name of the requesting agency, authority, or court;
• the name, title, badge number or other official identifier, official email address, telephone number, and mailing address of the responsible officer or official;
• the investigation, proceeding, or case number;
• the jurisdiction and legal basis for the request;
• the warrant, court order, subpoena, summons, preservation request, production order, regulatory demand, or other legal process relied on;
• information reasonably sufficient to identify the relevant KinkzAI account or activity, such as an account email address, internal identifier if known, transaction identifier, verification-provider reference, IP address if known, or other relevant identifier;
• a description of the specific records or information requested;
• the relevant date or time period;
• the applicable territorial scope, if relevant;
• any requested preservation;
• any applicable response deadline and the legal basis for an unusually short deadline;
• any legally binding nondisclosure, confidentiality, delayed-notice, or sealing requirement; and
• a secure official method for transmitting responsive information.

A request that is incomplete, unclear, unverifiable, overbroad, or unsupported by the legal process required by applicable law may be delayed while Nightcloud seeks clarification, narrowed where appropriate, challenged, or declined to the extent permitted by law.

4. Review of Requests

Nightcloud reviews official requests for matters including:

• authenticity;
• identity and authority of the requester;
• jurisdiction;
• legal basis;
• sufficiency and validity of legal process;
• scope and specificity;
• whether the requested information exists and is within Nightcloud’s possession or control;
• applicable privacy, data-protection, confidentiality, and other legal requirements;
• the rights and safety of affected persons;
• whether a request is overbroad, disproportionate, unduly burdensome, or seeks information unrelated to the stated matter; and
• other considerations relevant under applicable law.

Nightcloud may seek clarification or narrowing of a request and may object to, challenge, or decline a request where permitted by applicable law.

A request from an authority outside the United States does not necessarily create an obligation for Nightcloud to disclose information directly to that authority. An applicable cross-border evidence mechanism or other legally recognized procedure may be required.

5. Preservation Requests

A preservation request asks Nightcloud to preserve existing information so that it is not deleted through ordinary processes while the requesting authority obtains any legal process required for disclosure.

Preservation is not disclosure. A preservation request does not by itself entitle the requesting authority to receive preserved information.

A preservation request should identify:

• the relevant account, record, transaction, report, or other information;
• information reasonably sufficient to locate the material;
• the relevant date range;
• the legal basis for the request; and
• the requesting authority and investigation or proceeding.

Where 18 U.S.C. § 2703(f) applies to Nightcloud and the request, Nightcloud will preserve existing records and other evidence within its possession for the period required by that provision, including any additional preservation period required by a qualifying renewed request.

Nightcloud may also preserve information when required by other applicable law, valid legal process, a legal hold, or another legally binding preservation obligation.

Nightcloud cannot preserve information that it does not possess or control.

A preservation request does not require Nightcloud to create new information, reconstruct information that was not retained, or begin retaining categories of information that the Service does not ordinarily retain unless applicable law requires otherwise.

Receipt of a preservation request or other legal process does not by itself result in suspension, restriction, or termination of an account. Nightcloud may separately take account action where warranted under applicable law, the Terms of Service, or KinkzAI policies.

6. KinkzAI’s Data Architecture

The information Nightcloud can provide or preserve is materially affected by how KinkzAI operates.

6.1 Hosted Service conversations

Hosted Service conversation content is processed transiently to provide AI-generated responses.

Nightcloud does not maintain a server-side conversation history as part of its ordinary operation of the Service, and its ordinary Service logs are not designed to maintain a record of Hosted Content.

Accordingly, after a Hosted Service interaction has been processed and the conversation content is no longer within Nightcloud’s possession or control, Nightcloud generally cannot retrieve, reconstruct, produce, or preserve that conversation content in response to later legal process.

This applies to Hosted Content, including text and voice input processed through the Hosted Service.

6.2 Local and offline content

The Desktop App may permit characters, conversations, images, audio files, settings, user-supplied AI models, and other Local Content to remain entirely on a user’s own device.

Local Content that remains on a user’s device is not possessed or controlled by Nightcloud merely because the user operates the Desktop App.

Nightcloud generally cannot access, search, retrieve, preserve, or produce Local Content that has not been transmitted to Nightcloud.

6.3 Separately submitted information

The limitations above do not apply to information separately submitted to Nightcloud through a complaint, support request, safety report, legal communication, or other channel.

Information submitted through those channels may be retained and may be available in response to valid legal process, subject to applicable law.

7. Information That May Be Available

The information potentially available in response to valid legal process depends on the relevant account, feature, time period, retention status, service provider, and applicable law.

Subject to those limitations, information within Nightcloud’s possession or control may include:

• account information, including an account email address, internal identifiers, account status, subscription tier, registration information, and available account settings;
• subscription entitlement and message-allowance information;
• age-verification result information received by Nightcloud, such as a provider-issued identifier, verification or eligibility result, expiration or validity information, country, subdivision, and assurance level;
• subscription, payment, refund, reversal, chargeback, or transaction-reference information that Nightcloud receives from its payment processor;
• technical and security records actually retained by Nightcloud, which may include request timing, error information, prompt-length information, IP-address information, login or session timestamps, browser or user-agent information, device-related information, registration information, and security-event information;
• complaint, safety-report, support, investigation, moderation, appeal, and enforcement records;
• information submitted by a complainant or user as part of a report, including copied text or screenshots;
• non-content crisis-referral or safety-event records maintained in accordance with the AI Companion Safety Protocol;
• records concerning restrictions, suspensions, terminations, or other account actions;
• legal, regulatory, and compliance correspondence; and
• other information actually retained by Nightcloud and responsive to the request.

The availability of any category listed above in a particular case is not guaranteed.

Nightcloud does not receive complete payment-card numbers entered directly through a payment provider’s systems.

Nightcloud does not receive copies of identification documents submitted directly to its age-verification provider as part of the ordinary age-verification process.

Certain records may be held by an independent service provider rather than Nightcloud. Depending on the information requested and applicable law, an authority may need to direct legal process separately to Nightcloud’s payment processor, age-verification provider, hosting or infrastructure provider, authentication provider, or another applicable third-party custodian.

Nightcloud does not undertake to obtain records from a third party that are not within Nightcloud’s possession or control merely because the third party provides services used by KinkzAI.

8. Technical Capabilities

These Guidelines do not represent that Nightcloud has the ability to provide information that the Service does not ordinarily generate, retain, or make available to Nightcloud.

Nightcloud does not ordinarily maintain:

• a server-side archive of completed Hosted Service conversations;
• a copy of Local Content that remains entirely on a user’s device; or
• copies of identification documents submitted directly to Nightcloud’s age-verification provider.

If Nightcloud receives legal process seeking prospective monitoring, interception, real-time information, or other technical assistance, Nightcloud will evaluate the request based on applicable law and Nightcloud’s actual technical capabilities at the time of the request.

Nothing in these Guidelines expands Nightcloud’s technical capabilities or requires Nightcloud to create records that do not exist.

9. Emergency Requests

A competent government authority may submit an emergency request when it believes that an imminent danger of death or serious physical injury requires disclosure of information without the delay associated with ordinary legal process.

Emergency requests should be sent to:

admin@kinkzai.com

and should clearly state Emergency Request in the subject line.

An emergency request should include:

• the requesting agency or authority;
• the requesting officer’s or official’s name, title, official contact information, and agency affiliation;
• the nature of the emergency;
• the specific facts supporting the claimed imminent danger of death or serious physical injury;
• the person or persons believed to be at risk;
• the specific information requested;
• why the requested information is reasonably expected to address the emergency;
• why ordinary legal process cannot be obtained in time; and
• direct official contact information that Nightcloud can use to authenticate and discuss the request.

Nightcloud reviews emergency requests case by case.

Where applicable law permits emergency disclosure, Nightcloud may disclose information if Nightcloud determines in good faith that the applicable legal standard for emergency disclosure is satisfied.

Submitting an emergency request does not guarantee disclosure or an immediate response. Nightcloud may require additional information, independently verify the requester, limit the information disclosed, require follow-up legal process, or decline the request where the applicable standard is not established.

Authorities addressing an active emergency should use applicable emergency and law-enforcement channels in addition to submitting a request to Nightcloud.

If the emergency no longer exists or disclosure without ordinary legal process is not legally authorized, Nightcloud may require appropriate legal process before producing information.

10. Direct Reports of Imminent Danger

A user or other member of the public who believes a person is in immediate danger should contact the emergency services available where that person is located.

KinkzAI is not an emergency service.

If Nightcloud separately receives information through a complaint, support request, safety report, or other direct communication indicating an imminent risk to a person’s life or safety, Nightcloud may contact emergency services or law enforcement where permitted by applicable law.

Nightcloud does not undertake an obligation to do so and does not continuously monitor the Service for that purpose.

Additional information concerning KinkzAI’s crisis-response practices appears in our AI Companion Safety Protocol.

11. Reports and Voluntary Disclosures by Nightcloud

Nightcloud will make reports or disclosures to government authorities when required by applicable law.

Nightcloud may also make voluntary disclosures where expressly permitted by applicable law.

If the Stored Communications Act applies to Nightcloud and the information at issue, Nightcloud will disclose communications content or customer records voluntarily only as permitted by an applicable exception under that law, including applicable provisions concerning emergency disclosures, reports involving child sexual exploitation, consent, inadvertent acquisition of information concerning apparent criminal conduct, or other authorized circumstances.

Nightcloud may also make other reports or disclosures permitted by applicable privacy, safety, fraud-prevention, or other laws where the applicable legal requirements are satisfied.

A complaint submitted to Nightcloud does not automatically result in a report to law enforcement or another authority.

12. User Notice and Confidentiality

Nightcloud considers whether notice to an affected user is appropriate as part of its review of a government request.

Nightcloud may provide notice before or after disclosure where notice is permitted by applicable law and appropriate in the circumstances.

Nightcloud does not promise advance notice in every case.

Nightcloud may delay, limit, or withhold notice where:

• a binding law, court order, warrant, nondisclosure requirement, or other valid legal process prohibits or delays notice;
• notice could interfere with an investigation or proceeding;
• notice could create a material safety risk;
• notice could facilitate retaliation, evasion, destruction of evidence, fraud, or continued unlawful activity;
• notice could compromise another person’s rights, privacy, or safety; or
• another applicable legal basis permits or requires notice to be withheld or delayed.

Nightcloud may challenge or seek modification of an indefinite or overbroad nondisclosure obligation where appropriate and permitted by applicable law.

13. Cross-Border and Foreign Requests

Government authorities outside the United States should identify the legal basis on which they contend Nightcloud is required or permitted to respond.

Depending on applicable law, a foreign authority may be required to use:

• a mutual legal assistance process;
• letters rogatory;
• applicable domestic legal process;
• a process established under an international agreement;
• an applicable European production, preservation, or electronic-evidence mechanism; or
• another legally recognized cross-border procedure.

Where applicable law requires service through a designated establishment, legal representative, authority contact point, or other prescribed channel, the requesting authority must use the legally required mechanism.

Submission to admin@kinkzai.com does not replace a statutorily required method of service or prescribed cross-border process.

Nightcloud may voluntarily respond to a foreign request where disclosure is lawful and appropriate, but these Guidelines do not commit Nightcloud to do so.

14. Privacy, Data Minimization, and Security

Nightcloud processes government requests and related information in accordance with applicable privacy, data-protection, confidentiality, and procedural requirements.

Nightcloud seeks to identify information responsive to a valid request and to avoid producing unrelated information where reasonably practicable.

Requests involving sexual or intimate information, age-verification information, safety information, complaint materials, financial information, or other sensitive personal information receive particular care because of the risks associated with unnecessary disclosure.

Nightcloud may redact, limit, segregate, or securely transmit responsive information where appropriate.

Our Privacy Policy provides additional information concerning Nightcloud’s processing of personal information for legal compliance, investigations, safety, preservation, and disclosure to government authorities.

15. Response Timing

Response time depends on the nature, legal basis, scope, complexity, and urgency of the request and the time reasonably necessary to authenticate the request, evaluate applicable law, identify responsive information, and prepare a response.

Nightcloud will comply with binding response deadlines applicable to it.

These Guidelines do not establish a fixed response time for every official request.

Authorities should identify any legally applicable deadline and explain the basis for a request requiring expedited treatment.

16. Costs

Where permitted by applicable law, Nightcloud may seek reimbursement of reasonable costs associated with preserving, searching for, retrieving, reviewing, reproducing, or securely transmitting records in response to legal process.

Nightcloud may waive reimbursement where appropriate, including for qualifying emergency matters or other serious safety matters.

17. Rights Reserved

Nothing in these Guidelines waives any:

• objection to jurisdiction;
• requirement for proper service;
• objection to the validity, scope, proportionality, or legal sufficiency of a request;
• attorney-client privilege or work-product protection;
• privacy, confidentiality, trade-secret, or security protection;
• right to seek clarification or narrowing;
• right to challenge legal process;
• right to require a legally recognized cross-border process; or
• other right, defense, privilege, protection, or remedy available under applicable law.

Nightcloud’s decision to accept or respond to a request in one matter does not waive any right or establish a practice applicable to another request.

18. Changes to These Guidelines

Nightcloud may modify these Guidelines from time to time to reflect changes in the Service, Nightcloud’s data practices, applicable law, government-request procedures, or technological capabilities.

The date at the top identifies when these Guidelines were last updated.

19. Contact Information

Official law-enforcement and government requests:

Legal and Compliance Contact admin@kinkzai.com

KinkzAI is operated by:

Nightcloud Interactive LLC
5205 Harvest Run Way
Myrtle Beach, South Carolina 29579
United States

General user complaints and reports should be submitted in accordance with our Complaints and Appeals Policy.