Privacy policy
Effective 2026-10-12.
Axiom DX Labs, LLC, a Delaware limited liability company ("we", "us"), makes dx and runs dxcli.com, axiomdxlab.com and the feedback service at feedback.dxcli.com. We are responsible for the personal data described here (the "controller", in the words of the GDPR). This page says what personal data we handle, why, who handles it for us, and what you can do about it. Questions and requests: [email protected].
The short version
- dx keeps your sessions on your own devices. We never receive your sessions, code, transcripts or session metadata. dx has no accounts, no analytics and no telemetry.
- What does reach us: the technical details of a web request (your IP address and user agent) when you visit our sites or install or update dx, which our hosting provider needs to deliver the page or download, and of which we keep no log; a note, if you choose to send one with
dx feedback; and email you send us. - We use no cookies and no trackers, and we don't sell your personal data or share it for advertising.
What dx does on your computer
dx stores its data under ~/.dx and reads Claude Code's own session files. That data stays there unless you set up a destination yourself:
dx synccopies it to a git repository you own.dx connectanddx sharemove it between your devices, or to a person you name, over an end-to-end encrypted connection. If your devices can't reach each other directly, they may use public relay servers run by n0, which see connection metadata but not your data.connect_lan=1keepsdx connecton your local network.dx share --fileinstead writes a file that you hand over yourself.dx connect installdownloads thersntrprogram from GitHub, so GitHub sees that request.
dx is not affiliated with Anthropic. Your use of Claude Code is covered by Anthropic's own terms and privacy policy.
What we collect, and why
Visits to our sites. When you open dxcli.com or axiomdxlab.com, our hosting provider, Render, receives your IP address, the time, the address you asked for and your browser's user agent, because it needs them to deliver the page. We keep no log of visits and we don't analyse them. Render may keep its own operational records under its own policy. We set no cookies, and our pages contain no analytics or advertising. They load nothing from anyone else: even the fonts are our own files.
Installing and updating dx. curl … | bash, dx update and the automatic update check fetch files from dxcli.com: the installer, the release tarball, and the checksum list with its signature. The same applies: Render sees the request, and we keep no log. The update check runs at most once a week; turn it off with DX_NO_UPDATE_CHECK=1. dx sends no identifier of its own: no account, device ID or install ID.
Feedback you send. Only when you run dx feedback, dx bug or dx idea. We receive:
- your note (up to 16 KiB), its title and its kind;
- unless you use
--bare: the dx version, your operating system and architecture, your shell's version, the terminal's name, and the Claude Code and git versions.
Never sent: file paths, host names, user names, repository names, session content. --dry-run shows you exactly what would go. The note travels to our feedback service at feedback.dxcli.com, which files it as an issue in a private repository on GitHub. The service's request log, which holds your IP address and the note's title, is kept by Render for 7 days. To limit abuse, the service also counts notes per IP address in memory only. If you put your email address in the note, we have that too; we use it only to answer you. While you type at the bare dx feedback prompt, dx contacts the service's health check so that it is awake when you press Enter; that request carries nothing but an IP address and user agent.
Email. If you write to us, we receive your email address and whatever you send. We use it to answer you. Our mail is handled by Google Workspace.
What we don't collect
Accounts or passwords, payment details (dx is free), cookies, analytics, advertising identifiers, device fingerprints, location, or anything from your sessions.
Why we may use it (EEA and UK)
If you are in the European Economic Area or the UK, these are our reasons:
- Running and securing the sites, the installer and updates: our legitimate interest in a working, safe service.
- Feedback and email: your consent when you send it, and our legitimate interest in replying and in fixing problems.
- Security reports: our legitimate interest in protecting users, and a duty to handle what you report responsibly.
Who handles it for us
- Render hosts our websites, the installer, the release files and the feedback service.
- GitHub (Microsoft) stores feedback as issues in a private repository.
- Google runs our email (Google Workspace).
- Amazon Web Services runs the DNS for our domains and sends mail from our domain.
They handle personal data only on our behalf, under their data processing terms, and may use sub-processors of their own. We don't sell personal data and don't share it for advertising. We may disclose it if the law requires, or to protect people from harm.
How long we keep it
| What | How long |
|---|---|
| The feedback service's request log (IP address, note title) | 7 days, kept by Render |
| Visits to our websites | We keep no log |
| Feedback notes (the GitHub issues) | 12 months after the issue is closed, then deleted; sooner if you ask |
| 3 years after the last message | |
| Security reports | 3 years after the fix |
Where it is processed
Our providers process data mainly in the United States. If you are in the European Economic Area or the UK, your personal data is transferred there. We rely on the safeguards in our providers' data processing terms, such as the EU's standard contractual clauses.
Your choices and rights
- Turn off the update check (
DX_NO_UPDATE_CHECK=1), skipdx feedback, or use--bare. - Ask us what we hold about you, to correct it, or to delete it: write to [email protected]. We may ask you to confirm it is you, and we reply within 30 days. The feedback service's log is keyed by IP address, so to ask about a log entry give us the address and the date.
- If you are in the EEA or the UK you also have the rights to restrict or object to processing, to take your data with you, and to complain to your data protection authority.
- If you are in California you have the rights to know, correct and delete. We don't sell or share personal information, and we won't treat you worse for asking. The categories we collect are identifiers (your IP address and, if you give it, your email address), internet activity (the request details above) and what you write to us (feedback and email). We keep each for the time in the table above.
Do Not Track
We don't track you across websites or over time, and we don't let other parties do it on our pages, so there is nothing to switch off. Browser signals such as "Do Not Track" or Global Privacy Control make no difference to what we do.
Security
Our sites are served over HTTPS. Releases are signed, and dx checks the signature before it installs an update (the fingerprints are at axiomdxlab.com/security). The accounts that hold your data (GitHub, Render, Google and AWS) require multi-factor authentication. To report a security problem, write to [email protected].
Children
dx is a tool for developers and is not directed at children.
Changes
If we change this policy we post the new version here with a new date, and note a material change in the dx release notes.
Contact
Axiom DX Labs, LLC · [email protected]