AI memory privacy and ownership
Who owns your AI's memory?
Memory contains the durable model of a person or team. Ownership must include access, correction, portability, and control over maintenance.
You own an AI memory only when you can inspect it, correct it, control who accesses it, and take it elsewhere in a usable form. A download of chat transcripts is not the same as ownership of the maintained profile, relationships, and decisions the system actually uses to shape future answers.
Memory is different from conversation history
A transcript records what was said. Memory determines what the system carries forward.
That maintained layer may contain:
- preferences and personal facts;
- inferred relationships;
- project decisions;
- summaries of past behavior;
- confidence or importance scores;
- facts invalidated by later events;
- links between people, work, and time.
It is a durable model of a person or organization. Its control deserves the same attention as the model’s capability.
The four parts of ownership
Access
You can see the memory in a form that corresponds to what the agent uses. A decorative profile page is not enough if the retrieval system relies on a hidden representation you cannot inspect.
Correction
You can change an incorrect fact and know how that correction affects derived memory. The system should not quietly restore the old claim from another summary.
Portability
You can export content, structure, and provenance in standard formats. The export remains useful without the original service.
Governance
You decide which agents and people can read or write each scope. Personal and team memory do not merge merely because both are convenient to retrieve.
Privacy is an architecture
A privacy statement matters. Enforcement matters more.
Memory access should be scoped in the database or service layer, not left to a prompt that asks the agent to behave. Agent permissions should exclude operations the agent does not need. Sensitive governance—such as inviting a member—should remain a human action.
OceanDB uses row-level security for workspace membership and a restricted agent role with no delete, truncate, or schema privileges. The dashboard and agent have different grants because they have different jobs.
Who performs the maintenance?
Many memory systems use models to extract, summarize, merge, or rank memories. Ownership includes knowing which model does that work, where it runs, and whether the original material remains available.
OceanDB separates storage from consolidation. The hosted service holds the database and MCP endpoint. The Dreamer runs from the user’s own agent with the user’s chosen model. Its actions are visible in the dashboard, and ambiguous contradictions or merges become proposals rather than silent edits.
The right to leave
Portability should be tested before it is needed.
Ask:
- Can the entire memory be exported without contacting support?
- Does export include relationships and source references?
- Are proprietary embeddings required to read the content?
- Can another system reconstruct current and historical state?
- Can the service account be closed without losing the only readable copy?
OceanDB exports a Markdown archive for reading and a SQL dump for fidelity. The primary store is Postgres. Embeddings improve retrieval but do not contain the only copy of the memory.
Sovereign does not mean isolated
A sovereign memory can still be hosted, shared, and used by several agents. Sovereignty describes authority: the memory answers to the user, moves at the user’s direction, and is not repurposed as someone else’s asset.
It also imposes responsibility. Once an authorized external agent reads memory, that agent’s provider may process the content under its own terms. Connect only agents you trust, and keep scopes narrow enough for the work.
A practical ownership test
Correct one fact. Export the result. Open it without the product. Trace the fact to its source. Remove an agent’s access. Move a project into a shared workspace without exposing private notes.
If the system can do those things, ownership is becoming real. If it cannot, “your memory” may describe the subject more accurately than the owner.
Read sovereignty and your data for OceanDB’s implementation boundaries.