Cookie and browser storage notice

1. First-party account cookies

Wayboro sets the following cookies after an approved driver or operations user signs in. Public discovery, quoting, tracking, and privacy-request pages do not require these account cookies.

“Do not require” does not mean an existing cookie is absent from every public request. Until sign-out, expiry, or removal, the browser may still attach a same-origin account cookie automatically. Public workflows do not use it to grant access to another person's order or privacy request.

Wayboro uses the __Host- prefix on its secure web origin. Supporting browsers accept these cookies only from HTTPS with Secure, path /, and no Domain attribute, which prevents a subdomain or narrower path from replacing them.

Signing out invalidates the server-side refresh credential and asks the browser to clear all three cookies. The server may reject them earlier after a credential change, account restriction, revocation, or security event. Blocking them prevents protected portals from staying signed in.

During the Wayboro name transition, an existing access_token, refresh_token, or XSRF-TOKEN may remain accepted only within its original maximum age. A successful sign-in or refresh replaces and clears the legacy names; sign-out clears both formats.

2. Checkout data stored in this tab

Wayboro uses sessionStorage, not persistent localStorage, to recover an interrupted checkout in the same browser tab. Storage is a convenience only: denial, corruption, or quota failure does not prevent a fresh checkout. Each new record has an explicit timestamp and is rejected and removed at its boundary.

Older checkout formats did not contain a verifiable saved time. Wayboro now removes those unbounded legacy records instead of restoring them and silently restarting their lifetime. This can require re-entering an old draft, but prevents stale contact details or a private payment capability from being retained beyond a proven boundary.

Builds before version 2026-08-03-r2 saved the public item summary returned when the order was prepared. When browser storage permits, Wayboro reduces a still-live record to the fields listed above when this notice or checkout next reads it, without changing its original expiry. A tab that is never reopened loses that older record at its existing 24-hour maximum or when the browser ends the tab session.

3. Security, payment, and map providers

Provider technologies are conditional. A browser may show a different exact name or duration as providers, payment methods, security challenges, and browser partitioning change. Wayboro reviews browser storage whenever a provider, domain, or payment method changes.

Technical references: Cloudflare cookies, Stripe cookie inventory, and Mapbox product privacy, and browser cookie-prefix rules. Provider notices govern their own processing; this Wayboro notice explains where the current application invokes them.

4. First-party response cache

The browser may keep versioned public JavaScript, CSS, fonts, and images in its ordinary HTTP response cache according to their response headers. The current application does not register a service worker and does not place responses in the browser Cache API. Public HTML and CDN behavior follows the response policy of the deployed Wayboro origin.

Every Wayboro API response now carries Cache-Control: private, no-store. This includes authentication, public tracking and checkout, driver/admin data, uploaded files, health, webhook, and error responses. The directive tells browsers and intermediary caches not to store that dynamic response; it does not erase a copy already saved elsewhere by a user, recipient, provider, or device tool. See the browser cache-control reference.

5. Private links, logs, and browser history

A delivery tracking URL is not a cookie, but its long random value is a bearer capability. Anyone holding an active copy may view the order data exposed by that page. Wayboro applies expiry, immediate revocation and replacement controls; removes the value from tracking API responses and stored notification logs; and masks it in application request logs. Do not post or forward the link outside the delivery participants.

Browser history, screenshots, clipboard tools, messaging applications, DNS/network infrastructure, Cloudflare, and other necessary delivery services may still process or retain the requested URL under their own technical and legal boundaries. The tracking page sends a no-referrer policy to reduce disclosure when following an external link.

Password-reset and privacy-request verification links place their private capability after the URL # fragment. The browser does not send that fragment in the initial HTTP request. The page copies the value into memory, removes it from the visible URL before the API call, and does not save it in Web Storage. The original email, browser history before removal, clipboard, screenshots, extensions, and device tools can still expose it, so do not forward either link or send it to support.

6. Choices and notice updates

Browser settings can inspect, delete, or block cookies, site storage, and cached files. The current Wayboro code has no advertising pixel, session replay, or optional Wayboro analytics SDK, and therefore has no Wayboro analytics preference to switch on or off. Stripe fraud controls and the driver map are functional provider technologies, not Wayboro advertising profiles.

Wayboro reviews cookie and storage use when the service or its providers change. Optional analytics, advertising, cross-site tracking, session replay, or another non-necessary technology remains disabled until this notice and any required consent or opt-out control are updated. The Privacy Notice explains broader personal-information handling.

7. Contact

Cookie, browser-storage, or private-link privacy questions: [email protected].