Privacy Policy

Bluetooth Codec Monitor

Effective Date: August 19, 2026

Before publishing, replace the two highlighted fields above and remove this note.

This Privacy Policy describes what information the Bluetooth Codec Monitor application processes, the purposes for which it is used, where it is stored, and what controls are available to the user.

Purpose of the Application

Bluetooth Codec Monitor displays information about the active Bluetooth audio connection, including the profile, codec, sample rate, bit depth, bitrate, and number of channels.

The application also provides compatible controls for Bluetooth codec parameters, absolute volume mode, background monitoring, and the widget.

Information Processed Locally

The application locally processes the name of the connected Bluetooth device, connection profile, codec in use, sample rate, bit depth, bitrate, number of channels, absolute volume status, and the time when parameters were changed.

This information is used to display the current status, persistent notification, widget, and change history. The history contains no more than 250 entries and is stored only in the device’s internal storage.

The port number and six-digit wireless debugging pairing code are used only for local pairing with ADB on the same device. The pairing code is not stored after the operation is completed. To authenticate the local ADB connection, the application generates its own cryptographic key pair and stores it in an internal area excluded from backups.

The developer does not receive Bluetooth reports, codec history, pairing codes, or user settings and does not transmit them to the developer’s own servers.

BLUETOOTH CODEC MONITOR | PRIVACY POLICY

Advertising and Third-Party SDK

The application uses the Yandex Mobile Ads SDK to display banner advertisements and app open advertisements.

The Yandex Mobile Ads SDK may collect and transmit device identifiers, including the Android Advertising ID, if access to it is permitted by the system. This information is used to display and personalize advertisements and to measure their effectiveness. Data is transmitted in encrypted form using HTTPS/TLS.

Detailed terms regarding the processing of advertising data are published in the “Yandex Privacy Policy.”

Users can limit ad personalization or delete the advertising identifier in the Android system settings. The availability of specific settings depends on the Android version and Google Play services installed on the device.

Permissions Used

BLUETOOTH_CONNECT — used to obtain information about the connected Bluetooth device and manage compatible connection parameters.

DUMP — used to read the system Bluetooth report after the user voluntarily completes a one-time setup through wireless debugging.

WRITE_SECURE_SETTINGS — used to modify supported system settings, including the absolute volume mode.

INTERNET — used to load and display advertisements through the Yandex Mobile Ads SDK.

POST_NOTIFICATIONS and FOREGROUND_SERVICE — used for background monitoring of Bluetooth parameters and for displaying a persistent notification.

ACCESS_LOCAL_NETWORK — used to discover and access the local wireless debugging service on the device; the application does not establish remote connections to external ADB devices.

Data Storage and Deletion

The local history can be deleted using the “Clear History” command within the application.

All other locally stored data is deleted when the application data is cleared in the Android settings or when the application is uninstalled. Bluetooth Codec Monitor does not create user accounts.

The retention periods and deletion procedures for information processed by the advertising SDK are determined by Yandex’s policies. For questions related to such data, users may use the contact methods specified in Yandex’s privacy policy or contact the developer.

BLUETOOTH CODEC MONITOR | PRIVACY POLICY

Sharing Data with Third Parties

The developer does not sell user data.

Locally stored information about Bluetooth devices and codecs is not shared with third parties. Device identifiers may be transmitted to Yandex solely in connection with loading, displaying, personalizing, and measuring advertisements.

Security

Local data is stored in Android’s internal application storage.

Application data backup is disabled. Network traffic generated by the advertising SDK is transmitted over a secure HTTPS/TLS connection.

Despite the measures taken, no method of data storage or transmission can guarantee absolute security.

Children

The application is intended for a general audience and is not specifically directed at children under the age of 13.

If the developer becomes aware of the improper processing of a child’s data, the developer will take reasonable measures to stop such processing.

Changes to This Policy

This Privacy Policy may be updated when the application’s features, the SDKs used, or applicable requirements change.

The effective date of the current version is indicated at the beginning of this document.