What the page code does not collect
None of these are present
- No analytics. No measurement service of any kind, and no placeholder tag left in the markup.
- No ad scripts, no pixels, no third-party trackers.
- No cookies. This site writes none, which is why there is no consent banner.
- No local storage. No
localStorage, nosessionStorage, no IndexedDB. - No accounts, no login, no comments, no signup form. There is nothing here that asks you to submit anything.
- No external fonts or scripts. Pages load one stylesheet and one script, both from this site, and request nothing from any third-party domain.
Which means: the page code has no form, account, analytics or local-storage collection path. It does not prove that the hosting server or content delivery network never processes or records connection data; that layer is addressed below.
How the tools handle what you enter
All five run entirely in the browser. Addresses you paste, boxes you tick, situations you select — all of it exists only in the current page's memory, is computed on your own device, and disappears on refresh without leaving your machine.
Take the address checker as the clearest example: it contains its own implementations of SHA-256, Keccak-256, Base58 and Bech32, and decodes and recomputes locally. It queries no block explorer and sends the address nowhere, which is precisely why it cannot tell you a balance or an owner.
The reason we insist: a site about avoiding scams whose tools quietly send your pasted addresses back to a server would be the joke writing itself. So this is made true in the code, not promised in a policy.
Verifying it yourself
Do not take this page's word for it.
Three checks
- The network panel. Open developer tools, reload any tool page, and you will see only this site's own HTML, one CSS file, one JS file and images. Operating the tool afterwards produces no further requests.
- The executable scripts. Check inline
<script>blocks and/assets/main.jsfor actual calls tofetch,XMLHttpRequest,localStorage,gtagoranalytics— there are none. Those names appear only as explanatory text on this page. - The storage panel. Check cookies and storage in the application panel; visiting this site creates no entries.
The server and network layer
An honest caveat: every website's hosting server, and any content delivery network in front of it, necessarily processes requests, and that involves connection information such as IP addresses. That is how HTTP works rather than something this site chooses to gather.
The hosting server or content delivery network may retain security and access logs under its operating configuration. Whether those logs are enabled and how long they are kept are deployment facts that this static source cannot verify. What the code does prove is that it sends no extra analytics events, advertising identifiers or tool input, and has no site account with which to associate a connection.
Third parties
No third-party content is embedded anywhere: no video embeds, no social widgets, no external comment system, no CDN-hosted fonts or scripts.
Articles do contain ordinary links to external sites — exchange help pages, regulator publications, technical specifications. Following one takes you off this site, and that destination's own privacy policy applies from then on. We cannot and do not track where you go.
If you use a promotional code or link to register at Binance, Binance processes that registration under its own systems and privacy terms. This site currently has no verifiable material showing exactly which fields a referral dashboard exposes, so it does not promise that reporting is aggregate-only. Check Binance's current page before submitting; this site's commercial relationship is described on the disclosure page.
Your rights
Under common data protection frameworks such as the EU GDPR, you have rights over your personal data including access, rectification, erasure, restriction and portability.
The page code stores no forms, accounts, cookies, analytics identifiers or tool input. Any connection logs at the hosting layer depend on deployment configuration. If you want to ask about that processing, object to it, or think practice differs from this page, write through the contact page.
If this page changes, the date at the top is updated and the change is logged on the corrections page.