Law Enforcement Guidelines

How law enforcement and government agencies can request information from UBee, and the legal process we require.

Operated by WooWay LLC, a Virginia limited liability company · Effective: June 2026 · Last updated: June 2026 · Version 1.0 (baseline)

Related: Privacy Policy · Child Safety Standards · Report CSAM · Terms of Service

1. Introduction & scope

These Guidelines are for law enforcement and other government authorities who seek information from WooWay LLC ("WooWay," "UBee," "we," "us," or "our") in connection with UBee. They explain how to send requests, the legal process we generally require, and how we handle preservation, emergencies, and notice to users. These Guidelines are provided for general information, do not provide legal advice, and do not create any rights or obligations beyond those imposed by law. They are not a complete statement of our practices, which depend on the specific facts and the law that applies.

2. How to submit requests

Please send legal process and related requests to [email protected]. Requests should come from an official government email address or other verifiable official channel, should identify the requesting agency and the official making the request, and should give enough detail for us to identify the relevant account or content — for example, the exact username and, where possible, the email associated with the account. We may take reasonable steps to verify the authenticity of a request, and we may decline requests that are not properly authenticated. Submitting a request to this address does not waive any requirement that the request be served in a manner required by law, and does not waive any objection we may have.

3. Authenticating requests

To protect our users, we take steps to confirm that a request is genuine before we act on it. We expect legal process and related requests to come from an official government email address or other verifiable official channel, and to identify the requesting agency and the official making the request. We may take reasonable steps to verify the authenticity of a request and the authority of the requester, and we may decline to act on requests we cannot authenticate. We are especially careful with urgent and emergency requests, because fraudulent "emergency" requests — sometimes sent from compromised or spoofed official accounts — are a known method of attempting to obtain user data improperly. Verifying a request is part of protecting the people who use UBee, not a delay tactic.

4. Legal process we require

We disclose user information only where required or expressly permitted by law, and we require legal process appropriate to the information sought. Under U.S. law, including the Stored Communications Act (18 U.S.C. §2701 et seq.):

• Basic subscriber information (such as account identifiers and limited records of account creation and activity) generally requires a valid subpoena.
• Certain other records and transactional information generally require a court order issued under 18 U.S.C. §2703(d) or other appropriate process.
• The contents of communications (such as the text of messages or posts) generally require a valid search warrant issued on a showing of probable cause by a court of competent jurisdiction.

We may also disclose information with the relevant user's lawful consent, or where another exception under applicable law applies. We do not produce data in response to informal requests that lack appropriate legal process, except as described for emergencies below.

5. What information we may have

UBee is built to collect as little as it reasonably can, so the information we can provide is limited. Depending on the account and the time period, we may hold limited account and registration information (such as an email address and account identifiers), self-reported profile details, the broad, self-reported places associated with a profile (UBee does not collect or store precise or GPS device location), text content created on the Service, and limited usage, log, and diagnostic information used to operate and secure the Service. UBee is text-only and does not host photo or video uploads, and it does not access a device's contacts, camera, or microphone, so no such data exists to produce. We can only provide information we actually have at the time of a valid request; we do not create data that we do not collect.

6. Information we cannot or will not provide

There are limits to what we can produce. We can only provide information we actually hold at the time of a valid request, and UBee is designed to collect little: we do not have a user's precise or GPS location, photographs or video, contacts, or other data we do not collect, so such information does not exist to produce. We do not disclose the contents of communications without a valid search warrant, and we do not disclose non-content records without appropriate legal process, except in the genuine emergencies described below. We do not produce data in response to informal requests that lack proper legal process, and we may object to, or seek to narrow, requests that are overbroad, vague, improper, or unlawful. Nothing in these Guidelines requires us to create, compile, or analyze information we do not already maintain in the ordinary course.

7. Preservation requests

We honor valid preservation requests under 18 U.S.C. §2703(f) and will take reasonable steps to preserve records we have at the time of the request, pending service of valid legal process. Consistent with the statute, we preserve such records for 90 days, which may be extended for one additional 90-day period upon a renewed request. A preservation request does not by itself require us to disclose anything; disclosure still requires appropriate legal process. (Preservation related to apparent child sexual abuse material is handled separately and for longer, as described in Section 10.)

8. Emergency disclosure requests

In a genuine emergency involving a danger of death or serious physical injury to a person, the law permits us to voluntarily disclose information to a government entity where we in good faith believe such disclosure is necessary to prevent that harm (18 U.S.C. §2702(b)(8) and (c)(4)). To make an emergency request, email [email protected] with "EMERGENCY DISCLOSURE REQUEST" in the subject line, and include the nature of the emergency, the specific harm you are trying to prevent, the account(s) involved, and the specific information you need and why. Emergency disclosure is voluntary on our part and limited to what we reasonably believe is necessary to address the emergency.

9. Notice to affected users

Our policy is to notify the people whose information is sought by legal process so they can protect their rights, unless we are prohibited from doing so by law or a valid court order (for example, a non-disclosure order under 18 U.S.C. §2705(b)), or unless we believe in good faith that notice would create a risk of harm to a person, would be counterproductive (for example, in a child-safety matter), or is otherwise inappropriate in the circumstances. Where a non-disclosure obligation expires, we may provide notice afterward.

10. Child safety

We have a dedicated process for child-safety matters. When we become aware of apparent child sexual abuse material, we report it to the National Center for Missing & Exploited Children ("NCMEC") through its CyberTipline as required by law, and NCMEC makes reports available to the appropriate law enforcement agencies. We preserve related information for the period the law requires — currently at least one year — and that preservation is independent of, and survives, account deletion. See our Child Safety Standards and CSAM reporting page.

11. Requests from outside the U.S.

WooWay LLC is a United States company. Requests from authorities outside the United States generally must be made through recognized channels for cross-border legal assistance — such as a mutual legal assistance treaty (MLAT) or letters rogatory — or otherwise be served through valid U.S. legal process. We evaluate such requests under U.S. law and the applicable legal framework.

12. Authentication of records & testimony

Where we produce records in response to valid legal process, and where the law permits, we may provide a written certification of authenticity of business records (for example, under the Federal Rules of Evidence) in lieu of live testimony, so that records can be admitted without requiring a custodian to appear. Requests for a records certification, or for testimony where it is genuinely required, should be directed to [email protected] with as much advance notice as possible, so we can respond while minimizing the burden on our small team.

13. No waiver; objections; cost

Responding to or acknowledging a request does not waive any legal objection, and we may object to or seek to narrow requests that are overbroad, vague, improper, or not supported by valid legal process. Where the law provides for reimbursement of the reasonable costs of responding (for example, under 18 U.S.C. §2706), we may seek such reimbursement. The law provides that no cause of action lies against a provider for disclosing information in accordance with valid legal process.

14. Relationship to our other policies

These Guidelines should be read together with our Privacy Policy, which describes the information we handle and how we retain it, and our Terms of Service. Nothing in these Guidelines limits any obligation imposed on us by law or any right available to us.

15. Changes to these guidelines

We may update these Guidelines from time to time — for example, to reflect changes in our practices or in the law. When we make material changes, we will update the "Last updated" date above.

16. How to contact us

Send legal process, preservation requests, and emergency disclosure requests to [email protected]. This address is for law enforcement and legal matters; for general support, use [email protected]. Email is the fastest and best way to reach us.