AI vendors and your data

Vendors146Answers427

146 vendors · 427 answers

Gemini Enterprise Agent Platform and zero data retention changed Google, Oct 19, 2026

Google · Oct 19, 2026 · 21 added, 4 removed · seen by the weekly check

The pageAll Google terms
  1. Added: By default, Google's published Gemini models cache Customer Data to reduce latency and accelerate responses. Implicit caching uses two storage tiers:
  2. Added: In-memory caching : Enabled by default for supported Gemini models.
  3. Added: Durable caching : Enabled by default for supported Gemini models. For the list of supported models, see Context caching overview .
  4. Added: Implicit caching stores Customer Data (inputs, outputs, and derived data) in memory. In-memory cached data has the following properties:
  5. Added: It's stored only in memory, not at rest.
  6. Added: It's scoped to your project and is never served to another project.
  7. Added: It's deleted no later than 24 hours after it's written.
  8. Added: It's processed in the region that serves the request.
  9. Added: It's used only to serve your requests faster, and is never used to train or fine-tune models.
  10. Added: On models that support durable caching, when in-memory cache capacity is exhausted, Google stores derived cache data (key-value representations computed from your inputs) in durable storage within the Agent Platform serving environment. Durable cached data has the following properties:
  11. Added: It's stored at rest and encrypted with Google default encryption.
  12. Added: It's deleted no later than 24 hours after it's written, and is often evicted sooner.
  13. Added: It stays within the selected location and adheres to its Data Residency requirements when you use a regional or multi-regional endpoint. When you use the global endpoint, requests and their cached data can be served from any region.
  14. Added: Customer-managed encryption keys (CMEK) aren't supported for durable caching.
  15. Added: If your organization's policy does not permit Customer Data to be stored at rest, you can disable durable caching on a per-project basis and maintain in-memory caching. Alternatively, you can disable caching entirely. To disable durable caching across your organization rather than on a project level, contact your account team.
  16. Added: You can use the following curl commands to get caching status, disable caching, re-enable caching, or turn durable caching off and on. Turning off caching disables both in-memory caching and durable caching. When you disable or re-enable caching, the change applies to all Google Cloud regions. For more information about using Identity and Access Management to grant permissions required to enable or disable caching, see Gemini Enterprise Agent Platform access control with IAM . Expand the following sections to learn how to get the current cache setting, to disable caching, to enable caching, and to turn durable caching off and on.
  17. Added: Run the following command to check whether in-memory caching and durable caching are enabled for a project. To run this command, a user must be granted one of the following roles: roles/aiplatform.viewer , roles/aiplatform.user , or roles/aiplatform.admin .
  18. Added: Run the following curl command to turn off all caching for a Google Cloud project. This disables both in-memory caching and durable caching, and no cached data is retained. To run this command, a user must be granted the Gemini Enterprise Agent Platform administrator role, roles/aiplatform.admin .
  19. Added: To keep in-memory caching and turn off only durable caching, see Turn off durable caching .
  20. Removed: By default, Google's published Gemini models cache Customer Data (inputs, outputs, and derived data) in-memory to reduce latency and accelerate responses. This data is stored only in-memory (not at-rest), is isolated at the project level, and has a 24-hour TTL. Cached data is used only for improving service performance and adheres to all Data Residency requirements for the selected location and does not violate zero data retention. This feature can be disabled at the project level.
  21. Removed: You can use the following curl commands to get caching status, disable caching, or re-enable caching. When you disable or re-enable caching, the change applies to all Google Cloud regions. For more information about using Identity and Access Management to grant permissions required to enable or disable caching, see Gemini Enterprise Agent Platform access control with IAM . Expand the following sections to learn how to get the current cache setting, to disable caching, and to enable caching.
  22. Removed: Run the following command to determine if caching is enabled or turned off for a project. To run this command, a user must be granted one of the following roles: roles/aiplatform.viewer , roles/aiplatform.user , or roles/aiplatform.admin .
  23. Removed: Run the following curl command to disable caching for a Google Cloud project. To run this command, a user must be granted the Gemini Enterprise Agent Platform administrator role, roles/aiplatform.admin .
  24. Added: Run the following curl command to turn off durable caching and keep in-memory caching for a Google Cloud project. To run this command, a user must be granted the Gemini Enterprise Agent Platform administrator role, roles/aiplatform.admin .
  25. Added: If you turned off durable caching for a Google Cloud project and want to turn it back on, run the following curl command. To run this command, a user must be granted the Gemini Enterprise Agent Platform administrator role, roles/aiplatform.admin .
About this change
Page
docs.cloud.google.com/gemini-enterprise-agent-platform/resources/zero-data-retention
Kind
Documentation
Text hash
3e9921752d42 to 2dbe7eed6f4e
Dated by
the weekly check that first read the new text