Rewisp 0.23.0 — your memory is now encrypted

Rewisp's database is encrypted at rest.

Until now your captured text sat in a plain database file, protected by FileVault and your account permissions. That's real protection while the file stays on your Mac, but it disappears the moment the file doesn't: a backup, a copied folder, a disk pulled out of a stolen laptop.

The database is now encrypted with AES-256. Someone who takes the disk, restores a backup, or copies your Rewisp folder gets nothing readable.

There is nothing for you to do. No password, nothing to remember, nothing to set up. The key is created on first run and kept in your login Keychain, and Rewisp unlocks it automatically. If you already use Rewisp, it converts your existing memory the next time it starts — about a second, with a copy of the old file kept alongside until everything checks out.

Being straight about the limit. Because Rewisp has to keep capturing before you've touched your Mac, it unlocks the key on its own. That means a program already running as you could still get at it. Encryption protects the file, not the running session. Requiring Touch ID wouldn't change that, and would leave gaps in your timeline after every restart.

Search is unaffected. Everything still works exactly as before, about 1% slower.