Guides and FAQs
Know your archive.
Use it mindfully.
The essential concepts and steps to orient yourself: from the first vault to backup copies, up to use in the browser.
First steps
Vault creation, access and recovery.
Data and copies
Backup, import, export and packages.
The browser
Configuration, shortcut and conditions of use.
Frequently asked questions
Straightforward answers on privacy, compatibility and features.
01 / Start here
Create and find the vault.
- Create a test vault with a strong master password. Keep your recovery code in a separate place.
- Add a demo account. Try folders, search, favorites and data editing.
- Lock the vault and verify unlocking with master password and recovery.
- Prepare an independent copy of the encrypted file and try recovery by linking the copy.
Connect an existing archive
The function Link existing vault allows you to choose a file. For the first test use an independent copy: some operations can write to the vault, even when merging external changes.
02 / Understanding the differences
Backup, export and packages.
| FORMAT | WHAT IT IS FOR |
|---|---|
| .vault files | Complete encrypted archive. Independent copies allow you to maintain a vault state. |
| .bak files | An older encrypted copy, created before writes. It is not a version history. |
| CSV / JSON | Unencrypted exports to transfer data. They do not include all settings and are not the same as a full backup. |
| .jshare package | Exchange of data encrypted with separate passphrase. It does not offer collaborative sharing or remote revocation. |
Import
The client accepts CSV and JSON; the packages .jshare require your own passphrase. JSON and .jshare payloads are checked before merging and rejected in full if a record does not meet the required checks. Compatibility with any export of other products is not guaranteed.
Sharing a package
Protect the passphrase separately from the file. A complete package can include recycle bin and history: check the contents and scope of the export path before delivering it.
03 / Position and synchronization
A local file, even in a cloud folder.
You can choose the location of the vault. Changing location copies the file, checks its hash and keeps the original. It is not a destructive shift.
An external provider can synchronize the folder. The app can read and merge compatible copies using timestamps for whole records and deletion markers.
This mechanism is partial: There is no proprietary cloud transport, multi-process locking, or single-field merging. Contemporary changes, inconsistent clocks, and outages require further verification. Maintain independent backups.
Essential answers