Privacy Notice

Last updated: 2026-10-27

This Privacy Policy describes how HaulForza LLC ("we", "us") operates HaulForza. This privacy notice explains what personal data we collect, why, who we share it with, and the rights you have.

1. Data we collect and why

• Account data (name, email, username, password hash, company and role) — to create and secure accounts and control access.
• Operational data you enter (loads, brokers, drivers, trucks, documents, payments, expenses, fuel and IFTA records) — to provide the Service.
• Uploaded documents and inbound messages (rate confirmations, BOLs, authorized email intake) — to route, classify and extract load data for your review.
• Support messages — to answer your requests.
• Payment data — Stripe customer and subscription identifiers and billing status in HaulForza. We do not store full card numbers. Stripe processes card payments and receives card details directly.
• Location and tracking data (GPS coordinates, accuracy, heading, speed, timestamps and tracking status) — when a driver is working an assigned load, to provide live load tracking, route history, ETA updates and operational visibility, and during truck GPS navigation to provide turn-by-turn guidance. On supported mobile devices, location may continue to be collected in the background while an active load is being tracked or while truck GPS navigation is active, including when the app is not on screen.
• Technical data (IP address, device identifiers, browser type, usage and error logs, audit events) — for security, fraud prevention, abuse detection and reliability.

2. Background location and live tracking

HaulForza uses background precise location for two core driver workflows: (1) Live Load Tracking during an active assigned load, so authorized company users and time-limited tracking-link recipients can see current load progress when the app is not on screen; and (2) truck GPS navigation, so turn-by-turn guidance can continue when the driver leaves the GPS screen or uses another app during an active trip. The app shows a prominent in-app disclosure before requesting background location. Device permission remains under the user's control. Load tracking is intended to stop when the active load ends. GPS navigation is intended to stop when the driver ends the trip. When the assigned truck has no ELD, background location also supplies that truck's fleet-map position and distance records until an ELD is connected for the truck. While a driver is assigned to a truck, the same location is also stored as IFTA distance evidence for that truck, including when an ELD is connected. Those IFTA points are kept apart from live-load tracking points.

3. Automated and AI processing

Documents you upload may be processed by AI models to extract operational fields. Results are shown for human review before they become records when the workflow requires review.

4. Google user data (Gmail Connect)

When a company administrator connects the company's Gmail mailbox in HaulForza (Integrations → Company Email), we request these Google OAuth scopes: https://www.googleapis.com/auth/gmail.send, https://www.googleapis.com/auth/gmail.readonly, https://www.googleapis.com/auth/userinfo.email, and openid.

• What we access and why. Send (gmail.send): only when the user confirms send in HaulForza, to send from the connected mailbox factoring packets (invoice, rate confirmation, and BOL/POD), Load Board broker emails (for example request details or make offer), and, when the platform operator has enabled carrier package email sending, carrier setup packets to brokers. We do not send bulk or automatic email. Read (gmail.readonly): (a) find recent messages with attachments that look like broker rate confirmations and import them into Rate Inbox for human review; (b) show replies in email threads the user started from HaulForza (for example Load Board broker emails). If the user declines read access on Google's consent screen, sending can still work; automatic import and reply tracking do not. Identity (userinfo.email, openid): confirm the authorized Google account matches the company mailbox the administrator entered.
• What we store and what we do not. Encrypted OAuth tokens (server-side only). For imported rate confirmations: sender, recipient, subject, snippet, and the qualifying PDF or image attachment. For app-started threads: sender, recipient, subject, plain-text body (up to 8,000 characters), and timestamps. Non-qualifying messages are not stored. We do not keep a copy of the full mailbox.
• AI processing. Gmail attachments we import are processed with the Google Gemini API only to extract load details for the user's review. Google user data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models, by us or by any provider.
• Use. Only to provide the Gmail Connect features described in the HaulForza interface. We do not use Google user data for advertising, retargeting, personalized ads, credit-worthiness, lending, or market research.
• Share. We do not sell Google user data or transfer it to advertisers, data brokers, or information resellers. It is processed only by our hosting and database providers (for example Supabase and Vercel) and the AI extraction service (Google Gemini API) to operate these features, or when required by law. Authorized users in the same company can see imported load documents and thread messages.
• Human access. HaulForza personnel do not read Google user data unless the company gives us permission for specific messages (support), it is needed for security or to investigate abuse, to comply with law, or the data is aggregated and anonymized and used for internal operations in accordance with applicable law.
• Revocation and deletion. Disconnecting Gmail in HaulForza revokes our access at Google and deletes stored tokens. You can also remove access at https://myaccount.google.com/connections. Imported load documents and thread messages remain as company records until you delete them in the app or request deletion by emailing haulforza@gmail.com (OAuth consent screen support email).

HaulForza's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5. Who we share data with

• Cloud hosting, database/storage, email delivery, AI processing and support providers.
• Stripe, Inc. for card payment processing of subscriptions.
• Integrations you explicitly connect, such as ELD or email providers.
• Professional advisers and authorities where required by law.

We do not sell personal data.

6. International transfers

Data may be processed outside your country. Where required, appropriate legal safeguards are used for international transfers.

7. Retention

Operational data is retained while the account is active and may remain available for a limited export period after termination, subject to legal, billing, security and backup requirements.

8. Security

We use measures including encryption in transit, protected integration credentials, tenant isolation, least-privilege access and audit logging for sensitive actions.

9. Your rights and account deletion

Depending on your location, you may have rights to access, correct, delete, restrict or port personal data, object to certain processing, or withdraw consent. You can initiate an account-deletion request at https://www.haulforza.com/delete-account or contact support@haulforza.com.

10. Cookies and local storage

We use necessary cookies/browser storage for sign-in, language, theme, selected company and PWA/offline support. We do not use advertising cookies.

11. Contact

HaulForza LLC — 1213 Costa Brava Dr, Brownsville, TX 78520 — support@haulforza.com