Who operates Engram
Outcome Driven Holdings LLC operates the hosted service at engram.ani.computer and is responsible for its handling of your information. Contact ani@odstdio.com for privacy requests, account or workspace deletion, and support. We aim to acknowledge requests within two business days.
This notice covers our hosted service. A self-hosted installation is operated by whoever runs it; their privacy and retention choices apply.
What we store and why
We store the memory and activity you or your agents submit, workspace names and settings, member email addresses, connection and access records, billing references, and onboarding-email progress, delivery records, and unsubscribe preferences. We use these to run your workspace, authenticate people and agents, deliver sign-in, invitation, and onboarding emails, manage subscriptions, resolve support requests, and protect the service.
Memory access, memberships, and credentials are scoped to the workspace. Activity, billing, and access records in the shared control database are scoped to the workspace. People and agents in a shared workspace can read its shared data; a personal workspace is separate. The Sharing screen proposes excerpts from a natural-language instruction and requires explicit approval of each exact excerpt. Approved snapshots are stored separately; new or changed memories need a fresh review. Teams can read approved snapshots alongside their other team memory. An isolated agent credential reads only its snapshots at /mcp/shared; existing broader connections keep their access unless separately disconnected or revoked. Temporary previews, instructions, and approved excerpts are stored in sharing records. Used preview text is cleared, and expired owner previews are cleaned on a later preview request; this is not scheduled deletion. Legacy standing rules have separate matching and copying behavior. Workspace owners manage membership and agent access. Read the sharing boundaries.
Engram observes calls to its own tools. Other agent actions appear when an agent or integration reports them. Connecting an agent does not automatically collect all of its conversations or tool use. A connected agent receives the workspace results it requests and handles them under its own service’s terms.
Optional AI has separate permissions
Core memory storage, keyword search, and activity history work without sending your content to an AI provider. New workspaces start with optional processing off. A workspace owner can opt in through Workspace settings.
Jev has its own permission. When allowed, configured, and eligible, it sends relevant query text, bounded memory context, and activity context to TypeSafe for optional routing, ranking, and review suggestions. Enabling Jev does not enable Voyage embeddings or OpenAI briefs. Embeddings and generated briefs have a separate permission: configured Voyage can receive relevant text and queries for embeddings, and OpenAI can receive bounded activity context for optional generated briefs.
Provider terms and retention apply to information they receive. Turning a permission off stops new calls covered by that permission; it cannot recall information already sent, and a call already in flight may finish. We do not promise zero retention or a particular training policy on behalf of another provider.
Hosted Jev usage records include the workspace, model, task category, token counts, call status, cost, and billing references. These support usage reporting, budgets, and billing. Customer billing requires a paid subscription and explicit acceptance of the displayed rate; operator-funded workspaces receive no Jev usage charge. Read the usage and soft-budget details.
Hosting, payments, email, and cookies
Google Cloud hosts the service and database, and Cloudflare handles edge traffic. Hosting and security infrastructure may process IP addresses, request metadata, and diagnostic logs. The app’s bundled scripts do not include advertising pixels or third-party analytics; its scripts, icons, and fonts are served with the app. Engram counts its own page visits, a few button clicks (such as asking for an invite) and sign-up submissions, with the referring site and campaign tags. It uses no cookies, stores no IP address or email with these counts, and identifies a visitor only by a code that changes every day. Your browser tab remembers the campaign you arrived from until the tab closes. Do Not Track and Global Privacy Control turn this counting off. Counts are kept for up to 13 months.
A session cookie keeps you signed in. The browser can also keep non-sensitive interface preferences, such as dismissing the getting started guide. Agent access keys are shown when created and are not stored in browser storage by the app.
Stripe collects payment and billing information. Engram sends workspace/customer references to associate a subscription, without memory, activity content, or agent transcripts. Resend delivers hosted sign-in, invitation, and onboarding emails, including the recipient address and message. Invitations identify the workspace and inviter; onboarding emails can identify your workspace and use completion checks to choose a useful next step. We do not include private memory or activity contents in onboarding emails, and we do not add open-tracking pixels. You can stop the onboarding series through the unsubscribe link in any of its emails; requested sign-in and security emails continue. These services have their own privacy and retention terms.
Public sharing is a deliberate choice
Your activity profile starts unpublished. A workspace owner chooses its name, bio, and address before publishing. Profiles share aggregate counts, dates, and broad tool categories by default. The owner can separately enable a redacted activity stream showing agent products, services, broad action labels, status, evidence, and receipt times. The preview shows the selected sharing scope before saving.
Public action labels come from fixed operation types, not private task text. Private memory, personal agent aliases, repository and document names, resource URLs, action details, and transcripts are excluded. Existing profiles keep the activity-stream option off until their owner enables it.
Unpublishing removes public access from Engram. It cannot recall copies already exported, shared to another workspace, or downloaded by social networks and other third parties.
How long information stays
Workspace memory, activity, and account/access records are retained until you request their removal. There is no automatic cleanup of inactive workspaces or activity history. Ending a trial or canceling a subscription does not erase your data; existing data remains readable and exportable.
Deleting a memory page in the app is recoverable soft deletion. It is not permanent erasure and does not remove associated activity, access records, or copies already shared elsewhere.
The hosted database keeps a rolling set of 14 automated backup copies and seven days of transaction logs for recovery. Fourteen backup copies is a count setting, not a guarantee that every deleted record disappears after 14 days. Earlier data can remain in recovery copies until they are replaced or removed. On-demand release/recovery backups are retained separately and can last longer.
The default Google Cloud application-log bucket is configured for 30 days of retention. This does not describe every security, system, or edge log, or records held by payment and email providers. We identify relevant retention exceptions when handling an erasure request.
Access, correction, and deletion requests
You can export the memory and activity your account can read from Workspace settings. Store the export carefully; it contains private data. For help accessing or correcting information, or to request account/workspace erasure, email ani@odstdio.com. Include your workspace name and account email, without tokens, passwords, or private memory contents.
There is no self-service account or workspace erasure button. An operator verifies your authority and processes the request manually, including the scope of shared-workspace information. Our target is to complete an approved request in the active service within 30 days after verification. We explain delays and any information retained for security, disputes, or accounting. Recovery copies expire or are removed separately; they are not used for ordinary workspace access. If we restore a backup, we reapply recorded erasure requests before returning restored data to service.
Security and self-hosting
The gateway must read workspace content to serve it, and an infrastructure administrator can access underlying storage and backups. Hosted data is not cryptographically isolated from the service operator. Engram does not promise absolute security, end-to-end encryption, or a compliance certification.
Self-hosting puts the infrastructure, backups, network security, and optional service keys under your operator’s control. See the self-hosting guide. For a security report, contact ani@odstdio.com privately; do not send live credentials or another person’s data.