Privacy policy

What Recall collects, where it's kept, who can see it, what happens with Gmail data, and how to get any of it deleted.

Effective

Recall is a memory engine for AI agents at recall.zakiego.com. I'm Zaki, and I run it myself as a personal, self-hosted service for me and the people I invite. In this policy, "I" and "me" mean Zaki, and "you" means anyone with a Recall account or anyone visiting this site.

In short

  • Recall keeps your account, the content you add, the session details that keep you signed in, and, if you connect Gmail, your Google address and encrypted tokens.
  • It lives on a server I run. Nightly backups go to Cloudflare R2 and are deleted after 30 days.
  • Text you add is sent to an AI model to pull out facts. Search runs on the server.
  • Gmail access is read-only, and Recall reads a whole message only when you import it, yourself or with an API key you created. See Google user data.
  • Nothing is sold, nothing is used for ads, and there are no analytics or tracking cookies.
  • Write to [contact email to be added] and I'll delete your account and everything in it.

What Recall collects

  • Your account. Your username and display name, and how you sign in: a password, stored only as a salted hash, or a passkey, of which only the public key is stored. Recall also keeps which workspaces you belong to and your role in each. It doesn't ask for your email address.
  • Content you add. Text, chats, links and the pages fetched from them, files you upload and Gmail messages you import. Recall also stores what it makes from them: facts and their version history, summaries, answers and the search index.
  • API keys. Stored only as a SHA-256 hash. The key itself is shown to you once, when it's created.
  • Sessions. A cookie keeps you signed in. Each session record stores the IP address and browser it was started from, so you can be signed out and abuse can be traced. Sessions end after 7 days without use.
  • IP addresses for rate limiting. Sign-in and invite requests are counted per IP address, in memory only, to slow down password guessing. The counts are never written to disk.

Recall doesn't use analytics, advertising trackers or third-party cookies, on this site or in the dashboard.

How it's used

Only to run Recall for you: sign you in, store what you add, turn it into facts, search it, answer questions about it, and keep the service working and secure. I don't sell personal data, use it for advertising, or build profiles of you for anyone else.

Where it's stored

  • Recall keeps everything in one SQLite database, plus a folder of uploaded files, on a self-hosted server I own and run. There is no cloud database.
  • The LLM gateway described under AI processing runs on the same server and keeps a log of each request it handles, including the text sent to the model, for 30 days.
  • Traffic reaches it through Cloudflare's network over HTTPS. Cloudflare also hosts this public site, so it sees IP addresses and request details as part of carrying the traffic.
  • Every night a snapshot of the database is compressed and uploaded to a private Cloudflare R2 bucket, where it's encrypted at rest. Each backup is deleted automatically after 30 days.

AI processing

To pull facts out of what you add, write summaries and answer questions, Recall sends the text to an LLM gateway I run, which passes it to Anthropic's Claude models and returns the result. Recall's Anthropic account has model training turned off, so this text isn't used to train Anthropic's models. Before content you add is saved as text or sent for fact extraction, Recall masks things that look like API keys, access tokens and card numbers. Search uses a small model that runs on the server itself, so nothing leaves it.

Google user data

This section only applies if you connect a Gmail account on the Connectors page of the dashboard.

What Recall can access

Recall asks Google for one permission: gmail.readonly. It can read your mail, and it can't send, delete, move or label anything. Nothing syncs in the background and nothing runs on a schedule.

  • When you search on the Connectors page, Recall asks Gmail for the matching messages' sender, subject, date and short preview, so it can show you the list. These search results aren't stored.
  • Recall reads a whole message, and its PDF attachments, only when you pick that message and import it, retry an import you started, or import it by its ID with an API key you created. If Gmail doesn't answer, Recall tries that read again a few times over the next few minutes.
  • Recall stores the address of the Google account you connected, so imports keep using the same mailbox. On the Connectors page, owners and admins of your workspace see that you connected Gmail and when, not your address or your mailbox. But each imported message keeps that address in its details, and often in its To line, so anyone in the workspace who can read the message, including their agents, can see it.

How it's used

An imported message becomes a document in the container you chose: its subject, sender, recipients, date and text. Each PDF attachment, up to 20 MB, becomes a document of its own. Recall then pulls facts out of them like any other content, through the AI processing above. Members of that workspace can read these documents and their facts, and so can the AI agents they connect to the workspace with API keys or MCP, just like anything else added there. So only import into a container whose members you're happy to share the message with. Only you can search Gmail with your connection, and only you, or an API key you created, can import with it.

How it's protected

  • Google's access and refresh tokens are encrypted with AES-256-GCM before they're saved, using a key only the server holds, and each one is tied to your connection so it can't be reused for anyone else.
  • Connecting uses OAuth with PKCE and a short-lived, encrypted cookie.
  • Recall's own logs never contain mail content. Errors record only which step failed and the HTTP status. The LLM gateway's request log does keep the text sent to the model, which includes imported mail, for 30 days (see Where it's stored).

Sharing and limits

  • Google user data is never sold, never used for advertising and never used to build profiles for anyone else.
  • It's only passed on where that's needed to provide the import you asked for (the AI processing step above, and the members and agents of the workspace you imported into), to keep the service secure, or when the law requires it.
  • I don't read your Google data unless you ask me to look at specific messages (for example, to fix an import that failed), it's needed to investigate security problems or abuse, or the law requires it.
  • Recall doesn't use Google user data to develop, improve or train generalized AI or machine learning models.

Recall's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting and deleting Gmail data

  • On the Connectors page, open the menu on the Gmail card and choose Disconnect. Recall deletes the stored tokens straight away and asks Google to revoke its access. If Google doesn't confirm, the page tells you, so you can remove Recall at Google yourself.
  • You can also remove Recall from your Google account at myaccount.google.com/permissions. Leaving a workspace, or being removed from it, deletes your connection there too, but doesn't revoke it at Google, so remove Recall there as well.
  • Messages you already imported stay after you disconnect, until they're deleted. The email and each of its attachments are separate documents, and deleting one removes its stored text or file. Facts they produced are handled separately: deleting a fact on the Memories page hides it from search and agents, but keeps it in that fact's version history. To have every trace erased for good, write to [contact email to be added] and I'll do it within 30 days.

Who can see your data

  • Members of a workspace can see the content and facts in that workspace. Owners and admins also manage its members and API keys. An API key only ever sees its own workspace.
  • I run the server, so I can technically reach the database. I only do that to run, fix or secure Recall, or when you ask me to, and for Google user data only in the cases listed under Sharing and limits.
  • Services that handle data on Recall's behalf: Cloudflare (network, this site and backup storage), Anthropic (AI processing) and Google (only if you connect Gmail). No one else.

How long it's kept

  • Your account and content: until they're deleted. Edited or deleted facts stay in their version history until I erase them on request.
  • Imported Gmail messages: like any other content, they stay after you disconnect until they're deleted.
  • Sessions: until you sign out, or 7 days without use.
  • Gmail tokens: until you disconnect, connect again, leave the workspace or your account is deleted. If Google ends the grant first, the dead tokens stay encrypted until one of those happens.
  • The LLM gateway's request log: 30 days.
  • Backups: 30 days. Anything erased from Recall is gone from every backup 30 days later.

Your choices and deletion requests

In the dashboard you can edit or delete facts (old versions stay in their history), delete documents, revoke API keys and disconnect Gmail. For anything else, such as a copy of your data, a correction, or deleting your account and everything in it, write to [contact email to be added]. I'll reply within 30 days and confirm once it's done.

Security

Recall is only reachable over HTTPS. Passwords and API keys are stored as hashes, Google tokens are encrypted, and backups sit in a private bucket. No system is perfectly secure, so if I learn of a breach that affects your data, I'll tell you.

Children

Recall isn't meant for anyone under 13, and I don't knowingly invite them.

Changes to this policy

When this policy changes, I'll update this page and the date at the top. If a change affects how Google user data is used, I'll tell everyone who has connected Gmail first, and ask again where Google requires it. See also the terms of service.

Contact

Questions, requests or concerns about your data: [contact email to be added].