Last updated: 2026-08-03
What WebDebugX collects, what it does not, and why. The short version: the pages you inspect are not sent to us, and there is no account to create.
What you inspect is between your computer and your device.
The contents of the pages you debug are not transmitted to us. The debugging session runs between the WebDebugX application on your computer and the device connected to it, or the browser you pointed it at.
DOM contents, console output, network requests, script sources, cookies and storage values you view in the inspector are handled locally and are not uploaded.
Version checks, basic usage events and activation codes. No account, no payment details.
Version and update checks. The application asks our service for current version information so it can tell you that an update exists or that your version is below the minimum supported one.
Basic usage events. The application reports coarse events so we can understand which parts of the product are used and diagnose failures. These are about the application, not about the pages you inspect.
A device identifier. An anonymous identifier derived from your hardware, used to count distinct installations and to detect abuse. It is not linked to a name, an email address or a payment method.
Language preference. Your chosen interface language, so it persists across sessions. This is stored on your machine.
Activation codes. Using the Software requires a free activation code. When you enter one, the application sends that code to our licence service so it can be checked and so the resulting entitlement can be recorded against this installation, together with the device identifier described above. A code has a validity period, so this exchange happens again when you enter a replacement.
There is no account, so we hold no username, no password and no email address for you unless you send us one by contacting support. A code is not linked to a person; it is linked to the installation that redeemed it.
To deliver updates, understand usage and keep the app working.
To deliver update and compatibility information; to understand which features are used; to diagnose faults and improve the product; and to respond to your support requests.
We do not sell your data.
We do not sell personal data. We share it only with service providers that operate our infrastructure on our behalf, and only as needed to provide the service, or where required by law.
Diagnostic and usage events are kept for a limited window.
Diagnostic and usage events are retained for a limited period and then deleted. Aggregated counts that cannot identify an installation may be kept longer.
You can ask what we hold and ask us to delete it.
Because there is no account, we usually cannot connect the data we hold to you as an individual. If you believe we hold data relating to you, contact us and we will help you locate and delete it where we can identify it.
Not intended for children.
WebDebugX is a developer tool and is not directed at children. We do not knowingly collect personal data from children.
We will update the date at the top when this changes.
When this policy changes we will revise the date shown above. Questions can be sent to the contact address published on this website.