Privacy

MemIndex records agent activity so it can help in later sessions. Choose where that memory lives and what work you let it capture.

What can be kept

Memory includes saved prompts, notes, and session summaries. Capture can also include tool inputs and results, filenames, project details, and session records. Endless Mode can write a local record of a Claude Code conversation.

With a local setup, these files live on your computer. This does not mean every step stays offline. Writing notes sends activity to the model service you choose, under that service's terms.

If that service cannot write notes, the local setup can send the work to a fallback service. The default fallback uses your Anthropic login or API key when available. To turn fallback off, add "MEMINDEX_QUOTA_FALLBACK_PROVIDER": "off" to your existing settings file. Fallback usage can have its own cost or plan limit.

With MemIndex hosting, activity and memory are sent to our server. To write notes, our server sends that activity through OpenRouter to the model that writes them (an OpenAI model today).

Mark content private

Private tags filter text from saved memory notes. They are not a general boundary for protecting secrets. Local pending files and the agent's own history may still hold the activity.

Wrap the text in a complete pair of tags:

<private>
A temporary detail to leave out of saved notes.
</private>

MemIndex removes these blocks when it prepares captured text for memory. The tags do not hide text from the agent's current conversation or erase the agent's own saved conversation files. Always close the tag.

Treat the MemIndex data folder as sensitive, even when you use private tags.

Leave out a project

The local capture settings support project exclusions. Add MEMINDEX_EXCLUDED_PROJECTS to the existing ~/.memindex/settings.json object. Its value is a comma-separated list of folder patterns. For example:

{
  "MEMINDEX_EXCLUDED_PROJECTS": "confidential-project"
}

This example matches a project folder by name. Add the entry to your settings; do not replace the whole file with the example. Exclusions stop new capture in supported paths. They do not erase earlier memory. Check your integration's behavior before working with sensitive material.

Optional secret filtering

Automatic secret filtering is off by default. To turn it on, add this entry to the same settings file:

{
  "MEMINDEX_REDACT_ENABLED": "true"
}

It replaces recognized secret patterns with a marker. It cannot recognize every secret. It does not encrypt your memory or clean an agent's own history. With hosting, we set this on our server; it is not a separate setting for each team.

Usage reporting

Usage reporting is off by default. The package ships without an analytics key. Sending reports requires both your own analytics key and an explicit choice to enable reporting.

Check or turn it off with:

npx memindex telemetry status
npx memindex telemetry disable

If enabled, reporting can include system details, counts, timings, and scrubbed error information. It is separate from sending work to the model that writes notes.

Who can read your memory on this computer

MemIndex runs a small service on your computer. Other programs on the same machine can reach it, so reading your notes needs a private install secret, just as changing them does. MemIndex creates the secret once. It is the worker-secret file in your data folder (~/.memindex unless you changed MEMINDEX_DATA_DIR), and only your user account can read that file.

A request without the secret gets a 401 answer and sees no notes. Only the health and readiness checks stay open, and they show no memory.

Your agent's hooks, the search tools, the command line, and the viewer send the secret for you. To open the viewer, use the link MemIndex prints when a session starts. A plain localhost address still loads the page, but it shows a notice that it was not let in and no notes. Observation TV on this computer works the same way. A remote Observation TV that sends your MEMINDEX_TV_TOKEN is not affected.

If you wrote your own script that calls the service, send the secret in an X-Memindex-Secret header. This keeps it off the command line, where other programs could see it. Use the address and port from npx memindex doctor:

printf 'X-Memindex-Secret: %s\n' "$(cat ~/.memindex/worker-secret)" | curl -H @- http://127.0.0.1:PORT/api/stats

Your tools also check that the program answering on that port is really your MemIndex before they send it anything. It must prove that it holds the same secret, without the secret ever being sent to it first. If another program has taken the port, for example while MemIndex was restarting, it gets neither the secret nor your notes; your notes wait on disk until MemIndex answers again. A page served from another local port, such as a development server, cannot read your notes from the browser either: only the viewer page MemIndex serves itself is let in, plus any origin you list in MEMINDEX_ALLOWED_ORIGINS.

Keep the secret and your private viewer link out of anything you share. Tools that were already running before you upgraded keep their old behavior until you restart them. If one reports that reading memory needs the install secret, restart it or run npx memindex update. See Troubleshooting.

Access and deletion

Keep server keys and private connection links out of public code and screenshots. Server access is limited by the key, team membership, and project. See team memory.

The local viewer lets you inspect memory and delete individual notes. Changes need the private viewer link printed by the installer; opening the service address alone does not authorize them. The server supports deleting a note and, for owners and admins, clearing a project's memory. Exports contain saved memory; store them privately.

Deleting memory is not a promise that all copies are gone. Agent histories, exports, pending files, and backups need separate care. Ask MemIndex how long hosted backups keep deleted data before relying on deletion for that purpose.

For privacy questions, contact [email protected]. For your account, contact [email protected].