Terms of use
What Fleet Bot reads, what it does with it, and what you're responsible for once you connect your fleet.
What we read
Fleet Bot reads every message in the Telegram groups you connect — not only the lines about loads. That's how it catches rate changes, cancellations, and TONUs typed mid-conversation. If a group carries a mix of dispatch and personal chat, we read all of it.
How we read it
Messages are parsed by Anthropic's Claude, a third-party AI model, to extract load and rate data. Flagged events and status changes carry a quoted excerpt as the record of why.
How we build this
This website and the bot are built with the help of AI coding tools, reviewed and shipped by our engineering team. That doesn't change anything said elsewhere on this page: what we read, how we store it, and who's responsible for decisions stay the same.
Where your data lives, and backups
Every message your connected groups send — its text and the full data Telegram gives us — is stored in Fleet Bot's production database and kept permanently; nothing is edited or deleted from that record. Every day the full database is exported and sent to the operator as a backup file — there's no separate long-term archive beyond that daily snapshot.
What we show, and where we're honest about gaps
We reconcile every load against the Amazon statement and Trips export. Where a statement line doesn't match — or hasn't arrived yet — we show that as an open item, not as money you've lost. For the week of August 15, for example, 54% of the statement amount hadn't been reconciled line by line yet; we show that gap, not a loss estimate.
Turning it off
You can ask us to deactivate your company and delete your data at any time; we'll confirm once it's done.
Your calls, your responsibility
Fleet Bot surfaces numbers and discrepancies. Decisions you make based on them — disputing a payment, changing a rate, contacting Amazon — are yours; we don't make them for you and aren't responsible for the outcome.