Aivora
Google DeepMindAI SafetyIntermediate

Google Advances Private AI Compute with Secure, Server-Side Memory

Google 發表 Private AI Compute 記憶技術:實現跨裝置 AI 助理與終端級隱私

2 min read
Google Advances Private AI Compute with Secure, Server-Side Memory
The 30-second version

To provide continuous assistance across devices, AI needs long-term memory, which traditionally poses privacy risks in the cloud. Google DeepMind's update to Private AI Compute solves this by creating a secure "digital vault" in the cloud. User context is stored encrypted on servers, while the decryption keys reside strictly on the user's personal devices. When the AI processes a request, an end-to-end encrypted channel connects to an isolated "secure enclave" in the cloud, where data is temporarily decrypted, updated, and instantly re-encrypted—preventing even Google from accessing it.

Key points

01

Cloud-Scale Secure Vault

Information needed to assist you is sealed within dedicated, encrypted storage in the cloud.

02

Device-Exclusive Keys

Cryptographic keys required to unlock the data are held exclusively on your personal devices.

03

Secure Enclave Execution

An isolated secure enclave temporarily decrypts data in memory to handle requests and immediately re-encrypts it.

04

Cross-Device Continuity

Maintains a continuous, long-term AI assistant memory across multiple devices without sacrificing privacy.

How it works

Private AI Compute Secure Memory Architecture
Sends requestTransports encrypted dataLoads sealed memoryUpdates & re-encryptsUser Device (with Keys)E2EE ChannelSecure EnclaveEncrypted Cloud Storage

Why it matters

This technical update provides the essential trust foundation for the widespread adoption of AI Agents. Previously, strict privacy required limiting data processing to a single physical device, hindering performance and continuity. By proving that cloud-scale computing can match on-device privacy standards through hardware-level protection and cryptography, it opens the door to truly helpful, hyper-personalized AI companions.

Who it affects

  • AI Developer
  • AI Researcher
  • Product Manager
  • Enterprise Leader

How to use it

  1. 1Cross-device personalized AI assistants
  2. 2Highly private personal knowledge bases and context storage

Limitations & caveats

  • Heavily reliant on specific hardware trusted execution environments and secure enclave support.
  • End-to-end encrypted transfers and enclave decryption might introduce minor processing latency under poor network conditions.

Related

TRACE: Reconstructing Private Robot Trajectories from Policy Gradients in Embodied RL
arXivAI Safety

TRACE: Reconstructing Private Robot Trajectories from Policy Gradients in Embodied RL

具身強化學習的隱私危機:TRACE 演算法僅憑「策略梯度」即可重建機器人私密軌跡

This paper introduces TRACE, a rapid temporal gradient-inversion attack showing that sharing only policy gradients in embodied RL fails to prevent reconstruction of private observation-action trajectories.

2 min read
The Invisible Trap: How Natural Context Can Easily Flip AI Decision Models
arXivAI Safety

The Invisible Trap: How Natural Context Can Easily Flip AI Decision Models

語言中的隱形陷阱:自然脈絡如何輕易誘騙 AI 決策模型

This study exposes a critical vulnerability in AI decision models: adding short, natural-looking context without altering the underlying question can easily trick models like Jev into making high-confidence wrong choices.

2 min read