Privacy
What Raven collects, what it doesn’t, and where your data lives.
What Raven collects
Raven runs locally as an MCP server on your machine. It reads what you point it at — a URL, a screenshot, a DESIGN.md — and returns design findings. It writes an anonymous local usage log (which tools ran, how often, whether they succeeded) to your own machine. Nothing in that log is transmitted. RAVEN_NO_USAGE_LOG=1 turns it off.
What Raven does not collect
Your source code, design files, and screenshots never leave your machine, except when a tool you invoked explicitly reaches outward — see below. There is no analytics SDK, no telemetry beacon, and no account required to run Raven locally.
Taste Engine data
Taste profiles and decisions are stored locally at ~/.raven/taste. If you connect to the hosted endpoint at mcp.ravenmcp.ai, your taste data is stored per-user, keyed to your OAuth identity. The only personal data that identity carries is the email address and user ID your sign-in provider returns; it is used to keep your taste data separate from everyone else’s and for nothing else. Delete it any time with delete_taste_data, which removes the server-side record as well.
Who else touches your data
Two processors, on the hosted endpoint only: WorkOS (AuthKit) handles sign-in and holds your email address and user ID; Upstash (Redis) stores the taste data itself. Nothing is sold, and nothing is shared with anyone else. If you only run Raven locally, neither is involved.
Tools you invoke that reach outward — an audit of a URL you passed, a generation tool calling a provider you configured with your own API key — send data from your machine straight to that destination. Raven does not proxy or store those calls.
Retention
Local data — taste profiles, the usage log — lives on your machine and persists until you delete it or uninstall Raven. Nothing expires on its own. Hosted taste data persists until you delete it with delete_taste_data or ask us to; that removes the stored record.
Contact
andrew@ravenmcp.ai — or open an issue at github.com/rhinocap/raven-mcp/issues.
Last updated 25 July 2026.