Cookie & Storage Policy
Last updated: August 16, 2026
relay-dispatch.com sets no cookies of its own and uses no advertising or cross-site tracking. What it does use is a small amount of storage inside your browser to remember two things (which view of the homepage you prefer and, while a tab is open, an unfinished capacity request) plus a first-party analytics beacon that we run ourselves. This page names each item, says what it holds, how long it lasts, and how to clear it, so there is nothing to guess at.
1. Cookies: none of our own
The site does not set any first-party cookies today: no session cookie, no login cookie, no consent cookie, and no analytics or advertising cookie. That is why you do not see a cookie banner. Our hosting and backend providers may set strictly necessary cookies of their own for security or load balancing when they serve the site or receive a form submission [CONFIRM: audit the live site for any platform-set cookies from the hosting network and list them here if present]. If we ever add a cookie that is not strictly necessary, we will update this page and ask for consent first where the law requires it.
2. Local storage: your homepage preference
The homepage can be viewed from a driver angle or a shipper angle. When you switch, the site stores a single value named relay-audience in your browser's local storage (either carrier or freight) so the next visit opens on the view you last chose. It contains nothing about you personally, is never sent to our servers, and stays until you clear site data or switch again. On each page load the site also removes an older value named relay-theme, left over from a light-and-dark mode setting the site no longer has, so nothing stale lingers in your browser.
3. Session storage: your unfinished capacity request
While you work through the four-step capacity request on the For Shippers page, the site saves your progress in the browser tab's session storage under a key named relay-quote-draft followed by the equipment type you picked (for example relay-quote-draft:reefer). The draft holds the step you were on and everything you typed: stops, dates and windows, freight details, contact details, notes, and references. It exists only in that one tab, so a second tab or window starts fresh; it is written a moment after you stop typing; it expires twenty-four hours after it was last saved; and it is removed when you send the request, choose Start over, or close the tab. Nothing in the draft is sent to Relay until you press send, and the two invisible anti-spam signals described in our Privacy Policy are never written into it.
4. First-party analytics beacon
To learn which pages and tools people actually use, the live site sends short anonymous events to our own analytics endpoint using your browser's beacon feature: page views, calculator opens and shares, the shipper view being shown, and the start, steps, and submission of an application or capacity request, and contact form sends. Each event carries the event name, the page path, a timestamp, and a little context such as the equipment type or which button opened the request wizard. No cookie or identifier is set to tie events together, no personal details ride along, and no third-party analytics or advertising service receives them. Because the events are ordinary web requests, our server sees your IP address in transit [CONFIRM: whether it is stored, truncated, or discarded]. Analytics do not run in preview or test builds of the site.
5. Requests to other companies' servers
Everything a page is built from — the page itself, its images, maps, scripts, and typefaces (the site asks for Helvetica or Arial, which your device already has; the Inter fallback, if your device needs it, is served from our own hosting rather than a font service) — comes from our hosting network; no font service, content network, tag, or pixel from another company is loaded. The only requests that leave the page are the anonymous analytics events described above and the forms you choose to send, which go to our backend functions on Supabase. Links to third-party sites (FMCSA, state agencies, partners) take you off our site and are subject to those sites' own cookie practices. There are no embedded social widgets, chat vendors, ad pixels, or session-recording tools on the site; the small chat helper in the corner is scripted on the page itself, keeps nothing between visits, and sends nothing anywhere.
6. What we do not do
We do not use advertising cookies or pixels, retargeting, cross-site or cross-device tracking, browser fingerprinting, or session replay. We do not sell or share browser data with data brokers or advertisers, and we do not combine site usage with your form submissions to build a profile of you. If that ever changes, this page will change first.
7. How to clear or block storage
You can remove everything the site stores by clearing site data for relay-dispatch.com in your browser's settings (usually under Privacy or Site Settings), or by clearing all browsing data; a private or incognito window discards session storage when it closes. Clearing site data resets your homepage preference and removes any unfinished capacity request, so send or note down anything you want to keep first. Browsers also let you block storage or beacon requests entirely; the site will still work, but it will not remember your view or your draft, and we will not receive usage events. Because we set no cookies, there is no cookie consent to withdraw; if you have questions about anything on this page, write to support@relay-dispatch.com.
8. Changes to this policy
If we add, rename, or remove any browser storage or beacon on the site, or introduce a cookie, we will update this page and the date at the top, and where the law requires consent for a new item we will ask for it before setting it. This page is meant to match the site exactly, so if you notice something stored by relay-dispatch.com that is not described here, please tell us at support@relay-dispatch.com and we will fix the page or the site.
This policy is a template pending review by legal counsel before launch.