Privacy Policy

1. Operator and scope

BoxRoute is operated by SavX Ventures. This policy explains information handling for boxroutetech.com, the authenticated BoxRoute platform at savage.boxroutetech.com and its linked workspaces, and the BoxRoute Driver apps for iOS and Android.

For the app-specific policy, see BoxRoute Driver — Privacy Policy. The web platform supports Super Vendor, Broker and Trucking workflows. BoxRoute Driver supports driver workflows in Trucking. The information involved depends on the features you use, your organization and your role. Mobile-specific practices below describe BoxRoute Driver; they do not imply that every web module accesses your device permissions.

2. Information we handle

Public website and inquiries. Forms collect your name, email, company, inquiry type and message. Company is optional on the account-deletion request form. Email correspondence also includes the content and attachments you choose to send. Hosting processes IP addresses, request details, response status and technical logs. The form service uses temporary request counters and hashed network identifiers to limit spam and duplicate submissions.

Accounts and organizations. The platform processes account identifiers, names, email addresses, passwords for authentication, and company, role and permission information. Account records can also contain phone numbers, titles and administrative notes. Information comes from you, organization administrators and linked BoxRoute account services. Signing in to BoxRoute Driver with an existing BoxRoute account can create a linked Driver account.

Business records. Super Vendor and Broker workflows handle container inventory, availability, quotes, purchases, sales, orders, releases, business contacts, addresses, messages and associated documents. Trucking workflows handle loads, drivers, vehicles, pickup and delivery details, status updates, dispatch messages, bids, expenses and payment records. Your organization and relevant counterparties supply and update these records.

Mobile submissions. BoxRoute Driver sends submitted checklist and status information, container details, issue reports, dispatch messages, photos, delivery documents and signatures to the platform. Expense entries include amounts and any receipts you attach. Uploaded files and their metadata are linked to the relevant user and operational record. Information cached for offline work and pending uploads is also stored on the device.

Notifications and diagnostics. When mobile notifications are enabled and permission is granted, the app registers a push notification token, device platform and app environment with your account. If you choose to send a diagnostics email, the draft includes your account email, app version, device model, operating-system version and pending-sync count; you choose whether to send it. Services also generate technical and operational audit logs.

3. Why we use information

We use account information to authenticate users, connect their workspaces and apply access permissions. Operational information supports inventory and order management, release coordination, dispatch, delivery evidence, communications and the expense or mileage features in use.

Contact information lets us respond to inquiries and privacy requests. Push tokens deliver operational notifications. Technical records support troubleshooting, service operation and abuse prevention; audit records record changes to business information.

4. Providers and other recipients

Organization administrators and staff with the relevant permissions can access records needed for their work. Suppliers, brokers, customers, carriers and assigned drivers receive information through the orders, loads, messages and documents they participate in, according to the applicable workspace access rules. This is not a promise that all records are visible to all participants.

Google Cloud provides website hosting and backend storage infrastructure, including storage for uploaded documents. Website forms are delivered to support@boxroutetech.com through Google Workspace and become mailbox records. BoxRoute Driver uses Expo services for app updates and push delivery; notification delivery also involves Apple or Google platform services. Push delivery processes tokens and notification content.

When you open navigation from BoxRoute Driver, the destination is passed to Apple Maps or Google Maps. Configured platform route-distance features send origin and destination addresses to Google Maps. Your email and navigation providers handle the information you send to them under their own terms and privacy notices.

Operational documents can be distributed through file links. People who receive a working document link can have access to its contents; share links and documents only with appropriate recipients.

5. Device permissions and choices

Camera and selected photos. BoxRoute Driver requests camera access for container and delivery evidence. You can select a photo when using the photo picker. Granting permission alone does not upload your photo library: photos used in operational workflows are saved locally and uploaded with the relevant submission or queued sync. Container-number recognition processes the captured image on the device.

Location and mileage. When you start mileage tracking, BoxRoute Driver requests location permission and uses coordinates to calculate miles by state on the device. With background permission, tracking can continue while the app is not in the foreground, until stopped. The mileage sync sends state, date and distance totals; trip mileage also includes trip/load identifiers, journey-leg totals and revision information. These mileage functions do not upload the raw GPS coordinates. State-level mileage still reveals information about where work travel occurred.

You can stop tracking in the mileage screen and change location, camera, photo and notification permissions in device settings. Denying a permission limits the related feature. Disabling a permission does not erase information already submitted.

Device unlock. Optional Face ID or fingerprint unlock uses the device’s authentication service. BoxRoute receives the authentication result rather than the biometric template.

6. Cookies, local storage and similar technologies

The public marketing website serves its own fonts and images and has no advertising or third-party analytics integration in its current implementation. This statement applies to the public website, not to every service or SDK involved in the platform.

Authenticated web workspaces use browser storage for session tokens, user information and interface preferences. BoxRoute Driver stores session information, preferences, cached work, photos and queued changes on the device so work can continue through connectivity interruptions. The app uses device secure storage for its session token where available. Clearing browser or app storage can remove local preferences or unsynced work, but does not delete server records.

7. Retention and deletion

Information is held in different places: support emails in the support mailbox, account and operational records in platform databases, uploads in file storage, and cached or pending work on devices. Server-side account removal controls can mark records as deleted while retaining stored records and audit history. Signing out, disabling access or uninstalling an app is not the same as deleting an account and its associated data.

To ask which records are held about you, how long they are retained, or to request deletion, use the account and data deletion request page or contact support@boxroutetech.com. Identify the relevant account and service. This policy does not promise an automatic erasure process or a fixed completion period. The request form confirms that a request was sent, not that records have been erased.

8. Security

The public website uses HTTPS. Platform controls include authenticated sessions, password hashing, and role- and organization-based authorization. The website request service validates inputs and limits repeated submissions. These controls reduce risk but do not guarantee that every transmission, device or stored record is secure.

Keep your sign-in details private and secure devices used for BoxRoute. Do not send passwords, payment-card details or identity documents through the public contact forms.

9. Processing locations

The public website runs on Google Cloud in the United States. Accessing it from another country involves processing request information there. This hosting location does not establish the location of every platform database, uploaded file, mailbox or mobile service. Contact us for processing-location information relevant to your organization’s use.

10. Access, correction and deletion requests

Contact support@boxroutetech.com to request access to information about you, a correction, or deletion. You can also use the privacy request form or the dedicated deletion request form. No sign-in is required for these website forms.

Include the account email, service and organization concerned, plus a description of your request. If you cannot access the account email, provide an address where you can be contacted and explain that situation. Additional information can be needed to identify the correct records and verify your authority; do not send identity documents unless specifically requested through an appropriate process. Requests concerning shared company records need to take account of the organization and other people’s information.

11. Changes to this policy

We will update this page as BoxRoute’s features and information handling change. The last-updated date identifies this version. Review this page when you have questions about a service or a newly available feature.

12. Contact

Product: BoxRoute
Operator: SavX Ventures
Support and privacy: support@boxroutetech.com
Website: https://boxroutetech.com/