This field explicitly contains an email address associated with the account, which matches the "email" taxonomy tag. Even though the description mentions it's treated as metadata and not used for authentication, it still directly contains an email address.

The field contains an email address associated with the account, matching the 'email' taxonomy tag.

The field directly stores an email address associated with the account, matching the 'email' taxonomy tag.

The 'email' field explicitly stores an email address associated with the account, meeting the taxonomy's criteria for direct inclusion of email addresses.

The field 'email' directly represents an email address, which matches the 'email' tag in the taxonomy.

The 'reference' field is related to PromptPay, a system that can be associated with phone numbers. However, it's described as a 'Bill reference,' not directly as a phone number. There's a possibility it could contain or be related to a phone number, but it's not a direct match based on the description alone.

This field stores the customer's name, which directly matches the "person-name" category in the taxonomy.

The field 'customer_name' represents a person's name.

The field contains the customer's full name.

The field holds the customer's name, which could be a person's name, though it might also represent a business name.

The field `customer_name` contains the customer's name, which falls under the 'person-name' taxonomy tag.

This field contains the "Owner's verified full name" which directly matches the person-name tag in the taxonomy that covers "The name (first, last, or both) of a person."

Contains the full name of the person.

Explicitly stated to hold the "owner's verified full name," which directly matches the taxonomy definition of a person's name.

The verified_name field explicitly stores a full name, directly aligning with the person-name taxonomy tag for personal identifiers.

The field 'verified_name' contains the owner's verified full name, which directly corresponds to a person's name.

This field could contain a person's name if the account belongs to an individual or sole proprietor. For Bacs Direct Debit payments, the display name would likely include the account holder's name, which would be displayed on mandates and statement descriptors.

The display_name is likely to contain a name associated with the account or payment method, fitting the description of person-name.

The 'display_name' is used as the name appearing on Bacs Direct Debit mandates and statements, which typically corresponds to the account holder's legal name. While this could represent a person's name, the schema does not explicitly confirm if it refers to personal or business use.

The field `display_name` can potentially include a person's name, as it refers to the name appearing on Bacs Direct Debit mandates and as a statement descriptor, which often includes an individual's name.

While this field is described as "customer-facing business name," many small businesses include the owner's name in their business name (e.g., "John Smith Plumbing"). It could potentially contain personal name information, though it's primarily intended for business names.

Although this field is more related to a business name, it could potentially be related to a person's name in certain contexts (like a sole proprietorship). However, based on the provided description, it's less likely to be directly tagged as person-name without more context indicating it's a personal name. Thus, a more cautious approach is not to tag it as person-name.

The field 'name' can represent a business name which may not be directly classified as sensitive personal data under 'person-name'. However, based on common data storage practices, it often contains the name associated with a business, which might not involve sensitive personal data. In this context, it does not map directly to 'person-name'.

The field 'name' directly contains the customer-facing business name, which can be considered as the name of a person or entity, and thus matches the 'person-name' tag.

The field could potentially contain a business or personal name as it is used on credit card statements.

The Kana variation of the statement descriptor could potentially contain a business or personal name.

The Kanji variation of the statement descriptor could potentially contain a business or personal name.

The "display_name" field likely contains the name of a person associated with the account, especially since it's described as being used "to differentiate between accounts" on the Stripe Dashboard. While it could potentially contain a business name, it's very common for individual users to use their personal names as display names.

The display name could potentially contain a person's name, although it's not explicitly stated. It's used to differentiate between accounts on the Stripe Dashboard.

The term "display_name" suggests this field is used to store a name, likely either a personal or business name, which aligns with the taxonomy tag "person-name."

The display name for an account could potentially contain a person's name, as it is used to differentiate between accounts on the Stripe Dashboard.

The taxonomy requires person-name to be the name of a person. The "name" field refers to an application's name, not a person's name. This is incorrect tagging and does not qualify. The correct answer is no matches. Wait, this indicates an error in tagging which should not happen.

The field 'name' explicitly refers to the name of the application, which could potentially include personal names if the application is named after an individual. Therefore, it fits the taxonomy tag for 'person-name'.

The 'name' field is described as 'The name of the application', but given that 'name' could also imply a person's name in a different context and based on the taxonomy description of person-name, it seems like it could fit. However, the description provided here specifies 'of the application', which suggests it might not directly refer to a person's name. Yet, as 'name' is a common field for person names and the description does not explicitly rule out the possibility of it being used for a person's name, caution dictates it could be. But based on the description provided it's less clear.

The field 'name' is classified as 'person-name' assuming it directly refers to a person's name, although the description suggests it's a name for the secret.

The property "name" is described as "A name for the secret that's unique within the scope." While it is not directly a person's name, it is named "name" and could imply identifying information. However, based on the context, it seems more like a label rather than representing a person's actual name; hence it should not be tagged with "person-name".

The name field could potentially hold a person's name, although it's not definitive.

The "name" field is described as "Name of the coupon displayed to customers on for instance invoices or receipts." While this specific field is intended for a coupon name rather than a person's name, the field name and type (string) could potentially be misused to store a person's name, especially if the coupon is named after a person.

The 'reference' field is user-supplied and could potentially contain a person's name or other identifying information.

This field contains apartment/suite/unit/building information, which is part of a street address according to the taxonomy.

The field is a continuation of the street address, making it part of the full address.

Part of the street address (e.g., apartment/suite), which is included in the taxonomy.

`address_line2` offers additional detail to a street address, such as an apartment or suite number, thereby meeting the taxonomy for street-address.

The field 'address_line2' provides additional information about a street address.

The field represents a verification check against the first line of an address, which corresponds to a street address.

This field stores town/cho-me information, which is a component of a Japanese address that represents a subdivision of a city or ward. This is part of what would constitute a street address in the Japanese addressing system.

The field 'town' is part of a detailed address, similar to 'line1' and 'line2', and can be considered under 'street-address'.

The field 'town' represents a town/cho-me, which can be considered part of a street address.

While airport codes represent specific airports, they indirectly identify cities, allowing someone to determine a person's travel destination city. Airport codes are directly tied to geographic locations, typically cities.

Similar to arrival_airport_code, departure airport codes indirectly identify cities, allowing someone to determine a person's departure city. Airport codes are directly tied to geographic locations.

The field directly represents a state, which is part of a full address.

"address_state" specifies the state/region (e.g., "California"), which aligns with the taxonomy's "state" category for direct state representations.

Explicitly represents a state/region, matching the 'state' taxonomy tag.

The field `address_state` corresponds to the state component of an address, matching the taxonomy tag for state.

The field 'address_state' represents a state or province.

The field is related to whether a postal code was provided and verified, making it directly related to checking a postal code.

The creditor_id field contains a SEPA creditor identifier, which is a unique identifier that can be used to authenticate and verify the company making the payment, and thus can be considered as authentication credential.

The 'url' represents a short-lived access token that allows customers to authenticate and access the customer portal, fulfilling the criteria of an authentication credential.

The field "setup_future_usage" indicates intended use of future payments with a saved payment method. It relates to the authentication process for future transactions, involving attaching methods to a Customer after transactions through processes that may include detailed authentication. This fits the "authn-credential" category as it pertains to authentication, though the field itself might not contain credentials directly.

This field controls payment method attachment and future usage configuration but does not directly store authentication credentials like passwords, tokens, or payment method details. It is a behavioral/operational parameter rather than a credential store.

The field `setup_future_usage` involves future payment methods and could relate to authentication processes and the storage of payment methods, potentially involving authentication credentials as part of the payment flow.

The `setup_future_usage` field indicates future intention for payment method usage and is involved in potential attachment to a customer, which aligns with authentication credentials due to its role in confirming and utilizing payment validations and compliance checks. This setup projection may indirectly involve sensitive purchase or financial flow information, particularly in how it might facilitate authentication within payment processes.

The id field could potentially be used as a unique identifier for the object, which could be considered as an authentication credential.

The id field could potentially be used as a unique identifier for the object, which could be considered sensitive authentication information.

The id field could potentially be used as a unique identifier for authentication purposes, although it's not a direct authentication credential, it's a unique identifier that could be used in authentication processes.

The id field could potentially be used as a unique identifier for the object, which could be considered sensitive information.

The id field could potentially be used as a unique identifier for authentication purposes.

The id field could potentially be used as a unique identifier for a user or object, which could be considered sensitive authentication information.

The id field could potentially be used as a unique identifier for authentication purposes.

The id field could potentially be used as a unique identifier for the object, which could be considered sensitive information.

The id field could potentially be used as a unique identifier for authentication purposes.

The connected_account field contains an ID that would be used to authenticate or identify a specific account in the system. It serves as a credential for accessing account-specific information.

The field 'connected_account' represents an ID related to account management, which can be considered sensitive as it could be utilized in authentication and identification processes.

No, the document field does not contain authentication credentials; it contains an ID of a file holding an image of an identity document

The field is part of a schema explicitly named "gelato_data_document_report_date_of_birth" which clearly indicates these fields are components of a date of birth. Though "day" alone wouldn't normally be classified as date of birth, the schema name provides the necessary context.

The field 'day' is considered part of a date of birth given the schema name and field context.

The field 'day' is part of a date, and given that it represents a numerical day between 1 and 31, it could be considered part of a date of birth when combined with month and year.

Like the "day" field, this field is part of a schema explicitly named "gelato_data_document_report_date_of_birth" which clearly indicates these fields are components of a date of birth. The schema name provides definitive context.

The field 'month' is considered part of a date of birth given the schema name and field context.

The field 'month' represents a numerical month between 1 and 12. Like 'day', it could be part of a date of birth when combined with day and year.

This field is part of a schema explicitly named "gelato_data_document_report_date_of_birth" which clearly indicates these fields are components of a date of birth. The schema name provides definitive context that this refers to a birth year.

The field 'year' is considered part of a date of birth given the schema name and field context.

The field 'year' represents a four-digit year. It could also be part of a date of birth when combined with day and month.

This field represents the day component of a birth date, as indicated by the property description "The day of birth, between 1 and 31." The schema name "legal_entity_dob" (DOB = date of birth) also provides context that this is specifically a birth date component.

The field 'day' is described as 'day of birth', which directly relates to the date of birth.

The field description explicitly states this represents "day of birth", directly linking it to date-of-birth components as defined in the taxonomy.

The field explicitly represents the day component of a date of birth. The presence of "birth" in the schema name further indicates its relation to a birth date.

The field 'day' represents a component of a date of birth.

This field represents the month component of a birth date, as indicated by the property description "The month of birth, between 1 and 12." The schema name "legal_entity_dob" further confirms this is specifically for date of birth information.

The field 'month' is described as 'month of birth', making it part of the date of birth.

The field description explicitly states this represents "month of birth", meeting the taxonomy requirement for contextual birthdate indicators in descriptions.

The field explicitly represents the month component of a date of birth. The presence of "birth" in the schema name further indicates its relation to a birth date.

The field 'month' represents a component of a date of birth.

This field represents the year component of a birth date, as indicated by the property description "The four-digit year of birth." The schema name "legal_entity_dob" provides additional context that this is specifically for date of birth information.

The field 'year' is described as 'year of birth', which is part of the date of birth.

The field description explicitly states this represents "year of birth", satisfying the taxonomy rule for partial birthdate components with birth-related context.

The field explicitly represents the year component of a date of birth. The presence of "birth" in the schema name further indicates its relation to a birth date.

The field 'year' represents a component of a date of birth.

The field 'day' could be part of a date of birth, as it represents a component of a date.

The field 'month' could be part of a date of birth, as it represents a component of a date.

The field 'year' could be part of a date of birth, as it represents a component of a date.

The field 'day' could potentially represent part of a date of birth, as it is a numerical value between 1 and 31, which corresponds to the possible day values in a date.

Similar to the 'day' field, 'month' could represent part of a date of birth as it is a numerical value between 1 and 12, which corresponds to the possible month values in a date.

The 'year' field could also represent part of a date of birth as it is a four-digit year, which is often used in date representations.