Privacy Policy

Last updated: August 14, 2026

Ontonym (“we”, “us”) provides shared, structured memories that AI clients read and write over the Model Context Protocol (MCP). This policy describes what we collect, how we use it, and what we never do with it.

What we collect

  • Account data — your email address and a hashed password (or the identity your sign-in provider asserts).
  • Memory content— what you or your AI clients deliberately ingest into a memory: structured objects and relationships submitted over MCP, emails you forward to your memory's ingestion address, content from connectors you authorize (for example Gmail), and pages fetched by crawl schedules you create.
  • Credentials you create— MCP keys and OAuth tokens minted when you connect an AI client. For source connectors you authorize, we hold the provider's OAuth token so scheduled syncs can run.
  • Billing data — handled by Stripe; we never see or store card numbers.
  • Operational logs — request logs (IP address, request IDs, timestamps) kept for security, rate limiting, and debugging.

What we do with it

  • We store your memory content to serve it back to you, your team, and the AI clients you connect. That is the product.
  • Extraction over MCP runs on your model — your raw conversation never passes through an LLM we operate. Server-side automations you enable (email forwarding, connector syncs, scheduled crawls, agents) run on the model key you configure for your workspace.
  • Memories are private by default: only members you add can read them. A memory becomes publicly readable only if its owner explicitly marks it public.

What we never do

  • We do not sell your data or share it with advertisers.
  • We do not train AI models on your content.
  • We never send your memory content to analytics services.

Cookies & analytics

We set one cookie of our own: the session cookie that keeps you signed in. We also use Google Analytics to understand aggregate site usage (pages visited, rough geography, client type); it sets its own cookies and receives standard browsing events from our pages — never the contents of your memories.

Where it lives

Content and account data are stored on our servers in the United Kingdom (AWS, London region). Transport is TLS-encrypted end to end.

Subprocessors

Amazon Web Services (hosting), Stripe (payments), Resend (email delivery and inbound forwarding), Google Analytics (aggregate site usage), and the model provider whose API key you configure for your own workspace automations.

Retention & deletion

Your content stays until you delete it. Deleting an object, a memory, or your account removes the corresponding data from the live database; encrypted backups age out on a rolling schedule. Revoking an MCP key or OAuth token takes effect immediately.

Your choices

  • Revoke any connected AI client or key at Settings → MCP keys.
  • Disconnect source connectors at any time.
  • Make a public memory private again at any time.
  • Ask us to export or delete your data.

Contact

Questions or requests: support@ontonym.com. We'll update this page when our practices change and note the date above.