Privacy Policy
Effective Date: 3rd November 2026
This Privacy Policy describes how the CellInfo Android application (“we”, “our”, “us”), developed by theBFGuk, handles your information when you use our services.
1. Information We Collect
CellInfo does not collect or store your local Mast Names, signal history, imported tower databases, cached lookup results or nearby-cell results on CellInfo-operated servers. CellInfo processes these data locally on your device, and data that remains local is not accessible to CellInfo or the developer. You control whether this data is exported or shared. They leave the device only when you deliberately use an online lookup, upload, export or share action. When you explicitly use an online lookup, selected cellular identifiers may be sent to the relevant third-party service, such as OpenCellID or Unwired Labs. CellInfo does not automatically upload measurements in the current version.
2. Location Data
CellInfo accesses device location information, including precise location when permission is granted, because Android restricts access to certain cellular network information and because location is required for CellInfo’s mapping and drive-testing features.
Location data may be used to:
- Display your current position on maps.
- Associate cellular measurements such as Cell ID, network type, signal strength and signal quality with the location where they were observed.
- Create signal coverage maps and route histories during Signal Mapping and Drive Testing.
- Include coordinates in user-generated logs or exports when the relevant logging or export feature is used.
When a user starts a mapping or monitoring session that continues while CellInfo is not visible, location may continue to be accessed while that session is running.
CellInfo does not operate a server that stores users’ precise GPS location or location history. Mapping and diagnostic location data is processed on the device unless the user explicitly exports or uploads it. CellInfo does not use tower coordinates to track or determine the user’s location. Tower-location information comes from OpenCellID or from a tower database deliberately imported by the user. The optional Nearby OpenCellID search uses the selected mast’s recorded coordinates, not the device’s current location, and sends those mast coordinates and MCC/MNC to OpenCellID using the user’s own API key. Saved nearby results are reused locally without a new request.
CellInfo includes third-party services including Google AdMob and Firebase. Google Mobile Ads may collect the device’s IP address, which can be used to estimate general location, as well as device identifiers, diagnostic information and interaction data. These third-party services process information according to their own privacy policies.
CellInfo does not intentionally provide precise GPS coordinates to advertising services for personalised advertising.
3. Device and Cellular Network Identifiers
The app accesses cellular identifiers including Cell ID, eNB/gNB ID, PCI, TAC, LAC, MCC, MNC and radio technology for local display and analysis. When an online lookup is explicitly requested, relevant identifiers may be sent to the selected lookup service. For the optional Nearby OpenCellID beta search, the selected mast coordinates and MCC/MNC are sent to OpenCellID using the user’s own API key; the feature does not use the device’s current location. When a user explicitly uploads a measurement to OpenCellID, the record may include MCC, MNC, TAC/LAC, Cell ID, radio type, signal strength, PCI, timestamp, GPS accuracy, speed and direction. CellInfo does not automatically transmit these detailed cellular identifiers in the current version.
- No IMEI Access: We do not knowingly access or store IMEI numbers.
- Random Identifiers: We use randomly generated UUIDs, rather than permanent device identifiers for analytics.
4. Third-Party Services
a) Google AdMob: Uses device information and the Google Advertising ID to deliver ads. Google Mobile Ads may collect the device’s IP address, which can be used to estimate general location, as well as device identifiers, diagnostic information and interaction data. AdMob mediation partners may also process data under their own policies.b) Google Firebase: CellInfo may use Firebase Authentication, Firestore, Analytics, Crashlytics, Remote Config, Cloud Messaging and related services. These services process account, diagnostic and usage information according to Google’s privacy policy.c) OpenCellID: CellInfo may use OpenCellID for explicit cellular lookups, the optional Nearby OpenCellID beta search and user-selected measurement contributions.d) Unwired Labs: Where enabled, CellInfo may use Unwired Labs for explicit cellular geolocation lookups. OpenCellID and Unwired Labs process information according to their own policies and terms. CellInfo does not control how these services retain or process information after submission.
5. Legal Basis for Processing (GDPR)
For users in the EEA and UK, local processing is used to provide the features requested by the user. Online lookups, the optional Nearby OpenCellID beta search, exports, sharing and measurement uploads are optional and are initiated by the user. The Nearby beta search uses the selected mast’s recorded coordinates and the user’s own OpenCellID API key, not the device’s current location. Any future automatic or background upload feature would require a separate, clear opt-in and would not be enabled by default. You can withdraw consent at any time within the app or your device settings.
6. Your Privacy Rights
Under GDPR and CCPA, you have the right to access, correct, or delete your personal data. To exercise these rights, contact us at the email address provided in Section 12.
7. Data Removal and Account Deletion
You may delete your CellInfo user record and Firebase Authentication account through the in-app “Delete Account” setting. This removes the CellInfo account record from Firebase/Firestore, deletes the authentication account, resets the app analytics identifier, clears selected account preferences and signs you out. Local logs, saved Mast Names, signal history, cached results, imported databases, API keys and exported files are separate device data and are not automatically deleted by account deletion; you can delete them in the app, remove the app or delete exported files. Some records submitted to third-party services may require a separate request to those services. You can also use our [Account Deletion Page](cellinfo.co.uk/account-deletion/) or email support for privacy and deletion requests.
8. Supporter Status (Coffee Count)
CellInfo maintains a non-personal aggregate “Coffee Supporter” count. This is not linked to personal identifiers stored by CellInfo.
9. Android Backup and Device Transfer
If Android Backup (Google One) is enabled, the OS may back up certain app preferences. CellInfo’s in-app settings backup may include configured OpenCellID and Unwired Labs API keys in the exported JSON, so treat the backup like a password and do not share it publicly. Mast Names, local signal history, cached nearby results and other selected app settings may also be included when the user exports them. Users control whether an export or backup is created, where it is saved and who it is shared with. The imported OpenCellID Room tower database is not included in the CellInfo settings backup. Users must re-import the original CSV, GZ or ZIP file after uninstalling the app or moving to another device. Android Backup behaviour is controlled partly by Android and the user’s Google account settings.
10. Data Retention
CellInfo stores local logs, Mast Names, saved tower information, signal history, cached lookup results and settings on the device until the user deletes them or removes the app. CellInfo does not control the retention of information submitted directly to OpenCellID or Unwired Labs. Those services manage submitted data according to their own policies and terms. Data collected by Google AdMob and Firebase is retained according to Google’s standard retention policies.
11. Security
API keys entered into CellInfo are stored locally on the device for use with the selected service. Users control whether to export or share Mast Names, logs, nearby results and other user-generated data. Users are responsible for protecting their API keys, exported settings backups and shared files. API keys should not be included in screenshots, source code, public repositories, support messages or publicly shared backup files. CellInfo does not intentionally send API keys to CellInfo-operated servers. We expect third-party service providers to use appropriate security measures to protect the information they process.
12. Contact Us
If you have questions about this Privacy Policy, please contact:
[email protected]