Support & Troubleshooting
Most ChatVault issues fall into a handful of categories, and each has a concrete next step. A single failed conversation never destroys the rest of a batch: finished work is checkpointed, and failed items can be retried individually from the side panel.
Permission errors
The extension cannot read a platform until you grant that platform's host permission. Open the extension settings, check the platform's permission state, and grant access to the platform you want to use. Declining one platform never affects the others, and revoking a permission cleanly unregisters that platform's content scripts.
Authentication and sign-in problems
ChatVault reads only what your signed-in account can see. If a scan or job reports an authentication error, open the platform in a normal tab, sign in again, then resume the job. The extension never asks for or stores your password, cookies, or tokens, and it stops immediately when a platform reports an access error instead of retrying aggressively.
Platform changes and unsupported pages
When a platform changes its page structure, the adapter reports a controlled unsupported state rather than guessing. The rest of the batch keeps working and the affected conversations are flagged. Check the extension version first; updating to the current release usually restores compatibility once the adapter has caught up.
Incomplete loads and warnings
A conversation marked incomplete could not be proven fully loaded; one marked warning is intact but degraded, for example an unsupported attachment kept as a structured reference. Retry the item from the side panel with the platform tab in the foreground so long threads can finish loading. An incomplete conversation is never reclassified as success, so a clean manifest after a retry means the retry worked.
Storage problems
Jobs checkpoint to IndexedDB, and Vault content also lives there. If a job reports a storage error, free up disk space, check that the browser is not blocking site data for the extension, and resume the job. Clearing your browser profile data removes Vault content and checkpoints, so keep exported ZIP files in safe storage as the backup of record.
Rendering and packaging errors
If a specific conversation fails to render or the ZIP fails to package, the rest of the job is preserved. Retry only the failed items from the side panel. Repeated render failures for the same chat usually mean an unusual content type; the manifest records the reason, and the item can be excluded or exported in a different format while it is investigated.
Contact support
Still stuck? Email [email protected] and include the product version, adapter version, platform, and the error category from the side panel. Never paste conversation content into a support message; diagnostics only ever need content-free states, versions, and error codes.
For how your data is handled, see the privacy policy.