Hello @Spartan - thanks for reaching out about this. One thing to consider here with Codebook is that the underlying storage of secure data is encapsulated in a single file that can easily be backed up at any time, e.g. using a standard operating system or device backup.
The file format for Codebook itself is already in an open standard form. Codebook uses SQLCipher, which is an open source, widely used encrypted database library. You can open the database and access all of your information using a freely available tool like DB Browser for SQLite. You can even run arbitrary SQL queries against the data.
On the desktops the
strip.db file can be accessed in
%APPDATA%\Zetetic LLC\Strip\ for Windows, and
~/Library/Containers/net.zetetic.Strip.mac/Data/Library/Application Support/Strip for macOS. You can copy that file, back it up, and then restore it directly onto a new environment if you really needed to in an emergency.
In Codebook, “export to plain text” is not intended to be used for day to day backups. Rather, it is a way for users to:
- make a “hard copy” of their data, for example to keep a printout in a safe
- Move their data in a portable format to another platform (i.e. so they are never “locked in”).
These are both really valid use cases, and in our opinion any tool that doesn’t provide an option to export your data to support those basic requirements should be looked at skeptically. If I might ask, would you mind pointing me to the place you noticed our competitors saying this was the marker of Codebook being an insecure application?
Finally, with regard to Merge, what you describe is similar to how it works today. If you run a merge operation and there are different distinct entries on both sides, they will both be present in the final database.
Please let me know if this helps address your concerns. Thanks!