KnowledgeAnswersSensitivityStoragePolicy

AI Overview😉

  • The potential purpose of this module is to control and manage the storage of sensitive data within Google's search results, ensuring that certain information is encrypted or removed to protect user privacy and prevent unauthorized access.
  • This module could impact search results by influencing how data is stored and retrieved, potentially affecting the ranking or visibility of certain results. For example, if a website's data is not properly encrypted, it may be penalized or removed from search results. On the other hand, websites that comply with these storage policies may be rewarded with better visibility or ranking.
  • A website may change things to be more favorable for this function by ensuring that sensitive data is properly encrypted and stored, complying with Google's storage policies. This may involve implementing encryption protocols, removing unnecessary sensitive data, and configuring storage settings to align with Google's requirements. By doing so, a website can increase its chances of being indexed and ranked higher in search results.

Interesting Module? Vote 👇

Voting helps other researchers find interesting modules.

Current Votes: 0

GoogleApi.ContentWarehouse.V1.Model.KnowledgeAnswersSensitivityStoragePolicy (google_api_content_warehouse v0.4.0)

Policies controlling the storage.

Attributes

  • encryptArgumentValue (type: boolean(), default: nil) - The contents of the argument value should be encrypted before being written to a persistent storage (even if the storage has short time-to-live). No-op when specified at intent level.
  • encryptFieldCandidateValueTerm (type: boolean(), default: nil) - If true, triggers encryption of |value_term| [1] and move into |sensitive_value_term|. This is useful to support finer grain encryption controls for disambiguation, where the broader |encrypt_argument_value| is too restrictive. In particular, when we know that the values being disambiguated are non-sensitive (e.g. opaque event IDs), but the value_terms are sensitive (e.g. event titles), it can be helpful for debugging purposes to circulate the value unencrypted. This policy only has an effect when configured at argument-level. It has no effect in Intent or PreviousQuery stanzas. See go/delete-event-disambiguation-redaction-v2 for context and usage. [1]cs/s:quality.dialog_manager.IntentStateSignals.FieldCandidate.value_term
  • encryptQueryAnnotationData (type: boolean(), default: nil) - If this is set true, we encrypt QueryAnnotationDataProto prior to writing it to Footprint ASSISTANT_EPHEMERAL corpus. This enables restricting ACL to the data.
  • scrubAuxiliaryFieldsInConversationSnapshot (type: boolean(), default: nil) - If this is set to true, the following fields in ConversationSnapshot are scrubbed: circulated_state.squery spoken_query * All client_op arguments |from_assistant| interactions

Summary

Types

t()

Functions

decode(value, options)

Unwrap a decoded JSON object into its complex fields.

Types

Link to this type

t()

@type t() ::
  %GoogleApi.ContentWarehouse.V1.Model.KnowledgeAnswersSensitivityStoragePolicy{
    encryptArgumentValue: boolean() | nil,
    encryptFieldCandidateValueTerm: boolean() | nil,
    encryptQueryAnnotationData: boolean() | nil,
    scrubAuxiliaryFieldsInConversationSnapshot: boolean() | nil
  }

Functions

Link to this function

decode(value, options)

@spec decode(struct(), keyword()) :: struct()

Unwrap a decoded JSON object into its complex fields.