Device Mediet Inspector Privacy Policy

App: Device Mediet Inspector
Developer: VEB LAIF PP
Privacy contact: info@veblaif.online

Privacy Policy for Device Mediet Inspector

Developer: VEB LAIF PP
Privacy contact: info@veblaif.online

About this policy

This policy describes how Device Mediet Inspector accesses, uses, stores, and shares information. It reflects the current application source and supplied app description.

Information the app accesses

The app reads information exposed by Android to help you inspect your device. Depending on availability, this includes:

• Manufacturer, model, brand, product, board, processor architectures, processor count, hardware, and chipset details.
• Android version, API level, security patch, build identifiers, and build fingerprint.
• Total and available RAM, system memory usage, and internal storage capacity and available space.
• Display resolution, density, font scale, refresh rate, and supported display modes.
• Battery charge, charging status, power source, temperature, voltage, and battery technology.
• Hardware capabilities and Android feature support.
• Sensor names, vendors, types, and live readings, including sample values, accuracy, and timestamps.

Checking whether hardware such as a camera, GPS receiver, or fingerprint sensor is supported does not itself access photos, location, or fingerprints. Accessible information and sensor readings depend on your device and Android restrictions. The app does not estimate unavailable values.

How information is used

Information is processed on your device to display device details, monitor selected sensors, show a graph of the latest 60 samples of a sensor’s first component, create reports, and compare saved snapshots. Device information can be refreshed manually and updates every five seconds while the app is in the foreground. Sensor monitoring can be paused and resumes through the app’s monitoring controls; Android sensor listeners are suspended when the activity is paused.

You can name a report and save a snapshot containing device information and the latest samples from sensors monitored during the session. The app also stores your preference for decimal GB or binary GiB units. No account is required.

Collection and transmission

The inspected device-inspection and reporting features do not send device information, sensor readings, report names, or saved reports to the developer or an app-operated server. No analytics, crash-reporting, or advertising SDK was identified in the inspected application dependencies and source.

The Android manifest includes Internet and advertising ID permissions. No code that reads the advertising ID or displays advertisements was identified. A declared permission alone does not establish that information is collected.

The app also contains a WebView for a terms/privacy page. The current startup path opens the inspector directly and does not display that WebView. If that page is loaded, it can make a network request, which ordinarily exposes connection information such as an IP address to the destination. The inspected source does not establish the destination’s logging, cookies, or retention practices. JavaScript is enabled in that WebView.

Local storage and Android backup

Saved report names, snapshot dates, device facts, included sensor samples, and the unit preference are stored in the app’s private local storage. Live readings and graph history are held in memory unless samples are included in a saved report.

Android backup is enabled in the application configuration. Depending on Android’s behavior and your device and backup settings, app data may be included in system-managed backup or transfer. Such processing is controlled by Android and the applicable backup service, rather than by an app-operated backup service.

Sharing and third parties

Reports are shared only when you use a sharing control. The app prepares report text and a text file, then opens Android’s sharing chooser so you can select a recipient or another app. A shared report can include its name, date, device details, and captured sensor samples. Review its contents before sharing.

The report file is placed in the app’s private cache, and the selected receiving app is granted read access through Android’s sharing mechanism. Receiving apps and services handle shared information under their own privacy practices. Deleting a report in Device Mediet Inspector does not delete copies already shared.

The inspected source does not show automatic disclosure of inspection data to advertising or analytics providers. The app uses Android platform services and Kotlin/Compose libraries to provide its interface and device functions.

Security

The app uses Android’s private application storage for saved reports and settings. Its report-sharing provider is not publicly exported and provides read-only access through granted sharing permissions. These measures help limit access but cannot guarantee security.

The inspected code does not implement additional encryption for saved reports or cached export files. Because the core inspection features do not transmit information to a developer server, there is no app-server encryption-in-transit practice to describe for those features. Protection during sharing depends on the receiving app or service.

Retention and deletion

Saved snapshots remain in local app storage until you delete them or the app’s data is removed. You can delete individual reports or all saved reports within the app. The unit preference remains until changed or app data is cleared.

Each sharing action creates a cached text file. The inspected code does not set a fixed expiration or automatically remove that file when a saved report is deleted. You can remove local app data or cache through Android settings. Uninstalling the app generally removes its local application data; system backups and copies held by recipients may remain subject to their respective controls.

No server-side account or deletion-request feature was identified. The developer cannot delete copies held independently by recipients through the app’s local deletion controls.

Children’s privacy

The supplied information does not specify a target age group or establish whether the app is directed to children. The inspected app has no account registration or age-entry feature, and its core inspection data is processed locally as described above. Report-sharing controls can disclose information to recipients you choose.

Changes to this policy

This policy may be updated to reflect changes in the app’s features or data practices. Review the policy made available with the app for the current description of its handling of information.

Contact

Developer: VEB LAIF PP
Privacy questions: info@veblaif.online