Privacy Policy

This Privacy Policy explains how BMM Media Group LLC ("Mesa TMS", "we", "our", or "us") collects, uses, and discloses information when you use our Mesa TMS yard management software and the Mesa TMS Driver mobile application (together, the "Service").

This policy applies to the Service operated at mesatms.com and any customer-specific subdomain such as <customer>.mesatms.com.

1. How Mesa TMS is structured

Mesa TMS is sold to trucking carriers and intermodal yard operators ("Customer"). Each Customer is provisioned a dedicated, isolated software instance (the "Customer Instance") that they administer.

• Mesa TMS is the software vendor.
• The Customer is the data controller for all yard data, driver identities, and gate moves stored in their Customer Instance.
• Drivers and dispatchers ("End Users") interact with the Customer's instance through the dispatcher web app or the Mesa TMS Driver mobile app.

Mesa TMS does not access, sell, or share End User data with any third party. All data lives in the Customer Instance under the Customer's control.

2. What we collect

2.1 — Information you provide directly

When you sign up as a dispatcher or driver, you provide:

• Email address (login and dispatcher communication)
• Full name (so dispatchers know who's logging gate moves)
• Phone number (drivers only, for dispatcher verification)
• Password (stored as a salted SHA-256 hash, never the plaintext)
• Driver code + unlock PIN (issued by your dispatcher; stored as hashes)

2.2 — Information generated during normal use

When a driver logs a gate move via the mobile app: container number, order/BL number, chassis number, SSL, size, type, load state, seal number, optional notes, optional photo, submission timestamp, driver code, and IP address.

When a dispatcher uses the operator board: yard configuration, driver roster, container records and event log, and uploaded container photos.

2.3 — Information we collect automatically

Standard web server logs (IP address, user agent, timestamp, endpoint, HTTP status). These logs live in the Customer Instance and are typically retained for 30 days.

2.4 — Information we do NOT collect

• Precise location / GPS
• Contacts, calendar, browsing history
• Microphone or background audio
• Behavioral advertising data
• Third-party analytics or trackers

3. How we use the information

We use End User information only to operate the Service for the Customer who employs you: authenticate sign-ins, display gate moves, send AI-OCR (Anthropic Claude) requests when you upload a container photo, maintain a 14-day driver-submission history visible only to you and your dispatcher, and generate aggregate reports for your dispatcher.

We do not use End User data for advertising, profiling, model training, or sale to third parties.

4. Third-party processors

Anthropic does not train its models on your data. Anthropic's API terms prohibit using customer data for model training.

5. Data retention

• Dispatcher session tokens: 8 hours
• Driver session tokens: 14 days
• Driver submission history visible in-app: 14 days
• Container records on the yard board: indefinitely (Customer decides)
• Server access logs: 30 days
• Backup snapshots: 5–30 daily depending on Customer plan

6. Your rights

You may have the right to access, correct, delete, or export your personal data, and to lodge a complaint with your local data protection authority. Because Mesa TMS is a processor for Customer data, direct your requests to your dispatcher first. If they cannot resolve it, contact us at the address below.

7. Children

Mesa TMS is a business tool for licensed commercial drivers and dispatchers. It is not directed to anyone under 18 and we do not knowingly collect data from children under 13.

8. Changes

We may update this policy. When we do, we'll update the "Last updated" date above and, for material changes, notify Customers via email.

9. Contact

BMM Media Group LLC
Email: privacy@mesatms.com
Support: support@mesatms.com