Dispatch Stream
Load Lead Capture Extension Privacy Notice
1) Scope
This notice applies to the Dispatch Stream Load Lead Capture Chrome extension (the "Extension"). The Extension works with the Dispatch Stream platform for authenticated Dispatch Stream customers and authorized users.
2) What the Extension accesses
When the user clicks the inline Add to Dispatch Stream control, the Extension reads only the currently selected or open load detail needed to send one selected load into Dispatch Stream Load Leads. Supported board domains include one.dat.com, navispherecarrier.com, subdomains of navispherecarrier.com, and navisphere.chrobinson.com.
This may include visible posting fields such as:
- Origin and destination city/state
- Pickup and delivery dates or appointment windows
- Rate, miles, rate per mile, and market-rate guidance when visible
- Broker or shipper company name, reference numbers, visible phone number, and visible email
- Equipment, weight, commodity, comments, and notes visible in the selected detail
- The source page URL and visible board identifiers when shown
3) What the Extension stores locally
The Extension stores bounded pending captures, selected-load preview state, and connection preferences in Chrome extension storage so the user can review the selected load or retry sync if Dispatch Stream is not ready. Passive preview state is read-only and does not create or update a Load Lead. Load Leads are created or updated only after the user clicks the inline Dispatch Stream board button for one selected/open detail, or clicks Send pending leads in the popup to retry already-pending captures. The Extension does not maintain a loadboard database, does not crawl in the background, and clears successfully synced pending captures.
4) What the Extension sends to Dispatch Stream
After explicit user action, the Extension sends the selected capture to the user's authenticated Dispatch Stream workspace. Dispatch Stream saves it as a separate Load Lead, either linked to a valid posted truck or held for assignment in Unlinked Captures.
5) What the Extension does not do
- It does not crawl or poll DAT, Navisphere, or other load boards in the background.
- It does not bulk-harvest search results or entire result lists.
- It does not create Load Leads from passive selected-load previews.
- It does not request Google OAuth, Gmail, or Google API scopes.
- It does not read, modify, draft, or send Gmail messages.
- It does not write directly to Firestore or bypass Dispatch Stream authentication.
- It does not store Dispatch Stream passwords, session cookies, or long-lived Dispatch Stream credentials.
- It does not store OAuth tokens, API keys, or secrets in Chrome extension storage.
- It does not publish captured load data to other customers outside the authenticated Dispatch Stream workflow.
6) How saved data is handled
Once a user saves or syncs a Load Lead in Dispatch Stream, the saved record is handled under the Dispatch Stream platform privacy policy, customer account controls, and applicable workspace retention settings.
The Extension's use of selected load-board information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Captured data is used only to provide or improve the Extension's single purpose: moving user-selected load opportunities into the authenticated Dispatch Stream Load Leads workflow.
7) Contact
Questions about this Extension or its data handling can be sent to support@dispatchstream.com.