Cookies and local storage
Last updated 2026-10-24
zephyrmedia uses no analytics, tracking or advertising cookies. The website stores only what it needs to work, what you ask it to remember, and one anonymous visit counter with no personal data in it: keeping you signed in, the theme you chose, recovering from a failed page load after an update, making payments safe, and counting visits to a few of our pages. 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 so you can send a request or book a call with your confirmed email address, see your requests in the client portal, 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 (confirming your email on the request form or the call booking page, client portal, order pages, or when you approve connecting an AI assistant).
zm-theme- Provider
- zephyrmedia
- Purpose
- Remembers the light or dark theme you picked with the theme button, so pages open in that theme. The value is only “light” or “dark”. Until you press the button, the site follows your device setting and stores nothing.
- Type
- Local storage (in your browser, never sent to us)
- Duration
- Until you clear your browser’s site data.
- Where it is set
- Any page, only after you press the theme button.
zm-request-draft,zm-call-draft- Provider
- zephyrmedia
- Purpose
- Keeps what you typed in the request form or the call booking form while you confirm your email address, so you do not have to type it again. It is deleted as soon as the form is filled back in.
- Type
- Session storage (in your browser, never sent to us)
- Duration
- Until the form is filled back in after you confirm your email, or until you close the tab.
- Where it is set
- The request form and the call booking page, only when you confirm your email before sending.
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.
zm-visitor- Provider
- zephyrmedia
- Purpose
- A random number generated in your browser, used only to count visits to the homepage, the How it works page and the packs page, and how many requests and pack orders follow, so the studio can see which page explains the offer well. It contains no personal data and is never linked to your requests, sign-in or payments. A session-storage flag stops the same tab being counted twice in one visit.
- Type
- Local storage and session storage (in your browser, not a cookie)
- Duration
- The number: until you clear your browser’s site data. The flag: until you close the tab.
- Where it is set
- The homepage (/), How it works (/how-it-works) and packs (/packs) pages only; each browser tab session counts at most once.
__stripe_mid,__stripe_sidand 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, billing page and invoice 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 order page (/order), where Stripe’s script loads for the payment, and on Stripe’s own pages: the billing page that “Manage billing” opens and the invoice payment page. Other pages, including the client portal, do not load Stripe’s script.
Google sign-in cookies
- Provider
- 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.
3. Why we do not ask for consent
Everything listed above is strictly necessary to provide a service you ask for: signing in, showing the theme you picked, loading the site correctly and paying securely. The theme choice is stored only when you press the theme button, to do what you asked. EU, Hungarian and UK law allow such storage without consent (Article 5(3) of the ePrivacy Directive 2002/58/EC, § 155(4) of the Hungarian Electronic Communications Act, Act C of 2003, and regulation 6(4) of the UK Privacy and Electronic Communications Regulations 2003). Any personal data involved is processed as described in our Privacy policy.
Before we add any other cookie or storage that is not strictly necessary, we will ask for your consent first, and you will be able to refuse it as easily as accept it. The one storage outside “strictly necessary” today is zm-visitor: an anonymous visit counter for a few pages with no personal data in it, which is why it is listed here and not asked about.
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 or deleting the theme setting only means the site follows your device’s light or dark setting again;
- blocking session storage only means the site cannot recover automatically from a failed page load; reload the page yourself;
- deleting
zm-visitoronly means the site creates a new random number the next time you open a counted page; nothing else changes; - 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.