1 · The short version
Helmry is a desktop application with no backend. Your code, your prompts, your repository names, your terminal output and your agent history stay on your machine. We could not read them if we wanted to — there is nowhere for them to go.
Two narrow exceptions exist, and both are described in full below: a once-a-day licence refresh near renewal (paid users only), and aggregate visit counts for this website measured at the edge.
2 · The desktop app
The app stores everything it needs locally: configuration in ~/.helmry/config.json, agent history and artifacts under your data directory, and credentials in your operating system's keychain. None of it is transmitted to us.
3 · The one licence call
A monthly licence cannot mean a key pasted by hand twelve times a year, so a paid installation asks our licence service to re-sign its key. This is the only request the app itself makes to us, and it is bounded:
- It sends the licence id and the app version — nothing else. No repository names, no counts, no machine fingerprint.
- It runs at most once per day, and only when the key expires within 30 days.
- Failure is never fatal; a 14-day grace period covers an offline laptop or a card that failed.
- Free installations never make this call at all.
4 · If you buy a licence
Payment is processed by a merchant of record acting as the seller. It collects what a payment requires — name, email, billing country, tax identifiers, card details — under its own privacy policy. We never see your card.
What reaches us is a webhook. Our licence service stores your email address, a licence id and the subscription state, so we can issue and re-issue your key and answer “I lost it”. That is the entire record.
5 · This website
No cookies are set, no consent banner is needed, and no third-party script runs on any page here — fonts and assets are served from the same origin. Visit counts are aggregated by our hosting provider at the edge from request logs; we see totals per page, not people.
If you give us your email for release notes, we store the address and nothing else, send one message per release, and unsubscribe you in one click.
6 · Anthropic and your model use
When an agent works, your machine talks to Anthropic through the Claude Code CLI, authenticated as you. What you send — prompts, file contents, command output — is governed by Anthropic's privacy policy and your agreement with them, not by this one. We are not a party to it and receive no copy.
7 · How long we keep things
- Licence records: while your subscription is active, then [N] months, after which they are deleted.
- Release-note subscriptions: until you unsubscribe.
- Aggregate site counts: no personal data, kept indefinitely as totals.
- Support email: [N] months after the conversation ends.
8 · Your rights
You can ask for a copy of what we hold, correct it, or have it deleted; deleting a licence record ends the ability to re-issue your key, so we will say so before doing it. Write to privacy@helmry.com and we answer within 30 days.
Legal bases where the GDPR applies: performing our contract with you (licence records), your consent (release notes), and legitimate interest in a working website (aggregate counts). Data controller: [legal entity name and address].
9 · Changes and contact
If this policy changes materially — in particular if the app ever starts sending something new — we will say so in the changelog and in the app before the change ships, not after. Questions: privacy@helmry.com.