MQTT Client

Privacy Policy

Last Updated: October 16, 2026 | Document Version: 1.2

Notice: This is an English translation of the original Russian document. In case of any discrepancies between the Russian and English versions, the Russian version shall prevail.

1. General Provisions

This Privacy Policy is developed in accordance with the Federal Law of the Russian Federation No. 152-FZ dated July 27, 2006 "On Personal Data" and other regulatory legal acts of the Russian Federation in the field of personal data and applies to relationships arising from the use of the mobile application "MQTT Client (MQTT Dashboard Client)" (hereinafter referred to as the "Application").

This Privacy Policy applies to all Users of the Application regardless of their location. Processing of personal data is carried out in accordance with:

Federal Law of the Russian Federation No. 152-FZ "On Personal Data" (for users from the Russian Federation)
General Data Protection Regulation (GDPR) (for users from the European Union)
California Consumer Privacy Act (CCPA) (for users from California, USA)

This Privacy Policy applies exclusively to the Application and does not extend to other applications, websites, products or services of third parties, even if they are accessible via links from the Application.

2. Subject of Personal Data

The subject of personal data is a natural person using the Application (hereinafter referred to as the "User").

3. Personal Data Collected and Processed

3.1. Personal data provided by the User:

Email address (when contacting customer support)
Username (when contacting customer support)

3.2. Personal data collected automatically:

Unique device identifiers
Device type and its characteristics
Operating system version
IP address
Information about application usage sessions
Data about completed purchases (transaction identifiers)

To verify and cancel a subscription, the Application sends the purchase identifier, the subscription identifier and the Application package name to the Operator's server; the server also receives the IP address of the connection. The server passes this data to RuStore only to verify or cancel the subscription and does not store it.

3.3. Data collected through analytics services:

Application usage statistics
Frequency of use of Application functions
Information about application failures
Approximate location determined from the IP address

Collection of analytics and crash information starts only after the User gives consent in the Application and stops when the consent is withdrawn.

3.4. Data for advertising networks:

Advertising identifier (GAID for Android)
IP address (for geotargeting advertisements)
Device type and OS version
Information about interaction with advertising materials

3.5. Data the User sends to their own MQTT broker:

Broker addresses, credentials for connecting to them, messages and dashboard settings are stored on the User's device and are sent only to the brokers specified by the User.

When the "Phone as a device" feature is enabled, the Application sends to the broker chosen by the User only the device state data selected by the User:

Battery level and state
Screen and power saving state
Sound mode and Do Not Disturb mode
Network connection type
Free storage
Next alarm time
Device location (if the User has enabled sending it and allowed the Application to access location)
Device model and manufacturer, its name and an identifier created by the Application

The Operator does not receive or store this data. Its storage and processing are determined by the owner of the broker.

4. Purposes of Collection and Processing of Personal Data

Personal data is processed for the following purposes:

Providing and improving Application functionality
Processing and fulfilling obligations under the contract (public offer)
Providing technical support to Users
Conducting statistical research
Preventing violations of Application usage terms
Sending informational messages (with User consent)

5. Legal Basis for Processing Personal Data

The legal basis for processing personal data are:

User consent to process their personal data (para. 1 art. 6 of Federal Law No. 152-FZ)
Necessity to perform a contract to which the User is a party or beneficiary or guarantor (para. 3 art. 6 of Federal Law No. 152-FZ)

6. Transfer of Personal Data to Third Parties

Personal data may be transferred to the following third parties:

RuStore Pay (Sberbank PJSC) — for processing subscription payments
Yandex Advertising Network (Yandex LLC) and its mediation partners, including Google AdMob (Google LLC) — for displaying ads and monetization
Firebase Analytics (Google LLC) — for analyzing Application usage
Firebase Crashlytics and Firebase Performance Monitoring (Google LLC) — for collecting information about Application failures and performance
Firebase Cloud Messaging and Firebase Remote Config (Google LLC) — for delivering notifications and Application settings
Yandex AppMetrica (Yandex LLC) — for analyzing Application usage
OpenFreeMap — for loading map data; when a map is shown, the server receives the device's IP address

Important: Firebase services and Yandex AppMetrica may transfer data to servers outside the Russian Federation, including countries that do not provide an adequate level of protection of personal data. By using the Application, the User consents to such transfer in accordance with the terms of this Privacy Policy.

For users from the European Union and California (USA), additional guarantees apply in accordance with GDPR and CCPA respectively. Advertising networks may collect device data, IP address, advertising identifiers (GAID, OAID) for personalizing advertising materials. The User can opt out of personalized advertising by resetting or deleting the advertising ID in the Android settings.

7. Processing Period and Storage of Personal Data

Personal data is processed and stored for the entire period of Application use by the User, as well as for the period necessary to comply with the requirements of the legislation of the Russian Federation.

Upon expiration of the storage period, personal data is subject to destruction or anonymization.

8. Rights of the Subject of Personal Data

The User has the right:

To receive information regarding the processing of their personal data
To demand clarification, blocking or destruction of incomplete, inaccurate or outdated personal data
To withdraw their consent to the processing of personal data
To become familiar with the personal data processed by the Operator
To demand cessation of processing of personal data
For users from the EU: Right to data portability
For users from the EU: Right to be forgotten
For users from California: Right to opt-out from sale of data
To appeal the Operator's actions to the authorized body for the protection of the rights of personal data subjects

To exercise their rights, the User can send a request to mqtt.client.feedback@gmail.com. The request must contain sufficient information to identify the User and clearly describe the requested rights.

9. Operator's Obligations

The Operator is obliged:

To process personal data in accordance with the legislation of the Russian Federation
To take necessary legal, organizational and technical measures to protect personal data
To provide information about the Operator, purposes and methods of processing personal data when collecting personal data
To ensure confidentiality of personal data
To carry out processing of personal data exclusively for the purposes specified in this Policy

10. Contact Information

For questions related to the processing of personal data, the User can contact:

Individual Entrepreneur: Evgeny Valerievich Doikov
TIN: 263111454680
PSRNIP: 326237500086973
Address: Krasnodar, Krasnodar Krai, Russia
Email for personal data requests: mqtt.client.feedback@gmail.com

11. Final Provisions

This Privacy Policy is governed by the legislation of the Russian Federation.

All disputes arising from this Policy shall be resolved in court in accordance with the legislation of the Russian Federation.

The Operator has the right to make changes to this Privacy Policy. When making changes, the date of the last update is indicated in the current edition. The new edition of the Policy comes into force from the moment of its posting, unless otherwise provided by the new edition of the Policy.

Continued use of the Application after changes have been made means the User's consent with the current edition of the Privacy Policy.