Scope
This notice covers the public website at 0xmixer.com. The site does not provide an account form, login, KYC form, checkout, or support form. It does use website analytics and external infrastructure, so a statement that the public site processes no data at all would be inaccurate.
The published no-retained-mapping posture describes the mixer flow. It does not mean that GA4, hosting, CDN, or network providers receive no technical request data.
GA4 and Web Vitals
0xMixer uses Google Analytics 4 with measurement ID G-KXD74PZVS7. GA4 can record page views and technical context such as page URL, referrer availability, browser, device, screen size, approximate location derived by the provider, and interaction timestamps.
The site sends these first-party event names to GA4:
- open_console when a visitor activates a mixer CTA.
- handoff_view when a visitor starts the internal handoff.
- web_vital for performance metrics such as LCP, CLS, INP, FCP, and TTFB, together with rating and navigation type.
GA4 may set analytics identifiers such as _ga and _ga_*, depending on browser controls and provider behavior. Requests to Google necessarily expose network metadata to Google while the request is delivered. This site does not install Yandex Metrika.
Infrastructure data
Hosting, reverse-proxy, CDN, DNS, and security providers may process IP address, requested URL, request time, user agent, response status, and similar network metadata to deliver and protect the site. 0xMixer does not publish a verified fixed retention period for those provider records, so this notice does not invent one.
Static files such as fonts, icons, the manifest, and application bundles are served as part of normal website delivery. The site has no public form that asks you to submit a name, email address, wallet seed, private key, or identity document.
External handoff
Choosing a mixer CTA first opens the internal /run page and then redirects to the external mixing core configured for this deployment, currently xuanxi.app. The same handoff is used for USDT and USDC; asset and network selection happens on the external service. The handoff requests a no-referrer policy, but the destination and its network providers still receive the technical metadata needed to establish a connection, including the destination request and source IP.
The external destination is outside this privacy notice. Its interface, processing, provider logs, cookies, and terms are governed by that destination's own published information. Review the destination before submitting a wallet address or funds.
Your choices
- Block or clear analytics cookies with your browser controls.
- Use content-blocking or script controls if you do not want GA4 to load.
- Leave the site without opening the external handoff.
- Review the external destination's own notice before continuing.
This notice may change when analytics, infrastructure, or the handoff flow changes. The current version was last updated on July 15, 2026.