Privacy & data
Privacy Policy
This policy explains how MQTT Nova Broker processes local broker data and how Google Mobile Ads processes limited data when advertising features are used.
Effective and last updated: August 2, 2026
01
Scope
This Privacy Policy applies to the MQTT Nova Broker Android application, package name com.mqttnova.broker, provided by Raschebbi ("we", "us", or "the developer").
The app turns an Android phone or tablet into an MQTT broker for devices on the user's local network. Core broker operation does not require a developer account and does not upload broker configuration or MQTT message content to a server operated by us.
02
Local broker data
To provide its core functionality, the app processes the following information locally on the Android device:
- broker settings, ports, authentication settings, alert rules, and app preferences;
- the device's local IP address and Wi-Fi network name;
- connected MQTT client identifiers and local network addresses;
- topics, subscriptions, connection events, and broker statistics; and
- MQTT message payloads while they are being routed between connected clients.
This information is used only to operate the broker, show its status, provide alerts, and preserve user-selected settings. App settings remain in app-local storage until the user clears the app's data or uninstalls the app. MQTT message content is routed in memory and is not intentionally retained as a permanent message archive.
03
Local network communication
The app accepts connections initiated by devices chosen by the user. MQTT clients may send identifiers, subscriptions, topics, and message content to the broker and may receive content routed by the broker. These transfers are controlled by the user and the connected clients; they are not sent to the developer.
The app offers both standard and TLS-enabled broker endpoints. Traffic sent through standard MQTT or WebSocket endpoints is not transport-encrypted. Users who require encrypted local traffic should use the MQTTS or secure WebSocket endpoints and configure their clients appropriately.
04
Google Mobile Ads
The app integrates the Google Mobile Ads SDK (AdMob) to load and display advertising, including interstitial and rewarded advertising. Google provides this third-party service and processes data under its own policies.
According to Google's Mobile Ads SDK disclosure, the SDK automatically collects and shares:
- Approximate location, estimated from the device's IP address;
- App interactions, such as app launches, taps, and ad or video interactions;
- Diagnostic information, such as app and SDK performance information; and
- Device or other identifiers, including the Android advertising ID, app set ID, and applicable device or account identifiers.
Google uses this data for advertising or marketing, analytics, and fraud prevention, security, and compliance. Data handled by the Google Mobile Ads SDK is encrypted in transit using TLS. Google's processing, retention, and deletion practices are governed by Google's policies.
More information is available in Google's Google Play data disclosure for Mobile Ads and Google Privacy Policy.
05
Permissions
Network access
Internet, network-state, Wi-Fi-state, and foreground-service permissions allow the app to operate the broker, accept client connections, display network status, run when placed in the background, and request ads.
Location permission for Wi-Fi name
On Android versions that restrict access to Wi-Fi information, the app may request precise location permission solely to read and display the connected Wi-Fi network name (SSID). The app does not use this permission to request GPS coordinates, and it does not send the SSID to the developer. Users may deny this optional permission; the Wi-Fi name may then be unavailable while core broker functionality remains available.
Notifications and device operation
Notification, wake-lock, and boot permissions support broker status notifications and user-configured background operation. These permissions are not used to create a developer-controlled user profile.
06
Choices and controls
Users can stop the broker at any time, disconnect clients, clear app-local data through Android settings, or uninstall the app. Android also provides controls to reset or delete the advertising ID. Google advertising and personalization controls are available through My Ad Center and the device's Google settings.
MQTT Nova Broker does not provide user accounts. We therefore do not hold account data that can be deleted through an account-deletion request. Questions about this policy can be sent to the contact address below.
07
Security and retention
We use the security controls provided by Android and use encrypted transport for data sent by the Google Mobile Ads SDK. No method of storage or network transmission is completely secure. Users are responsible for securing their local network, choosing strong broker credentials, and selecting TLS-enabled broker endpoints where appropriate.
Local settings are retained until changed, cleared, or removed by the user. Third-party data retention is determined by Google under its own policies.
08
Children
MQTT Nova Broker is a technical network utility and is not directed to children under 13 or the minimum age required in their country. We do not knowingly ask children to provide personal information directly to us.
09
Changes
We may update this policy when the app, its SDKs, or legal requirements change. The effective date at the top of this page will identify the latest version. Material changes will be reflected in the app's public disclosures where required.
10
Contact
For questions about this policy or the app's privacy practices, contact: