Local-first
Privacy and responsibility are two sides of the same design decision. Here is exactly what that means in plain terms.
No account
Songcards does not ask you to sign up or sign in. There is no username, password, or profile tied to your library.
No Songcards backend
There is no HugByte server that stores, processes, or even sees your Songcards data. The app talks to your own machine, not to us.
No cloud sync
Your library does not automatically sync anywhere. If you move to a new machine, you carry your data across yourself — see the backup and restore page.
No upload of song content to HugByte
Prompts, lyrics, and rights notes you write into a Songcard are never sent to HugByte. They stay on your machine.
Where data is actually stored
Songcards stores your library in a local application data folder on your Windows machine, managed by the desktop app itself. You don't need to think about databases to use Songcards day to day — that detail only matters if you're curious.
Backups are your responsibility
Because there is no cloud copy, a lost or corrupted machine means a lost library unless you made a backup. Songcards gives you the tools — a full JSON backup and Obsidian export — but running them is up to you. See backup, restore, import and export.
What HugByte can and cannot do
HugByte cannot restore data that was never backed up. There is no server-side copy to recover from. This is the direct tradeoff for not running a cloud service at all.