Do not remove the installed extension before updating. Notes, covers, settings, protection records, and Private Vault data belong to that installation in that browser profile.
Chromium installations
- Note the current edition, version, extension ID, browser profile, and permanent installation folder.
- Obtain the update for the same edition.
- Extract it over the same permanent folder. Make sure
manifest.jsonremains at the same level, rather than inside an extra nested directory. - Open the browser's extensions page and select Reload on the existing Groovy card.
- Check the version, settings, previews, notes, and folder protection.
Do not use Load unpacked from a different directory to update an unpacked development build. It may create a separate extension identity with an empty local store.
Firefox installations
Install the newer signed XPI over the existing edition. Keep Toolbar over Toolbar and New Tab over New Tab. Do not uninstall the old add-on first.
What is and is not a backup
Browser bookmark export protects ordinary bookmark URLs and titles. It does not export Groovy notes, covers, widget settings, folder locks, or encrypted Private Vaults.
A complete Groovy export/import feature is not yet available. Browser bookmark sync is not Groovy settings sync. Local recovery copies, where present in a build, are not independent backups and do not survive deletion of the entire extension profile.
The newest storage-recovery improvements are currently in the local DEV build, not yet in rebuilt customer archives. See the changelog. Do not assume an older package has those safeguards solely because its displayed version is also 1.0.34.
If settings unexpectedly disappear, stop making changes and do not clear storage or reinstall. Record the extension ID and installation path and contact support.