Your memory should come with you
The V1 plan includes a Transfer my library flow: choose all or selected collections, export a portable archive, and restore it on another Mac. This transfers your seenX library and the context attached to it, not a full operating-system or laptop backup.
Two export modes
| Mode | Included | On the new Mac |
|---|---|---|
| Complete library | Selected image originals, notes, selected text, pins, regions, collections, typed relationships, and source history. | Restore without depending on the old file locations. Report any missing originals before calling the archive complete. |
| Context only | Notes and structured context, image identities/content hashes, dimensions, source history, and a manifest; no image originals. | Locate matching originals already present on the new computer. Unresolved images remain visibly missing until relinked. |
Preserve meaning and location
Stable asset and revision IDs keep notes attached to the right pixels. Content hashes help identify matching originals even when filenames and folder locations differ. Normalized highlight coordinates, selected text, and explicit relationships travel with their source revision. A selected-collection export must keep relationships consistent without silently including unrelated private originals.
Keep archives independent
Use a versioned manifest and a consistent snapshot of records and image files. Readable notes and source context should remain exportable independently of any model. Compatible search indexes may travel as an optional cache; incompatible indexes are rebuilt without losing human annotations. This is not a promise that copying a live database file by itself is a complete backup.
Optional encrypted transfer
A passphrase-protected archive is planned using a maintained authenticated-encryption format/library selected during implementation. Protect the metadata as well as the images. Cross-device restore must not depend only on a key held by the old Mac, and the app must explain passphrase recovery limitations. No archive encryption feature or security audit exists today.
Reconnect access deliberately
Do not transfer assistant credentials, tokens, active grants, or machine-specific source permissions. Reconnect external folders and authorize assistants on the new Mac. Source history is preserved as evidence, not silently treated as valid access to a new path.
Import safely
Validate the schema version, image hashes, archive paths, missing files, and relationship targets before writing. Restore into a fresh library or show an explicit conflict/duplicate preview for merging; never silently overwrite newer notes. A canceled or failed restore should leave existing memories intact.
The release check
Export an annotated library from one Mac, restore it into a fresh library on another, and verify the originals, notes, selected text, highlight alignment, and relationships. Test context-only relinking, incompatible indexes, corrupt/missing images, encrypted archives, and schema migration.
Transfer first, continuous sync later
V1 targets deliberate backup and restore. Live multi-device synchronization, concurrent note edits, and deletion propagation need separate conflict and access designs and remain later work.
What the website can do today
The preview exports one sample memory as JSON. It does not export or restore a complete library, transfer real images between computers, or produce encrypted archives. Browser-local sample edits do not automatically move between laptops.