Law Enforcement Request Policy

Scope

This policy explains how Rindforge LLC, a company incorporated in Wyoming, USA, responds to requests from law enforcement and other public authorities for information about users of OmegleWeb (omegleweb.cam). OmegleWeb runs on one platform together with lemonchat.app, omegle.fm and chatoo.pl; all of these sites share one user base, so a request about any of them is handled in the same way and through the same contact.

Requests from authorities: [email protected]. Requests from users about their own data are handled under our Privacy Policy, not this page.

Principles

• —We disclose personal data only in response to valid legal process — a subpoena, court order, warrant or an equivalent order that is binding on us — where the law otherwise requires it, or in the emergencies described below.
• —We do not give any authority informal, voluntary or standing access to user data, and we do not run searches without legal process.
• —Requests must be specific. We reject or narrow requests that are overly broad, vague or unsupported by a legal basis, and we disclose only the data a request lawfully covers.
• —We review every request for validity before responding.

What Data Exists

OmegleWeb is an anonymous video chat. We do not record video or audio and we do not store conversations. A short-lived log of chat sessions — who chatted with whom, from where and when, never what was said — is kept for 30 days. The full list of what we hold is in our Privacy Policy; in summary, the following can exist for an account at the time of a request:

• —Account data — the account identifier; for Google sign-in, the Google account identifier, email address, profile name and avatar link; for anonymous accounts, only the nickname; declared gender; country derived from the IP address; sign-up date and last-visit date; browser and device type.
• —Connection IP addresses — the address of the most recent connection, the last 10 distinct addresses with dates, and the public addresses observed while a video connection was being set up.
• —Moderation records — bans and their reasons, reports (the pair of user identifiers and a timestamp, without content), internal moderation flags, the most recent moderation frame if the account is not banned, and recent anonymized face-analysis estimates (gender and age group).
• —Payment records — purchase history without payment details, and the order identifiers issued by Google Play or by our cryptocurrency payment processor.
• —Technical server logs (IP addresses, browser type, requested pages, timestamps) — for up to 30 days.
• —Chat session records — the identifiers of both participants, their IP addresses and countries, the site each of them was using, the start and end time of the chat, and whether the session was reported — for up to 30 days.
• —Correspondence with our support.

What we do not have and therefore cannot provide: recordings or screenshots of chats (other than the single most recent moderation frame), the text of messages, chat session records older than 30 days, precise location, phone numbers, or payment card details.

Data is deleted on the schedule set out in the Privacy Policy regardless of pending informal enquiries. If you need data kept, send a preservation request (below) before it expires.

How to Submit a Request

Send requests to [email protected] from an official government email address; we do not act on requests sent from personal or anonymous addresses. A postal address for formal service of process is provided on request through the same address. A request should include:

• —The issuing authority, the name and contact details of the responsible officer, and the case or reference number.
• —The legal basis and the type of process (subpoena, court order, warrant, or the applicable statute), with a copy of the order attached.
• —The identifiers that let us find the account: user ID or nickname, the email address for Google accounts, or an IP address together with a date and time including the time zone.
• —The specific categories of data requested and the date range.

We aim to respond within 10 business days. Emergency requests are reviewed as a priority (see below).

Preservation Requests

On a valid preservation request (for example under 18 U.S.C. § 2703(f)), we preserve the existing data for the identified account for 90 days, renewable once for a further 90 days, pending legal process for its disclosure. Preservation applies only to data that exists when the request is received; we do not start collecting or recording anything new.

Emergency Disclosure

Where we have a good-faith belief that disclosure is necessary to prevent an imminent risk of death or serious physical injury, or child sexual exploitation, we may disclose limited data to law enforcement without formal legal process.

Send such requests to [email protected] with the subject line EMERGENCY DISCLOSURE REQUEST and state the nature of the emergency, the person at risk, the specific data needed and how it will prevent the harm. Emergency requests are reviewed as a priority. We may ask the requesting officer to confirm the request through an official channel.

Requests From Outside the United States

Rindforge LLC is a United States company, and user data is stored on our own servers in the European Union. Authorities outside the United States should use a mutual legal assistance treaty (MLAT), letters rogatory or another established cooperation channel. We also comply with orders that are binding on us under the law that applies to our service, including orders issued under the EU Digital Services Act, provided they meet the requirements above.

Reports We Make Ourselves

Where the law requires it, we report child sexual abuse material to the National Center for Missing & Exploited Children (NCMEC) and preserve the related material for the period the law prescribes. Details are on our Child Safety Standards page.

Notice to Users

Most users are anonymous, and we have no way to contact them. Where an account has an email address, the law permits it, and the request is neither under seal nor an emergency, we may notify the user of the request before disclosing data.

Records

We keep an internal record of every request we receive and its outcome, and we may publish aggregate numbers. We never publish the personal data of users, reporters or officers.

Nothing in this policy creates rights for third parties or obliges us to disclose data beyond what the law requires.