# Your memory should have an exit door

2026-10-03 (updated 2026-10-20) · Bubbling AI team

Canonical: https://bubblingai.com/blog/memory-should-have-an-exit-door

How Bubbling AI keeps memory portable, from revisioned records to a plain ZIP export you can take with you.

*From our design notebook: Bubbling AI is in development. This article describes the approach we’re building toward; the service is not open for sign-up.*

Memory makes an assistant more useful over time. It also changes the relationship: a tool that remembers your projects and preferences should make it possible to leave with what it learned about you.

That is why Bubbling AI treats memory as a collection of records you can inspect and carry, rather than a secret ingredient trapped inside a chat history.

## Edits leave a trail

Memory and documents live as records in your account. When you edit one, the change adds a revision instead of overwriting the previous version. That gives the record a history: a correction can build on what came before without quietly replacing it.

The contents can also be useful outside the app. Memory and documents export as Markdown, a plain-text format that people can read and edit with ordinary tools. Uploaded files stay in their original form. A `manifest.json` lists each record’s ID, owner, label, revision and hash, so the archive has an inventory rather than a pile of unexplained files.

The export is one ZIP, designed to open without Bubbling AI. You should not need a special reader to get your own notes back.

## Take only what you choose to share

Portability can also mean connecting another tool to selected memory. Bubbling AI supports MCP connections with project-level access choices: blocked by default, allowed, or allowed with vault content. Those choices let you decide whether a connection sees nothing, ordinary project memory, or confidential material as well.

Opening vault access is a meaningful boundary. The app warns that the content leaves the platform’s protections, and is subject to the receiving tool’s own data practices. You can change a connection’s access or revoke it; changes apply on its next call. Access records and permission controls are part of making that choice understandable. The views available at launch will be documented before sign-up opens.

## Portable does not mean every privacy question is solved

An export gives you a way to take your records with you. Portability and privacy answer different questions. Different kinds of stored information have different access and recovery rules. We will explain the key-custody model and its limits before the service opens. Exporting information also does not make another tool inherit the protections around the original workspace. Sharing with another tool is a choice to let that tool receive the content.

We think memory should make an assistant feel more familiar without making your information feel captive. Revision history and a standard-format export are practical parts of that promise. The right to leave should be built into the shape of the product, not saved for a goodbye screen.

For the boundaries around sharing, read [why approval is part of the product](/blog/approval-is-part-of-the-product) and our [privacy and security statement](/privacy-and-security).