Law Enforcement Protocols

Effective date: August 26, 2026

1. What Information We Store

When a user creates an account and uses the Service, we may collect and store the following categories of information:

• Account information: email address, hashed password, and subscription status.
• Profile information: name, date of birth, gender, city and state, bio, interests, and up to six profile photos.
• Messages: content of messages sent and received through the Service, including timestamps.
• Location data: approximate location (city/state level) as provided by the user for matching purposes.
• Usage data: profiles viewed and rated, features used, and interaction patterns.
• Technical data: IP addresses, device type, operating system, app version, and log data including connection timestamps.
• Payment information: transaction records processed through Stripe (we do not store full card numbers).
• Reports and content moderation records: reports filed by or about a user, and any associated moderation actions.

2. How to Submit a Request

All law enforcement data requests must be submitted on official letterhead from the requesting agency and must include:

• A detailed reason for the request, including the nature and citation of the crime or legal authority.
• Specific data being requested and the relevant date range to be searched.
• A valid copy of the applicable legal process (e.g., subpoena, court order, search warrant, or production order).
• Contact information for the requesting officer, including full name, agency, department, rank or title, and a contact phone number.
• An official email address from a law enforcement or government domain.

We do not accept requests submitted via fax, phone, or from unauthorized individuals. If submitted by mail, please allow for longer processing times.

3. Account Identification

To locate a specific user account, we require the name of the account holder and at least one of the following identifiers:

• The email address registered to the account.
• The phone number registered to or linked with the account.
• The unique user ID (if known).

Providing additional identifiers helps us locate the correct account more quickly and avoid delays in processing.

4. Emergency Disclosure Requests

We may provide an expedited response to a legal request if the information relates to an emergency situation where we have reason to believe there is an imminent danger of death or serious physical injury to any person.

To qualify as an emergency, your request must include enough information for us to form a reasonable belief that the situation is genuinely urgent. Examples of situations we would consider emergencies include:

• A current kidnapping or missing person situation.
• An active sexual assault, including child sexual abuse.
• Imminent threats of mass violence.
• Acts of terrorism.
• Any other situation where a person's life is in serious and imminent danger.

Mark your request clearly as an "Emergency Disclosure Request" in the subject line. If we cannot verify that an emergency exists based on the information provided, we may delay our response while seeking additional details.

5. Preservation Requests

If you need us to preserve specific user data while you obtain the appropriate legal process, you may submit a preservation request. A valid preservation request:

• Must identify the account(s) to be preserved using the identifiers in Section 3.
• Must specify the categories of data to be preserved and the relevant date range.
• Must be submitted on official letterhead with the requesting officer's contact information.

Preservation requests are valid for 90 days from the date we receive them and may be renewed once for an additional 90-day period. Preservation does not constitute disclosure — data will only be released upon receipt of valid legal process as described in Section 2.

6. Valid Legal Process

We disclose data in response to valid legal process issued under applicable law. Depending on the jurisdiction, this may include:

• Subpoenas (including grand jury subpoenas and administrative subpoenas where authorized by law).
• Court orders issued under applicable statutes, including orders under the Stored Communications Act (18 U.S.C. § 2703).
• Search warrants supported by probable cause and issued by a court of competent jurisdiction.
• Mutual Legal Assistance Treaty (MLAT) requests for requests originating outside the United States.

We evaluate each request to ensure it is legally valid and properly scoped. We may challenge or narrow requests that are overly broad, legally deficient, or that we believe would impose an undue burden.

7. Where to Send Requests

All law enforcement requests should be addressed to:

You may also submit requests by email to legal@diezapp.com. Email submissions must come from an official law enforcement or government email address and must include the required legal process as an attachment.

For emergency requests only, you may also contact us at emergency@diezapp.com.

8. Response Timeline

We aim to respond to valid law enforcement requests as promptly as possible:

• Emergency Disclosure Requests: we endeavor to respond within 24 hours of receiving sufficient information to verify the emergency.
• Preservation Requests: we will confirm receipt and begin preservation within 3 business days.
• Subpoenas and Court Orders: we endeavor to respond within 10 business days of receiving a valid request.
• Search Warrants: we endeavor to respond within 10 business days of the warrant being signed by a court, or as otherwise required by the warrant.
• MLAT Requests: response times depend on the applicable treaty process and may be longer.

These timelines are targets, not guarantees. Complex or voluminous requests, or requests that require clarification, may take longer. We will notify you if we anticipate a delay.

9. Fees

We do not charge fees for emergency disclosure requests. For other requests, we reserve the right to charge reasonable costs for search, retrieval, and production, including administrative and technical costs, in accordance with applicable law. We will inform you of any estimated fees before processing your request.

10. User Notification

Our standard practice is not to notify users about law enforcement requests for their data, except where required by law (for example, where a court order includes a non-disclosure provision that later expires, or where disclosure is otherwise mandated). If you believe notification would compromise your investigation, please identify any applicable non-disclosure requirements in your request.

11. Contact Us

If you have questions about these protocols or need assistance with a request, please contact us at legal@diezapp.com.