This policy explains what information SyncFleet collects through the website syncfleet.io, the SyncFleet web and mobile app used by fleet offices, and the SyncFleet Driver app used by drivers and job applicants (together, the “Services”), how we use it, who we share it with, and the choices you have.
1. Who we are and who this covers
SyncFleet provides software that trucking companies (“carriers” or “customers”) use to connect their fleet systems, send alerts, track maintenance and safety documents, hire drivers and run inspections.
- Customers and their staff. For account, billing and support information, SyncFleet decides how the information is used.
- Drivers and job applicants. Carriers use SyncFleet to keep driver files and process applications. For that information, the carrier is responsible for it and decides how it is used, and SyncFleet processes it on the carrier's behalf and under the carrier's instructions. If you are a driver or applicant, the carrier you work for or applied to is your first point of contact for questions about your information. See section 6.
2. Information we collect
Account information. Name, email address, phone number, company name, DOT number, fleet size and password. Passwords are stored only as a one-way hash.
Passkeys. If you add a passkey (for example Touch ID or Face ID), we store only its public key, a name and when it was used. Your fingerprint or face is checked on your own device and never sent to us.
Ideas you post. Feature ideas posted on the Ideas board are shown to other customers without your name or company. We see which company posted and voted.
Credentials for connected platforms. API keys, tokens or logins a customer enters to connect platforms such as their telematics, ELD or TMS provider. These are encrypted before they are stored and are used only to read that customer's own fleet data.
Fleet data from connected platforms. Depending on what a customer connects: truck and trailer identifiers, vehicle location and speed, odometer and engine data (including engine and idle hours), fault codes, driving safety events (such as following too close, harsh braking, speeding and crashes) used for reports and weekly driver scores, hours-of-service status and remaining drive time, driver names and assignments, and load and trip details, and from a TMS, driver contact details, hire dates and license and medical certificate expiration dates, and from a fuel platform such as RELAY, fuel purchases (date, station and location, gallons, prices paid, driver name and the truck number the driver entered), and from a toll provider such as Bestpass, toll transactions (date, amount, toll location, truck unit, license plate and transponder number).
Documents and records. Files and details the customer or a driver uploads, such as registrations, inspection reports, insurance cards, lease agreements, commercial driver's licenses (CDLs), medical examiner's certificates, and the numbers and dates on them.
Driver applications. When a carrier sends an application link, the applicant may provide: legal name, date of birth, Social Security number, contact details, current and previous addresses, license history, driving experience, accidents and traffic convictions, employment history, emergency contact, tax information (W-9), bank routing and account numbers for direct deposit, uploaded document images, and electronic signatures.
Public application forms. When a carrier turns on its public application link, a job seeker can start an application from the carrier's page on syncfleet.io or a form on the carrier's own website. That form collects name, email, mobile phone, the position wanted, years of CDL experience, CDL state and consent to be contacted, plus the IP address to stop abuse. The carrier is notified, and the applicant receives an email with their personal link.
Loads (SyncFleet TMS). When a carrier uses the SyncFleet TMS, we store its loads: customers (brokers and shippers) with their MC/USDOT numbers, contacts, billing details, payment terms and credit limits; pickup and delivery places and appointment times; rates, extra charges, carrier pay and driver pay; references (PO, BOL, pickup numbers); notes; rate confirmations and other load documents; and who changed what and when. A rate confirmation may be read by AI (Anthropic) to fill in the load, only when the carrier asks for it. Street addresses are sent to the U.S. Census Bureau geocoder to place stops on the map (only the address, nothing else). Drivers see only what the carrier chooses (addresses and times by default); team-only notes and what the customer pays are never shown to drivers. If the carrier emails load documents from SyncFleet, they go to the addresses the carrier types. Invoices (with payments received) and factoring batches are kept for the carrier's records; invoice emails go to the billing address the carrier sets. Driver pay plans and weekly pay statements (pay per load, credits and deductions) are visible to the carrier's money roles and, once approved, to that driver in the Driver app.
Inspections. Pre-trip inspection results from the Driver app, including the photos the driver takes, checklist answers, defect notes, the driver's result statement (satisfactory, or problems found and whether the truck is safe to drive), odometer reading, trailer number and signature. Inspection photos are reduced in size and automatically deleted after the period the carrier chooses (30 days to 1 year, 90 days by default), except photos of a defect that isn't repaired yet and inspections the carrier chooses to keep; the inspection record itself is kept. Drivers can also upload photos or PDFs of DOT roadside inspection reports (date, state, report number, violations and the inspector's notes); these are read by AI and reviewed by the carrier. If a carrier turns on the Safe Driver Bonus, we calculate each driver's points and ranking from their safety events, fuel purchases, driving days and confirmed inspections, and send each driver their result.
Random drug and alcohol tests. When a carrier sends a driver to a random test, we store the collection site, appointment time and Chain of Custody Form number the carrier enters, when the driver saw the notice, and the photo of the test receipt or form copy the driver takes (with its time and location). These are kept in the driver's file and are visible only to the carrier's team members allowed to see driver files. We tell only that driver, privately, and never post it to group chats. Test results are recorded by the carrier.
Truck documents (in-cab). The papers a driver must show at a roadside inspection (ELD manual and instructions, blank log sheets, registration, insurance card, IFTA, permits, lease) are shown to the drivers of that truck in the Driver app, which keeps a copy on the phone so they open without signal. If a paper is missing, the driver can photograph it (with the photo's time and location); it is added to the truck's documents for the carrier to review.
Accident reports. If there is an accident, drivers can send photos of the vehicles, the scene and the other driver's license, insurance card and plate, a police report number, and the names and phone numbers of the other driver and witnesses. We store this for the carrier as an accident report. When a carrier uses Samsara, crash alerts from Samsara (time and location) open these reports automatically.
Electronic signatures. When someone signs in the Services we record the drawn signature, the typed name, the date and time, the IP address and the device's browser information, as evidence of the signature.
Team roles and truck assignments. For each team member we store their role (owner, admin, dispatcher, accounting, safety, fleet manager or viewer) and, for dispatchers, which trucks they work. A role decides which parts of the carrier's data that person can see; drivers' personal data is visible only to owners, admins and safety. We also record when a carrier sets a truck's driver by hand, so automatic ELD/TMS updates don't override it.
Messaging and notifications. Identifiers needed to deliver alerts to the channels a customer sets up, such as Telegram group and user IDs, Slack, Microsoft Teams or Google Chat webhook addresses, and email addresses or phone numbers for alerts. If a driver turns on reminders in the Driver app, we store that phone's push notification address (web push, or an Expo push token in the iPhone/Android apps).
Load paperwork and stop times. When a driver scans a proof of delivery, lumper receipt or bill of lading in the SyncFleet Driver app, we keep the scanned pages (as a PDF), the amount on a lumper receipt, the load it belongs to, and when and where each page was taken. We record when a truck arrived at and left each load stop, found from the Driver app's location and the ELD's GPS or set by the driver. The carrier's office sees them; if the carrier turns on sending to Alvys, the times and documents are also sent to the carrier's own Alvys account.
Alvys. When a carrier connects Alvys, we read its users (to match each truck's dispatcher to the carrier's team), driver deductions (to show charges in Profit) and trailers. If the carrier turns them on, we also send scanned medical cards and CDLs to the matching driver, and pre-trip inspection reports to the matching truck, in the carrier's own Alvys account, and receive instant load updates from Alvys (signed webhooks we verify before using).
In-app messages. Messages SyncFleet sends to a truck's channels are also kept in that truck's conversation in SyncFleet, together with messages and photos the carrier's office and its drivers send each other in the SyncFleet apps and on the web, who sent them, when, and who has read them. Confidential items such as random test notices are kept only in that driver's private conversation. Messages are deleted after one year, or sooner under the carrier's data retention setting.
Support. Messages and attachments sent to our support team, including replies by email.
Electronic signatures. When a driver signs a hiring document, we record their typed name, drawn signature, the time, their IP address and browser/device, and store a signed PDF with this audit information and a fingerprint (hash) of the document in the carrier's driver file.
Problem reports. When someone uses “Report a problem”, we receive their description, an optional screenshot they choose to add, and (unless they turn it off) technical details: the page, browser and screen size, app version, recent error messages and technical traces, failed requests, and the last buttons and pages they clicked. What they type into fields and passwords are never collected, and emails, phone numbers, Social Security, card and bank numbers and access tokens are masked first. We also keep a log of errors on our servers (the page or action, the error message and technical trace, and which company and user it happened for) for 30 days to fix problems.
Sign-in and security information. For each user: when they signed in, the device type and IP address of each signed-in session, failed sign-in attempts, two-factor login status (the secret is encrypted), and an activity log of important actions in the workspace (for example team changes, downloads and views of full sensitive numbers). If you use "Sign in with Google", we receive your name, email address and Google account ID from Google. Customers can create read-only API keys; we store only a fingerprint of each key.
Technical information. Our servers keep standard logs (such as IP address, browser type, pages requested and errors) to run and secure the Services. We do not use advertising or third-party analytics trackers.
Payment information. When paid billing is active, payments are handled by our payment processor, Stripe: cards, US bank accounts (including through Stripe Link), Cash App Pay and Google or Apple Pay. We do not receive or store full card or bank account numbers; we keep the Stripe customer and subscription IDs and see the payment method type, its last 4 digits and your invoices.
3. How we use information
- To provide the Services: syncing fleet data, running the automations a customer turns on, sending alerts and reminders, tracking documents and expirations, processing driver applications and inspections, checking factoring payments against invoices, and producing downloads.
- To create and secure accounts, sign people in, and prevent fraud and abuse.
- To provide support and send service messages (for example application links, document reminders and replies to support requests).
- To bill customers when paid billing is active.
- To maintain, troubleshoot and improve the Services.
- To comply with law and enforce our terms.
We do not sell personal information, and we do not use it for targeted advertising. We do not use drivers' or applicants' information for any purpose other than providing the Services to the carrier.
4. How information is shared
With the customer. Information in a carrier's account, including driver files, applications and inspections, is available to that carrier's authorized users.
With the channels the customer chooses. Alerts, reminders and document copies are delivered to the places the customer configures, such as Telegram, Slack, Microsoft Teams, Google Chat, email or text message. Those services handle the messages under their own privacy policies.
With service providers that help us run the Services, only as needed for their work and under obligations to protect the information:
- Hosting and infrastructure (our servers are operated by Hostinger).
- Resend, which delivers the emails SyncFleet sends (application links, reminders, alerts and support replies). It receives the recipient's address and the message.
- Titan (Hostinger), which hosts our support mailbox.
- Sentry, which records technical errors so we can fix them. We send no session recordings, cookies, request contents or IP addresses, and we mask anything that looks like a Social Security, tax, bank or email address before an error report leaves our servers or your browser.
- Anthropic, for AI reading of uploaded documents (see section 5).
- Google Drive, only if a customer connects it for backups: SyncFleet copies the customer's own files (documents, inspection photos and reports) into a folder in the customer's Google Drive. SyncFleet asks only for the drive.file permission, so it can see and change only the files it creates there, nothing else in that Drive. The customer can disconnect at any time; files already copied stay in their Drive.
- Intuit QuickBooks Online, only if a customer connects it: SyncFleet reads the customer's expense accounts, classes, locations and expense transactions (vendor, memo, date, amount) to calculate truck costs and profit. Access is read-only, the sign-in token is stored encrypted, and disconnecting deletes the copied expense lines.
- Esri, which serves the map images on the fleet map (your browser loads them directly, so Esri sees your IP address), and OpenStreetMap / Overpass, from which we download public lists of truck shops. If a carrier enables Google search on the map, the visible map area is sent to Google Places to find shops; no personal information is sent. To show diesel prices near a truck, the truck's approximate location (or the city a user types) is sent to Google Places; no driver names or other personal information are sent. To plan fuel stops for a load, the truckTo show diesel prices near a truck, the truck's approximate location (or the city a user types) is sent to Google Places; no driver names or other personal information are sent.apos;s location and the loadTo show diesel prices near a truck, the truck's approximate location (or the city a user types) is sent to Google Places; no driver names or other personal information are sent.apos;s pickup and delivery locations are sent to Google (Routes and Places) to draw the route and find truck stops along it; no driver names are sent.
- Stripe, for payments when paid billing is active.
- Telegram, for messages sent by the SyncFleet bot, and a text-message provider if text alerts are enabled.
With connected platforms. When a customer connects a platform, SyncFleet sends requests to that platform with the customer's credentials to read the customer's data. We do not write data to those platforms unless a feature clearly says it does.
For legal reasons. If required by law, court order or a valid government request, or to protect the rights, safety and property of our users, the public or SyncFleet.
Business transfers. If SyncFleet is involved in a merger, acquisition or sale of assets, information may be transferred as part of that transaction, subject to this policy.
5. AI document reading
When AI reading is enabled and someone uploads a document, the file is sent to Anthropic's Claude API to read the document type, number and dates so they can be filled in for a person to check. The same applies to factoring funding reports and TMS reports uploaded as PDF or photo: the lines are read so they can be matched with the carrier's loads. Anthropic processes this data to provide the service to us. Under its commercial terms, it does not use it to train its models. The result is a suggestion: a person reviews and saves it. When a carrier sends an announcement with “Translate for each driver” on, the announcement text is sent to Anthropic to translate it into each driver's language. When a driver uploads a DOT roadside inspection report, it is sent to Anthropic to read the date, state, report number and violations for the carrier to confirm. When a truck reports an engine fault code (for example from Samsara), the code and the truck's make and model, without any personal information, are sent to Anthropic, which may run a web search, to explain in plain English what the code likely means.
6. Drivers and job applicants
- Your carrier controls your file. Motor carriers are required to keep driver qualification files and inspection records (for example under 49 CFR Part 391 and Part 396). Your carrier decides what to collect, who on its team can see it and how long it keeps it, within the law.
- Application data is visible only to the carrier you applied to. Social Security, tax ID and bank account numbers are encrypted and hidden on screen until an authorized user chooses to reveal them.
- Applying from a website. If you start an application from a carrier's website and you already have one open with that email, we don't open it from the form: we email your personal link to that address instead, so no one else can see your application.
- Your personal link. Application and Driver app links are personal. Don't share them. If a link is lost or shared, ask your carrier for a new one, which turns off the old link.
- Requests. To see, correct or delete your information, contact the carrier first. If you contact us, we will forward your request to the carrier and help them respond.
7. The SyncFleet and SyncFleet Driver apps
- Location in the Driver app. If a driver allows it, the SyncFleet Driver app for iPhone or Android sends the phone's location (position, speed, direction and accuracy) every few minutes while the driver is working, including when the app is in the background. Their carrier sees it on the Fleet map when the truck's ELD has no recent position. Drivers can pause it any time in the app's Settings or turn it off in the phone's settings, and carriers can turn it off for the whole fleet. Positions are deleted after 30 days and are not used for alerts or sold.
- Camera and photos. The Driver app uses the camera only when you choose to take a photo (inspection, document, roadside or accident photos). The SyncFleet Driver app for iPhone and Android takes photos with the camera only and saves, with each photo, the time it was taken and the phone's location at that moment, so your company can see the photo was taken live at the truck. Photos are uploaded to your company's SyncFleet account and kept with its records.
- Location. The Driver app does not access your phone's location. Vehicle location shown in SyncFleet comes from the carrier's own telematics or ELD provider.
- Notifications. Reminders are sent only if you turn them on, and you can turn them off at any time in your phone's settings.
- iPhone and Android apps. When you sign in to the SyncFleet or SyncFleet Driver app for iPhone or Android, we store a sign-in record for that phone (a hashed sign-in token, the device name and type, the IP address and when it was last used) so you stay signed in. Signing out, or your carrier making a new Driver app link, ends it. If you allow notifications, we store the phone's push token and language; notifications are delivered through Expo's push service, which passes them to Apple or Google. Photos you take in the app with the camera (documents, inspections, accident photos) are uploaded to your carrier's account the same way as in the web app.
- Sign-in codes. A driver can sign in to the SyncFleet Driver app with their phone number: we send a one-time code by text message or to the email on their driver file. We keep only a scrambled copy of the code, for 10 minutes.
- On your phone. An inspection in progress is saved on your phone until you submit it or start over, so you don't lose your work if you are interrupted.
8. Cookies and local storage
We use only cookies that are needed for the Services to work: a sign-in cookie for the SyncFleet app, and in the Driver app a cookie that keeps you signed in with your personal link (or keeps your application open). We also save a few display preferences on your device (such as the last tab you opened). We do not use advertising or tracking cookies.
9. Security
Information is sent over encrypted connections (HTTPS). Uploaded files, application answers, and credentials for connected platforms are encrypted at rest with AES-256-GCM. Access is limited to the customer's authorized users and to SyncFleet staff who need it to operate and support the Services. No system is perfectly secure. If we learn of a security incident affecting your information, we will notify the affected customers and, where required, individuals and authorities.
10. How long we keep information
We keep customer information for as long as the account is active and as needed to provide the Services. Carriers decide how long driver files, applications and inspections are kept, and many are legally required to keep them for set periods (for example, driver qualification files for three years after employment ends). When a customer deletes information or closes their account, we delete it from the live Services within 30 days, and it is removed from backups as they are replaced, except where we must keep it to meet legal obligations, resolve disputes or enforce our agreements. Server logs are kept for a limited time for security and troubleshooting.
11. Your choices and rights
Depending on where you live, including California and other U.S. states with privacy laws, you may have the right to know what personal information we have about you, to get a copy, to correct it, to delete it, and to not be discriminated against for exercising these rights. We do not sell or share personal information for cross-context behavioral advertising.
- Customers can update account details in the app and can ask us to delete their account by contacting us.
- Drivers and applicants should send requests to their carrier first (see section 6).
- To make a request, email us at the address below. We will verify the request and respond within the time required by law. You may use an authorized agent where the law allows.
12. Children
The Services are for businesses and for adults seeking or holding commercial driving work. They are not directed to children, and we do not knowingly collect information from anyone under 18.
13. Changes to this policy
We may update this policy as the Services change. We will post the new version here with a new “last updated” date and, for significant changes, notify customers by email or in the app.
14. Contact us
SyncFleet LLC, Hallandale Beach, Florida. This policy is part of our Terms of Service.
Questions or requests about privacy: [email protected]. You can also reach us from the Help button inside the SyncFleet app.