What Fleet is
Fleet is an operations platform for Amazon Delivery Service Partners (DSPs), hosted at fleetdsp.app and operated by SF Services Solutions LLC (the Fleet team). Each DSP's data lives in its own account and is visible only to that DSP's members and, where a DSP has granted access, to the Fleet team supporting it.
When the Fleet team sees your data
Normally, not at all: we enter a DSP's account only after someone there approves it. Support asks, an Admin or Manager says yes, the visit runs for a limited window, you can watch what we do and end it in one click, and everything we change is recorded as us. You can read the whole history under Support → Fleet activity.
There is one exception. If something is wrong and nobody at your company is able to approve — a locked-out Admin, a broken sign-in — a Fleet owner can open emergency access without waiting. It is recorded the same way and appears in Fleet activity marked as emergency access, with the reason we typed. While Fleet is in beta these do not email or alert you; the record is there for you to read either way, and we will tell you if anything of yours changed.
Data the web app holds
- Account data — names, work email addresses, usernames and roles of the people a DSP adds to its account.
- Operational data — the rosters, routes, schedules, vehicle and driver records, scorecards and safety reports a DSP uploads or syncs. This can include the names and work identifiers of the DSP's drivers.
- Activity records — an audit log of changes made in the account, kept so a DSP can see who changed what.
This data is used to run the product for that DSP and for nothing else. We do not sell it, rent it, or use it for advertising. Fleet runs on servers we operate ourselves; the third parties that touch data at all are these, each bound to process it only on our instructions:
- Amazon Web Services (Amazon SES) — transactional email delivery: they handle the recipient address and the message of the email Fleet sends.
- Stripe — subscription billing: they handle the payment details, which never touch Fleet's servers.
- Anthropic — when a DSP uses the vehicle-damage inspector, Anthropic's Claude receives only the van photo and its unit number to produce the damage report — never account data, driver records or anything else. These are photos of vehicles: the inspector is not for photographing people or documents, and DSPs must not include them. Photos are used solely for that report.
- Slack — only when a DSP connects its own Slack workspace, and only the messages that feature sends to it.
- Twilio — text-message delivery, only when a DSP enables the SMS add-on described below: they handle the enrolled phone numbers and the content of the texts Fleet sends.
SMS/text messaging (optional add-on)
Text messaging is an optional add-on a DSP may enable as part of its subscription. When a DSP activates it — for its existing roster or for a driver added later — each of its drivers receives a one-time text inviting them to confirm they want shift and duty notification texts from Fleet. Only drivers who reply YES to that message are enrolled and receive further texts. Nobody is enrolled without that confirmation, and consent is never a condition of employment or of any purchase.
Enrolled drivers receive texts related to their duties: shift reminders, schedule or route changes, dispatch updates, and account-related alerts. These are operational messages only — Fleet does not send marketing or promotional texts. Message frequency varies with the DSP's scheduling and dispatch activity (typically a few messages per scheduled shift day). The recipient's message and data rates may apply.
To operate the service Fleet keeps each enrolled driver's mobile number, enrollment status (the YES, any STOP, and their timestamps), and a record of the messages sent. This information is used solely to run the messaging service. No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties. It will not be sold, and will not be used for purposes unrelated to the Services described here.
- Opting out — a driver may reply STOP to any message; they receive a one-time confirmation of the unsubscribe and nothing further. Opting out only stops the texts: nothing else about the driver changes in Fleet, and shift and dispatch information reaches them through the DSP's other channels instead. Our terms require DSPs to treat texting as optional — never a condition of employment.
- Help — a driver may reply HELP to any message for information about the program and how to opt out. Questions about the messages themselves — shifts, routes, schedules — are for the driver's employer, who manages their enrollment.
- Supported carriers are not liable for delayed or undelivered messages.
The Fleet Sync browser extension
Fleet Sync is our Chrome extension. It captures operational data from the portals a DSP already uses — the Amazon DSP Portal, When I Work and Netradyne — and delivers it to that DSP's own Fleet account. In plain terms:
- Everything is off until you turn it on. The extension captures nothing and sends nothing until a signed-in user explicitly enables a data kind in its popup.
- What it handles — export files you download from those portals and, for the kinds you enable, the operational data those pages load (routes, schedules, scorecards, fleet and driver records). This can include driver names and work identifiers. It does not read pages outside the portals listed in its permissions, and it does not touch browsing history, keystrokes or any personal browsing.
- Where it goes — only to the Fleet server your account lives on, over HTTPS, authenticated by a token you generate in your Fleet profile. Never to any third party.
- What stays local — the extension keeps its settings, a short activity log and file fingerprints (for de-duplication) in your browser's extension storage. Its optional debug sampling stores data locally only and is exported only by your own click.
- Limited Use — our use of data obtained through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements: the data is used solely to provide Fleet's user-facing features to the DSP it belongs to, is never sold, and is never used for advertising or creditworthiness purposes.
What Fleet Sync does not collect
- Passwords — never. The extension reads pages you are already signed into; it never sees, asks for or stores your portal credentials.
- Browsing history, or anything from sites outside the portals listed in its permissions.
- Keystrokes, mouse movement, or form input of any kind.
- Your location.
- Personal communications — email, messages, documents.
Retention and deletion
Operational data is kept while a DSP's account is active, because it is the DSP's working record. When an account closes, or on a verified deletion request, we delete its data within 30 days, keeping only what the law requires us to keep. Switching a data kind off in the extension's popup — or removing the extension — stops the corresponding capture immediately.
Your rights
Fleet serves DSPs in the United States and Canada. You can export your data from the app at any time, and ask us to correct or delete it — write to the address below and we take care of it. That covers the rights the CCPA/CPRA (California) and PIPEDA (Canada) give you over personal information: access, correction, deletion, and knowing what is held.
Children
Fleet is a business tool and is not directed at anyone under 16.
Changes
Material changes to this policy are announced to account Admins at least 14 days before they take effect; the effective date above moves when they do.
Contact
Questions about this policy or your data: [email protected].