| prod/aida- | | dictionary_item_added | - root['schemas']['LanguageLabsAidaSwebotProtoCodeReviewRequested']
- root['schemas']['LanguageLabsAidaSwebotProtoAgentActivity']['properties']['codeReviewRequested']
|
|---|
| values_changed | | root['resources']['swebot']['resources']['sources']['methods']['list']['parameters']['gaiaId']['description'] | | new_value | The gaia id of the user to list sources for, primarly should be used for installation repositories events from the GitHub webhook. |
|---|
| old_value | The gaia id of the user to list sources for, primarly should be used for installation repositories events from the GitHub webhook. TODO b/430268611 - guard this for prod job only |
|---|
|
|---|
| root['schemas']['LanguageLabsAidaSwebotProtoAgentActivity']['description'] | | new_value | Next ID: 22 |
|---|
| old_value | Next ID: 21 |
|---|
|
|---|
|
|---|
|
|---|
| prod/aida-v1 | | dictionary_item_added | - root['schemas']['LanguageLabsAidaSwebotProtoCodeReviewRequested']
- root['schemas']['LanguageLabsAidaSwebotProtoAgentActivity']['properties']['codeReviewRequested']
|
|---|
| values_changed | | root['resources']['swebot']['resources']['sources']['methods']['list']['parameters']['gaiaId']['description'] | | new_value | The gaia id of the user to list sources for, primarly should be used for installation repositories events from the GitHub webhook. |
|---|
| old_value | The gaia id of the user to list sources for, primarly should be used for installation repositories events from the GitHub webhook. TODO b/430268611 - guard this for prod job only |
|---|
|
|---|
| root['schemas']['LanguageLabsAidaSwebotProtoAgentActivity']['description'] | | new_value | Next ID: 22 |
|---|
| old_value | Next ID: 21 |
|---|
|
|---|
|
|---|
|
|---|
| prod/apigeeconnect- | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250720 |
|---|
|
|---|
|
|---|
|
|---|
| prod/apigeeconnect-v1 | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250720 |
|---|
|
|---|
|
|---|
|
|---|
| prod/asia-south1-connectgateway- | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/asia-south1-connectgateway-v1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/asia-south1-connectgateway-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/autopush-notifications-pa.sandbox- | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/autopush-notifications-pa.sandbox-v1 | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/autopush-proddata-notifications-pa.sandbox- | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/autopush-proddata-notifications-pa.sandbox-v1 | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/autopush-qual-playground-notifications-pa.sandbox- | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/autopush-qual-playground-notifications-pa.sandbox-v1 | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/chromedevicetoken- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/chromedevicetoken-v1 | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudmarketplaceadmin- | | dictionary_item_added | - root['schemas']['VendorInfo']['properties']['paymentsAccount']['description']
|
|---|
| values_changed | | root['resources']['partners']['methods']['vendorInfo']['description'] | | new_value | Note: The update call will not modify PaymentAccount data, as it's being deprecated. The authoritative source for Payments data is the "cloud-commerce-bizen-pod-spanner" database. To override Payment data, use InternalBizenServiceV2.UpdatePaymentConfigWithReason RPC. |
|---|
| old_value | Update a partner's VendorInfo |
|---|
|
|---|
| root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudmarketplaceadmin-v1test | | dictionary_item_added | - root['schemas']['VendorInfo']['properties']['paymentsAccount']['description']
|
|---|
| values_changed | | root['resources']['partners']['methods']['vendorInfo']['description'] | | new_value | Note: The update call will not modify PaymentAccount data, as it's being deprecated. The authoritative source for Payments data is the "cloud-commerce-bizen-pod-spanner" database. To override Payment data, use InternalBizenServiceV2.UpdatePaymentConfigWithReason RPC. |
|---|
| old_value | Update a partner's VendorInfo |
|---|
|
|---|
| root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudmarketplacepartner- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudmarketplacepartner-v2test | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudprivatecatalog- | | values_changed | | root['revision'] | | new_value | 20250803 |
|---|
| old_value | 20250727 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudprivatecatalog-v1 | | values_changed | | root['revision'] | | new_value | 20250803 |
|---|
| old_value | 20250727 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudprivatecatalog-v1alpha1 | | values_changed | | root['revision'] | | new_value | 20250803 |
|---|
| old_value | 20250727 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudprivatecatalog-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250803 |
|---|
| old_value | 20250727 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudprivatecatalogproducer- | | values_changed | | root['revision'] | | new_value | 20250803 |
|---|
| old_value | 20250727 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudprivatecatalogproducer-v1 | | values_changed | | root['revision'] | | new_value | 20250803 |
|---|
| old_value | 20250727 |
|---|
|
|---|
|
|---|
|
|---|
| prod/cloudprivatecatalogproducer-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250803 |
|---|
| old_value | 20250727 |
|---|
|
|---|
|
|---|
|
|---|
| prod/corplearning- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250806 |
|---|
|
|---|
|
|---|
|
|---|
| prod/corplearning-v1 | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250806 |
|---|
|
|---|
|
|---|
|
|---|
| prod/daily-dynamicmail-pa.sandbox- | | values_changed | | root['revision'] | | new_value | 20250809 |
|---|
| old_value | 20250807 |
|---|
|
|---|
| root['schemas']['DynamicMailSender']['properties']['serviceType']['enumDescriptions'][42] | | new_value | Dev version of the LucidOps service, used by the Mandiant Consulting Americas Engineering team to test changes before rolling out to a larger audience. |
|---|
| old_value | Dev version of LucidOps sends dynamic emails that, for example, allow users to reply to comments in case notifications. |
|---|
|
|---|
|
|---|
|
|---|
| prod/daily-dynamicmail-pa.sandbox-v2 | | values_changed | | root['revision'] | | new_value | 20250809 |
|---|
| old_value | 20250807 |
|---|
|
|---|
| root['schemas']['DynamicMailSender']['properties']['serviceType']['enumDescriptions'][42] | | new_value | Dev version of the LucidOps service, used by the Mandiant Consulting Americas Engineering team to test changes before rolling out to a larger audience. |
|---|
| old_value | Dev version of LucidOps sends dynamic emails that, for example, allow users to reply to comments in case notifications. |
|---|
|
|---|
|
|---|
|
|---|
| prod/dataaccessauditlogging-pa- | | values_changed | | root['revision'] | | new_value | 20250724 |
|---|
| old_value | 20250731 |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][76] | | new_value | User entered content, or data from which such content could be derived. This is used for data that has been gathered incidentally, such as user entered search query. Also things like sufficiently detailed search results from which the user query could be lossily reconstructed should be annotated as ST_USER_CONTENT. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
| old_value | Incidentally gathered user content or data from which such content could be derived. More specific types should be used if available. For example, user provided freeform text in response to a feedback prompt or questionare is ST_USER_CONTENT that does not have an applicable subtype. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][34] | | new_value | Full Google File API path location. Some example values for fields with this annotation are: * "/bigstore/my_bucket/my_object.txt" * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
| old_value | A full Google File API path location. More specific types should be preferred, e.g., ST_BIGSTORE_PATH or ST_BLOBSTORE_ID. Some example values for fields with this annotation are: * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][54] | | new_value | The following types define network endpoints such as IP addresses. |
|---|
| old_value | Data that defines a network endpoint. Prefer to use more specific types if available. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][15] | | new_value | Contains a human name. |
|---|
| old_value | Contains a human user's name. Online aliases should use ST_USERNAME. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][69] | | new_value | Google relationship IDs. |
|---|
| old_value | An ID used to identify an advertiser, publisher, or other corporate entity that Google has a business relationship with. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][41] | | new_value | Political Beliefs. |
|---|
| old_value | Data that identifies or implies the political beliefs of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][71] | | new_value | A partner ID. Partner is a generic term for a customer of Google. |
|---|
| old_value | The ID of a customer or partner of a Google product or service. This is differentiated from ST_CUSTOMER_ID in that a partner relationship is viewed as more symbiotic than a customer relationship. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][20] | | new_value | Ares IDs (http://go/project-ares-ids) are IDs use in the Google unified abuse infrastructure (http://go/ares). They identify entities that are targeted for abuse classification. |
|---|
| old_value | Ares IDs (go/project-ares-ids) are IDs used in the Google unified abuse infrastructure (go/ares). They identify entities that are targeted for abuse classification. Abuse IDs not related to Ares might use a combination of ST_FRAUD_ABUSE_INFO and ST_IDENTIFYING_ID or an appropriate subtype. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][64] | | new_value | Anonymous data points such as: - race, ethnicity - political affiliation |
|---|
| old_value | Data that has been modified in some way to be anonymous. Can be sensitive information such as race, ethnicity, political affiliation, etc., however it must not be capable of identifying any specific individual or group of individuals. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][15] | | new_value | Contains a human name. |
|---|
| old_value | Contains a human user's name. Online aliases should use ST_USERNAME. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][94] | | new_value | Calendar events. |
|---|
| old_value | The user generated email subject or content of an email message. Entities embedded within an email can also be considered ST_EMAIL_CONTENT however they should apply any other applicable types as well. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][26] | | new_value | Device USer ID (go/dusi) - a user-scoped (unique-per-user) device identifier. |
|---|
| old_value | A Device USer Id (go/dusi) that is a user-scoped (unique-per-user) device identifier. It is akin to an index for a given user's devices. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][44] | | new_value | Age |
|---|
| old_value | Data that identifies or implies the age of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][42] | | new_value | Religious Beliefs. |
|---|
| old_value | Data that identifies or implies the religious beliefs of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][64] | | new_value | Anonymous data points such as: - race, ethnicity - political affiliation |
|---|
| old_value | Data that has been modified in some way to be anonymous. Can be sensitive information such as race, ethnicity, political affiliation, etc., however it must not be capable of identifying any specific individual or group of individuals. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][28] | | new_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Blobstore: BlobRef for a blob *not* owned by Workspace, but which is associated with a specific user/entity; this has client-supplied bytes, and if those include other specific types, additional annotations like ST_GAIA_ID or (in the worst case) ST_USER_CONTENT should be added. Note that ST_BLOBSTORE_ID should also be added. Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
| old_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. Additionally, ST_BIGSTORE_PATH or ST_BLOBSTORE_ID should be used if applicable. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][40] | | new_value | Race and Ethnicity. |
|---|
| old_value | Data that identifies or implies the race or ethnic background of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][65] | | new_value | Demographic info such as: - age, year of birth - gender, marital status, number of children - education, income - language locale ST_DEMOGRAPHIC_INFO is intended for anonymized data and should not be used for identified data, or in a way that allows reidentification at 'default' logs access level. For non anonymized data, use ST_SENSITIVE_BACKGROUND_INFO specific annotations. As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
| old_value | Data that can be used to group users into defined categories based on shared characteristics. This data can have varying levels of sensitivity. SPII that is present and tied to an identifiable set of users should use the specific SPII semantic type whereas this should be reserved for instances which are anonymized. Demographic info can include: - age, year of birth - gender, marital status, number of children - education, income - language locale As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][70] | | new_value | Identifies customer IDs. For example, ID of the AdWords account. |
|---|
| old_value | The ID of a customer of a Google product or service. For example, the ID of an AdWords account. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][41] | | new_value | Political Beliefs. |
|---|
| old_value | Data that identifies or implies the political beliefs of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][13] | | new_value | The following types should be used to annotate the fields that contain data that can identify a person or entity directly or by reference. |
|---|
| old_value | An identifier that can be used to identify a user or an entity. Prefer to use the most specific ID type, e.g., prefer ST_GAIA_ID over ST_IDENTIFYING_ID if the field is a Gaia ID. An identifier that cannot directly identify a user or entity should use ST_PSEUDONYMOUS_ID instead. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][37] | | new_value | Details about an individual's past, present or future physical or mental health or condition. |
|---|
| old_value | Details about an individual's past, present, or future physical or mental health, condition, or operations. Data used to identify health records should use ST_MEDICAL_RECORD_NUMBER. Data collected from 1P wearables should use ST_FAROE_MBD_HFALD. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][26] | | new_value | Device USer ID (go/dusi) - a user-scoped (unique-per-user) device identifier. |
|---|
| old_value | A Device USer Id (go/dusi) that is a user-scoped (unique-per-user) device identifier. It is akin to an index for a given user's devices. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][28] | | new_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Blobstore: BlobRef for a blob *not* owned by Workspace, but which is associated with a specific user/entity; this has client-supplied bytes, and if those include other specific types, additional annotations like ST_GAIA_ID or (in the worst case) ST_USER_CONTENT should be added. Note that ST_BLOBSTORE_ID should also be added. Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
| old_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. Additionally, ST_BIGSTORE_PATH or ST_BLOBSTORE_ID should be used if applicable. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][35] | | new_value | The following types should be used only when the data has sensitive PII. This includes fields with passwords, credit card numbers, etc. See the data classification guidelines for more info. See go/spii for details on the subtypes of ST_SPII_ID. |
|---|
| old_value | Data that has sensitive PII, see go/spii for details on subtypes of PII. Prefer to use a more specific subtype of SPII. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][54] | | new_value | The following types define network endpoints such as IP addresses. |
|---|
| old_value | Data that defines a network endpoint. Prefer to use more specific types if available. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][17] | | new_value | Contains a user's Gaia ID. Please use qualifiers when the Gaia ID is a Google entity or service account rather than a user. |
|---|
| old_value | Contains a Gaia ID representing a user, group, business, service, device, etc. A field that only holds Google internal Gaia IDs should use the `is_google` qualifier. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][37] | | new_value | Details about an individual's past, present or future physical or mental health or condition. |
|---|
| old_value | Details about an individual's past, present, or future physical or mental health, condition, or operations. Data used to identify health records should use ST_MEDICAL_RECORD_NUMBER. Data collected from 1P wearables should use ST_FAROE_MBD_HFALD. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][43] | | new_value | Sexual orientation or gender identity. |
|---|
| old_value | Data that identifies or implies sexual orientation or gender identity of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][16] | | new_value | Contains a phone number. If for example the telephone number of the business is logged, this uniquely identifies the business and therefore its location. This is important to keep in mind since phone numbers are content dependant. If the phone number that is used to dial into a hangouts call is not identifying to a user it is considered less sensitive. |
|---|
| old_value | Contains a phone number. This identifies a user or entity associated with the phone number. The sensitivity of this data is content dependent. Examples: - The logging of a business's phone number could uniquely identify the business and therefore its location. - The phone number that is used to dial into a hangouts call belongs to a Google system and is considered less sensitive. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][40] | | new_value | Race and Ethnicity. |
|---|
| old_value | Data that identifies or implies the race or ethnic background of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][69] | | new_value | Google relationship IDs. |
|---|
| old_value | An ID used to identify an advertiser, publisher, or other corporate entity that Google has a business relationship with. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][35] | | new_value | The following types should be used only when the data has sensitive PII. This includes fields with passwords, credit card numbers, etc. See the data classification guidelines for more info. See go/spii for details on the subtypes of ST_SPII_ID. |
|---|
| old_value | Data that has sensitive PII, see go/spii for details on subtypes of PII. Prefer to use a more specific subtype of SPII. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][34] | | new_value | Full Google File API path location. Some example values for fields with this annotation are: * "/bigstore/my_bucket/my_object.txt" * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
| old_value | A full Google File API path location. More specific types should be preferred, e.g., ST_BIGSTORE_PATH or ST_BLOBSTORE_ID. Some example values for fields with this annotation are: * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][76] | | new_value | User entered content, or data from which such content could be derived. This is used for data that has been gathered incidentally, such as user entered search query. Also things like sufficiently detailed search results from which the user query could be lossily reconstructed should be annotated as ST_USER_CONTENT. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
| old_value | Incidentally gathered user content or data from which such content could be derived. More specific types should be used if available. For example, user provided freeform text in response to a feedback prompt or questionare is ST_USER_CONTENT that does not have an applicable subtype. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][94] | | new_value | Calendar events. |
|---|
| old_value | The user generated email subject or content of an email message. Entities embedded within an email can also be considered ST_EMAIL_CONTENT however they should apply any other applicable types as well. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][20] | | new_value | Ares IDs (http://go/project-ares-ids) are IDs use in the Google unified abuse infrastructure (http://go/ares). They identify entities that are targeted for abuse classification. |
|---|
| old_value | Ares IDs (go/project-ares-ids) are IDs used in the Google unified abuse infrastructure (go/ares). They identify entities that are targeted for abuse classification. Abuse IDs not related to Ares might use a combination of ST_FRAUD_ABUSE_INFO and ST_IDENTIFYING_ID or an appropriate subtype. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][65] | | new_value | Demographic info such as: - age, year of birth - gender, marital status, number of children - education, income - language locale ST_DEMOGRAPHIC_INFO is intended for anonymized data and should not be used for identified data, or in a way that allows reidentification at 'default' logs access level. For non anonymized data, use ST_SENSITIVE_BACKGROUND_INFO specific annotations. As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
| old_value | Data that can be used to group users into defined categories based on shared characteristics. This data can have varying levels of sensitivity. SPII that is present and tied to an identifiable set of users should use the specific SPII semantic type whereas this should be reserved for instances which are anonymized. Demographic info can include: - age, year of birth - gender, marital status, number of children - education, income - language locale As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][44] | | new_value | Age |
|---|
| old_value | Data that identifies or implies the age of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][17] | | new_value | Contains a user's Gaia ID. Please use qualifiers when the Gaia ID is a Google entity or service account rather than a user. |
|---|
| old_value | Contains a Gaia ID representing a user, group, business, service, device, etc. A field that only holds Google internal Gaia IDs should use the `is_google` qualifier. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][71] | | new_value | A partner ID. Partner is a generic term for a customer of Google. |
|---|
| old_value | The ID of a customer or partner of a Google product or service. This is differentiated from ST_CUSTOMER_ID in that a partner relationship is viewed as more symbiotic than a customer relationship. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][43] | | new_value | Sexual orientation or gender identity. |
|---|
| old_value | Data that identifies or implies sexual orientation or gender identity of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][13] | | new_value | The following types should be used to annotate the fields that contain data that can identify a person or entity directly or by reference. |
|---|
| old_value | An identifier that can be used to identify a user or an entity. Prefer to use the most specific ID type, e.g., prefer ST_GAIA_ID over ST_IDENTIFYING_ID if the field is a Gaia ID. An identifier that cannot directly identify a user or entity should use ST_PSEUDONYMOUS_ID instead. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][70] | | new_value | Identifies customer IDs. For example, ID of the AdWords account. |
|---|
| old_value | The ID of a customer of a Google product or service. For example, the ID of an AdWords account. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][42] | | new_value | Religious Beliefs. |
|---|
| old_value | Data that identifies or implies the religious beliefs of a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][16] | | new_value | Contains a phone number. If for example the telephone number of the business is logged, this uniquely identifies the business and therefore its location. This is important to keep in mind since phone numbers are content dependant. If the phone number that is used to dial into a hangouts call is not identifying to a user it is considered less sensitive. |
|---|
| old_value | Contains a phone number. This identifies a user or entity associated with the phone number. The sensitivity of this data is content dependent. Examples: - The logging of a business's phone number could uniquely identify the business and therefore its location. - The phone number that is used to dial into a hangouts call belongs to a Google system and is considered less sensitive. |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][88] | Content that defines an attribute of a service object, such as name, id, or other metadata. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][91] | Content to which no more specific annotation applies. This content is usually unstructured. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][93] | Email subject or content. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][96] | Non-email communication between users, through in-app messages or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][101] | Data collected from body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][107] | Third party data. For example, information sent by a publisher to Google that may contain sensitive info. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][116] | Security material (aka Secrets) This should be used for fields that contain security material such as cryptographic keys, nonces, and other entities that require special handling (never being recorded to disk or logged, etc). Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][130] | Used for data related to fraud and abuse. PII and User Content needs to be annotated with the appropriate semantic type in addition to this annotation. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][136] | Metric or computed value. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Examples: Count of running borg tasks Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][88] | Content that defines an attribute of a service object, such as name, id, or other metadata. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][91] | Content to which no more specific annotation applies. This content is usually unstructured. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][93] | Email subject or content. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][96] | Non-email communication between users, through in-app messages or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][101] | Data collected from body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][107] | Third party data. For example, information sent by a publisher to Google that may contain sensitive info. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][116] | Security material (aka Secrets) This should be used for fields that contain security material such as cryptographic keys, nonces, and other entities that require special handling (never being recorded to disk or logged, etc). Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][130] | Used for data related to fraud and abuse. PII and User Content needs to be annotated with the appropriate semantic type in addition to this annotation. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][136] | Metric or computed value. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Examples: Count of running borg tasks Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
|
|---|
| iterable_item_removed | | root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enum'][79] | ST_PERSONAL_DATA_CROSS_PA_SOURCE |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][79] | Search fields containing personal data obtained from other PAs, i.e. Workspace. See go/ptoken-aim-workspace-p13n-policy and go/aim-workspace-p13n-policy-doc for more details. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][89] | Content that defines an attribute of a service object's metadata. More specific user content types should be used if applicable. This metadata may be user visible but it is intended to provide meta-functionality such as searching, indexing, grouping or listing. For example, labels for GCP resources. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][92] | User core content is the subset of sensitive user content, captured by ST_PERSONAL_DATA, that is purely content and not used to operate the product or service it is part of. Examples: - A user's voice request to Google Assistant is sensitive as its identifying but it is not core content as it is used to operate the app, it is instead ST_VOICE. - A user's voice recorded and stored from an audio recorder app is core content as it is the core content of the app versus merely being used in operation. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][95] | The user generated content of a Calendar entity, e.g., an event name, description, or attendee list. This should be used for user generated content within Calendar entities. Data related to Calendar entities that is not user generated might use ST_WORKSPACE_OBJECT_INFO. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][97] | Non-email user generated text messaging communicated between users through in-app messaging or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][102] | Data collected from worn body sensors. ST_FAROE_MDB_HFALD may be more appropriate for information related to healthcare or physical or mental well-being derived from worn body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][108] | Third party data. For example, information sent by a publisher to Google that may contain sensitive information. Please apply any other semantic types that are applicable to the data as well. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][117] | Security material (aka Secrets) This should be used for fields that contain security material such as nonces and other entities that require special handling (never being recorded to disk or logged, etc) and are not covered by a more specific type. Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][131] | Data related to fraud and abuse. PII and user content should be annotated with the appropriate semantic type in addition to this. IDs related to abuse which are not from Ares should use this type. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][137] | Metric or computed value related to user data. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Counts and aggregates related to processing or the operation of Google systems should use ST_GOOGLE_OPERATIONAL_METRICS. Examples: Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enum'][79] | ST_PERSONAL_DATA_CROSS_PA_SOURCE |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][79] | Search fields containing personal data obtained from other PAs, i.e. Workspace. See go/ptoken-aim-workspace-p13n-policy and go/aim-workspace-p13n-policy-doc for more details. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][89] | Content that defines an attribute of a service object's metadata. More specific user content types should be used if applicable. This metadata may be user visible but it is intended to provide meta-functionality such as searching, indexing, grouping or listing. For example, labels for GCP resources. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][92] | User core content is the subset of sensitive user content, captured by ST_PERSONAL_DATA, that is purely content and not used to operate the product or service it is part of. Examples: - A user's voice request to Google Assistant is sensitive as its identifying but it is not core content as it is used to operate the app, it is instead ST_VOICE. - A user's voice recorded and stored from an audio recorder app is core content as it is the core content of the app versus merely being used in operation. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][95] | The user generated content of a Calendar entity, e.g., an event name, description, or attendee list. This should be used for user generated content within Calendar entities. Data related to Calendar entities that is not user generated might use ST_WORKSPACE_OBJECT_INFO. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][97] | Non-email user generated text messaging communicated between users through in-app messaging or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][102] | Data collected from worn body sensors. ST_FAROE_MDB_HFALD may be more appropriate for information related to healthcare or physical or mental well-being derived from worn body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][108] | Third party data. For example, information sent by a publisher to Google that may contain sensitive information. Please apply any other semantic types that are applicable to the data as well. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][117] | Security material (aka Secrets) This should be used for fields that contain security material such as nonces and other entities that require special handling (never being recorded to disk or logged, etc) and are not covered by a more specific type. Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][131] | Data related to fraud and abuse. PII and user content should be annotated with the appropriate semantic type in addition to this. IDs related to abuse which are not from Ares should use this type. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][137] | Metric or computed value related to user data. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Counts and aggregates related to processing or the operation of Google systems should use ST_GOOGLE_OPERATIONAL_METRICS. Examples: Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
|
|---|
|
|---|
| prod/dataaccessauditlogging-pa-v1 | | values_changed | | root['revision'] | | new_value | 20250731 |
|---|
| old_value | 20250724 |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][76] | | new_value | Incidentally gathered user content or data from which such content could be derived. More specific types should be used if available. For example, user provided freeform text in response to a feedback prompt or questionare is ST_USER_CONTENT that does not have an applicable subtype. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
| old_value | User entered content, or data from which such content could be derived. This is used for data that has been gathered incidentally, such as user entered search query. Also things like sufficiently detailed search results from which the user query could be lossily reconstructed should be annotated as ST_USER_CONTENT. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][34] | | new_value | A full Google File API path location. More specific types should be preferred, e.g., ST_BIGSTORE_PATH or ST_BLOBSTORE_ID. Some example values for fields with this annotation are: * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
| old_value | Full Google File API path location. Some example values for fields with this annotation are: * "/bigstore/my_bucket/my_object.txt" * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][54] | | new_value | Data that defines a network endpoint. Prefer to use more specific types if available. |
|---|
| old_value | The following types define network endpoints such as IP addresses. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][15] | | new_value | Contains a human user's name. Online aliases should use ST_USERNAME. |
|---|
| old_value | Contains a human name. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][69] | | new_value | An ID used to identify an advertiser, publisher, or other corporate entity that Google has a business relationship with. |
|---|
| old_value | Google relationship IDs. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][41] | | new_value | Data that identifies or implies the political beliefs of a user. |
|---|
| old_value | Political Beliefs. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][71] | | new_value | The ID of a customer or partner of a Google product or service. This is differentiated from ST_CUSTOMER_ID in that a partner relationship is viewed as more symbiotic than a customer relationship. |
|---|
| old_value | A partner ID. Partner is a generic term for a customer of Google. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][20] | | new_value | Ares IDs (go/project-ares-ids) are IDs used in the Google unified abuse infrastructure (go/ares). They identify entities that are targeted for abuse classification. Abuse IDs not related to Ares might use a combination of ST_FRAUD_ABUSE_INFO and ST_IDENTIFYING_ID or an appropriate subtype. |
|---|
| old_value | Ares IDs (http://go/project-ares-ids) are IDs use in the Google unified abuse infrastructure (http://go/ares). They identify entities that are targeted for abuse classification. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][64] | | new_value | Data that has been modified in some way to be anonymous. Can be sensitive information such as race, ethnicity, political affiliation, etc., however it must not be capable of identifying any specific individual or group of individuals. |
|---|
| old_value | Anonymous data points such as: - race, ethnicity - political affiliation |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][15] | | new_value | Contains a human user's name. Online aliases should use ST_USERNAME. |
|---|
| old_value | Contains a human name. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][94] | | new_value | The user generated email subject or content of an email message. Entities embedded within an email can also be considered ST_EMAIL_CONTENT however they should apply any other applicable types as well. |
|---|
| old_value | Calendar events. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][26] | | new_value | A Device USer Id (go/dusi) that is a user-scoped (unique-per-user) device identifier. It is akin to an index for a given user's devices. |
|---|
| old_value | Device USer ID (go/dusi) - a user-scoped (unique-per-user) device identifier. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][44] | | new_value | Data that identifies or implies the age of a user. |
|---|
| old_value | Age |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][42] | | new_value | Data that identifies or implies the religious beliefs of a user. |
|---|
| old_value | Religious Beliefs. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][64] | | new_value | Data that has been modified in some way to be anonymous. Can be sensitive information such as race, ethnicity, political affiliation, etc., however it must not be capable of identifying any specific individual or group of individuals. |
|---|
| old_value | Anonymous data points such as: - race, ethnicity - political affiliation |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][28] | | new_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. Additionally, ST_BIGSTORE_PATH or ST_BLOBSTORE_ID should be used if applicable. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
| old_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Blobstore: BlobRef for a blob *not* owned by Workspace, but which is associated with a specific user/entity; this has client-supplied bytes, and if those include other specific types, additional annotations like ST_GAIA_ID or (in the worst case) ST_USER_CONTENT should be added. Note that ST_BLOBSTORE_ID should also be added. Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][40] | | new_value | Data that identifies or implies the race or ethnic background of a user. |
|---|
| old_value | Race and Ethnicity. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][65] | | new_value | Data that can be used to group users into defined categories based on shared characteristics. This data can have varying levels of sensitivity. SPII that is present and tied to an identifiable set of users should use the specific SPII semantic type whereas this should be reserved for instances which are anonymized. Demographic info can include: - age, year of birth - gender, marital status, number of children - education, income - language locale As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
| old_value | Demographic info such as: - age, year of birth - gender, marital status, number of children - education, income - language locale ST_DEMOGRAPHIC_INFO is intended for anonymized data and should not be used for identified data, or in a way that allows reidentification at 'default' logs access level. For non anonymized data, use ST_SENSITIVE_BACKGROUND_INFO specific annotations. As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][70] | | new_value | The ID of a customer of a Google product or service. For example, the ID of an AdWords account. |
|---|
| old_value | Identifies customer IDs. For example, ID of the AdWords account. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][41] | | new_value | Data that identifies or implies the political beliefs of a user. |
|---|
| old_value | Political Beliefs. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][13] | | new_value | An identifier that can be used to identify a user or an entity. Prefer to use the most specific ID type, e.g., prefer ST_GAIA_ID over ST_IDENTIFYING_ID if the field is a Gaia ID. An identifier that cannot directly identify a user or entity should use ST_PSEUDONYMOUS_ID instead. |
|---|
| old_value | The following types should be used to annotate the fields that contain data that can identify a person or entity directly or by reference. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][37] | | new_value | Details about an individual's past, present, or future physical or mental health, condition, or operations. Data used to identify health records should use ST_MEDICAL_RECORD_NUMBER. Data collected from 1P wearables should use ST_FAROE_MBD_HFALD. |
|---|
| old_value | Details about an individual's past, present or future physical or mental health or condition. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][26] | | new_value | A Device USer Id (go/dusi) that is a user-scoped (unique-per-user) device identifier. It is akin to an index for a given user's devices. |
|---|
| old_value | Device USer ID (go/dusi) - a user-scoped (unique-per-user) device identifier. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][28] | | new_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. Additionally, ST_BIGSTORE_PATH or ST_BLOBSTORE_ID should be used if applicable. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
| old_value | Identifier for any Google object in storage. A field that contains the ID of a Workspace object (or which *may* contain such an ID, if it's multipurpose), should use ST_WORKSPACE_OBJECT_ID instead. ST_GOOGLE_OBJECT_ID *may not* directly identify a user, though in cases where an object has a user owner, that user could be identified after looking up the object by this ID. Examples: Blobstore: BlobRef for a blob *not* owned by Workspace, but which is associated with a specific user/entity; this has client-supplied bytes, and if those include other specific types, additional annotations like ST_GAIA_ID or (in the worst case) ST_USER_CONTENT should be added. Note that ST_BLOBSTORE_ID should also be added. Geo: Place ID YouTube: ID of a video *not* owned by Workspace |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][35] | | new_value | Data that has sensitive PII, see go/spii for details on subtypes of PII. Prefer to use a more specific subtype of SPII. |
|---|
| old_value | The following types should be used only when the data has sensitive PII. This includes fields with passwords, credit card numbers, etc. See the data classification guidelines for more info. See go/spii for details on the subtypes of ST_SPII_ID. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][54] | | new_value | Data that defines a network endpoint. Prefer to use more specific types if available. |
|---|
| old_value | The following types define network endpoints such as IP addresses. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][17] | | new_value | Contains a Gaia ID representing a user, group, business, service, device, etc. A field that only holds Google internal Gaia IDs should use the `is_google` qualifier. |
|---|
| old_value | Contains a user's Gaia ID. Please use qualifiers when the Gaia ID is a Google entity or service account rather than a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][37] | | new_value | Details about an individual's past, present, or future physical or mental health, condition, or operations. Data used to identify health records should use ST_MEDICAL_RECORD_NUMBER. Data collected from 1P wearables should use ST_FAROE_MBD_HFALD. |
|---|
| old_value | Details about an individual's past, present or future physical or mental health or condition. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][43] | | new_value | Data that identifies or implies sexual orientation or gender identity of a user. |
|---|
| old_value | Sexual orientation or gender identity. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][16] | | new_value | Contains a phone number. This identifies a user or entity associated with the phone number. The sensitivity of this data is content dependent. Examples: - The logging of a business's phone number could uniquely identify the business and therefore its location. - The phone number that is used to dial into a hangouts call belongs to a Google system and is considered less sensitive. |
|---|
| old_value | Contains a phone number. If for example the telephone number of the business is logged, this uniquely identifies the business and therefore its location. This is important to keep in mind since phone numbers are content dependant. If the phone number that is used to dial into a hangouts call is not identifying to a user it is considered less sensitive. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][40] | | new_value | Data that identifies or implies the race or ethnic background of a user. |
|---|
| old_value | Race and Ethnicity. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][69] | | new_value | An ID used to identify an advertiser, publisher, or other corporate entity that Google has a business relationship with. |
|---|
| old_value | Google relationship IDs. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][35] | | new_value | Data that has sensitive PII, see go/spii for details on subtypes of PII. Prefer to use a more specific subtype of SPII. |
|---|
| old_value | The following types should be used only when the data has sensitive PII. This includes fields with passwords, credit card numbers, etc. See the data classification guidelines for more info. See go/spii for details on the subtypes of ST_SPII_ID. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][34] | | new_value | A full Google File API path location. More specific types should be preferred, e.g., ST_BIGSTORE_PATH or ST_BLOBSTORE_ID. Some example values for fields with this annotation are: * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
| old_value | Full Google File API path location. Some example values for fields with this annotation are: * "/bigstore/my_bucket/my_object.txt" * "/cns/sandbox/home/ares-eng/some_file.txt" * "/sm/streamer/youtube/7/e/" |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][76] | | new_value | Incidentally gathered user content or data from which such content could be derived. More specific types should be used if available. For example, user provided freeform text in response to a feedback prompt or questionare is ST_USER_CONTENT that does not have an applicable subtype. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
| old_value | User entered content, or data from which such content could be derived. This is used for data that has been gathered incidentally, such as user entered search query. Also things like sufficiently detailed search results from which the user query could be lossily reconstructed should be annotated as ST_USER_CONTENT. WARNING: Available at default access. If a field may contain (S)PII, use ST_PERSONAL_DATA instead. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][94] | | new_value | The user generated email subject or content of an email message. Entities embedded within an email can also be considered ST_EMAIL_CONTENT however they should apply any other applicable types as well. |
|---|
| old_value | Calendar events. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][20] | | new_value | Ares IDs (go/project-ares-ids) are IDs used in the Google unified abuse infrastructure (go/ares). They identify entities that are targeted for abuse classification. Abuse IDs not related to Ares might use a combination of ST_FRAUD_ABUSE_INFO and ST_IDENTIFYING_ID or an appropriate subtype. |
|---|
| old_value | Ares IDs (http://go/project-ares-ids) are IDs use in the Google unified abuse infrastructure (http://go/ares). They identify entities that are targeted for abuse classification. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][65] | | new_value | Data that can be used to group users into defined categories based on shared characteristics. This data can have varying levels of sensitivity. SPII that is present and tied to an identifiable set of users should use the specific SPII semantic type whereas this should be reserved for instances which are anonymized. Demographic info can include: - age, year of birth - gender, marital status, number of children - education, income - language locale As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
| old_value | Demographic info such as: - age, year of birth - gender, marital status, number of children - education, income - language locale ST_DEMOGRAPHIC_INFO is intended for anonymized data and should not be used for identified data, or in a way that allows reidentification at 'default' logs access level. For non anonymized data, use ST_SENSITIVE_BACKGROUND_INFO specific annotations. As an example, full birthdate + Zip code + gender uniquely identifies 87% of US residents. It's recommended that birthdate be split into day/month/year components, with the former two annotated ST_PERSONAL_DATA and the third ST_DEMOGRAPHIC_INFO to reduce the risk of reidentification at 'default' logs access level. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][44] | | new_value | Data that identifies or implies the age of a user. |
|---|
| old_value | Age |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][17] | | new_value | Contains a Gaia ID representing a user, group, business, service, device, etc. A field that only holds Google internal Gaia IDs should use the `is_google` qualifier. |
|---|
| old_value | Contains a user's Gaia ID. Please use qualifiers when the Gaia ID is a Google entity or service account rather than a user. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][71] | | new_value | The ID of a customer or partner of a Google product or service. This is differentiated from ST_CUSTOMER_ID in that a partner relationship is viewed as more symbiotic than a customer relationship. |
|---|
| old_value | A partner ID. Partner is a generic term for a customer of Google. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][43] | | new_value | Data that identifies or implies sexual orientation or gender identity of a user. |
|---|
| old_value | Sexual orientation or gender identity. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][13] | | new_value | An identifier that can be used to identify a user or an entity. Prefer to use the most specific ID type, e.g., prefer ST_GAIA_ID over ST_IDENTIFYING_ID if the field is a Gaia ID. An identifier that cannot directly identify a user or entity should use ST_PSEUDONYMOUS_ID instead. |
|---|
| old_value | The following types should be used to annotate the fields that contain data that can identify a person or entity directly or by reference. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][70] | | new_value | The ID of a customer of a Google product or service. For example, the ID of an AdWords account. |
|---|
| old_value | Identifies customer IDs. For example, ID of the AdWords account. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][42] | | new_value | Data that identifies or implies the religious beliefs of a user. |
|---|
| old_value | Religious Beliefs. |
|---|
|
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][16] | | new_value | Contains a phone number. This identifies a user or entity associated with the phone number. The sensitivity of this data is content dependent. Examples: - The logging of a business's phone number could uniquely identify the business and therefore its location. - The phone number that is used to dial into a hangouts call belongs to a Google system and is considered less sensitive. |
|---|
| old_value | Contains a phone number. If for example the telephone number of the business is logged, this uniquely identifies the business and therefore its location. This is important to keep in mind since phone numbers are content dependant. If the phone number that is used to dial into a hangouts call is not identifying to a user it is considered less sensitive. |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enum'][79] | ST_PERSONAL_DATA_CROSS_PA_SOURCE |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][79] | Search fields containing personal data obtained from other PAs, i.e. Workspace. See go/ptoken-aim-workspace-p13n-policy and go/aim-workspace-p13n-policy-doc for more details. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][89] | Content that defines an attribute of a service object's metadata. More specific user content types should be used if applicable. This metadata may be user visible but it is intended to provide meta-functionality such as searching, indexing, grouping or listing. For example, labels for GCP resources. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][92] | User core content is the subset of sensitive user content, captured by ST_PERSONAL_DATA, that is purely content and not used to operate the product or service it is part of. Examples: - A user's voice request to Google Assistant is sensitive as its identifying but it is not core content as it is used to operate the app, it is instead ST_VOICE. - A user's voice recorded and stored from an audio recorder app is core content as it is the core content of the app versus merely being used in operation. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][95] | The user generated content of a Calendar entity, e.g., an event name, description, or attendee list. This should be used for user generated content within Calendar entities. Data related to Calendar entities that is not user generated might use ST_WORKSPACE_OBJECT_INFO. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][97] | Non-email user generated text messaging communicated between users through in-app messaging or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][102] | Data collected from worn body sensors. ST_FAROE_MDB_HFALD may be more appropriate for information related to healthcare or physical or mental well-being derived from worn body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][108] | Third party data. For example, information sent by a publisher to Google that may contain sensitive information. Please apply any other semantic types that are applicable to the data as well. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][117] | Security material (aka Secrets) This should be used for fields that contain security material such as nonces and other entities that require special handling (never being recorded to disk or logged, etc) and are not covered by a more specific type. Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][131] | Data related to fraud and abuse. PII and user content should be annotated with the appropriate semantic type in addition to this. IDs related to abuse which are not from Ares should use this type. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][137] | Metric or computed value related to user data. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Counts and aggregates related to processing or the operation of Google systems should use ST_GOOGLE_OPERATIONAL_METRICS. Examples: Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enum'][79] | ST_PERSONAL_DATA_CROSS_PA_SOURCE |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][79] | Search fields containing personal data obtained from other PAs, i.e. Workspace. See go/ptoken-aim-workspace-p13n-policy and go/aim-workspace-p13n-policy-doc for more details. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][89] | Content that defines an attribute of a service object's metadata. More specific user content types should be used if applicable. This metadata may be user visible but it is intended to provide meta-functionality such as searching, indexing, grouping or listing. For example, labels for GCP resources. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][92] | User core content is the subset of sensitive user content, captured by ST_PERSONAL_DATA, that is purely content and not used to operate the product or service it is part of. Examples: - A user's voice request to Google Assistant is sensitive as its identifying but it is not core content as it is used to operate the app, it is instead ST_VOICE. - A user's voice recorded and stored from an audio recorder app is core content as it is the core content of the app versus merely being used in operation. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][95] | The user generated content of a Calendar entity, e.g., an event name, description, or attendee list. This should be used for user generated content within Calendar entities. Data related to Calendar entities that is not user generated might use ST_WORKSPACE_OBJECT_INFO. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][97] | Non-email user generated text messaging communicated between users through in-app messaging or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][102] | Data collected from worn body sensors. ST_FAROE_MDB_HFALD may be more appropriate for information related to healthcare or physical or mental well-being derived from worn body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][108] | Third party data. For example, information sent by a publisher to Google that may contain sensitive information. Please apply any other semantic types that are applicable to the data as well. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][117] | Security material (aka Secrets) This should be used for fields that contain security material such as nonces and other entities that require special handling (never being recorded to disk or logged, etc) and are not covered by a more specific type. Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][131] | Data related to fraud and abuse. PII and user content should be annotated with the appropriate semantic type in addition to this. IDs related to abuse which are not from Ares should use this type. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][137] | Metric or computed value related to user data. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Counts and aggregates related to processing or the operation of Google systems should use ST_GOOGLE_OPERATIONAL_METRICS. Examples: Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
|
|---|
| iterable_item_removed | | root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][88] | Content that defines an attribute of a service object, such as name, id, or other metadata. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][91] | Content to which no more specific annotation applies. This content is usually unstructured. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][93] | Email subject or content. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][96] | Non-email communication between users, through in-app messages or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][101] | Data collected from body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][107] | Third party data. For example, information sent by a publisher to Google that may contain sensitive info. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][116] | Security material (aka Secrets) This should be used for fields that contain security material such as cryptographic keys, nonces, and other entities that require special handling (never being recorded to disk or logged, etc). Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][130] | Used for data related to fraud and abuse. PII and User Content needs to be annotated with the appropriate semantic type in addition to this annotation. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessDataAccessLogProtoFieldMetadata']['properties']['semanticType']['items']['enumDescriptions'][136] | Metric or computed value. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Examples: Count of running borg tasks Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][88] | Content that defines an attribute of a service object, such as name, id, or other metadata. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][91] | Content to which no more specific annotation applies. This content is usually unstructured. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][93] | Email subject or content. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][96] | Non-email communication between users, through in-app messages or SMS/MMS. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][101] | Data collected from body sensors. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][107] | Third party data. For example, information sent by a publisher to Google that may contain sensitive info. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][116] | Security material (aka Secrets) This should be used for fields that contain security material such as cryptographic keys, nonces, and other entities that require special handling (never being recorded to disk or logged, etc). Also see: go/pwg-cloud-secrets go/cloud-dcg-secrets-draft |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][130] | Used for data related to fraud and abuse. PII and User Content needs to be annotated with the appropriate semantic type in addition to this annotation. Examples: * Abuse details such object state at the time of the abuse, whether the incident was sent for review. * Abuse verdicts. * Spam feature sets. |
|---|
| root['schemas']['DataaccessauditloggingPaSecurityDataAccessResourceId']['properties']['semanticType']['items']['enumDescriptions'][136] | Metric or computed value. This should not be used for values which are aggregated across a user or multiple users, there are more specific types for those below. If user filtering occurs or a user/customer count/ID appears with the data, then the aggregate should use one of the user specific subtypes. Examples: Count of running borg tasks Drive: quota bytes consumed by an item Gmail: count of characters in a message Meet: count of attendees in a meeting |
|---|
|
|---|
|
|---|
| prod/dataconnectors- | | values_changed | | root['revision'] | | new_value | 20250109 |
|---|
| old_value | 20250116 |
|---|
|
|---|
|
|---|
|
|---|
| prod/drivemetadata- | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250728 |
|---|
|
|---|
|
|---|
|
|---|
| prod/drivemetadata-v1 | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250728 |
|---|
|
|---|
|
|---|
|
|---|
| prod/drivemetadata-v1alpha | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250728 |
|---|
|
|---|
|
|---|
|
|---|
| prod/europe-west2-connectgateway- | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/europe-west2-connectgateway-v1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/europe-west2-connectgateway-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebaseapptesters- | | values_changed | | root['resources']['devices']['methods']['list']['parameters']['pageSize']['description'] | | new_value | Optional. Maximum number of devices to return |
|---|
| old_value | Maximum number of devices to return |
|---|
|
|---|
| root['resources']['devices']['methods']['list']['parameters']['pageToken']['description'] | | new_value | Optional. Page token received from previous ListDevices call |
|---|
| old_value | Page token received from previous ListDevices call |
|---|
|
|---|
| root['revision'] | | new_value | 20250808 |
|---|
| old_value | 20250807 |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaDevice']['properties']['name']['description'] | | new_value | Identifier. The name of the device Format: devices/{device} |
|---|
| old_value | The name of the device Format: devices/{device} |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaFeedbackReport']['properties']['name']['description'] | | new_value | Identifier. The name of the feedback Format: projects/{project}/installations/{installation}/releases/{release}/feedbackReports/{feedback_report} |
|---|
| old_value | The name of the feedback Format: projects/{project}/installations/{installation}/releases/{release}/feedbackReports/{feedback_report} |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaFeedbackReport']['properties']['text']['description'] | | new_value | Required. The text elaborating on the feedback |
|---|
| old_value | The text elaborating on the feedback |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaInvitation']['properties']['name']['description'] | | new_value | Identifier. The name of the invitation to retrieve Format: invitations/{invitation} |
|---|
| old_value | The name of the invitation to retrieve Format: invitations/{invitation} |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaInviteLink']['properties']['name']['description'] | | new_value | Identifier. The name of the invite link Format: inviteLinks/{invite_link} |
|---|
| old_value | The name of the invite link Format: inviteLinks/{invite_link} |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebaseapptesters-v1 | | values_changed | | root['revision'] | | new_value | 20250808 |
|---|
| old_value | 20250807 |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebaseapptesters-v1alpha | | values_changed | | root['resources']['devices']['methods']['list']['parameters']['pageSize']['description'] | | new_value | Optional. Maximum number of devices to return |
|---|
| old_value | Maximum number of devices to return |
|---|
|
|---|
| root['resources']['devices']['methods']['list']['parameters']['pageToken']['description'] | | new_value | Optional. Page token received from previous ListDevices call |
|---|
| old_value | Page token received from previous ListDevices call |
|---|
|
|---|
| root['revision'] | | new_value | 20250808 |
|---|
| old_value | 20250807 |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaDevice']['properties']['name']['description'] | | new_value | Identifier. The name of the device Format: devices/{device} |
|---|
| old_value | The name of the device Format: devices/{device} |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaFeedbackReport']['properties']['name']['description'] | | new_value | Identifier. The name of the feedback Format: projects/{project}/installations/{installation}/releases/{release}/feedbackReports/{feedback_report} |
|---|
| old_value | The name of the feedback Format: projects/{project}/installations/{installation}/releases/{release}/feedbackReports/{feedback_report} |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaFeedbackReport']['properties']['text']['description'] | | new_value | Required. The text elaborating on the feedback |
|---|
| old_value | The text elaborating on the feedback |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaInvitation']['properties']['name']['description'] | | new_value | Identifier. The name of the invitation to retrieve Format: invitations/{invitation} |
|---|
| old_value | The name of the invitation to retrieve Format: invitations/{invitation} |
|---|
|
|---|
| root['schemas']['GoogleFirebaseApptestersV1alphaInviteLink']['properties']['name']['description'] | | new_value | Identifier. The name of the invite link Format: inviteLinks/{invite_link} |
|---|
| old_value | The name of the invite link Format: inviteLinks/{invite_link} |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebasecrashlytics- | | values_changed | | root['revision'] | | new_value | 20250808 |
|---|
| old_value | 20250807 |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebasecrashlytics-v1alpha | | values_changed | | root['revision'] | | new_value | 20250808 |
|---|
| old_value | 20250807 |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebaseextensions- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250804 |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebaseextensions-v1beta | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250804 |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebaseextensionspublisher- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250804 |
|---|
|
|---|
|
|---|
|
|---|
| prod/firebaseextensionspublisher-v1beta | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250804 |
|---|
|
|---|
|
|---|
|
|---|
| prod/gdchardwaremanagement- | | values_changed | | root['revision'] | | new_value | 20250730 |
|---|
| old_value | 20250724 |
|---|
|
|---|
|
|---|
|
|---|
| prod/gdchardwaremanagement-v1alpha | | values_changed | | root['revision'] | | new_value | 20250730 |
|---|
| old_value | 20250724 |
|---|
|
|---|
|
|---|
|
|---|
| prod/guidedhelp-pa- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/guidedhelp-pa-v1 | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/hourly-dynamicmail-pa.sandbox- | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['DynamicMailSender']['properties']['serviceType']['enumDescriptions'][42] | | new_value | Dev version of the LucidOps service, used by the Mandiant Consulting Americas Engineering team to test changes before rolling out to a larger audience. |
|---|
| old_value | Dev version of LucidOps sends dynamic emails that, for example, allow users to reply to comments in case notifications. |
|---|
|
|---|
|
|---|
|
|---|
| prod/hourly-dynamicmail-pa.sandbox-v2 | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['DynamicMailSender']['properties']['serviceType']['enumDescriptions'][42] | | new_value | Dev version of the LucidOps service, used by the Mandiant Consulting Americas Engineering team to test changes before rolling out to a larger audience. |
|---|
| old_value | Dev version of LucidOps sends dynamic emails that, for example, allow users to reply to comments in case notifications. |
|---|
|
|---|
|
|---|
|
|---|
| prod/localservicespartner- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250806 |
|---|
|
|---|
|
|---|
|
|---|
| prod/localservicespartner-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250806 |
|---|
|
|---|
|
|---|
|
|---|
| prod/media3p- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250806 |
|---|
|
|---|
|
|---|
|
|---|
| prod/media3p-v1 | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250806 |
|---|
|
|---|
|
|---|
|
|---|
| prod/meshconfig- | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250803 |
|---|
|
|---|
|
|---|
|
|---|
| prod/meshconfig-v1alpha1 | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250803 |
|---|
|
|---|
|
|---|
|
|---|
| prod/meshconfig-v1internal | | values_changed | | root['revision'] | | new_value | 20250806 |
|---|
| old_value | 20250803 |
|---|
|
|---|
|
|---|
|
|---|
| prod/mobilemlaccelerationcompatibility- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/mobilemlaccelerationcompatibility-v1 | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/searchresearcherresults- | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/searchresearcherresults-v1 | | values_changed | | root['revision'] | | new_value | 20250807 |
|---|
| old_value | 20250805 |
|---|
|
|---|
|
|---|
|
|---|
| prod/southamerica-east1-connectgateway- | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/southamerica-east1-connectgateway-v1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/southamerica-east1-connectgateway-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/staging-notifications-pa.sandbox- | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/staging-notifications-pa.sandbox-v1 | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/staging-qual-qa-notifications-pa.sandbox- | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/staging-qual-qa-notifications-pa.sandbox-v1 | | values_changed | | root['revision'] | | new_value | 20250810 |
|---|
| old_value | 20250808 |
|---|
|
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][36] | | new_value | Change the clothes of the subject to a new clothes described by the text. |
|---|
| old_value | Change the clothes of the subject to a new clothes described by the text. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| iterable_item_added | | root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][37] | MAKE_SMILE |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][38] | REMOVE_OCCLUSION |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enum'][39] | OPEN_EYES |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][37] | Make the person in the image smile using AI. Optionally uses reference images of the person to determine the smile appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][38] | Remove the occlusion object hidding the person face as described by text using AI. Optionally uses reference images of the person to determine face appearance. |
|---|
| root['schemas']['PhotosEffects__NonSerializableEffectParams']['properties']['effects']['items']['enumDescriptions'][39] | Open the eyes of the person in the image using AI. Optionally uses reference images of the person to determine open eyes appearance. LINT.ThenChange(//depot/google3/photos/security/provenance/c2pa_write_helper.cc) |
|---|
|
|---|
|
|---|
| prod/us-central1-connectgateway- | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/us-central1-connectgateway-v1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/us-central1-connectgateway-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/us-west3-connectgateway- | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/us-west3-connectgateway-v1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|
| prod/us-west3-connectgateway-v1beta1 | | values_changed | | root['revision'] | | new_value | 20250801 |
|---|
| old_value | 20250725 |
|---|
|
|---|
|
|---|
|
|---|