Keep a copy. Know where it lives.

Anonymous journals stay in this browser

Anonymous saves do not upload. Prediction runs on your device without sending seed queries to a server. Your journal belongs to the browser profile and app address where you saved it.

Different browsers, devices, hosts and ports have separate storage. Moving from a local prototype to a future public app will not automatically transfer your records.

Clearing browser data, private-mode cleanup, storage eviction or device loss can remove saves. Anyone using the same browser profile may be able to read its journal.

Export and restore

1. Open Account & settings → Journal & backups.
2. Choose Export and keep the JSON file somewhere safe.
3. On the destination browser or app address, open the intended journal and import the file.

Imports add fresh copies with “(imported)” names. They do not merge or overwrite existing worlds, even when seeds match. Importing the same backup again creates more copies.

Exports contain seeds, places and private notes. They are not encrypted; anyone with the file can read them. Keep backups private rather than attaching them to public bug reports.

Optional accounts are a separate journal

GitHub/Google sign-in and account sync are implemented and manually tested locally. Public account service and deployment are still pending; this is not an announcement of live cloud availability.

In the local implementation, signing in alone does not upload anonymous records. Enabling account sync requires explicit consent: account seeds, places, notes and progress then leave the device for cloud storage. This is not end-to-end encrypted storage.

To move anonymous records into an account, export them, open the intended account journal with consent, then import and confirm copies. Anonymous originals stay separate.

Pending edits are not the same as acknowledged cloud saves. Conflicts require a choice; unsynced edits can still be lost if browser storage is lost. Export backups even when using sync.