Device Info | Privacy Policy

1. Scope

Device Info is a native Android application that shows device hardware, software, battery, memory, network, sensor, installed-app, widget, diagnostics, and export information. This policy applies to the Android app and this support website.

2. Information used by the app

The app reads device and app-related information to display it to the user inside the app. Depending on the screen or feature being used, this can include device model, manufacturer, Android version, build details, display metrics, battery state, network state, available sensors, RAM and storage details, installed app inventory, 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. The app is not designed to sell personal information.

3. Firebase services

Device Info uses Firebase Analytics, Firebase Crashlytics, and Firebase Remote Config. These services are provided by Google and may process technical data needed to operate those services.

Firebase Analytics

Used to understand app usage, feature adoption, and overall product health. Analytics may process app instance identifiers, app interaction events, and related technical metadata.

Firebase Crashlytics

Used to detect crashes, diagnose failures, and improve stability. Crashlytics may process crash stack traces, app state at the time of a crash, device metadata, and installation-related identifiers.

Firebase Remote Config

Used to manage app behavior, update policy, and selected security or product controls without requiring an app update. Remote Config may process country, language, time zone, platform and OS version, app identifiers, and installation identifiers to deliver the right configuration values.

Firebase data handling and retention may vary by service and project settings. Firebase documentation currently states that Crashlytics retains crash data for a limited period and that installation identifiers may remain until deleted, after which removal from live and backup systems can take time.

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.

`ACCESS_NETWORK_STATE`

Used to detect active network connectivity and transport type so the app can show network status, run network-related diagnostics, and keep dashboard or widget summaries current.

`ACCESS_WIFI_STATE`

Used to read Wi-Fi connection details needed for network information screens and diagnostics, such as current Wi-Fi state and supported connection details available to the app.

`INTERNET`

Used for Firebase Analytics, Crashlytics, and Remote Config communication, and to reach online services required for diagnostics or app support flows.

`READ_PHONE_STATE`

Used only for device and telephony-related status information that may be shown in system or network details on supported devices, such as carrier or service state information. It is not used to place calls or read contacts or messages.

`CAMERA`

Used for flashlight or torch diagnostics that rely on camera hardware access. The permission supports the hardware test flow and is not intended for capturing photos or videos.

`RECORD_AUDIO`

Used for the microphone diagnostic to show live audio level feedback while the user runs the test. Audio is not intended to be stored as user content by this feature.

`VIBRATE`

Used for vibration diagnostics and haptic verification so users can confirm that device vibration hardware is working correctly.

`QUERY_ALL_PACKAGES`

Used for the app's installed-app inventory feature so users can browse app details across user and supported system packages, apply filters, search by package or app name, review app source information, and surface risk-related visibility for supported packages. This permission relates to a visible, user-facing app management and device information feature.

`ACTIVITY_RECOGNITION`

Used for Sensor Lab behavior tied to step-counter style sensors on supported devices. This supports session-relative movement or sensor experiences and is not intended for background fitness profiling.

5. Installed apps visibility and risk analysis

If the installed-app inventory feature is used, Device Info may access package names, app labels, icons, version information, install or update timestamps, source type, and other app metadata available through Android package APIs. This information is used to render the Apps tab and related summaries.

The app may also apply risk-oriented rules to supported packages, including source-aware heuristics and remotely delivered package signals, so potentially unsafe apps can be surfaced to the user inside the Apps experience.

App inventory data is treated as sensitive by Google Play policy. It should be used only for the user-facing inventory feature described in the app listing, not for advertising or resale.

6. Diagnostics, Sensor Lab, and local storage

The app may store local diagnostic state on the device so pass, fail, and in-progress test results can remain visible after app restarts. Sensor Lab may also maintain short-lived in-app history needed for live charts or recent sensor activity views. This local state supports the user experience and is not intended to act as a hidden profile of the user.

7. PDF exports, widgets, and updates

When a user chooses to export dashboard sections to PDF, the exported document contains the device information selected for that report. Exported files are user-initiated outputs created for the user's own viewing or sharing.

Home-screen widgets use app data to render RAM and device summary information on the device. The app may also check remotely delivered update policy and Play-provided update availability so recommended or required upgrades can be shown accurately.

8. Data sharing

Device Info may share technical and service-related data with Google Firebase for the purposes described above. Outside of these service providers and legal or security obligations, the app is not intended to sell personal information.

9. Security and retention

Reasonable steps are taken to limit data access to what is necessary for app features, debugging, and service operation. Network communication with Firebase services is intended to occur over secure HTTPS connections.

Locally stored diagnostic state can generally be removed by clearing the app's storage or uninstalling the app from the device. Retention and deletion of Firebase-processed data is governed by Firebase and Google service behavior, documentation, and project configuration.

10. 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.

11. Contact

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

Suryansh Prajapati

itssuryanshprajapati@gmail.com