Privacy Policy

We collect account and contact details you provide, workspace and tenant identifiers, authentication metadata, support messages, and configuration needed to operate Eve.

When you use Eve, we process memory content, prompts, retrieved context, metadata, audit events, and diagnostic logs needed to store, search, inspect, and secure your managed memory.

We use information to provide the service, authenticate users and MCP clients, store and retrieve memories, show tenant controls, operate support workflows, detect abuse, improve reliability, and comply with legal obligations.

Eve may process memory content with AI and infrastructure providers so the product can extract, summarize, search, rank, and answer from user-visible memory context.

We do not sell personal information. We share information only with service providers that help operate Eve, with your organization administrators, when required by law, or to protect the service and its users.

AI and infrastructure providers listed here act as our subprocessors. Google is our AI subprocessor: memory extraction, summarization, ranking, and answer synthesis run on Google Gemini models (currently Gemini 3.6 Flash) via Google Cloud Vertex AI, which receives memory content, conversation transcripts, and summaries submitted for processing. Google Cloud Platform hosts the service and stores workspace data, including vector embeddings generated with Google embedding models.

We update this list as subprocessors change.

When you connect Eve to a coding agent or CLI, Eve receives and stores conversation transcripts, conversation summaries, and session logs. This includes content sent before context compaction, transcripts submitted for extraction, and session start and end records. This content is stored on Eve's servers, processed by the AI subprocessors listed above, and retained until you delete it or configured retention expires.

You can view stored data at any time from your Eve workspace at evemem.com/app, and delete conversation summaries, session logs, and episodic memory entries there. Semantic memory chunks can be deleted with the memory_forget tool. Deleted items are excluded from browse, search, and retrieval; residual copies may be retained in audit records consistent with the Security and retention section.

Eve uses access controls, tenant scoping, audit trails, transport security, and operational monitoring to protect managed memory data.

Memory records remain available until deleted, expired by configured retention, or removed through an audited support or admin workflow. Operational logs may be retained for security, reliability, and compliance needs.

You may request access, correction, export, or deletion of personal information associated with your account or workspace, subject to security checks and organization controls.

For privacy requests, contact support@evemem.com.