Travel Partner Relay Data Classification Profile
Data classification annotations for the current Travel Partner Inferal Relay RDF ontology, focused on personal-data and PII-like fields without modifying generated Relay source RDF.
This profile treats Travel Partner Relay API schema fields as data elements and annotates predicate-level terms with candidate DPV-PD categories, confidence values, sensitivity, review flags, and detection provenance. Candidate annotations identify fields requiring human or source-system review before asserting personal-data semantics.
Classification context for predicate-level fields in the current merged Inferal Relay RDF ontologies. These annotations describe schema terms, not observed payload values.
Deterministic field-name and upstream-comment rules used to draft the Relay data-classification profile.
The rule set reads RDF property IRIs, labels, and comments from generated Relay RDF. It excludes obvious constants, aggregate metrics, monetary amounts, product, business, vendor, configuration, audience-breakdown, and product-catalog demographic fields. It proposes candidate personal-data categories for explicit person-name, email, telephone, IP address, user-agent, birth, gender, address, postal-code, city, country, GPS-coordinate, payment-card, official-identifier, nationality, age, enhanced-match, URL, device, credential-adjacent, profile-media, identifier-like, contact-object, locale, freeform-note, document, and tax-registration fields. Confidence and sensitivity values are heuristic defaults for governance triage, not legal determinations, manual-review evidence, or assertions that observed payload values contain personal data.
Suppresses constant-style schema terms because Relay constants usually name enum values or generated symbols rather than data-bearing personal fields.
Suppresses container or configuration fields for automatic enhanced matching; individual enhanced-match fields are handled separately when the provider exposes them.
Non-personal enabled flag exclusion rule
enabled$ unless the field also mentions email, phone, gender, birth, or name
Suppresses generic enabled/configuration flags that do not carry personal-data values.
Suppresses aggregate metrics because they normally describe counts, totals, or rates rather than addressable personal-data values.
(amount|price|cost|currency|tax|revenue|sales|spend|budget|refund) unless the same field also mentions id, email, phone, address, zip, postal, country, city, or state
Suppresses ordinary monetary metrics while preserving fields whose names also contain personal-data cues.
Business and product name exclusion rule
Suppresses organization, product, brand, method, topic, and integration names that are not treated as personal-data fields by this profile.
Marks username fields as candidates requiring review of whether the value is a real username, handle, display alias, or non-person account label.
first name|last name|middle name|display name|reviewer name|author name|sender name|receiver name|customer name|shop owner name|account owner|account name|cardholder name
Marks explicit person-name fields and source descriptions that state a person-name meaning.
Marks fields whose local name contains email, except status/configuration fields handled by the candidate email-derived flag rule.
Marks email-derived status or configuration fields for review because they may contain only booleans or policy state rather than email addresses.
Marks fields whose local name directly names phone or telephone values.
Marks country calling code as telephone-number-related but with lower confidence because it may be a general country dial prefix.
ipAddress|clientIp|customerIp|^ip$|^ips$|ip address
Marks fields and comments that explicitly name IP addresses.
userAgent|clientUserAgent|customerUserAgent|user agent
Marks fields and comments that explicitly name user-agent values.
Marks fields whose local name directly denotes a birth date.
Marks fields whose local name directly denotes a birth place.
Marks fields whose name or source description explicitly denotes gender.
Marks payment-card-number fields as candidates requiring review of whether the schema value carries a full payment card number, token, or masked value.
Marks payment-card object fields as candidates requiring review of whether nested payloads carry card numbers, expiry data, tokens, or masked card references.
Marks bank-account fields as candidates requiring review of whether the value carries account details, tokens, or operational references.
Marks account-number fields as financial-account-number candidates requiring review of whether the number identifies a personal financial account.
Marks travel-document and official-identifier fields as candidates requiring source-system review.
Marks nationality fields as candidates requiring review of whether the value describes a person or only a market/document attribute.
^age$|child age|traveler age|passenger age
Marks explicit age fields as candidates requiring review of whether the value describes a person or an aggregate bucket.
address|addr1|addr2|street|physical address|billing address|shipping address|street address
Marks address-bearing fields while excluding logistics, shipping, billing-cycle, and address identifier fields that are likely operational metadata.
Marks street-address components and address-line fields.
Marks fields whose local name denotes a postal or ZIP code.
cityCode|locationCode, and a qualified automation state such as <qualifier>State
Marks city fields while excluding code-like location identifiers.
Marks country fields while excluding currency, dial-prefix, and code-like country fields.
Marks location codes and region fields as candidates because they may represent personal address data, market geography, or operational routing.
Marks URL and query-parameter fields as candidates because payloads may carry identifiers, campaign parameters, or personal data depending on source policy.
Marks device, cookie, app, and carrier fields as candidates for device-based personal data.
Marks password fields as candidates requiring review of whether the value contains a password, password policy flag, or opaque credential reference.
Marks authentication-adjacent fields as candidates requiring review of whether the value authenticates, identifies, or is only operational metadata.
Marks unstructured transport and credential-adjacent fields as candidates because they may contain personal identifiers, authentication data, or no personal data depending on payload policy.
Marks profile-media URL fields as candidates because they may point to profile or image data about a person.
Marks account- or user-like identifier fields as candidates requiring linkability review.
<artifact>Id where the artifact is a form, template, spec, preset, placement, rule, catalog, or feed
Marks identifier-like fields as candidates requiring review of whether the identifier is personal, account-level, device-level, or operational only.
Marks broad contact, customer, user, owner, and actor object fields as candidates because nested payloads may carry contact or account data.
Marks locale and language fields as candidates because they may describe a person's language preference or only a market setting.
Marks freeform note fields as candidates because they may contain customer communications or arbitrary personal data.
Marks payment-details fields as candidates requiring review of whether nested values contain card, token, billing, or transaction identifiers.
Marks document container fields as candidates because nested travel or identity documents may carry official identifiers.
Marks VAT and tax-registration fields as candidates because they can identify a person or business tax registration depending on source context.
Generator script that produced this candidate-only Relay data-classification profile from Relay RDF schema terms.
Rule-based detection activity over Relay predicate names, labels, and comments. It produces candidate classifications only and is not evidence of manual review or observed personal data.
Travel Partner Google Ads Customer Name field
Relay schema field from Travel Partner. Upstream comment: Required for CREATE requests. The value representing the Google Ads customer ID in the format `customers/{google_ads_customer_id}`. For example: `customers/0123456789`. Note that the `googleAdsCustomerName` field is not returned in responses to GET requests.
Travel Partner Google Ads Customer Name classification
Upstream comment: Required for CREATE requests. The value representing the Google Ads customer ID in the format `customers/{google_ads_customer_id}`. For example: `customers/0123456789`. Note that the `googleAdsCustomerName` field is not returned in responses to GET requests.
Travel Partner Google Ads Customer Name confidence assessment
Structured probability-scale confidence assessment generated from the Relay data-classification rule confidence projection.
Travel Partner Active Display Names field
Relay schema field from Travel Partner. Upstream comment: Output only. The brand's active display names in all provided languages, only present if the display name is approved for all provided languages.
Travel Partner Active Display Names classification
Upstream comment: Output only. The brand's active display names in all provided languages, only present if the display name is approved for all provided languages.
Travel Partner Active Display Names confidence assessment
Travel Partner Display Name Disapproval Reason field
Relay schema field from Travel Partner. Upstream comment: Output only. Display name's disapproval reason. Only applies to display names with the review state 'REJECTED'.
Travel Partner Display Name Disapproval Reason classification
Upstream comment: Output only. Display name's disapproval reason. Only applies to display names with the review state 'REJECTED'.
Travel Partner Display Name Disapproval Reason confidence assessment
Relay schema field from Travel Partner. Upstream comment: Output only. The brand's display names review state, which applies to all display name language entries. If there are both submitted and active display names, this refers to the submitted display names.
Travel Partner Display Name State classification
Upstream comment: Output only. The brand's display names review state, which applies to all display name language entries. If there are both submitted and active display names, this refers to the submitted display names.
Travel Partner Display Name State confidence assessment
Relay schema field from Travel Partner. Upstream comment: Input only. The name Google displays for the brand's properties. Setting the display names is only necessary if you want to override the landing page display name or account-level display name for the brand. Google reviews the display names for appropriate content. When there are multiple languages, Google will only show the display names once Google approves all the languages.
Travel Partner Display Names classification
Upstream comment: Input only. The name Google displays for the brand's properties. Setting the display names is only necessary if you want to override the landing page display name or account-level display name for the brand. Google reviews the display names for appropriate content. When there are multiple languages, Google will only show the display names once Google approves all the languages.
Travel Partner Display Names confidence assessment
Relay schema field from Travel Partner. Upstream comment: Output only. The brand's icon's review state. If there are both submitted and active icons, this refers to the submitted icon.
Travel Partner Icon State classification
Upstream comment: Output only. The brand's icon's review state. If there are both submitted and active icons, this refers to the submitted icon. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner Icon State confidence assessment
Travel Partner Submitted Display Names field
Relay schema field from Travel Partner. Upstream comment: Output only. The brand's submitted display names in all provided languages, only present if the display name is new or rejected for any language.
Travel Partner Submitted Display Names classification
Upstream comment: Output only. The brand's submitted display names in all provided languages, only present if the display name is new or rejected for any language.
Travel Partner Submitted Display Names confidence assessment
Relay schema field from Travel Partner. Upstream comment: Language of the disapproved display name.
Travel Partner Language Code classification
Upstream comment: Language of the disapproved display name. Locale or language field; review whether it describes a person's language preference or only a market setting.
Travel Partner Language Code confidence assessment
Travel Partner Partner Hotel Display Name field
Relay schema field from Travel Partner. Upstream comment: Partner's hotel name. Only present if `partnerHotelDisplayName` is specified in `aggregateBy` in the request.
Travel Partner Partner Hotel Display Name classification
Upstream comment: Partner's hotel name. Only present if `partnerHotelDisplayName` is specified in `aggregateBy` in the request.
Travel Partner Partner Hotel Display Name confidence assessment
Relay schema field from Travel Partner. Upstream comment: ISO 3116 region code of the country/region of the user. Only present if `userRegionCode` is specified in `aggregateBy` in the request
Travel Partner User Region Code classification
Upstream comment: ISO 3116 region code of the country/region of the user. Only present if `userRegionCode` is specified in `aggregateBy` in the request Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner User Region Code confidence assessment
Travel Partner Google Hotel Display Name field
Relay schema field from Travel Partner. Upstream comment: Google's hotel name.
Travel Partner Google Hotel Display Name classification
Travel Partner Google Hotel Display Name confidence assessment
Relay schema field from Travel Partner. Upstream comment: Partner's hotel name.
Relay schema field from Travel Partner. Upstream comment: Optional. Value for tracking the icon. It could be the primary key to your icon in your system, or the icon's filename. Google does not use this value.
Upstream comment: Optional. Value for tracking the icon. It could be the primary key to your icon in your system, or the icon's filename. Google does not use this value. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Travel Partner Reference confidence assessment
Relay schema field from Travel Partner. Upstream comment: Output only. The icon's current state.
Upstream comment: Output only. The icon's current state. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner State confidence assessment
Relay schema field from Travel Partner. Upstream comment: CLDR region code of the country/region of the hotel. If `hotelRegionCode` is not a value of the `aggregateBy` parameter in the request call, then the `hotelRegionCode` field is not returned in the `Key`.
Travel Partner Hotel Region Code classification
Upstream comment: CLDR region code of the country/region of the hotel. If `hotelRegionCode` is not a value of the `aggregateBy` parameter in the request call, then the `hotelRegionCode` field is not returned in the `Key`. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner Hotel Region Code confidence assessment
Relay schema field from Travel Partner. Upstream comment: ISO 3116 region code of the country/region of the user. If `userRegionCode` is not a value of the `aggregateBy` parameter in the request call, then the `userRegionCode` field is not returned in the `Key`.
Upstream comment: ISO 3116 region code of the country/region of the user. If `userRegionCode` is not a value of the `aggregateBy` parameter in the request call, then the `userRegionCode` field is not returned in the `Key`. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Travel Partner. Upstream comment: The latitude in degrees. It must be in the range [-90.0, +90.0].
Upstream comment: The latitude in degrees. It must be in the range [-90.0, +90.0].
Travel Partner Latitude confidence assessment
Relay schema field from Travel Partner. Upstream comment: The longitude in degrees. It must be in the range [-180.0, +180.0].
Upstream comment: The longitude in degrees. It must be in the range [-180.0, +180.0].
Travel Partner Longitude confidence assessment
Relay schema field from Travel Partner. Upstream comment: Token that can be sent as `page_token` to retrieve the next page. If this field is omitted, there are no subsequent pages.
Travel Partner Next Page Token classification
Upstream comment: Token that can be sent as `page_token` to retrieve the next page. If this field is omitted, there are no subsequent pages. Authentication-adjacent field; review whether the value authenticates, identifies, or is only operational metadata.
Travel Partner Next Page Token confidence assessment
Relay schema field from Travel Partner. Upstream comment: Pagination token used to retrieve the next page of results.
Upstream comment: Pagination token used to retrieve the next page of results. Authentication-adjacent field; review whether the value authenticates, identifies, or is only operational metadata.
Relay schema field from Travel Partner. Upstream comment: The text's BCP-47 language code, such as "en-US" or "sr-Latn". For more information, see http://www.unicode.org/reports/tr35/#Unicode_locale_identifier.
Upstream comment: The text's BCP-47 language code, such as "en-US" or "sr-Latn". For more information, see http://www.unicode.org/reports/tr35/#Unicode_locale_identifier. Locale or language field; review whether it describes a person's language preference or only a market setting.
Travel Partner No Landing Page Count field
Relay schema field from Travel Partner. Upstream comment: No landing page matched the user.
Travel Partner No Landing Page Count classification
Upstream comment: No landing page matched the user. URL or query-parameter field may carry identifiers, campaign parameters, or personal data in the source system.
Travel Partner No Landing Page Count confidence assessment
Relay schema field from Travel Partner. Upstream comment: The country code where the listing is located.
Travel Partner Region Code classification
Upstream comment: The country code where the listing is located. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner Region Code confidence assessment
Relay schema field from Travel Partner. Upstream comment: Partner's hotel display name. This field is only populated when the result is aggregated by `partnerHotelId`.
Upstream comment: Partner's hotel display name. This field is only populated when the result is aggregated by `partnerHotelId`.
Relay schema field from Travel Partner. Upstream comment: The country of the hotel (based on address).
Travel Partner Hotel Country Code classification
Upstream comment: The country of the hotel (based on address). Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner Hotel Country Code confidence assessment
Relay schema field from Travel Partner. Upstream comment: The user's region.
Upstream comment: The user's region. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner Partner Property Display Name field
Relay schema field from Travel Partner. Upstream comment: Partner's property name. Only present if `partnerPropertyDisplayName` is specified in `aggregateBy` in the request.
Travel Partner Partner Property Display Name classification
Upstream comment: Partner's property name. Only present if `partnerPropertyDisplayName` is specified in `aggregateBy` in the request.
Travel Partner Partner Property Display Name confidence assessment
Travel Partner Property Region Code field
Relay schema field from Travel Partner. Upstream comment: ISO 3116 region code of the country/region of the property. Only present if `propertyRegionCode` is specified in `aggregateBy` in the request
Travel Partner Property Region Code classification
Upstream comment: ISO 3116 region code of the country/region of the property. Only present if `propertyRegionCode` is specified in `aggregateBy` in the request Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Travel Partner Property Region Code confidence assessment
Relay schema field from Travel Partner. Upstream comment: Pagination token used to retrieve the next page of results. If this field is omitted, there are no subsequent pages.
Upstream comment: Pagination token used to retrieve the next page of results. If this field is omitted, there are no subsequent pages. Authentication-adjacent field; review whether the value authenticates, identifies, or is only operational metadata.
Relay schema field from Travel Partner. Upstream comment: Language of the review in ISO639 format, such as "en", "de", etc.
Upstream comment: Language of the review in ISO639 format, such as "en", "de", etc. Locale or language field; review whether it describes a person's language preference or only a market setting.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares displayNameDisapprovalReason.
Upstream comment: Query alias: 1 model declares displayNameDisapprovalReason.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares displayNameState.
Upstream comment: Query alias: 1 model declares displayNameState.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares googleAdsCustomerName.
Upstream comment: Query alias: 1 model declares googleAdsCustomerName.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares googleHotelDisplayName.
Upstream comment: Query alias: 1 model declares googleHotelDisplayName.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares hotelCountryCode.
Upstream comment: Query alias: 1 model declares hotelCountryCode. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares hotelRegionCode.
Upstream comment: Query alias: 1 model declares hotelRegionCode. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares iconState.
Upstream comment: Query alias: 1 model declares iconState. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Travel Partner. Upstream comment: Query alias: 3 models declare languageCode.
Upstream comment: Query alias: 3 models declare languageCode. Locale or language field; review whether it describes a person's language preference or only a market setting.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares latitude.
Upstream comment: Query alias: 1 model declares latitude.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares longitude.
Upstream comment: Query alias: 1 model declares longitude.
Relay schema field from Travel Partner. Upstream comment: Query alias: 5 models declare nextPageToken.
Upstream comment: Query alias: 5 models declare nextPageToken. Authentication-adjacent field; review whether the value authenticates, identifies, or is only operational metadata.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares noLandingPageCount.
Upstream comment: Query alias: 1 model declares noLandingPageCount. URL or query-parameter field may carry identifiers, campaign parameters, or personal data in the source system.
Relay schema field from Travel Partner. Upstream comment: Query alias: 3 models declare partnerHotelDisplayName.
Upstream comment: Query alias: 3 models declare partnerHotelDisplayName.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares partnerPropertyDisplayName.
Upstream comment: Query alias: 1 model declares partnerPropertyDisplayName.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares propertyRegionCode.
Upstream comment: Query alias: 1 model declares propertyRegionCode. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares reference.
Upstream comment: Query alias: 1 model declares reference. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares regionCode.
Upstream comment: Query alias: 1 model declares regionCode. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Travel Partner. Upstream comment: Query alias: 1 model declares state.
Upstream comment: Query alias: 1 model declares state. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Travel Partner. Upstream comment: Query alias: 4 models declare userRegionCode.
Upstream comment: Query alias: 4 models declare userRegionCode. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.