Effective 27 September 2026 · Version 2026-09-27

Cookie Policy

This policy explains the cookies and similar browser storage used by ZBANG LTD for the Zbang website. Essential state supports checkout, security, your privacy choices, and paid onboarding. Analytics and advertising technologies operate only after you choose the corresponding category.

Your choices

You can accept or reject analytics and advertising independently. Rejecting either category does not prevent you from ordering an audit. Essential technologies cannot be switched off through this control because they are used to provide a feature you request or to remember and enforce your privacy choice.

Essential browser state

Name or storage	Provider and type	Purpose and data	Duration
`zb_consent_v1`	Zbang · first-party cookie	Stores a signed record of your analytics and advertising choices. A matching pseudonymous server record enforces advertising withdrawal for pending Meta events. The cookie is HttpOnly, SameSite=Lax, and Secure in production.	The choice expires after 180 days; limited consent evidence may be retained with an order as described in the Privacy Notice
`zb_consent_subject_v1`	Zbang · first-party cookie	Stores a signed pseudonymous identifier used only to serialize and restore your privacy choices across browser tabs. It is HttpOnly, SameSite=Lax, and Secure in production.	Up to 180 days
`zb_checkout_attempt_v1`	Zbang · first-party cookie	Contains an opaque, necessary browser-attempt credential used to make repeated or interrupted checkout submissions converge on one order. It contains no contact, website, or card details. HttpOnly, SameSite=Lax, and Secure in production.	Up to 30 days; rotated after a completed or definitively ended checkout attempt
`zb_checkout_<order-id>`	Zbang · first-party cookie	Contains an opaque credential that binds the Stripe return to the browser and order that started checkout. It does not contain card details. HttpOnly, SameSite=Lax, and Secure in production.	Up to 30 days; removed after a successful checkout return
`zb_onboarding_<order-id>`	Zbang · first-party cookie	Contains an opaque credential used to authenticate a paid customer during onboarding. HttpOnly, SameSite=Lax, and Secure in production.	14 days
Onboarding draft	Zbang · first-party session storage	Preserves unfinished business-intake fields in the current browser tab after a validation or temporary save error.	Current browser session; removed after submission and ignored after 24 hours
Stripe Checkout storage	Stripe · third-party cookies or local storage on Stripe's hosted page	Payment, fraud prevention, security, and checkout operation. Stripe controls the exact names and durations under its Cookie Policy and Privacy Policy.	Set by Stripe for the period described in Stripe's policy

Legacy cookies beginning pp_ may be read temporarily to preserve a checkout or onboarding session started before the Zbang naming update. They are not used for advertising and may remain until the relevant expiry period ends or you clear site data.

Optional analytics and advertising

Technology	Category	Purpose	Typical storage
Google Analytics 4, including `_ga` and a property-specific `_ga_*` cookie where set	Analytics	Measures public visits, campaign sources and verified purchases. Purchase value excludes tax, which is reported separately with the service item. Google Signals is disabled.	Google-controlled; up to 2 years depending on configuration
Google Ads conversion measurement, including `_gcl_*` storage where set	Advertising	Attributes page-view, lead, and purchase events to advertising and helps measure campaign effectiveness. Purchase value excludes tax. Google advertising personalisation is disabled.	Google-controlled; commonly up to 90 days depending on configuration
Meta Pixel and Conversions API, including `_fbp` or `_fbc` where set	Advertising	Attributes site and purchase events to Meta advertising. Server purchase events include the total charged and a SHA-256 hash of your normalised work email for account matching. The hash is personal data, not anonymous data.	Meta-controlled; commonly up to 90 days depending on configuration
`zbang_tracking_delivered_v1`, `zbang_tracking_pending_leads_v1`, and `zbang_meta_server_delivered_v1` session storage	Analytics and advertising	Stores limited event and order identifiers, consent-epoch details, and per-provider acknowledgement while optional measurement is attempted, to retry interrupted sends and reduce duplicate browser and server events.	Current browser-tab session; pending entries are also removed when their consent choice expires, and each list is capped

Explicit Google events on public pages may include bounded campaign labels and the external referrer's origin, without its path, query or fragment. Explicit paid-onboarding purchase events use the public site root and an empty referrer. Optional purchase tracking does not include your intake answers or audit-account data.

An earlier release could place zbang_tracking_pending_leads_v1 in first-party local storage. On the next visit, Zbang first confirms the current saved choice, attempts to move only a matching unexpired retry into this tab's session storage, and deletes the local-storage copy after transfer or delivery. Invalid, expired, denied, or non-matching records are deleted without being sent. If tab storage and delivery are both temporarily unavailable, an eligible legacy copy remains for a later confirmed attempt, but no later than its consent expiry.

Optional tools and related event transmission remain disabled until a corresponding choice is recorded. A change applies to future processing. When you withdraw a category, Zbang disables its loaded tags, refreshes the page, and attempts to remove the known first-party measurement cookies for that category. Provider storage created after an earlier choice may still remain until it expires or you remove it using browser controls.

Managing browser storage

Most browsers let you inspect, block, or delete cookies and site storage. Blocking essential state may stop checkout return verification or paid onboarding from working. Browser settings do not replace the Cookie settings control for telling Zbang whether optional tools may operate.

More information