WooCommerce Relay Data Classification Profile
Data classification annotations for the current WooCommerce Inferal Relay RDF ontology, focused on personal-data and PII-like fields without modifying generated Relay source RDF.
This profile treats WooCommerce 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 WooCommerce with predicate woocommerce:orderId and path orderId.
Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
WooCommerce Order Id confidence assessment
Structured probability-scale confidence assessment generated from the Relay data-classification rule confidence projection.
Relay schema field from WooCommerce. Upstream comment: Address line 1
WooCommerce Address1 confidence assessment
Relay schema field from WooCommerce. Upstream comment: Address line 2
WooCommerce Address2 confidence assessment
Relay schema field from WooCommerce. Upstream comment: City
Relay schema field from WooCommerce. Upstream comment: Country code (ISO 3166-1 alpha-2)
Upstream comment: Country code (ISO 3166-1 alpha-2)
WooCommerce Country confidence assessment
Relay schema field from WooCommerce. Upstream comment: Email address
Relay schema field from WooCommerce. Upstream comment: First name
WooCommerce First Name confidence assessment
Relay schema field from WooCommerce. Upstream comment: Last name
WooCommerce Last Name confidence assessment
Relay schema field from WooCommerce. Upstream comment: Phone number
Relay schema field from WooCommerce. Upstream comment: Postal/ZIP code
WooCommerce Postcode confidence assessment
Relay schema field from WooCommerce. Upstream comment: State/Province code
Upstream comment: State/Province code Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from WooCommerce. Upstream comment: List of states in this country
Upstream comment: List of states in this country Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
WooCommerce States confidence assessment
Relay schema field from WooCommerce. Upstream comment: List of email addresses that can use this coupon
WooCommerce Email Restrictions classification
Upstream comment: List of email addresses that can use this coupon
WooCommerce Email Restrictions confidence assessment
Relay schema field from WooCommerce. Upstream comment: List of user IDs (or guest email addresses) that have used the coupon
Upstream comment: List of user IDs (or guest email addresses) that have used the coupon Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
WooCommerce Used By confidence assessment
Relay schema field from WooCommerce. Upstream comment: Avatar URL
WooCommerce Avatar Url confidence assessment
Relay schema field from WooCommerce. Upstream comment: List of billing address data
Upstream comment: List of billing address data
WooCommerce Billing confidence assessment
Relay schema field from WooCommerce. Upstream comment: The email address for the customer
Upstream comment: The email address for the customer
Relay schema field from WooCommerce. Upstream comment: Customer first name
Relay schema field from WooCommerce. Upstream comment: Customer last name
Relay schema field from WooCommerce. Upstream comment: List of shipping address data
Upstream comment: List of shipping address data
WooCommerce Shipping confidence assessment
Relay schema field from WooCommerce. Upstream comment: Customer login name
Upstream comment: Customer login name Username-like field; review whether values are real usernames, handles, display aliases, or non-person account labels.
WooCommerce Username confidence assessment
Relay schema field from WooCommerce. Upstream comment: Customer password
Upstream comment: Customer password Password field; review whether values contain a password, password policy flag, or opaque credential reference.
WooCommerce Password confidence assessment
Relay schema field from WooCommerce. Upstream comment: Billing address
Relay schema field from WooCommerce. Upstream comment: Customer who owns the order. 0 for guests.
Upstream comment: Customer who owns the order. 0 for guests. Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
WooCommerce Customer confidence assessment
Relay schema field from WooCommerce. Upstream comment: Customer's IP address
WooCommerce Customer Ip Address classification
WooCommerce Customer Ip Address confidence assessment
Relay schema field from WooCommerce. Upstream comment: Note left by customer during checkout
WooCommerce Customer Note classification
Upstream comment: Note left by customer during checkout Freeform note field; review whether values contain customer communications or arbitrary personal data.
WooCommerce Customer Note confidence assessment
Relay schema field from WooCommerce. Upstream comment: User agent of the customer
WooCommerce Customer User Agent classification
Upstream comment: User agent of the customer
WooCommerce Customer User Agent confidence assessment
Relay schema field from WooCommerce. Upstream comment: Shipping address
Relay schema field from WooCommerce. Upstream comment: Customer ID
Upstream comment: Customer ID Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from WooCommerce. Upstream comment: Customer note
Upstream comment: Customer note Freeform note field; review whether values contain customer communications or arbitrary personal data.
Relay schema field from WooCommerce. Upstream comment: Whether note is for customer (visible to customer). Default is false.
Upstream comment: Whether note is for customer (visible to customer). Default is false. Freeform note field; review whether values contain customer communications or arbitrary personal data.
Relay schema field from WooCommerce. Upstream comment: Note content
Upstream comment: Note content Freeform note field; review whether values contain customer communications or arbitrary personal data.
Relay schema field from WooCommerce. Upstream comment: Whether note is for customer
Upstream comment: Whether note is for customer Freeform note field; review whether values contain customer communications or arbitrary personal data.
Relay schema field from WooCommerce. Upstream comment: Reviewer name
WooCommerce Reviewer confidence assessment
Relay schema field from WooCommerce. Upstream comment: Avatar URLs for the reviewer
WooCommerce Reviewer Avatar Urls classification
Upstream comment: Avatar URLs for the reviewer
WooCommerce Reviewer Avatar Urls confidence assessment
Relay schema field from WooCommerce. Upstream comment: Reviewer email
WooCommerce Reviewer Email classification
WooCommerce Reviewer Email confidence assessment
Relay schema field from WooCommerce. Upstream comment: Number of customers
Upstream comment: Number of customers Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
WooCommerce Customers confidence assessment
Relay schema field from WooCommerce. Upstream comment: Email address to send to. Required if order has no billing email.
Upstream comment: Email address to send to. Required if order has no billing email.
Relay schema field from WooCommerce. Upstream comment: If true, update the order's billing email with the provided email address.
WooCommerce Force Email Update classification
Upstream comment: If true, update the order's billing email with the provided email address.
WooCommerce Force Email Update confidence assessment
Relay schema field from WooCommerce. Upstream comment: Plugin author name
WooCommerce Author Name confidence assessment
Relay schema field from WooCommerce. Upstream comment: WordPress language
Upstream comment: WordPress language Locale or language field; review whether it describes a person's language preference or only a market setting.
WooCommerce Language confidence assessment
Relay schema field from WooCommerce. Upstream comment: City name. Deprecated: use cities instead
Upstream comment: City name. Deprecated: use cities instead
Relay schema field from WooCommerce. Upstream comment: Country ISO 3166 code
Relay schema field from WooCommerce. Upstream comment: Postcode/ZIP. Deprecated: use postcodes instead
Upstream comment: Postcode/ZIP. Deprecated: use postcodes instead
Relay schema field from WooCommerce. Upstream comment: Postcodes/ZIPs
WooCommerce Postcodes confidence assessment
Relay schema field from WooCommerce. Upstream comment: State code
Upstream comment: State code Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from WooCommerce. Upstream comment: Secret key used to generate a hash of the delivered webhook (HMAC-SHA256)
Upstream comment: Secret key used to generate a hash of the delivered webhook (HMAC-SHA256) Authentication-adjacent field; review whether the value authenticates, identifies, or is only operational metadata.
WooCommerce Secret confidence assessment
Relay schema field from WooCommerce. Upstream comment: Secret key used to generate a hash of the delivered webhook
Upstream comment: Secret key used to generate a hash of the delivered webhook Authentication-adjacent field; review whether the value authenticates, identifies, or is only operational metadata.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare address1.
Upstream comment: Query alias: 2 models declare address1.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare address2.
Upstream comment: Query alias: 2 models declare address2.
Relay schema field from WooCommerce. Upstream comment: Query alias: 1 model declares authorName.
Upstream comment: Query alias: 1 model declares authorName.
Relay schema field from WooCommerce. Upstream comment: Query alias: 3 models declare avatarUrl.
Upstream comment: Query alias: 3 models declare avatarUrl.
Relay schema field from WooCommerce. Upstream comment: Query alias: 4 models declare city.
Upstream comment: Query alias: 4 models declare city.
Relay schema field from WooCommerce. Upstream comment: Query alias: 4 models declare country.
Upstream comment: Query alias: 4 models declare country.
Relay schema field from WooCommerce. Upstream comment: Query alias: 5 models declare customer.
Upstream comment: Query alias: 5 models declare customer. Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from WooCommerce. Upstream comment: Query alias: 4 models declare customerIpAddress.
Upstream comment: Query alias: 4 models declare customerIpAddress.
Relay schema field from WooCommerce. Upstream comment: Query alias: 4 models declare customerUserAgent.
Upstream comment: Query alias: 4 models declare customerUserAgent.
Relay schema field from WooCommerce. Upstream comment: Query alias: 1 model declares customers.
Upstream comment: Query alias: 1 model declares customers. Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from WooCommerce. Upstream comment: Query alias: 7 models declare email.
Upstream comment: Query alias: 7 models declare email.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare emailRestrictions.
Upstream comment: Query alias: 2 models declare emailRestrictions.
Relay schema field from WooCommerce. Upstream comment: Query alias: 6 models declare firstName.
Upstream comment: Query alias: 6 models declare firstName.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare forceEmailUpdate.
Upstream comment: Query alias: 2 models declare forceEmailUpdate.
Relay schema field from WooCommerce. Upstream comment: Query alias: 1 model declares language.
Upstream comment: Query alias: 1 model declares language. Locale or language field; review whether it describes a person's language preference or only a market setting.
Relay schema field from WooCommerce. Upstream comment: Query alias: 6 models declare lastName.
Upstream comment: Query alias: 6 models declare lastName.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare note.
Upstream comment: Query alias: 2 models declare note. Freeform note field; review whether values contain customer communications or arbitrary personal data.
Relay schema field from WooCommerce. Upstream comment: Query alias: 1 model declares password.
Upstream comment: Query alias: 1 model declares password. Password field; review whether values contain a password, password policy flag, or opaque credential reference.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare phone.
Upstream comment: Query alias: 2 models declare phone.
Relay schema field from WooCommerce. Upstream comment: Query alias: 4 models declare postcode.
Upstream comment: Query alias: 4 models declare postcode.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare postcodes.
Upstream comment: Query alias: 2 models declare postcodes.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare reviewer.
Upstream comment: Query alias: 2 models declare reviewer.
Relay schema field from WooCommerce. Upstream comment: Query alias: 1 model declares reviewerAvatarUrls.
Upstream comment: Query alias: 1 model declares reviewerAvatarUrls.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare reviewerEmail.
Upstream comment: Query alias: 2 models declare reviewerEmail.
Relay schema field from WooCommerce. Upstream comment: Query alias: 3 models declare secret.
Upstream comment: Query alias: 3 models declare secret. Authentication-adjacent field; review whether the value authenticates, identifies, or is only operational metadata.
Relay schema field from WooCommerce. Upstream comment: Query alias: 4 models declare state.
Upstream comment: Query alias: 4 models declare state. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from WooCommerce. Upstream comment: Query alias: 2 models declare states.
Upstream comment: Query alias: 2 models declare states. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from WooCommerce. Upstream comment: Query alias: 1 model declares usedBy.
Upstream comment: Query alias: 1 model declares usedBy. Identifier-like field; review linkability and whether the identifier is personal, account-level, device-level, or operational only.
Relay schema field from WooCommerce. Upstream comment: Query alias: 4 models declare username.
Upstream comment: Query alias: 4 models declare username. Username-like field; review whether values are real usernames, handles, display aliases, or non-person account labels.