IDITOR, INC. · d/b/a ECHO
Subprocessor List
Echo engages the third parties below to help provide the Service. A subprocessor processes personal information or user content on Echo's behalf. This list supports the disclosures in our Privacy Policy, Terms of Use, and Memory Usage Terms. Retention windows reflect Echo's current plans and configurations and will be updated if these change.
User-connected AI accounts (your own ChatGPT, Claude, Gemini, DeepSeek, Grok, or Perplexity logins) are Connectors you control, not Echo subprocessors. The AI providers below are engaged by Echo to process content on Echo's behalf (embeddings and memory extraction).
Infrastructure and hosting
| Subprocessor | Purpose | Data processed | Location | Retention (Echo's plan) |
|---|---|---|---|---|
| Supabase | Primary database, authentication (including account/transactional emails such as verification and password reset), storage, realtime, vector/search data | Account data, authentication data, memories, source conversations, embeddings, metadata, and stored files | US (West US / N. California) | Active rows deleted per Echo workflow; daily backups retained 7 days (Pro plan, PITR off) |
| Vercel | Application hosting and serverless deployment (extension backend, web app) | Request metadata, function/runtime logs, operational telemetry. Raw user content is not written to logs or deployment artifacts. | US | Runtime logs ~1 day (Pro). Build logs / deployments retained by default — kept free of user content. |
| Cloudflare, Inc. | Domain registration and authoritative DNS; CDN and reverse proxy; TLS termination; caching; DDoS protection and WAF; HTTP traffic analysis; cookieless Web Analytics/RUM | Visitor IP addresses; request and connection metadata; headers; URL/path; timestamps; user-agent, browser/device and performance data; security signals; and website or API content routed through or cached on Cloudflare’s network | US provider; global edge network | Web Analytics retains unsampled beacon data ~7 days and aggregated analytics longer (dashboard access currently up to 6 months); other processing per Cloudflare’s configuration and DPA |
AI processing
| Subprocessor | Purpose | Data processed | Training? | Abuse-log retention |
|---|---|---|---|---|
| OpenAI | Embedding generation (/v1/embeddings) for memory search | Memory text / search text submitted for vector embedding | No (not used for training; no app-state retention; ZDR-eligible) | Up to 30 days |
| Google — Gemini / Vertex AI | Memory extraction, structured generation, classification, labels | Conversation text, extraction prompts, context, generated structured outputs | No (paid services / Vertex — not used to train Google's models) | Up to 55 days (paid Gemini abuse monitoring) |
Operational services
| Subprocessor | Purpose | Data processed | Scope | Consent / notes |
|---|---|---|---|---|
| Amplitude | Product and website usage analytics across Echo surfaces | Usage/interaction analytics (feature usage, navigation events). No memory content. | Chrome Extension, MCP, web platform, Echo Chat, and website (incl. consent-gated research pages) | Processor under DPA (incorporated into Amplitude ToS). Research-page analytics runs only after cookie consent; product analytics on app surfaces is first-party product operation, disclosed in the Privacy Policy. |
| Google — Firebase Crashlytics | Crash and error diagnostics for Echo Chat (app) | Crash/error diagnostic data (device/OS, stack traces, event metadata). No memory content. | Echo Chat app | Google/Firebase data-processing terms; crash/diagnostic data retained ~90 days (Firebase default). No memory content or precise identifiers. |
| Stripe | Payment processing for paid plans (website) | Payment card details (collected directly by Stripe, not through Echo); billing/transaction metadata. No memory content. | Website checkout | Processes under Stripe’s own terms; Echo does not store full card numbers |
How we manage subprocessors
We require subprocessors to protect personal information under obligations consistent with our commitments and applicable data-processing terms. We update this list when we add or remove a subprocessor or materially change how user content is processed or retained.