Who we are
Kenva is operated by ALFREDHQ LLC, an Oregon limited liability company ("we," "us"), based in Portland, Oregon. We run kenva.app — a personal CRM that connects your AI assistant to contact notes stored in your own Google Drive. Questions about this policy: kenvaapp@gmail.com.
What we store — and where
Design principle: Kenva is a bridge, not a vault. Your contact notes are written to a "Kenva Contacts" folder in your own Google Drive as plain text files. We do not keep copies of them on our servers.
To run the service, we store a small amount of data ourselves:
- Account basics — the email address and user ID from your Google sign-in, so you can log in and we know whose account is whose.
- Drive credential — an encrypted Google Drive refresh token, kept in an encrypted vault, so Kenva can write to its folder in your Drive between sessions. It is scoped to the narrowest permission Google offers (files Kenva creates — nothing else in your Drive).
- Account status — whether your Drive is connected, your trial dates, and your plan status.
- Payment records — if you purchase a plan, payment is handled by Stripe. Stripe processes your card details directly under its own privacy policy; we never see or store your card number. We keep a record that the purchase happened (which plan, when, and Stripe's reference for it).
What passes through Kenva
When you ask your AI assistant to save or recall a contact, the relevant note travels through Kenva's server between the assistant and your Drive to fulfill that one request. It is processed in memory to complete the request and is not retained as a copy of your notes afterward.
What we don't do
- We don't sell your personal information.
- We don't train AI models on your notes — not Claude, not anything else.
- We don't read your Drive beyond the files Kenva itself created.
- We don't show ads.
Third-party services
Kenva relies on a small set of processors to operate:
- Google — sign-in and Drive storage, under your own Google account and Google's privacy policy.
- Supabase — authentication and our encrypted credential vault.
- Cloudflare — hosting and serving the website and API.
- Stripe — payment processing. Card details go directly to Stripe and are handled under Stripe's privacy policy; we don't receive them.
- Anthropic (Claude) — your conversations with Claude happen under your own Claude account and Anthropic's terms; Kenva only responds to the requests Claude sends it on your behalf.
Your controls
- Revoke Drive access anytime from your Google account's security settings (Connections / third-party access). Kenva loses the ability to touch your Drive the moment you do.
- Your files stay yours — the Kenva Contacts folder remains in your Drive, readable and editable, whether or not you keep using Kenva.
- Delete your account — email kenvaapp@gmail.com and we'll delete your account record and stored credential. Files in your Drive are yours; we couldn't delete them even if asked to — remove them yourself if you wish.
Data retention
We keep your account data for as long as you have an account. If you delete your account, we delete your account record and stored Drive credential; payment records are kept only as long as tax and accounting rules require. Your files in Drive are unaffected — they're yours.