Privacy policy
Last updated 15 November 2026
Claktor provides the claktor command-line tool (the CLI) and the website claktor.com. This page says what each records. Write to [email protected] with any question about it.
What stays on your machine
Your source code, file paths, repository names and command arguments. The CLI analyses code locally and sends none of it.
What an installed CLI sends
- Usage events. One per command: the command name, exit code, duration, CLI version, platform, the coding agent or terminal that ran it, the languages of the mapped repository and a random install id. A
length diffevent also carries the number of tokens it measured and hashes of its starting commit, its branch name and the commits made since that start. The hashes are keyed with a value that never leaves your machine, so we cannot match them to a commit, a branch or a repository. - Interest.
claktor interestsends the install id, version and driver, and your email address if you give one. - Feedback.
claktor feedbacksends the text you or your agent wrote, with the version, platform, driver and install id.
The install id is a random number created on your machine. It tells one installed copy from another and names no person.
What the website records
- Visits. A random id, the page, the site you came from and a campaign tag if the link had one. The browser keeps a marker for the tab's session so one visit is counted once. We set no cookies, and we record nothing when your browser sends Global Privacy Control or Do Not Track.
- Downloads. The file, the time and the kind of client that fetched it (curl, wget, a bot or other).
IP addresses
Requests reach us through Cloudflare, which handles your IP address to deliver and protect the site. Our server uses the address in memory to limit how many requests one network can send, and does not store it. Release files are downloaded from GitHub, which receives your address when you install or update.
How we use it
To count installs and use, to see which agents, languages and commands matter, to measure in total how much code Claktor removes, and to answer interest and feedback. We may publish totals, such as the number of tokens removed across all installs. We do not sell data.
Who processes it
Amazon Web Services hosts our server and its backups in Frankfurt, Germany. Cloudflare carries the traffic. GitHub serves the release files.
How long we keep it
Usage, visit and download records name no person, and we keep them while we operate Claktor. We keep an email address or a feedback message until you ask us to delete it or we no longer need it. Backups expire after thirty days.
Your choices
claktor telemetry offstops the usage events and deletes the ones still waiting to be sent.DO_NOT_TRACK=1in the environment does the same for the commands that run with it.- Global Privacy Control or Do Not Track in your browser stops the visit record.
- Write to [email protected] with your email address or your install id (in
~/.claktor/config.json) to get a copy of what we hold for it or to have it deleted. Where data protection law gives you further rights, such as objecting to this use or complaining to your data protection authority, they apply here.
Changes
We may update this policy. The new version appears on this page with its date.