← Back to home

Privacy Policy

Effective date: September 22, 2026

This Privacy Policy explains how Gorilla Cargo LLC ("RoadDogTMS", "we", "us") collects, uses, and protects information through the RoadDogTMS application and website (the "Service"). It applies to office users, drivers using the driver portal, and visitors to our marketing site.

1. Information we collect

Account and company information: name, email, phone, company details (legal name, DOT/MC numbers, address) you provide when signing up or completing your company profile.

Operational data you or your team enter: loads, customers, drivers, trucks, trailers, invoices, payments, settlements, expenses, documents (including proof-of-delivery images, rate confirmations, and compliance records), and messages sent through the Service.

Driver-specific data: for drivers granted portal access, we store what your company enters for compliance purposes, which can include license and medical-card details. We do not collect or store Social Security Numbers for drivers, employees, or contractors — your company handles that outside the Service (for example, when preparing a 1099). Drug and alcohol testing records your company maintains under U.S. DOT rules (49 CFR Part 40) are kept confidential and are only released as Part 40 permits — for example, to the driver, to DOT or the National Transportation Safety Board as required by law, or with the driver's specific written consent.

Location data: if a driver enables live tracking for a load, we record periodic location pings for the duration tracking is on, tied to that load, so dispatch can see progress in real time. Location sharing is driver-initiated and can be turned off at any time.

Payment information: subscription payments are processed by Stripe; we do not store full card numbers on our servers. Freight payment records (amounts, methods, dates) entered by your team are stored as part of your operational data.

Signature requests: if your company sends a document (such as a rate confirmation or carrier agreement) for e-signature, we collect the signer's typed or drawn signature, name, and — for verification purposes — the IP address and browser used at the time of signing or declining. The signer does not need a RoadDogTMS account; this information is used solely to complete and verify that specific request.

Usage and device data: standard web log data (IP address, browser type, pages visited) collected automatically to operate and secure the Service.

2. How we use information

To provide the Service: running the application, generating documents (invoices, BOLs, settlements), sending notifications, and enabling the features your plan includes.

To communicate with you: service emails (invoices, payment confirmations, password resets, support replies) and, if you opt in, product updates.

To secure the Service: detecting fraud, abuse, and unauthorized access, and enforcing our Terms.

We do not sell Customer Data.

3. Artificial intelligence features

RoadDogTMS uses Anthropic's Claude API for specific, opt-in features: (1) reading a photo of a receipt you upload and prefilling an expense form with the amount, vendor, and date it detects, and (2) reading a rate confirmation document — either one you upload, or one your team forwards by email to your company's private, non-guessable alias address — and extracting broker, rate, stops, and load details to create a draft load. Both only run when you trigger them (by an upload or a forwarded email); nothing is applied automatically to other data in your account, and every field a draft load or expense contains is reviewed and can be edited by your team before it's treated as final. The AI's output is a starting point, not a final record.

We do not use Customer Data to train Anthropic's or any other third party's AI models.

4. Cookies and analytics

We use cookies and similar technology that are strictly necessary to operate the Service, such as keeping you signed in. On our public marketing pages, we also use Google Analytics to understand how visitors find and use the site — this collects standard web analytics data (pages visited, general location, device and browser type) governed by Google's own privacy policy. We do not run Google Analytics inside the authenticated application, where your operational business data lives.

A short notice banner on our public marketing pages lets first-time visitors know about this. Dismissing it only hides the banner itself — it does not change which cookies are set.

5. Third-party service providers

We share data with the following providers, only as needed to operate the features you use: Supabase (database hosting and authentication), Vercel (application hosting), Stripe (subscription billing), Resend (transactional email delivery, and — only for companies that turn this on — receiving rate confirmation emails forwarded to that company's private alias address), Google Maps/Places (address autocomplete, driving directions, and mileage calculation), Google Analytics (marketing-site usage analytics, see above), the U.S. Federal Motor Carrier Safety Administration's public API (carrier lookup during onboarding), the U.S. Energy Information Administration's public API (fuel price benchmarking, no personal data sent), Anthropic's Claude API (receipt-photo scanning and rate confirmation extraction — each only invoked when you use that specific feature), and Sentry (error monitoring — when the Service encounters an unexpected error, technical diagnostic data such as the error message, stack trace, and the page or request involved is sent to Sentry so we can detect and fix the problem; we do not configure Sentry to collect your IP address or cookies).

If you connect QuickBooks Online from Settings, invoice, customer, and payment data you choose to sync is sent to Intuit under your own QuickBooks account, governed by Intuit's own privacy policy. This integration is fully opt-in and can be disconnected at any time, which also revokes our access token with Intuit.

Each provider only receives the data necessary for its function and is contractually or by design restricted from using it for unrelated purposes.

6. Data security

Data is isolated per company using database-level row-level security, so one company's data is never visible to another. Sensitive credentials (like QuickBooks access tokens) and select sensitive company fields (such as your EIN and a vendor's tax ID) are encrypted at rest. Access to the Service requires authentication, and you can enable two-factor authentication (TOTP) on your account for additional login security. Administrative actions — including document signature requests and completions — are logged in an audit trail visible to company admins. No system is 100% secure, and we can't guarantee absolute security, but we design and review the Service with these protections as a baseline.

7. Data retention and deletion

We retain Customer Data for as long as your account is active, plus a limited period after cancellation to allow you to export data or reactivate. You can request deletion of your company's data by contacting us; some records may be retained longer where required by law (e.g., financial records) or to resolve disputes.

Drivers can request removal of their portal access and associated location-tracking history by asking their company administrator, who can deactivate portal access from the Service.

8. Your choices and rights

You can access, correct, or export most of your data directly within the Service. You can disconnect optional integrations (QuickBooks) and turn off location tracking at any time. Depending on where you're located, you may have additional rights under applicable law (such as the right to request deletion or a copy of your data) — contact us to exercise these.

9. Children's privacy

The Service is intended for business use by adults (drivers, dispatchers, and company staff) and is not directed at children. We do not knowingly collect data from anyone under 18.

10. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we'll provide notice (in-app or by email) before they take effect.

11. Contact

Questions or requests regarding this Privacy Policy can be sent to .