SALTR PILOT · UPDATED NOVEMBER 14, 2026
Your data and privacy
This page covers Saltr Customer, Saltr Driver and the browser Command Center used in Durango’s pilot. For questions about your data, contact the Durango office. The original Durango tracker, Dispatch and Blowout are separate services.
Account and delivery information
Sign-in uses your email and account identifier. Customer profiles save your name and phone number. You can also add a company name. Requests can include a receiving contact, site address, exact unloading pin, access instructions and notes. Driver profiles include contact and truck information. We keep order, pickup, delivery, issue and review records so the office can manage each load.
Tickets, unloading-area photos and delivered-pile photos are stored as delivery evidence. They may contain identifying information or embedded location metadata. Photograph only what is needed for the load. Opening an update records that you read it.
Who can see it
The office can manage operational records. Customers can see their own orders and permitted delivery proof. Approved, assigned drivers can see the contact, destination and load information needed for their deliveries. Uploads and order details require authorized access.
Company owners and administrators can save shared delivery sites, including their address, unloading pin and access instructions, and choose which accepted ordering supervisors may use each site. Supervisors see only their active assigned sites. A company can require these approved sites for new delivery requests. Each saved order keeps the site details used when it was submitted; changing a shared site does not change past orders.
Maps and sign-in services
Supabase handles account sign-in. Cloudflare-hosted services store Saltr records and photos. Network requests to these services include technical information such as your IP address.
Google Maps provides satellite maps and address lookup. The site address you enter is sent to Google to find its location. Maps display the destination and, when shared, the truck’s position. Opening navigation sends the selected destination to Google Maps.
When you type a billing street address, Google receives the address search text to offer suggestions. Choosing one fills the address fields; you can edit them before saving. Your billing contact and payment details are not sent with this search. Google Maps terms.
Google’s map software also processes technical and usage information, including device or SDK identifiers, map interactions and diagnostics. This is separate from Saltr’s optional truck-location sharing. See Google’s privacy policy.
Payment methods and company accounts
Saltr stores billing contact and address details, completed-order amounts and the history of amount approvals or correction requests. These records include the reviewed quantity, rate, freight, tax, credits, supporting notes, account and company identifiers, and decision times. Reviewing or approving an amount does not charge a payment method.
When payment collection is enabled and you choose to pay an approved order balance, Saltr sends the exact amount, currency, order reference and billing account references to Stripe Checkout. Saltr retains your checkout consent and normalized payment status, provider references, captured or refunded amounts, dispute indicators and receipt times. Payment checks can continue through signed provider notifications and background reconciliation. Full card and bank numbers stay with the payment provider. Device-local recovery records help check an interrupted attempt without creating another payment.
Just Add Water is the payment merchant for Durango salt orders. When payment setup is enabled and you choose to save a method, Stripe receives your account email, account name and billing details. You enter card or bank details on Stripe’s hosted page. Saltr stores provider references, your saving permission and its date, setup status, bank or card name, last four digits and card expiry. It does not store full card numbers, security codes or bank account/routing numbers. Saving a method does not charge it or authorize automatic charges.
Personal methods are tied to your verified sign-in account. For a company, only the owner and billing managers using their accepted account can manage methods. Ordering supervisors and company administrators do not receive billing access by default. Company owners, administrators and billing managers can see company orders; ordering supervisors can see requests they placed. Removing a method detaches it from the merchant’s Stripe customer after verification; the audit receipt remains. Provider records and shared company records need separate review for deletion requests. See Stripe’s privacy policy.
Truck location is a choice
Before pickup confirmation, the Driver app explains that confirming pickup starts location sharing for that active delivery. The phone still requires location permission. The office and that customer may see the latest position while sharing is active, including while the app is in the background. For a company-assigned load, the pickup notice also identifies the assigned trucking company’s managers. They can see the latest shared position only in a new sharing session with that disclosure, while the assignment and company memberships remain active. Existing sharing sessions are not automatically expanded to the fleet. Tap Stop location sharing to stop. Sharing also ends on delivery submission or sign-out, and its authorization expires after 12 hours. If permission or a current location is unavailable, the app shows that tracking is unavailable rather than displaying a claimed live position.
The last position is hidden after five minutes without an update. Saltr does not show a continuous route history. If you stop sharing while offline, Saltr rejects new points for that sharing session and retries cleanup when it reconnects. If cleanup cannot finish, the app shows a warning. The Customer app does not request your phone’s location; it still saves the site address and unloading pin you provide.
Delivery updates and phone alerts
Delivery updates are saved inside Saltr. Phone alerts are off unless you turn them on for your signed-in Customer or Driver account and allow notifications in your phone settings. When enabled, Saltr registers an app installation identifier, an Expo push token, the app role, phone platform and account identifier. Expo and the phone platform process that token to deliver alerts. Saltr’s lock-screen alert contains only a general delivery-update message; order, customer, destination and load details stay inside the signed-in app.
Opening an alert rechecks current account and load access before showing anything and records the update as opened. Turning alerts off, signing into another account or removing permission deactivates the registration. Registrations expire unless the app renews them, and invalid device tokens are disabled. Saltr keeps bounded provider status and audit receipts so the office can distinguish queued, accepted, rejected and uncertain alerts without resending an uncertain alert. Phone alerts do not prove that a load was picked up, delivered, read or accepted.
Photo copies and retention
After an online refresh, Saltr Driver keeps a protected, account-bound copy of only the driver’s assigned active loads for up to 12 hours so the release, destination, contact and instructions remain readable during a connection loss. An offline copy is visibly marked and cannot be used to claim, pick up, photograph, submit or share a location until the app reconnects and refreshes. Offered and completed loads are not copied. The saved load copy is removed on sign-out and an expired or altered copy is rejected.
Native apps keep unverified uploads in account-specific phone storage for retry. The website keeps retry copies in this browser, tied to the signed-in account. Signing out hides pending photos but does not erase them; signing back into the same account restores them when the service is reachable. You can remove local copies using the app’s controls. The website also lets you download browser copies. Clearing app or browser data can remove local copies. Keep originals until the office verifies receipt.
Server records and originals remain available for operational review. Automatic deletion periods for the pilot have not yet been set. Account deletion processing, provider copies and any required retention must be reviewed before the public store launch.
Requesting deletion
A saved request is not completed deletion. Contact Saltr support for help with your account.
Request account deletion
Request deletion of your Saltr account and associated personal data.
A saved request is not completed deletion. Contact Saltr support for help with your account.
Sign in to request deletionNeed help or cannot sign in? Contact Saltr support.