Encryption at rest
What encryption protects on your device, and what it does not.
On a device set up with encryption at rest, your data is stored encrypted on the memory card. The Linux system does this (ext4 encryption, AES-256). The key lives inside the Raspberry Pi’s own chip, in memory that can be written only once. That is why the device starts by itself after a power cut, with no password.
How to
Check it yourself
- Open the Terminal on the device, or connect with SSH.
- Type
sudo phntm-at-rest status.
The privacy proof also reports it: Settings → What has left this device → Generate the proof.
Good to know
- Encrypted: the app’s data and settings (memories, conversations, documents, the search index, logs, API keys), the backups on the device, the screen browser’s data, your home folder, saved Wi-Fi passwords and the system log.
- It protects a memory card that is taken out, thrown away or copied: the data on it cannot be read.
- It does not protect against a thief who takes the whole device (another system started on the same board can read the key), or against someone who already has full control (root) of the running device.
- Not in the encrypted stores: installed skills’ private data, the device’s own records of skills, accounts and authorizations, and the owner’s username.
- Temporary files and swap stay in memory. They are never written to the card.
- A unit used before it was encrypted may still hold old pieces of data in free space on the card. A full reset and a fresh card image is the clean start.
Related topics
From the device manual for software 0.9.0 (November 15, 2026). Your device serves the manual for its installed software; where this copy and your device differ, your device is right.