Law Enforcement and Data Requests Policy

Last Updated: March 15, 2025

This Law Enforcement and Data Requests Policy is published by Muvr Technologies, Inc. and its affiliates (“Muvr,” “we,” “us,” or “our”). This policy applies to information processed by or on behalf of Muvr in connection with the Platform, subject to applicable law.

This policy explains how we respond to requests from law enforcement, government agencies, regulators, civil litigants, and other third parties seeking information related to the Platform, including user information and records. It also describes how users can submit requests for their own information where applicable.

This policy is provided for transparency. It does not create contractual rights for third parties, and it does not limit our rights or obligations under applicable law.

1) Scope

This policy applies to requests seeking:

Account information (such as name, email, phone number, and identifiers)
Booking and service information (such as dates, times, locations, job notes, and service status)
Communications and content (such as messages, photos, reviews, and support submissions) where applicable
Transaction and billing information (such as receipts and payment related records we maintain)
Technical and device information (such as IP addresses, device identifiers, log data, and security signals) where applicable
Any other records we may hold in connection with the Platform

This policy covers requests from:

Law enforcement and government agencies
Courts and legal processes (subpoenas, court orders, warrants)
Regulators and administrative agencies
Civil litigants and attorneys
Private parties, including insurers and investigators

2) Core principles

We apply the following principles when responding to requests:

Legality: We require valid legal process where required by law.
Minimization: We aim to provide only the information reasonably necessary and responsive to the request.
User privacy and safety: We consider privacy, safety, and applicable legal restrictions before disclosing information.
Integrity and security: We protect our systems and data and do not disclose information in a way that compromises security.
Transparency where permitted: When allowed, we may notify users of requests for their information.

3) How to submit a request

All requests should be submitted through the law enforcement contact method listed on our website or through Support with “Law Enforcement Request” in the subject line. If a dedicated portal or email address is provided on our website, that method should be used.

Requests should include:

Agency or requester name, badge or employee ID (if applicable), and official contact information
The legal process relied upon (for example, subpoena, court order, warrant) and a copy of the document
The specific information sought
The relevant identifiers (for example, booking ID, user ID, email, phone number, dates, and locations)
The statutory basis, case number, or reference number (if applicable)
A statement if the request is time sensitive and the reason
Any requested non disclosure or delayed notice request, including the legal basis and duration (if applicable)

Incomplete requests may be delayed or rejected.

4) Required legal process

The type of legal process required depends on the category of information requested, the jurisdiction, and the circumstances. We generally require appropriate legal process, which may include:

Subpoena: typically for limited, non content records where permitted by law
Court order: typically for more sensitive non content records or where required
Search warrant: typically for content or other highly protected information where required by law
Emergency request: in limited emergency circumstances (see Section 6)

We may object to, narrow, or decline requests that are overbroad, unclear, improper, or not legally valid.

5) Data categories and examples

Depending on the request and legal process, we may be able to disclose certain categories of records we maintain, such as:

Basic account information: name, email, phone number, account creation date, account status, and certain account identifiers
Booking information: dates and times, service type, status, and related metadata
Location related information: pickup and drop off addresses provided for a booking; limited location or routing signals where available and legally appropriate
Communications: in app messages or support communications where we store them and where legally required process is provided
User content: photos or uploaded content associated with a booking where stored by us
Payment records: receipts and billing records we maintain; we do not disclose full payment card numbers
Technical logs: IP addresses, device identifiers, and security related logs where maintained

We do not guarantee that we collect, store, or retain every category listed above. Availability varies by service type, device settings, user actions, and time.

6) Emergency disclosure requests

We may disclose limited information without formal legal process when we reasonably believe, in good faith, that doing so is necessary to prevent an imminent risk of death or serious physical harm, and disclosure is permitted by applicable law.

Emergency requests should:

clearly describe the emergency and the imminent threat
identify the person at risk and the information requested
provide official requester credentials and a direct callback number and email from an official domain
include any available case number or incident number

We may require follow up legal process after an emergency disclosure where appropriate.

7) User notification

Where permitted by law and not prohibited by legal process, we may attempt to notify the affected user before disclosing information. We may delay or decline notification when:

prohibited by law, court order, or a valid non disclosure request
notification could create risk of harm or materially interfere with an investigation
we are unable to contact the user using the information on file

8) Preservation requests

Authorized requesters may ask us to preserve records for a limited period while they seek formal legal process. Preservation requests should:

be in writing
specify the accounts, identifiers, or bookings to be preserved
specify the date range
include a case or reference number

We may preserve records consistent with applicable law and our retention practices. Preservation does not guarantee that records exist or will be retained beyond legally required or reasonable preservation periods.

9) Requests from civil litigants and private parties

We generally do not provide user information to private parties without valid legal process (such as a subpoena) or user consent, except as required by law.

If you are a private party seeking information, you should pursue appropriate legal process. We may require:

service of process in compliance with applicable law
sufficient specificity to identify the relevant records
a protective order or confidentiality order in appropriate cases

We do not provide legal advice about how to obtain records.

10) International requests and cross border considerations

We evaluate requests based on applicable law, jurisdiction, and our ability to lawfully respond. For requests from outside the country where the relevant Muvr entity operates, we may require the request to be made through applicable international legal mechanisms, treaties, or other lawful processes.

11) Confidentiality and non disclosure requests

Some legal processes may include or require a request not to notify a user. We will follow applicable law and valid legal restrictions. We may challenge non disclosure requests that are improper, overbroad, unsupported, or not legally valid.

12) Fees and cost reimbursement

Where permitted by law, we may charge reasonable fees to cover the costs of responding to requests, such as research, retrieval, review, and production. We may require prepayment in appropriate cases, except where prohibited by law.

13) Verification, security, and integrity

We take reasonable steps to verify the authenticity of requests. We may reject requests that appear fraudulent or are submitted through unofficial channels.

We may provide information through secure means and may require:

encryption
secure portals
return of sensitive productions under protective terms
confirmation of receipt

14) Retention and availability

We retain information for periods described in our Privacy Policy and internal retention practices, and as required by law. Retention periods vary based on data type, legal obligations, safety and fraud prevention needs, and dispute handling requirements.

We do not guarantee that information will be available for any particular time period.

15) User access and user data requests

Users may be able to request access to certain personal information or records they are entitled to receive under applicable law. Requests should be submitted through Support and may require identity verification.

Some information may be withheld or redacted to:

protect the privacy or safety of others
comply with law or legal restrictions
protect security, anti fraud, and abuse prevention systems
preserve privileged or confidential information

16) Reserved rights

We reserve the right to:

object to, narrow, or challenge requests
require appropriate legal process
decline requests that are unlawful, overbroad, or improper
disclose information where required by law or permitted to protect rights, safety, and security
cooperate with law enforcement and regulators as permitted by law

Failure to enforce this policy in a particular instance does not waive our rights.

17) Updates

We may update this policy from time to time. Updates will be reflected by the “Last Updated” date above.

18) Contact

For law enforcement and government requests, use the law enforcement contact method listed on our website. For user requests, contact Support through the Platform or via the support contact methods listed on our website.