Privacy Policy

There are no accounts, no wallet connections and no sign-ups. We do not ask for your name, your email or your address, and we have no way to link a scan to a person.

We do not run advertising or third-party analytics, and we do not sell or share data with anyone for marketing.

One cookie: rugscan_dil, which remembers the interface language you chose. It contains a language code such as "en" and nothing else. It lasts one year and you can delete it at any time.

That is the only cookie we set. We do not use tracking pixels, fingerprinting or session recording.

RugScan keeps an archive of what it has scanned: token addresses, market state over time, deployer wallets, the addresses those wallets sent funds to, and bundled-buy patterns.

All of that is public blockchain data. It describes tokens and wallets, not the people who looked them up. A scan you run is not recorded against you, because there is no "you" in our database.

The archive exists so the tool can say when a token died and recognise when the same operator launches again — both of which require history that a single query cannot produce.

Our host records standard request logs, which include IP address, timestamp, requested path and user agent. These are generated by the hosting platform for security and operational purposes and are retained under its policy, not ours.

We do not query these logs to build profiles and we do not join them to scan data.

Hosting and request logs: Vercel. Archive database: Supabase. Fonts are served from Google Fonts at page load.

Data sources queried by our server, never by your browser: GeckoTerminal, DEX Screener, GoPlus Security, Etherscan and Helius. Because these requests originate from our server, those services see us, not you.

Token images shown in the radar are loaded by your browser from the CDN that hosts them, which means that CDN can see the request. That is the only third party your browser contacts directly other than the font provider.

All API keys used by the service are held server-side and never reach the browser. No credential of ours is exposed in the page source or in any client request.

Because we do not hold personal data about you, there is normally nothing to access, correct or erase. If you believe we hold something about you, contact us and we will look.

If you are the operator of a wallet that appears in the archive: that record describes public on-chain activity performed by an address, which is not private information, and we do not attempt to identify the person behind it.

If what we collect changes, this page changes with it, and the date above is updated. We do not make this policy weaker without saying so plainly here.