Device Info

1. Scope

Device Info is a native Android application that shows device hardware, software, battery, memory, thermal, network, camera, sensor, installed-app, widget, diagnostics, Wi-Fi analyzer, floating monitor, and export information. This policy applies to the Android app and this support website. App version v6.0.0 supports Android 11 and newer.

2. Information used by the app

The app reads device and app-related information through Android system APIs so it can display that information to the user. Depending on the feature, this can include device model and manufacturer, Android and build details, CPU state, RAM and storage, display metrics, battery and thermal state, local network addresses, current and nearby Wi-Fi network details, camera capabilities, available sensors, fingerprint hardware readiness, installed-app metadata, overlay monitor settings, and diagnostics status.

Most of this information is used locally on the device to render UI, widgets, diagnostics results, app risk visibility, and optional PDF exports initiated by the user. Device Info does not create user accounts, contain advertising, request background location, collect GPS coordinates, or use the device information it displays to build an advertising profile. Fine-location permission is requested only for the Wi-Fi Analyzer because Android gates nearby Wi-Fi scan results behind that permission on many devices.

The app's own code does not upload the installed package list, individual package names, nearby Wi-Fi scan results, SSIDs, BSSIDs, sensor readings, microphone samples, fingerprint data, overlay metric readings, or generated PDF contents to Firebase.

3. Firebase services

Device Info includes Google Analytics for Firebase, Firebase Remote Config, and Firebase Crashlytics in release builds. These Google services may process technical data needed to provide analytics, configuration delivery, and crash reporting.

Google's current Firebase documentation states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal, while Remote Config keeps Firebase installation IDs until deletion is requested. See Privacy and Security in Firebase for Google's current service details, retention statements, and processing locations.

4. Permissions and why they are used

Device Info declares only permissions intended to support visible app features. If a permission is not granted, the related feature or diagnostic may be limited or unavailable.

5. Installed apps visibility and risk analysis

Device Info accesses package names, app labels, icons, versions, app size, install or update timestamps, install source, requested and granted permission metadata, and other app details available through Android package APIs. This information is used to render the Apps tab, app details, report sections, and the security summary.

Risk analysis is performed locally. Depending on the app source, Device Info may check factual signals such as whether another app currently has an accessibility service, notification listener, or device-admin role enabled; whether sensitive permissions are granted; and whether a package and optional certificate hash matches a curated Remote Config allowlist or blocklist.

Heuristic findings describe capabilities and risk indicators, not proof that an app is malware. Only curated blocklist data can apply a malicious-app label. System apps are not flagged by the local heuristic scanner.

Google Play treats installed-app inventory as sensitive data. Device Info uses broad package visibility only for its visible app-inventory and device-security features. It does not upload or sell the inventory, and does not share it for advertising or analytics monetization. See Google's broad package visibility policy.

6. Diagnostics, Sensor Lab, microphone, NFC, and biometrics

Hardware Tests includes user-initiated visual, camera, audio, haptic, flashlight, button, NFC, Bluetooth, and connectivity tests. Pass, fail, running, and pending status is stored in local app preferences so results remain visible after a restart.

Sensor Lab registers supported Android sensors while the feature is active and keeps a limited in-memory history for live charts. Step-counter values are presented relative to the current session. Sensor Lab is not designed for background movement tracking.

The microphone test reads audio amplitude for live feedback and does not save audio recordings. The fingerprint test uses Android's protected biometric prompt; fingerprint templates remain under operating-system control and are never exposed to Device Info.

7. Wi-Fi Analyzer and Floating Monitor

Wi-Fi Analyzer scans nearby access points while the screen is open and displays SSID, BSSID, vendor, signal strength, band, channel, channel width, security type, estimated distance, current-connection details, and channel recommendations. Scan results are used for the on-screen tool and are not uploaded by the app's own code. The bundled OUI vendor lookup asset is stored in the app and does not require a runtime network lookup.

Wi-Fi scanning may require both permission and the device's system Location toggle to be enabled because Android and some device manufacturers gate scan results that way. Device Info does not request background location, does not use GPS, and does not keep a location history.

Floating Monitor is started by the user and shows selected device metrics, such as FPS, RAM, battery, network throughput, and storage, in draggable overlay tiles. It uses a foreground service while active, stores tile settings and positions locally, and stops when the user turns monitoring off or uses the service notification stop action.

8. PDF exports, widgets, updates, and reviews

PDF export is user initiated. The user selects report sections and chooses the destination through Android's system document picker. The resulting PDF may include device, network, installed-app, security, sensor, camera, and diagnostics information, so users should review a report before sharing it. The app does not upload the PDF.

Six home-screen widgets display RAM, device summary, battery, storage, CPU and temperature, or network information. Widget values remain on the device and refresh automatically, on user request, or when the app resumes.

Remote Config and Google Play APIs are used to evaluate recommended or required app updates. The app also keeps local counters and timestamps to avoid showing Play's in-app review flow too frequently. Google controls whether the review dialog appears, and Device Info does not receive the user's rating or review text from that flow.

9. Local storage and Android backup

The app stores diagnostic status, in-app review eligibility counters, and Floating Monitor settings such as enabled metrics, tile positions, size, theme, and transparency in private local preferences. Sensor chart history and Wi-Fi scan results are session-oriented. Saved PDF reports live in the location selected by the user and are managed separately from app storage.

Android backup and device-transfer support is enabled. Depending on Android version, device settings, and the user's backup configuration, app-managed preferences may be eligible for cloud backup or device-to-device transfer. Google or the device manufacturer controls that backup service. Clearing app storage or uninstalling the app removes local app data, but a backup may later restore eligible preferences.

10. Sharing, advertising, and sale of data

Technical service data may be processed by Google through Analytics, Firebase Crashlytics, Firebase Remote Config, Google Play updates, and Google Play in-app review for the purposes described above. Data may also be disclosed when required by law or necessary to protect users, the developer, or the public.

Device Info contains no advertising SDK and the manifest explicitly removes Google advertising-ID and AdServices advertising-attribution permissions. The developer does not sell personal information, installed-app inventory, Wi-Fi scan results, or overlay metric readings.

11. Security and retention

Reasonable steps are taken to limit data access to what is necessary for app features, debugging, and service operation. Firebase documents encryption in transit using HTTPS and encryption at rest for Crashlytics data.

Local diagnostic, review, and Floating Monitor settings remain until they are overwritten, cleared with app storage, or removed by uninstalling the app, subject to any Android backup restoration. Exported PDFs remain until the user deletes them from the chosen storage location. Google-service retention follows Google's documentation and project configuration.

12. User choices and deletion

Camera, microphone, activity-recognition, fine-location, nearby Wi-Fi, notification, and overlay access can be denied or revoked through Android settings; the related test, Sensor Lab, Wi-Fi Analyzer, notification, or Floating Monitor feature may then be limited or unavailable. The system biometric prompt can be canceled at any time. Users can stop Floating Monitor from the app or service notification, clear local app data or uninstall Device Info to remove app-managed local state, manage Android backups through device or Google account settings, and delete exported PDFs through their file manager.

13. Policy updates

This policy may be updated when app features, permissions, third-party services, or regulatory expectations change. The latest version will be published on this page with a revised update date.

14. Contact

If you have privacy, data handling, or permission questions, contact:

Suryansh Prajapati

itssuryanshprajapati@gmail.com