Privacy policy
Updated October 28, 2026
About Dispatch
Dispatch is software that Amazon delivery service partners (DSPs) use for timecards, vehicle inspections, uniforms, documents and messages with their team. Each DSP decides who on its team uses Dispatch and what they can see.
What Dispatch collects
- Your account: your name, email address, role, when you sign in and the display settings you choose, such as text size.
- Your DSP’s records: timecards, vehicle inspections, uniforms, documents, messages and other records your DSP adds or brings in from services it connects.
- Technical details: your IP address, browser and the times of your requests, kept to keep accounts secure.
Google user data
A DSP can connect a Google account to keep its documents in Google Drive. Dispatch then receives that account’s email address and access to its Google Drive, which it uses for the DSP’s Documents folder and the files its team adds to it. We recommend a Google account kept for Dispatch alone.
- Dispatch uses this access only to make the DSP’s folder; to list what’s in it, whoever put it there; to open, upload, download, rename and trash those files; to show previews of them; to bring in files the team adds from elsewhere, as a shortcut when someone else owns them; to save there the files the DSP imports from its Slack channels, and the Slack canvases it keeps as Google Docs, written over as each canvas changes; and to share the folder, and files the team adds, with the DSP’s team.
- To keep the folder up to date, Dispatch reads Google’s list of what changed in that Drive and sets aside anything outside the folder. It doesn’t open, change or keep files outside the folder, except one the team adds or a shortcut in it points to.
- When a team member links their own Google account, Dispatch receives only its email address, to share the folder with it, and gives up its access at once.
- When a team member adds a file from their own Google Drive, Google asks them to choose it, and Dispatch receives access to that file only, to move it into the folder or share it with the DSP’s Google account.
- Dispatch keeps the account’s access encrypted and deletes it when the DSP disconnects Google. You can also remove it at any time in your Google account.
- Dispatch doesn’t sell Google user data, use it for advertising, or use it to train AI models.
Dispatch’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Slack data
A DSP can add Dispatch to one or more of its Slack workspaces. For each workspace, Dispatch then receives its name, ID and logo, and access tokens for Dispatch’s app in that workspace.
- Dispatch uses this to know which DSP each workspace belongs to, to list the workspace in the DSP’s Settings, and to show, on Dispatch’s Home tab in Slack, which DSP the workspace belongs to. When someone opens that tab, Slack tells Dispatch their Slack user ID, which Dispatch uses only to show them the tab and doesn’t keep. Dispatch keeps a copy of the workspace’s logo, downloaded from Slack, to show beside the workspace’s name.
- Dispatch reads the names of the workspace’s public channels, and of the private channels someone invites it to, so the DSP can choose which channels Dispatch is in. It joins or leaves a channel only when someone at the DSP chooses to.
- Dispatch reads the workspace’s members: each one’s Slack user ID, name, display name, email address, phone number if their profile has one, and whether their account is active or a guest. It leaves out bots. Dispatch keeps these only to match each member to the same person in the DSP’s other records, such as its payroll or Amazon’s roster, so the DSP sees one record for each person, and to know who sent a direct message, whom to open one with, whose Slack profile photo to send one under, and how to reach the member a conversation is with. People at the DSP whose role lets them manage Driver Match see them. People with access to Communications see who each direct message is with; every active member of the workspaces where it’s on, to message them, with their name and the role and photo Driver Match has for them; and, beside a conversation, a phone number and email address Driver Match has for the member it’s with, which may be those on their Slack profile. No one else at the DSP sees them.
- When the DSP switches on Import Files in a workspace and links a channel to a folder in its Documents, Dispatch reads the files and photos posted in that channel from then on, and saves a copy of each in that folder. Slack tells Dispatch each time a file is shared in a channel Dispatch is in. For files in a linked channel, Dispatch keeps each file’s ID, name, type and size, who posted it and how saving it went; it matches who posted it to the DSP’s team by email address, to show who added it. It ignores files in channels that aren’t linked, and files posted while Import Files is off. A copy stays in Documents if the file is later deleted in Slack.
- When the DSP switches on Sync Canvases in a workspace and links a channel to a folder in its Documents, or chooses canvases in a channel, Dispatch reads those canvases, the pictures in them and the names of the members they mention, and keeps each as a Google Doc in that folder, written over whenever the canvas changes. Slack tells Dispatch each time one of those canvases changes, and each time a file is shared in a linked channel. For each canvas, Dispatch keeps its ID, title, when it last changed and where its Doc is; it matches who made it to the DSP’s team by email address, to show who added it. It doesn’t read canvases in channels that aren’t linked unless they’re chosen. A Doc stays in Documents if its canvas is later deleted in Slack, or no longer synced.
- Anyone in the workspace can send Dispatch’s app a direct message, and Slack tells Dispatch of each one. When the DSP uses Communications in the workspace, Dispatch reads it, with any photos or files attached, so people at the DSP can read and answer it on Dispatch’s Communications page. Dispatch keeps these messages, with their photos and files, and those sent by people at the DSP, for that DSP until the DSP is deleted from Dispatch. When someone edits a message they sent in Slack, Dispatch keeps the edited text in place of the earlier text and marks the message as edited. A message stays if it’s later deleted in Slack. Only people at the DSP whose role gives them access to Communications see them.
- When the DSP uses Communications in the workspace, Dispatch also lists its app’s direct messages there and reads them from Slack’s history, to catch up on any it missed. It never keeps a message sent before Communications was on there.
- Dispatch sends each message from someone at the DSP to that direct message in Slack, under the full name of the person who wrote it and their Slack profile photo, which it reads, without keeping it, from the member with their email address in that workspace, or else in another of the DSP’s workspaces. For someone with no photo of their own in Slack, or no member with their email address, it sends the message under an image of their first and last initials instead, which it publishes at a public web address, because Slack can only show an image from one. Photos someone at the DSP adds to a message are kept with it, and uploaded to the workspace’s Slack, shared in no channel, to show in the message.
- When someone at the DSP with access to Communications messages a member of the workspace first, Dispatch opens a direct message with them from its app.
- Someone at the DSP with access to Communications can also send one message, with any photos, to many members at once. Each gets it in their own direct message with Dispatch’s app, under the sender’s name and photo, and doesn’t see who else it went to or what they answer. Dispatch keeps the message with its photos, who sent it and the group’s name, which may hold first names. It also keeps whom it went to, by their Slack user ID and their name in Slack then, and how sending it to each went. Only people at the DSP whose role gives them access to Communications see any of it, and it stays for that DSP until the DSP is deleted from Dispatch. Each copy carries, unseen in Slack, only Dispatch’s ID for the message, which Dispatch looks for in the direct message’s history when a send was cut short, so it doesn’t send anyone a second copy.
- When the DSP doesn’t use Communications in the workspace, Dispatch answers each direct message to its app “DSP Messaging is unavailable”, and doesn’t keep it.
- Dispatch doesn’t read any other messages in the workspace, files other than those in the channels linked for Import Files or sent to its app, or canvases that aren’t linked or chosen for Sync Canvases.
- Dispatch keeps the access tokens encrypted. It deletes them, the workspace’s logo, the members it read, and what it kept of linked channels, chosen canvases, files and canvases, when the DSP disconnects the workspace or someone removes Dispatch from it in Slack. Copies and Docs already saved in Documents stay there. Direct messages stay too, with who sent each and the photos and files attached to them, and so do messages to groups, with whom each went to.
- Dispatch doesn’t sell Slack data, use it for advertising, or use it to train AI models.
Texts from a DSP’s dispatch phone
A DSP can pair the Android phones its drivers and others text, its dispatch phones, with Dispatch, through Dispatch’s app on each phone. Each phone then sends Dispatch the texts it receives and those sent from it, straight from the phone, with no other service in between. Carriers carry the texts themselves, as they carry any text.
- For each phone, Dispatch keeps its name, number and model, the version of Dispatch’s app on it, who at the DSP paired it and when, and when it was last in touch, to show the DSP its phones. It keeps the code a phone pairs with, and the phone’s key, only in a form that can’t be turned back into them. People at the DSP whose role lets them manage its connections or its phones manage them in Settings; people with access to Communications see their names and when they were last in touch.
- For each text, Dispatch keeps the other person’s phone number, what it says, its pictures and other files, when it was written and which phone it came through; and for a text sent from Dispatch, who at the DSP wrote it and whether it was sent and delivered.
- Dispatch files each text under whom it’s with: a driver’s own phone number by the DSP’s records of its team; a company work phone, which drivers pass between them, by the route data from Amazon the DSP brings in, which says which work phone each driver has each day, so a day’s texts with it go to the driver whose latest work phone it is that day; anyone else by their number, or by a name someone at the DSP saved for it. Where today’s route data shows no one driver with a work phone, someone at the DSP can choose which of today’s drivers its texts are from.
- People at the DSP with access to Communications read and answer the texts on Dispatch’s Communications page. They see the names saved for numbers and the numbers blocked, and the names and phone numbers the DSP’s records hold for its team, to text them first. A text sent from Dispatch goes from the DSP’s phone with nothing added, so the person it’s to sees only the DSP’s number. A blocked number’s texts are kept, but set aside.
- Dispatch keeps who at the DSP added each picture, saved each name, blocked each number, chose each driver and marked texts done, and when.
- Dispatch keeps the texts, with their pictures and files, the names saved for numbers and the numbers blocked, for that DSP until the DSP is deleted from Dispatch. A picture someone at the DSP adds to a text and doesn’t send is deleted after a day, while the DSP uses Communications. A phone the DSP removes can no longer reach Dispatch; what Dispatch kept of it, and the texts it sent, stay.
- Dispatch doesn’t sell texts or phone numbers, use them for advertising, or use them to train AI models.
How it’s used
Only to run Dispatch for your DSP: to show your team its records, send and receive its messages in Slack and by text, keep accounts secure, send the emails Dispatch needs to (such as invitations and password resets) and help when you ask for support.
Who it’s shared with
The people at your DSP whose role lets them see it, the services that host Dispatch and deliver its email, and anyone the law requires. Dispatch never sells information.
Keeping and deleting
Dispatch keeps your DSP’s information while it uses Dispatch. To have your own or your DSP’s information deleted, email us and we’ll delete it within 30 days.