DSP Performance Hub extension privacy policy

Effective October 16, 2026. This policy covers the DSP Performance Hub Chrome extension and its operational-data connection to the configured Hub workspace.

Purpose and collection

The extension synchronizes authorized Amazon DSP operational data for route performance and working-hours dashboards. Collection is off until you configure a workspace, choose jobs and authorize data sharing. It uses a signed-in Amazon Logistics tab; it does not collect unrelated browsing history.

Daily routes collect raw route summaries, itinerary summaries and itinerary details for today. Working hours collect company-wide compliance responses in calendar weeks covering the last 14 station dates. Raw boundary-week responses can include dates outside that window; dashboard views filter to the last 14 dates. Responses may include driver names and identifiers, work and rest hours, break and delivery activity, route and stop details, delivery addresses and location information. Raw Amazon responses are preserved rather than limited to the fields currently shown in the dashboard.

Where data goes and who can access it

Enabled jobs send those records over HTTPS to the Hub address and organization you select. The default service is https://dspperformancehub.com. A different configured Hub operator becomes the recipient of the same data; only select a destination you trust and are authorized to use. HTTP is allowed only for local development. The Hub stores records in its configured PostgreSQL database and permits collection uploads from active workspace members and restricts raw source-data viewing to authorized workspace management and platform administrators. Hosting/database providers process records to operate that service.

The extension does not sell data, use it for advertising, credit decisions or unrelated profiling, or transfer it to data brokers. Human access is limited to authorized workspace functions and necessary service support or legal obligations. The use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Authentication and local storage

Amazon session and HMAC authentication material is used inside the Amazon page; the extension does not send those keys to the Hub or store Amazon passwords. Hub requests use your existing browser-managed Hub session. Extension local storage contains the Hub address, organization/station settings, remembered company/provider/station connection identifiers, consent, enabled jobs, job status and freshness metadata. Raw operational responses are sent to the Hub rather than retained as an extension archive.

Retention and deletion

On the default Hub, saved route captures are retained by organization, station, day and collection. Working hours preserve the latest successful snapshot for each end date; a refresh replaces only the same end date. Previously overwritten or purged source responses cannot be reconstructed. Incomplete attempts may remain until a later successful refresh; stale collecting attempts are pruned on new working-hours runs. These are operational retention rules, not a promise that offline backups expire at the same moment. Alternate Hub operators control their own retention and backup policies.

To stop future collection, disable all enabled jobs and categories and save in Extension settings, or remove the extension. Uninstalling removes local extension settings through Chrome; it does not delete records already uploaded to the Hub. For access, correction, export or deletion of uploaded data, contact your DSP workspace administrator and ask them to involve the DSP Performance Hub platform administrator. Requests must be verified for the affected organization. Consult your workspace operator about backups and legal retention requirements.

Support and privacy contact

For extension support, privacy questions, or requests to access, correct, export or delete uploaded data, email Joeystillwell.onth@gmail.com. Include your organization name and request type; do not email passwords, session keys or sensitive delivery records. We verify authority for the affected organization before handling data requests.

Security and changes

Hub access requires an authenticated authorized session; uploads have bounded input validation and organization-scoped storage. Collection pauses when authentication fails. No system can guarantee absolute security. Material changes to the collection destination or disclosed purpose require updated disclosure and consent. Review this policy when updating the extension.