VisionLeeDocumentation
Documentation HubTerms of ServicePrivacy PolicyAcceptable Use PolicyLaw Enforcement Guidelines

Last updated: March 2026

Law Enforcement Guidelines

These guidelines are intended for law enforcement agencies seeking information from VisionLee LLC in connection with official investigations. This document describes the types of data VisionLee maintains, the legal process required to obtain that data, and how to submit requests.

1. About VisionLee and Dokibada

VisionLee LLC operates the Dokibada platform, a WebRTC signaling service that facilitates peer-to-peer connections between content providers ("Firms") and viewers. It is important to understand the following about our technical architecture:

  • Signaling only: VisionLee operates signaling infrastructure that facilitates the establishment of WebRTC peer-to-peer connections. The signaling server exchanges session descriptions (SDP offers/answers) and ICE candidates between peers.
  • No content storage: VisionLee does not host, store, cache, process, inspect, or moderate any video, audio, or other media content. All media content flows directly between peers via encrypted WebRTC connections.
  • TURN relay: When direct peer-to-peer connections cannot be established, traffic may be routed through a TURN relay server. Even relayed data is encrypted end-to-end between peers and is not accessible to VisionLee.
  • Connection metadata only: The data VisionLee maintains is limited to connection metadata as described in Section 2 below.

2. Available Data

VisionLee maintains append-only, tamper-evident connection logs. The following categories of data are available in response to valid legal process:

2.1 Firm Account Records

  • Firm name and description
  • Account holder email address
  • Account creation date
  • Authentication provider (email, Google, GitHub)
  • API Key issuance and revocation history (keys themselves are hashed; we do not store plaintext API keys)
  • Account status (active, suspended, terminated)

2.2 Connection Event Logs

For each signaling connection event, the following is logged:

  • Firm ID: The identifier of the Firm providing the stream
  • Stream ID: A unique identifier for the streaming session
  • IP Address Hash: A SHA-256 hash of the connecting party's IP address (with rotating salt). Raw IP addresses are not stored when privacy mode is enabled (default)
  • Timestamps: Connection initiation time, connection establishment time, and disconnection time (UTC)
  • ICE Method: The connection method used (host/direct, server-reflexive/STUN, or relay/TURN)
  • User Agent: The browser or client application identifier string
  • Session Duration: Total time the connection was active

2.3 Hash Chain Verification

All connection event logs are stored in an append-only format with cryptographic hash chain verification. Each log entry includes a hash of the previous entry, forming a tamper-evident chain. This means:

  • Logs cannot be modified or deleted after creation without breaking the hash chain
  • The integrity of any individual log entry can be verified against the chain
  • VisionLee can provide cryptographic proof that logs have not been tampered with

2.4 Data We Cannot Provide

Due to our technical architecture, VisionLee cannot provide:

  • Video, audio, or other media content (we never have access to this data)
  • Raw IP addresses (only hashed IPs are stored when privacy mode is enabled)
  • The content of WebRTC signaling messages beyond connection metadata
  • Information about what was communicated between peers
  • Decrypted TURN relay traffic

2.5 IP Hash Verification

While VisionLee cannot reverse IP address hashes to determine original IP addresses, we can perform hash verification. If law enforcement provides a specific IP address, we can confirm whether that IP address matches any stored hash within a given time window (as the salt rotates periodically). This can be used to confirm or deny that a specific IP address connected to a specific stream.

3. Legal Process Requirements

3.1 United States

VisionLee LLC is a Delaware limited liability company. For U.S. law enforcement, the following legal process is required:

  • Subpoena: Required for basic subscriber information (firm name, email, account creation date, account status)
  • Court Order (18 U.S.C. Section 2703(d)): Required for connection event logs, including IP hashes, timestamps, ICE methods, and session metadata
  • Search Warrant: Required for the full scope of available data, including API key history and complete connection logs for a specified period

3.2 International Requests

VisionLee will respond to international law enforcement requests through the following channels:

  • Mutual Legal Assistance Treaty (MLAT) requests processed through the U.S. Department of Justice
  • Letters rogatory issued by a foreign court and domesticated through a U.S. court
  • Requests made pursuant to applicable international agreements (such as the CLOUD Act executive agreements)

VisionLee will not respond to direct requests from foreign law enforcement that have not been processed through appropriate legal channels, unless required by applicable law or in cases of imminent threat to life (see Section 4.2).

3.3 Preservation Requests

Law enforcement may submit a preservation request pursuant to 18 U.S.C. Section 2703(f) to ensure that data relevant to an investigation is not deleted. Because VisionLee uses append-only log storage, connection event data is not subject to routine deletion. However, account data may be subject to deletion upon user request. Preservation requests will be honored for ninety (90) days and may be extended upon request.

4. Submitting Requests

4.1 Contact Information

All law enforcement requests should be directed to:

4.2 Emergency Requests

In situations involving imminent danger of death or serious physical injury, VisionLee may disclose information to law enforcement without requiring formal legal process, pursuant to 18 U.S.C. Section 2702(b)(8) and (c)(4). Emergency requests must be submitted by a sworn law enforcement officer and must include:

  • The nature of the emergency, including specific facts establishing imminent danger
  • Identification of the person(s) at risk
  • The specific information requested and why it is necessary to address the emergency
  • The identity and contact information of the requesting officer, including badge number and agency

Emergency requests should be sent to law-enforcement@visionlee.com with "EMERGENCY REQUEST" in the subject line. We will make best efforts to respond to emergency requests within four (4) hours.

4.3 Required Information

All non-emergency requests must include:

  • The valid legal process (subpoena, court order, or search warrant)
  • A description of the information sought
  • The relevant identifiers (firm name, firm ID, stream ID, date/time ranges, or specific IP addresses for hash verification)
  • The case number or investigation reference
  • The name, badge number, and contact information of the requesting officer
  • The name and contact information of the prosecuting attorney, if applicable

5. Response Timelines

  • Emergency requests: Best efforts within four (4) hours
  • Standard requests: Within five (5) business days of receipt of valid legal process
  • Preservation requests: Implemented within twenty-four (24) hours of receipt
  • Complex requests (large date ranges or multiple accounts): Within ten (10) business days, with notification if additional time is needed

6. Data Format

Data produced in response to legal process will be provided in one of the following formats as requested:

  • JSON: Structured data export with full field names and nested objects
  • CSV: Tabular data export suitable for spreadsheet applications

All data exports include a cryptographic hash verification certificate that allows the recipient to verify the integrity of the provided data against the original hash chain.

7. User Notification

Unless prohibited by law, court order, or the legal process itself, VisionLee will attempt to notify affected users before disclosing their information in response to legal process. We will provide a reasonable period (typically ten business days) for the user to seek legal counsel and, if appropriate, challenge the legal process before disclosure.

VisionLee will not provide user notification when:

  • Notification is prohibited by the legal process or applicable law
  • A court has issued a non-disclosure order (gag order)
  • The request involves an emergency situation
  • Notification would jeopardize the safety of any individual
  • The account has been terminated for violations of the Acceptable Use Policy involving illegal content

8. Cost Reimbursement

VisionLee may seek reimbursement for the costs of producing records in response to legal process, as permitted by 18 U.S.C. Section 2706. Cost estimates will be provided upon request before data production.

9. Transparency

VisionLee is committed to transparency regarding law enforcement requests. We intend to publish an annual transparency report disclosing aggregate statistics about the number and type of law enforcement requests received, the number of accounts affected, and the percentage of requests that resulted in data disclosure, to the extent permitted by law.

10. Contact Information

For all law enforcement inquiries:

For non-law-enforcement legal inquiries, contact legal@visionlee.com.