This Privacy Policy explains how TruckTA LLC ("TruckTA," "we," "our," or "us") collects, uses, discloses, retains, and protects personal information when you use TruckTA websites, web software, iOS or Android apps, driver tools, owner-fleet tools, onboarding, document, support, or related services (the "Services").
TruckTA is business software for trucking companies. A customer company usually decides why its driver, employee, contractor, load, equipment, and operational information is processed. In those situations, the company is the controller or business and TruckTA processes the information for that company. TruckTA is responsible for information it collects for its own account administration, security, billing, support, and service operation.
1. Scope and who should read this policy
This policy applies to TruckTA visitors, account users, drivers, fleet-owner users, company administrators, applicants completing company forms, and people who contact support. It does not govern a customer company's independent practices outside TruckTA.
If your employer, carrier, contractor, or another TruckTA customer supplied your information or enabled location sharing, contact that company first about its policies and legal authority. You may also contact TruckTA using the request methods below.
2. Information we collect
The information collected depends on the Services, company settings, permissions, and features you use.
- Account and contact information, such as name, email, phone number, password authentication records, role, language, company, and account status.
- Company and business information, such as legal and trade names, address, contacts, DOT or MC identifiers, settings, subscriptions, invitations, and authorized users.
- Driver, applicant, and workforce information entered by a company or individual, which may include address, date of birth, driver-license and medical-card information, emergency contact, qualifications, employment or contractor records, acknowledgments, initials, signatures, and uploaded documents.
- Load and operational information, such as assignments, routes, pickup and delivery details, customer or broker contacts, transported vehicles and VINs, statuses, notes, documents, photos, BOL or POD files, payment-method labels, prices, settlements, and activity history where authorized.
- Equipment and fleet information, such as trucks, trailers, plates, registrations, insurance, inspections, assignments, documents, maintenance, accidents, and violations.
- Financial and commercial information used by the business platform, such as subscription status, invoices, payment status, load revenue, driver compensation, deductions, settlement records, and billing-provider references. The mobile apps do not sell in-app purchases or subscriptions.
- User content and support information, including forms, files, photos, messages, feedback, issue descriptions, and communications you choose to provide.
- Device and technical information, such as IP address, browser and operating-system type, app version, device or installation identifiers, push notification token, timestamps, security events, request logs, crash or performance information, and cookie or session information.
- Public website and signup usage information collected only after analytics consent, such as marketing page paths without query parameters, page titles, referring sites without query parameters, resource article or category identifiers, selected calls to action, controlled form-start and failure categories, successful public contact actions, verified signup completion, approximate location derived from IP address, and browser or device characteristics.
- Authenticated product analytics information collected only after a separate product-analytics choice, limited to approved event names; stable module, app-surface, prior-surface, navigation, feature, action, UI-surface, coarse outcome, and search-result-type identifiers; broad role category; application language; opaque browser and company identifiers; and technical event identifiers needed to count consented sessions. Person profiles are disabled. Selected successful milestones also increment a separate first-party daily total that stores no company, person, browser, record, route, content, or financial identifier.
- Precise and approximate location, motion state, speed, direction, accuracy, capture time, assigned driver or truck, and device-health information when an authorized company enables TruckTA Drive and the user grants required device permissions.
- When you use the Map and truck navigation in the mobile app: precise location while the Map is open or a trip is running, the truck dimensions used for routing, the places you search for or select, and the route you request.
- Public and connected-source information, such as public FMCSA records and data you direct TruckTA to retrieve from an optional integration.
Medical-card information is used only as an authorized driver qualification or compliance record. TruckTA is not a medical device and does not diagnose, treat, cure, or prevent any medical condition. Consult a qualified healthcare professional for medical advice, diagnosis, or treatment.
3. Sources of information
- You, when you create an account, sign in, submit a form, upload a file, change a load status, enable a permission, or contact us.
- The TruckTA customer that invited you, linked your driver profile, assigned work or equipment, configured permissions, or supplied business records.
- Your device and browser when you use the Services.
- Service providers and optional integrations used to operate a feature you or your company enabled.
- Public government and commercial sources used for business verification or operational features.
Mobile app permissions and controls
The iOS and Android apps request device access only when it is needed for a feature. Camera or photo-library access is requested when you choose to capture or select an authorized upload. File access is used when you choose a document or save or share a requested download. Notification access is used for company, load, update, security, or location-service notices. Precise location while the app is in use is requested for the Map and truck navigation. Background location is requested only for the TruckTA Drive workflow described below.
You can decline an optional device permission or later change it in iOS or Android settings. Declining may disable the related feature but does not by itself delete your account or unrelated information. TruckTA presents its background-location disclosure before requesting the operating system's location permission.
Location Privacy NoticeDriver Location DisclosureApp Support
4. How we use information
- Provide, authenticate, secure, maintain, troubleshoot, and improve the Services.
- Operate company accounts, roles, invitations, driver workspaces, fleet-owner workspaces, and permission boundaries.
- Display assigned loads, equipment, documents, settlements, notifications, maps, and other authorized workflows.
- Collect and display assigned-truck location when TruckTA Drive is lawfully enabled, as described in the Location Privacy Notice.
- Process uploads, generate requested documents, deliver email or push notifications, and respond to support and privacy requests.
- Measure consented use of TruckTA marketing and public signup pages, understand which public pages and calls to action are useful, measure successful contact and verified account-creation outcomes, and improve website content and navigation.
- Measure consented use of the authenticated staff product through a controlled product-event taxonomy so TruckTA can understand module and app-surface adoption, navigation and explicit feature use, company and role cohorts, and successful workflow milestones; selected milestones are also summarized as identity-free daily totals for product improvement.
- Understand whether a customer workspace is being adopted through a restricted internal company-level summary built from existing latest-sign-in and audit records. The summary contains counts, broad time ranges, and broad non-financial work areas only; it does not expose individual users, customer records, exact activity times, content, or a drill-down.
- Prevent abuse, investigate security incidents, preserve auditability, enforce agreements, and protect users and the Services.
- Administer trials, subscriptions, web billing, customer relationships, and business records.
- Comply with law, valid legal process, and enforceable retention duties.
Connected email accounts for Load Opportunities
When an authorized user connects a mailbox for Load Opportunities, TruckTA uses Nylas to read email and identify load notifications. Gmail connections request Google account identity and read-only email access. This access covers the connected mailbox, so a dedicated notifications inbox can limit exposure of unrelated correspondence. TruckTA processes the mailbox address, sender and recipient details, timestamps, subject, message text or HTML, and headers to extract listing, route, vehicle, price, and broker details for that company's permission-authorized users.
Nylas handles provider authentication and mailbox delivery. TruckTA's hosting and database providers support processing and storage of the resulting records. TruckTA retains structured opportunities, connection metadata, and limited processing receipts; it does not retain raw email subjects, bodies, HTML, headers, attachments, mailbox passwords, or provider access tokens. Load Opportunity parsing is deterministic and does not send email content to an AI model. This integration does not send, modify, or delete email in the connected mailbox.
New and Dismissed opportunities are removed after six hours, and Contacted opportunities after 24 hours, under the queue's activity-based retention rules. Eligible activity may reset those deadlines. Inbound receipt metadata is retained for 30 days. A load created after an authorized review follows normal company load-record retention. Disconnecting a mailbox in Loads Settings revokes its Nylas access; it does not delete opportunities already created. Use Privacy Requests below to request deletion of associated information.
TruckTA will use and transfer information received from Google APIs only in accordance with the Google API Services User Data Policy, including its Limited Use requirements.
Google API Services User Data PolicySubprocessorsPrivacy Requests
SMS Communications and Mobile Information
TruckTA may process SMS for two non-marketing purposes: one-to-one conversations with TruckTA about inquiries, requested demonstrations, onboarding, support, and requested follow-up; and transactional operational communications sent by a TruckTA customer about a specific shipment or existing service relationship. Operational messages may concern vehicle readiness, pickup or delivery windows, appointments, location or access instructions, shipment exceptions, and requested follow-up.
For direct conversations with TruckTA, we may collect your mobile number, message content, communication history, and information you voluntarily provide. For customer operational messaging, we may also process the sender company, shipment or service context, recipient and contact details supplied by the customer, message drafts and content, timestamps, delivery and failure status, limited provider identifiers, and the authorized users who prepared, approved, or reviewed the communication.
TruckTA also processes consent and preference evidence, which may include the mobile number, consent status, consent date and time, capture source and method, disclosure version, identified sender, permitted message subject, opt-out or re-consent time, HELP request, and related company or shipment context. We receive this information from the recipient, the TruckTA customer and its authorized users, and telecommunications providers supporting delivery.
We use SMS information to verify consent, prepare and transmit requested operational messages, maintain authorized company communication history, prevent duplicate or unwanted sends, honor opt-outs, respond to HELP requests, investigate delivery failures or misuse, apply message and spend limits, support billing and audit, and comply with law and carrier requirements. We do not use operational SMS information for marketing, advertising, lead generation, or unrelated profiling.
For operational messages, the customer company generally determines the purpose and acts as the controller or business, while TruckTA processes the information to provide the selected messaging service. The customer company's permission-authorized users may see the operational message and its shipment context. Consent is specific to the identified sender and message subject and is not transferred between TruckTA companies.
If AI-assisted messaging is enabled, TruckTA may provide the selected model only the bounded communication and shipment context reasonably needed to prepare or interpret the operational message. The model does not receive telecommunications-provider credentials, choose the customer company, or authorize a load or appointment change.
TruckTA may disclose mobile information to the applicable customer company and use telecommunications, hosting, security, and AI service providers only as reasonably necessary to provide the requested messaging workflow. Mobile numbers, opt-in records, and text-message consent are not sold, rented, transferred, or shared with third parties or affiliates for their own marketing or promotional purposes, and providers may not use them for those purposes.
We retain message records according to the customer relationship, configured retention, security and audit needs, disputes, and legal obligations. Consent evidence is retained for as long as reasonably necessary to demonstrate authorization. After an opt-out, TruckTA may retain a minimal suppression record to prevent additional messages unless the recipient provides new valid consent.
Message frequency varies according to the active shipment or requested conversation. Message and data rates may apply. The initial message explains how to reply STOP to opt out. Reply HELP for assistance. Consent is not a condition of purchasing or using TruckTA services.
Separately, companies may connect their own RingCentral phone accounts to TruckTA through the optional RingCentral integration. Calls and text messages made through that integration are carried by RingCentral under the company's own RingCentral agreement — TruckTA is not the carrier. When a company enables communication logging, TruckTA stores call and message records for that company (phone numbers, timestamps, durations, short message previews, and notes written by company staff) as part of that company's business records, visible only within that company under its own permission settings. TruckTA does not store call audio; recordings remain in the company's RingCentral account and are streamed on demand.
Outbound AI Voice Calls
When a TruckTA company enables outbound AI Voice for a shipment, TruckTA processes the selected contact's phone number, the company and shipment context needed for the pickup, delivery, or linked-customer objective, company attestation versions and acceptance times, historical consent records, suppression status, call times and status, limited provider identifiers, usage, and a structured result for authorized company users. TruckTA does not collect a new recipient consent form for each Voice call. SMS consent and registration remain separate.
During a call, communications and AI providers process speech to recognize the recipient's words and generate spoken responses. TruckTA's baseline AI Voice service does not retain call audio or a full transcript. It may retain the structured result and operational metadata needed for company history, billing, safety, audit, consent, suppression, and troubleshooting. A company user's acceptance of TruckTA's terms is separate from the called party's consent to an AI call.
The company determines the selected operational purpose and recipient and is responsible for documenting consent, checking local calling hours, and honoring an opt-out. TruckTA restricts access by company and role, uses service providers to carry out the call, and may retain minimal suppression evidence to avoid unwanted future calls. Requests to access or delete information are handled under the Privacy Requests process, subject to applicable retention and legal obligations.
5. Location information
TruckTA Drive is a core fleet-operations feature for approved companies and jurisdictions. When it is enabled, TruckTA may collect precise assigned-truck location while the app is in use, in the background, while another app is open, while the screen is off, and, where the operating system permits, after the app leaves the foreground. Collection requires the applicable TruckTA disclosure, server authorization, assignment, and operating-system permissions.
Location is used for current fleet visibility, limited route and location history, operations, security, support, and reliability—not for advertising. Authorized company staff may view current location and permitted history. A currently authorized Fleet Owner may receive assignment-scoped current location and limited history. TruckTA does not sell location information.
The Map and truck navigation use precise location only while you use them, to show the truck, plan truck routes, and give turn-by-turn directions. After you start a trip, guidance can continue with the screen off or another app in front, and it stops when you end the trip. TruckTA sends this location, your searches, and route requests to Google's maps, routing, places, and navigation services, and sends the route to the U.S. National Weather Service to check driving alerts. Using the Map does not by itself share location with your company; company location sharing happens only through TruckTA Drive.
TruckTA Drive Location Privacy NoticeDriver Location Disclosure
6. How we disclose information
- To the customer company and its permission-authorized users, and to an authorized Fleet Owner only within the assigned fleet boundary.
- To service providers that host, secure, communicate, map, store, process, or support the Services under contractual and confidentiality obligations.
- To integrations selected or authorized by the customer or user, subject to that integration's terms.
- To comply with law, subpoena, court order, government request, or legal process, or to protect rights, safety, security, users, and the public.
- In a merger, financing, acquisition, reorganization, bankruptcy, or sale of all or part of our business, subject to appropriate protections.
- With your direction or consent.
TruckTA requires service providers and other processors handling personal information on TruckTA's behalf to protect it under contractual, confidentiality, security, and purpose-limitation obligations. TruckTA confirms that third parties with access to app user data must provide the same or equal protection described in this Privacy Policy and required by applicable app-store rules.
The disclosure categories above do not permit mobile numbers, opt-in records, or text-message consent to be sold, rented, transferred, or shared with third parties or affiliates for their own marketing or promotional purposes. The SMS section above describes the limited customer and service-provider processing needed to provide a requested messaging workflow.
7. No sale, targeted advertising, or cross-app tracking
TruckTA does not sell personal information. TruckTA does not share personal information for cross-context behavioral or targeted advertising, and the mobile apps do not use personal information to track users across other companies' apps or websites. TruckTA does not use precise location for advertising.
8. Cookies, analytics, sessions, and local storage
TruckTA uses cookies, secure session storage, and similar technology needed to sign users in, remember settings, protect requests, prevent abuse, and operate the Services. Mobile apps may store secure authentication sessions, language preferences, queued authorized uploads, update information, and location-service state on the device. Blocking essential storage may prevent the Services from working.
On TruckTA's production marketing pages and narrow public signup flow, TruckTA uses optional Google Analytics measurement, which visitors can decline. The Google Analytics tag loads for every visitor to these pages. Analytics storage is granted by default and stops when a visitor declines, except in the European Economic Area, the United Kingdom, and Switzerland, where analytics storage is denied until a visitor selects Accept analytics and TruckTA receives only cookieless measurement until then. Google LLC processes limited usage information as TruckTA's analytics provider so TruckTA can understand website traffic, marketing engagement, successful public contact actions, and verified account creation. Advertising storage, ad-user-data consent, ad personalization, Google Signals, and remarketing are not enabled for this measurement.
TruckTA does not intentionally send names, email addresses, phone numbers, street addresses, form contents, SMS contents, resource-search text, passwords, authentication information, verification tokens, TruckTA user or company identifiers, VINs, load information, documents, financial information, driver information, or other sensitive operational data to Google Analytics. Marketing page locations and referrers sent by TruckTA exclude query parameters. The signup flow does not send page views, login or invitation activity, authentication routes, or verification-link parameters.
Visitors can accept or decline analytics in the first-visit banner and can later change or withdraw the choice through Cookie & analytics settings, which appears in the public website footer and in the Privacy Center. A first-party consent cookie shares that choice across www.truckta.com and app.truckta.com without putting identifiers in links. Declining or withdrawing analytics consent removes analytics storage, so no analytics cookie or identifier is kept and Google receives only cookieless measurement of the pages viewed; it does not stop the pages being counted. Article-level view and link counts that TruckTA stores itself are recorded only after a visitor accepts, everywhere. Separately from Google Analytics, TruckTA keeps its own count of how many times each public page was viewed on each day. That count is an aggregate number only: it records no identifier, IP address, device or browser information, session, referrer, query string, or time of day, so it describes pages rather than people and is not affected by the analytics choice. Essential website and account storage is separate from this optional analytics choice. More information about how Google processes data from sites using its services is available at https://policies.google.com/technologies/partner-sites.
The authenticated production staff workspace offers a separate, optional PostHog product-analytics choice. The PostHog SDK is not loaded before acceptance. If accepted, TruckTA sends only allowlisted product event names and stable semantic identifiers for modules, app surfaces, the prior safe surface, selected navigation, explicit feature actions, broad UI surfaces, coarse outcomes, broad role category, application language, opaque browser and company context, schema version, and controlled onboarding steps. TruckTA does not send its user identifier or create PostHog person profiles. The opaque company identifier is also attached as a company group so authorized product analysis can compare tenants without sending company properties or display names. TruckTA configures this project to discard client IP data and does not enable autocapture, automatic page views, URL or referrer collection, form tracking, heatmaps, session replay, surveys, automatic exception capture, web-vitals capture, feature flags, or experiments.
TruckTA does not intentionally send names, email addresses, phone numbers, company display names, page URLs, raw paths, query parameters, link or button text, DOM content, search text, form or input values, customer or record identifiers, VINs, load or driver details, document names or contents, financial values, TruckTA AI prompts or responses, or other operational record content to PostHog. Approved sanitized technical exception events may contain only controlled source, surface, route-template, error-class, digest, operation, and reference categories; raw error messages, stack frames, and URLs are excluded. Product analytics is disabled for the public website, Owner Portal, Driver App, native apps, admin surfaces, demos, staging, previews, local development, support impersonation when detectable, and automated browser sessions when detectable.
When an accepted, allowlisted workflow milestone is sent, TruckTA may also increment a first-party aggregate for the UTC day and milestone type. That aggregate contains only the date, fixed milestone key, and total; it has no company, person, browser, record, route, content, exact event time, or financial dimension. Internal product-improvement views delay these totals, round them, hide low-volume results, and offer no customer drill-down.
Separately from optional PostHog analytics and the identity-free milestone total, authorized TruckTA administrators may view a restricted company-level adoption summary. It is calculated from latest sign-in timestamps and existing company audit records that TruckTA already keeps to authenticate accounts and preserve auditability. It returns only recent signed-in-user counts, broad recency ranges, aggregate action and active-day counts, a simple usage status, and broad non-financial work-area indicators. It does not create a new event stream or reveal a user, event, customer record, exact timestamp, content, location, document, route, provider identifier, or financial detail.
An eligible signed-in staff user can accept or decline in the first product-analytics banner and can later change or withdraw the choice under Settings > Security > Product analytics privacy. Withdrawing consent stops future product events and resets the local PostHog identity. The public website analytics choice and authenticated product analytics choice are independent.
9. Data retention
We keep personal information only for the period reasonably necessary for the purposes described here, the customer's instructions, security and audit needs, dispute resolution, or legal obligations. Retention differs by record type and may be affected by trucking, employment, tax, insurance, litigation-hold, and contract requirements.
Raw and derived TruckTA Drive location records are retained for no more than 30 days under the current approved product policy. Location disclosure acknowledgments may be retained for the customer relationship plus three years. Closed privacy-request case metadata may be retained for three years. These records do not extend the retention of raw coordinates.
When an account is deleted, TruckTA removes or de-identifies information that it is not required or permitted to retain. Information in backups may remain until normal protected backup rotation completes and is not returned to ordinary use. A customer may retain independent copies or have legal duties that TruckTA cannot override.
10. Account and data deletion
Signed-in mobile users can start an account-deletion request from Account settings. Anyone can use the public web deletion request. Account deletion means deletion of the account and associated personal information that TruckTA is not legally required to retain; temporary deactivation alone is not treated as deletion.
TruckTA may verify identity and authority, notify the customer company, preserve legally required business records, and use a cancelable safety hold before irreversible deletion. A last company Owner may need to transfer ownership or request deletion of the whole company account. Instructions and request status are provided during the process.
11. Your privacy choices and rights
Depending on where you live and our role for the data, you may have rights to know or access information, correct it, receive a portable copy, delete it, restrict or object to processing, withdraw consent, appeal a decision, or complain to a regulator. We do not discriminate for exercising applicable rights.
Submit a request through the public Privacy Requests page or email the privacy contact below. We may verify identity, authority, company relationship, and request scope. If TruckTA processes the information for a customer company, we may refer the request to or coordinate with that company.
12. U.S. state privacy disclosures
Where an applicable U.S. state privacy law covers TruckTA's processing, residents may use the methods above to exercise the rights provided by that law. TruckTA does not sell personal information or use it for targeted advertising. Authorized agents may submit requests where permitted, subject to verification.
13. International users and transfers
TruckTA LLC is based in Pennsylvania, United States. The Services may be listed in app stores worldwide, but particular features—especially employer or contractor location monitoring—are available only for companies and jurisdictions approved for production.
Information may be processed in the United States and other countries where TruckTA or its service providers operate. Where required, TruckTA uses appropriate contractual or other lawful transfer safeguards. Local privacy, employment, labor, and monitoring obligations remain the customer's responsibility for its workforce and operations.
14. Security
TruckTA uses administrative, technical, and organizational safeguards designed for the nature of the information, including authenticated APIs, company and fleet authorization boundaries, row-level database controls, encrypted transport, protected storage, revocable credentials, audit records, and restricted administrative access. No system is completely secure, and we cannot guarantee absolute security.
Do not send passwords, bank details, raw coordinates, identity documents, or private driver files through ordinary support email.
15. Children
The Services are for businesses and adults and are not directed to children. TruckTA does not knowingly collect personal information from a child under 13 and does not intend the mobile apps for anyone under 18. Contact us if you believe a child supplied information improperly.
16. Service providers
TruckTA publishes its current service-provider categories and named providers. Providers may change as the Services evolve. Optional providers process data only when the related feature is enabled.
17. Changes to this policy
We may update this policy when the Services, law, or data practices change. We will update the effective date and version above and provide additional notice when required. A material change to TruckTA Drive purpose, recipients, retention, or collection requires an updated in-app disclosure before further collection.
18. Contact us
For privacy questions or requests, use the public request form or contact:
TruckTA LLC 4387 W. Swamp Road #618 Doylestown, PA 18902 United States Phone: (445) 444-8870 Email: privacy@truckta.com Website: https://www.truckta.com