Cookie Policy
Last updated: 2026-05-14
1. Our position on cookies
DeliveryHub uses only strictly-necessary cookies — the cookies required to keep you signed in and to operate the Services securely. Under Regulation 6(4) of the Privacy and Electronic Communications Regulations 2003 (PECR), strictly-necessary cookies are exempt from the prior-consent requirement. We therefore do not display a cookie consent banner.
We do not use cookies for advertising, marketing, or third-party analytics, and we do not permit third parties to set cookies through the Services for those purposes.
2. The cookies we set
The following cookies are set by us or by the authentication library we use (Supabase Auth via @supabase/ssr) on every host of the Services (deliveryhubapp.com, app.deliveryhubapp.com, and admin.deliveryhubapp.com).
| Name | Provider | Purpose | Duration |
|---|---|---|---|
sb-yraydourqwdpvpmcjygx-auth-token | DeliveryHub (Supabase Auth) | Holds your authenticated session: the short-lived access token and the longer-lived refresh token. Without it the Services cannot identify you and you cannot stay signed in. When the session payload exceeds the per-cookie size limit, this cookie is split into numbered chunks (…-auth-token.0, .1, …); they form a single logical cookie. | Session lifetime; refresh token rotates and is renewed by the browser on each visit. Cleared on sign-out. |
sb-yraydourqwdpvpmcjygx-auth-token-code-verifier | DeliveryHub (Supabase Auth) | Stores the PKCE code verifier during the magic-link or password-reset sign-in flow so the browser can complete the exchange when you click the link in your email. | Transient — typically a few minutes; deleted as soon as the sign-in flow completes (or expires). |
The string yraydourqwdpvpmcjygx is our Supabase project reference; it appears in the cookie name because the auth library namespaces session cookies by project.
3. How to manage cookies
You can delete the cookies set by the Services at any time through your browser’s site-data settings. Most browsers also allow you to block cookies for a specific site. Note: if you delete or block the cookies listed above, you will be signed out and will not be able to use the Services until you sign in again.
Browser vendor support pages explain how to view and remove cookies: Chrome, Firefox, Safari, Edge.
4. Third-party cookies
We do not set advertising, analytics, or social-media cookies. We do not embed advertising pixels, social buttons, or third-party analytics scripts on the marketing site or inside the Services. No third party sets cookies through our site for those purposes.
5. Do Not Track
Because we do not engage in the kind of cross-site tracking that Do-Not-Track signals are designed to limit, DNT signals have no effect on our processing.
6. Changes to this policy
We may update this Cookie Policy from time to time. The updated version will be indicated by the “Last updated” date at the top of this page. Material changes will be notified to operators by email at least 14 days before they take effect.
7. Contact
Questions about this Cookie Policy? Email contact@deliveryhubapp.com.
8. Our commitment if this ever changes
If we ever introduce non-essential cookies (for example product analytics, marketing pixels, or third-party embeds), we will deploy an ICO-compliant consent banner offering granular reject and accept controls at equal friction, and we will update this page to list each new cookie, before any non-essential cookie is set on your device.