Privacy policy
Effective 16 September 2026
The short version
We collect what we need to run your account. We do not sell it. We do not give it to brokers, insurers or load boards. We do not use your data to build products for other people. You decide who gets a proof link.
What the product does
FleetView tracks compliance deadlines for your trucks and drivers. It also runs dispatch and loads, keeps your customer and broker list, works out driver pay, and prepares your IFTA figures.
So we do hold load and trip information: stops and addresses, rates, and miles by state for IFTA. Earlier versions of this page said we did not. That was wrong, and this is the correction.
What we are not: we are not an ELD, and we do not sell one. We do not record hours of service. We do not track your trucks by GPS and we keep no location trail. We are not a load board.
Two kinds of information
Your account. When you sign in we hold your name, email address, phone number if you give one, time zone, your role on the account, and your notification settings. We decide what to collect here, and this policy covers it.
Your records. Everything you put inside the account — drivers, vehicles, loads, customers, pay — belongs to you, the carrier. You decided to collect it. We only process it to run the service for you. Under California law we act as your service provider for this. You stay the business responsible for it.
If you are a driver and you want to know what is held about you, or want it corrected or deleted, ask your employer first. The carrier controls the record. We will help them answer. If you write to us, we will pass your request to the carrier and tell you that we did.
What we hold
- Account — name, email, phone, time zone, role, notification settings and quiet hours.
- Carrier — legal name, DBA, USDOT number, address, phone, time zone. Most of this comes from the public federal record.
- Drivers — name, date of birth, phone, email, CDL number and state, CDL expiry, hire and termination dates, status and your notes. This is personal information about your employees, and we treat it that way.
- Vehicles and terminals — unit number, VIN, make, model, year, weight rating, plate and state, status, notes, and terminal addresses.
- Compliance records — what was recorded as done, the date it happened, and which user recorded it.
- Customers and brokers — company name, MC and DOT number, contact name, phone, email, billing email, billing address and pay terms.
- Loads — load number, broker reference, status, rates, equipment, commodity, weight, hazmat flag, detention terms and notes.
- Stops — company name, street address, city, state, ZIP, a contact name and phone at the stop, appointment windows, when the truck arrived and left, reference numbers and instructions.
- Assignments — which driver, co-driver, tractor and trailer were put on a load, by whom, and the reason if a warning was overridden.
- Driver pay — pay agreements and rates, settlements, every line on them, when a settlement was approved and by whom, when it was paid, and the payment reference you typed.
- IFTA — fuel purchases (date, state, gallons, amount, vendor, receipt number) and miles by state, per truck, per quarter.
- Proof links — the link itself, what it covers, who you made it for, when it expires, whether you revoked it, and how many times it was opened.
- USDOT claim — when you prove a USDOT number is yours: the number, the channel you chose, a masked version of the destination, and the number of tries. The code itself is stored only as a hash.
- Messages we sent — the address we sent to, the subject and text of the message, when it went, and what the provider said happened to it.
- Documents — photographs and PDFs a driver sends in through his link: medical certificates, licenses, and whatever else you asked him for, with which driver it belongs to and when it arrived.
- Driver photos — a small square photo of a driver, if you add one: a photo you take or pick on the driver's page, or the face cut from their license when you choose to use it. The cut is made on your device and kept small. It is stored privately and shown in the app through private addresses that expire within hours. It is deleted when you remove it or remove the driver.
- Your own reminders — the title, the note and the date of anything you set yourself a reminder for, beyond the rules we already track.
Documents a driver sends in. When you ask a driver for a document, the link he opens lets him photograph it or attach a PDF, and we hold that file so the office can put it on his record. Dates you type in are held as dates; a card he photographs is held as the photograph.
We use no advertising pixels and no third-party marketing analytics. The cookies we set are for signing in.
Where it comes from
From you, and from public federal records that anyone can look up. We re-check the public record from time to time so we can tell you when something on it changes.
Who else sees it
Only the companies we need to run the service. Each one may use the information only to do its job for us. This list is a promise: a company goes on it before it gets data, not after.
- Supabase — Database and sign-in. Holds every record in your account: carrier, drivers, vehicles, loads, customers, settlements, IFTA figures, and proof links. (United States)
- Cloudflare — Runs the website and the app (Cloudflare Workers). Every request passes through it. Also stores the documents a driver sends in through his link — photographs and PDFs of cards and certificates — in Cloudflare R2. Your typed records are not kept here. (United States (global network))
- Stripe — Takes the subscription payment. Receives the billing email address and what the plan costs. Card numbers are entered on Stripe’s own checkout page and never reach us, so we hold no card details. (United States)
- Resend — Sends our email: the deadline digest, alerts, and sign-in emails. Receives the address we send to and what the message says. (United States)
- Twilio — Sends our text messages: the deadline reminders and document requests a person has agreed to receive, and the six-digit code that proves a USDOT number is yours. Receives the number we are sending to and what the message says, and acts only as our delivery provider. The USDOT code goes to the phone number on the public federal record; the reminders and requests go to the number on the account or the driver record. (United States)
Card payments are taken by Stripe, on Stripe’s own checkout page. We hold the billing email address and what the plan costs. The card number is never sent to us and we could not produce it if you asked.
Otherwise we give your data to someone else only if the law requires it. If that happens and we are allowed to tell you, we will.
What we send out for you
- FMCSA public data (data.transportation.gov) — A USDOT number, to read the public Motor Carrier Census and operating-authority record. No driver information and no load information is sent.
When you type a street address in the app, the letters you type are sent to Google so it can suggest matching addresses, and Google handles them under its own privacy policy.
Proof links
A proof link lets a broker or an insurer see a summary without signing in. That is the point of it. You choose what it covers, how long it lasts, and who you send it to. You can revoke it at any time and it stops working straight away.
Until it expires or you revoke it, anyone holding the link can open it, including someone it was forwarded to. Treat it like a password.
Text messages
We send two kinds of text message. To you and your staff: a deadline coming due on your account. To a driver: a message from you, naming your company, asking him to send in a document, with a link that expires.
Where the number comes from. Yours, you type in yourself, and you tick a box of your own beside it. A driver’s, you type in for him — and that is all it does. It does not switch texts on, and it is not you agreeing for him: we do not text a driver until he has opened a link, read what he is agreeing to and ticked an empty box himself. We keep the words he was shown, which version of them they were, when he ticked it and the address his browser came from. If his number changes, that agreement ends with it and he has to give it again on the new number.
Message frequency varies with your account and with what is coming due — usually a few messages a month. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help. Opting out of texts stops the texts and nothing else — your account and your email carry on as before.
We do not sell, share, or provide your mobile phone number, text-message opt-in data or messaging consent data to third parties or affiliates for marketing or promotional purposes. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text-message opt-in data and consent are not shared with anyone. Twilio carries the messages for us, as the table above says. That is delivery, not marketing, and nobody else receives the number.
The program is registered with the mobile carriers as FleetView Compliance. The full terms are on the text message page.
What we do not do
- We do not sell personal information, and we do not share it for cross-context behavioral advertising, as those words are used in California law.
- We do not market to you or to your drivers by text, and we never text a number to sell something. We do not sell, share, or provide your mobile phone number, text-message opt-in data or messaging consent data to third parties or affiliates for marketing or promotional purposes. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text-message opt-in data and consent are not shared with anyone.
- We do not use your records to train machine-learning models.
- We do not use one carrier's data to serve another. Carriers are kept apart in the database itself, not only in the screens.
- We do not file anything with any agency on your behalf.
- We do not give legal advice.
How long we keep it
Compliance records have to last. A driver qualification file must be kept while the driver works for you and for three years after. So deactivating a driver keeps the history instead of wiping it, and a corrected record supersedes the old one rather than erasing it.
We keep your data while the account is open. After the account ends we delete or de-identify it within about 90 days, except where the law requires longer, and except backups, which age out on their own schedule.
Ask us for a copy of your data and we will send it to you. Ask us to delete a record and we will, unless we are required to keep it — and if deleting it would destroy evidence you may still need, we will tell you before we act.
Security
Traffic to the site is encrypted, and our database provider encrypts what it stores. Carriers are separated by database policy, so a query that forgets to filter by carrier returns nothing instead of somebody else's records. USDOT verification codes are stored only as a salted hash, and you get a limited number of tries.
A proof link is protected by the link itself: 256 random bits, generated fresh, derived from nothing about you. There is no second password behind it, which is why it expires and why you can turn it off. We do not keep a copy of the link. We keep only a one-way fingerprint of it, so the link cannot be read back out of our database by anyone, including us. That is also why we can show you a new link only once, when you make it.
No system is perfectly secure. If a breach affects your information we will tell you without undue delay and say what we know.
Your rights in California
Under California law you may ask us what personal information we hold about you, to correct it, to delete it, and to tell you who we gave it to. You may ask us to limit how we use sensitive personal information. We will not treat you worse for asking.
To make a request, write to info@fleetviewhub.com. We will check who you are first — usually by confirming you control the email address on the account — and answer within 45 days. Someone may act for you in writing.
For driver records, see above: the request goes to the carrier, and we help them.
Children
This is a tool for businesses. It is not for anyone under 16, and we do not knowingly collect information from children.
Changes
If we change this policy we change the date at the top. If a change materially affects your rights, we will email account holders before it takes effect.
See also our terms of use and pricing.