Overview
WixCargo processes company and operational information to provide carrier software — not to monetize your data through advertising. This policy describes what we collect, why we collect it, and the choices available to you.
Privacy inquiries: privacy@wixcargo.com
Roles
- Account owners and carrier staff: For registration and billing, we act as a controller. For operational data you store in the application (loads, drivers, invoices, documents), we act as your processor, handling data on your instructions.
- Drivers using the portal: The motor carrier is generally the controller of driver information. We process uploads and messages according to the carrier’s instructions.
Information we process
We collect information needed to operate the service:
- Account details — name, email, hashed password, optional Quick ID / passkey public credentials (credential identifiers and public keys; private keys never leave the user’s device), role, company association, and terms acceptance
- Company profile — legal name, DOT/MC, EIN, address, payment settings, integration configuration
- Billing records — subscription status, plan pricing, trial dates, invoice history, and payment method type and last four digits (full card numbers are stored by our payment provider, not on our servers)
- Operational records — loads and estimates, brokers/clients, drivers (contact information, CDL, pay settings), trucks and trailers, invoices, expenses, settlements, documents, dispatch and driver chat (including optional voice notes), incident reports, uploads, and optional backhaul match activity
- Location and tracking — when enabled, live or last-known GPS coordinates from a driver’s smartphone (for example Telegram live location), optional heading/speed and stop metadata, and fleet telematics when you connect Samsara or Motive. Location is shown to authorized staff on load maps and may support operational status updates. We do not sell location data.
- Route weather and fuel estimates — when you view or save a truck route, we may request weather forecasts along that path and published diesel prices to estimate fuel and related costs. These are operational planning tools for carrier staff.
- Driver portal — optional PIN (stored as a secure hash), trusted device and network identifiers, optional Quick ID / passkey public credentials for that driver, upload files, and chat messages when drivers use their carrier’s portal link
- Broker tracking — when you share a public load tracking code with a broker assigned on that load, we store a first-party cookie so the tracking site can show their loads and invoices with your company and accept rate-change or invoice-dispute requests for your review. No separate broker login is required.
- Driver Telegram — when enabled, drivers may connect a Telegram account for load prompts and live location through Telegram’s application. Message content and location sharing are controlled by the carrier and the driver.
- Driver SMS — when enabled, we send messages to the phone number on the driver profile through Twilio, including document requests and a portal link. Content and recipients are controlled by the carrier. See Driver SMS and mobile numbers below.
- Optional document import — when rate-confirmation AI import is enabled, document content you submit may be processed by configured AI providers solely to extract load fields into your workspace
- Language preference — selected workspace language (English, Spanish, Romanian, or Russian)
- Technical logs — IP address, browser type, session cookies, security events, and integration sync metadata
How we use information
We use data to:
- Deliver, secure, and improve WixCargo
- Bill subscriptions and process payments through our payment provider
- Operate integrations you enable
- Send notifications you configure (including optional driver SMS)
- Provide support
- Prevent fraud, abuse, and unauthorized access
- Meet legal obligations when required
We do not sell personal information or use your carrier data for unrelated advertising.
Driver SMS and mobile numbers
When a carrier enables Driver SMS through WixCargo, we process mobile phone numbers to deliver operational text messages on the carrier's behalf through our SMS provider, Twilio.
What we collect
- Mobile phone numbers stored on a driver profile in the carrier workspace.
- How numbers are collected: A dispatcher or other authorized carrier staff enters or updates the number on Add Driver / Edit Driver and must check an SMS consent box that is unchecked by default. Drivers may also enter or update their contact phone in driver portal Settings and must check the same unchecked-by-default consent box. Hosted screenshots of both opt-in screens: https://wixcargo.com/sms-opt-in. The carrier is responsible for confirming the driver has agreed to receive texts before the number is saved for SMS.
Why we send texts
Carriers use Driver SMS for operational messages only, such as:
- Document and upload requests (BOL, POD, and other load paperwork)
- Load status and assignment updates
- Dispatch notices and chat alerts routed by SMS
- Portal links so drivers can upload documents or view load details
- Safety-related notices configured by the carrier (for example, drug-test scheduling where enabled)
We do not use driver mobile numbers for unrelated marketing or promotional campaigns.
Non-sharing for marketing
We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes.
We do not sell, rent, lease, or share mobile phone numbers or SMS opt-in/consent records with third parties or affiliates for marketing or promotional purposes.
Limited sharing to operate the program
We may share mobile numbers only with subprocessors and service providers who help deliver the SMS program — including Twilio as our SMS delivery provider — under contractual confidentiality and data-processing obligations, and only as needed to transmit messages, maintain delivery logs, honor opt-out requests, and operate the technical infrastructure. See Subprocessors below.
Opt-out
Drivers may opt out at any time by replying STOP to a message sent through the program. After a valid STOP request, we send one confirmation text and stop further operational SMS to that number unless the driver re-subscribes (for example by replying START) or the carrier updates consent in accordance with applicable law. Carriers may also disable Driver SMS for their workspace in Integrations.
Message frequency and rates
Message frequency varies based on operational activity (for example, when dispatch sends a document request or load update). There is no fixed monthly message count. Message and data rates may apply.
Contact
Questions about the SMS program may be directed to privacy@wixcargo.com or support@wixcargo.com. Drivers who have questions about texts from their carrier should contact that carrier's dispatch or office first — the motor carrier is the sender of operational messages.
EEA, UK, and Switzerland
Where GDPR or UK GDPR applies, we process data on the bases of contract, legitimate interests (security, product improvement, fraud prevention), consent where required (for example non-essential cookies), and legal obligation.
U.S. state privacy rights
Residents of California, Colorado, Connecticut, Virginia, Utah, and other states with comprehensive privacy laws may have rights to know, access, correct, delete, port, and opt out of certain processing.
We do not sell personal information or share it for cross-context behavioral advertising under the CPRA and similar laws.
Subprocessors
We use service providers to host and operate WixCargo. Stripe processes subscription payments and stores card details on our behalf. Current subprocessors:
| Vendor | Purpose | Location |
|---|---|---|
| Stripe | Subscription billing, invoicing, and secure card processing | United States |
| Twilio | Driver SMS delivery, opt-out handling, and message logs when enabled by a carrier | United States |
| Telegram | Driver bot messaging and live location sharing when enabled by a carrier | Global |
| Mapbox | Geocoding, truck routing, and route miles for operational estimates | United States |
| OpenStreetMap / OSM contributors | Map tiles and geocoding fallback | Global |
| Intuit QuickBooks | Accounting sync (optional) | United States |
| Samsara | Fleet telematics (optional) | United States |
| Motive | Fleet telematics (optional) | United States |
| xAI / Groq (configured AI providers) | Optional rate-confirmation document field extraction when enabled by the platform | United States |
| U.S. Energy Information Administration (EIA) | Published diesel price lookups for fuel estimates | United States |
| FMCSA / DOT public APIs | Broker authority lookups | United States |
| Open-Meteo / U.S. National Weather Service | Route weather forecasts and fuel-estimate adjustments | EU / United States |
| Email delivery (SMTP / Resend) | Transactional email | Varies by configuration |
| Bunny Fonts CDN | Web font delivery | Netherlands |
| ALTCHA (self-hosted) | Login bot protection (proof-of-work, first-party) | Your server / same region as hosting |
When you manage billing, you may visit Stripe-hosted pages governed by Stripe’s privacy policy. We may also disclose information when required by law or to protect safety and rights.
International transfers
Data may be processed in the United States and other countries where our infrastructure and subprocessors operate. Where required, we use appropriate safeguards, including Standard Contractual Clauses (SCCs) and supplementary measures.
Retention
We retain information while your account is active and for a reasonable period afterward for backups, disputes, and legal requirements. Activity and sync logs are trimmed over time. Use Settings → Data & backups to export and archive records on your schedule.
Your rights
Depending on jurisdiction, you may have rights to access, correct, delete, restrict, or port data, or to object to certain processing.
- Carriers may export company data from Settings → Data & backups
- Individual users may update profile details from Profile
- Privacy requests: privacy@wixcargo.com. We respond within applicable timelines (for example, 45 days under CPRA, 30 days under GDPR where applicable)
Security
We apply industry-standard controls: encryption for integration secrets and sensitive financial fields, tenant isolation, role-based access, self-hosted bot protection on login, and signed URLs for sensitive files.
Quick ID (passkeys / WebAuthn). When enabled, WixCargo stores only public credential material and device labels needed to verify sign-in. Biometric unlock (Face ID, fingerprint, or device PIN) is performed by the operating system or browser on the user’s device; we do not receive biometric images or templates. Users can remove Quick ID devices from Profile, platform Security, or driver Settings at any time and continue signing in with password or portal PIN.
No system is perfect. We treat operational data with the care a carrier business requires.
Children
WixCargo is business software directed at carriers and their staff, not children under 16 (or the minimum age in your jurisdiction).
Cookies
See our Cookie Notice for details on browser storage used by the product.
Policy updates
When this policy changes, we post a new effective date. Significant changes may require renewed consent where the law requires it.