← Dispatch Pro

Cookie Policy

Last updated: September 5, 2026 · Privacy Policy · Terms of Service

Working draft for the review phase — wording may change before launch.

1. The short version

One cookie, and it only keeps you signed in. No advertising cookies, no analytics cookies, no third-party cookies, no tracking pixels, and nothing shared with anyone for marketing. There is no consent banner because there is nothing here to consent to beyond what makes signing in work — see section 4.

2. The cookie

This is the complete list.

NameWhat it holdsHow longWhy
dp_session A random token. Nothing else — not your email, not your name, not an identifier that means anything outside our own database. 30 days from last use Strictly necessary. It is what keeps you signed in between pages. Without it you would sign in again on every click.

It is set with HttpOnly (JavaScript on the page cannot read it), SameSite=Lax (another site cannot cause your browser to send it), and Secure over HTTPS. On our side we store only a one-way hash of the token, so the database does not contain anything that could be replayed as your session. Signing out clears it immediately.

3. Other things stored in your browser

Cookies are not the only way a site can keep something on your device, so here is the rest of it. These use your browser's local storage, are readable only by this site, and are never sent to us — they stay on your device until you clear them.

KeyWhat it holdsWhy
dispatch-pro-tenant
dispatch-pro-driver-tenant
Which company you last worked as, on the dispatch board and in the driver app. People who work for more than one company would otherwise re-pick on every visit. Cleared by the company switcher.
dp.maph.… How tall you dragged a map panel, one entry per map. So a map you resized stays that size. A number, nothing more.

Neither identifies you, and neither is used to build a profile or follow you anywhere.

Consent rules exist for storage that is not necessary to deliver the service you asked for — advertising, analytics, cross-site profiling. Everything above is either strictly necessary (the sign-in cookie) or a setting you created yourself by using the product (which company, how tall the map). None of it is shared, sold, or used for marketing.

So a banner would ask you to approve something we do not do. If that ever changes — if we ever add analytics or anything that follows you — we will ask first, and the default will be off. This page and the Privacy Policy are updated before any such change takes effect, not after.

5. Your control

6. Third parties

None set anything. The pages load no third-party scripts, fonts, frames, or images. The map library is served from our own servers, and map tiles are fetched through our server rather than from the map provider directly — so the map provider never sees your browser or your address. This is enforced by a Content Security Policy that only permits the page to load and connect to this site, not merely by our intention to keep it that way.

7. Questions

[OPERATOR LEGAL NAME] · [CONTACT EMAIL]. Privacy requests go to our privacy officer, named in the Privacy Policy.