Bluetooth Mediet Explorer Privacy Policy

App: Bluetooth Mediet Explorer
Developer: VEB LAIF PP
Privacy contact: info@veblaif.online

Privacy Policy for Bluetooth Mediet Explorer

About this policy

This policy describes the data handling supported by the current application source and Store listing for Bluetooth Mediet Explorer. The developer is VEB LAIF PP. The privacy contact is info@veblaif.online.

Information accessed and stored

Bluetooth Mediet Explorer accesses Bluetooth information made available by Android to discover Bluetooth Classic devices, inspect nearby Bluetooth Low Energy (BLE) advertisements, display paired devices, and monitor received signal strength.

Depending on availability, this information includes device names, Bluetooth addresses or identifiers, transport type, device category, pairing status, signal strength, observation timestamps, advertised service UUIDs, manufacturer identifiers and data, service data, advertised transmission power, and whether an advertisement indicates that a device is connectable. Device names, identifiers, and advertisement contents may identify a device or contain information associated with its owner.

When you save a device, the app stores its observation together with any custom label and notes you enter. The app also automatically saves scan history when a scan stops, including the scan type, start time, elapsed duration, completion or stop status, and device snapshots. Your chosen scan duration is stored as a preference.

Live signal readings and their timestamps are held in memory for display. The app keeps up to 180 readings per observed device in the current results; the full live reading series is not included in saved device records or scan history.

Purposes

The app uses this information to display and organize device observations, search and filter results, show signal charts, retain saved labels and notes, and let you review earlier scan sessions. Signal strength is not an exact distance measurement. Paired devices may be out of range, and historical observations do not establish current proximity.

Permissions and your choices

On Android 12 and later, the app requests Nearby devices permissions for Bluetooth scanning and access to device information, including paired devices. On earlier supported Android versions, it requests fine location permission and checks whether Location services are enabled because Android requires them for Bluetooth discovery. The inspected code does not request geographic coordinates or background location. On Android 12 and later, the scan permission is declared as not used to derive physical location.

You can deny or revoke permissions through Android settings, although discovery and related features may then be unavailable. Scans start through your actions, can be stopped manually, and stop after the selected duration or when the app leaves the foreground. Revoking permissions does not delete previously saved records.

Local storage and collection by the developer

Saved devices, labels, notes, scan history, and preferences are stored in the app’s private Android SharedPreferences storage. The inspected Bluetooth features do not upload this information to the developer or operate an account system or app-managed cloud synchronization service.

Android backup is enabled in the application manifest. Depending on your device, Android version, and system settings, app data may therefore be included in system-managed backup or transfer and restored later. This is separate from the app’s own storage features.

Sharing, advertising, and third-party components

The inspected source contains no advertising, analytics, or crash-reporting SDK integration and no code that sells or sends Bluetooth observations to third parties. It uses Android platform services and AndroidX, Jetpack Compose, and Kotlin libraries to provide its functions.

The application manifest declares advertising ID permission, but the inspected code does not read or use the advertising ID or display advertisements. That permission alone does not establish advertising data collection.

If you choose Copy identifier, the app places the selected device identifier on the system clipboard. Access to clipboard contents is governed by Android and your actions, including pasting the identifier into another app.

Internet access and privacy-page component

The app declares Internet permission and includes a WebView component configured to open a terms/privacy page with JavaScript enabled. The current entry point opens the Bluetooth interface directly; the inspected user interface does not expose a control that opens that WebView. No network upload is implemented in the Bluetooth features.

If the WebView is activated, loading a remote page can disclose ordinary connection information, such as an IP address and browser request information, to its hosting service. The inspected source does not establish the page host’s storage, cookies, tracking, or retention practices, so this draft cannot describe them as verified practices.

Security

The app uses Android app-private storage and Android permission controls. The inspected code does not implement additional encryption for stored observations, labels, notes, or history. No Bluetooth-record upload is implemented, so encryption in transit for such an upload is not applicable to the inspected features. The source does not establish the security of system backups or any remote page. No storage or transmission method can be guaranteed completely secure.

Retention and deletion

The app does not implement an automatic expiration period for saved records or scan history. These records remain in app storage until you remove them or clear the app’s data.

You can remove a saved device, including its saved label and notes, delete an individual scan session, or clear all scan history. Saved records and scan history are separate: clearing history preserves saved devices, labels, and notes, and removing a saved device does not remove its historical snapshots. Removing a saved record also leaves Android’s system pairing unchanged.

You can clear the app’s storage through Android settings to remove its local records and preferences. System backups, restored copies, and identifiers copied to the clipboard or another app are controlled separately and are not erased by the app’s record-deletion controls.

For privacy questions or deletion assistance, contact info@veblaif.online. No server-side deletion request feature is implemented in the inspected app, and the developer cannot directly remove records stored only on your device. The handling and retention of any information you send by email are not established by the inspected application.

Children’s privacy

The supplied information does not specify an intended age range. The inspected app has no accounts, age-verification feature, or child-specific data collection flow. Bluetooth observations and user-entered notes are handled as described above regardless of the user’s age. Avoid entering unnecessary personal information about children or other people in labels or notes.

Changes to this policy

This policy should be updated when the app’s permissions, storage, networking, third-party integrations, or other data practices change. Review the policy accompanying the version you use for current information.

Contact

App: Bluetooth Mediet Explorer
Developer: VEB LAIF PP
Privacy contact: info@veblaif.online