Sensitive Data Protection release notes

Sensitive Data Protection content policies are in General Availability. You can use content policies to evaluate content and return an ALLOW or BLOCK verdict based on data sensitivity.

For more information about content policies, see the following:

• Overview of content policies
• Create and manage content policies

Sensitive Data Protection content policies are integrated with Gemini Enterprise. For more information, see the following:

• Protect sensitive data in sources
• Protect sensitive data in Gemini Notebook Enterprise sources

Image scanning is available in the following regions:

• europe-north1
• us-central1

For more information, see Locations that support image scanning.

The ANTHROPIC_API_KEY, GEMINI_API_KEY, and OPENAI_API_KEY infoType detectors are available in all regions. For more information about all built-in infoTypes, see the InfoType detector reference.

The CRIME_STATUS infoType detector is available in all regions. For more information about all built-in infoTypes, see the InfoType detector reference.

If you leave InfoType.version unset or set it to stable when setting the MEDICAL_ID infoType in your InspectConfig, Sensitive Data Protection includes MEDICAL_RECORD_NUMBER findings as type MEDICAL_ID in the scan results.

You can still use the old functionality by setting InfoType.version to legacy for the next 90 days.

The SWITZERLAND_PASSPORT infoType detector is available in all regions. For more information about all built-in infoTypes, see the InfoType detector reference.

You can configure Sensitive Data Protection to detect specific file labels, which can represent Google Drive labels or Microsoft sensitivity labels. For more information, see Create a custom metadata label detector.

Image safety classification infoTypes are now supported in ExcludeByImageFindings and AdjustByImageFindings detection rules.

For information about configuring these rules, see Modifying infoType detectors to refine scan results.

Image scanning is available in the following cloud regions:

• asia-southeast1
• us-east4
• us-west1

For more information, see Locations that support image scanning.

Between July 2025 and June 2026, some table data profiles saved to BigQuery contained an incorrect 1970-01-01 timestamp instead of NULL in expiration_time for tables that don't expire. This issue has been fixed. New exports of table data profiles show the correct expiration timestamps.

Added support for inspecting and de-identifying batched content. You can now include a BatchContentItem in your ContentItem requests.

The OBJECT_TYPE/PERSON/SIGNATURE infoType detector is available in global and the asia, europe, and us multi-regions. For more information about all infoTypes, see InfoType detector reference.

Added support for inspecting and de-identifying conversational content. You can now include a Conversation in your ContentItem requests.

If you set InfoType.version to latest when including the MEDICAL_ID infoType in your InspectConfig, Sensitive Data Protection will now include MEDICAL_RECORD_NUMBER findings as type MEDICAL_ID in the scan results.

You can still use the old functionality by setting InfoType.version to stable. In 30 days, the new functionality will be promoted to stable.

You can configure Sensitive Data Protection to detect specific client-provided metadata. For more information, see Create a custom metadata label detector.

The USER_NAME infoType detector is available in all regions. For more information about all built-in infoTypes, see the InfoType detector reference.

The CRIME_STATUS infoType detector is available in Preview. For more information about all infoTypes, see InfoType detector reference.

You can configure Sensitive Data Protection to detect specific metadata labels in your content. For more information, see Create a custom metadata label detector.

Sensitive Data Protection can discover and profile Vertex AI tuning jobs. For more information, see Sensitive data discovery for Vertex AI.