BaitPath

Privacy

Pages now include Google Analytics, load a Google script and may set analytics cookies. The five tools still calculate in your browser without an input-upload function in their code. Local calculation does not mean that the entire page makes no network requests. Hosting infrastructure also processes connection data.

What the page code collects

Visit measurement and tool calculations

  • Google Analytics 4 is included. Pages load its script to measure visits.
  • Measurement can include visits and interactions. Examples include page views, referrers and, when enhanced measurement is enabled, scrolling or outbound clicks. Enabled events depend on service settings.
  • Analytics cookies may be set. Google documents cookies such as _ga for distinguishing users and sessions. Actual storage depends on browser and analytics settings.
  • The tools do not persist input. Tool code does not write input to localStorage, sessionStorage or IndexedDB. This statement does not cover third-party analytics storage.
  • No accounts, no login, no comments, no signup form. There is nothing here that asks you to submit anything.
  • Pages request third-party resources. Alongside local styles, scripts and images, they request Google analytics resources.

Local tools, visit analytics and hosting logs are separate processes. A locally calculated result does not mean that the website collects no visit data.

How the tools handle what you enter

All five run entirely in the browser. Addresses you paste, boxes you tick, situations you select — the tool code processes this in the current page's memory and computes on your device. It does not connect those values to an analytics event or upload endpoint.

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 and reload a tool page. Distinguish local resources from Google analytics requests. Try a non-sensitive example and inspect request payloads for input values; the absence of a tool upload endpoint does not mean no network traffic.
  • The executable scripts. The page head contains a Google script and gtag initialization. Separately inspect the tool event handlers and calculations to see whether input values are passed to analytics or a network call.
  • The storage panel. Check cookies and storage in the application panel, including analytics entries such as _ga. You can clear or restrict cookies; blocking cookies alone does not block every analytics request.

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. Google analytics is separate from hosting logs. This site has no account system. Analytics retention settings and enabled enhanced-measurement events cannot be established from the local source alone.

Third parties

Google Analytics is a third-party service included on these pages. See Google’s GA4 cookie documentation and enhanced measurement documentation, checked in September 2026.

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. If outbound-click measurement is enabled, analytics may record the link you click. This does not give this site visibility into everything you do at the destination.

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 tool code does not store or upload input; visit analytics may use cookies and identifiers. Browser controls can restrict analytics scripts and manage cookies. Hosting logs and analytics retention depend on their service 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.