Privacy

The site sets no cookies, runs no analytics, embeds no pixels, and loads no fonts, scripts or widgets from anyone else. The content security policy in the deployment pins scripts to this origin, so a third-party script cannot be added by accident on a page that can sign a transaction. Fonts are served from this domain.

Because there are no accounts, there is no profile to build. We do not know who you are and have no mechanism to find out.

When a tool needs to know something about an address, your browser asks the data source itself. The request does not pass through our server, is not logged by us, and is not cached by us. That is a deliberate design choice, not a side effect: routing those reads through a server would hand it a record of every address anyone looked at.

Being plain about the limit of that promise: it means we do not see it. The service that answers does. Any web request reveals your IP address to whoever receives it, along with whatever you asked for. Those companies have their own policies, their own logs and their own retention, and we have no control over any of it. If that matters for a particular lookup, a VPN or Tor changes what they see about you; nothing this site does can.

Tools that need nothing but your own browser — converters, encoders, decoders, calculators, key and hash utilities — make no network request at all, and keep working with the network switched off.

Three routes proxy data, and all three carry global datasets only: protocol and chain totals, stablecoin figures, prices and yield pool lists from DefiLlama. Those payloads run to megabytes and several seconds at the source, so they are fetched once, trimmed and cached for everyone. No address is part of those requests, so there is nothing personal in them to log. The proxy is an allowlist of specific upstream hosts, never a general pass-through.

Our host records ordinary web-server request data for the pages and those three routes — IP address, timestamp, requested path, user agent — as any web server does, in order to serve and protect the site. We add nothing to it and do not use it to build a profile. The site is hosted by Vercel, whose own policy governs those logs and their retention.

Alert rules — the address, the condition and the threshold — are stored in your browser’s IndexedDB and are read only by the service worker running on your own machine. They are never uploaded. Wallet connection state is kept in local storage by the wallet library. Clearing site data in your browser removes all of it, and none of it exists anywhere else.

If you turn on browser alerts, the server stores exactly three values: the opaque endpoint URL your browser’s push service issued, and the two keys needed to encrypt to it. No address, no rule, no threshold, no email, no name. Anything else sent to that route is dropped rather than stored.

The wakeup we send carries no payload at all — it is a signal that says only “now would be a good time to check”. The service worker in your browser then does the checking, because the server does not know what you are watching and is not meant to. Whoever holds that table learns that some browser wants wakeups, and nothing more.

Turning alerts off in the browser deletes the stored endpoint. The push service that issued the endpoint — Google, Mozilla or Apple, depending on your browser — necessarily sees that a wakeup was sent to it.

There is no account to delete and no profile to export. What can be erased is the push endpoint, by disabling alerts in your browser, and your local data, by clearing site data. For anything else, including data-protection requests, contact hello@ihategas.xyz.

This page may change as tools are added or data sources swapped. The effective date above says when this version was published.