What we store
Mindcache stores the minimum hosted product data needed to run accounts, sessions, playground workspaces, API access, billing records, and memory operations you explicitly trigger.
Privacy
Mindcache is built around isolated workspaces, explicit imports, and visible usage.
This page explains what the hosted service stores, when model providers may process content, and how that differs from the local runtime. It is meant to stay readable as the product evolves.
Last updated: April 2, 2026
Workspace isolation
Hosted playground memory lives inside isolated workspaces. That isolation exists so your imported memory is not mixed into another user's graph, retrieval flow, or digest layer.
Model processing
When extraction, embedding, retrieval support, or digest uses an external model provider, the relevant input for that operation may be sent to that provider. Mindcache also records model usage metadata such as provider, model name, token counts, and timestamps.
Billing records
Mindcache stores plan status, top-ups, usage events, token counts, and estimated cost data so limits can be enforced and usage can be shown back to the account owner.
Hosted vs local runtime
The hosted playground and the local CLI are different product surfaces. Hosted workspace data follows the hosted service rules on this page. Local runtime data stays in your own local database and filesystem unless you explicitly send it to a hosted or external model service.
Deletion and control
Inside the hosted playground, users can clear workspace memory. Some operational, security, and billing records may still be retained where needed for fraud prevention, debugging, financial reporting, or service continuity.
Third-party services
Mindcache may rely on third-party providers for payments, model inference, hosting, and related infrastructure. Those providers receive only the data necessary to perform the service they are responsible for.
Contact
For privacy or data handling questions, contact Mindcache at [email protected].
The short version: hosted Mindcache stores account, usage, and workspace data needed to operate the service. Local Mindcache data remains local unless you explicitly route it through a hosted or external service.
For plan limits and billing context, see Pricing. For hosted endpoints, see API.