Version history 🕘
Every note keeps a short history of its previous states. Edit a note, and the content you just replaced is saved as a version — so a bad edit or an accidental deletion of a paragraph is never fatal. Version history works on all three tiers: Notes, Secrets, and Seals.
How versions are created
You don't manage versions — they happen automatically:
- Every save records the previous state of the note (title and body) as a version.
- Rapid edits collapse. Saves within a 5-minute window are treated as one editing session and produce a single version, not one per keystroke-and-save.
- The last 10 versions are kept. When an edit would create an 11th, the oldest version is dropped.
Style changes (color, pattern) and tag changes don't create versions — only the title and body are versioned.
Browsing and restoring
Open a note's actions menu and choose Version history (the item shows how many versions exist). A timeline appears next to the note:
- Hover a version to preview it in place (on touch devices, tap to select)
- Restore replaces the current content with the selected version
- Delete removes a single version from the timeline
Restoring is safe: the content you're replacing is itself saved as the newest version first, and the confirmation toast has an Undo button that puts it right back.
Encryption: versions are as private as the note 🔐
Versions inherit the security tier of their note:
| Tier | What the server stores per version |
|---|---|
| 1 – Notes | Plaintext title + body |
| 2 – Secrets | Plaintext title, ciphertext body |
| 3 – Seals | Plaintext title, ciphertext body |
For Secrets and Seals, version snapshots are stored as ciphertext only and are decrypted in your browser the same way the note itself is. For Seals, all versions are encrypted with the note's own key (the per-note key never changes across edits), so the server never gains any new decryption capability from history existing. → Encryption
Version history is also kept out of normal traffic: listing or fetching notes never includes version data. Versions only travel over the dedicated version-history endpoints, when you actually open the timeline.
One honest caveat for Tier 1
For plaintext Notes, versions are plaintext too. Deleting sensitive text from a Tier 1 note does not scrub it from history — the old content lives on as a version until it ages out of the 10-version window. If something should never have been in a plaintext note, delete the versions that contain it from the timeline (or better: it belonged in a Secret or Seal to begin with).
Deleting a note permanently deletes its versions with it.