Security and privacy
A memory holds what people tell you, so who can read it, and how it is forgotten, matter as much as what it can do. This is how Geniffy handles both.
Where memory is stored
Geniffy stores memory in India. The models that learn from it and answer are Claude, on Anthropic's API, with Google's Gemini taking over if Claude cannot answer, so what they read may be processed outside India: Anthropic keeps what it receives in the United States for up to 30 days, to check for misuse, unless its usage policy or the law needs it kept longer, and Gemini runs on Google's global endpoint. Neither provider trains its models on what it reads, and both providers' data processing terms include the European Commission's standard contractual clauses. Every call to the API, the MCP server and the app travels over HTTPS.
Who can read a memory
- Your key reaches your memory, and nothing else. An API key reaches its owner's memory and the spaces beneath it, never another account's. Revoke a key in the Geniffy app and it stops working at once.
- Each of your users is separate. A space is one of your users. What is added to one space is never found from another, and your own memory never mixes with theirs.
- Keys stay on your server. A key is shown once, when you make it. Keep it out of browsers and mobile apps.
- A user's own app gets a key for that user alone. A key limited to one user reads and writes their memory and nothing else, can be made to expire, and stops when you revoke it or erase that user.
- A blank space is refused. A call that names a space but leaves it empty, which is what a missing user id looks like, is refused rather than read as your own memory.
How AI apps are let in
Claude, ChatGPT, Cursor and the other apps connect through the MCP server with a sign-in, never with a copied key.
- You approve each app. Geniffy shows who is asking and where it will send you back, and nothing is shared until you choose Allow. You can allow reading only.
- Access is short-lived. An app's access lasts an hour and is renewed with a refresh token that works once. A refresh token used twice ends that app's access, because only a copied token would be used twice.
- Tokens are stored as hashes. Geniffy keeps a one-way hash of each app's tokens, not the tokens themselves.
- You can disconnect at any time, by removing Geniffy in the AI app's own settings.
The details are in Sign-in.
Forgetting
- One memory, forgotten for good, or marked wrong with what is right saved in its place. See Correct and forget.
- One source, and every memory only it taught.
- Everything held for one of your users, with one call, when they ask to be forgotten. Their calls come off Requests, and keys limited to that user stop with it.
- Your whole account. Deleting it erases your memory and every space beneath it, one for each of your users, and stops every key, then counts what is left and reports done only when nothing is.
A record of every call
Every call gets a request id, and a record of what was asked and what came back that you can search in the Geniffy app for 30 days. See Request ids.
Secrets
Don't add passwords, API keys or other secrets to a memory. The memory tools tell AI apps never to save them, and the Claude Code plugin removes them before anything leaves your computer.
Report a vulnerability
Email ops@geniffy.com with what you found and how to reproduce it, and please don't open a public issue. See the security policy.