Privacy policy.

Last updated: 27 October 2026. SyntheticMem is a preview service operated by autoaidev.

1. What this covers

This policy describes the SyntheticMem website and service at syntheticmem.com, including the landing pages, the MCP server (/api/mcp), the REST API (/api/v1) and the dashboard (/app). It does not cover third-party AI clients you connect from, which have their own policies.

2. Agent data we store

• Memories. The content you send with memory_remember and the provenance metadata attached to it (source, timestamps, namespace, confidence, invalidation tag and condition, status), plus a locally-computed embedding vector. This is stored so we can return it on recall.
• Agents and keys. An agent record and its API keys. Keys are stored only as salted hashes — we cannot recover the plaintext of a key after it is shown to you once.
• Account. If you register, the account identifier used to sign in (for example, an email address or OAuth identifier) so your agents can be linked to you.
• Operational logs. Standard request logs may record IP address and timing for security, rate-limiting and debugging.

3. Ephemeral (24-hour) data

Memories written with an anonymous demo key — one that is not linked to a registered account — are ephemeral: they are automatically deleted within 24 hours by a scheduled prune. Demo keys are rate-limited and share a capped pool. Register and link an agent for permanent memory.

4. Where embeddings are computed

Embeddings are generated locally on our server using Ollama (the nomic-embed-text model). Your memory text is not sent to any third-party embedding provider for indexing.

5. Analytics and cookies

The marketing website uses two analytics tools to understand aggregate usage:

• Google Analytics 4 (Google) — sets cookies and collects usage events such as page views and approximate location. See Google's privacy policy for details.
• Microsoft Clarity (Microsoft) — sets cookies and records aggregate interaction analytics such as heatmaps and session trends. See Microsoft's privacy statement for details.

You can block or clear these cookies in your browser settings, or use a browser-level analytics/opt-out control. The MCP and REST endpoints themselves do not set analytics cookies.

6. How we use data

We use the data above only to operate the service: to store and return your memories, to authenticate agents, to keep the demo available via rate-limiting, to secure and debug the service, and to understand aggregate website usage. We do not sell your data, and we do not use your stored memory content to train models.

7. Revoking and deleting

• Revoke a key: registered users revoke per-agent keys from the dashboard at /app; a revoked key stops working immediately.
• Delete memories: use memory_forget to retire a memory, or delete agents and their memories from the dashboard.
• Demo data: expires automatically within 24 hours; no action needed.
• Account deletion / other requests: open an issue at github.com/autoaidev/syntheticmem-app/issues.

8. Changes

As a preview service this policy may change. Material changes will be reflected here with a new "last updated" date.

See also the Terms of Service and the FAQ.