← Legal
zephyrmedia · legal

Cookies and local storage

Last updated 2026-10-08

zephyrmedia uses no analytics, tracking or advertising cookies. The website stores only what it needs to work: keeping you signed in, recovering from a failed page load after an update, and making payments safe. That is why there is no cookie banner. This page lists every item and how to control it.

1. What cookies and browser storage are

Cookies are small text files a website saves in your browser. Local storage and session storage are similar browser features that keep small pieces of data for a website; session storage is cleared when you close the tab. The rules below apply to all of them.

2. What we use

  • sb-pzpdpnonljcrymreipcl-auth-token

    Provider
    zephyrmedia (our sign-in system, run on our hosting provider’s managed backend)
    Purpose
    Keeps you signed in to the client portal so you can see your requests, pay for approved requests and manage billing.
    Type
    Local storage (in your browser, not sent automatically with every request)
    Duration
    Until you sign out or the session expires. The token renews itself while you keep using the portal.
    Where it is set
    Only after you sign in (client portal, order pages, or when you approve connecting an AI assistant).
  • zm-chunk-reload

    Provider
    zephyrmedia
    Purpose
    A technical flag, value “1”. If a page file fails to load right after we publish an update, the site reloads once to fetch the new files; the flag stops it reloading in a loop.
    Type
    Session storage
    Duration
    About 10 seconds; it is also removed when you close the tab.
    Where it is set
    Any page, only when a page file fails to load.
  • __stripe_mid, __stripe_sid and other Stripe cookies

    Provider
    Stripe
    Purpose
    Fraud prevention and secure payment processing. Stripe’s script and its checkout and billing pages use them to recognise the device and detect fraudulent payments.
    Type
    Cookies. __stripe_mid and __stripe_sid are set on our domain by Stripe’s script; Stripe’s checkout frame and billing page may set further cookies on Stripe’s own domains.
    Duration
    __stripe_mid: about 1 year. __stripe_sid: about 30 minutes. Others: as set out in Stripe’s cookie policy.
    Where it is set
    Only on the payment pages (/order, /order/confirmation), the client portal (/portal) and Stripe’s billing page that “Manage billing” opens.
  • Google sign-in cookies

    Provider
    Google
    Purpose
    Signing you in with your Google account and keeping that sign-in secure.
    Type
    Cookies on Google’s own domains (not on zephyrmedia.online).
    Duration
    As set out in Google’s cookie policy.
    Where it is set
    Only if you choose “Sign in with Google”.

Stripe describes its cookies in its cookie policy and lets you review its settings at stripe.com/cookie-settings. Google describes its cookies in its cookie policy.

We do not load analytics, advertising pixels, embedded YouTube videos, social media plugins or externally hosted fonts.

4. How to control and delete them

You can see, block and delete cookies and site data in your browser settings, usually under “Privacy” or “Site data”. Browser help pages explain how: Chrome, Firefox, Safari, Edge. Signing out of the portal removes the sign-in token.

If you block or delete them:

  • blocking local storage means you cannot stay signed in to the client portal; deleting the sign-in token signs you out;
  • blocking session storage only means the site cannot recover automatically from a failed page load; reload the page yourself;
  • blocking Stripe’s cookies may stop the payment form or billing page from working, or make Stripe decline or ask for extra checks on a payment;
  • blocking Google’s cookies stops “Sign in with Google”; you can sign in by email link instead.

Browsing the public pages and sending a request work without any of them.

5. Questions

For questions about cookies or this page, use this contact: contact@zephyrmedia.online.