Privacy policy: Dispatch Map Driver
Davis Delivery Service Inc.
Effective date: November 8, 2026
Who we are
Dispatch Map Driver is a phone app from Davis Delivery Service Inc. ("Davis", "we", "us"). It is for Davis's own drivers and contractors. It runs the day's route: sign in, see the loads dispatched to you, work each stop, take proof of delivery, report problems to customer service, and keep working with no signal.
There is no public sign-up. Nobody can create an account in the app. The office makes every login on Dispatch Map, Davis's dispatch website, and links it to the name you go by on the dispatch roster.
This policy covers the app and the parts of Dispatch Map that receive and keep what the app sends. In it, "staff" means anyone signed in to Dispatch Map with a staff login (viewer, dispatcher or admin). A driver login is not a staff login.
Some features work only while the office has turned them on for your login, in Dispatch Map's Settings ▸ Delivery app. Each one is named below.
What we collect, and why
1. Your login
- Your username and password. You type them to sign in, and on Change password. If the office emails you a link to set or reset your password, you type the new one on Dispatch Map's website. The app never stores your password. Your phone's own password manager may fill the boxes; what it keeps belongs to your phone, not the app. Our server keeps only a salted scrypt hash of your password, not the password itself. No Dispatch Map service hands that hash out. If the office sets your password, the admin who set it knows it. A password you choose yourself is not shown to anyone and is not written to any log.
- Your login details. Your username, display name, role, your roster name and its other spellings, and your email if the office entered one. Why: to know who you are and which loads are yours. Your email is where an invite or a password-reset link is sent. Who sees them: admins see all of it. You see your username and display name on the phone. Staff see the username and display name of the driver on an order, and your roster name on an open wrong-location flag.
- Records about your login. Whether it is turned on, when it was made and by which admin, when your password last changed, whether you must change it, a sign-in counter, and the details of any emailed reset link. Why: so the office can manage your login: turn it off, make you choose a new password, or sign it out everywhere. Who sees them: admins see whether it is on, when it was made, when the password last changed, and whether you must change it. Your phone gets the same when you sign in, and keeps only whether you must change your password. No Dispatch Map service hands out which admin made it or the reset link's details.
- Sign-in safety. Your last sign-in time and how many wrong passwords were typed. After 8 wrong passwords, the login locks for 15 minutes. Admins see your last sign-in, and whether your login is locked and until when. The count of wrong passwords is in the server's log.
- Your phone's internet (IP) address, and the server's logs. When you sign in, the server reads your phone's IP address. It writes it to the server's log with your username, on each sign-in and each wrong password. Asking for a password-reset link logs your username, and the IP address when a link is made. Using a link logs your username and IP address. Each server instance also holds the address in its memory, to slow repeated sign-in and reset tries from one address. The log also records, with your username: when you sign out or change your password; when the server refuses a report, photo, position or reference-photo request from your phone (with its id, or the load and stop); each time it holds a report for your phone to send again because your login has no roster name of its own, or because the stop's pin, its customer's note or its drop spots could not be read (with its id, the load and stop, and why); when a search for the reference photo of your stop stops on a record it cannot read (with the load, stop and drop spot, and the id and board day of the earlier delivery it stopped on, which can be another driver's); when a photo check starts, fails to start, or finishes; when a position upload cannot read that day's LIVE presses; and, once the server keeps reports for dispatch to check, when dispatch accepts or rejects one of yours (with its id, the load and stop), or an Accept is refused because a different report of yours is stored under the same id. It records which admin made or changed your login, which staff member pressed LIVE for you, who sent a drop spot on which order, and who accepted or rejected a report of yours kept for dispatch to check. Why: security, and finding faults. These addresses and log lines are kept by Netlify, our host, not in our database. Who sees them: whoever can read the site's logs on Netlify.
- Your sign-in. When you sign in, the server gives your phone a token that keeps you signed in. It names your username, display name, role and sign-in counter, and when it was issued and when it expires. Our server signs it; it is not encrypted. It lasts 14 days unless Davis sets another length. It is kept only on your phone, in the phone's secure storage (Android Keystore or iPhone Keychain). Your phone sends it with every request. The server checks it and does not store it. It is deleted from your phone when you sign out, or when the phone finds your sign-in has ended.
2. Location
The app reads your phone's location in these ways.
- When you make a report. One reading each time you tap Arrived, Delivered or Can't deliver, start or end a break, or tap Start route; when a drop spot from customer service shows on your stop screen; when your route is finished; and once when you open the scanner at the door (each piece you scan carries that reading). If the phone has no location, the report says why (not allowed, not available, or timed out). Why: every report says where the phone was. A delivery's and an Arrived's place is checked against the stop (below), and deliveries teach us each customer's usual drop spots (section 5). Who sees it: in Signed for, staff see a delivery's place and GPS accuracy on a map beside the stop's pin, and, while our far-Arrived check is on (below), how far from the stop each Arrived was pressed. The places of Can't deliver, breaks, Start route, drop spot seen, scans and route complete are stored, but nothing shows or uses them.
- With each photo. Where the phone was when each photo was taken, and, with the signature, where it was when you tapped Delivered. It is kept beside the file. Nothing shows it or checks it.
-
While you work (live location). This is collected in the background, even when the app is closed or not in use. It runs only while the office has "Live location for customer service" on for your login, you have pressed Continue on the location notice on this phone, and you have allowed the app to use location. Then:
- While the office also has "Location from sign-in" on for your login, which is how the app comes, it runs from when you sign in, or open the app, on a day you have a load still to deliver on your board, until that day's route is finished or you sign out. A day with no load on your board is not shared. While the office also has "Location required to start a route" on, nothing in the app opens after you sign in until you have read the notice and allowed the app to use your location (on an iPhone, Always).
- Otherwise it runs from when you press Start route. While the office has "Location required to start a route" on, a route starts only once the app may use your location (on an iPhone, Always).
- See "Saying no to live location".
- What it records: each point's time, place, GPS accuracy, speed and heading, with the day, and, once you press Start route, the load and route. Each upload is stored with your username and display name, and each day's record with your roster name and its other spellings. A point every 30 seconds while moving and every 5 minutes while stopped, sent every 5 minutes.
- If your phone's clock runs more than 5 minutes ahead of the server's, an upload waits on your phone until the server's clock catches up. How far ahead your clock read is kept, with the upload's id, day, load and route and your username, and staff see those points at their time less that amount.
- When a dispatcher or admin presses LIVE on one of your orders, your phone takes a point every 5 seconds and sends every 10 seconds, from its next upload until 10 minutes after the press. If the app is in the background, the faster rate starts the next time you open it. The app does not tell you when staff are watching or have pressed LIVE.
- It stops when you finish the route, the load leaves your phone, you sign out, the office turns the feature off, the server refuses the points or answers that your sign-in has ended, or the app finds the route has run more than 16 hours. Shared from sign-in, before you press Start route, it stops when every load on that day's board is finished or none is left on your phone, when you sign out or someone else signs in on the phone, when the office turns either setting off, when the server refuses the points, or after 16 hours. Once it has stopped for the day, it starts again only the next time the app is started.
- Why: so dispatch and customer service can see where the truck is and answer customers.
- Who sees it: staff with a dispatcher or admin login. The Map tab shows each driver's latest point from the last 30 minutes, while the office has "Driver phones on the Map tab" set for everyone. The office can also set the Map tab to show only drivers without Motive. The Stops tab shows the last point the phone of the driver on an order took on that order's load, and its points on that load since a LIVE press. Points taken before you press Start route are on no load, so the Stops tab does not show them; the Map tab and the look-up below do. A dispatcher or admin login can also look up one driver's points over any stretch of up to 14 hours of a day. Our server will give your own login a count of your points, not the points; the app has no screen for it.
- The notice you see before sharing starts, word for word:
Dispatch Map Driver collects location data to enable live location for dispatch and customer service, even when the app is closed or not in use.
It starts when you sign in, or open the app, on a day you have a route, and stops when that day's route is finished or you sign out. While it runs, your phone shows that the app is using your location.
Who sees it: signed-in Davis dispatch and customer service staff, on Dispatch Map, to see where the truck is and answer customers. It is not sent to customers.
While the office has "Location from sign-in" off for your login, its second paragraph says instead:
It starts when you press Start route and stops when the route is finished or you sign out. While it runs, your phone shows that the app is using your location.
-
Speed for the driving lock, and the door picker. Both stay on the phone. While the office has "Driving lock" on for your login, and once you have allowed location, the app reads the phone's speed while it is open: about once a second on Android, and at each change on an iPhone. After 10 seconds over 5 mph, the app's Call and Text buttons and typing in the app are locked. Each reading is dropped as soon as its speed is read. It is not kept and not sent. The door picker reads your position once, to show how far each door is. It is not sent.
- Our check of where you delivered and where you pressed Arrived. On every delivery, and on each Arrived while our server's far-Arrived check is on (it is on unless it is switched off), the server works out whether it was at the stop or in the wrong place, or could not judge it (GPS too weak, or no pin). It keeps the distance to the nearest of the stop's pin and the customer's usual drop spots, the GPS accuracy, and the pin it measured to. On a delivery, the phone also makes its own check, so it can warn you at once with no signal. It sends that result only while the office has "Wrong-location warning + CS banner" on for your login. If the app asked you to pick the door, the delivery carries the door's number and position. Why: to catch a delivery made in the wrong place. An Arrived pressed far from the stop is left out of on-site times and is never put on the customer service banner. Who sees it: in Signed for, staff see a delivery's result and, while the far-Arrived check is on, how far from the stop each Arrived was. Our server will also give your own login your results, and an admin anyone's; no screen shows that read.
- Wrong-location flags. When the server finds a delivery in the wrong place, it files a flag for customer service. The flag keeps a copy of the delivery's place and our check, the phone's own check, your username and name, and the phone's and the server's times. Customer service records who claimed it and when, who completed it, what they found (the pin was wrong, the customer asked for it there, the driver is going back, or redelivery), and a note of up to 300 characters. Completing a flag records what they found; it moves no pin and sends nothing. Our nightly drop-spot learning reads it: a delivery they found was in the wrong place (the driver is going back, or redelivery), with every other record of that stop, never teaches the customer's usual drop spots (section 5), while that rule is on (it is on unless it is switched off). While a second rule is on too (it is on unless it is switched off), a flagged delivery teaches nothing until they complete its flag as the pin was wrong or the customer asked for it there: not the usual drop spots, not the customer's on-site time, and not a test login's practice drop spots. Who sees it: staff, on the customer service banner while the office has that feature on for everyone, and in a day's list of flags. Claiming and completing a flag need a dispatcher login.
3. Proof of delivery
- Photos. The named photos a customer's delivery profile asks for, damage photos, and the photos of a Can't
deliver report. A store build of the app takes photos with the camera only; it has no way to pick one from the
gallery. While the office has full-size photos on, and only while new photos go to our Google Cloud Storage bucket,
the app keeps the camera's own full-size photo, as it was taken, and sends it after a smaller copy of it (below);
otherwise it sends the photo resized to at most 1600 pixels. The server takes photos of up to 3 MB, and a full-size
photo of up to 19 MiB; a larger one stays on your phone and is never sent, and its smaller copy is. With each photo
we keep: a fingerprint of the file (its sha256), its size and type, its width and height as the file itself gives
them, the phone's time, the photo's name, whether it came from the camera, which delivery or report it belongs to,
the day, where the phone was (section 2), your username, and when the server received it and stored it; for a
full-size photo, also the size and quality the app says it was taken at. Why: proof of delivery, of damage, and of
why a stop could not be delivered.
- Who sees them: staff, in Signed for (delivery and damage photos) and on the order's driver report (Can't deliver photos). A photo with a smaller copy is shown by its copy, labelled as a copy, and its full-size photo is opened only when asked for. Our server will give your own login the record of each of your files, and an admin anyone's, without its place and without the photo itself; no screen shows that read.
- Other drivers: while the office has "Reference photo of the drop spot" on for their login, a driver with a stop at the same customer, on their own load, may be shown one of your delivery photos as the reference photo of that drop spot. It is the first photo of a delivery, never a damage photo, a Can't deliver photo or a signature, and never a full-size photo larger than 3 MB: they are sent its smaller copy, or the photo itself when it is no larger than that. They see when that delivery was made, not who made it.
- The AI photo check can send a delivery photo to Anthropic (see "Other companies").
- Smaller copies of photos. The server also takes a smaller copy of a photo, at most 1600 pixels on its longest side, made by the app from each full-size photo it takes. It is marked as a copy and never counts as proof. With it we keep: its fingerprint (sha256), size, width and height, the fingerprint and size of the photo it was made from, the photo's name, whether it came from the camera, which delivery or report it belongs to, the day, your username, and when the server received it and stored it (not where the phone was, and not the phone's time: those are kept with the photo itself); and what the app says it holds on the phone: how many files and how many bytes, and how many full-size photos are still waiting to be sent, their bytes and the time of the oldest. Never how much free space the phone has. Why: so the office can open a delivery's photo at its usual size while the full-size photo is still on your phone. Who sees them: staff, in Signed for and on the order's driver report, labelled as a copy; the drop spot's reference photo and the AI photo check use the copy too. Admins see what the app said it holds, per driver, while full-size photos are still on phones. Our server will give your own login the record of each, and an admin anyone's, without the copy itself.
- The customer's signature. Drawn on your screen and saved as an image, with the same kind of record as a photo. Why: proof the customer signed. Who sees it: staff, in Signed for and on the signed delivery ticket printed from it (for orders that are not Uline's). The ticket is made in the browser and is not stored. A signature is never a reference photo and is never sent to Anthropic. Our server will give your own login its record, and an admin anyone's, without its place and without the image.
- The customer's printed name. Typed on Delivered, up to 80 characters. Why: proof of who signed. Who sees it: staff, in Signed for and on the signed ticket.
- Refused to sign, and a damage note. Marked on Delivered, with a damage note of up to 300 characters, while the office has "Problem codes with required photos" on for your login. Why: proof of what happened at the door. Who sees it: staff, in Signed for and on the signed ticket. Which one it was (damaged or refused to sign) is also filed under the customer (section 5). Our server will also give your own login yours, and an admin anyone's.
- A short noted on a delivery. When some of a stop's pieces are not on the truck, you deliver what is there and note the short on Delivered: the pieces handed over, the stop's piece count the phone showed, which pieces are missing in your words (up to 300 characters), and, on a stop with Davis labels, the label numbers not scanned at the door. Offered while the office has "Problem codes with required photos" on for your login and our server says it takes a short on a delivery. Why: so customer service knows which pieces did not arrive, from a delivery the customer signed for. Who sees it: staff, in Signed for (beside the pieces scanned at the door) and on the signed ticket. Our server will also give your own login yours, and an admin anyone's.
- Left unattended. Where the office allows it for every order on the stop and has "Problem codes with required photos" on for your login, "Nobody here to sign? Leave it unattended" lets you deliver with no signature and no printed name: you take the photos, ask dispatch (section 4), and Delivered — left unattended works only once dispatch has entered who at the customer's allowed it. It is not offered beside damage, a refusal to sign or a short noted on the delivery. With the delivery we keep its photos, the time of the entry your phone was shown, and our server's own copy of who allowed it: the name dispatch entered, which dispatcher entered it and when, any name dispatch entered for your request after it, when you last asked, and whether your phone's time was more than 5 minutes before the entry. A delivery that reaches us after dispatch took the name back is kept for dispatch to accept or reject (section 4). Why: proof of a delivery nobody was there to sign for, and of who allowed it. Who sees it: staff, in Signed for and on the signed ticket printed from it.
- Signed Uline BOL copies. This is switched off in the code, and none are made today. When it is on, a dispatcher or admin presses a button that stamps the customer's Uline BOL with the signature, printed name, signed time and place, and stores that copy with who made it and when. Staff can open it.
4. Reports from your phone
Every report the server accepts is stored once and never overwritten. It keeps the report's id and type, the day, the load and the stop, the phone's own time, the time the server received it, the place (section 2), your username and display name, whether it came from a test login, a check that tells a resend from a different report, and, on a real delivery, the customer it is filed under. A report the server would refuse only because the office's board changed while your phone was sending it — for example, the load was moved to another driver, or the order to another load or day — is kept instead, and so is a delivery or Can't deliver report that reaches us more than 7 days after its load's day: each exactly as it would have been stored, with its photos and signature and why it was kept, for dispatch to accept or reject. Such a report is not a delivery until dispatch accepts it, and no AI photo check is made of it while it waits. Signed-in staff can read it; only a dispatcher or admin decides it, and who decided it and when is kept with it. A report the server refuses is not stored. Some refusals leave a line in the server's log with your username, and so does each report kept for dispatch. A report the server holds instead is not stored either: your phone keeps it, and everything you saved after it, and sends them again until the server takes them, keeps them for dispatch, or refuses one more than 7 days after its load's day. The server holds every report while your login has no roster name of its own, until the office fixes the login. It can also hold a delivery or an Arrived while the stop's pin, its customer's note (which may correct the pin) or the customer's usual drop spots cannot be read, and a report it is keeping for dispatch while the store cannot save it yet. Each try leaves a line in the server's log with your username. Our server will give your own login a summary of your stored reports for a day, with your reports kept for dispatch and what dispatch decided, and an admin any driver's. Neither the app nor any Dispatch Map screen asks for it.
- Arrived. When you got to the stop. Offered only while the office has "Arrived/Completed timestamps + far-Arrived flag" on for your login. Why: to record when you got there. Each customer's on-site time is learned from it (section 5). Who sees it: staff, in Signed for, with the driver and how far from the stop it was pressed, while the far-Arrived check is on (section 2).
- Delivered. The delivery itself, with what sections 2 and 3 describe. Who sees it: staff, in Signed for and in the Stops tab's past deliveries.
- Can't deliver. The reason, a note of up to 300 characters, and its photos. For Short, the pieces here and the stop's piece count the phone showed, when that count is a whole number from 0 to 9999; otherwise the report goes without the count. While our server takes a short on a delivery, a Short report is for none of the stop's pieces here (0 here), or, at a stop whose pieces are scanned before Delivered, for every piece here when a label would not scan; with some pieces here you deliver them and note the short (section 3). For Refused, whether it was damaged. Offered only while the office has "Problem codes with required photos" on for your login. Why: so customer service can follow up and confirm an attempt. Who sees it: staff, on the order. For a reason that counts as an attempt, customer service's "Mark as attempt" opens already filled in with your reason and note, and customer service presses it (section 6).
- Breaks. The start, with its kind (Lunch 30, Rest 15 or Fuel 10 minutes), and the end. Why: to record your breaks. Who sees it: no Dispatch Map screen shows a real driver's breaks today.
- Start route. Marks your route as started. Why: your positions are filed under it from then on, and it starts live location when that is on (shared from sign-in, it moves the sharing onto the route). Who sees it: staff. The Stops tab uses it to find the driver of an order and shows your name.
- Drop spot seen. Sent by the app on its own, once, when a drop spot customer service sent shows on your stop screen. It records that the screen showed it, not that you looked. Who sees it: staff see "Seen on the phone at" and the phone's time.
- Pieces scanned. Each piece's id and the PRO read from its label, when each was read, and the stop's piece count the phone showed. Taken only while the office has "Scan pieces at the door" on for your login. Why: to count the pieces that came off at the door against the stop's count. Who sees it: staff see the count (for example "3 of 3") in Signed for. Beside a delivery carrying a piece count, staff also see the piece ids scanned at the door. Your phone gets the piece ids back with your loads (section 7), and an admin can read them. A barcode you scan at the door that is not on your load's list from Uline counts nothing and is kept too, with the stop, so the office can see it happened; our server looks it up in Uline's file when it arrives.
- Pieces scanned while loading the truck. The same, for each piece you scan onto your truck on the Load truck screen, taken only while the office has "Scan the truck while loading" on for your login. With it: a piece loaded damaged and your note, a scan you took back, and a barcode that counted nothing — one not in Uline's file, or a piece of another truck with the route our server named (scanned with no signal, our server looks it up when it arrives, and keeps what it found with your login). When a piece will not scan, you take a photo of it with the app's camera (never from your gallery), with why; the photo, the piece and the reason are kept with the scan. Your Start route then carries what the truck held: the pieces it showed, loaded and by photo, and each piece not loaded with your reason (when the office asks for one). Why: so the office knows what went on each truck and what was left behind, and can find a piece that did not go. Who sees it: staff see the trucks loaded with the app, each piece counted by its photo with that photo, and a truck that left with pieces not loaded (on a banner at the top of Dispatch Map, on the warehouse's dock screens, and on the order's page). Your phone gets the piece ids back with your loads (section 7).
- A request to leave a delivery unattended. The day, load and stop, and your phone's time, sent when you press "Nobody here to sign? Leave it unattended", and again every 10 seconds until our server has it. Your phone then checks for dispatch's answer every 10 seconds, every 30 after 10 minutes, only while that screen is open. "Someone is here after all" and Can't deliver withdraw it. It is not a report: we keep each request with your username and name, when our server and your phone made it, every withdrawal, and whether it is waiting, answered or withdrawn. Each request leaves a line in the server's log with your username and the order. Why: so dispatch knows you are waiting at the door, and your phone can unlock Delivered — left unattended once dispatch has entered who allowed it. Who sees it: dispatchers and admins see each driver waiting across the top of every Dispatch Map screen, and staff see it on the order.
- Route complete. Sent by the app on its own, once, when your route is finished: the last stop has its outcome, or dispatch took the orders still open off it (once more, if our server could not take it yet). It carries your phone's time, where the phone was, and the numbers your Done screen showed — how long the route took, from Start route (or your first Arrived or finished stop) to your last stop, each day on its own, and how many stops were delivered and how many not. Why: to record that the route finished, and to give you and dispatch your time on route and deliveries per hour. Who sees it: staff, beside our server's own count from your reports, and on Dispatch Map's routing screen, where your route reads Completed with its time on route and deliveries per hour; you, on your Done screen.
- Dock check-in. Only while the office has "Dock check-in" on for your login. When you scan the QR sign on a dock door, the app sends the door number, your load number, your phone's time, and where the phone is at that moment with its GPS accuracy (a fresh reading, never an older one); scanning the sign again checks you out. A scan made off the warehouse property, with a location too rough to judge, or at a door drivers do not use is refused and kept, with how far from the warehouse it was. While the office has "Selfie at dock check-in" on for your login, the app also takes a selfie with the front camera (camera only, never from the gallery) and sends it with the check-in; check-out never asks for one. While the office also has "Compare the selfie to the driver's photo" on, our server compares that selfie with your approved Load Scan profile photo and keeps the answer (a match, not a match with how similar, no face found, the check failed, or no photo to compare); it never stops you checking in, and it is not a liveness check. If the office requires check-in and you start your route without one before the day's cut-off, the app says so and dispatch is told, and it is counted against your login. Why: to know who is at which dock door, and that a check-in was made by the driver whose login it is. Who sees it: staff, on Dispatch Map's warehouse screens and the dock supervisor's tablet, beside the check-ins made in Load Scan; a dispatcher or admin opens a selfie one at a time; you, on your load screen.
- Dock line. Only while the office has "Dock line" and "Dock check-in" on for your login. When no dock door is free and you tap Get in line on your load screen, the app sends your load number, your phone's time and where the phone is at that moment with its GPS accuracy (a fresh reading); a tap off the warehouse property, with a location too rough to judge, or with no location is refused and kept, with how far from the warehouse it was, how accurate the location was, your phone's time of the tap and, with no location, why the phone had none. While drivers wait, a door scan lets you in only at the door the line called you to, or at a free door the line would give you next anyway; any other door scan is refused and kept like any other, and if you were not in the line you are put in it with your load number. While you wait with the load screen open, the app sends where the phone is about once a minute with its read of the line. Our server keeps your place, when you joined, the door you are called to and until when, whether the push reached our notification service, and every change to the line with who made it. A waiting driver judged off the property for longer than the office's set minutes is taken out of the line — judged only from positions your phone sent (with the app closed, the positions "Location from sign-in" already sends, where that is on for you); no position, or one too rough, never costs your place. Why: to call drivers to the dock doors in turn. Who sees it: staff, on Dispatch Map's warehouse screens and the dock supervisor's tablet (your name, load, place, how long you waited and, while you wait, how long your phone's positions have read off the property — never the positions themselves); you, your own place and door. Other drivers never see your name or your door.
5. What our server works out from your reports
- Each real delivery, filed under its customer. When it was made; the day, load and order; the place and its accuracy; our check and the distance; any exception (damaged or refused to sign); and your username and display name. Never for a test login. Why: so customer service can see where past deliveries to a customer were made. Drop spots, on-site times and reference photos are worked out from these. Who sees it: staff see the newest 50 for a customer, with each driver's name. The reference photo and drop spots another driver is shown never carry your name.
- Each customer's usual drop spots. Positions worked out from past deliveries there, each stop counted once and leaving out any customer service found were in the wrong place, or whose wrong-place flag they have not yet completed as the right place (section 2); how many deliveries make each one; the newest and oldest of those deliveries' times, each the earlier of the phone's time and when our server received it; and their delivery ids. No driver names. Worked out again each night. Why: to warn a driver who is far from the usual spot, and to name a spot for the door pick, the reference photo and the AI photo check. Who sees it: a driver with a stop at that customer on their own load sees the positions and counts. Staff see the whole record.
- Each customer's on-site time. For each delivery: the day, the order, the Delivered time and the driver's username; and every Arrived pressed at that stop that day, with its time, the username and our check. A delivery is left out while a wrong-place flag on that stop is not yet completed as the right place, and the record keeps why: where the flag stands, and the name of whoever in customer service is working it (section 2). Worked out again each night. Why: future arrival times. Nothing uses it yet. Who sees it: staff.
- The AI photo check's answer. Only while the office has "AI photo check" on for your login. It keeps the answer (same spot, different, or unsure), the model's words, the model used, its usage and cost; the driver, day, load, stop and customer; the drop spot it compared with; the earlier deliveries it tried for the reference photo; and each photo's size and fingerprint. A check that could not be made is kept as "not checked", with why. It makes at most one check per stop a day: for each stop it keeps which delivery had that check (the driver, day, load and stop, that delivery's id and photo name, and when), and another delivery on the stop that day is kept as "not checked". A test login has at most 20 checks a day: for each, it keeps which delivery had it (the login, day, load and stop, that delivery's id and photo name, and when), and that login's later delivery photos that day are kept as "not checked". Why: a second look at whether the photo shows the right drop spot. Who sees it: staff can read part of it (the answer, the model's words, the cost, and which earlier delivery was used). No screen shows it yet. Admins can read the whole record.
6. What staff do, and refused calls
- A LIVE press. When a dispatcher or admin presses LIVE on the Stops tab: who pressed it, when, on which order and load, for which driver (your username and name), and until when. Why: it raises your phone's position rate for 10 minutes (section 2). Who sees it: staff. Your phone gets only the faster rate and shows nothing different.
- A drop spot sent to you. The order, the pin, a note of up to 200 characters, who sent it and when, the board day it was sent from, and the board days it is kept under: the day the order is filed on and every later day (up to 14 days on) whose roster lists the order's load, one copy per day; a later day whose roster cannot be read when it is sent may be left out. Why: to show you where to leave the freight. Who sees it: you, on that stop, with the sender's name. Staff see it, and whether your phone has shown it.
- An attempt marked from your Can't deliver report. When customer service marks the order as an attempt, the mark stores your note as its details (cut to 200 characters; customer service can change it), the reason, when, and the name of the login that pressed it. A mark made before sign-in was required for marking may store no name. Undo, or a delete from the driver scorecard, removes the mark, and your note goes with it. Why: to record why the delivery became an attempt; the driver scorecard reads the attempts list. Who sees it: staff, on the order and on the attempts list. An order's history read without signing in shows only that the mark was made and its reason, not your note or who marked it. While Davis still uses NuVizz, the note can go to NuVizz (see "Who sees your information").
- A refused call to the photo check. If our server refuses a call to the AI photo check's background job, it records the job, the reason, a fixed message, the time and the internet address the call came from. No username. Our server makes this call, not your phone, so the address recorded is our host's, not yours. Why: so a refused call leaves a record.
-
Who allowed a delivery to be left unattended. The name of the person at the customer's who allowed it, typed by a dispatcher or admin (up to 80 characters), or a take-back of a name entered on the wrong order; who entered it and when; and which drivers' requests it answers, with each driver's username and name. Entries are only added, never changed or deleted. Why: so an unattended delivery carries who allowed it, which dispatcher entered it, and when. Who sees it: staff; only a dispatcher or admin enters or takes back a name. You see the name entered for your own request (see "Who sees your information").
-
Messages between you and dispatch. Each message's words (up to 1,000 characters), who sent it (the dispatcher's name and username, or your username), when our server received it, whether it was one of the one-tap replies, your phone's own time for a message you send, whether a dispatch message went to every driver out that day, and when you accepted a dispatch message; and, for your conversation, your name, the start of the last message, and when dispatch last read it. Why: so you and dispatch can message each other in the app, and dispatch can see that you accepted each message. Who sees it: you, in your own conversation (the last 14 days); staff, every driver's conversation; only a dispatcher or admin can send.
- Your phone's notification address. If you allow notifications, your phone's push token (an address Expo's push service gives the app), which kind of phone it is, and when it was saved. Why: so a message from dispatch rings your phone. Each message from dispatch is sent through Expo's push service (Expo, the company behind the app's toolkit), with its words and who sent it. Who sees it: staff can read the token; it is never shown on a screen. If you do not allow notifications, none of this is kept and messages still reach you in the app.
7. What stays on your phone
- The outbox. Every report and file you make is saved on the phone before it is sent, with your username. Why: so nothing you do is lost when there is no signal, while the office has "Offline saving" on (it starts on for every login). Saved items stay on the phone after they are sent, with what the report said (printed name, notes, place, scanned labels). Each photo and signature is a file of its own on the phone, and it stays there after the server has stored it: the app removes one only if we set our server to say so, and then only one our server has stored and checked; unset, the app keeps them all. Until the server has stored it, its saved item keeps a copy of it too. A dock check-in selfie stays in its saved item only until our server has answered the check-in, taking it or refusing it; then the picture is removed from the item. While a photo or signature is going to our Google Cloud Storage bucket, the phone also keeps where that upload got to, with a temporary address for that one upload, until the file is stored or set aside. Signing out does not clear the outbox. The app does not encrypt it. If another driver signs in on the same phone, they see only how many items are waiting for another login, not what they are.
- Positions waiting to send. Kept on the phone until the server has stored them; then they are removed. A batch the server refuses keeps its points.
- Settings and the location notice. A copy of the app's settings, kept with the username it was read for and used only for that login; a mark for each driver who pressed Continue on the location notice on this phone (never removed); and the running route and its position rates. The route is removed when it ends.
- Your loads. Your loads for two board days: each stop's customer, address and pin, contact name and phone, delivery window, requirements, freight, instructions, drop spots, the pieces scanned, and the outcome. For arrival times, each load also carries every stop on its route, with the driver name and username on the board, except a stop with no load number yet on a route name that two live loads share that day. The last good read is kept on the phone, with your username and when it was read, so your stops are still there after the app is closed or the phone restarts with no signal. It is shown only to your login. Each good read replaces it, and it is removed when you sign out or your sign-in ends. The app does not encrypt it.
- Reference photos and door picks. Up to 40 reference photos, and the door you picked at each stop. Held in memory only. Forgotten when the sign-in changes or the app is shut down.
- Camera files. The picture the camera takes and its resized copy, in the app's cache folder. The app does not delete them, except a dock check-in selfie's two files, which it deletes once the selfie is saved with the check-in.
- A stop you are waiting at. When you press "Nobody here to sign? Leave it unattended", the phone keeps the stop, its photos (with where and when each was taken), your request as our server last answered it, and the name dispatch entered with who entered it and when, under your username, so they are still there if the app is closed. Why: so the photos and the request are not lost while you wait. It is removed once the stop's delivery or Can't deliver report is sent, or when you press "Someone is here after all". It is never removed for its age. Each photo's own file stays on the phone, as other photos do. Signing out does not clear it. Only your login sees it. The app does not encrypt it.
- Phone backup. The app does not turn off your phone's own backup. If your phone backs up its apps (iCloud Backup on an iPhone, or Google backup on Android), what the app keeps on the phone, including the outbox, a stop you are waiting at, and the photos and signatures it keeps, can go into that backup. That backup belongs to your phone's account, not to Davis.
Test logins
The office can make a few test logins, for testing and for app store reviewers. A test login works its own practice route and never sees or reports on a real load. Everything it makes is marked as a test. Staff screens leave test records out. Through Dispatch Map's services, only admins and the test login itself can see them. A test login's positions are only counted, and no one is shown them.
Who sees your information
Davis staff
Signed-in staff see what each item above says. Every Dispatch Map service that hands out a driver's reports, photos or positions requires a signed-in login. These are the exceptions today:
- That an attempt was marked, through an order's history. An order's history read without signing in shows that an attempt mark was made, when, and its reason. It does not show your note or who marked it. The day's attempts list, which Davis's driver scorecard reads, and an order's Attempt box need a signed-in staff login, and only a dispatcher or admin can make or remove a mark.
- On our test site, when a stop was delivered. On the separate test site our pilot uses, the board marks a stop delivered with the delivery's time. While sign-in enforcement is off there, that mark can be read without signing in.
- The database itself. Davis's database rules refuse every read and write from anyone without a Davis sign-in. Your login's records and every driver report, position, check and flag are kept server-only: even a signed-in browser cannot read them directly; they reach staff only through Dispatch Map's services, as this section says. The photo and signature files and the server's logs are not in that database. The logs are kept by Netlify. The files are kept by Netlify, or in our Google Cloud Storage bucket once the office turns it on (see "Google and Netlify" under "Other companies").
You
You see your own records, as each item above says. For each stop on a load your phone shows, it also gets the stop's recorded outcome (Delivered or Can't deliver, the phone's time, and the report id), the pieces scanned, and whether customer service's drop spot was seen. These come with no names, from any login's reports on that load: for example, a driver who had the load before it moved to you. At a stop on your load you also see the customer's usual drop spots (no names), a drop spot customer service sent (with the sender's name), and a reference photo, which may be another driver's photo (section 3). If you ask to leave a delivery unattended, you see whether Dispatch Map has your request and how long it has waited, and the name dispatch enters for your request, with the dispatcher's name and when, or that dispatch took it back. A name entered for another driver's request, or for an earlier request of yours, is not sent to you.
Other drivers
Another driver may see one of your delivery photos as a reference photo, and the outcome of stops you reported on a load that later moves to them. Neither shows your name.
Other companies
- Anthropic (the AI photo check). Only while the office has "AI photo check" on for your login, and only when our server is set up for it. Each check sends two photos: an earlier delivery's photo of that drop spot and today's delivery photo, each as its smaller copy when it has one, and never a full-size photo larger than 3 MB, with fixed text. The request carries no name, address, position or time. Whatever the pictures show goes with them, and so does any detail the phone wrote inside the photo file (for example, when and where it was taken). What Anthropic keeps is set by its own terms.
- Amazon Web Services (the dock check-in face match). Only while the office has "Compare the selfie to the driver's photo" on for your login and our server is set up for it (it is not today). Each check sends two pictures: your dock check-in selfie and your approved Load Scan profile photo. The request carries no name, address, position or time. What Amazon Web Services keeps is set by its own terms.
- Google and Netlify (our hosts). Everything our server stores is held by Google and Netlify. Google holds the Firestore database. Netlify holds our server and its logs. Photos and signatures are held by Netlify until the office turns on our Google Cloud Storage bucket. From then on, new ones are held in that bucket, by Google: the app sends each file there itself, at an address our server gives it after checking the delivery, and the server counts it as stored only once it has read it back. One the bucket refuses or cannot take is held by Netlify instead, unless the office has turned that off. Files already stored stay where they are. What they may do with it is set by their own terms.
- Resend (sign-in email). Only if the office entered your email. Your email, username and display name go to Resend in an invite or password-reset email, with a one-time link. The phone app does not send these emails.
- NuVizz. The app sends nothing to NuVizz. While Davis still uses NuVizz, one staff action can pass your words on. When customer service marks an order as an attempt from your Can't deliver report, the reason and the details can go onto that order in NuVizz (another delivery system Davis uses) as a dispatcher note, in the form "ATT m/d: reason — details". The details start as your note, cut to 200 characters, and customer service can change them. The note carries no driver name. Once Davis stops using NuVizz, nothing goes to it.
- Estes (Estes orders only). Only while the office has turned it on (EFM_DRIVER_APP_SEND) and our server is connected to Estes. When you tap Arrived on an Estes order, our server tells Estes you arrived; when you deliver one, it sends Estes the customer's printed name, the number of pieces delivered and the time of the delivery, and the delivery photos you took (Estes requires three with each delivery). Whatever a photo shows goes with it. No signature, position or driver name is sent. What Estes keeps is set by its own terms.
- Your phone's own apps, when you tap. Directions hands one stop's pin or address, or customer service's drop-spot pin, to your maps app: Google Maps, or Apple Maps on an iPhone, with Google Maps offered when it is installed. On the route's map view, "Open all in Google Maps" (or "Open stops x–y in Google Maps") hands the route's stops, up to 10 per link, to Google Maps, on every phone. The app never sends your position; the maps app reads it itself. Call and Text hand the contact's number to your phone's dialer or messages app. The app never navigates or dials by itself. What those apps collect is set by their own terms.
- Google Maps, from staff. Staff can press "Both in Google Maps" in Signed for or on the customer service banner. That opens Google Maps with the delivery's place and the stop's pin.
- Services built into the app and the phone. The app's route map and drop-spot map use Google's maps on Android
(once the map is set up there) and Apple's maps on an iPhone; the app does not ask either map to show your position.
On Android, the barcode scanner uses Google's ML Kit; on an iPhone, Apple's own camera framework. Location comes
through Google Play services on Android and Apple's Core Location on an iPhone. Dispatch Map's own maps, where staff
see positions, are Google's. Our code does not control what these services collect on their own. On Android, Google
says this about two of them:
- ML Kit (the barcode scanner). Google's page lists, for every ML Kit feature: "Device information (such as manufacturer, model, OS version and build) and available ML hardware accelerators"; "Package name and app versions"; "Per-installation identifiers that are not intended to uniquely identify a user or physical device"; performance metrics; and error codes. Each is "Used for diagnostics and usage analytics". For some features ("thin features", in Google's words) it also lists a "Device identifier used for diagnostics and usage analytics". Google also says: "ML Kit does not transfer this data to third-parties." (https://developers.google.com/ml-kit/android-data-disclosure)
- The Maps SDK (the Android map, once it is set up). Google's page says: "The Maps SDK for Android automatically collects data like device metadata, crash metrics, IP address, and a unique identifier to improve Google services." It adds that, depending on how an app uses the map, it "may collect map interaction data, such as panning and zooming." (https://developers.google.com/maps/documentation/android-sdk/play-data-disclosure)
What Play services location, Apple's maps, Apple's camera framework and Core Location collect on their own is set by Google's and Apple's own terms. - Customers. No email or text we send to customers carries what this app collects.
Each company named here that receives your information from us (Anthropic, Amazon Web Services, Google, Netlify, Resend, Estes and, while Davis still uses it, NuVizz) handles it for Davis under its business terms with us, which protect it at least as this policy does.
What we do not do
- We do not sell your information. Our code sends it to no company other than those named above.
- The app includes no advertising, analytics, crash-reporting, push-notification or over-the-air update library. The app's own code adds no device id and no advertising id to what it sends. On Android, Google's barcode and map libraries collect device details and identifiers of their own (see "Services built into the app and the phone").
- The app's own code makes every call to one server: Davis's Dispatch Map. A test build of the app, for our pilot, calls our separate test site instead, which keeps what it is sent in its own database. Once the office turns on our Google Cloud Storage bucket, the app also sends each photo's and signature's file there, only at the upload address our server gives it.
- The app sends nothing to NuVizz. The one staff action that can pass your words on is described above.
- The app does not share your position while a route runs unless you started the route, allowed location, pressed Continue on the location notice, and the office has live location on for your login.
How long we keep it
What the code does today:
- It deletes none of your reports, photos, signatures, positions or logins.
- On our server, one kind of record can be deleted. An attempt mark can be removed by Undo or from the driver scorecard, and your note goes with it. The refused-call record keeps every row.
- Some records are updated in place. A customer's drop spots and on-site times are worked out again each night. A wrong-location flag gets its claim and completion. A photo's record is marked stored once its image arrives. An AI photo check's record gets its answer. Your login's last sign-in time is replaced on each good sign-in, and its details change when the office edits it or the password changes.
- On your phone, a batch's positions are removed once the server has stored them. A stop you are waiting at is removed as section 7 says. Photos and signatures stay on the phone (above). Your stored sign-in is deleted when you sign out or it ends, and so is the copy of your loads. Reference photos and door picks are held in memory only.
How long each kind is kept: we keep everything we store, with no end date, until we decide otherwise. We have no rule that deletes any of it. The table says where the code still does something else.
| What | How long it is kept |
|---|---|
| Your login, and the records about it | Indefinitely |
| The server's logs, with IP addresses | As long as our host, Netlify, keeps its logs |
| Your location at each report and with each photo | Indefinitely |
| Positions while a route runs | Indefinitely |
| Our location checks, and wrong-location flags | Indefinitely |
| Photos | Indefinitely |
| Signatures | Indefinitely |
| Printed names | Indefinitely |
| Refused-to-sign marks, damage notes and shorts noted on deliveries | Indefinitely |
| Signed Uline BOL copies | Indefinitely |
| Reports: Arrived, Delivered, Can't deliver, breaks, Start route, drop spot seen, pieces scanned, route complete | Indefinitely |
| Deliveries filed under each customer, drop spots and on-site times | Indefinitely |
| AI photo check answers | Indefinitely |
| LIVE presses, and drop spots sent to you | Indefinitely |
| Attempt marks with your note | Indefinitely, unless the office removes the mark (Undo, or the driver scorecard) |
| Who allowed a delivery to be left unattended, and your requests to leave one | Indefinitely |
| The refused-call record | Indefinitely |
| What stays on your phone: the outbox, waiting positions, settings, your loads, camera files, a stop you are waiting at | As "What the code does today" says above. Photos and signatures stay on the phone |
Deleting your data or your login
- The app has no sign-up and no delete button.
- The office can turn your login off on Account & logins. Then it stops working: your phone signs out and shows "This login has been turned off. Ask the office." Turning a login off does not delete it, or anything you sent. Our code never deletes a login.
- To ask us to delete your login or your data, contact us (below). When you ask, we turn your login off. We keep the records of the deliveries and reports you made, because they are Davis's business records of the freight we delivered and how; we keep them as "How long we keep it" says.
- On your phone, signing out deletes your stored sign-in and the copy of your loads. It does not clear the outbox (section 7).
Saying no to live location, and stopping it
- While the office has "Location from sign-in" and "Location required to start a route" on for your login, which is how the app comes, the app shows the location notice (section 2) right after you sign in, before it asks for location, and nothing else in the app opens until you have pressed Continue and the app may use your location (on an iPhone, Always). It offers Open Settings, Try again and Sign out. It is checked again each time you come back to the app, so turning location off in your phone's settings brings it back. Start route then asks nothing more.
- Otherwise, the first time you press Start route on a phone while live location is on for your login, the app shows the location notice (section 2) before it asks for location.
- Location is required to run a route while the office has "Location required to start a route" on for your login, which is how the app comes. Then the notice has no way to start without sharing: your route starts only once the app may use your location, and on an iPhone that means Always. Until then the route does not start, nothing is sent, and the notice says where to change it in your phone's settings. A route you have already started is never held up for this: its stops always open.
- With that setting off, "Not now — start without sharing my location" starts your route without sharing. Start route itself still records where the phone was, as section 2 says.
- Once you press Continue on a phone, the app remembers it for your login on that phone and does not show the notice again, unless location is required and the app may not use your location when you press Start route. Your later routes on that phone share your location from Start route, while live location is on for your login and the app is allowed to use location.
- On a started route that is not being shared, "Share my location" opens the notice again.
- Sharing stops when you finish the route or sign out, and in the other cases listed in section 2. The app has no button to stop sharing during a route, or before it.
- The office's "Live location for customer service" setting covers all drivers at once (Off, Test drivers only, or Everyone). It cannot turn sharing off for one driver alone.
- To withdraw your consent, you can turn off location for Dispatch Map Driver in your phone's settings, or tell the office (see Contact) and they can turn "Live location for customer service" off. While location is required, a new route cannot start with location turned off, and while "Location from sign-in" is on as well, the app does not open until location is allowed again; you can still sign out.
How we keep it safe
- Passwords are kept only as a salted scrypt hash. No Dispatch Map service hands it out.
- After 8 wrong passwords, a login locks for 15 minutes. Each server instance also slows repeated sign-in tries from one internet address.
- Your sign-in token is signed by our server and kept in your phone's secure storage. On every request the server checks its signature and your login's sign-in counter, so the office can turn a login off or sign it out everywhere.
- Every Dispatch Map service that hands out a driver's reports, photos or positions requires a signed-in login, with the exceptions listed under "Who sees your information".
- A driver login has no staff rank, so it passes no staff sign-in check.
- A store build takes photos only with the camera. The store for photos and signatures has no delete and no overwrite. Each report is written once and never overwritten.
- Our database rules refuse anyone without a Davis sign-in, and keep the driver records and the logins server-only: a browser cannot read them, only our server can.
- On your phone, the app does not encrypt the outbox (section 7). Your sign-in is kept in the phone's secure storage.
Children
Dispatch Map Driver is for Davis's drivers and contractors. Every login is made by the office; nobody can sign up in the app. The app is for people 18 and over. It is not meant for children, and we do not knowingly collect information from anyone under 18.
Changes to this policy
When the app changes what it collects, why, or who sees it, we will post the updated policy at this same address, with a new effective date at the top.
Contact
Davis Delivery Service Inc.
Postal address: 943 Gainesville Highway, Buford, GA 30518
Email for privacy questions and deletion requests: customerservice@davisdelivery.com