Memory Usage Terms

1What a Memory Is

Echo works with several distinct kinds of data, and different controls apply to each:

• Source content — raw conversations, uploaded files, notes, prompts, and outputs that you provide or that Echo captures at your direction.
• Extracted memories — the memories, summaries, and structured records Echo generates from source content.
• Embeddings and indexes — vector representations and search indexes derived from your content to make it retrievable.
• Visibility and relationship data — whether a memory is private, friend-gated, or public, and any friend or connection relationships you establish.
• Metadata — timestamps, source linkage, the surface a memory came from, and similar contextual information.

You own all of these as User Content under the Terms of Use. Echo receives only the limited license described there to operate the Service.

2Memory Is User-Directed

Echo captures and writes memory in response to your actions and settings — not by independently monitoring you. A durable memory write occurs when Echo stores content in a way that persists in your account. Because some surfaces (particularly agent-driven ones) can trigger writes quickly, these Memory Terms explain, for each surface, when a durable write happens and what consent it requires.

Before any durable memory write, you must have accepted the current Terms of Use, Privacy Policy, and these Memory Terms, and confirmed that you meet the age requirement in the Terms of Use.

3Memories Are Private by Default

Every memory is private by default. Private memories are used to serve you.

Making a memory public, friend-gated, or otherwise shareable requires a separate, affirmative action by you. When you share a memory:

• you represent that you have the right to share it and to share any third-party information it contains;
• you understand it may be viewed, copied, saved, or used by others according to the visibility setting you select;
• Echo may record the share and subsequent access in an audit trail; and
• you can change the visibility or unshare it, subject to technical and legal limits — content already viewed, copied, saved, or delivered to others may persist.

4Your Responsibility for Memory Content

You are responsible for what you save, extract, sync, share, and rely on. You represent and warrant that you have all rights, permissions, consents, notices, and lawful bases needed for Echo to capture, store, extract, index, retrieve, and (where you direct) share your memories, including where they involve other people.

You will not use Echo to store or process restricted or sensitive data except as permitted, as described in Section 8.

5Memory Accuracy and Reliance

Extracted memories are automated interpretations of your content. They may be inaccurate, incomplete, outdated, duplicated, overcompressed, or missing context. Echo does not guarantee that any memory is complete, accurate, current, lawful, or suitable for any purpose. You should verify memories before relying on them, and you may not rely on Echo as the sole basis for any material decision, as described in the Terms of Use.

6Surface-Specific Memory Terms

The following terms apply to each surface in addition to the general terms above.

6.1 Echo Chrome Extension

The Extension’s single purpose is user-directed memory capture from supported AI chat providers into your Echo account, so that memories can be extracted, given provenance, and searched. The supported providers are ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), DeepSeek, Grok (xAI), and Perplexity.

How Echo accesses your conversations. When you connect a provider, the Extension uses your existing logged-in session with that provider (for example, your session cookie or access token already present in your browser) to access your conversations with that provider on your behalf. To let you choose what to save, the Extension reads the list of your conversations with that provider, which may include your full conversation history with that provider. You then select which conversations to extract into memories.

• You connect each provider individually, and each supported provider has its own toggle.
• You will see an indicator when the Extension is active.
• Access in incognito or private-browsing contexts is off by default.
• When you extract a conversation, Echo stores both the extracted memories and the source conversation, to enable re-extraction, provenance, source references, and regenerating memories for your account.
• You are responsible for what you extract. Do not extract conversations containing passwords, payment details, secrets, or other data you do not want stored.
• Data captured by the Extension is not used for personalized advertising, data brokerage, creditworthiness or lending decisions, or unrelated profiling, consistent with the Chrome Web Store Limited Use requirements.

Provider independence and your responsibility. Each provider (OpenAI, Anthropic, Google, DeepSeek, xAI, Perplexity) is independent of Echo, and Echo is not affiliated with or endorsed by them. You access only your own accounts and your own content through your own session, your use of each provider remains governed by that provider’s own terms, and you are responsible for your compliance with those terms. A provider may change its service, restrict access, rate-limit, or suspend your account, and Echo is not responsible for those consequences.

6.2 MCP Server / npm Package

The Echo MCP server (distributed as a user-installed npm package) lets you and agents you authorize save conversations, create and retrieve memories, search memories, manage visibility, and send or respond to friend requests.

The MCP server reads coding-session records that your local coding tools (for example, Codex CLI or Claude Code) write to your own machine, so that you can turn them into memories. It reads these local files on your device; it does not sign in to, or retrieve conversations from, any third-party provider account or service on your behalf. The optional Echo Context HUD is distributed in the same npm package and, while running, monitors supported local coding-session files to calculate context-health information. Local scoring does not create memories. If you invoke the HUD’s session-renewal or checkpoint action, the active session’s user and assistant text is sent to Echo and extracted into checkpoint memories stored under your account; tool calls, tool results, and thinking blocks are kept local and are not included in that upload.

• MCP memory writes default to private. Public or friend-gated visibility requires a separate action.
• MCP memory writes require prior acceptance of the Terms of Use and these Memory Terms. Because the MCP server reads local coding-session files on your device rather than connecting to a provider account, the per-provider connector consent in Section 7 does not apply to the MCP server; the Section 7 connector consent applies to surfaces that connect to a provider (such as the Chrome Extension).
• Because coding-session records can contain sensitive material such as source code, file paths, or credentials, you are responsible for what you make available to the MCP server, and you should avoid including secrets you do not want processed. As with all surfaces, content you save is processed to create memories, which includes sending content to third-party AI providers for extraction, as described in the Privacy Policy.
• MCP responses are designed not to expose private memories to anyone other than the authorized user. Access to public or friend-gated memories may be recorded in an audit trail.
• Friend requests show the target identity and relationship state and do not grant memory access unless and until the other user approves.

Because an agent can invoke MCP tools rapidly, you are responsible for the instructions you give agents and for the memory writes those instructions produce.

6.3 Echo Chat

Echo Chat uses your memories to personalize responses and may create or update memories from your conversations with it.

• Where feasible, you can see which memories informed a response.
• When Echo Chat creates a memory, you can review, correct, delete, or ignore it.
• Echo Chat presents memories as aides, not as verified facts, and does not provide regulated professional advice (legal, medical, financial, employment, housing, insurance, educational, or similar) based on memory.

6.4 EchoMem Web Platform

The web platform is where your memories, source content, visibility settings, relationships, and account controls are managed. Through the privacy dashboard you can, where supported, view, search, edit, correct, delete, and export memories, and see whether each memory is private, friend-gated, or public.

Where feasible, the platform shows source linkage so you can understand the relationship between a memory and its source, and what deleting each one does (see Section 9).

7Connectors and Third-Party Processing

You may connect Echo to Third-Party Services at your direction. Connecting a provider requires connector-specific consent — consent is granted per provider, not as a single blanket authorization, so connecting one provider (for example, ChatGPT) is a separate authorization from connecting another (for example, Claude). This applies wherever you connect a provider to your account, such as the Chrome Extension or the web platform. (The MCP server does not connect to provider accounts; it reads local coding-session files, as described in Section 6.2, and so does not involve connector consent.) When you connect a provider, you authorize Echo to access that source for the disclosed memory purpose, and you acknowledge that the provider operates under its own terms and privacy policy.

Per-provider acknowledgment at first connect. In the Chrome Extension, the first time you connect each of ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), DeepSeek, Grok (xAI), or Perplexity, Echo shows an acknowledgment before access begins — the extension’s presentation of the connector consent described above. By continuing, you confirm that you understand: Echo will use your existing logged-in session with that provider to access your conversations on your behalf, including reading your conversation list to let you choose what to extract; the provider is independent of Echo; you are accessing your own account and content through your own session; your use of the provider is governed by the provider’s own terms and you are responsible for complying with them; access may affect your provider account (for example, rate-limiting or suspension); and you can disconnect the provider and delete extracted data at any time.

To provide memory extraction, retrieval, and organization, content you direct Echo to process may be transmitted to third-party AI providers, as described in the Privacy Policy. You can disable a connector at any time. Echo may suspend or disable a connector to comply with law, a provider’s policies, a change in a provider’s terms, security requirements, or operational needs.

You are responsible for complying with the terms of any Third-Party Service you connect, and for ensuring you access only your own accounts and content. See the Terms of Use, Section 9.

8Restricted and Sensitive Memory Content

You may not store or process through Echo any personal information from or about anyone under 18. This is a strict condition of use.

In addition, unless expressly supported under a separate written agreement, you will not store or process through Echo: protected health information; payment card data; passwords, API keys, secrets, or access tokens; government-issued identifiers; biometric data; or precise geolocation data. Echo may block, quarantine, redact, or decline to process content it identifies as restricted.

9Memory Deletion, Retention, and Export

Your controls. You can delete individual memories and can request deletion of your account and associated data through supported interfaces, including the Echo website, the Chrome Extension, and Echo Chat. You can export your memories, and where applicable your source content and settings, in a machine-readable format. Deleting your account removes memory data from Echo’s active production systems, but does not by itself remove Context HUD files, preferences, or cached carryover/checkpoint text stored locally on your device; those are removed by quitting the Context HUD, disabling launch at login, and removing the local Echo files.

What deleting a memory does. Deleting a memory deletes that memory and the embeddings and indexes derived from it. Because a single source conversation may relate to multiple memories, deleting a memory does not delete the source conversation it was extracted from.

What deleting your account does. Deleting your account runs a cascaded deletion process that removes, from active production systems, the data Echo holds about you, including your source conversations, extracted memories, embeddings and indexes, derived data, and sharing and visibility records.

Content you shared with others. Deleting your account does not delete messages or memories you previously shared with or sent to other users. Content already delivered to another user, including messages in paired or friend exchanges, may remain in that user’s account after your deletion.

Deleting a specific source. To delete a specific source conversation on its own (without deleting your account), you can contact us at [email protected] and we will delete it within the timeframe required by applicable law (generally within 45 days).

How your content is stored. Your memories and source conversations are stored in our secured database, which uses access controls and other protections. You can also enable optional encryption for an additional layer of protection at rest: if you turn it on, you set a key, and your content is encrypted at rest using a key derived from it. Encryption is not enabled by default. In either case, to create and organize memories your content is processed in readable form by Echo and by third-party AI providers, and the Service is not end-to-end encrypted. See the Privacy Policy for details.

Retention. Memories and source content are retained until you delete them (or, for source content, until account deletion) or disable the relevant feature. When you delete your account or make a verified deletion request, Echo acts on it promptly and removes data from active production systems without undue delay, and in any case within the timeframe required by applicable law (generally within 45 days). Deletion is not instantaneous everywhere: residual copies may persist in backups, provider logs, and abuse-monitoring systems for limited periods before automatic expiration. Retention periods for each of these are stated in the Privacy Policy.

10Enforcement

Echo may remove content, restrict memory extraction, disable connectors, adjust or remove sharing, suspend, or terminate access where memory content or conduct violates law, a Third-Party Service’s terms, these Memory Terms, the Terms of Use, security requirements, or the rights of others, as further described in the Terms of Use.

11Changes to These Memory Terms

Echo may update these Memory Terms as the Service and surfaces change. Material changes will be notified as described in the Terms of Use, and where appropriate Echo will seek renewed acceptance before continued memory writes.

12Relationship to Other Documents

These Memory Terms operate together with the Terms of Use and the Privacy Policy. The Privacy Policy governs how personal information is collected, used, shared, and protected, including the specific third-party recipients of content. The Terms of Use govern the overall contract, including disclaimers, liability, indemnification, and dispute resolution. These Memory Terms govern memory capture, storage, sharing, and processing across surfaces.