# Memory is now encrypted per account 2026-10-20 · Security > Memory entries, writing-style samples, agent memory and the agent journal are stored encrypted with a separate key for each account. This is not end-to-end encryption. Until now, memory sat as plain text in the account database. It is now encrypted with AES-256-GCM, with a separate key for each account. The account key is stored wrapped with a server key at the operator in Switzerland. This covers memory entries, writing-style samples, agent memory, the agent journal and the agent's raw files. A copy of the database or a backup no longer shows them in clear text. Existing entries are re-encrypted in batches after a backup. It is not end-to-end encryption. The running service decrypts entries when it needs them, so the operator can technically read them. When you delete your account, its key is deleted too, and entries left in backups become unreadable. The separate end-to-end memory engine is still not offered. Chat memory is also wired in: when you switch memory on for a chat, relevant entries are added to the turn, with a visible notice. The data export includes these entries as readable text.