Trust
For teams and managers
What the app on a driver’s phone is, what it is not, where the data lives, and why it is designed the way it is.
Written by the delivery driver who created CarrierCaddy. This page is the short answer; the full one is the Privacy Policy.
Independent. Not affiliated with any postal operator, delivery company or employer.
Why drivers use it
Because it makes the day safer and the service better. Stop details are spoken as each stop comes up, so the driver’s eyes stay on the road, and every instruction waits at the right address, so fewer stops go wrong and fewer customers have to call.
What it is
A personal organizer for someone who works a set of stops: the order, what is waiting at each address, spoken reminders as a stop comes up, a label scanner, a parcel-run planner and a sorting-rack layout.
What it is not
It is not an employer system and connects to none. It does not read scanners, handhelds or delivery databases, receives nothing from them, and sends nothing to them. It is not the authority for a delivery decision; the app says so, and asks the driver to verify against official records and the item in hand.
Where the data lives
On the phone. Route addresses, notes, holds, forwards, names and packages are stored in the app, protected by the phone’s own encryption and screen lock (on Android the route database is encrypted as well), and the app keeps them out of the phone’s cloud backup. There is no account, no sync and no route storage on a CarrierCaddy server. When the driver asks for an address lookup or a road path, the service passes the address or coordinates to the US Census Bureau’s public geocoder or to Google Maps and keeps a usage count against an anonymous device identifier; it never sees customer names, notes or photos. The map itself is Google Maps, which loads straight from Google.
When data moves
Only when the driver chooses. A route can be handed to a coworker as an encrypted file to a phone they have paired with in person, as a sealed file with a code, or as QR codes shown in person. Backups are password-encrypted files the driver keeps. The app reminds them to share only with authorized people, and that a coworker who receives a route can read it.
Driving
The app and its terms tell the driver never to use it while driving and to keep their eyes on the road. Setup, scanning and editing belong to time safely parked. On the road the app speaks; the design goal is that the driver never needs to look at it. Spoken reminders support attention; they do not replace it, road signs or your procedures.
Raising a concern
If you are worried about how a colleague is using the app, we would rather hear it than not: email support@carriercaddy.com. Nothing about a workplace policy is decided by this app; it is a tool the driver chose, and your policies still apply to what they store and share.
Custom dispatch systems
Function Desk LLC, which makes CarrierCaddy, builds custom dispatch systems for organizations that need more than their current route management platform gives them. Each one is built to order around the organization’s own routes, draws on what this app has taught us about route work, and is designed to make the most of advances in AI as they arrive: plans that adjust during the day, with safety and human oversight built in, so your operation gains an edge without giving up control. This is separate work; the CarrierCaddy app itself stays a personal tool and connects to no employer system.
Talk to us about a dispatch system
hi@carriercaddy.com
This page is a good-faith explanation by the app’s author, who works a route and is not a lawyer. It is not legal advice and does not speak for any employer.