Designed to hold less.
Colla helps preserve structure, context, provenance, and relationships without trying to become the place where all of your files live.
Data Ownership
Your files remain in your storage.
Colla manages the structure around your work: where something belongs, how it relates to a workspace, what context it was gathered into, and what provenance should travel with it.
Most software tries to take custody. Colla is built around a different posture: we help organize your world. We do not become your world.
Where Your Files Live
Google Drive is the first storage adapter. When Drive is connected, file bytes stay in your Google account unless a specific future feature says otherwise.
Colla can remember that a file belongs in a workspace, folder, course, or Context Set without making Colla the owner of the file bytes. Placement and storage are related, but they are not the same thing.
What Colla Stores
- Account information needed for authentication.
- Workspace, folder, course, and Context Set structure.
- File metadata such as names, placement, provider ids, and tags.
- Provenance such as redacted source URLs and capture events.
- Encrypted OAuth tokens when you connect Google Drive.
What Colla Does Not Store By Default
- Your file bytes on Colla servers.
- Full source URLs with authentication query parameters.
- Materials sent silently to AI tools in the background.
- A message-level AI memory system.
AI Conversation Capture
AI conversations only enter Colla when you intentionally capture them. A captured conversation is treated as source material: a preserved snapshot that can be placed, gathered, and reused later.
Colla does not treat AI output as verified truth. It preserves working context so you can continue from it with appropriate provenance.