In short: MQTT Connect is secure and private by default. It doesn't have a server — there's no account, no analytics, and no cloud sync. Your broker profiles, clients, credentials and certificates are encrypted and stored only on your device. The only network traffic the app generates is the MQTT connection a client makes to the broker it's set up to use.
1. What we collect
We — the developer of MQTT Connect — collect nothing. The app does not include analytics, crash-reporting, advertising, or telemetry SDKs of any kind, and it does not communicate with any server operated by us. We have no account system, so we never see your name, email, device identifier, or usage activity. Nothing about how you use the app is transmitted anywhere for us to receive.
2. What's stored on your device
To function, MQTT Connect stores the following information locally, on your device only:
- Broker profiles — a broker's domain/host, port, and transport (TCP/TLS/WS/WSS) that you save once and reuse. Creating a client is just picking a saved broker; its connection details fill in automatically from there.
- Clients — the MQTT clients you create, each linked to a broker profile, with its own client ID, MQTT protocol version, and connection options (keep-alive, clean session, timeouts, etc.).
- Credentials — usernames and passwords for a client's broker authentication, encrypted at rest using the operating system's secure storage (the iOS/Android keychain) combined with encrypted local storage.
- Certificates & keys — CA certificates, client certificates, and private keys you import for a client's TLS/mTLS connection (see §4).
- Topics & message history — subscribed topics, saved topic suggestions, publish snippets, and a rolling buffer of recently sent/received messages per client, kept only for your own reference within the app.
- App preferences — settings like Face ID lock, auto-lock timeout, and message buffer size.
All of the above lives in encrypted local storage and the platform keychain on your device. None of it is synced to a cloud service, backed up to a server we operate, or accessible to us. Uninstalling the app removes it.
3. Network & broker traffic
The only network connections MQTT Connect initiates are the ones you configure: each client connects to the host and port defined by the broker profile it's linked to, using the transport and credentials you supply for that client. Any data you publish or subscribe to is sent directly between your device and that broker — it does not pass through us or any server we control. The security and retention practices of that data are governed by the operator of the broker you connect to, not by this policy.
4. Certificates & private keys
When you import a CA certificate, client certificate, private key, or a
.p12 bundle — whether by picking a file, pasting PEM text, or
unlocking a passphrase-protected key — the file is read once through the
system file picker and its contents are written directly into the device
keychain. The original file is never copied elsewhere by the app, never
leaves your device, and is excluded from the client export feature described
below.
5. Export & deletion
Settings includes an Export clients (no secrets) option, which lets you export your client configuration (the linked broker's host/port/transport, topic lists, etc.) without passwords, private keys, or certificates — useful for moving clients between devices without exposing credentials.
Settings also includes an Erase all data option, which permanently deletes every broker profile, client, credential, certificate, and message stored by the app on that device. This action is irreversible and, because we hold no copy of your data, cannot be undone by us either.
6. Biometrics & device locks
You may enable Face ID / biometric authentication to open the app, an auto-lock timer, and an option to hide message payloads while the app is in the background (e.g. in the OS app switcher). Biometric data itself is processed entirely by your device's operating system — the app never receives or stores your biometric data; it only receives a yes/no authentication result from the OS.
7. Third parties & data sharing
We do not sell, rent, or share any data, because we do not collect or have access to any. The app does not integrate any third-party analytics, advertising, or data-broker SDKs. The MQTT broker(s) you configure are third-party services you choose to connect to, and are outside our control — review their own privacy practices separately.
8. Children's privacy
MQTT Connect is a technical tool intended for developers and operators configuring MQTT infrastructure, and is not directed at children. Since we collect no data from any user, we do not knowingly collect data from children either.
9. Changes to this policy
If this policy changes, we'll update the "Last updated" date at the top of this page and, for material changes, note it in the app's release notes. Continued use of the app after a change constitutes acceptance of the revised policy.
10. Contact
Questions about this policy or the app's data handling can be sent to shreyansh@shrynshjn.com.