Cell Signal Monitor — Privacy Policy
Last updated: July 13, 2026
This Privacy Policy describes how the developer processes information when you use the Cell Signal Monitor mobile applications for Android (the "Application" or "App").
The Application helps you monitor cellular network connectivity and related telephony information on your device. This policy applies to:
| App | Package name | Notes |
|---|---|---|
| Cell Signal Monitor (free) | com.signalmonitoring.gsmsignalmonitoring |
Includes advertising |
| Cell Signal Monitor Pro | com.signalmonitoring.gsmsignalmonitoringpro |
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: contact@signalmonitoring.com
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:
- Reads and displays cellular network information (for example, operator name, MCC/MNC, cell identifiers, signal strength, network type, roaming status, and related technical parameters).
- Monitors mobile data transfer speed using system traffic counters.
- Stores monitoring data locally on your device to show charts, logs, statistics, widgets, 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 check whether system location services are enabled, because Android often requires location permission and enabled location services for cellular network access.
The Application does not operate a user account system, and cellular monitoring history is 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 |
|---|---|---|
| Cellular network information | Operator name, MCC/MNC, raw cell ID (CID/NCI), LAC/TAC, network type, RSSI, RSRP, RSRQ, ARFCN, PCI, roaming status, service state | Display connection status, charts, logs, statistics, and widgets |
| SIM information | Whether one or two SIM cards are present, dual/single-SIM mode, active SIM slot selection | Operate dual-SIM monitoring and related UI |
| Mobile data speed | Mobile RX/TX byte counters and derived uplink/downlink speed | Speed chart and monitoring features |
| Wi‑Fi connection state | Whether Wi‑Fi is connected, lost, unavailable, or unknown (SSID/BSSID are not read) | Supplementary connectivity context |
| Location services status | Whether GPS and network location providers are enabled on the device | Inform the user when location services are required for cell access |
| App settings and preferences | Chart size, log retention, stats window, log format, delimiter, screen-on setting, notification-related choices | Operate features according to your choices |
| Local monitoring history | Strength measurements, speed measurements, deduplicated cell records, monitoring start/stop events stored in a local Room database | Charts, logs, statistics, and recent monitoring history |
| Exported files you create | CSV log files and chart screenshots shared through Android share flows | Troubleshooting or sharing at your request |
Most of this information remains on your device unless you choose to share it (for example, by exporting log files, sharing chart images, 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, screen views, locale/language, app flavor, device brand and model, SIM mode, app store identifier, preference keys changed (not values), share-button clicks, ad lifecycle events (free version), and other operational events | During normal app use |
| Firebase Crashlytics | Crash reports, error logs, diagnostic breadcrumbs, locale/language, SIM mode, app store identifier, JVM memory information, device ABI list, and screen/lifecycle log messages | Especially in release builds |
| Firebase Performance Monitoring | Performance traces and related technical metrics | Release builds |
Firebase assigns its own installation-scoped identifiers through the Firebase SDK. The Application does not set a custom analytics user ID in code and does not read your phone number, IMEI, or IMSI for analytics.
3.3 Information processed by advertising partners (free version only)
If you use Cell Signal Monitor (free), the Application integrates Google AdMob, Yandex Mobile Ads, and related mediation partners, which may include:
- Google (AdMob)
- Mintegral
- Liftoff Monetize (Vungle)
- AppLovin
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.
The Application reads SIM and registered-network country ISO codes on the device to decide whether AdMob or Yandex should be used in a given session. This country information is used for ad routing logic and is not uploaded to the developer's servers based on the current code.
If primary 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 accessed from the developer's website
The Application may open pages on the developer's website in your browser, including:
https://signalmonitoring.com/en/cell-signal-monitor-privacy-policyhttps://signalmonitoring.com/en/cell-signal-monitor-description
These are standard user-initiated or settings-screen links. Based on the current Application code, the Application does not download remote configuration files from the developer's website on startup.
3.5 Information you choose to send to the developer
If you contact the developer through the in-app "send email to the developer" feature, your email app may prefill:
- App name
- App version
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.6 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, IMEI, and IMSI are not collected.
- Cellular monitoring databases 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: cellular network identifiers (especially cell ID and LAC/TAC) 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 cellular monitoring on Android, the Application may request:
READ_PHONE_STATEACCESS_COARSE_LOCATIONACCESS_FINE_LOCATION(on supported Android versions)ACCESS_NETWORK_STATEINTERNETPOST_NOTIFICATIONS- Foreground service permissions needed for background monitoring, including a location-related foreground service type on supported Android versions
The Application uses location-related permissions because Android requires them for access to cellular network information 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 runs as a foreground service with a persistent notification.
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 cellular status, charts, logs, statistics, widgets, 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 |
| 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 |
| Cellular monitoring 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 |
| 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 share log files, chart images, or open website links |
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/
- AppLovin: https://www.applovin.com/privacy/
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 chart history (strength and speed measurements) | Kept locally for a limited rolling window suitable for charts; older entries are deleted automatically |
| Log and statistics history | Kept locally for user-configurable windows (defaults: 3 hours for logs and 60 minutes for statistics); older entries are deleted automatically |
| App settings and local database records | Kept locally until you clear app data, uninstall the Application, or change/delete the relevant settings |
| Exported files you create | Kept wherever you save or share them; not controlled by the Application after export |
| 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, and exported files stored by the App.
- Adjust retention and display settings in the Application where available.
- Disable ad personalization through Android settings and partner opt-out mechanisms where available.
- Avoid optional actions such as support email, log sharing, and chart sharing.
- Use Cell Signal 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 contact@signalmonitoring.com. 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 cellular network identifiers may be sensitive in practice.
To submit a request, email contact@signalmonitoring.com.
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 disables Android backup for app data and excludes databases, preferences, and files from backup rules.
- Monitoring data is stored in app-private storage.
- 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: contact@signalmonitoring.com
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.
SignalMonitoring