ClearEvo browser tools: privacy - and how to verify it yourself

The browser tools on this site - GNSS Monitor, GIS converter, QR generator, audio converter, HyperTerminal, AT Command Tester, Hex viewer/editor, doctor, calc, isearch - run 100% in your browser. Your data (serial traffic, GNSS positions, files you open, anything you type) is processed on your machine and never uploaded.

The one external service these pages use is Google Analytics, for visit stats only: which pages get visited, how many visitors, roughly from where. All GA4 “enhanced measurement” auto-events (outbound-click, scroll, form tracking and the rest) are turned off for this property - last verified 2026-07-22.

Don’t take my word for any of this - here is how to check each claim:

1. Watch the network traffic yourself

Open your browser’s developer tools (F12) → Network tab, then use any of the tools with your real device or file. You will see the page’s own assets from clearevo.com, one script load from googletagmanager.com, and small /g/collect page-view pings to Google Analytics. No request carries your serial data, position, file contents, or anything you typed. Official guide to the Network panel: https://developer.chrome.com/docs/devtools/network

2. Check that GA enhanced measurement is really off

Enhanced measurement is a GA4 feature that auto-tracks outbound link clicks, scrolls and more - official description: https://support.google.com/analytics/answer/9216061. A property’s enhanced-measurement settings are compiled into the analytics script Google serves for it, so you can verify from the outside: open https://www.googletagmanager.com/gtag/js?id=G-H457QK43L6 and search the text for __ccd_em_ (e.g. __ccd_em_outbound_click). When enhanced measurement is disabled, those modules are absent from the script.

3. Read the source

The tools are open source: web_gnss, hyperterminal, web_at, web_fun (doctor / calc / isearch / hex).


One design detail in the same spirit: the GNSS tool’s “open in map” link deliberately keeps your coordinates out of the link’s href (the map is opened by script only when you click), so no analytics click-tracker could ever read a position from the page - even if enhanced measurement were turned back on.

If you spot any request or behavior that contradicts the above, please comment on any post or open an issue on the repos - I will fix it and say so.

Full disclosure: this post - and any code or tool it describes - was co-authored with Claude (Anthropic’s AI, via Claude Code). I directed, reviewed and tested; Claude wrote most of the code and most of the text. I don’t want to pretend otherwise.