privacy

// what we collect

• > anonymous client id. a random uuid your browser generates on first visit and stores locally. lets us count returning visitors without knowing who they are. clear your site data and the id is gone.
• > coarse location. country, region, and city, derived from your ip at the network edge. used for traffic analytics. we never store your ip address.
• > scan inputs. the token mints you scan, with timestamps. these are public on-chain addresses, not personal data.
• > platform analytics. request counts, page latency, error rates. standard hosting telemetry.
• > google analytics 4. anonymous pageviews, scan submissions, and verdict events. only fires if you accept on the consent banner. rejected = no cookies, no events. when accepted, ga4 sets first-party cookies (_ga, _ga_*) so returning visits aren't double-counted, and the data is sent to google. used for traffic shape, not ad targeting. no google signals, no audience export.

// what we don't collect

• >your ip address (on our infra). used briefly for rate limiting, never stored. ga4 receives it at google's edge before anonymization, like every site that uses ga.
• > your wallet address. we never ask you to connect.
• > your email, name, phone number, or any contact info, unless you mail us directly. in which case we just have your email until we reply.
• >ad retargeting pixels. we don't sell or share scan data with ad networks.

// why we collect this

the legal basis is legitimate interest in keeping the service usable: rate limits to prevent abuse, traffic shape to anticipate load, and unique-user counts to tell whether a tweet just sent a wave of visitors. no decisions about you are made from this data.

// your controls

• > clear site data in your browser → fresh client id, treated as a new visitor.
• > use private browsing → client id lives only for the session.
• > change your mind on analytics → clear site data, the consent banner shows again on next visit.
• > email hello@doomer.wtf to ask what (if anything) we have on your client id, or to request deletion.

// changes

if this policy changes in a way that meaningfully affects what we collect, we'll bump the date at the top and call it out on the homepage. no silent updates.