SignalMonitoring
WiFi Monitor — Privacy Policy
Last updated: July 13, 2026
This Privacy Policy describes how the developer processes information when you use the WiFi Monitor mobile applications for Android (the "Application" or "App").
The Application helps you monitor Wi‑Fi networks and related connection information on your device. This policy applies to:
| App | Package name | Notes |
|---|---|---|
| WiFi Monitor (free) | com.signalmonitoring.wifimonitoring |
Includes advertising |
| WiFi Monitor Pro | com.signalmonitoring.wifimonitoringpro |
No advertising SDKs |
If you do not agree with this policy, please do not use the Application.
1. Who is responsible for your information?
Data controller: Alexander Kozyukov
Privacy contact: [email protected]
For privacy-related requests, including requests to exercise your rights under applicable data protection laws, contact the developer at the email address above. The developer may ask you to verify your identity before responding.
2. Summary of what the Application does
The Application:
- Scans and displays information about nearby and connected Wi‑Fi access points (for example, SSID, BSSID/MAC address, signal strength, channel, frequency, and security type).
- May scan devices on your local network when you use related features (for example, IP addresses and MAC addresses visible on the local subnet).
- Stores some monitoring data locally on your device to show charts, history, and settings.
- Sends limited diagnostic and usage information to analytics and crash-reporting services.
- In the free version only, displays advertisements through third-party advertising partners.
- May look up your public IP address and related ISP/country information using external services when you use those features.
The Application does not operate a user account system, and full Wi‑Fi scan results or local network scan results are not uploaded to the developer's own servers based on the current Application code.
3. Information processed
3.1 Information processed on your device
The Application processes the following categories of information primarily on your device:
| Category | Examples | Purpose |
|---|---|---|
| Wi‑Fi network information | SSID, BSSID/MAC address, RSSI, frequency, channel, capabilities, security type, Wi‑Fi standard | Display network status, charts, scan results, and monitoring features |
| Connected network information | Currently connected SSID/BSSID and related connection parameters | Show connection details and monitor changes |
| Local network information | IP addresses and MAC addresses of hosts on your LAN, gateway/DHCP information | Local network scan and diagnostics |
| Device network identifiers | Your device's Wi‑Fi interface MAC address where available from the operating system | Display and diagnostics |
| Manufacturer lookup data | OUI/manufacturer names derived from BSSID prefixes | Identify access point manufacturers |
| User-provided labels | Custom host names mapped to MAC addresses, hidden-network preferences | Personalize scan results |
| Known networks list | SSIDs previously seen by the Application | Notifications and network history |
| App settings and preferences | Monitoring intervals, notification settings, ping targets, logging options | Operate features according to your choices |
| Local diagnostic history | Short-term RSSI and speed measurements stored in a local database | Charts and recent monitoring history |
| Optional log files | Connection logs; in Pro, optional nearby-network logs that may include SSID, BSSID, RSSI, channel, and frequency | Troubleshooting at your request; stored under app-private storage |
Most of this information remains on your device unless you choose to share it (for example, by exporting log files or sending a support email).
3.2 Information generated or collected for analytics and diagnostics
The Application uses Google Firebase services in both the free and Pro versions:
| Service | What may be processed | When |
|---|---|---|
| Firebase Analytics | App events, feature usage, locale/language, app store identifier, Google Play services status, app standby bucket, ISP name/description/country code (when that feature is used), ad lifecycle events (free version), preference keys changed (not values), and other operational events | During normal app use |
| Firebase Crashlytics | Crash reports, error logs, diagnostic breadcrumbs, install-scoped identifier, locale/language, device ABI list, app store identifier, Google Play services status, app standby bucket | Especially in release builds |
| Firebase Performance Monitoring | Performance traces and related technical metrics | Release builds |
The Application assigns a random install-scoped identifier (a UUID stored in app-private preferences) and uses it as the Firebase Analytics and Crashlytics user ID. This identifier is not the Android advertising ID and is not derived from your hardware serial number.
Crashlytics collection is disabled in debug builds. Firebase Performance collection is disabled in debug builds.
3.3 Information processed by advertising partners (free version only)
If you use WiFi Monitor (free), the Application integrates Yandex Mobile Ads and related mediation partners, which may include:
- Google (AdMob)
- Mintegral
- Liftoff Monetize (Vungle)
When ads are shown, these partners may process device and advertising-related information according to their own privacy policies. The Application initializes the Yandex SDK with ad and location consent flags set to enabled in code; a separate consent management platform (CMP) is not currently integrated.
If Yandex ad loading fails, the Application may show a house ad managed by the developer that can use app store and package information to promote related apps.
The Pro version does not include these advertising SDKs.
3.4 Information sent to external lookup services
When you use public IP or ISP information features, the Application sends network requests to third-party services. These services typically infer your public IP address from the request itself.
Public IP lookup services used may include:
- api.ipify.org
- ipv4.seeip.org / ipv6.seeip.org
- 4.ident.me / 6.ident.me
- ipv4.icanhazip.com / ipv6.icanhazip.com
- checkip.amazonaws.com
- api-ipv6.ip.sb
ISP / country lookup services used may include:
- api.ip2location.io
- ipwhois.app
- free.freeipapi.com
The Application displays the returned information on your device. In addition, when ISP information is successfully retrieved, the Application may send ISP name, description, and country code to Firebase Analytics. The Application does not send your public IP address itself as an analytics event parameter based on the current code.
3.5 Information fetched from the developer's website
On startup, the Application may download a small configuration file from:
https://signalmonitoring.com/app_settings/wm_config.txt
This file is used to configure advertising settings (for example, Yandex ad unit IDs) and related app behavior. The request is a standard HTTPS GET request.
3.6 Information you choose to send to the developer
If you contact the developer through the in-app "mail to developer" feature, your email app may include:
- App name and version
- Android version
- Device manufacturer and model
- Install-scoped device ID
- App store identifier
- Permission grant status
- App standby bucket
You can edit or remove this information before sending the message. The developer receives only what you choose to send via your email provider.
3.7 Information not collected through the Application
Based on the current Application code:
- GPS coordinates or continuous location history are not read or stored.
- Your phone number is not collected.
- Full Wi‑Fi scan databases or LAN scan results are not uploaded to the developer's servers.
- Registration is not required, and your name or email address is not collected unless you contact the developer voluntarily.
Please note: Wi‑Fi network identifiers (especially SSID and BSSID) can reveal information about where you are or where you have been, even when precise GPS is not used.
4. Permissions and location-related processing
To perform Wi‑Fi scanning on Android, the Application may request:
ACCESS_COARSE_LOCATIONACCESS_FINE_LOCATION(on supported Android versions)NEARBY_WIFI_DEVICES(on newer Android versions, declared as not used for location where applicable)- Wi‑Fi, network, notification, foreground service, and boot-completed permissions needed for monitoring features
The Application uses location-related permissions because Android requires them for Wi‑Fi scanning on many OS versions. The Application checks whether location services are enabled and may prompt you to enable them, but it does not use the location permission to collect GPS coordinates for storage or transmission.
Background monitoring may run as a foreground service with a location-related service type on supported Android versions because of how Android classifies Wi‑Fi monitoring services.
You can revoke permissions at any time in Android settings, but some features may stop working.
5. How information is used
Information is processed for the following purposes:
| Purpose | Examples |
|---|---|
| Provide app functionality | Show Wi‑Fi/network status, scans, charts, logs, notifications, and diagnostics |
| Maintain and improve the Application | Analytics, crash reporting, performance monitoring, troubleshooting |
| Display advertising | Show ads in the free version and measure ad delivery |
| Configure the Application | Download remote app/ad configuration |
| Respond to support requests | Handle emails you send voluntarily |
| Comply with legal obligations | Where required by applicable law |
6. Legal bases for processing (EEA, UK, and similar jurisdictions)
If you are in the European Economic Area (EEA), the United Kingdom, or another jurisdiction that requires a legal basis for processing, the following bases apply depending on the processing activity:
| Processing activity | Legal basis |
|---|---|
| Providing core app features you request | Performance of a contract or steps at your request before using the App |
| Wi‑Fi/network scanning and on-device storage needed for requested features | Performance of a contract / legitimate interests in operating the App |
| Analytics, crash reporting, and performance monitoring | Legitimate interests in maintaining, securing, and improving the Application; where required by law, consent |
| Advertising in the free version | Consent or legitimate interests, depending on applicable law and your choices; where consent is required, you should be able to refuse or withdraw it through device or partner controls |
| Responding to support emails | Legitimate interests and/or performance of a contract |
| Compliance with legal obligations | Legal obligation |
Where processing is based on legitimate interests, you have the right to object as described below. Where processing is based on consent, you may withdraw consent at any time without affecting the lawfulness of processing before withdrawal.
7. How information is shared
Information may be shared with the following categories of recipients:
| Recipient | Why information is shared |
|---|---|
| Google / Firebase | Analytics, crash reporting, and performance monitoring |
| Yandex and ad mediation partners | Advertising in the free version only |
| Public IP and ISP lookup providers | Retrieve public IP and ISP/country information at your use of those features |
| Google Play services | In-app review and update flows on Google Play builds |
| Your email provider | Only if you choose to contact the developer by email |
| Other apps or services you choose | For example, when you open external links, share log files, or visit your router settings in a browser |
Personal information is not sold in the conventional sense. Advertising partners may process information for ad delivery and measurement under their own policies.
Third-party privacy policies
Because not all third-party processing is under the developer's control, please review the privacy policies of relevant partners, including:
- Google / Firebase: https://policies.google.com/privacy
- Yandex: https://yandex.com/legal/confidential/
- Google Ads / AdMob: https://policies.google.com/technologies/ads
- Mintegral: https://www.mintegral.com/en/privacy/
- Liftoff: https://liftoff.io/privacy-policy/
- IP lookup and ISP providers listed in Section 3.4
8. International transfers
Service providers used by the Application may process information in the United States and other countries outside your own. Those countries may have data protection laws that differ from the laws of your country.
Where required by applicable law, appropriate safeguards for international transfers are used, such as standard contractual clauses or equivalent mechanisms offered by service providers. You may contact the developer for more information about safeguards relevant to your request.
9. Data retention
Retention depends on the type of information:
| Data type | Retention |
|---|---|
| Short-term monitoring history (for example, recent RSSI/speed entries) | Kept locally for a limited rolling window suitable for charts and recent diagnostics; older entries are deleted automatically |
| App settings, known networks, host names, install-scoped ID | Kept locally until you clear app data, uninstall the Application, or change/delete the relevant settings |
| Optional log files | Kept locally until you delete them in the App or remove app data |
| Firebase analytics and crash data | Retained according to Google Firebase retention settings and operational needs |
| Advertising partner data | Retained according to each partner's policies |
| Support emails | Retained as long as needed to handle your request and for reasonable business record-keeping |
Fixed retention periods are not committed to for all categories where retention is controlled by third-party platforms or operational necessity.
10. Your choices and controls
You can:
- Revoke permissions in Android settings.
- Clear app data or uninstall the Application to remove local databases, preferences, install-scoped ID, and log files stored by the App.
- Delete log files using in-app controls where available.
- Disable ad personalization through Android settings and partner opt-out mechanisms where available.
- Avoid optional features such as public IP / ISP lookup, support email, and log sharing.
- Use WiFi Monitor Pro if you want the version without third-party advertising SDKs.
Because the Application does not use account-based authentication, many rights must be exercised through device controls, partner opt-out tools, uninstallation, or by contacting the developer.
11. Your rights (EEA, UK, and similar jurisdictions)
Depending on your location, you may have the right to:
- Access your personal information
- Rectify inaccurate information
- Erase your personal information
- Restrict processing
- Object to processing based on legitimate interests
- Data portability, where applicable
- Withdraw consent at any time, where processing is based on consent
- Lodge a complaint with your local data protection authority
To exercise these rights, contact [email protected]. The developer will respond within the time required by applicable law.
If you are in the EEA or UK, you may also complain to your local supervisory authority.
12. California and U.S. state privacy notices
If you are a resident of California or another U.S. state with a comprehensive privacy law, you may have additional rights, such as the right to know, delete, correct, or opt out of certain processing.
Based on the current Application:
- Personal information is not sold for money.
- Personal information is not shared for cross-context behavioral advertising in a way controlled by the developer as a "sale" or "share" under California law, although advertising SDKs in the free version may engage in ad-related processing under their own policies.
- Sensitive personal information is not collected for the purpose of inferring characteristics about you, although Wi‑Fi identifiers may be sensitive in practice.
To submit a request, email [email protected].
13. Children
The Application is not directed to children under 13, and personal information from children under 13 is not knowingly collected. If you believe a child has provided personal information to the developer, contact the developer; appropriate steps will be taken to delete it.
14. Security
Reasonable administrative, technical, and organizational measures are used to protect processed information. For example:
- The Application limits backup behavior in the manifest and uses app-private storage for databases, preferences, and logs.
- Access to support communications is limited to what is needed to operate and support the Application.
However, no method of transmission or storage is completely secure, and absolute security cannot be guaranteed.
15. Changes to this Privacy Policy
This Privacy Policy may be updated from time to time. When it is, the "Last updated" date above will be revised. If changes are material, additional notice may be provided in the Application or on the developer's website where appropriate.
Your continued use of the Application after an update means you acknowledge the revised policy, to the extent permitted by law.
16. Contact
If you have questions or concerns about this Privacy Policy or the developer's data practices, contact:
Alexander Kozyukov
Email: [email protected]
17. Important note about this document
This Privacy Policy is based on the Application's source code and configuration as of the date above. It is intended to describe product privacy practices accurately, but it is not legal advice. Before publishing, especially for advertising and EEA/UK compliance, consider review by qualified legal counsel.