Security & compliance

Supermemory stores long-horizon context about people and organizations. Security and compliance are part of the product surface, not a footer claim. This page is the product-level trust overview. For multi-tenant design details, see Namespaces and authentication docs in the Developer Platform.

​

Compliance posture

Need a report, DPA, or BAA? Contact support@supermemory.com or your enterprise contact.

​

Security controls

​

Encryption

• In transit: TLS for API and console traffic
• At rest: Industry-standard encryption for stored data (AES-256 class controls in the managed cloud)

​

Isolation and access

• Namespaces (what v3/v4 called container tags) enforce hard boundaries between users, tenants, or projects — the primary multi-tenancy primitive.
• API keys authenticate every request. Prefer scoped keys when a client or session must only touch one namespace.
• Organizations in the console manage members, keys, and billing separation.

A malicious or buggy client with a correctly scoped key cannot read another namespace’s memories.

​

Data use

Supermemory is infrastructure for your agents. Your customer content is never used to train models — this applies to every plan, free or paid, with no difference between them. For contractual wording (DPA, subprocessors, training policies), request the latest legal pack from support.

​

Data residency and deployment options

• Managed cloud — default multi-tenant SaaS.
• Self-hosted binary — the engine, storage, and default local embeddings run on your machine or VPC. If you configure remote LLM or embedding providers, their processing inputs are sent to those providers. See Self-hosting.
• Enterprise / dedicated — for stricter residency, air-gap, or custom deployment requirements. See Local vs Enterprise.

​

Privacy operations you should design for

​

Deleting a user (right to erasure)

The practical GDPR-style path for app builders:

1. Scope each end-user (or tenant) to a namespace.
2. When the user requests deletion, use DELETE /ns/{namespace} with an org admin or owner credential that has write access. It deletes the namespace, its namespace-owned memory records, and documents exclusive to it; documents shared with other namespaces are retained. The default sm_project_default namespace cannot be deleted.
3. Revoke any scoped keys issued for that user.

Designing isolation up front still makes identifying the user’s content easier.

​

Connectors and third-party sources

OAuth connectors (Drive, Notion, Gmail, and others) pull content your users authorize. Disconnecting a connector stops future sync; you still control whether already-ingested documents remain in the memory store. Treat connector scope and retention as part of your product privacy policy.

​

Self-host when cloud is not enough

If policy requires data never leave your network, run the self-hosted engine. You bring the model endpoint (including fully offline OpenAI-compatible local models). Enterprise adds managed on-prem / dedicated options with organizational controls.

​

Reliability and support

• Status and incidents are communicated through Supermemory’s status and support channels.
• Support depth scales with plan (community → email → priority → dedicated enterprise).
• Latency targets for retrieval are in the ~sub-300ms p50 range on the managed platform for typical search workloads; always validate on your traffic shape.

​

Related