Privacy
Privacy policy 1.9.4: memory is encrypted per account
The memory paragraph now says that entries are encrypted with a key per account, and states plainly that this is not end-to-end encryption.
The privacy policy now says memory is encrypted per account but not end-to-end, and you do not need to accept anything again.
Version 1.9.4 changes one paragraph. It no longer says that confirmed memories are stored as plain text. It now describes the encryption per account (AES-256-GCM) of memory entries, writing-style samples, agent memory and the agent journal, and when it started.
The paragraph also states that the running service decrypts entries and the operator can technically read them, that deleting your account deletes its key, and that the end-to-end memory engine is not offered.
No new recipient or service is added. Memories that are injected into a prompt go to Featherless exactly as before. You do not need to accept anything again. The full change log is on the legal page.