Privacy
What is encrypted, what is not, and the limits of both.
Everything you store with junkyard is encrypted on its way into the database, so what gets stored was never readable in the first place. A copy of the database is not a copy of your data.
What is encrypted
Anything you type, sealed with AES-256-GCM. Encryption is the default, not a list of chosen fields, so a tool added tomorrow is covered just like the ones here today.
- Locked to your account. An encrypted value copied into someone else's account fails to decrypt rather than quietly working.
- Padded numbers. Encrypted text is as long as the original, so amounts are padded to a fixed width first. Otherwise a large amount would look longer than a small one.
What is not
Only what the database needs to function: timestamps for sorting, and the internal IDs that link records together. They show that you did something and when, never what.
Signing in
Sign-in goes through Google, so I never see a password.
- Only verified Google addresses are accepted.
- Sign-in codes work once, and are stored only as one-way digests.
- Revoking access ends existing sessions immediately.
The honest limit
The server can read your data
Encryption protects your data from anyone who gets at the database. It does not protect it from whoever holds the key, which is me, as the person running the server.
That is the tradeoff of any hosted tool, and I would rather say it plainly. If you need protection from the operator too, a tool that runs on your own machine is the better fit.

