1. Local-First Sandbox
The primary security layer of Lorebase is its offline-first architecture. The desktop application runs standalone, meaning:
- By default, your data stays local on your machine and is never transmitted to external databases unless you explicitly choose to enable optional Loresync node synchronization.
- The desktop application works completely offline, eliminating remote network exploits when not in collaboration mode.
2. Database Encryption
In the interest of open standards, data portability, and user ownership, the Lorebase local database is not encrypted. This ensures you can always open, query, and migrate your data using standard, open-source SQLite viewers and tools.
To protect your work from unauthorized local physical access or device theft, we strongly recommend enabling full-disk encryption on your operating system:
- macOS: Enable FileVault via System Settings.
- Windows: Enable BitLocker or Device Encryption via Control Panel.
- Linux: Use LUKS encryption on your system drive partitions during OS installation.
3. Backup Guidelines
To protect against accidental database corruption, Lorebase automatically performs a local database backup, saving a copy of base.db as base.db.bak in the vault directory under a .lorebase folder.
However, in local-only mode, because we do not store your files on any remote server, we cannot recover lost data in the event of physical drive failure, operating system crash, or device loss.
We highly recommend incorporating your Lorebase workspace directories into your routine external backup policies (e.g. Backblaze, BorgBackup, Time Machine, Duplicati) or initializing a local git repository in your workspace folder for revision history tracking.
4. Reporting Issues
If you identify any security issues, vulnerabilities, or bug vectors in the Lorebase desktop application, network sync interface, or website, please contact us directly.
Please email security alerts to: