Engram Privacy Policy

Effective September 23, 2026

This policy describes this self-hosted Engram service, operated by its instance administrator. It explains what data this instance handles when you use it, including when you connect a Google account.

Information you provide

Engram stores the notes, documents, memories, and account details you submit to this instance. Its operational records may include connector configuration, sync status, and security audit events.

Google user data and Gmail

If you connect Gmail, Engram requests only the gmail.readonly permission. It uses that permission to read messages that match the search query and labels you selected. For those messages, it processes the Gmail address, message and thread identifiers, sender, subject, date, labels, snippet, and message body. It does not import attachments or send, modify, label, archive, or delete messages.

The message text is stored as a Engram source document so you can search it and, if enabled, analyze it into suggested memories for review. Engram does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Processing uses the AI and embedding services configured for this self-hosted instance; its default model service runs alongside Engram.

Engram stores the Google refresh token encrypted in its database using AES-256-GCM. The token is used to obtain access tokens for scheduled read-only syncs and is not returned by the Engram API.

Storage, access, and sharing

This instance stores application data in its configured database and object storage on the Engram deployment. The instance administrator can access and administer that data. Administrators may maintain backups under their own retention and security controls. Google data is shared only as needed with Google to authorize and retrieve the messages you selected, and with the services configured to operate this Engram instance.

Retention and deletion

Disconnecting Gmail stops future syncs and asks Google to revoke the stored token. Disconnecting does not delete messages already imported into Engram or memories you accepted from them. Remove those source documents and memories in Engram, and contact the instance administrator for account or instance-level deletion requests. Administrators' backups may retain data until their normal backup retention period ends. You can also review or revoke Engram's access from your Google Account security settings.

Security

The instance uses access controls and encrypts Google refresh tokens before storing them. No internet service can guarantee absolute security; protect your Engram account and contact the instance administrator if you suspect unauthorized access.

Changes and contact

This policy may be updated when the service or its data practices change. For questions or deletion requests, contact the Engram instance administrator using the support address shown on the Google OAuth consent screen.

Engram's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.