---
title: "Privacy · Mentat"
description: "What Mentat stores, what it does not, and what leaves your machine."
url: https://trymentat.pages.dev/privacy
---

Privacy

# Privacy

Last updated 25 July 2026.

## The short version

Mentat stores constraints, not conversations. When a session transcript is mined for decisions, the extracted constraint, its justification, its scope, and a pointer back to the session are kept. The transcript itself is not uploaded and not retained.

## Local by default

The CLI keeps your graph in .mentat/graph.json inside your own repository. Nothing is transmitted unless you create a hosted workspace or point an agent at the hosted MCP endpoint.

## Hosted workspaces

A hosted workspace holds your decision graph and an append-only event log of resolutions. Authentication is a bearer token; we store only its SHA-256 hash and cannot recover the original. Losing the key means losing access to that graph, which is the tradeoff for having no signup form.

## The demo graph

Requests without a token resolve against a fixed, read-only demo graph. Those requests are rate limited by IP address in ephemeral storage and are not otherwise logged.

## Model calls

When an Anthropic API key is configured, two constraint texts plus their justifications and scopes may be sent to Anthropic for adjudication, and transcript text may be sent for extraction. With no key configured, no request leaves the Worker and the deterministic path runs instead. Mentat never trains on your data.

## Deleting things

Delete a local graph by deleting the file. For a hosted workspace, email karthik \[dot\] subramanian \[at\] berkeley \[dot\] edu with the workspace id and it is removed along with its event log.

---

Mentat: https://trymentat.pages.dev/ · Docs: https://trymentat.pages.dev/docs · Developers: https://trymentat.pages.dev/developers · API: https://trymentat.pages.dev/openapi.json · Index for agents: https://trymentat.pages.dev/llms.txt
