Valid process.
Careful production.

These Law Enforcement Guidelines (the "Guidelines") are for U.S. law enforcement and government authorities seeking customer account information or other data held by FleetPath Technologies, Inc. ("FleetPath," "we," "us"). They do not apply to ordinary customer support requests, civil third-party subpoenas from private litigants (which are handled separately), or international requests that lack proper U.S. legal process.

FleetPath operates a multi-tenant business-to-business software platform for commercial motor carrier operations. Customer data is isolated by tenant. We produce data only when legally compelled or when an emergency disclosure is permitted by law, and only after review.

These Guidelines support Section 11 of our Terms of Service and should be read with our Privacy Policy and Data Processing Addendum.

Send legal process by email to law-enforcement@fleetpath.app with the subject line Law Enforcement Data Request. That address is the dedicated intake for government process; do not use marketing or sales inboxes. Mail may be directed to: FleetPath Technologies, Inc., 30 N Gould Street, Suite N, Sheridan, WY 82801. Mail is slower and does not waive objections to jurisdiction, service, or process.

A complete request includes:

• The issuing agency and official contact name, title, phone, and email on an official domain
• A copy of the valid legal process (see Section 3)
• Sufficient identifiers to locate the account (for example, tenant or company name, registered work email, or known account ID) — no fishing expeditions
• The categories of records sought and a defined time range
• Any non-disclosure or delayed-notice order, if applicable
• For emergencies: the facts supporting imminent danger (Section 5)

We review every demand for facial validity, jurisdiction, and scope. We may narrow overbroad requests, object, or challenge process that does not comply with applicable law. The Electronic Communications Privacy Act (ECPA) and related authorities guide our U.S. production posture for stored electronic communications and customer records.

Basic subscriber and non-content account records (for example, account holder name and work email on file, tenant organization name, subscription status, IP logs associated with authentication where retained, and similar non-content metadata) generally require at least a valid subpoena or equivalent compulsory process.

Customer content(for example, documents customers upload, messages and operational records stored in the service, extracted document fields, and similar content of communications or stored files) generally requires a search warrant or equivalent process supported by probable cause, except where another lawful basis applies (including customer consent or a valid emergency disclosure under 18 U.S.C. § 2702).

We do not produce data belonging to one customer tenant in response to process that only identifies an unrelated account. We do not provide bulk dumps of multi-tenant data.

Where not legally prohibited, we notify the affected Customer before producing data so they may seek to limit or quash the request. That is the commitment in our Terms of Service §11.

We may delay or withhold notice when:

• A court order, statute, or the legal process itself forbids notice
• We believe in good faith that notice would create a risk of death or serious physical injury to an identifiable person
• Notice would compromise an investigation into child exploitation or similar crimes against children
• The account appears compromised and notice would be counterproductive until secured

When a non-disclosure period expires, we generally provide delayed notice unless an exception still applies.

Under ECPA, a provider may voluntarily disclose information to a governmental entity if the provider believes in good faith that an emergency involving danger of death or serious physical injury to any person requires disclosure without delay (18 U.S.C. §§ 2702(b)(8), 2702(c)(4)). We evaluate emergency requests case by case. They must be in writing from an official agency contact, state the nature of the emergency, and explain why the specific data is needed.

We report apparent child sexual exploitation material as required by law and cooperate with lawful investigations into crimes against children.

Authorities may request preservation of existing account records pending formal process. We will consider written preservation requests that identify the account with particularity. Preservation periods generally follow applicable law (commonly up to 90 days, renewable as the law allows), subject to system capability and ordinary retention schedules. Preservation is not production.

For routine process that can be satisfied with standard account lookups, we generally do not charge a fee. For unusually burdensome or extraordinary production (for example, large historical exports, custom forensic extraction, or repeated serial demands), we may seek cost recovery for reasonable staff time and out-of-pocket costs, consistent with applicable law and after notice to the requesting agency. We do not charge for bona fide emergency disclosures or child-safety reports.

We aim to respond within a reasonable time after receiving complete, valid process — typically within two to three weeks for standard requests. Complex or incomplete requests take longer. Mark true emergencies clearly in the subject line and body.

These Guidelines are written for government and law enforcement. Civil subpoenas and private party process are not automatically honored under this page. Private parties should serve process in accordance with applicable rules of civil procedure; FleetPath may require a court order, customer consent, or other lawful basis before producing customer content, and may notify the customer where permitted.

We may update these Guidelines. Material changes will update the effective date above. The version published at fleetpath.app/law-enforcement is controlling for public reference.