Personal details for AI agents
Your agent fills the form. It doesn't need to see your passport number.
Hesimesi seals your personal details on your device. When an agent needs one for a website that uses our site kit, you approve it on your phone, and it goes to that site sealed so only the site can open it. The agent gets a one-time token in its place, and we can't open the detail.
BetaAn early version for developers and early testers: free, invite-only and approved by hand. Use sample details only, and keep your own copy of anything you put in. The full version is coming soon.
The problem
Agents can fill forms now. Most of them see everything they type.
To fill a visa form or a checkout, an agent usually gets your details as plain text. Anything it reads can end up in its chat history, its logs or its provider's servers.
How it works
Three steps, and the agent doesn't need to hold your details.
- 01
Save your details once
Passport number, date of birth, nationality. They are sealed on your device with a passphrase only you know.
- 02
Your agent asks
It gets the names of your details from us, not the values, and asks for the ones the form needs.
- 03
You approve on your phone
Your passkey says yes. The details go to the website sealed so only it can open them, and you get a receipt.
See it step by step
Your agent asks. You approve. The site receives.
Your details travel from your phone to the website sealed so only that site can open them. The agent carries a one-time token, never the values.
Who it's for
Two sides, one promise: the agent doesn't need to hold the details.
For people who build agents
Connect any agent that can send an HTTP request (the MCP server isn't available to download during the beta). When a website receives your clients' details through our site kit, they stay out of your workflows and your logs.
Request free beta accessFor websites
Receive details from AI agents sealed for your site, while the agent carries a one-time token. A small server-side kit checks each request and gives you a signed receipt.
Talk to usWhy trust us
Claims you can check.
What we promise, and what is true today.
We can't read your details
Their values are sealed on your device before they reach us; we keep only that sealed copy. The names you give them stay readable, so your agent can ask for them.
You stay in control
Every site request needs a passkey approval. Other uses follow the rules you set.
Site deliveries are on the record
A site delivery can't go ahead until it is in your activity log, with the agent that asked. Fills and other requests are logged as they happen, but not every one: a refused request, or a rare failure, leaves no entry.
Built on reviewed building blocks
Standard cryptography, never our own. Hesimesi has not had an outside audit yet, and neither has the post-quantum library that seals site deliveries; we will say so here when that changes.
And if something goes wrong?
Forget your passphrase? If you turned on recovery, the people holding your latest recovery shares can bring your saved details back; without recovery they are lost, though you can still type them in each time you approve. Lose your phone? A passkey on another device, including one synced there, keeps working. If you have none, sign in and add a new passkey in Settings: you confirm it's you with your password and a link we email you, and it starts working 24 hours later.
Pricing
Free during the beta.
Hesimesi is an early version for developers and early testers, free and invite-only: we approve each account by hand. No card needed.
Questions
The things people actually ask.
Not when a website receives them through our site kit and you approve on a device your agent doesn't use: the agent gets their names and a one-time token, and the values go sealed from your device to the site. If the browser extension fills a form instead, the value lands in a page your agent may be able to read.
Not their values: they are sealed on your device, and we keep only a sealed copy we cannot open. The names you give them, like "Passport number", are readable so your agent can ask for them.
Any agent that can send an HTTP request, with a key of its own. During the beta the MCP server isn't available to download; if your agent needs it, write to support@hesimesi.com.
Websites that add our site kit. None outside our own tests yet — if you run a website, talk to us. Beta testers can try a delivery on our demo visa site, with sample details only. Write to support@hesimesi.com and we'll send you its address.
Forget your passphrase? If you turned on recovery, the people holding your latest recovery shares can bring your saved details back; without recovery they are lost, though you can still type them in each time you approve. Lose your phone? A passkey on another device, including one synced there, keeps working. If you have none, sign in and add a new passkey in Settings: you confirm it's you with your password and a link we email you, and it starts working 24 hours later.
Not yet. Hesimesi has not had an outside audit, and neither has the post-quantum library that seals site deliveries; we'll say so here the day that changes. The building blocks — XChaCha20-Poly1305, Argon2id, Shamir — are standard ones the security community has already reviewed, and we don't invent our own. The values you save are sealed on your device before they reach us, so a breach of our storage, or anyone here reading what we store, could not open them. They would see what we keep readable, for example email addresses, file names and labels, the sign-in log with IP addresses, and contact-form messages. You still trust the code our website sends to your browser, because that code does the sealing.
Yes, during the beta. No card needed.
Use sample details for now, not your real passport. Your saved details are sealed on your device and we can't read them, but during the beta we can't promise to keep them. Keep your original files.
Join the beta.
Free, no card, and invite-only: we open beta accounts by hand, a few at a time, so we can help each one get set up.
Request beta access