Privacy Policy
Last updated July 29, 2026
This Privacy Policy explains how [Company Legal Name](“we”) processes personal data in connection with eWall TMS(the “Service”).
1. Our role
For personal data about our direct users and account administrators (for example, name, email, and login activity), we act as a controller. For personal data a Carrier submits into the Service about its own drivers, customers, and contacts, the Carrier is the controller and we act as a processoron the Carrier’s behalf — those arrangements are governed by our Data Processing Agreement.
2. Data we process
Account and profile data
- Name, email address, and mobile phone number (when provided);
- a hashed password (we never store passwords in plain text);
- if you enable two-factor authentication, an encrypted authenticator secret and hashed recovery codes;
- SMS messaging preferences and opt-in / opt-out status;
- sign-in timestamps.
Usage and security data
- IP address and browser user-agent associated with sessions and security events;
- audit log entries recording significant actions (who did what and when) for security and accountability;
- SMS delivery metadata (for example, message status, timestamps, and carrier error codes) needed to send and troubleshoot texts.
Operational data submitted by Carriers
Carriers use the Service to manage their operations, which may include personal data such as:
- Driver data — name, contact details (including mobile numbers for dispatch and operational texts), employee identifier, date of birth, hire/termination dates, and qualification records including CDL number, class, state, and issue/expiry dates, endorsements, restrictions, medical-card expiry, MVR and drug-test dates, and Clearinghouse status;
- Business-contact data — names and contact details of customers, shippers, receivers, and brokers;
- Operational records — loads, stops and addresses, equipment, invoices, and driver settlements;
- Uploaded documents — compliance files (such as licenses and medical cards) stored in cloud object storage; and
- Vehicle location data— where a Carrier connects Motive, GPS positions and related telematics for the Carrier’s vehicles and drivers.
Payment data
When a customer pays an invoice online, payment is processed by Stripe. We receive the payment amount, status, and a payment reference; we do not receive or store full card numbers.
3. How we use data
- to provide, maintain, and secure the Service;
- to authenticate users and prevent fraud and abuse;
- to send transactional communications by email and, where you have opted in, by SMS (including invitations, verification codes, dispatch updates, and operational notices);
- to honor opt-out, help, and support requests related to messaging;
- to provide support and respond to requests; and
- to comply with legal obligations and enforce our terms.
4. Text messaging (SMS)
When you or your Carrier enroll a mobile number in eWall TMS Alerts, we process that number and related consent records to deliver program texts. Message types may include: account verification and security codes; driver invitations and onboarding links; load assignment, dispatch, and status updates; document, compliance, and settlement reminders; operational support notices related to the Service. Message frequency varies based on your role and activity in the Service. Message and data rates may apply.
- Opt-in: we send program texts only after prior express consent (for example, a checkbox or confirmation in the Service, a YES reply when required, or enrollment by a Carrier that has authorization to text that number). Consent is not a condition of purchase except where a message is required to complete a security or account action you requested.
- Opt-out: text STOP to the number that messaged you, use in-product SMS settings where available, or email support@example.com. We will process opt-outs promptly and send a one-time confirmation when required.
- Help: text HELP or contact support@example.com.
- No sale / no third-party marketing use: we do not sell personal data. We do not share mobile opt-in data or consent with third parties or affiliates for their marketing or promotional purposes. Phone numbers are shared with our SMS delivery provider only to transmit messages and manage delivery.
Full program rules are in our SMS Terms.
5. Legal bases
Where the GDPR or similar laws apply, we rely on: performance of a contract (to provide the Service); our legitimate interests (to secure and improve the Service); compliance with legal obligations; and consent where required (including SMS opt-in where applicable). For operational data processed on a Carrier’s behalf, the Carrier is responsible for establishing the legal basis.
6. Sharing and sub-processors
We do not sell personal data. We share it with service providers that process it on our behalf, under contract and only as needed to run the Service:
| Sub-processor | Purpose | Location |
|---|---|---|
| Motive (Keep Truckin, Inc.) | ELD / GPS vehicle location & driver data import for live tracking | United States |
| FMCSA QCMobile — U.S. Department of Transportation | Carrier lookup by USDOT/MC number | United States |
| Google Maps Platform (Google LLC) | Address autocomplete and mapping | United States |
| Microsoft Azure Communication Services | Transactional email and SMS delivery (invitations, verification codes, dispatch and operational notifications) | United States / European Union |
| Microsoft Azure Blob Storage | Storage of uploaded compliance documents | United States / European Union |
| Stripe, Inc. | Online invoice payment processing (card data handled entirely by Stripe) | United States |
We may also disclose data where required by law or to protect rights, safety, and the integrity of the Service.
7. International transfers
Our providers may process data in the United States and other countries. Where required, we rely on appropriate safeguards (such as Standard Contractual Clauses) for cross-border transfers.
8. Retention
We retain personal data for as long as an account is active and as needed to provide the Service, then delete or anonymize it within a reasonable period, unless a longer retention is required by law. SMS opt-out records may be retained as needed to honor your request and comply with messaging rules. Carriers control the retention of the operational data they submit.
9. Security
We use technical and organizational measures appropriate to the risk, including password hashing, encryption of authenticator secrets, hashing of session and reset tokens, role-based access control scoped per Carrier, audit logging, and encryption in transit. No method of transmission or storage is completely secure.
10. Your rights
Depending on your location, you may have the right to access, correct, delete, restrict, or object to the processing of your personal data, and to data portability. To exercise these rights, contact us at privacy@example.com. If your data was provided by a Carrier (for example, as one of its drivers), we will refer your request to that Carrier, who is the controller of that data. You may separately stop SMS as described in Section 4 without deleting your account.
11. Children
The Service is intended for business use and is not directed to children.
12. Changes
We may update this Policy; we will revise the “last updated” date and, where appropriate, provide additional notice.
13. Contact
Privacy questions or requests: privacy@example.com. SMS help: support@example.com.