Mailchimp Relay Data Classification Profile
Data classification annotations for the current Mailchimp Inferal Relay RDF ontology, focused on personal-data and PII-like fields without modifying generated Relay source RDF.
This profile treats Mailchimp 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 Mailchimp. Upstream comment: Total emails dispatched across all steps of the workflow.
Upstream comment: Total emails dispatched across all steps of the workflow.
Mailchimp Emails Sent confidence assessment
Structured probability-scale confidence assessment generated from the Relay data-classification rule confidence projection.
Relay schema field from Mailchimp. Upstream comment: Display name of the parent list.
Upstream comment: Display name of the parent list.
Mailchimp List Name confidence assessment
Relay schema field from Mailchimp. Upstream comment: Count of email steps configured under this workflow.
Mailchimp Workflow Emails Count classification
Upstream comment: Count of email steps configured under this workflow.
Mailchimp Workflow Emails Count confidence assessment
Relay schema field from Mailchimp. Upstream comment: Total number of emails sent
Upstream comment: Total number of emails sent
Relay schema field from Mailchimp. Upstream comment: Display name of the target audience
Upstream comment: Display name of the target audience
Relay schema field from Mailchimp. Upstream comment: Recipients of the test send. Must be a non-empty array of email addresses.
Upstream comment: Recipients of the test send. Must be a non-empty array of email addresses.
Mailchimp Test Emails confidence assessment
Relay schema field from Mailchimp. Upstream comment: Reply-to email used for variant A
Upstream comment: Reply-to email used for variant A
Mailchimp Reply Email A confidence assessment
Relay schema field from Mailchimp. Upstream comment: Reply-to email used for variant B
Upstream comment: Reply-to email used for variant B
Mailchimp Reply Email B confidence assessment
Relay schema field from Mailchimp. Upstream comment: Display name shown in the From header
Upstream comment: Display name shown in the From header
Mailchimp From Name confidence assessment
Relay schema field from Mailchimp. Upstream comment: Reply-to addresses tested in this variate campaign
Mailchimp Reply To Addresses classification
Upstream comment: Reply-to addresses tested in this variate campaign
Mailchimp Reply To Addresses confidence assessment
Relay schema field from Mailchimp. Upstream comment: Count of messages that were canceled before send.
Mailchimp Emails Canceled classification
Upstream comment: Count of messages that were canceled before send.
Mailchimp Emails Canceled confidence assessment
Relay schema field from Mailchimp. Upstream comment: Count of messages successfully handed off to the SMTP layer.
Upstream comment: Count of messages successfully handed off to the SMTP layer.
Relay schema field from Mailchimp. Upstream comment: Originating IP address. Best-effort; may be empty for proxy opens.
Upstream comment: Originating IP address. Best-effort; may be empty for proxy opens.
Relay schema field from Mailchimp. Upstream comment: Recipient email address.
Upstream comment: Recipient email address.
Mailchimp Email Address confidence assessment
Relay schema field from Mailchimp. Upstream comment: Member subscriber-hash (MD5 of the lowercased email address) — same value as `Member.id`. Used to join activity back to the Member resource.
Upstream comment: Member subscriber-hash (MD5 of the lowercased email address) — same value as `Member.id`. Used to join activity back to the Member resource.
Mailchimp Email Id confidence assessment
Relay schema field from Mailchimp. Upstream comment: Per-recipient activity envelopes for this campaign.
Upstream comment: Per-recipient activity envelopes for this campaign.
Relay schema field from Mailchimp. Upstream comment: Display name shown in subscribe forms and the admin UI.
Upstream comment: Display name shown in subscribe forms and the admin UI.
Relay schema field from Mailchimp. Upstream comment: Email Beamer inbound address for converting emails into campaigns.
Upstream comment: Email Beamer inbound address for converting emails into campaigns.
Mailchimp Beamer Address confidence assessment
Relay schema field from Mailchimp. Upstream comment: Physical mailing address printed in the campaign footer.
Upstream comment: Physical mailing address printed in the campaign footer. Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from Mailchimp. Upstream comment: Whether subscribers can choose between HTML and plain-text email.
Mailchimp Email Type Option classification
Upstream comment: Whether subscribers can choose between HTML and plain-text email.
Mailchimp Email Type Option confidence assessment
Relay schema field from Mailchimp. Upstream comment: Display name of the list.
Upstream comment: Display name of the list.
Relay schema field from Mailchimp with predicate <https://relay.inferal.com/ontology/mailchimp/property/Mailchimp.ListBatchMembersResponse.errors/emailAddress> and path emailAddress.
Relay schema field from Mailchimp. Upstream comment: Default "from" email address.
Upstream comment: Default "from" email address.
Mailchimp From Email confidence assessment
Relay schema field from Mailchimp. Upstream comment: Default language code (e.g. `en`, `es`).
Upstream comment: Default language code (e.g. `en`, `es`). Locale or language field; review whether it describes a person's language preference or only a market setting.
Mailchimp Language confidence assessment
Relay schema field from Mailchimp. Upstream comment: Street address line 1.
Upstream comment: Street address line 1.
Mailchimp Address1 confidence assessment
Relay schema field from Mailchimp. Upstream comment: Street address line 2 (suite, unit, etc.).
Upstream comment: Street address line 2 (suite, unit, etc.).
Mailchimp Address2 confidence assessment
Relay schema field from Mailchimp. Upstream comment: City.
Relay schema field from Mailchimp. Upstream comment: ISO 3166-1 alpha-2 country code.
Upstream comment: ISO 3166-1 alpha-2 country code.
Relay schema field from Mailchimp. Upstream comment: Contact phone number.
Relay schema field from Mailchimp. Upstream comment: State or province.
Upstream comment: State or province. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Mailchimp. Upstream comment: Postal code.
Relay schema field from Mailchimp. Upstream comment: Audience postal contact information shown in campaign footers (CAN-SPAM).
Upstream comment: Audience postal contact information shown in campaign footers (CAN-SPAM). Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from Mailchimp. Upstream comment: Allow subscribers to choose between HTML and plain-text emails.
Upstream comment: Allow subscribers to choose between HTML and plain-text emails.
Relay schema field from Mailchimp. Upstream comment: Deliver a callback when a subscriber changes their email address.
Upstream comment: Deliver a callback when a subscriber changes their email address.
Relay schema field from Mailchimp. Upstream comment: Deliver events triggered by the subscriber themselves.
Upstream comment: Deliver events triggered by the subscriber themselves. Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from Mailchimp. Upstream comment: Subscriber's email address.
Upstream comment: Subscriber's email address.
Relay schema field from Mailchimp. Upstream comment: Inferred email client (`Apple Mail`, `Gmail`, etc.).
Upstream comment: Inferred email client (`Apple Mail`, `Gmail`, etc.).
Mailchimp Email Client confidence assessment
Relay schema field from Mailchimp. Upstream comment: Delivery format preference (`html` or `text`).
Upstream comment: Delivery format preference (`html` or `text`).
Mailchimp Email Type confidence assessment
Relay schema field from Mailchimp. Upstream comment: Subscriber's full name as resolved from merge fields.
Upstream comment: Subscriber's full name as resolved from merge fields.
Mailchimp Full Name confidence assessment
Relay schema field from Mailchimp. Upstream comment: IP address recorded at confirmed opt-in.
Upstream comment: IP address recorded at confirmed opt-in.
Relay schema field from Mailchimp. Upstream comment: IP address recorded at signup.
Upstream comment: IP address recorded at signup.
Mailchimp Ip Signup confidence assessment
Relay schema field from Mailchimp. Upstream comment: Subscriber language code (e.g. `en`, `es`).
Upstream comment: Subscriber language code (e.g. `en`, `es`). Locale or language field; review whether it describes a person's language preference or only a market setting.
Relay schema field from Mailchimp. Upstream comment: SMS phone number on file. US numbers only.
Mailchimp Sms Phone Number classification
Upstream comment: SMS phone number on file. US numbers only.
Mailchimp Sms Phone Number confidence assessment
Relay schema field from Mailchimp. Upstream comment: Cross-Mailchimp email-address identifier (different from `id`).
Mailchimp Unique Email Id classification
Upstream comment: Cross-Mailchimp email-address identifier (different from `id`).
Mailchimp Unique Email Id confidence assessment
Relay schema field from Mailchimp. Upstream comment: Member email address. The MD5 of the lowercased email becomes the `subscriber_hash` used as `Member.id` and as the path parameter for per-member endpoints.
Upstream comment: Member email address. The MD5 of the lowercased email becomes the `subscriber_hash` used as `Member.id` and as the path parameter for per-member endpoints.
Relay schema field from Mailchimp. Upstream comment: Preferred email format.
Upstream comment: Preferred email format.
Relay schema field from Mailchimp. Upstream comment: Subscriber language code (ISO 639-1).
Upstream comment: Subscriber language code (ISO 639-1). Locale or language field; review whether it describes a person's language preference or only a market setting.
Relay schema field from Mailchimp. Upstream comment: Display name of the account user who authored the note.
Upstream comment: Display name of the account user who authored the note.
Mailchimp Created By confidence assessment
Relay schema field from Mailchimp. Upstream comment: Free-text note body.
Upstream comment: Free-text note body. Freeform note field; review whether values contain customer communications or arbitrary personal data.
Upstream comment: ISO 3166-1 alpha-2 country code. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Mailchimp Country Code confidence assessment
Relay schema field from Mailchimp. Upstream comment: Approximate latitude.
Mailchimp Latitude confidence assessment
Relay schema field from Mailchimp. Upstream comment: Approximate longitude.
Upstream comment: Approximate longitude.
Mailchimp Longitude confidence assessment
Relay schema field from Mailchimp. Upstream comment: ISO 3166-2 subdivision code.
Upstream comment: ISO 3166-2 subdivision code. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Mailchimp. Upstream comment: New email address. Updates the subscriber identity.
Upstream comment: New email address. Updates the subscriber identity.
Relay schema field from Mailchimp with predicate <https://relay.inferal.com/ontology/mailchimp/property/Mailchimp.MemberPatchInput/emailType> and path emailType.
Relay schema field from Mailchimp with predicate <https://relay.inferal.com/ontology/mailchimp/property/Mailchimp.MemberPatchInput/language> and path language.
Locale or language field; review whether it describes a person's language preference or only a market setting.
Relay schema field from Mailchimp. Upstream comment: Member email address. Required only when upserting a new member.
Upstream comment: Member email address. Required only when upserting a new member.
Relay schema field from Mailchimp. Upstream comment: Display name shown in the Mailchimp admin UI and on forms.
Upstream comment: Display name shown in the Mailchimp admin UI and on forms.
Relay schema field from Mailchimp. Upstream comment: Numeric Mailchimp country code applied as the default for `address` merge fields.
Mailchimp Default Country classification
Upstream comment: Numeric Mailchimp country code applied as the default for `address` merge fields.
Mailchimp Default Country confidence assessment
Relay schema field from Mailchimp. Upstream comment: Phone-number format applied to `phone` merge fields.
Upstream comment: Phone-number format applied to `phone` merge fields.
Mailchimp Phone Format confidence assessment
Relay schema field from Mailchimp. Upstream comment: Password protecting the share URL
Upstream comment: Password protecting the share URL Password field; review whether values contain a password, password policy flag, or opaque credential reference.
Mailchimp Share Password confidence assessment
Relay schema field from Mailchimp. Upstream comment: Number of emails sent during this bucket
Upstream comment: Number of emails sent during this bucket
Relay schema field from Mailchimp. Upstream comment: Display name of the segment.
Upstream comment: Display name of the segment.
Relay schema field from Mailchimp with predicate <https://relay.inferal.com/ontology/mailchimp/property/Mailchimp.SegmentBatchMembersResponse.errors/emailAddresses> and path emailAddresses.
Mailchimp Email Addresses classification
Mailchimp Email Addresses confidence assessment
Relay schema field from Mailchimp. Upstream comment: Display name of the tag.
Upstream comment: Display name of the tag.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares address1.
Upstream comment: Query alias: 1 model declares address1.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares address2.
Upstream comment: Query alias: 1 model declares address2.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares beamerAddress.
Upstream comment: Query alias: 1 model declares beamerAddress.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares city.
Upstream comment: Query alias: 1 model declares city.
Relay schema field from Mailchimp. Upstream comment: Query alias: 2 models declare contact.
Upstream comment: Query alias: 2 models declare contact. Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares country.
Upstream comment: Query alias: 1 model declares country.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares countryCode.
Upstream comment: Query alias: 1 model declares countryCode. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares defaultCountry.
Upstream comment: Query alias: 1 model declares defaultCountry.
Relay schema field from Mailchimp. Upstream comment: Query alias: 6 models declare emailAddress.
Upstream comment: Query alias: 6 models declare emailAddress.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares emailAddresses.
Upstream comment: Query alias: 1 model declares emailAddresses.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares emailClient.
Upstream comment: Query alias: 1 model declares emailClient.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares emailId.
Upstream comment: Query alias: 1 model declares emailId.
Relay schema field from Mailchimp. Upstream comment: Query alias: 4 models declare emailType.
Upstream comment: Query alias: 4 models declare emailType.
Relay schema field from Mailchimp. Upstream comment: Query alias: 2 models declare emailTypeOption.
Upstream comment: Query alias: 2 models declare emailTypeOption.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares emails.
Upstream comment: Query alias: 1 model declares emails.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares emailsCanceled.
Upstream comment: Query alias: 1 model declares emailsCanceled.
Relay schema field from Mailchimp. Upstream comment: Query alias: 5 models declare emailsSent.
Upstream comment: Query alias: 5 models declare emailsSent.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares fromEmail.
Upstream comment: Query alias: 1 model declares fromEmail.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares fullName.
Upstream comment: Query alias: 1 model declares fullName.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares ip.
Upstream comment: Query alias: 1 model declares ip.
Relay schema field from Mailchimp. Upstream comment: Query alias: 5 models declare language.
Upstream comment: Query alias: 5 models declare language. Locale or language field; review whether it describes a person's language preference or only a market setting.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares latitude.
Upstream comment: Query alias: 1 model declares latitude.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares longitude.
Upstream comment: Query alias: 1 model declares longitude.
Relay schema field from Mailchimp. 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 Mailchimp. Upstream comment: Query alias: 1 model declares phone.
Upstream comment: Query alias: 1 model declares phone.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares phoneFormat.
Upstream comment: Query alias: 1 model declares phoneFormat.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares region.
Upstream comment: Query alias: 1 model declares region. Location code or region field; review whether it identifies a person, billing/shipping address, or only a market/geography.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares replyEmailA.
Upstream comment: Query alias: 1 model declares replyEmailA.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares replyEmailB.
Upstream comment: Query alias: 1 model declares replyEmailB.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares replyToAddresses.
Upstream comment: Query alias: 1 model declares replyToAddresses.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares sharePassword.
Upstream comment: Query alias: 1 model declares sharePassword. Password field; review whether values contain a password, password policy flag, or opaque credential reference.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares smsPhoneNumber.
Upstream comment: Query alias: 1 model declares smsPhoneNumber.
Relay schema field from Mailchimp. 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 Mailchimp. Upstream comment: Query alias: 1 model declares testEmails.
Upstream comment: Query alias: 1 model declares testEmails.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares uniqueEmailId.
Upstream comment: Query alias: 1 model declares uniqueEmailId.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares upemail.
Upstream comment: Query alias: 1 model declares upemail.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares user.
Upstream comment: Query alias: 1 model declares user. Broad contact, customer, user, owner, or actor object field; review nested payloads before asserting specific personal-data categories.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares workflowEmailsCount.
Upstream comment: Query alias: 1 model declares workflowEmailsCount.
Relay schema field from Mailchimp. Upstream comment: Query alias: 1 model declares zip.
Upstream comment: Query alias: 1 model declares zip.