1. Scope and overview
Razor Dispatch provides trucking and logistics software for Driver and Dispatcher accounts. This policy applies to information processed through Razor Dispatch applications, related services, and support communications. The public website itself does not use analytics, advertising trackers, cookies, or contact forms.
2. Information we may process
Contact and account information
We may process a user's name, email address, phone number, company information, and business or physical address where applicable. We may also process a Razor Dispatch User ID, account identifiers, and device or push-notification identifiers where applicable.
Location information
We may process precise GPS location and coarse city or state location. A Driver's precise location may be used for navigation, route progress, proximity functionality, and location sharing with an authorized Dispatcher when applicable to an assigned active load.
Driver location is not public. Location sharing is limited to authorized or applicable operational use within Razor Dispatch.
Load and transportation information
We may process load information, pickup and delivery information, load status, assignments, requests, mileage, rates, equipment information, notes, and Driver or Dispatcher relationships.
Documents and user content
We may process bills of lading (BOL), proof of delivery (POD), PDF files, JPEG or PNG images, load-related documents, notes, and other content users provide.
Driver finance information
Driver finance functionality may contain earnings, expenses, mileage, fuel estimates, and operating calculations or reports.
Subscription and payment information
We may process subscription status, the applicable store and product, introductory or trial status, renewal status, and expiration or access dates. Razor Dispatch uses RevenueCat for subscription entitlement management, while Apple and Google process their respective store payments.
Razor Dispatch does not receive or store a customer's full payment-card number for Apple App Store or Google Play subscriptions.
Logbook information
We may process Driver duty-status and logbook information.
Razor Dispatch logbook functionality should not be considered an FMCSA-certified Electronic Logging Device unless Razor Dispatch expressly states that such certification has been completed.
Usage and diagnostics
We may process application interactions, feature usage, crashes, performance diagnostics, and push-notification identifiers to operate, maintain, and improve the service.
3. How we use information
We may use information to:
- Create, authenticate, and administer Driver and Dispatcher accounts.
- Provide loads, assignments, navigation, route progress, proximity features, documents, notifications, finance tools, and logbook functionality.
- Connect Drivers with authorized Dispatchers for applicable freight operations.
- Manage subscription access and restore eligible purchases.
- Respond to support, privacy, security, and account-deletion requests.
- Diagnose crashes, maintain performance, protect accounts, prevent fraud or misuse, and improve Razor Dispatch.
- Comply with applicable legal obligations and resolve disputes.
4. When information may be shared
Information may be shared with an authorized Dispatcher or Driver when needed for an applicable assignment, active load, or Driver/Dispatcher relationship. For example, a Driver's location may be available to an authorized Dispatcher when applicable to that Driver's assigned active load. Documents, load details, status, and related operational information may likewise be available to authorized participants.
We may also disclose information to service providers acting for Razor Dispatch, when required by law or a valid legal process, to protect rights and safety, to investigate fraud or security events, or as part of a business transaction subject to appropriate safeguards.
Razor Dispatch does not sell personal information to advertisers and does not use app information for cross-app advertising tracking.
5. Service providers
Service providers that support Razor Dispatch may include Apple, Google, RevenueCat, Twilio, TomTom, Supabase, Expo, PostHog, Sentry, Railway, and email delivery providers. The provider used, and the information it processes, depends on the feature or platform involved; this list does not mean every provider receives every data type.
These providers may support functions such as authentication, phone verification, mapping and navigation, application hosting and data storage, subscription entitlements, notifications, product operations, diagnostics, error reporting, and email delivery. Their handling of information may also be governed by their own terms and privacy notices.
6. Retention and security
We retain information for as long as reasonably necessary to provide Razor Dispatch, administer accounts, support transportation and audit history, meet legal or financial obligations, prevent fraud, maintain security, and resolve disputes. After account deletion, the timing and retention limits in the Account deletion section apply.
We use administrative, technical, and organizational measures intended to protect information. No storage or transmission method can be guaranteed to be completely secure, and users should protect their devices, credentials, and authentication codes.
7. Account deletion
Users may delete their account in the app through Profile > Delete Account, or request deletion by emailing support@razordispatch.com. Visit Account deletion for the full in-app steps and external request instructions, available without signing in.
For emailed requests, use the email associated with your account and include whether the account is a Driver or Dispatcher. Never provide your password, verification code, or payment information. Razor Dispatch may request limited identity confirmation before processing an emailed request.
Operational restrictions apply to both deletion methods while in-transit work is active:
- Driver: A Driver cannot delete their Razor Dispatch account while they have an assigned load with
IN_TRANSITstatus. - Dispatcher: A Dispatcher cannot delete their Razor Dispatch account while any load owned by that Dispatcher has
IN_TRANSITstatus.
Once the applicable in-transit activity is completed or resolved, deletion may proceed.
What is deleted
Account deletion removes the following data, subject to the retention requirements below:
- Account login credentials and active sessions
- Driver or Dispatcher profile information
- Contact and company-profile information not required for retention
- Current location and stored device/push-notification identifiers
- Notification preferences
- Uploaded documents and operational records that are not subject to a legitimate retention requirement
- Other personal data associated solely with the deleted account
Timing and retention
Eligible deletion requests are processed immediately when completed in the app or within 30 days when requested through support.
Residual backup copies may remain for up to 90 days before being overwritten through normal backup rotation.
Records required for legal obligations, accounting, fraud prevention, security, transportation or audit history, and dispute resolution may be retained for up to seven years, then deleted or anonymized when no longer required. Retained records are restricted to those purposes and are not used for advertising.
Subscriptions and deletion
Apple App Store: Deleting a Razor Dispatch account does not automatically cancel an Apple App Store subscription. Users must cancel it through Apple's subscription settings to prevent future renewal.
Google Play: Razor Dispatch may request cancellation of future Google Play renewal during eligible account deletion, but deletion does not promise a refund or immediate revocation of already purchased access.
Deletion of specific data
You may also request deletion of eligible specific data without closing your Razor Dispatch account. See Request deletion of specific data for email instructions. Eligible emailed requests are processed within 30 days, subject to retention requirements and safe removal during active operations.
8. Privacy rights and choices
Depending on the user's jurisdiction, they may be able to request access to personal information, correction of inaccurate information, deletion, or information about how their information is processed. These rights may be subject to verification, applicable exceptions, and operational or legal retention requirements.
To make a privacy request, email support@razordispatch.com. Please do not send passwords, authentication codes, full payment-card numbers, or secret credentials.
Device settings may provide choices for location access and notifications. Restricting a permission can prevent the corresponding Razor Dispatch feature from working as intended.
9. Children's Privacy
Razor Dispatch is a commercial trucking and logistics application and is not designed for children.
10. Regional availability
Razor Dispatch is initially available in the United States and Canada. Information may be processed in locations where Razor Dispatch and its service providers operate, subject to applicable safeguards and legal requirements.
11. Changes to this policy
We may update this Privacy Policy as Razor Dispatch evolves or legal and operational requirements change. When we do, we will post the revised policy and update its effective date. Material changes may also be communicated through the application or another appropriate channel.
12. Contact us
For privacy questions or requests, contact Razor Dispatch at support@razordispatch.com.