ISOLATION
Separate personal contexts
A person’s records belong in their own context, with boundaries between accounts.
We are building the memory foundation for privacy-first AI agents. Zelo is the first application; continuity across other apps and channels is our longer-term vision.
01 / Privacy
Protection is a system of decisions: who gets access, how long data stays, and what a model is allowed to learn.
01 / PERSONAL CONTEXT
The agent’s memory should serve the person it belongs to, with clear boundaries around access and use.
02 / DATA
What is kept, what reaches an AI provider and what can be removed are decisions at the heart of the product.
03 / DEVELOPMENT
Zelo is in development. Bloom and connections to external assistants and channels are planned.
04 / Limits
Participation in an ecosystem should come with explicit boundaries for what each participant can access.
05 / CONTEXT
A useful response needs context. Explain which information is used and why it is relevant.
06 / CONTINUITY
Our vision is for private memory to remain useful as a person moves between apps, assistants, messages and calls.
02 / The Ring — Persistent memory
A useful AI product can carry relevant context from one interaction to the next. Facts remain connected to sources, so people can understand and correct what is remembered. Facts, sources, dates, documents, and what is due next. The Ring keeps a structured memory of the subject your companion serves.
Every fact is a line you can read, dismiss, restore, and export.
The memory foundation is under development for Zelo. The broader architecture describes where we want to take personal agents.

FIRST INTERACTION
Start with the subject, the question and the information a person provides.
OVER TIME
Carry relevant records and their sources forward instead of relying on a single conversation.
NEXT INTERACTION
Use that history to inform the response, while keeping the record open to inspection.
SESSION
RECENT PATTERNS
PERMANENT ARCHIVE
03 / How it works
The principles guiding our development: private personal context, useful memory and clear boundaries. Availability will be described for each product as it launches.
ISOLATION
A person’s records belong in their own context, with boundaries between accounts.
DATA LIFECYCLE
Design memory so the person can understand what is kept and how to correct or remove it.
MODEL TRAINING
Our commitment is to build personal memory for the person, without using it to train shared AI models.
USE POLICY
Participation by a business should have a clear purpose and permission, with access boundaries around personal records.
OBSERVABILITY
Supporting a product should not mean unrestricted access to someone’s personal history.
DATA PROTECTION
Consider how information is protected when stored, transferred and used to produce a response.
ACCURACY
Information read from a document should be reviewable before it becomes part of the record.
TRANSPARENCY
Explain the role of external AI providers and the context a response may require.
PORTABILITY
Connections to assistants, messaging and voice are planned paths for the same private memory.
04 / Technology, privacy and security