Security
Built like it holds your keys
Because it does. Your bots sign in to your accounts, read your mail and sometimes pay for things. This page explains, plainly, how that's kept safe, and what we don't claim.
Sealed computers
Every bot computer is boxed in, with no special powers and no way to reach other computers or our servers.
Logins it never reads
Passwords, and cards from your 1Password vault, are typed in by Henchkin itself, only on their own site.
You approve what matters
Payments, messages and anything irreversible wait for an OK only you can give.
Encrypted and backed up
Servers in Poland today, secrets encrypted at rest, encrypted backups every hour and every night.
Bot computers
Each bot works on a computer of its own (or one shared by a company's bots, if you choose): a desktop with a browser, a terminal and files, running as an isolated container on our servers.
- No special powers. Computers start with every Linux privilege removed, can't gain new ones, and have hard limits on memory, processor and processes.
- Walled off. A firewall stops a computer reaching our own servers, private networks, or any other customer's computer. It can reach the public internet, and nothing else.
- Separate from the browser. The bot's browser runs as a different user from its terminal, so a script the bot runs can't read the browser's saved sessions.
- You can watch. Open a bot's screen to see every click as it happens, take control at any time, and hand it back.
Logins and the vault
A company's vault holds the passwords and one-time codes its bots may use. Entries are encrypted at rest (AES-256-GCM) with a key that lives only on our server. Payment cards come from your 1Password vault, if you connect it.
- The AI never reads them. A bot asks to sign in or pay; Henchkin types the secret into the bot's browser itself. The model sees that it worked, never the secret.
- Only on their own site. A login is typed only into the site it belongs to, so a look-alike page can't collect it.
- Scoped per company. Bots see only their own company's vault, and each bot only the apps you've connected for it.
- Logged. Every use of the vault is recorded in your account's activity log.
What the AI reads
Web pages, emails and files can contain text written to trick an AI ("ignore your instructions and…"). Henchkin marks everything a bot reads from the outside world as untrusted data, and bots are instructed to treat it as information, never as instructions. A page asking for an action is something the bot reports to you, not something it does.
Approvals
Payments, messages to other people, deleting and cancelling, and anything else that can't be undone wait for your OK.
- A bot can't approve itself. Your "Approve" arrives from your own app, as your answer to the bot's question. The bot can't write it for you.
- One action at a time. An approval covers the one action you were shown, and it expires after 30 minutes.
- Nothing gets lost. Open questions stay pinned at the top of the chat, and a bot can call your phone when one can't wait.
Your account
- Passwords are stored only as a scrypt hash, never the password itself.
- Sign-in codes. Each sign-in asks for a code we email you, or one from an authenticator app if you add one.
- Activity log. Sign-ins, vault use and every time someone took control of a bot's screen are recorded where you can see them.
- Signed updates. The phone and desktop apps only accept interface updates signed by us.
Payments
Subscriptions are paid through Stripe, or through Razorpay for rupees. Your card or UPI details go straight to them and never touch Henchkin; we keep your customer or subscription id with them, your plan and whether your invoices are paid.
Hosting
Henchkin runs on servers we rent, today in the European Union (Poland). We plan to add regions closer to our customers for lower latency, and this page will list each one. Every connection to Henchkin is encrypted (HTTPS, with HSTS). Bot computers run on those same servers.
Backups
Every hour the database (your bots, chats, memories and settings) is backed up, and every night the database and the bots' files, all encrypted, to a separate machine (kept in India). We keep two days of hourly backups, a week of daily ones, a month of weekly ones and six months of monthly ones, and monitoring alerts us if a backup fails or anything on the servers looks wrong.
A mistake doesn't need a backup: anything you delete in Henchkin waits in Recently deleted for 30 days (in Settings, and in each computer's Files panel), and you can restore it yourself, as it was.
Your AI model
Your bots' messages go to the model provider you connect (OpenAI, Anthropic, xAI or another), under that provider's own terms. Your sign-in or key for it is encrypted at rest. We never use your bots' conversations or files to train anything, and never sell data.
What we don't claim
- We don't hold security certifications such as SOC 2 or ISO 27001 yet.
- Chats are encrypted in transit and stored on our servers; they are not end-to-end encrypted, because your bots need to read them.
- No system is unhackable. We design so that a mistake in one place, or a page trying to trick a bot, can't reach your secrets on its own.
Reporting a problem
If you think you've found a security issue, email hello@henchkin.com with "Security" in the subject. We'll reply quickly and keep you updated while we fix it. Please don't test against other people's accounts or data.
More about what we store and why is in the privacy policy.