KnowledgeAnswersSensitivitySensitivity

AI Overview😉

  • The potential purpose of this module is to identify and handle sensitive user data, such as personal information, across multiple accounts. This module aims to ensure that sensitive data is not leaked or mixed between accounts, which could compromise user privacy.
  • This module could impact search results by filtering out or modifying queries that contain sensitive data, especially if the data is from multiple accounts. This could lead to more accurate and personalized results, while also protecting user privacy. Additionally, it may influence the ranking of results, giving more weight to sources that respect user privacy and handle sensitive data properly.
  • To be more favorable for this function, a website could: Clearly annotate and separate sensitive user data, especially when dealing with multiple accounts. Implement measures to prevent data leakage and mixing between accounts. Provide clear instructions on how to handle sensitive intent and argument data. Ensure that their data sources and code paths are transparent and traceable. Avoid mixing sensitive data from different accounts in a single argument or query.

Interesting Module? Vote 👇

Voting helps other researchers find interesting modules.

Current Votes: 0

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

Canonical representation of query sensitivites. See go/sensitive-intents for more details.

Attributes

  • accountProvenance (type: list(GoogleApi.ContentWarehouse.V1.Model.QualityQrewriteAccountProvenance.t), default: nil) - Used to annotate the provenace of cross-account personal data. See go/cross-account-understanding. Sensitivity could be annotated at query, intent, and argument levels. Query and intent could have data from multiple accounts, so this field is repeated. A sensitive knowledge_context.PreviousQuery might be dropped to prevent leaking cross-account data via Genie rewrite. For arguments, the best practice is to not blend multi-account data, and this field should be treated as singular to make ownership clear. When publishing attentional entities, contextual NLU might drop an argument that contains data from a different account for data protection. Mixing multi-account data in one argument will cause data from the primary account to be dropped altogether, which is an unnecessary quality loss.
  • instruction (type: GoogleApi.ContentWarehouse.V1.Model.KnowledgeAnswersSensitivityInstruction.t, default: nil) - Instruction of handling sensitive intent/argument data. Can be specified in Intent Catalog.
  • source (type: list(String.t), default: nil) - This should be systematically added without requiring the feature developers to add a source. This is for debug purpose as to whether the Sensitivity's trace/path included any of landmark code path helpful for tracing back the sensitivity sources. One should add a new source when one sees fits. It's chronological order as to which source is added first. One should not manually add a source. The same source can be repeated if the Sensitivity object went through the same code path twice.
  • type (type: String.t, default: nil) - Sensitivity type. See the enum definition below.

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.KnowledgeAnswersSensitivitySensitivity{
    accountProvenance:
      [GoogleApi.ContentWarehouse.V1.Model.QualityQrewriteAccountProvenance.t()]
      | nil,
    instruction:
      GoogleApi.ContentWarehouse.V1.Model.KnowledgeAnswersSensitivityInstruction.t()
      | nil,
    source: [String.t()] | nil,
    type: String.t() | nil
  }

Functions

Link to this function

decode(value, options)

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

Unwrap a decoded JSON object into its complex fields.