Legal
Privacy
What Helmlane stores about you, why, for how long, and who else is involved — in plain language.
- In effect from
- 14 October 2026
- Operated by
- Ilia Mironchik
- Contact
- support@helmlane.com
The short version
- Your code stays on your computers. The coding agents run there, not on our servers.
- We store what the service needs to work across your devices: your account, your computers’ names and health, your projects, and your chats with the agents.
- No advertising, no analytics, no tracking, and we do not sell data. This website sets no cookies.
- You can run the whole service on your own server instead, in which case none of it reaches us.
What this covers
This policy covers this website, the Helmlane web app atapp.helmlane.com, the Helmlane control plane atapi.helmlane.com, and the Helmlane apps and agent while they are connected to it. It is operated by Ilia Mironchik.
If you connect Helmlane to a control plane you or someone else runs (“self-hosted”), that server’s operator decides what happens to the data on it, and this policy does not apply to it.
What we store
| What | Details | Why |
|---|---|---|
| Account | Your email address and display name, a hash of your password, your passkeys’ public keys, your authenticator secret (encrypted), hashes of your recovery codes, and your settings. | To sign you in and keep your preferences. |
| Sessions and devices | For each signed-in device: an identifier, its platform (for example iOS or web), when it first appeared, how it signed in, and hashes of its session tokens. No IP address, location or browser fingerprint. | To keep you signed in and let you see and sign out your devices. |
| Computers | Each enrolled computer’s name, platform, agent version and connection state; the folders you shared on it; which coding agents are installed and whether they are signed in; and health readings — power, battery, disk space, thermal state, uptime and load. | To route work to the right computer and to tell you when it needs attention. |
| Projects and chats | Project names and their folders on your computers; your chats — what you wrote, what the agents replied, and the tool activity they reported — plus drafts, images and files you attach, screenshots, terminal recordings you choose to make, and review comments. Chats can include code an agent quoted. | So every device shows the same history, even while the computer is offline. |
| Work records | Requests you sent, runs and their outcomes, and the token and cost figures agents report. | To run, queue and report on work, and to show usage. |
| Audit log | For every command sent to your computers: who asked, from which session and device, which computer and folder, the kind of command, the rule that decided it and the result. Never file contents, prompts, replies or credentials. | So you can review what reached your computers, and to enforce your command rules. |
| Notifications | Push tokens for your phones and browsers (encrypted, never shown back to any client), Live Activity tokens, your notification settings, and a history of notifications raised for your account. | To deliver the notifications you asked for. |
| Automations | Schedules, mission prompts, and webhook deliveries you configured, with their results. | To run them when you asked. |
| Connected apps | API tokens for the MCP server (stored as hashes), their scopes and expiry, and a record of each use. | So you can see and revoke what has access. |
| Telegram, if you link it | Your Telegram user and chat identifiers and an encrypted session for the bot. | To answer you in Telegram. |
| Log bundles you request | Agent logs a computer uploads when you ask for them from the app. | So you can read them remotely. |
| Verification and password-reset messages, held encrypted until they are sent and then cleared. | To confirm your address and recover your account. |
What stays on your computers
- Your repositories and files. When you open a file, a diff, terminal output or a preview from your phone, the control plane passes it through to you without keeping it. What you attach to a chat, a screenshot, or a terminal recording you choose to make becomes part of that chat.
- Your coding agents’ sign-ins and API keys. They never leave the computer.
- The agents’ own conversation stores. Helmlane reads them on the computer and stores its own copy of the chats as described above.
- The computer’s own Helmlane credential, kept in its keychain or an encrypted file.
On your phone
The iPhone app uses the camera only when you scan a pairing code or take a photo to attach, and the photo library only when you choose a photo to attach. Face ID, if you turn it on, is handled by iOS; we never receive biometric data. Your session token is kept in the device keychain.
What we do not collect
- No advertising or marketing trackers, and no product analytics, in the website, the web app or the phone apps.
- No cookies on this website. It remembers a light or dark theme you pick in your browser’s local storage, which never leaves your device.
- We do not sell or rent personal data, and we do not use your chats or code to train models.
Like any web server, ours keep standard access logs — IP address, time, the address requested and the browser’s user agent — for security and to keep the service running. They are rotated and deleted on the servers’ regular schedule.
How it is protected
Everything travels over HTTPS, and passwords, tokens and recovery codes are stored only as hashes. Chats and other content are stored on our servers so every device can show them; they are not end-to-end encrypted, and the control plane can read them in order to show them to you. The details are in Security.
Push notifications travel through Apple and Google, so they are written to reveal as little as possible: no project or chat names, prompts, replies, file paths or computer names — only the kind of event, the agent, and a number such as a percentage.
How long we keep it
| Data | Kept |
|---|---|
| Account, projects, chats, attachments | While your account exists. Archiving a chat hides it; it does not delete it. |
| A removed computer | Its record and credentials are deleted when you remove it. |
| Audit log | 180 days, then removed; the removal itself is recorded. |
| Computer health history | 30 days. |
| Account activity feed that syncs your devices | At least 7 days, then trimmed. |
| Use history of API tokens | 90 days. |
| Log bundles you requested | 24 hours. |
| Sessions | Until you sign out, or 90 days without use. |
| Push tokens | Until you sign out on that device or the token stops working. |
| Pending emails | Cleared once sent or expired. |
Who else is involved
We use a small number of providers to run the service. Each receives only what its job requires:
- Hetzner hosts the control plane servers and their database, in Germany.
- Amazon Web Services stores uploaded images and files (S3, Frankfurt region).
- Cloudflare serves the web app at
app.helmlane.comand forwards its requests to the control plane. - Apple and Google deliver push notifications to iPhones and Android phones, and browser makers deliver web push, with the minimal content described above.
- Telegram, only if you link the Telegram bot.
- GitHub hosts the Docker image; pulling it is subject to GitHub’s privacy terms. The Mac and Linux downloads are served from
helmlane.com.
The coding agents you use — Anthropic, OpenAI, Cursor, Google and others — are your own relationships. They run on your computer under your accounts, and what they do with your prompts is governed by their terms, not this policy.
Your choices
- See your data in the apps: chats, computers, sessions, connected apps and the audit log, which you can export.
- Remove a computer, sign out a device, revoke a connected app, or unlink Telegram at any time from the app.
- Turn off notifications per kind, set quiet hours, or remove push from a device.
- Delete your account by writing tosupport@helmlane.comfrom the email address on the account. We delete the account and its data within 30 days, except where the law requires us to keep something longer.
- Run your own server with the self-hosting guide, and nothing reaches us.
Depending on where you live, you may have further rights over your personal data, such as access, correction, export or objection. Write to us to use them. You can also complain to your local data protection authority.
Children
Helmlane is not directed at children under 13, and we do not knowingly collect their data.
Changes and contact
If this policy changes, we will update it here and change the date at the top. Questions or requests:support@helmlane.com. The source of the Helmlane software is published on GitHub.