This Privacy Policy explains how Tiriel collects, uses, stores, and shares information when you use the Tiriel AI platform. It applies to dispatcher subscribers, to the owner-operators and drivers the platform's AI agents contact, and to freight brokers whose information is processed in the course of providing the Services.
Tiriel, Inc. ("Tiriel," "we," or "us") is a Delaware corporation at 2261 Market Street STE 4462, San Francisco, California 94114. This Privacy Policy explains how we collect, use, store, and share information when you use the Tiriel AI platform ("Services").
This Policy applies to: (a) registered dispatcher subscribers; (b) owner-operators and drivers contacted by the platform's AI agents; and (c) freight brokers and other third parties whose information is processed in the course of providing the Services.
With respect to the personal information of owner-operators, drivers, and brokers, Tiriel acts as a service provider to the dispatcher subscriber who manages the relationship and processes that information on the dispatcher's behalf to provide the Services. Tiriel does not use that information for its own commercial purposes except as expressly described in this Policy and as permitted under applicable law. The terms governing that service provider relationship, including the restrictions on retention, use, disclosure, and combination of personal information required by applicable law, are set forth in our Terms of Service and in any data processing addendum executed with the dispatcher subscriber.
When you register and use the Services, we collect your name, business name, email, phone number, account credentials, and subscription payment information. We also collect the operational configurations and preferences you set in the platform, including owner-operator contact lists, dispatch preferences, and authorization settings.
We do not store full payment card numbers. Card and bank account details are collected and processed directly by our payment processor, and Tiriel receives only tokenized references, the last four digits, card brand, expiration, and transaction outcomes.
The platform's AI agents automatically collect the following during the course of providing the Services:
Owner-operator and driver data: name, phone number, current U.S. location (city and state, self-reported), truck loaded or empty status, movement direction, available ELD and HOS driving hours, voice call audio recordings and transcriptions, WhatsApp and email message content, and communication history.
Owner-operator and carrier credential and equipment data: USDOT number, MC number where applicable, entity and authority records, certificates of insurance and policy details, and vehicle identifiers including Vehicle Identification Number (VIN) and internal unit or truck number. Vehicle identifiers are extracted from the insurance and authority documentation submitted during verification and are used to identify each operating unit, to prevent duplicate registration of the same unit, and to determine the number of Seats occupied on a subscriber's account for billing purposes as described in our Billing, Pricing & Refund Policy.
Freight broker data: name, MC and DOT number, contact details, load posting data, Rate Confirmation documents, email communications, FMCSA authority and insurance status, and payment reliability signals.
Load and transaction data: load identifiers, origin and destination, equipment, weight, commodity, negotiated rates, deal records, Rate Confirmations, activation records, and incident records (detention, layover, TONU, lumper).
Shipping documents: Bills of Lading, scale tickets, Proofs of Delivery, lumper receipts, and cancellation notices, stored as immutable versioned artifacts.
Identity verification data: the questions the platform asks to confirm that the person on a call is the person it intended to reach, and the responses given, matched against information already on file for that person. No biometric identifier is created. See Section 4.1.
Consent and authorization records: the attestations, opt-ins, opt-outs, and revocations recorded through the platform, together with the dispatcher identifier, recipient identifier, timestamp, IP address, and the version of the terms then in effect.
Platform usage data: IP addresses, device and browser type, session data, and platform telemetry.
Where you connect a third-party account to the platform, we collect the following:
Load board accounts. Search criteria you configure, load postings returned, and the authorization token issued by that load board. We do not receive or store your load board password.
Email accounts. The content, headers, attachments, and metadata of messages in that account that relate to your dispatch operations, including messages exchanged with freight brokers, and messages the platform sends from that account on your behalf. We do not access messages unrelated to your dispatch operations. We do not receive or store your email password.
Google accounts. Where you connect a Google account, Tiriel's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not use Google user data to develop, improve, or train generalized artificial intelligence models, and we do not sell or transfer it for advertising, credit assessment, or lending purposes. Human access to Google user data occurs only with your consent, for security purposes, to comply with applicable law, or where the data has been aggregated and anonymized.
Where you install the Tiriel Browser Extension and use it on a load board page, we collect the load details you send to the platform through it, together with the source page address and the time of the action. The Extension transmits information only when you act to send a load, and does not monitor your browsing.
We receive load data from load board APIs (DAT, Truckstop, 123Loadboard, and others), authority and insurance data from FMCSA and public databases, vehicle specification data from the National Highway Traffic Safety Administration's public vehicle information API for the purpose of validating vehicle identifiers, and broker payment reliability signals from commercial data sources.
We do not process sensitive personal information as that term is defined under the California Consumer Privacy Act. In particular:
We do not use any information for the purpose of inferring characteristics about an individual.
We use information to: provide and operate the Services, including all AI agent functions; conduct compliance and fraud prevention, including entity verification and risk decisioning; improve and personalize the platform's AI models based on operational outcomes and dispatcher preferences; maintain platform security and prevent abuse; determine Seat occupancy and process billing and subscriptions; provide customer support; and comply with legal obligations.
We may use aggregated, anonymized data derived from platform usage to improve the Services and develop new capabilities. Such data does not identify you or any individual.
We may use operational data, including negotiation outcomes, load acceptance patterns, route data, and dispatcher preferences, to train, validate, and improve Tiriel's AI models only after such data has been deidentified or aggregated so that it no longer identifies, and cannot reasonably be linked to, any individual. We maintain measures to prevent reidentification and do not attempt to reidentify such data. Individual dispatcher data is not provided to third parties in identified form and is not used to develop AI capabilities made available to other users in a manner that identifies you. AI model improvements derived from such deidentified or aggregated data are proprietary to Tiriel. Because deidentified or aggregated data is not personal information, data already incorporated into AI model weights in that form is not subject to deletion requests under applicable privacy law.
Information received from a connected email account is used only to operate the Services for you. It is not used to train, validate, or improve Tiriel's AI models, whether in identified, deidentified, or aggregated form.
The platform records voice calls between its AI agents and owner-operators and freight brokers, including calls made during rate negotiation and incident resolution.
For owner-operators and drivers, the platform obtains documented prior consent before any call is placed, through the notice and authorization flow described in Section 4.2. The consent page identifies the agent as an automated system using an artificial voice, explains on whose behalf and from what number it will call and what information it will ask for, states that calls and messages are recorded, and offers accept and decline options of equal prominence, in the individual's language. The platform preserves an immutable, time-stamped record of the exact text and language shown and the decision made. Calls to a consented individual open with the agent identifying itself and the dispatcher it calls on behalf of, and do not repeat a per-call recording announcement. If the person on the call is not the consented individual, the agent delivers the full audible disclosure described below or continues without audio recording. The agent truthfully confirms that it is an automated system whenever asked. Revocation is governed by Section 4.4.
For calls not covered by documented prior consent, including calls with freight brokers: before each call is placed, the platform detects whether the destination number is subject to a two-party-consent requirement based on the number's associated state. Numbers that cannot be definitively mapped to a one-party state, including VoIP, toll-free, ported, and mobile numbers, are treated as requiring notice. For all calls subject to a notice requirement, the AI agent delivers an audible disclosure embedded in the opening statement, identifying itself as a dispatch assistant and stating that the call is being recorded. The disclosure is delivered in the language of the call. If a call participant objects to recording, the platform disables audio recording for that session, continues in metadata-only mode, and delivers a written summary to both the dispatcher and the participant by WhatsApp or email. Call recordings and transcripts are stored as immutable artifacts linked to the relevant load record, used for milestone verification, dispute resolution, quality assurance, and AI improvement. Transcripts are subject to automated PII redaction before storage.
Dispatcher subscribers are responsible for ensuring that the call-recording notice and the platform's consent flow are legally sufficient in each jurisdiction where their owner-operators operate and for obtaining any additional consent required under applicable state law. Tiriel does not represent that the call-opening announcement or the consent flow satisfies the specific requirements of any particular state.
The platform also sends automated WhatsApp messages, via Meta's WhatsApp Business API, and emails to owner-operators and brokers. Dispatcher subscribers are responsible for ensuring that message recipients have provided all legally required prior express written consents. Separately, the platform sends SMS messages containing verification codes, via Twilio, only to registered account holders who have requested a code at that moment. The AI agents do not contact owner-operators or brokers by SMS.
Where the platform needs to confirm that the person on a call is the owner-operator or driver it intended to reach, it does so by knowledge-based and documentary verification, asking questions whose answers are already on file for that person, and checking the responses against that record.
The platform does not create, capture, use, store, or disclose voiceprints, facial geometry, or any other biometric identifier or biometric information for the purpose of identifying an individual. Call audio is recorded and transcribed for the operational purposes described in this Section and is not processed to derive a biometric template or voice model of any individual. We do not process biometric information within the meaning of the Illinois Biometric Information Privacy Act (740 ILCS 14), the Texas Capture or Use of Biometric Identifier Act (Tex. Bus. & Com. Code § 503.001), Wash. Rev. Code § 19.375, or the California Consumer Privacy Act.
Before the platform contacts an owner-operator or driver, the dispatcher sends that person an introduction message from the dispatcher's own messaging account. That message contains a link to a page that identifies the dispatcher, describes how the AI dispatch assistant works, identifies it as artificial intelligence, links to this Policy, and allows the recipient to authorize contact or to decline it. We record the recipient's response together with the date, time, IP address, and the version of the notice displayed.
Verification codes. The platform sends SMS messages containing one-time verification codes, delivered by Twilio, only to registered account holders who have requested a code at that moment. These messages are not marketing, are not recurring, and are not used to contact owner-operators or brokers for dispatch purposes. Message and data rates may apply. Reply HELP for help, or email support@tiriel.ai. Carriers are not liable for delayed or undelivered messages.
Mobile information. Mobile phone numbers collected from owner-operators, brokers, and other recipients of platform communications are not shared, sold, or rented to any third party or affiliate for marketing or promotional purposes. Mobile information is shared only with the sub-processors strictly necessary to place a call or deliver a message, under contracts that prohibit secondary use.
A request by any recipient to stop receiving automated calls, emails, or WhatsApp messages, made by any reasonable means including telling the AI agent on a call or replying in a WhatsApp message, is recorded against that recipient's identity and is maintained in a suppression record separate from any individual unit, account, or load record. A revocation persists regardless of any subsequent change to the dispatcher's account, including pausing, archiving, reactivating, replacing, deleting, or re-adding the associated operating unit or contact. No such action clears a revocation.
This Section governs automated contact with owner-operators and brokers and does not affect verification codes sent to a registered account holder at that person's request.
The platform makes automated pre-activation risk decisions, Approve, Warn, Review, or Block, based on entity risk profiles derived from authority data, insurance status, fraud signals, and load context. These decisions may affect whether a load proceeds. The platform generates a plain-language explanation of each decision for dispatcher review.
The platform also uses AI to score and rank load opportunities and to conduct rate negotiations. These functions adapt over time based on operational data and dispatcher preferences. Adaptive learning is integral to the Services and cannot be disabled without discontinuing use.
We do not sell your personal information. We share information only in the following ways:
Service providers and sub-processors: We share data with vendors that process it on our behalf to provide the Services, under contracts requiring appropriate security and restricting use to the contracted services. These include our payment processor, which processes subscription payments and stores payment card and bank account details on our behalf; Twilio, which places and receives the AI agents' voice calls and delivers verification codes by SMS; Meta, which delivers WhatsApp messages; our cloud infrastructure providers; and the AI model providers described in our Terms of Service. Phone numbers are shared with Twilio solely to place or receive a call or to deliver a verification code and are not used for any other purpose. Information received from a connected email account is not shared with the AI model providers for any purpose other than operating the Services for you, and is never used for model training. A current list of our sub-processors is maintained in the Appendix to this Policy. We will provide at least thirty (30) days' advance notice of any material additions to our sub-processor list by updating that Appendix and sending email notice to active subscribers.
Operational counterparties: The platform transmits load-related communications and documents to freight brokers and owner-operators as necessary to perform dispatch operations on your behalf.
Load boards and data providers: The platform queries load board platforms on your behalf, subject to their terms of service.
Legal disclosures: We may disclose information to comply with applicable law, court orders, or regulatory requirements, or to protect the rights and safety of Tiriel, our users, or others.
Business transfers: In connection with a merger, acquisition, or asset sale, information may transfer to the relevant successor entity subject to continued privacy protections.
We retain load records, shipping documents, Rate Confirmations, incident records, and audit trails for five (5) years from the date of the relevant load completion or account termination. Call audio recordings and transcripts are retained for twelve (12) months from the date of the call, after which they are deleted or deidentified. Account and billing information is retained for five (5) years from account termination. Records of consent, authorization, and revocation are retained for five (5) years from account termination, and revocation records are retained for as long as necessary to honor the revocation. Messages processed from a connected email account are retained for twelve (12) months, and are deleted within thirty (30) days of your disconnecting that account except where they form part of a load record retained under the periods above. Platform usage logs are retained for up to two (2) years. After applicable retention periods, data is deleted or anonymized. We may retain data longer where required by law or for ongoing legal proceedings.
Retention is not the same as availability through your account. Our Billing, Pricing & Refund Policy describes the periods during which you may export your operational history after cancellation through self-service and through support. Those periods govern how long the data remains directly accessible to you; the retention periods in this Section govern how long Tiriel maintains the data, including after it ceases to be available through your account. Data that Tiriel retains after those access periods remains subject to your rights under Section 9.
We implement technically and organizationally appropriate measures to protect your information, including access controls, encrypted data transmission, sanitization of sensitive data in logs, and immutable audit trail architecture. No security measure is entirely infallible. If you believe there has been a security incident involving your account, contact us immediately at privacy@tiriel.ai.
In the event of a security breach affecting your personal information, we will notify you without unreasonable delay and within the timeframe required by applicable law, including the laws of the State of Delaware and any other state whose law applies to affected individuals. Notice will be provided by email to the address on file with your account.
If you are a California resident, you may have rights under the California Consumer Privacy Act (CCPA and CPRA), including: the right to know what personal information we have collected about you; the right to request deletion of your personal information; the right to correct inaccurate information; the right to opt out of the sale or sharing of personal information (we do not sell or share personal information as those terms are defined under the CCPA and CPRA); and the right to non-discrimination for exercising your rights. To submit a verifiable request, contact privacy@tiriel.ai. We will respond within 45 days, and may extend that period by an additional 45 days where reasonably necessary, in which case we will notify you of the extension and the reason for it within the initial 45-day period.
You may designate an authorized agent to submit a request on your behalf. We may require the agent to provide proof of authorization and may require you to verify your own identity directly with us.
Residents of Virginia, Colorado, Connecticut, Texas, Oregon, Montana, and other states with applicable privacy laws may have similar rights. Contact privacy@tiriel.ai to submit a request. We will respond within the timeframe required by applicable law.
Right to appeal. If we decline to act on your request, we will tell you why, and you may appeal that decision by replying to our response or writing to privacy@tiriel.ai with the subject line "Privacy Appeal." We will respond to an appeal within the period required by the law of your state, and in no event later than sixty (60) days. If we deny your appeal, we will provide you with a method to contact your state's attorney general to submit a complaint.
If the platform has contacted you, your information was provided by, or collected in the course of dispatch operations managed by, the dispatcher who manages or seeks to manage your loads. The categories of information we process about you and the purposes for which we process it are described in Sections 2, 3, and 4. To ask about your data or to exercise rights available to you under applicable law, contact privacy@tiriel.ai, and we will coordinate with the relevant dispatcher as needed to respond. Where we act as a service provider and are not permitted to act on a request directly, we will forward your request to the responsible dispatcher and tell you that we have done so.
The Tiriel web platform uses cookies and similar technologies for session management, authentication, platform functionality, and analytics. You may manage cookie preferences through your browser settings; disabling certain cookies may affect platform functionality.
The Services are not directed to individuals under 18. We do not knowingly collect personal information from minors. If you believe we have done so, contact privacy@tiriel.ai and we will delete the information promptly.
We may update this Policy at any time. Updates will be posted at www.tiriel.ai/privacy with a revised effective date. For material changes to our data practices or how we use personal information, we will provide at least thirty (30) days' advance notice by email or in-app notification. For all other material changes, we will provide at least fourteen (14) days' notice.
2261 Market Street STE 4462 · San Francisco, California 94114
Email: privacy@tiriel.ai · Website: www.tiriel.ai
This Appendix forms part of the Privacy Policy and is referenced in Section 6. Last updated: August 14, 2026.
The following sub-processors process personal information on Tiriel's behalf to provide the Services. Each is engaged under a contract requiring appropriate security measures and restricting use of the information to the contracted services.
| Sub-processor | Purpose | Categories processed | Location |
|---|---|---|---|
| Stripe, Inc. | Payment processing, subscription billing, tax calculation | Subscriber name, business name, email, billing address, payment card and bank account details, transaction records | United States |
| Twilio Inc. | Voice telephony: placing and receiving the AI agents' calls. SMS delivery of one-time verification codes | Recipient phone number, call audio, call metadata, call outcome, verification code delivery status | United States |
| Meta Platforms, Inc. | WhatsApp Business messaging | Recipient WhatsApp number, message content, delivery status | United States |
| Amazon Web Services, Inc. | Hosting, storage, backup, and database services | All categories described in Section 2 | United States |
| OpenAI, L.L.C. | Natural language processing and agent reasoning | Call transcripts, message content, load and document data, under an agreement restricting use for third-party model training | United States |
| Anthropic, PBC | Natural language processing and agent reasoning | Call transcripts, message content, load and document data, under an agreement restricting use for third-party model training | United States |
| Deepgram, Inc. | Speech recognition, transcription, and speech synthesis for the AI agents' calls | Call audio, transcripts | United States |
| Load board platforms (DAT, Truckstop, 123Loadboard and others) | Load search and posting on the subscriber's behalf | Search criteria, and the authorization token issued by the relevant board | United States |
Phone numbers are shared with Twilio solely to place or receive a call or to deliver a verification code, and with Meta solely to deliver a WhatsApp message. They are not shared with any other sub-processor, third party, or affiliate for marketing or promotional purposes.
To request notice of changes to this Appendix, or to ask a question about a specific sub-processor, contact privacy@tiriel.ai.