Strivie

Privacy Policy

Effective October 8, 2026 · Last updated October 27, 2026

Strivie ("we") builds the Strivie TMS platform and the companion mobile apps Strivie Driver, Strivie TMS and Strivie CRM. The apps are used by transportation companies ("carriers") and the drivers and office staff they employ or contract. Each carrier runs its own Strivie system and is the controller of its operational data; Strivie processes that data on the carrier's behalf. This policy also covers Strivie Connect, the service that connects AI assistants such as Claude and ChatGPT to a carrier's Strivie system.

Strivie CRM is a recruiting tool for a carrier's recruiters and onboarding staff. Unlike the other two apps, most of the data in it describes driver applicants — people who applied to drive for that carrier — rather than the person using the app. The "Recruiting and applicant data" section below covers that data specifically.

Data we collect

Account data — name, phone number, email, driver or employee ID, and assigned equipment, created by your carrier when they set up your account.

Location — the Strivie Driver app collects precise location, including in the background, while you are signed in, so your carrier's dispatch team can track progress on assigned loads. The app asks for your consent before any location collection starts, and you can stop it at any time by revoking the location permission or signing out.

Documents and photos — bills of lading, proof-of-delivery photos, licenses, and similar paperwork you choose to upload.

Messages — chat between you and your carrier's dispatch team.

Microphone and calls — the Strivie TMS and Strivie CRM apps include an optional in-app phone for your work line. It is off until you turn it on, and the app asks for microphone permission at that point. The microphone is used only during a call you place or answer; the audio goes live between your device and your carrier's phone service (such as RingCentral or Yoko) and is not recorded or stored by the app or by Strivie. If your carrier has call recording turned on in its own phone service, that service makes the recording and it may be kept on the carrier's system. A log of which calls took place is stored on the carrier's system, as for calls placed any other way.

Device data — push notification token, app version, and basic diagnostics used to keep the app working.

Recruiting and applicant data

This section applies to Strivie CRM, and to the recruiting features of the Strivie TMS platform.

Applicant details — name, phone number, email address, work history and the recruiter's own notes about an applicant, entered by the carrier's staff or submitted by the applicant through the carrier's driver application.

Applicant documents and photos — commercial driver's licence, medical certificate and similar paperwork, photographed or uploaded by a recruiter or sent in by the applicant.

Screening reports — a carrier can order a motor vehicle record (MVR) and an FMCSA Pre-Employment Screening Program (PSP) report on an applicant through the platform. These are consumer reports about the applicant. The carrier orders them as the prospective employer, under its own disclosure and authorization process with the applicant, and is responsible for that process; Strivie relays the request to the screening provider and stores the result on the carrier's system.

Call and message records — Strivie CRM places calls and sends text messages to applicants through the carrier's own phone service: either the service rings the recruiter's work phone and connects the call, or, when the recruiter has turned on the optional in-app phone, the call is made from the app itself (see "Microphone and calls" above). Unless the carrier gives a recruiter access to applicants' contact details, the app shows only the last four digits of an applicant's phone number. The app does not record call audio. A log of which calls and messages took place, and the text of messages sent, is stored on the carrier's system so the recruiting team shares one history.

Applicant data is used only to evaluate and onboard that applicant for the carrier that received the application. It is not sold, not used for advertising, and not shared with other carriers.

AI assistants and Strivie Connect

People at a carrier can connect an AI assistant they choose, such as Claude (by Anthropic) or ChatGPT (by OpenAI), to the Strivie TMS through Strivie Connect (connect.strivie.io; see the setup guide). This is off until an administrator at the carrier turns it on, and each person also needs the carrier's "Use an AI agent" permission. A person who works for several carriers can reach, through one connection, each carrier where they signed in and allowed it.

What the AI can see — the AI acts as the person who connected it and sees only what that person's Strivie login can see. Their permissions are checked again on every request. Social Security numbers, dates of birth, licence numbers, full bank account and routing numbers, passwords, PINs and stored company logins are removed from every answer, whatever the person's permissions. Driver applications, ACH payment files and the Clearinghouse file are never passed to the AI. A document the person asks for, such as a proof of delivery or a licence photo, is passed as it is, within their permissions.

What the AI can change — nothing in the carrier's records on its own. The AI can only propose a change or a message; it runs after the person reviews it and presses Approve, inside Strivie or, where the carrier has turned that on, inside the AI app.

What Strivie Connect keeps — the work email the person enters (to find their carrier), the carriers the connection reaches, the name of the AI app, a count of the requests made, and the sign-in tokens each carrier's system issues for the connection. Those tokens are stored encrypted (AES-256-GCM); the tokens Strivie Connect issues to the AI app are stored only as one-way hashes. Strivie Connect passes each request to the carrier's system and the answer back without storing either. Its server logs record the time, the type of request and the name of the tool used, never the contents.

When a connection ends — the person can end it at any time on their My Profile page in Strivie or in the AI app's connector settings, and a carrier administrator can end any connection at the carrier. A password change ends every connection on that login, and a connection ends by itself 30 days after it was made. When it ends, its tokens are deleted. A short record of the connection (email, carrier, AI app, when it started and ended) is kept for security.

Records on the carrier's system — for each AI request the carrier's Strivie system keeps an audit record: who asked, through which AI app, the exact change proposed, who approved or declined it and when, and the result. These records are kept with the carrier's other operational records.

The AI provider — the questions a person asks and the answers Strivie returns pass through the AI provider they chose (for example, Anthropic for Claude or OpenAI for ChatGPT), which handles them under its own terms and privacy policy and the person's or carrier's agreement with that provider.

Bug reports — when an AI assistant notices something in Strivie that looks broken, it may send a short description of the problem to Strivie's own support team. It goes to no one else.

AI features inside Strivie — some Strivie features use AI models to read documents, for example driver's licences, medical certificates, rate confirmations, fuel receipts and vendor invoices, including ones that arrive by email, and to write short summaries such as the morning briefing. These models are provided by Anthropic or run on hardware Strivie operates. Content is sent to them for that purpose only.

How data is used

Solely to operate your carrier's transportation business: dispatching loads, tracking shipments, paperwork, payroll and settlements, and messaging. We do not sell personal data, we show no advertising, and we use no third-party advertising or tracking SDKs.

Sharing

Your data is visible to your carrier (the company you drive or work for) and to the service providers Strivie uses to run the platform — cloud hosting, push-notification delivery and AI models (Anthropic) — under contracts that limit them to providing the service. When you connect an AI assistant, data also passes through that assistant's provider, as described under "AI assistants and Strivie Connect". We disclose data when the law requires it.

Retention

Account data is kept while your account is active. Operational records (completed loads, signed paperwork, settlement history) are retained by your carrier to meet transportation record-keeping requirements (for example, FMCSA regulations), even after an account is closed.

Security

Data is encrypted in transit (TLS) and stored on access-controlled servers. Credentials are stored hashed, and mobile sessions use scoped, expiring tokens.

Your choices

You can decline or revoke location permission at any time in your device settings. You can turn the in-app phone off in the app, or revoke microphone permission in your device settings, at any time; calls then ring your work phone as before. To correct account data, contact your carrier's office. To request deletion, see our data deletion page.

If you applied to drive for a carrier and want to see, correct or delete what that carrier holds about you, contact the carrier you applied to — it controls that record. If you cannot reach them, write to us at the address below and we will put you in touch.

Children

The apps are workplace tools for commercial drivers, recruiters and office staff and are not directed at anyone under 18.

Contact

Questions about this policy or your data: support@strivie.io.

We will post any changes to this policy on this page.