Localmem
Privacy
Your memories live on your Mac. There is no Localmem account, no Localmem server, and no telemetry.
Localmem stores everything in a SQLite database under ~/Library/Application Support/Localmem/, on your machine. We do not operate a backend that holds your data, so there is nothing for us to read, lose, subpoena, or sell. This page lists every connection the software makes, so you can check that claim rather than take it.
What leaves your machine
Two connections, both to GitHub, both about software updates:
| Connection | When | What it sends |
|---|---|---|
api.github.com/…/releases |
When you press Check for Updates — or once every 24 hours at launch, if you left automatic checks on during setup | Nothing but the request itself. GitHub sees your IP address and the app version in the user agent. |
| The release download URL | When you press Download Update | The same. This is the same file you would download from the releases page by hand. |
That is the entire list. An update check is a question, not a report: it asks whether a newer version exists and transmits nothing about you beyond what opening any HTTPS connection reveals. The localmem command-line tool and the localmem-mcp server make no network connections at all.
Automatic checking is your choice, and we ask up front. The setup wizard offers it on the same screen as Touch ID. Turn it off there — or later in Settings — and no check ever runs on a timer; the only connections left are the ones behind a button you press. Nothing is checked before you have answered that question.
Importing files, and AI agents
Localmem can read files you select and extract memories from them. How that extraction happens determines whether anything leaves your Mac, so you choose the engine before you choose the files:
- Apple Foundation Models (preferred, and the default where supported) runs on-device. Nothing leaves your Mac.
- A coding agent you have already installed — Claude Code or Codex — runs the extraction through that tool. The text of the files you selected is sent to that agent's provider, under your existing relationship with them and their privacy policy, not ours.
Localmem never calls a model API itself and never holds an API key. There is no silent fallback: if the on-device model is unavailable, Localmem tells you which agent would read your files and waits for you to agree. Agent extraction runs headless, as a plain text-to-text call with tools disabled and MCP configuration stripped out.
What never leaves your machine
- The content, titles, and tags of your memories
- Your folder names, agent names, and visibility rules
- Your searches, and how many memories you have
- The access history — which agent read or wrote what, and when
- File paths, project names, and anything else about your machine
There is no analytics package, no crash reporter, no usage counter, and no unique identifier of any kind in Localmem.
This website
localmem.ai is a static page hosted on Vercel. It sets no cookies, runs no analytics, and embeds no trackers. Vercel keeps standard web-server request logs, which include IP addresses, as any web host does. The fonts on this page are served by Google Fonts, which sees the request that fetches them.
Changes to this page
The list above is not marketing copy — it is a rule we hold ourselves to in the codebase. Localmem's design document requires that any new network connection be written into that table before it ships, and a change that cannot be described as a row there is treated as a change to the product's promise. You can read the current version in §5 of the technical design, and the source for all of it is on GitHub.
Questions
Open an issue at github.com/localmemai/localmem-app.
Last updated 9 August 2026.