What cookies are
A cookie is a small text file a website stores in your browser so it can recognise you between page loads — for example to keep you signed in or remember a setting. Cookies set by the site you are visiting are "first-party"; cookies set by other companies through embedded content are "third-party". Laws such as the EU ePrivacy Directive and the California CCPA require us to tell you which cookies we use and, for non-essential ones, ask permission.
Cookies we set
| Cookie | Purpose | Type | Expires |
|---|---|---|---|
| PHPSESSID | Identifies your session so that forms are protected against cross-site abuse, your My Account sign-in and admin sign-in persist, and status messages can be shown after a redirect. Contains a random identifier only. | Strictly necessary, first-party | When you close the browser |
| zw_cur | Remembers the display currency you selected (USD, AUD, CAD, GBP or EUR) so prices stay in that currency as you browse. | Strictly necessary (preference), first-party | 12 months |
Neither cookie contains personal information, and neither is used to track you on other websites.
Third-party content
- Payment fields. On product pages the card entry fields are served by our payment gateway from its own domain. The gateway may set its own cookies or use local storage to secure the card form and detect fraud; this is covered by the gateway's privacy policy and happens only on pages with a payment form.
- Fonts. Typefaces are loaded from Google Fonts. Google receives your IP address and browser details when the font files are requested; Google states that it does not use the Fonts API to set cookies or track users.
- Smooth-scrolling script. A small open-source scrolling library is loaded from a public CDN (unpkg). It sets no cookies.
What we do not use
No Google Analytics or similar analytics, no advertising pixels (Meta, Google Ads, Microsoft Ads), no remarketing tags, no session-recording tools, no social-media share buttons that load third-party scripts, no A/B-testing tools. Traffic figures come from anonymised server logs kept for 30 days.
Controlling cookies
Because both cookies are necessary for the site to function, there is no consent toggle to switch them off; you can block or delete them in your browser settings (Chrome: Settings → Privacy and security → Cookies; Safari: Preferences → Privacy; Firefox: Settings → Privacy & Security). Blocking PHPSESSID will prevent forms from submitting and sign-in from working; blocking zw_cur simply resets the display currency to USD on each visit. We honour the Global Privacy Control signal, although since we set no tracking cookies there is nothing for it to switch off.
Changes
If we ever add a non-essential cookie — for example analytics — we will update this page, add a consent control before it is set, and note the change here. Questions: FinTech@zedwebtech.com.