DebugtWhat leaves your machine, in full.
Last changed 12 October 2026.
A draft. The seller is not named yet (PUBLIC_LEGAL_NAME), and this has not been read by a lawyer.
Debugt is a tool for looking at your own services, and what it sees is yours. This page lists everything that is sent anywhere, by the extension and by this website, and what is kept. If something is not on this page, it is not sent.
What Debugt does not collect
- Your code, your file paths, and the names of your services and projects.
- Your requests and responses, their headers and their bodies.
- Traces, hops and execution recordings.
- Usage data, crash reports or analytics of any kind. There is no telemetry.
All of that is kept in a folder on your own machine (~/.debugt), outside your repositories, and is never uploaded. Credentials — Authorization, Cookie, API keys and the like — are redacted before a hop is recorded even there.
On the Free plan
Nothing is sent. There is no account, no activation and no check: the extension works with no network at all.
With a license
The extension calls the license server to activate a license and to renew it once a day. These calls carry the following, and nothing else:
| Sent | When | Why |
|---|---|---|
| Your license key | When you activate, once | To find your license |
| A hash of your machine's id | When you activate, at each daily renewal, and when you remove a machine | To count the 3 machines a license is good on. The id itself is not sent, and the hash cannot be turned back into it |
| The extension's version | When you activate, and at each renewal | To know which versions are in use |
| Your current license token | At each renewal, and when you remove a machine | To show that this machine was activated |
As with any request over the internet, the server also sees the IP address it came from. It is used to limit repeated attempts at guessing a key, and appears in short-lived server logs.
What is kept about a customer
- Your email address, and the id Paddle knows you by.
- Your license: its plan, what it is paid through, and whether it is cancelled. The key itself is kept only as a hash — it cannot be read back, by us or by anyone who got hold of the database.
- For each machine it is active on: the hash of its id, the extension's version, and when it was activated and last renewed.
- A record of what happened to the license — made, activated, removed from a machine, renewed, cancelled — kept for thirteen months.
Payments
Debugt Pro is sold through Paddle, which acts as the reseller: you pay Paddle, and Paddle's own privacy policy covers what it collects to take the payment and work out tax. Debugt never receives your card details. Paddle tells us that a subscription began, was renewed, cancelled or refunded, and your email address so that the key can be sent.
Your license key is emailed to you through an email delivery service, which handles your address and the message in order to deliver it. We do not send marketing email.
This website
These pages load no analytics, trackers or fonts from anyone else, and set no cookies until you sign in to your account: that sets one, which keeps you signed in for thirty days and does nothing else. The one exception is the checkout: pressing Buy loads Paddle's checkout from paddle.com, which may set cookies of its own to take the payment and prevent fraud.
Your choices
- To stop the license calls, remove the license from the machine under Settings → License. Debugt goes on working, on the Free plan.
- To see, correct or delete what is kept about you, write to us. Deleting an account ends its license.