Visitor analytics and privacy
What we measure
Production uses self-hosted Umami for page visits, referring websites, campaign tags, optional referral codes, country, device/browser type and actions such as sharing and purchase steps. Cloudflare Web Analytics also supplies basic public-page performance reports.
We do not send wallet addresses, transaction hashes, balances, purchase amounts, signatures, form contents or private draft identifiers to Umami. Public presale links are measured individually; creator and studio routes are reduced to generic page names. Referrer paths and arbitrary query parameters are removed. Wallet callback pages, local development and staging are excluded.
Your choices
Umami collection respects Do Not Track and Global Privacy Control. You can turn off MemeFactory product analytics in this browser or turn it back on. The choice is stored locally. Campaign tags and referring website are kept in tab session storage with a 30-minute inactivity limit so subsequent actions retain their source.
No recordings or wallet profiles
No analytics cookies, session replay, advertising identifiers or wallet identity links are enabled. Umami uses a daily rotating anonymous identifier derived from request information; raw IP addresses are not stored in its analytics tables. Our separate necessary wallet authentication cookies are unchanged. The Umami dashboard and database are private.
Fonts
Pages load the DM Sans and Manrope typefaces from Google Fonts, so your browser requests them from Google's font servers. No MemeFactory data is sent with those requests.
What the counts mean
Purchase confirmations are reported by the browser only after a successful transaction receipt. These reports are approximate product metrics, not an authoritative financial ledger. Blockers, privacy choices, shared networks and interrupted visits can affect totals. Referral codes measure attribution only and do not create rewards or change fees. New analytics starts at activation; earlier Cloudflare history is not imported.