Privacy Policy
TestMQTT needs no account. To run and improve the site we log page views and actions in the online MQTT client — but never your MQTT username, password or message contents.
Last updated:
What we log
When a person (not a bot) uses the site, our server records:
- Page views: the page address, its language and type (for example an article, a tool or the playground), the page you came from, your browser language and screen width.
- Playground activity: connecting, test connections, disconnecting, connection errors, subscribing, unsubscribing and publishing. For these we store the broker address (protocol, host, port and path), the MQTT version, the client ID, topic names, QoS and retain flags, message size, whether it worked, how long it took and any error message.
- Technical data sent with every request: your IP address, your browser’s user agent and the time.
- Two random identifiers created in your browser: a visitor ID in localStorage (tmq_vid) and an ID for the current tab in sessionStorage (tmq_sid). They are not cookies and are not linked to your name or email.
What we never store
- The username and password you enter for an MQTT broker. The logging API has no field for them, and the server removes anything that looks like a credential, including user:password@ inside broker URLs.
- The contents (payload) of messages you publish or receive, and the content of last-will messages — only their size.
- Query strings of broker URLs, which may contain tokens.
- Account data: there are no accounts on TestMQTT.
TCP and TLS connections through our server
Browsers cannot open raw TCP sockets, so mqtt:// and mqtts:// connections are relayed through the TestMQTT server. For those connections your username, password and messages pass through the server’s memory only while the connection is open, so it can talk to the broker. They are never written to disk, to a database or to log files. WebSocket (ws:// and wss://) connections go directly from your browser to the broker.
Google Analytics
The site also uses Google Analytics 4, a service by Google, to measure visits. Google Analytics sets cookies and processes your IP address under Google’s own privacy policy. You can block it with your browser’s tracking protection, a content blocker or Google’s opt-out add-on.
Why we use this data
- To keep the service running and secure, and to prevent abuse such as attacks through the TCP bridge.
- To find and fix errors, for example brokers that often fail to connect.
- To understand which pages, languages, tools and brokers are used, so we can improve them.
The legal basis is our legitimate interest in operating and securing a free service (Art. 6(1)(f) GDPR; Art. 5(2)(f) of the Turkish Personal Data Protection Law, KVKK).
Storage and retention
The logs are stored in our own database. We keep log records only as long as we need them for the purposes above, and then delete them.
Public brokers
Public brokers such as HiveMQ, EMQX or test.mosquitto.org are run by other organisations. Anything you publish to them can be read by anyone, and their own privacy policies apply. Never send personal data or credentials through a public broker.
Your choices and rights
You can clear the TestMQTT identifiers at any time by clearing this site’s data in your browser. You have the right to ask what data we hold about you and to have it corrected or deleted. Email support@testmqtt.com with your IP address and the approximate time of your visit (or your visitor ID from localStorage).
Changes and contact
If we change what we log, we will update this page and the date at the top. Questions about privacy: support@testmqtt.com.