NHCheck

Last updated 23 September 2026

NHCheck Lite collects nothing

No account, no analytics, no crash reporting, no advertising, no third-party SDKs. Nothing you do in the app is sent anywhere, and there is no server behind it to send anything to.

What is collected

Nothing. NHCheck Lite does not ask you to sign in, does not collect or transmit personal information, does not upload results, does not read your contacts, photos, files or position, and does not track you across apps or websites.

What stays on the device

Your language and appearance choices, so they are remembered next time. That is all. Results are held only while the app is open.

Both settings go when you uninstall the app. They are also small enough to be eligible for Android's own backup to your Google account — a platform feature, switched on or off in your device settings, not something this app operates. Nothing reaches us either way: there is no server behind the app.

What a run sends

The app measures your connection, so a run puts traffic on the network. Only when you press Run, and only this:

Your routerEcho requests that never leave your own network
The first public router past itProbes to find it, then echo requests to measure it
A DNS resolverOne name lookup, to time it. No page is fetched.
CloudflareFiller data down and up for eight seconds each, to measure throughput

Any server you contact sees the public address the request came from — that is true of every app on your phone. Nothing identifying you is attached: no identifier, no device name, no account, no results.

Looking at your own network

When you open the LAN page, the app sends a probe to every address on your local network and asks whatever answers what it is called, over mDNS, SSDP and Bonjour — the same announcements those devices already broadcast to the network. The names and addresses it finds are shown to you and held only while the app is open. They are never sent anywhere: there is no server behind this app.

A device name is often a person's name with a machine after it, so it is the most personal thing the app ever reads. It is read on your device, shown on your device, and gone when you close the app.

Comparing resolvers

The DNS page can time your resolver against four public ones — Cloudflare, Google, Quad9 and OpenDNS — so a slow one is something you can see rather than guess at. It runs only when you open that page and ask for it, never as part of a run.

This is the one thing in the app that contacts a company you did not choose, so it is worth being exact. It sends each of those four a handful of ordinary lookups for well-known sites — wikipedia.org, github.com and the like — which are ours, not yours: the app never sends a name you looked up. Each of them sees the public address the request came from, as any site you open does. The timings are shown on your screen and kept nowhere.

Measuring the route

The ISP page can trace the route to a public resolver you pick — Cloudflare, Google, Quad9 or OpenDNS — and send a handful of echoes to every router that answers along it — the ones inside your provider’s network and the few beyond. It runs only when you open that page and ask for it, never as part of a run. Each router sees that the echo came from your public address, as it does for every packet you send; nothing else goes with it. The timings are drawn on your screen and kept nowhere.

On mobile data

With Wi-Fi off, the app reads what your phone already knows about its own mobile link: the operator, the radio, the signal and its quality, the band and frequency, and the identities of the cells it can hear. Android gates the cell identities behind the same Location permission as the Wi-Fi scan, for the same reason — a list of nearby towers can be used to infer position. All of it is read on your device and shown on your device. None of it is stored, and none of it is sent anywhere.

The location permission

Android requires the Location permission before any app may read the Wi-Fi network name, scan for nearby networks, or identify the mobile cells in range — because a list of what is nearby, whether networks or towers, can be used to infer position. It is used for those alone — your position is never read, stored or sent. The app never requests a location fix, never touches GPS, and never accesses location in the background. Nothing is asked at launch: the app explains why before the system prompt appears. Decline it and every check still runs; you lose the network name, the channel advice and the mobile link details. You can withdraw it at any time in Settings → Apps → NHCheck Lite → Permissions.

Your rights

Rights of access, correction, deletion and portability apply to personal data that has been collected. None is, so there is nothing to disclose, export or erase.

Changes

If a future version changes what the app contacts or keeps, this page is updated before that version is released, and the date above changes with it.

Contact

NHCheck · Jeddah, Saudi Arabia · info@nhcheck.net