Google Details Private, Server-Side Memory for AI Assistants
Google plans to give Private AI Compute persistent memory across devices while keeping decryption keys exclusively on users’ personal devices.

Key takeaways · 3
- 01
Architects can separate cloud-stored encrypted memory from cryptographic keys kept solely on users’ devices.
- 02
Private AI Compute will use encrypted channels and isolated secure enclaves when models access stored information.
- 03
The architecture immediately re-encrypts saved context after processing a request inside isolated memory.
Memory Without Cloud Keys
Google says it will add private, server-side memory to Private AI Compute, enabling persistent, cross-device AI memory while retaining privacy standards typically associated with on-device processing. [1] The planned persistent memory layer will place information in dedicated, encrypted cloud storage, while the cryptographic keys required to unlock it remain exclusively on a user’s personal devices. [1]
Inside the Secure Enclave
When a model needs the stored information, an authenticated, end-to-end encrypted channel will connect the user’s device to a protected and isolated cloud environment that Google describes as a secure enclave. [1] Inside that enclave, data will be temporarily decrypted in isolated memory to process the request; new context will then be saved and immediately encrypted again. [1]
What it means
Google’s design separates encrypted server-side storage from device-held keys, then confines plaintext handling to an isolated enclave during a request. That architecture attempts to combine the continuity of cloud memory with the privacy posture Google associates with on-device processing, rather than choosing only one model. What the sources don't address: when the capability will reach users, which products will adopt it, or how its security properties will be independently verified.
Persistent memory can make AI assistance continuous across devices, but it requires protections for information retained in the cloud. Google’s proposed architecture keeps encrypted memory server-side while reserving the unlocking keys for users’ personal devices.
Why it matters
Put this to work — one session a day, built for your industry.
Create a free account for a daily session — eight questions and one real-work challenge, on the news that affects your role.
Start freeHow this developed
24 September 2026
Google Details Private, Server-Side Memory for AI Assistants
24 September 2026
Event created from source cluster.
Sources
- Advancing Private AI Compute with secure, server-side memoryGoogle DeepMind Blog