Verified by the sovseal team
Memory Exports
Export your memories in structured formats.
| Deployment Model | Availability |
|---|---|
| Platform | ✓ Available |
| Self-Hosted | ✓ Available |
Honesty Ledger (Provenance Layer): Backups are triggered at the Server-known (Layer A) layer, while decrypted data is compiled at the Client-derived (Layer B) layer.
ZK Trust Boundary:
- What the server sees: Request logs for export creation and raw ciphertext envelope indices.
- What stays on device: Decrypted JSON document exports (constructed purely in-browser heap).
Memory Exports
The console supports exporting your memory records for backups, model fine-tuning, or migration. Because your data is client-side encrypted, the export tool supports two distinct formats:
Decrypted JSON Export
- Client-Side Generation: The browser traverses all synced memory records, decrypts them using the project key in active memory, compiles the JSON document, and prompts a file download.
- ZK Privacy: The decryption and compilation occur 100% inside your browser's memory heap. No plaintext is ever transmitted back to the network.
- Key Prerequisite: If the project key is locked, the Decrypted JSON button is disabled with a lock indicator (
🔒 Key Locked).
Ciphertext Envelope Bundle Export
- Backup and Replay: This download packages raw database sync packets, containing base64 ciphertext, IVs, and SHA-256 Verified Semantic Recall (VSR) hashes.
- No Key Required: Because these envelopes are opaque, you can export them without verifying the decryption key.
- Portability: This bundle can be imported into self-hosted Supabase instances or loaded directly into an offline SDK client for manual playback and recovery.
Offline Reference Analogs: This documentation was written with visual and rhythm reference to api-reference/memory/create-memory-export.html.