Law Enforcement & Government Request Guidelines

Last updated: July 9, 2026

TerminalStreet LLC ("TerminalStreet," "we," "us," or "our") respects the privacy and security of our users' data while also recognizing our obligations to comply with valid legal requests from law enforcement and government agencies. This document outlines our policies and procedures for responding to such requests.

1. General Principles

Our approach to government and law enforcement requests is guided by the following principles:

• Legal Compliance: We comply with valid legal requests in accordance with applicable laws and regulations
• User Privacy: We respect and protect our users' privacy rights to the fullest extent possible
• Narrow Interpretation: We interpret requests narrowly to minimize the disclosure of user data
• Transparency: We maintain transparency about the types and volume of requests we receive
• Due Process: We require proper legal process and documentation before disclosing user information
• User Notification: Where legally permissible, we notify users of requests for their information

2. Types of Legal Process We Accept

2.1 Subpoenas

Subpoenas may compel the disclosure of basic subscriber information, including:

• Account registration information (name, email address, registration date)
• Service usage information (login times, IP addresses)
• Billing information (if applicable)

We require that subpoenas be valid, properly served, and issued by a court with appropriate jurisdiction.

2.2 Court Orders

Court orders may compel the disclosure of more detailed information than a subpoena, potentially including:

• Transaction records
• Usage patterns
• Service configurations
• Limited content information in some cases

We require court orders to demonstrate sufficient legal grounds and specificity regarding the information sought.

2.3 Search Warrants

Search warrants may compel the disclosure of user content and other sensitive information, including:

• Content of communications
• Stored files and data
• AI model inputs and outputs (where applicable)
• Code repositories and development logs
• Blockchain transaction details (where applicable)

We require search warrants to be based on probable cause, properly issued by a court with appropriate jurisdiction, and specifically describe the information to be disclosed.

2.4 National Security Orders

National security orders, such as those issued under the Foreign Intelligence Surveillance Act (FISA) or National Security Letters (NSLs), may compel the disclosure of user information for national security purposes.

Due to their sensitive nature and potential legal restrictions, we are limited in what we can disclose about these orders. We report on these requests to the extent permitted by law through our transparency reporting.

2.5 International Requests

For requests originating outside the United States, we require that they:

• Comply with applicable international treaties or conventions (such as Mutual Legal Assistance Treaties)
• Be issued through proper legal channels in the requesting country
• Be properly domesticated in a U.S. court if seeking content or other information requiring a warrant
• Comply with U.S. laws and constitutional protections

We may also evaluate international requests in light of human rights considerations and potential risks to users.

3. Our Process for Handling Requests

3.1 Receipt and Initial Review

When we receive a government or law enforcement request:

• Our legal team reviews the request to verify its authenticity and legal validity
• We confirm the request comes from the appropriate authority with proper jurisdiction
• We verify that the request includes all necessary legal documentation
• We evaluate whether the request is sufficiently specific and not overly broad

3.2 Legal Assessment

Our legal team assesses:

• Whether the request complies with applicable laws and regulations
• Whether the request seeks information we actually possess
• Whether the legal process (subpoena, court order, warrant) is appropriate for the type of information sought
• Whether we have legal grounds to challenge or narrow the request
• Whether there are any conflicts with data protection laws in other jurisdictions

3.3 Response Preparation

If we determine that the request is valid and we must comply:

• We identify the specific information responsive to the request
• We limit disclosure to only what is explicitly required by the legal process
• We prepare the information in a secure and appropriate format
• We document our response process for internal records

3.4 User Notification

Our policy on notifying users of requests for their information:

• We endeavor to notify users of requests for their information prior to disclosure unless:
  • We are legally prohibited from doing so (e.g., by a gag order)
  • There is an imminent risk of death or serious physical injury
  • There is a risk of child exploitation or harm to vulnerable individuals
  • Notification would be counterproductive to an ongoing fraud investigation
• When notification is delayed due to legal prohibition, we seek to notify the user once the prohibition expires
• Notifications include information about the requesting agency, date of request, and general nature of the request (to the extent legally permitted)

3.5 Record Keeping

We maintain detailed records of all government and law enforcement requests, including:

• Date and nature of the request
• Requesting agency and jurisdiction
• Type of legal process received
• Information disclosed (if any)
• Status of user notification

These records inform our transparency reporting and help us improve our processes.

4. Emergency Requests

In emergency situations involving imminent risk of death or serious physical injury, we may provide information without legal process. For emergency requests:

• Requirements: The requesting agency must provide a written statement detailing the emergency situation and why the information is needed immediately
• Verification: We verify the legitimacy of the emergency request and the requesting agency
• Scope: We limit disclosure to information necessary to address the emergency
• Documentation: We require follow-up legal process to be submitted after the emergency has been addressed
• Review: Each emergency request undergoes senior leadership review prior to disclosure

5. Specific Considerations for TerminalStreet Services

5.1 AI and Machine Learning Services

For requests related to our AI and machine learning services:

• Model Inputs/Outputs: Content provided to or generated by our AI models may be considered user content requiring appropriate legal process
• Training Data: Requests for access to training data are evaluated with heightened scrutiny due to potential privacy implications for multiple users
• Algorithm Transparency: Requests for information about our algorithms and models are evaluated for intellectual property implications

5.2 Blockchain and Crypto Services

For requests related to our blockchain and cryptocurrency services:

• Public Blockchain Data: We may direct agencies to publicly available blockchain explorers for information that is already public
• Private Keys: We do not typically have access to users' private keys and cannot provide them
• KYC Information: Customer verification information may be available with appropriate legal process
• Smart Contract Code: Deployed smart contract code is typically public on the blockchain, but proprietary development information requires appropriate legal process

5.3 Financial Technology Services

For requests related to our financial technology services:

• Financial Records: Financial transaction data typically requires heightened legal process (court order or warrant)
• Algorithmic Trading: Trading strategies and algorithms are considered highly sensitive intellectual property and require specific legal process
• Regulatory Cooperation: We cooperate with financial regulatory authorities according to applicable financial regulations in addition to law enforcement processes

6. Challenges to Government Requests

We may challenge government requests that:

• Do not comply with applicable laws or constitutional protections
• Are overly broad, vague, or unduly burdensome
• Use inappropriate legal process for the information sought
• Raise significant privacy or free speech concerns
• Would create conflicts with laws in other jurisdictions
• Would set concerning precedents for user privacy or data protection

We may seek clarification, modification, or judicial review of such requests as appropriate.

7. Cost Reimbursement

In accordance with applicable laws, we may seek reimbursement for costs associated with processing government requests, particularly for requests that are voluminous or require significant technical resources.

We determine reimbursement rates based on:

• Personnel time required to process the request
• Complexity of data retrieval
• Volume of responsive information
• Technical resources required

We may waive reimbursement for emergency requests or requests related to child safety.

8. Transparency Reporting

We are committed to transparency regarding government requests for user information. To the extent permitted by law, we publish periodic transparency reports that include:

• The number of requests received, by country and type of legal process
• The number of requests with which we complied, partially complied, or rejected
• The number of users or accounts affected
• The percentage of requests where we notified users
• General categories of information produced
• Information about national security requests (to the extent permitted by law)

Our transparency reports are available on our website and updated annually.

9. Contact Information

Government and law enforcement agencies seeking user information should submit requests to:

[email protected]

Requests should include:

• The legal process document (subpoena, court order, warrant) as an attachment
• Contact information for the requesting agency and specific agent
• A detailed description of the information sought
• The legal authority for the request
• Any applicable deadlines

10. Changes to These Guidelines

We may update these guidelines periodically to reflect changes in law, our practices, or our services. We will post the updated guidelines on our website with a revised "Last Updated" date.