SignalMonitoring
GPS Monitor — Privacy Policy
Last updated: July 13, 2026
This Privacy Policy describes how the developer processes information when you use the GPS Monitor mobile applications for Android (the "Application" or "App").
The Application helps you monitor satellite navigation (GNSS) signals, your current location, movement parameters, and visible satellites on your device. This policy applies to:
| App | Package name | Notes |
|---|---|---|
| GPS Monitor (free) | com.signalmonitoring.gpsmonitoring |
Includes advertising |
| GPS Monitor Pro | com.signalmonitoring.gpsmonitoringpro |
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 your current GPS/GNSS location (for example, latitude, longitude, altitude, speed, bearing, and horizontal/vertical accuracy).
- Shows information about visible navigation satellites (for example, constellation, signal strength, azimuth, elevation, and whether a satellite is used in a position fix).
- Uses device sensors to orient the satellite sky plot on the Locator screen.
- Runs optional background monitoring as a foreground service with a persistent notification when you enable it.
- Stores app settings and preferences locally on your device.
- 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 offer Google Play in-app review and update flows on Google Play builds.
The Application does not operate a user account system, does not maintain a history of your location track, and does not upload GPS coordinates or GNSS scan results 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 |
|---|---|---|
| Location and GNSS data | Latitude, longitude, altitude, speed, bearing, horizontal/vertical accuracy, GPS provider status | Display location, overview, map marker, and monitoring features |
| Satellite information | Constellation, satellite ID, azimuth, elevation, carrier frequency, C/N₀, used-in-fix status | Satellite list, sky plot, overview, and foreground notification summary |
| Device sensor data | Accelerometer and magnetometer readings | Orient the satellite sky plot on the Locator screen |
| App settings and preferences | Theme, speed units, coordinate format, satellite sort/filter options, launch counter, dialog timestamps | Operate features according to your choices |
| Current session state | Latest location and GNSS status held in memory while monitoring is active | Real-time display during app use |
Most of this information remains on your device unless you choose to share it (for example, by copying coordinates to the clipboard or sending a support email).
The Application uses a static map image on the Location screen. It does not load online map tiles from a third-party map provider.
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 (for example, ad lifecycle events in the free version and notification clicks), feature usage, and other operational events automatically collected by the Firebase SDK | During normal app use |
| Firebase Crashlytics | Crash reports, error logs, diagnostic breadcrumbs, locale/language, app store identifier, JVM memory metrics, and device ABI list | Especially in release builds |
The Application logs additional operational breadcrumbs to Crashlytics, such as tab navigation, monitoring service lifecycle events, and permission grant status. Based on the current Application code, GPS coordinates and GNSS measurements are not sent to Firebase Analytics or Crashlytics as event parameters or custom keys.
Firebase Analytics and Crashlytics may also process identifiers and technical metadata generated by the Firebase SDK itself (for example, Firebase Installation ID / App Instance ID), according to Google's policies.
3.3 Information processed by advertising partners (free version only)
If you use GPS Monitor (free), the Application integrates Yandex Mobile Ads and may show a house ad managed by the developer when Yandex ad loading fails.
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 (except on some store builds), the Application may show a house ad that can use app store and package information to promote related apps from the developer.
The Pro version does not include these advertising SDKs.
Yandex-related SDK components may run in separate app processes (for example, AppMetrica/Metrica processes associated with the Yandex SDK).
3.4 Google Play services (Google Play builds only)
On Google Play builds, the Application may use:
- Google Play In-App Review — to ask you to rate the Application after several launches.
- Google Play In-App Update — to offer flexible app updates through Google Play.
These flows are provided by Google Play services and are subject to Google's policies.
3.5 Information you choose to send to the developer
If you contact the developer through the in-app feedback feature, your email app opens with a pre-filled subject line that may include:
- App name
- App version
You can edit or remove this information before sending the message, and you choose what to include in the email body. 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:
- A location history or movement track is not stored locally in a database or file.
- Your phone number is not collected.
- GPS coordinates and GNSS measurements 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.
- Cell network / telephony parameters are not collected in the current Application code.
- Online map providers are not used for the in-app map display.
Please note: precise location data can reveal information about where you are or where you have been, even when you do not actively share it with others.
4. Permissions and location-related processing
To perform GNSS monitoring on Android, the Application requests:
ACCESS_FINE_LOCATIONACCESS_COARSE_LOCATIONINTERNETFOREGROUND_SERVICEand, on supported Android versions,FOREGROUND_SERVICE_DATA_SYNCPOST_NOTIFICATIONS(on Android 13 and newer)
The Application requires location permissions because reading GPS/GNSS location and satellite status is the core purpose of the App.
Background monitoring may run as a foreground service when you enable it. The persistent notification shows monitoring status and a satellite count summary; based on the current code, it does not display your coordinates on the lock screen.
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 location, GNSS status, satellite list, sky plot, map marker, notifications, settings |
| Maintain and improve the Application | Analytics, crash reporting, troubleshooting |
| Display advertising | Show ads in the free version and measure ad delivery |
| Respond to support requests | Handle emails you send voluntarily |
| Offer store-specific features | In-app review and update flows on Google Play builds |
| 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 |
| GNSS/location reading and on-device display needed for requested features | Performance of a contract / legitimate interests in operating the App |
| Analytics and crash reporting | 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 and crash reporting |
| Yandex and related ad components | 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 open app store links or copy coordinates into another app |
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 Play: https://policies.google.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 |
|---|---|
| Current location and GNSS session data | Held in memory while monitoring is active; not stored as a long-term location history in the current App code |
| App settings and preferences | Kept locally until you clear app data, uninstall the Application, or change/delete the relevant settings |
| 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.
- Disable background monitoring using the in-app monitoring toggle.
- Clear app data or uninstall the Application to remove local preferences and in-memory session data stored by the App.
- Disable ad personalization through Android settings and partner opt-out mechanisms where available.
- Avoid optional actions such as copying coordinates, sending support email, or opening external store links.
- Use GPS 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.
- Precise geolocation data is processed to provide core app functionality and may be made available to advertising SDKs in the free version because location consent is enabled for the Yandex SDK in code.
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 (
allowBackup="false") and uses app-private storage for preferences. - 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.