Law Enforcement Requests

1. Where to send a request

Requests from law enforcement and other competent authorities should be sent to support@lflabs.fund with “Law Enforcement Request” in the subject line, from an official government domain. Requests sent from a personal email address, through social media, or through the Telegram support handle will not be actioned.

2. Valid legal process is required

LF Labs discloses user information only where it is required or permitted by law, and only in response to legal process that is valid, properly served and within the authority of the body issuing it. We do not disclose user data on the basis of an informal request, a phone call, or a letter without underlying legal authority.

We review every request for authority, scope and proportionality before responding, and we may seek clarification or narrowing where a request is overbroad, vague or appears to exceed the issuing authority's jurisdiction.

3. What a request must contain

Issuing authority

The agency or court making the request, the officer's full name, rank or role, badge or reference number, official email address and a direct telephone number for verification.

Legal basis

The specific legal instrument relied on — warrant, court order, subpoena, production order or equivalent — attached in full, with the case or reference number.

Identifiers

Enough to identify the account: Telegram user ID or username, the email address on the account, deposit or withdrawal addresses, transaction hashes, or order and trade identifiers. A name alone is not sufficient to identify an account here.

Scope

Precisely what records are sought and the date range they cover. A request for “all records” without a period will be sent back for narrowing.

Response deadline

The date by which a response is required, with a realistic period allowed for review.

Preservation

State separately if you are asking us to preserve records pending legal process. A preservation request does not itself authorise disclosure.

4. Emergency requests

Where there is a credible risk of death or serious physical harm, mark the request “EMERGENCY DISCLOSURE REQUEST” in the subject line and set out the nature of the emergency, the harm risked, and why the information sought is needed to prevent it. Emergency requests are reviewed as a priority. Misuse of the emergency route to bypass ordinary process ends the accommodation.

5. What we can and cannot provide

• We can provide records we hold: account registration details, deposit and withdrawal history, on-platform transaction and order records, and connection logs, within our retention periods
• We cannot provide data we never collected — we do not receive Telegram passwords or login codes, and passwords are stored only as salted hashes
• We cannot produce records that have passed their retention period
• We cannot reverse a blockchain transaction; on-chain transfers are final and are already public
• Freezing an account balance requires the appropriate legal instrument and is not done on request

6. User privacy protection

We disclose only what a request actually covers, never the whole account by default. Where we are lawfully permitted to do so, our policy is to notify a user that their information has been requested, so that they have the opportunity to object — unless we are prohibited from notifying, or notification would create a risk of harm or of evidence being destroyed.

Requests, and what was disclosed in response, are logged internally.

7. Costs and service

Sending a request to the address on this page is not service of legal process on LF Labs, and this page does not designate an agent for service. We may recover reasonable costs of compiling a response where the law allows.