Under the hood, minus the jargon

How Kenva actually works

You don't need to understand any of this to use Kenva. But if you like knowing where your data goes before you trust something with the people in your life — this page walks the whole path with you.

The three parts

Meet the cast

Every Kenva moment involves the same three players. Nothing else touches your notes.

Claude — your assistant

The AI you already talk to. It does the reading, writing, and remembering-to-file. Kenva doesn't replace it; it gives it a place to keep notes.

Kenva — the bridge

A small service with one job: carry notes between Claude and your Drive, then get out of the way. It keeps no copy of what crosses it.

Your Google Drive — the filing cabinet

Where everything is stored, in a folder called Kenva Contacts, as plain text files you can open and read yourself.

The technology

What's an "MCP connection"?

During setup you paste a link into Claude and it becomes a "connector." That link is an MCP connection — MCP stands for Model Context Protocol, an open standard created by Anthropic (the makers of Claude) that lets AI assistants safely use outside tools.

Think of MCP as a universal wall socket for AI. Any tool that's built with the right plug can connect — and the assistant can only draw what the socket offers, nothing more.

Kenva is one of those tools. When you add your personal Kenva link, Claude gains exactly two new abilities: save a note about a person and look a person up. It can't use your Kenva connection to browse the web, read your email, or touch anything else — the socket simply doesn't offer that.

Because MCP is an open standard rather than something we invented, you're not locked into a proprietary system. It's the same mechanism thousands of tools use to connect to Claude.

The path — saving

What happens when you say "remember her"

The whole round trip takes a couple of seconds. Here's every stop along the way:

you → Claude → Kenva (the bridge) → your Google Drive · and nothing is stored anywhere in between

The path — remembering

And when you ask about someone later

Recall is the same road, driven the other way:

the note is handed over for that one reply, then set aside — never kept, never trained on

Security by design

Two separate keys, both in your pocket

Setup asks you for two permissions. They're deliberately separate, and you can revoke either one at any time from your own accounts — no need to ask us.

Key 1 · Identity

"This is me"

Your Google sign-in proves who you are, so your notes can never mix with anyone else's. It's the same one-tap sign-in you use elsewhere — Kenva never sees your password.

Key 2 · One folder

"You may use this one folder"

A separate Drive permission — the narrowest Google offers — lets Kenva touch only files it created. Your documents, photos, and everything else on your Drive are technically invisible to it. Revoke it in one click from your Google account.

The honest inventory

Where everything lives

A privacy promise only counts if you can check it. Here's the complete split:

In your Google Drive

yours — readable, editable, yours to keep even if you leave

  • Every contact note, as plain text files
  • Everything Claude has ever learned about your people
  • The Kenva Contacts folder itself

On Kenva's side

the minimum needed to keep the bridge standing

  • Your sign-in email and account status (trial dates, plan)
  • One encrypted Drive credential, locked in a vault, so the bridge works between sessions
  • That's it — no copies of your notes, ever

The fine print version lives in our Privacy Policy.

Seen enough?

Two minutes from here to "remember her"

Sign in with Google, allow the one folder, paste your link into Claude. That's the whole setup.

Start your 5-week free trial

Setup guide · Full FAQ