Privacy

This is a static site. No accounts, no comments, no shopping cart. Below is a plain account of what data exists — including the one place where your browser talks to somebody else's server.

What we don't collect

No signup, no login, no forms. There are no user accounts and no contact form on this site.
Nothing you type into a tool. Every calculation and filter on the tools pages runs in your browser; the block heights, amounts and keywords you enter never leave your device and are never written to a server.
No ad networks, no cross-site tracking, no personalised advertising.
No selling, renting or trading of user data. There is no user data to sell.

Cookies and local storage

This site sets no cookies that identify you. Styles, scripts and images all load from our own domain — no third-party fonts, analytics scripts or social widgets.

One exception, stated plainly: three of the eight tools (market heatmap, funding and leverage, depth and impact) fetch public market data endpoints directly from your browser. See the next section.

The three tools that call external endpoints

Those pages show live market data, which has to come from an exchange's public endpoint. The request happens in your browser and does not pass through our server — which has a consequence you're entitled to know about:

The endpoint operator can see your IP address, the time of the request and your browser's user agent. That is true of any network request.
What's requested are public market data endpoints: 24-hour price changes, order books, funding rates, open interest. No account, no credentials, and nothing about you beyond the connection-level facts above.
Domains involved: data-api.binance.vision (fallback api.binance.com) and the public data endpoints at www.okx.com.
We do not store, forward or analyse any of it, and we do not know which pages you opened or which pairs you looked up.
These requests only happen on those three pages. Every other page — articles, the other five tools, the policy pages — makes no external requests at all and reads fine offline.

If you'd rather not make those requests, simply don't open those three pages. Blocking them with a browser extension won't affect anything else on the site; those pages will show a clear failure message rather than filling in stale data.

Server logs

Like any website, the server hosting this one may record basic access logs when it receives a request: the time, the path requested, the HTTP status code, the referring page, the browser user agent, and a processed IP address. These are used for troubleshooting and spotting abnormal traffic. We don't use them to build profiles of individuals and we don't share them, unless legally compelled.

When you email us

When you write to [email protected] we see your address and the contents of your message. That's used to answer your enquiry and follow up if needed. You are never added to a mailing list, and nothing is used for marketing. You can ask us to delete the correspondence at any time and we will, once we've confirmed the request.

Please do not email us seed phrases, private keys, passwords, verification codes, identity documents or screenshots of an exchange account. We don't need any of it and will never ask for it.

External links

We refer to exchange documentation, regulators' sites and block explorers when explaining where data comes from. Once you follow a link off this site, this policy stops applying and the destination's own policies take over. That includes the coded sign-up link at the end of the sign-up guide: there is no redirect page in between, we do not record who clicks it, and what happens after the click is entirely up to the destination.

Screenshots on this site

The interface screenshots in our articles come from pages that are open to any visitor, captured while logged out. They contain no balances, positions, identity documents or other personal information. Image files are served from our own domain, not a third-party host.

Minors

This site is written for adults. It is not designed for minors and does not knowingly collect information from them.

Changes to this notice

If the technical setup changes — analytics introduced, hosting moved, a tool added that calls a new endpoint — this page is updated and re-dated. Significant changes are flagged on the home page.

This version effective 26 August 2026. Questions about it go to [email protected].