Local and cloud storage

Browser-local documents

Local documents live in the browser storage for this site and browser profile. They do not upload merely because you edit, print, or export them. They can disappear if you delete the document, clear site data, use a temporary browser profile, or lose the device.

Download an Experiencer JSON copy of important local work. Local storage is convenient working storage, not a substitute for a backup plan.

Pro cloud documents

Pro Cloud storage requires a signed-in account with active cloud access.

Cloud documents are associated with the signed-in account. Creating, saving, renaming, or deleting a cloud document uses the Pro service. The document selector identifies the active document and the navigation reports saved, saving, offline, conflict, or other sync states when relevant.

The cloud service applies bounded document and revision limits so storage cannot grow without limit. The editor reports a user-actionable error when an operation reaches a product limit; do not retry repeatedly without changing the document set.

Move local work to the cloud

When eligible local documents are found after sign-in, Experiencer can offer a migration workflow. Review the listed documents before confirming. Migration creates cloud copies and records which local documents were handled so the prompt does not continually repeat.

Keep a downloaded JSON backup until you have opened and verified each migrated cloud document. A migration status does not turn the original browser storage into a second live sync destination.

Understand saved and unsaved state

• Saved means the active repository accepted the current document version.
• Saving means a write is still in progress.
• Offline or unavailable means a cloud write could not currently complete; keep the tab open and preserve a JSON backup if the condition persists.
• Conflict or stale state means the server has a newer version than the editor expected. Reload the latest saved document before applying changes again.

MCP, revision history, saved-resume PDF export, and temporary review links operate on saved cloud state. They cannot see unsaved browser edits.

Export account data

Pro account Signed-in users can download a cloud archive from the account controls, including after paid access becomes inactive while retained data remains available.

The archive contains one current OSS-compatible JSON document for each retained cloud résumé or custom template. It does not include the separate revision-history rows. Open a sample export in the local editor before relying on an archive as your only copy.

Deleting a cloud document is separate from downloading an archive and removes that document and its eligible history. Follow the confirmation wording carefully.

Continue

• Use revision history for saved Pro versions.
• Review billing and retained data.