The short version
- Your history is encrypted on disk with AES-256, automatically, with nothing to set up.
- That protects a copied folder, a stolen or discarded drive, backups, and other accounts on the PC.
- It can’t stop malicious software already running under your own Windows account. Nothing that opens automatically can.
- You can add a Windows Hello lock in front of the window.
- RecallOS hasn’t had an independent security audit yet, and its installer isn’t code-signed yet. Both are on this page because you should know.
Encryption at rest
On by default from version 3.0. A history from an earlier version is encrypted the first time 3.0 starts, and it’s safe even if the PC loses power partway through: the original isn’t touched until an encrypted copy has been written and checked.
- The database holds the text read from your screen, window titles, the search index, your questions, your account and your settings. It’s encrypted with SQLCipher (AES-256), including its write-ahead log.
- Pictures and thumbnails are each encrypted with AES-256-GCM, so a file that has been altered fails to open instead of showing something false. They’re decrypted in memory only when you look at them.
- The key is a random 256-bit key made on your PC. It’s kept in
store.key, wrapped by Windows for your account (DPAPI). Windows unlocks it when you’re signed in, which is why you never type a password to start recording.
What this protects against
- Someone copying your RecallOS folder, or restoring it from a backup.
- A stolen or discarded drive, as long as they don’t also have your Windows password.
- Other accounts on the same PC.
What this doesn’t protect against
- Malicious software running as you. It can ask Windows for the key, just as RecallOS does. Encryption raises the cost well above reading a plain folder, but it isn’t a defence against this. If your PC is compromised while you’re signed in, assume your history is exposed.
- Someone using your unlocked PC. The Windows Hello lock below helps with casual access to the window. It doesn’t change what’s on disk.
- Whoever you send things to. If you connect a cloud model, share a project, or let a cloud-based AI tool search your memory, what they receive is then under their control.
Your backup code
Because Windows holds the key, losing your Windows account would lose your history. Settings → Security shows a backup code that restores access on a rebuilt account. It’s the only way back in: we don’t have a copy, and we have no way to get into your history. Keep it somewhere away from the PC.
The Windows Hello lock
Optional, in Settings → Security. When it’s on, RecallOS asks for your face, fingerprint or Windows PIN when it opens, when it comes back from the notification area, and after Windows locks. Where Hello isn’t set up, it asks for your RecallOS password instead. Recording carries on behind the lock, so stepping away doesn’t leave a gap. It guards the window; the files are guarded by encryption either way.
What’s left out automatically
On by default, and each can be turned off in Settings → Privacy. If one of these is visible anywhere on screen, not only in front, RecallOS skips that capture completely:
- Private and incognito browser windows, recognised by their window title.
- Password managers, including 1Password, Bitwarden, LastPass, Dashlane, KeePass, NordPass, Keeper and others.
- Common banking and payment sites and apps, recognised by their window title. This covers well-known names rather than every bank on earth, so add your own under “Never record windows whose title contains”.
Separately, password boxes are blurred at the moment of capture, and card numbers, API keys and tokens are removed from the picture and the search index. These are safeguards and can miss things, so please check your exclusions cover anything sensitive.
What you can inspect
RecallOS isn’t open source, but its privacy tests are public: the checks that a forgotten moment is really gone from the raw files, that an excluded window never reaches the disk, that the store is unreadable without its key, and that a tampered vault file is refused. You can read exactly what’s being promised and how it’s checked.
Not done yet
- Independent security audit. None so far. The claims here come from our own code and tests. When an audit happens, its report will go here.
- Code signing. The installer isn’t signed yet, so Windows SmartScreen may warn you when you run it. Each release lists the SHA-256 checksum of every file so you can verify your download.
- Compliance certifications. RecallOS isn’t certified for HIPAA, SOC 2 or similar, and we don’t sign business associate agreements. Because we never receive your data, some requirements don’t apply in the usual way, but that’s a decision for your compliance team, not a claim we make.
Report a problem
Found a security issue? Email anshpatel@recallosai.com. Please give us a chance to fix it before publishing the details. See also what’s stored, and where.