Back to sale

Cookie and Browser Storage Policy

Last updated: 17 November 2026

This policy covers cookies, browser storage and website measurements used by Matrix. Read it with the Privacy Policy. Contact contact@matrix.app with questions.

Necessary storage and security

The username reservation website saves your theme preference in local browser storage. Email codes, CAPTCHA tokens and temporary claim credentials stay in the current reservation flow's memory. They are not saved as theme or analytics preferences. Reloading can discard an unfinished flow.

Cloudflare hosts and protects the websites. Cloudflare Turnstile, or Google reCAPTCHA Enterprise when Turnstile is unavailable, checks for automated requests. These services can use security tokens and process technical connection or browser information. Their processing is distinct from optional PostHog analytics. See Cloudflare's Privacy Policy and Google's Privacy Policy.

If you use the separate private-sale portal, these first-party cookies support wallet authentication:

CookiePurposeBrowser lifetime
mtx_challengeConnects a sign-in challenge to its verification request.Up to 5 minutes.
mtx_sessionKeeps an authenticated wallet session.Up to 12 hours.

These authentication cookies cannot be read by page JavaScript. Production cookies use secure transport and a strict same-site rule. Their expiry is not a promise that all associated server records are deleted at the same time.

The private-sale portal also uses the mtx:last-purchase local-storage entry for purchase recovery references, such as the buyer, chain, contract, authorization reference and a transaction hash when one is available. Wallet connectors can maintain their own connection storage. A wallet connection does not disclose your private keys to Matrix.

Website measurements

Cloudflare Web Analytics uses the existing website beacon to measure website use and performance. Cloudflare hosting and security requests can still occur when you decline optional PostHog analytics.

PostHog is optional. After you accept it, we use a pseudonymous browser identifier and approved, fixed page and action labels to count visits, clicks and reservation-flow steps by consenting browsers. These counts are not a count of all visitors or unique people. We do not use these events for third-party behavioral advertising.

We use PostHog’s US region. The project discards client IP addresses from stored events, and our events disable location enrichment. Each optional event is sent directly from your browser to PostHog. It receives your IP address and standard browser information with that request, such as the browser type, website origin and language headers. PostHog processes this information under its project settings and privacy terms. This policy does not promise immediate IP deletion or a particular provider retention period.

The production website stores its analytics choice in the local-storage entry matrix:website-analytics:production. Staging uses matrix:website-analytics:staging. Each entry holds the choice and, only when analytics is accepted and configured, a random browser identifier. There is no separate first-party analytics cookie. Each website origin keeps its own entry and identifier. We do not share this identity across subdomains.

The choice remains in local storage until you clear it. Rejecting analytics or a supported browser privacy signal removes the local identifier where the browser allows the change. If storage cannot be updated or cleared, the page reports the problem and keeps optional analytics disabled for that page. The old stored choice can remain, so you may need to clear browser storage before opening a later page. Clearing that storage removes the local choice and identifier, but does not delete measurements already received by the analytics provider.

PostHog does not start before consent. You can decline it without losing access to the reservation form. You can change your choice through the website's cookie controls. A successful change to turn it off stops future optional events. It does not automatically erase records already received by the provider.

We do not enable session replay, automatic interaction capture or form capture. We do not send raw URLs, query strings, referrers, form values, emails, usernames, verification or CAPTCHA codes, claim credentials, wallet addresses or sale access codes in analytics events. PostHog website measurement does not cover the private-sale portal. See PostHog's Privacy Policy.

Private-sale analytics

The private-sale portal has a separate, optional analytics choice. Your choice is stored in your browser under matrix:sale-analytics:production on production or matrix:sale-analytics:staging on staging. A random browser identifier is stored only when you allow analytics and it is available. The choice does not affect wallet sign-in, face verification or purchases.

Optional sale analytics measures visits, checkout steps and limited request errors and timings as described in the Privacy Policy. It does not use session replay or collect form contents, invitation codes, wallet addresses or face data. You can turn it off through the sale page's analytics controls. Changing your choice stops future events but does not delete events already received by PostHog.

Managing storage

You can remove cookies and local storage in your browser. This can reset your preferences, sign you out of the private-sale portal and remove local purchase recovery references. Reloading the reservation page can also end its in-memory flow. Disconnecting a wallet alone does not necessarily clear every cookie, provider record or browser preference.

Clearing local storage does not cancel a submitted transaction, reverse a purchase or delete a server-side reservation. Contact us about server records or privacy requests. We may update this policy when the storage or providers change.