Law Enforcement Requests

These guidelines cover information controlled by Rookbeam Technologies LLC (the “Company,” “we,” “us,” or “our”) in connection with its Veydan services. We do not represent independent operators and have no authority to provide data from their servers.

#1. Submitting and Validating a Request

Send official requests to abuse@veydan.net and child safety matters to childsafety@veydan.net. Sending an email does not, by itself, satisfy applicable legal requirements for service of process or presentation of a demand.

A request must identify the agency, requesting official, verifiable official contact details, legal basis, case number, specific information sought, relevant time period, and identifiers that allow us to determine the subject of the request. An emergency request must explain the nature and immediacy of the threat.

We review the requesting authority's powers and the legal validity, applicability, and scope of the request. When needed, we ask for clarification, seek to narrow an overly broad request, or challenge it through the procedures available under law. Foreign requests are assessed under applicable procedures and international data transfer rules; receipt alone does not make them binding.

#2. Information We May Hold

The information available depends on the service used, its settings, and the records actually retained when we receive the request. We may hold:

• Public identifiers and technical information about a Cloud account, its plan, and quotas.
• Encrypted events, media, and files within their storage periods.
• Available connection, request, and security logs.
• Payment status, activation, and billing transaction records.
• User requests and materials separately submitted to support or with a report.

This list does not mean every category is collected in every case or retained for a particular user. An IP address or public key does not, by itself, verify a person's identity. We do not require a real name or phone number to create a chat identity.

We do not have users' private keys or the keys needed to independently decrypt content protected by end-to-end encryption. We cannot decrypt that content in response to a request. Separate copies of messages voluntarily provided to us in readable form by a person submitting a report or request are treated as materials received with that submission. Having those copies does not give us access to other messages or keys.

#3. Disclosure, Preservation, and Notice

We disclose information only when there is a valid, applicable legal basis, within the scope permitted or required, and only to the extent the data is actually available. Receiving a request does not create missing records, make deleted information recoverable, or provide missing keys.

A valid preservation request applies to existing data within its scope and the limits established by law. It may temporarily suspend routine deletion. Preserving an encrypted object does not decrypt it.

Emergency requests involving an imminent threat to life are reviewed based on verifiable circumstances and applicable grounds for emergency disclosure. Labeling a request an “emergency” does not remove the need to verify its origin and legal basis.

Reports of possible child sexual exploitation are handled in accordance with 18 U.S.C. § 2258A, where applicable, and our Child Safety Standards. When a legal duty to report or preserve information has arisen, we fulfill it without waiting for the entire internal review to be completed.

We provide legally required notice to users where notice is required and not prohibited by law. We may provide other notice where permitted, taking into account the rights of those involved and the integrity of the review or investigation. We do not publish materials from individual reviews or investigations; this does not limit mandatory disclosures to authorized recipients or mandatory reporting.

See also our Privacy Policy.

© 2026 Rookbeam Technologies LLC.