Skip to content
Henchkin
Product Pricing Download Compare Security Help
Sign in Choose a plan
Product Pricing Download Compare Security Help What's new
Choose a plan Get the app Sign in

Privacy policy

What Henchkin keeps, and why

Last updated 5 November 2026. Henchkin is run by Aditya Shrivastava. Questions and requests: hello@henchkin.com.

The short version

Henchkin stores what it needs to run your bots and nothing it can avoid. We never sell data, never show ads, and never use your bots' conversations or files to train anything. Your model provider, not Henchkin, processes the text your bots send to the model.

What we store

  • Your account. Your email address, name and a hash of your password (never the password itself), the sign-in codes we email you, and which devices are signed in. If you sign in with Google, also your Google account's id, so we recognise it next time. For each sign-in: when, from which IP address and device, and how (password, emailed code, Google); see Security records.
  • Your bots. Their names and instructions, their conversations with you, what they remember, their routines, and the files on their bot computers.
  • Apps and passwords you give a bot. Sign-ins and passwords you put in a company's vault are encrypted at rest with a key that lives only on our server. A bot uses them on its own computer; they are never shown to the model and never leave the vault in plain text except into the bot's browser.
  • Connected services. If you connect Google (Gmail, Drive, Docs, Sheets, Calendar) or another service, we store the access token that service issues, encrypted, so your bot can act on it. Disconnecting removes it. For Google, see Google user data below.
  • Your model provider. The sign-in or API key you connect for ChatGPT, Claude, Grok or another provider, encrypted at rest. Your bots' messages go to that provider under its own terms.
  • Billing. Payments are taken by Stripe, or by Razorpay for rupee payments by UPI or card. Your card or UPI details go straight to them and never touch Henchkin. We keep your Stripe customer id or Razorpay subscription id, your plan and whether your payments went through. Razorpay collects your contact and payment details on its own page; from us it gets your plan, the amount and an account number that only means something to Henchkin.
  • Activity. A log of security-relevant events on your account (sign-ins, vault use, when you took control of a bot's screen) so you can see what happened.

Google user data

Henchkin's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

  • Signing in with Google. We receive your name, email address and Google account id, and use them only to sign you in to your Henchkin account. Your sign-in still needs its second step (a code), as with a password.
  • What we access, when you connect Google. Only the Google apps you choose when connecting (Gmail, Drive, Docs, Sheets, Calendar), each read-only or with editing as you choose, for the Google account you sign in with.
  • How it's used. Only to do what you or your bots are asked to do in those apps: for example triage and draft email, find or edit a document, or manage your calendar. A bot asks you before it sends an email. Bots never see your Google sign-in itself: each task gets a short-lived access token on the bot's own computer.
  • Who it goes to. What a bot reads from Google becomes part of its work, so it is sent to the AI model provider you connected (ChatGPT, Claude, Grok or another) to carry out your request, under that provider's terms. We share Google data with nobody else, except when the law requires it.
  • What we never do. We don't sell Google data, use it for advertising, or use it to train or improve AI or machine-learning models, ours or anyone else's. People at Henchkin don't read it, unless you ask us to (for example in a support request), it's needed for security (such as investigating abuse), or the law requires it.
  • Storage and removal. The access we're given is stored encrypted on our servers. Disconnect a Google account in Henchkin, or remove Henchkin's access at myaccount.google.com/permissions, and every bot loses access at once. What your bots already saved (in chats or on their computers) stays in your account until you delete it or your account.

The phone and desktop apps

The apps are the same product as the website. They ask for the microphone only when you dictate or call a bot, and for notifications so a bot can tell you when it needs you. They don't read your contacts, location, photos or other apps. Nothing is collected about you for advertising or analytics.

Where it lives

Today, everything runs on servers we rent in the European Union (Poland), with encrypted backups kept in India. As we add hosting regions for lower latency, this page will say where each one is. Bot computers are isolated containers on those servers. Connections are encrypted in transit (HTTPS).

Who else sees it

Only the services needed to run Henchkin: your model provider (the messages your bots send it), Stripe and Razorpay (payments), the services you connect (through the access you grant), and our hosting providers (the servers themselves). We share data with nobody else unless the law requires it.

Security records, and the law

To protect Henchkin and the people our users' bots deal with, and because Indian law requires it (the CERT-In Directions under the IT Act, and the Digital Personal Data Protection Rules), we keep a small set of security records, and nothing more than they need:

  • Bot computers' connections, summarised by the hour. Which computer connected to which internet address and port, during which hour, and how many times. Not the names of websites, not the pages, and nothing that was sent or received.
  • Sign-ins and security events. When you signed in, from which IP address and device, and how; and the security events listed above under Activity.
  • A closed account's basic details. When an account is deleted: its name, email, plan, when it was opened and closed, and the address it first signed in from. Nothing else of the account is kept.

These records are kept for 30 days on our main server and for one year on our server in India, where they can't be changed, and are then deleted. They are used only to investigate abuse, fraud and security incidents, and to answer lawful requests. Looking one up takes a specific reason (such as an abuse report about one address at one time) and is itself recorded; there is no browsing of anyone's activity. We share them only when the law requires it, and where the law allows we tell the person concerned. People at Henchkin don't read your chats, files or vault, except when you ask us to, when needed for a specific security investigation, or when the law requires it.

Deleting it

You can delete bots, companies, vault entries and connected services yourself at any time. Deleted bots, computers, chats, files, memories, routines, saved logins and companies wait in Recently deleted for 30 days, so a mistake can be undone, and are then removed for good; you can remove them sooner from there. To delete your account and everything in it, use Delete account in Settings → Security (or email hello@henchkin.com from your account's address). It's deleted right away, and leaves our backups within 30 days as they rotate out. The security records described above stay for their set time, then go too.

Changes

If this policy changes in a way that matters, we'll say so in the app before it takes effect.

Henchkin

AI bots with their own computers. Give one a job, and it checks in only when it needs you.

Product

  • Overview
  • Pricing
  • Compare
  • Download
  • What's new

Resources

  • Help centre
  • Getting started
  • Videos
  • Security
  • Brand

Company

  • About
  • Talk to sales
  • Contact

Account

  • Sign in
  • Sign up
  • Open in browser
Download on theApp Store Get it onGoogle Play Get it fromMicrosoft Store Download forMac

© 2026 Henchkin. All rights reserved.

PrivacyTermsSecurityHosted in secure data centres