Security

• Secrets and saved logins you give your agent are encrypted to your own computer. Our servers can't open them.
• Most of what you keep in Kynver, like chats with your agents, reports and email, we can read. Some of it is stored encrypted, but we hold those keys.
• Private chats with friends are built so only your devices can open messages. They aren't on yet, and we'll explain below what we're fixing first.
• No system is perfectly safe, so we tell you the limits too.

Our servers store these only in a form we have no key to open.

• The values of secrets and saved-login passwords you give your agent

  They are encrypted in your browser to your computer's key. Our servers only pass them along.

• Memory Vault items

  They are encrypted in your browser with a key made from your passphrase, which we never receive.

• The text of private chat messages, once private chats are on for you

  Our servers store only the encrypted form and hold no key for it. Your history backup is encrypted with your recovery key, which we never receive.

  Limit: Messages a friend reports to us are different: we can read those. See "What we can see".

We need these to run Kynver. We don't sell your data.

• Your account

  Your name, email address and account settings.

• Your chats with your agents, your reports and comments on shared reports

  Some agent chats are stored encrypted with a key for your workspace, but we hold that key.

• What you send to an AI model

  When your agent uses an AI model, your request goes to that model's provider to get an answer.

• Who you chat with, and when

  For private chats with friends, we can see these things, even when we can't read the messages:

  • Who your friends are, who asked whom and when, how often a request was turned down, and who you've blocked
  • Who is in each chat, when each message was sent and roughly how long it is
  • Your devices: the names you give them, what kind they are, when you added them and the day each was last used
  • What you've read and when, whether you muted a chat, and when you cleared one
  • When a chat switched between Private and "Agents can help": who asked, who agreed or said not now, and each person's signed agreement
  • Reports: who reported whom, the reason they chose and which messages they picked
  • Invites you send by email: the address and any note you add
  • On shared shopping lists: which items are ticked, who ticked them and when
  • Your notifications: what each one was about, who it came from and when you opened it

• Messages a friend reports to us

  If a friend reports messages from a private chat, those messages are sent to Kynver and our staff can read them. We don't tell the person who wrote them.

• Chats where you turned on "Agents can help"

  When everyone in a private chat agrees to let agents help, new messages can be read by Kynver, by each person's agent and by the AI providers those agents use. Either person can switch it back.

• Email

  We hold the key to personal mailboxes so the service can show and send your mail. Mailboxes your agents use aren't separately encrypted.

• Labels around your secrets

  The names you give secrets, and for saved logins the site and the username.

• Everything you send us

  On

  Who holds the key: Your browser and our servers, for the trip only

  Pages and data travel over HTTPS. In production our site tells browsers to use HTTPS only, every time.

  Limit: HTTPS protects data on the way to us. Once it arrives, what protects it depends on the rows below.

• Secrets and saved logins for your agent

  On

  Who holds the key: Only your computer

  When you give your agent a password, API key or site login, your browser encrypts it to your computer's own key before it leaves. Our servers pass it along but have no key to open it. Your computer stores it encrypted, with its keys in the system keychain where one exists.

  Limit: We keep no copy, so if you lose that computer you'll need to enter them again. We can see the names you give them, and for saved logins the site and the username.

• Memory Vault items

  On

  Who holds the key: Only you (your passphrase)

  Items you put in the Vault are encrypted in your browser with a key made from your passphrase. We store the encrypted form.

  Limit: If you forget the passphrase, we can't recover the items.

• Private chats with friends

  Not on yet

  Who holds the key: Your devices and your friend's

  Private chats are built on MLS, an open messaging-encryption standard, using the OpenMLS library. Each message is encrypted on your device and opens only on devices you and your friend have set up. Our servers store the encrypted form. Private chats are still being turned on, and we don't yet call them end-to-end encrypted: our own review in November 2026 found gaps we are fixing first (listed below).

  Limit: We can still see who you chat with, when, roughly how long each message is, and your list of devices.

• Email in a personal Kynver mailbox

  On

  Who holds the key: Kynver (a key for your workspace)

  In mailboxes set up for a person rather than an agent, the subject, addresses, message text and attachments are stored encrypted, with a separate key for each workspace. Agents, tools and API keys can't open these mailboxes; you need to be signed in. Mailboxes your agents use aren't encrypted this way.

  Limit: We hold that key, so this protects a stolen copy of our database, not against us. Dates, read and starred status, message ids, and attachment names and sizes aren't encrypted. Email itself travels between mail servers outside our control.

• Connected accounts and sign-in codes

  On

  Who holds the key: Kynver

  Tokens for accounts you connect, two-factor secrets and similar keys are stored encrypted, so they aren't readable in a copy of the database.

  Limit: We hold the keys so the service can use these on your behalf.

• Reports, and reports you share with friends

  Not encrypted

  Who holds the key: No separate key; access is checked

  Reports are stored without a separate encryption key. When you share one, we check on every request that the person you shared it with is allowed to see it. Share links are stored only as a fingerprint of the link.

  Limit: We can read reports and comments on shared reports.

• You are trusting the app we send you

  The encryption above happens in your browser, using app code our servers send you. A changed version of that code could read what you type before it is encrypted, or messages after they are decrypted. We don't yet publish fingerprints of each release that someone outside Kynver could check. Until we do, we only promise what our servers can't open, not that Kynver as a company never could.

• Your device is part of the protection

  Anyone who can use your unlocked device, or a harmful browser extension, can see what you can see there. Keep your devices locked and remove one you've lost from your device list.

• Backups

  Copies of our database contain whatever the database holds: encrypted items stay encrypted, and items we can read stay readable to us. Your private chat history backup is encrypted with your recovery key. If you lose every device and that key, nobody can recover those messages.

• This page is our own review

  We checked each line against our code. No outside firm has audited it.

Our own review of private chats in November 2026 found these. We'll take each one off this list when the fix ships.

• A new or restored device doesn't yet bring your friends' verified security codes with it

  Until it does, a new device would not warn you if a friend's keys were swapped.

• Keys don't yet refresh on a schedule

  So someone who copied a device's keys once could read later messages in that chat.

• "Remove" doesn't yet change your backup key

  Use "Remove and secure" for a lost device.

• Your agent can still keep a note of a chat it was invited to read

  Only in chats where you turned on "Agents can help".