Every cookie we set, named, with what each one holds.

_zinx_vid

A random identifier for the browser, so the same visitor stays in the same test group. Not derived from anything personal. Lasts one year.

_zinx_grp

Which group of which experiment this visitor is in. Read at checkout so an order can be credited to the right group. Lasts one year.

_zinx_try_…

Written only by theme and template tests, one per experiment. It records that the redirect for this test has already been attempted, so a visitor can never be sent round a loop. Lasts 30 minutes.

_zinx_on_theme

Written only by a theme test, recording that we were the ones who moved this visitor onto a test theme. It is what lets us put them back on the live theme once the test stops. Lasts 7 days.

All four are first-party, set with SameSite=Lax, and marked Secure on any store served over HTTPS. None is readable by another site, and none is shared with anyone.

Local storage, alongside them

_zinx_cfg

A copy of the store's experiment configuration, so a returning visitor applies their variant with no network wait. It contains no information about the visitor.

_zinx_idle

Set while the store is running no tests, holding the time that stops being known. It lets the page skip hiding itself while there is nothing to change. It contains no information about the visitor.

_zinx_sent_…

One per redirect test, marking that this browser's visit to that test has already been counted. It stops one visitor being recorded twice.

_zinx_bar

Where a merchant previewing their own store put the preview toolbar, and whether it is collapsed. Never written for a shopper.

Session storage, cleared when the tab closes

_zinx_seen

Which experiments this tab has already reported a visit for, so a reload is not a second visitor.

_zinx_preview / _zinx_theme_…

Marks that this tab is a merchant previewing a variant rather than a shopper being tested. A preview is never counted and never writes the group cookie.

_zinx_pt

The signed preview links this tab has opened, so a merchant's preview keeps working as they click around. Never written for a shopper.

_zinx_ping

Written by our Shopify web pixel for a visitor in no test: marks that this session has already sent its one signal that the pixel is working.

_zinx_cart

The cart token last seen in this tab, used to match an order back to the visit that produced it.

_zinx_out

Written only by price and offer tests: the tests this tab sits out because the visitor's group could not be confirmed on their cart. They then see and pay the normal price.

_zinx_mp3:…

Written only by price tests, for a shopper outside the store's own currency: a tested product's price in their market, read from the store, so it is not fetched again on every page. It contains no information about the visitor.

Before writing anything, our script asks Shopify’s Customer Privacy API whether analytics processing is allowed for this visitor. Shopify’s answer already accounts for where the shopper is, so there is nothing for us to guess about geography.

Consent given

The cookies above are written and the test runs.

Consent refused

Nothing is written and nothing is measured. Anything stored on an earlier visit is deleted from the device. Withdrawing consent should stop us holding data, not merely stop us adding to it.

No consent banner on the store

Where there is no consent framework to ask, there is no consent to respect, so the test runs. A merchant can switch an experiment to strict, which makes silence count as a refusal.

Nothing is stored on your device until you choose Accept in the banner. Google Analytics is loaded with consent set to denied, which means it sets no cookie and receives no identifier — only an anonymous count that you visited. Reject is one click too, and then it is switched off entirely. PostHog does not load at all until you accept.

Google Analytics

On the marketing pages only: this one, the home page, how it works and the writing. It records the pages you visit, without the query string, and roughly where in the world you are. It sets its own _ga cookies.

PostHog

In the dashboard and on the sign-in page. It records what you use (pages, clicks, tests started), a session replay of the screen as you see it and any error the page hits. The replay never records the storefront password or links that carry a token. It stores its id in local storage (ph_…), not a cookie.

zinx_consent_v1

Your answer to the banner, in local storage, so we ask once.

Zinx Chat

The support bubble in the corner, ours rather than a third party's. It sets no cookies: one id in local storage (zinx.visitor), so a reply is still waiting after a reload, and it is told which site it is on but never which page or what is in the address. It loads whether or not you accept analytics, because it is how you reach a person rather than a way of measuring you.

Neither loads on invitation links, the store-connection page or staff pages, and neither is ever sent the query string of an address, where a token can sit.

Change your mind with Cookie settings in the site footer, or in your account menu inside the app. Rejecting stops both at once.

Once you sign in, a session cookie keeps you signed in, and a small preference is stored locally for your theme and display scale.

There is no advertising pixel and no advertising tracker on this site. We do not sell or share what either tool collects, and we do not use it to build a profile of you across other sites.

• Refuse analytics in the consent banner on the store you are visiting. That is the cleanest route, and it removes anything already stored.
• Clear cookies for the store in your browser. The next visit starts fresh, though the same group may be re-derived, because assignment is deterministic by design.
• Block cookies for the site entirely. Zinx Signal fails open, so the page still works and you simply see the store’s original version.

The privacy policy lists everything recorded, not just what is stored on a device. How it works explains why a sticky group is necessary in the first place.

Questions: [email protected].