Requesting Emergency Assistance

Road Rescue Network (“RRN”) responds to bona fide emergency disclosure requests 24/7 where we have a good-faith belief that an emergency involving danger of death or serious physical injury requires disclosure without delay.
To submit an emergency request, the requesting officer must certify that:

• The request relates to an emergency involving danger of death or serious physical injury.
• Disclosure is needed without delay and legal process cannot be obtained in time.
• The requester is legally authorized to make the request and will follow up with legal process if required.

Submit emergency requests to: [email protected] with subject line: “EMERGENCY REQUEST,” including agency, badge/ID, callback phone, details of the emergency, the specific data sought, and relevant identifiers (phone, email, job ID, plate, date/time, location). RRN may contact you for clarification.

Legal Process Overview (U.S.)

RRN discloses information in accordance with applicable law, our Terms of Use, and our Privacy Policy. In the U.S., the Electronic Communications Privacy Act (ECPA) governs what we may disclose and the legal process required. Certain records require a subpoena, others a 18 U.S.C. § 2703(d) court order, and content or precise location typically requires a search warrant based on probable cause. Emergency disclosures may be made consistent with 18 U.S.C. § 2702.

Service of Legal Process

Primary channel (preferred): [email protected]
Mailing address (if needed): Road Rescue Network – Public Safety Response, 100 Public Safety Way, Suite 200, Montgomery County, PA 19401
Who may submit: Only government or law-enforcement personnel authorized to obtain evidence in connection with official proceedings.

When identifying an RRN account or record, please include at least one unique identifier where possible:

• Email address and/or phone number on the account
• Job/dispatch ID, date/time window, pickup location, destination, vehicle plate, rescuer profile name
• Payment transaction ID, last four of card (if known), billing zip
  Names alone are rarely sufficient.

User Notice Policy

RRN’s policy is to notify users (customers or rescuers) of requests for their data unless:

• The request contains a valid legal prohibition on notice (e.g., 18 U.S.C. § 2705(b) order).
• Notice is otherwise prohibited by law or court order.
• We determine in good faith that notice would be counterproductive (e.g., child safety, credible emergency, risk of flight/tampering).

If a nondisclosure order later expires, RRN may provide delayed notice unless we determine that doing so would jeopardize safety or an investigation.

Guidelines for Requesting Information

To help us process your request quickly, legal process should:

• Be addressed to “Road Rescue Network – Public Safety Response” (see address above).
• Be issued and signed by the appropriate authority and dated.
• Specify a reasonable return date for records.
• Clearly identify the account(s) or records sought and date range.
• Be narrowly tailored and not unduly burdensome or vague.

Overbroad, unsupported, or invalid requests may be rejected or narrowed.

Types of Legal Process We Recognize (U.S.)

• Subpoena (administrative, grand jury, or trial): may compel disclosure of Basic Subscriber Information per 18 U.S.C. § 2703(c)(2) and certain business records not protected by ECPA.
• 2703(d) Court Order (“(d) Order”): may compel disclosure of non-content records upon the requisite showing; does not permit disclosure of communication content.
• Search Warrant: required for content of communications and precise location/GPS data, and may also compel non-content records.
• Preservation Requests (18 U.S.C. § 2703(f)): RRN will preserve existing records for 90 days, extendable once for an additional 90 days upon timely renewal. Preservation is a one-time snapshot, not ongoing collection.
• Emergency Disclosure Requests (18 U.S.C. § 2702): see “Requesting Emergency Assistance” above.
• Witness Testimony: RRN generally provides Certificates of Authenticity for records. Live testimony requests should be served with at least 14 days’ notice; availability is not guaranteed.

Information Potentially Available from RRN

Availability depends on product features, user settings, retention schedules, and applicable law. Examples below are illustrative, not exhaustive.

Basic Subscriber Information (subpoena, (d) order, warrant, or emergency)

• Account profile: name, email, phone, account creation date, account status
• Means and source of payment (e.g., masked card details, expiration, billing zip) where applicable

Vehicle & Rescuer Information ((d) order, warrant, or emergency)

• Vehicle plate, make/model, VIN, registration, insurance (as provided to RRN)
• Rescuer license number and basic profile fields (where provided)

Billing & Transaction Records ((d) order, warrant, or emergency)

• Non-content billing records: charges, dates/times, payment instrument type (not full PAN), payout records to rescuers

Job/Service (Trip) Information ((d) order, warrant, or emergency)

• Job identifiers, timestamps, service category, quoted/charged amounts
• Pickup and completion locations (lat/long where available)

Location Information (warrant or emergency)

• GPS/location events from devices when users have enabled collection and the app was active (availability varies by platform state and settings)

Other Profile & Feedback ((d) order, warrant, or emergency)

• Ratings, written feedback/comments, associated profile photos as stored

Communications Records

• Non-content metadata ((d) order, warrant, or emergency): to/from, timestamp
• Content of in-app messages (warrant or emergency only), if retained

Customer Support & Business Records (subpoena)

• Support tickets, selected call/chat logs, policy acknowledgments, signed agreements, uploaded license copies (as applicable)

Note on Data Variability: Records retained may differ by account, settings, jurisdiction, product version, and retention schedules. Deleted or expired data may be unavailable.

Frequently Asked Questions

How do I send legal process?
Use [email protected] (preferred). Include a return date, scope, identifiers, date range, and your official contact details.

Do you notify users?
Generally yes, except where prohibited by law/order or where RRN determines notice would jeopardize safety or an investigation.

What if we need records preserved now?
Serve a 2703(f) preservation request. We preserve a one-time snapshot for 90 days, extendable to 180 days upon written renewal.

Can you provide passwords or full card numbers?
No. RRN does not disclose passwords and does not store full primary account numbers.

How fast will you respond?
We triage by urgency, scope, and completeness. Emergency requests are handled 24/7. For non-emergency process, timelines vary with scope and volume.

Will you deactivate an account upon request?
We evaluate safety reports independently and may take action consistent with our policies and applicable law, but we do not deactivate solely upon request absent valid legal basis or platform policy grounds.

Do you charge for compliance?
RRN generally does not seek cost reimbursement but reserves the right to do so as permitted by law.

What should we do with records after the case?
Handle and dispose of records consistent with your agency’s retention and evidence policies and applicable law.

Important Notes

• These guidelines are for law enforcement and government authorities. They are not legal advice and create no enforceable rights. RRN may update this page without notice.
• For jurisdictions outside the U.S., submit requests to [email protected]. We will provide routing and requirements applicable to your jurisdiction and may require local process and/or mutual legal assistance.

Contact

Public Safety Response (24/7 emergencies and legal process)
Email: [email protected]
Non-emergency legal inquiries: [email protected]

By working with us through the above channels and processes, law enforcement can help ensure timely, lawful, and safe handling of requests while respecting user privacy and applicable legal standards.