1. Who this page is for

Send all legal process, emergency requests, and preservation requests to legal@kinkchatrooms.com — that address is the only channel we act on for this.

If you're a member of the public rather than an investigator, you want a different page: content removal goes through Content Removal and everything else through contact@kinkchatrooms.com — writing to the legal address will only slow you down.

2. Legal process we require

We disclose user records when we're served with valid legal process issued under U.S. law. As a rule:

• Subpoena — basic subscriber information: the username, the email address on the account, the sign-up date, and the IP addresses and source ports recorded at sign-in
• Court order — other non-content records, including device identifiers, user-agents, the age/gender/city snapshots, username history, and moderation records
• Search warrant — the contents of communications: messages and uploaded media, to the extent they still exist. See section 4 before you assume they do.

Send it as a PDF from an official domain, signed and dated, with a return address and a direct contact. We don't require a particular form.

Requests from outside the United States need to come through a U.S. court, by mutual legal assistance treaty or letter rogatory. We serve users in the United States, Canada, and New Zealand, but the company and its records are in the U.S. and U.S. process is what reaches them.

An informal email asking for user data is not process and we won't act on it. The one exception is section 5.

3. What we hold, and for how long

These periods are enforced automatically by scheduled jobs. Once a record is past its window it's deleted, and we can't produce what no longer exists. The same table is published to users in our Privacy Policy section 6.

One connection record per sign-in, not per action. We write a record when a user authenticates. There is no per-message IP log, and messages themselves carry a server timestamp in UTC but no address.

Uploaded images are hashed and checked against a database of known child sexual abuse material before anything is stored. A match blocks the upload — the file is never written to our storage — and we keep the hashes and the account details. We cooperate with law enforcement and child protection organizations on those records.

4. What doesn't exist

This section exists to save you a request. None of the following is data we hold and later delete — it is data the Service never creates.

• Room message history that goes past 500 messages per room. That cap is a matter of volume, not time: each room keeps its most recent 500 messages and the rest are deleted continuously. On a busy room that can mean a few hours. No retention period holds them, and a request that arrives afterwards cannot recover them.
• No schedule deletes private messages. They're kept as long as both accounts exist and neither user deletes them. That's the current state of the Service, not an undertaking to keep them.
• No IP bans, and so no IP blocklist. Enforcement runs on the email address and the device identifier. Mobile carriers share one address among hundreds of subscribers, so we never ban by address.
• No payment records. The Service is free. There is no payment processor, no card data, and no billing address anywhere in the system.
• No age-verification records. Nothing of the kind is retained once a session ends. There are no identity documents, and no scan, photograph, or attestation to produce.
• No real names. An account is a username, an email address, a gender, a city, and a year of birth. The date of birth we store carries a real year only — the day and month are placeholders.
• No GPS or device location. A user types a city; we resolve it and derive approximate coordinates from it. Nothing comes from the device's location services.
• No webcam recordings. Camera streams pass through our relays live and are never written to disk. There is nothing to produce after the fact.
• No passwords. Sign-in is by one-time email link or Google. There is no password on file.

5. Emergency disclosure requests

Where we believe in good faith that there is an emergency involving a risk of death or serious physical injury, we may disclose the information we hold about it without waiting for process. That's a judgment call we make case by case, not an entitlement.

Write to legal@kinkchatrooms.com with “emergency disclosure request” as the subject line, and put in the first paragraph:

• The nature of the emergency and why disclosure can't wait for process
• The specific records you need, and the account they concern
• Your agency, your name, your badge or bar number, and a direct phone number

Say it's an emergency in the subject line. We don't staff a 24-hour desk, and a request that reads like routine correspondence will be handled like routine correspondence.

6. Preservation requests

We accept preservation requests at legal@kinkchatrooms.com — identify the account precisely, state the records and the time period, and say what process is coming.

Being straight about it is more useful to you than a promise: nothing in the Service suspends a scheduled deletion, so preservation means someone copying records out by hand, case by case, and what's already gone is gone.

Send it early. Room messages are evicted by volume rather than by age, and deleted messages are erased within 24 hours. A preservation request that arrives after the fact can't bring any of it back.

7. Making a request we can act on

The more of this you give us, the less of it we have to guess:

• The exact username, spelled as it appears, plus the email address on the account if you have it. A username is unique at any one moment, but an abandoned one can be taken by someone else later — a username alone doesn't identify an account across time.
• A bounded time period, stated in UTC. Our timestamps are UTC. A window in local time without the offset is a source of error we can't correct for you.
• The specific records you want, by reference to section 3.

If you're working from an IP address, bring the source port. Carrier-grade NAT means one address can be shared by hundreds of subscribers at the same moment. Our connection records store the source port for exactly this reason, and an address on its own — without a port and a precise timestamp — identifies no one in particular.

A single connection-record export is capped at 10,000 records, so a request framed as “all activity” returns a truncated report. Bound the period instead.

8. What we don't do

• No direct access. We don't provide accounts, database access, dashboards, or any other portal into the Service. Records are produced by us, in response to process.
• No monitoring. We don't wiretap, we don't flag accounts to watch, and we don't collect anything going forward on request. What we can produce is what already exists.
• No informal disclosure. Outside the emergency in section 5, we don't disclose user records without process, whoever is asking.
• No reconstruction. We won't attempt to identify a user beyond what the records themselves say, and we won't infer, correlate, or profile on request.

Notice to the user: we don't notify an account holder where the law or a court forbids it. Outside those cases we make no commitment either way.

9. Changes to this page

We may update this page. When we do, we change the “Last updated” date at the top. The retention periods it states track what the Service actually enforces — if a period changes, this page and the Privacy Policy change with it.

10. Contact

Skyline Online LLC
1209 Mountain Road Place NE, Ste N
Albuquerque, NM 87110, USA

Legal process, emergency requests, and preservation requests: legal@kinkchatrooms.com