Privacy Policy for Network Analyzer

Last updated: May 17, 2026

Thanks for using Network Analyzer. This policy explains, in plain language, what little information the app handles and why. The short version: there is no account, no sign-up, and no profile. I don't want your personal data and I've designed the app to collect as little of it as possible.

If you only read one paragraph, read this one: Network Analyzer does not ask for your name, email, phone number, or any login. I don't know who you are, and I don't want to. The Lite version is free, and it is supported by ads served by Google AdMob — you'll find an explanation of what that involves in Section 3 below.

1. Who is responsible for your data

The person responsible for this app (the "data controller" in GDPR terms) is:

Name: Jiří Techet
Country: Czech Republic
Contact email: contact (iOS), contact (Android)
Website: https://techet.net

If you have any questions about this policy or your data, just email me at the address above.

2. What the app does

Network Analyzer is a free, ad-supported tool for inspecting networks. All of its features run on your device and operate on the network you choose to analyze. Depending on what you ask it to do, it can:

Show information about your current connection (Wi-Fi SSID/BSSID, IP address, default gateway, DNS server, external IP, cellular and VPN details where available).
Scan your local Wi-Fi network to discover devices on it, along with their IP addresses, hostnames, manufacturer, and which services they expose.
Display Wi-Fi signal strengths and channel usage for nearby networks (Android only).
Run common network tools: ping, traceroute, port scan, Whois, and DNS lookup against hosts you specify.

Results are shown to you on the device. They are not sent to me or stored on any server I operate.

3. What information is processed

I've grouped this by why the information is processed, so you can see exactly what is going on.

a) Crash reports and basic analytics (via Google Firebase)

The app uses Google Firebase Crashlytics (to tell me when the app crashes) and Google Firebase Analytics (to understand things like how many people open the app, which features get used, and on which devices).

Firebase does not receive your name, email, or any account information, because the app doesn't have any. What Firebase does process is technical data such as:

A randomly generated, app-specific installation ID (this is not your device ID and cannot be tied back to you personally).
App version, device model, operating system version, language, and country (derived from IP, not stored as a precise location).
Crash diagnostics (stack traces, the state of the app at the moment of a crash).
Events such as "app opened" or "feature X used."

I use this only to keep the app working and to decide what to improve. I never try to identify individual users, and I have no tools to do so.

Google acts as a data processor on my behalf. They may transfer this data outside the EU/EEA, including to the United States, under Google's standard contractual clauses and the EU–US Data Privacy Framework. You can read Google's own description of Firebase data handling here: https://firebase.google.com/support/privacy.

Legal basis (GDPR Art. 6): legitimate interest (Art. 6(1)(f)) – keeping the app stable and fixing bugs.

b) Ads (via Google AdMob)

The Lite version of the app is free, and it is supported by banner ads shown at the bottom of the screen. The ads are served by Google AdMob.

When you first open the app in the EU/EEA (or other regions with similar laws), Google's consent dialog will ask you to choose between:

Personalized ads – AdMob may use your device's advertising identifier and other information (such as IP-derived approximate location, device type, OS, and app usage) to show ads tailored to your interests, possibly through partner ad networks.
Non-personalized ads – ads are not based on your previous behavior. AdMob still receives some technical information needed to deliver the ad (like your IP address, device type, and a generic context), but it is not used to build an advertising profile of you.

You can change this choice at any time from the About page in the app → Configure Ad Consent.

I do not personally see or receive any of this advertising data. AdMob is operated by Google, which acts as an independent controller for advertising data. For details on what AdMob collects and how Google uses it, please see:

AdMob & AdSense privacy: https://support.google.com/admob/answer/6128543
How Google uses information from sites or apps that use our services: https://policies.google.com/technologies/partner-sites

Legal basis (GDPR Art. 6):

Personalized ads: your consent (Art. 6(1)(a)), given through the Google consent dialog. You can withdraw it any time via Configure Ad Consent.
Non-personalized ads: legitimate interest (Art. 6(1)(f)) — funding the free version of the app — balanced against the very limited data used.

c) Server logs on Google App Engine (US)

A few features of the app need to talk to a small backend I operate. The backend runs on Google App Engine, hosted in the United States. When the app makes a request to it, Google App Engine automatically writes a request log entry that contains:

The IP address of the request.
The time of the request and the endpoint that was contacted.
Standard technical metadata (e.g., HTTP method, response status, user-agent string).

These logs exist for one reason: debugging and troubleshooting, so I can figure out what went wrong if something breaks.

Logs are stored in Google App Engine's default log bucket and are automatically deleted by Google after 30 days. This retention is part of the App Engine platform — the logs are not under my direct control on a per-entry basis, and I do not export them, copy them elsewhere, or extend their retention.

Because the backend runs on Google App Engine in the United States, your IP address is transferred outside the EU/EEA. This transfer relies on the safeguards provided by Google Cloud (standard contractual clauses and Google's certification under the EU–US Data Privacy Framework). Google's own privacy information for Google Cloud services is available at https://cloud.google.com/terms/data-processing-addendum.

Legal basis (GDPR Art. 6): legitimate interest (Art. 6(1)(f)) – keeping the backend running and diagnosing problems.

d) What is NOT collected

To be explicit, the app does not collect or store:

Your name, email address, phone number, or any account credentials (there are no accounts).
Your location (location information never leaves your device).
Contacts, photos, microphone, or camera data.
The content of your network traffic.
A list of websites you visit.
The scan results, LAN history, or any other diagnostic output produced by the app — these stay on your device.

4. Who your data is shared with

Nobody, beyond what is needed to run the app:

Google (Firebase) – as described above, as a data processor for crash reports and analytics.
Google (AdMob) – as the ad provider, as described in Section 3b. AdMob may share data with its advertising partners as part of delivering ads.
Google (App Engine / Cloud Logging) – as the hosting provider for my backend, which therefore handles the temporary server logs.

I do not sell data. There is no marketing on my side.

5. How long data is kept

App Engine server logs: automatically deleted by Google after 30 days (the platform default for App Engine's request logs).
Firebase Crashlytics data: retained according to Google's defaults (typically up to 90 days for crash data).
Firebase Analytics data: retained for the minimum period configured (set to 2 months for user/event-level data, with aggregated event data kept longer for trend analysis).
AdMob data: governed by Google's advertising retention policies (see the links in Section 3b).

6. Your choices and how to opt out

The app does not currently offer an in-app toggle to disable analytics or crash reporting. If you would prefer not to send any data to Firebase, your options are:

Uninstall the app. Once uninstalled, no further data is generated.
Restrict tracking on your device. On iOS, you can deny app-tracking permissions in Settings. On Android, you can reset or limit your advertising ID in Settings.
Block network access for the app at the OS level if you want to prevent all outgoing analytics and backend traffic — note that most app features won't work in that case.

For advertising, you can:

Open the About page in the app and tap Configure Ad Consent to change your personalized/non-personalized ad choice at any time.
Reset or limit your advertising ID in your device's privacy settings.
Upgrade to Network Analyzer Pro, which has no ads, no AdMob SDK, and no advertising identifier usage.

7. Your rights under GDPR

If you are in the EU/EEA (and many other places with similar laws), you have the right to:

Access any personal data I hold about you.
Correct it, if it's wrong.
Erase it ("right to be forgotten").
Restrict or object to how it's processed.
Data portability – receive your data in a machine-readable format.
Withdraw consent at any time, where processing is based on consent.
Lodge a complaint with your local data protection authority.

A practical note on what these rights look like in practice:

The app does not identify you, so in most cases I have no data I can tie back to you on request.
Firebase data is keyed to a random installation ID that I cannot link to a person. If you want this data erased, you can clear the app's data on your device (which resets the ID), or uninstall the app. You can also contact Google directly regarding their processing of Firebase data.
AdMob / advertising data is processed by Google as its own controller. For access, deletion, or other requests about advertising data, please use Google's Ad Settings (https://adssettings.google.com) or contact Google directly. You can also withdraw consent to personalized ads at any time using Configure Ad Consent in the app's About page.
App Engine server logs are managed by Google Cloud Logging and are not individually editable by me — I cannot search for and delete a specific log line on request. Logs are automatically purged after 30 days, so any request log involving you will be deleted within that window regardless.

8. Children

The app is not directed at children under 16, and I do not knowingly process personal data from children.

9. Security

I take reasonable, industry-standard steps to protect the limited data the app handles: encrypted connections (HTTPS/TLS) between the app and the backend, reliance on Google's security for Firebase, AdMob and App Engine, and an overall design that avoids collecting anything that isn't necessary. No system is perfect, but there is very little here to protect in the first place — which is the safest design of all.

This policy is written in plain language on purpose. If anything here is unclear, that's my fault — please let me know and I'll fix it.