Privacy Policy

This Privacy Policy explains how TRUCKTEC LLC, a Nevada limited-liability company (“we”, “us”, “our”), processes personal data in connection with Ewall Drive (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, and the time of each session’s last activity, used for security and service monitoring;
• 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.

Secure document links

When an invoice email cannot carry every document, a Carrier’s send can include a secure link to the documents instead. For these links we process:

• the email address of the recipient the Carrier sent the invoice to, and a record of the files in the link as they were sent (file names, document types, load references, and sizes);
• when someone opens the link, the IP address and browser user-agent of each code request, code verification, download, and attempt to open a link that is no longer available, along with download counts and the time of last access;
• the one-time code emailed to the recipient, which we keep only as a keyed hash and never in plain text; and
• one strictly necessary cookie, __Secure-tms-share, set only after the recipient enters a valid code. It keeps that recipient’s access session open for up to 45 minutes, is limited to that link’s address, and is not used for tracking or advertising.

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 and ELD data— where a Carrier connects Motive, in the Service or in CarrierDesk, GPS positions and related telematics for the Carrier’s vehicles and drivers, and the vehicle, driver (name, email, phone, and license number and state), and trailer records imported from Motive.

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 voluntarily provide or confirm your mobile number and explicitly opt in through Ewall Drive, we process that number and related consent records to deliver eWall TMS Alerts texts. Message types may include: account verification and security codes; driver invitations and onboarding links; load assignments and dispatch updates; pickup and delivery updates; load status changes and cancellations; document and compliance reminders; settlement reminders; important operational and account alerts. Message frequency varies based on your role and activity in the Service. Message and data rates may apply.

• Opt-in: We send SMS messages only after you voluntarily provide your mobile phone number and explicitly opt in through the public form at /sms-consent, or by providing or confirming a mobile number and opting in through Ewall Drive. SMS consent is collected using a separate checkbox that is unchecked by default and is shown at the same time the phone number is collected. Consent to receive SMS is optional and is not required to create or use an Ewall Drive account. Message frequency varies. Message and data rates may apply.
• Opt-out: Reply STOP to the number that messaged you or disable SMS notifications through Ewall Drive where available. We process opt-out requests promptly.
• Help: Reply HELP or contact sosa@ewallcapitalsolutions.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 infrastructure providers only as necessary 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:

We may also disclose data where required by law or to protect rights, safety, and the integrity of the Service.

A Carrier may also send load documents and invoices to a recipient the Carrier chooses (for example, its factoring company), as email attachments or through a secure link. A secure link is made for a single recipient address and is protected by a code emailed to that same address. It expires 30 days after it is created, and the Carrier can revoke it earlier; it is also revoked automatically when a newer send to the same recipient replaces it or when the invoice is voided. Files are delivered through the Service, not through public storage addresses.

If a Carrier also uses CarrierDesk, our related product, the two services can be linked so its owner can move between them with one sign-in. While they are linked, we share the Carrier’s company details (legal and trade name, USDOT and MC numbers, a tax ID only when it is an EIN, address, and phone), the owner’s name and email, and access to its Motive connection: the Service can read the Carrier’s Motive data through a connection made in CarrierDesk, and CarrierDesk can do the same with one made in the Service. The first time the owner opens the Service from CarrierDesk, if the Carrier has no trucks or drivers yet, the Service imports its active Motive vehicles, drivers, and trailers automatically; otherwise the owner chooses what to import. CarrierDesk support reviews link requests the system cannot match on its own, seeing the Carrier’s name, USDOT number, and status, and its owners’ email addresses in masked form. When the CarrierDesk owner’s email is not an owner of the Carrier, the link only takes effect after an owner of the Carrier signs in to the Service and confirms it. Confirming lets that CarrierDesk user open the Service as the confirming account without a password, and lets the confirming account open the CarrierDesk company. A link can be removed by contacting support; that does not delete the Carrier’s data in either 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.

Secure document links (the link record, the list of files as sent, its access sessions, and the related audit entries, including IP addresses and browser user-agents) are retained, are tied to the invoice they belong to, and are not deleted automatically when a link expires or is revoked. We do not keep a separate copy of the documents for a link: it refers to the documents already stored in the Service, so a document that is archived or deleted afterwards is no longer available through the link.

Records of CarrierDesk links (when a link was created, requested, approved, confirmed, rejected, paused, or removed, by whom, and why) are retained as audit history after the link is removed.

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.

For secure document links, the link’s address contains a long random token that we store only as a hash. Opening the documents also requires a one-time six-digit code emailed to the recipient’s address, which we store only as a keyed hash. A code can be tried a limited number of times, a link locks after repeated wrong codes, requests are rate-limited, and a successful code opens only a short access session for that one link. Pages and downloads for these links are not indexed or cached.

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 sosa@ewallcapitalsolutions.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: sosa@ewallcapitalsolutions.com. SMS help: sosa@ewallcapitalsolutions.com.