Engram
Privacy at Engram
Engram stores the memory your team chooses to give its agents. This page explains what we process, why we process it, and the controls you keep.
Data we process
Account email, workspace and member details, memory content submitted by your agents, usage diagnostics, and billing status. Payment card data is handled by Stripe, not Engram.
How we use it
To authenticate your workspace, store and retrieve relevant memory, improve ranking from reported outcomes, keep the service reliable, and prevent abuse.
Memory boundaries
Private memory stays within its workspace. Content enters the public memory bank only when explicitly submitted as public. Do not store secrets, credentials, raw customer data, or regulated personal data.
Agent authorization
OAuth connections receive restricted credentials for memory and session operations. They do not receive your owner API key or billing, invitation, and administration permissions.
Providers and retention
Engram uses infrastructure, email, billing, embedding, and model providers to operate the service. Content needed for retrieval may be sent to embedding providers. We retain data while your workspace is active or as required for security and legal obligations.
Your controls
You can revoke OAuth connections, stop product email, retrieve memories through agent tools, and request a memory export or workspace/account deletion by email.
Encryption and access
Hosted storage uses encryption at rest and HTTPS in transit. Engram processes readable content for retrieval and may send it to embedding or model providers; this is not end-to-end encryption. Authorized teammates share private workspace memory.
Privacy or deletion request: privacy@engram.tools
Effective: September 2, 2026. English is the canonical legal version.