Data classification annotations for the current Hyros Inferal Relay RDF ontology, focused on personal-data and PII-like fields without modifying generated Relay source RDF.
This profile treats Hyros 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.
Relay schema field from Hyros. Upstream comment: Ad account id flattened from `adSource.adAccountId`.
Upstream comment: Ad account id flattened from `adSource.adAccountId`. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Hyros Ad Account Id confidence assessment
Structured probability-scale confidence assessment generated from the Relay data-classification rule confidence projection.
Relay schema field from Hyros. Upstream comment: Ad or campaign display name derived from `/api/v1.0/ads`.
Upstream comment: Ad or campaign display name derived from `/api/v1.0/ads`.
Relay schema field from Hyros. Upstream comment: Ad or campaign display name returned by `/api/v1.0/ads`.
Upstream comment: Ad or campaign display name returned by `/api/v1.0/ads`.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.AdSource/adAccountId> and path adAccountId.
Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Attribution/clickId> and path clickId.
Relay schema field from Hyros. Upstream comment: Client-supplied stable identifier from the upstream calling system (e.g. Calendly event ID). Acts as a dedup key on `POST /calls`: resubmitting the same `externalId` updates the existing call rather than creating a duplicate. Use this as the at-least-once retry handle when ingesting from a source system that issues stable IDs.
Upstream comment: Client-supplied stable identifier from the upstream calling system (e.g. Calendly event ID). Acts as a dedup key on `POST /calls`: resubmitting the same `externalId` updates the existing call rather than creating a duplicate. Use this as the at-least-once retry handle when ingesting from a source system that issues stable IDs. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Call/state> and path state.
Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.CartItem/externalId> and path externalId.
Relay schema field from Hyros. Upstream comment: Unique identifier from the external integration.
Upstream comment: Unique identifier from the external integration. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Lead/email> and path email.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Lead/firstName> and path firstName.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Lead/ips> and path ips.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Lead/lastName> and path lastName.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Lead/phoneNumbers> and path phoneNumbers.
Hyros Phone Numbers confidence assessment
Relay schema field from Hyros. Upstream comment: Order ID this cart resulted in. Only present if the cart was purchased.
Upstream comment: Order ID this cart resulted in. Only present if the cart was purchased. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros. Upstream comment: Client-supplied stable identifier from the upstream order system (typically a Stripe charge ID, payment processor reference, or e-commerce order number). Acts as a dedup key on `POST /orders`: resubmitting the same `orderId` updates the existing sale rather than creating a duplicate. Use this as the at-least-once retry handle when ingesting from a source system that issues stable IDs.
Upstream comment: Client-supplied stable identifier from the upstream order system (typically a Stripe charge ID, payment processor reference, or e-commerce order number). Acts as a dedup key on `POST /orders`: resubmitting the same `orderId` updates the existing sale rather than creating a duplicate. Use this as the at-least-once retry handle when ingesting from a source system that issues stable IDs. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.Subscription/subscriptionId> and path subscriptionId.
Hyros Subscription Id confidence assessment
Relay schema field from Hyros. Upstream comment: ID of the subscription that triggered delivery.
Upstream comment: ID of the subscription that triggered delivery. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.WebhookLead/firstName> and path firstName.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.WebhookLead/ips> and path ips.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.WebhookLead/lastName> and path lastName.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.WebhookLead/phoneNumbers> and path phoneNumbers.
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.WebhookLeadChild/email> and path email.
Relay schema field from Hyros. Upstream comment: Referrer URL from which the lead opted in.
Upstream comment: Referrer URL from which the lead opted in. URL or query-parameter field may carry identifiers, campaign parameters, or personal data in the source system.
Hyros Referrer Url confidence assessment
Relay schema field from Hyros with predicate <https://relay.inferal.com/ontology/hyros/property/Hyros.WebhookSaleEntity/orderId> and path orderId.
Relay schema field from Hyros. Upstream comment: Query alias: 2 models declare adAccountId.
Upstream comment: Query alias: 2 models declare adAccountId. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros. Upstream comment: Query alias: 1 model declares clickId.
Upstream comment: Query alias: 1 model declares clickId. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros. Upstream comment: Query alias: 2 models declare email.
Upstream comment: Query alias: 2 models declare email.
Relay schema field from Hyros. Upstream comment: Query alias: 3 models declare externalId.
Upstream comment: Query alias: 3 models declare externalId. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros. Upstream comment: Query alias: 2 models declare firstName.
Upstream comment: Query alias: 2 models declare firstName.
Relay schema field from Hyros. Upstream comment: Query alias: 2 models declare ips.
Upstream comment: Query alias: 2 models declare ips.
Relay schema field from Hyros. Upstream comment: Query alias: 2 models declare lastName.
Upstream comment: Query alias: 2 models declare lastName.
Relay schema field from Hyros. Upstream comment: Query alias: 3 models declare orderId.
Upstream comment: Query alias: 3 models declare orderId. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from Hyros. Upstream comment: Query alias: 2 models declare phoneNumbers.
Upstream comment: Query alias: 2 models declare phoneNumbers.
Relay schema field from Hyros. Upstream comment: Query alias: 1 model declares referrerUrl.
Upstream comment: Query alias: 1 model declares referrerUrl. URL or query-parameter field may carry identifiers, campaign parameters, or personal data in the source system.
Relay schema field from Hyros. 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 Hyros. Upstream comment: Query alias: 2 models declare subscriptionId.
Upstream comment: Query alias: 2 models declare subscriptionId. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.