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.
Every Kenva moment involves the same three players. Nothing else touches your notes.
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.
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.
Where everything is stored, in a folder called Kenva Contacts, as plain text files you can open and read yourself.
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.
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 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
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
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.
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.
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.
A privacy promise only counts if you can check it. Here's the complete split:
yours — readable, editable, yours to keep even if you leave
the minimum needed to keep the bridge standing
The fine print version lives in our Privacy Policy.
Sign in with Google, allow the one folder, paste your link into Claude. That's the whole setup.
Start your 5-week free trial