Privacy

Last updated: 12 August 2026

This is a short, accurate description of what VetMyToken does with data. You do not need an account to use it, and there is nothing to log in to.

What we store

• Scan results. When you submit a chain and a contract address, the address and the result of the scan are stored in a SQLite database on our server and published as a public result page. Treat everything you type into the scan box as public.
• Server logs. The Caddy web server in front of the site records one line per request: the time, the path you asked for, the status code, your browser's user-agent string, and the page that linked you here if there was one. Your IP address is shortened before the line is written to disk. The last block of an IPv4 address and the last three-quarters of an IPv6 address are replaced with zeros at the moment of writing, so the file never contains a whole address and there is no window in which one could be recovered from it. Your Cookie and Authorization headers are dropped before the line is written as well. These files rotate and are kept for at most fourteen days, or less if traffic rotates them out sooner. The application's own request log behind the proxy records the local proxy address, not yours.
• Rate limiting. Your IP address is counted in memory for a short rolling window so one visitor cannot exhaust the scanner. It is not written to the database and it is not attached to your scans.
• Anything you type into a form. Contact messages and community notes are stored so they can be read, answered and moderated. A community note is published on the token page you post it to.

Cookies

One cookie, named watch, holds the list of scans you added to your watchlist. It is set by this site only, it holds scan identifiers and nothing else, and clearing it empties your watchlist. Signing in to the admin area sets a second cookie; ordinary visitors never receive it.

What we do not do

There is no third-party analytics script, no advertising network, no tracking pixel and no cross-site profiling on this service. We do not sell or share personal data. We do not ask for your name, email address or payment details in order to run a scan.

We do count visitors, and we do it from the shortened server logs described above and nothing else. That means the count is approximate on purpose: two people behind the same network can look like one visitor, and one person on two devices can look like two. Nothing about the visit is sent anywhere off this server, and we cannot tell who you are or where you are from it — we do not hold a location database and the addresses are already shortened.

Data that leaves our server

To complete a scan we send the chain and the contract address — not your IP address — to public blockchain RPC endpoints and to the external market and token-security feeds listed on the data disclosures page. Token pages may embed a price chart served by Dexscreener; that embed loads from their servers, so they will see the request your browser makes for it.

Questions and removal requests

Use the contact form. Scan pages describe public on-chain contracts rather than people, so we will not normally remove one, but we will read and answer the request.