ContextVaultDocs
Documentation/Reference/Storage & privacy
← All guides

Reference

Storage & privacy

Understand where extension records, Markdown sessions, indexes, and exports live.

Reference · Data

Understand storage and privacy

Browser capture and project files remain distinct until you explicitly export and import. Markdown is durable; the generated index can be rebuilt.

Project vault layout

text
.contextvault/
├── config.json
├── memory.md
├── links.json
├── sessions/          # terminal and Desktop Markdown
├── imports/browser/   # imported browser conversations
├── index/             # generated local JSON index
└── exports/           # prepared context and timeline output

Browser extension

Conversation captures live in the browser profile's IndexedDB until the user downloads an export.

Vault Terminal and Desktop

Sessions, imports, project memory, links, indexes, and prepared context stay under the project's `.contextvault/` directory.

No automatic cloud sync

The product does not require a ContextVault account, backend, or automatic remote synchronization.

Inspect before sharing

Markdown is readable and can include prompts, agent output, project details, paths, or customer context. Review exports before sharing.

Source of truth

Markdown sessions and imports are durable. The generated search index can be rebuilt; prepared handoffs and timelines can be regenerated.