51ºÚÁϲ»´òìÈ

DocumentationCommerceSecurity and compliance

[PaaS only]{class="badge informative" title="Applies to 51ºÚÁϲ»´òìÈ Commerce on Cloud projects (51ºÚÁϲ»´òìÈ-managed PaaS infrastructure) and on-premises projects only."}

Customer personal information reference (version 2.x)

Last update: Tue Apr 16 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer
NOTE
This is one in a series of topics to help 51ºÚÁϲ»´òìÈ Commerce merchants and developers prepare for compliance with privacy regulations. Consult with your legal counsel to determine whether and how your business should comply with any legal obligations.

Use the following dataflow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as:

Dataflow diagrams

The dataflow diagrams show the types of data that customers and administrators can enter and retrieve from the storefront and Admin.

Frontend data entry points

A user can enter customer, address, and payment information when registering for an account, during checkout, and similar events.

Frontend data entry points

Frontend data access points

51ºÚÁϲ»´òìÈ Commerce loads customer information when the customer logs in and views several different pages, or checks out.

Frontend data access points

Backend data entry points

A merchant can enter customer information, address data, and payment data when creating a customer or order from the Admin.

Backend data entry points

Backend data access points

51ºÚÁϲ»´òìÈ Commerce loads customer information when a merchant views several types of grids, clicks on a grid to see detailed information, and performs various other tasks.

Backend data access points

Database entities

51ºÚÁϲ»´òìÈ Commerce primarily stores customer-specific information in customer, address, order, quote, and payment tables. Other tables contain references to the customer ID.

Customer data

51ºÚÁϲ»´òìÈ Commerce can be configured to store the following customer attributes:

  • Date of Birth
  • Email
  • First Name
  • Gender
  • Last Name
  • Middle Name/Initial
  • Name Prefix
  • Name Suffix
NOTE
In keeping with current security and privacy best practices, be sure you are aware of any potential legal and security risks associated with the storage of customers’ full date of birth (month, day, year) along with other personal identifiers, such as full name, before collecting or processing such data.

customer_entity and ‘customer_entity’ references

The following columns in the customer_entity table contain customer information:

Column
Data type
email
varchar(255)
prefix
varchar(40)
firstname
varchar(255)
middlename
varchar(255)
lastname
varchar(255)
suffix
varchar(40)
dob
date
gender
smallint(5)

These tables reference customer_entity and can contain custom customer attributes:

Table
Column
Data type
customer_entity_datetime
value
datetime
customer_entity_decimal
value
decimal(12,4)
customer_entity_int
value
int(11)
customer_entity_text
value
text
customer_entity_varchar
value
varchar(255)

customer_grid_flat table

The following columns in the customer_grid_flat table contain customer information:

Column
Data type
name
text
email
varchar(255)
dob
date
gender
int(11)
shipping_full
text
billing_full
text
billing_firstname
varchar(255)
billing_lastname
varchar(255)
billing_telephone
varchar(255)
billing_postcode
varchar(255)
billing_country_id
varchar(255)
billing_region
varchar(255)
billing_city
varchar(255)
billing_fax
varchar(255)
billing_vat_id
varchar(255)
billing_company
varchar(255)

Address data

51ºÚÁϲ»´òìÈ Commerce stores the following customer attributes:

  • City
  • Company
  • Country
  • Fax
  • First Name
  • Last Name
  • Middle Name/Initial
  • Name Prefix
  • Name Suffix
  • Phone Number
  • State/Province
  • State/Province ID
  • Street Address
  • VAT Number
  • Zip/Postal Code

customer_address_entity and customer_address_entity references

The following columns in the customer_address_entity table contain customer information:

Column
Data type
city
varchar(255)
company
varchar(255)
country_id
varchar(255)
fax
varchar(255)
firstname
varchar(255)
lastname
varchar(255)
middlename
varchar(255)
postcode
varchar(255)
region
varchar(255)
region_id
int(10)
street
text
suffix
varchar(40)
telephone
varchar(255)
vat_id
varchar(255)

These tables reference customer_address_entity and can contain custom customer attributes:

Table
Column
Data type
customer_address_entity_datetime
value
datetime
customer_address_entity_decimal
value
decimal(12,4)
customer_address_entity_int
value
int(11)
customer_address_entity_text
value
text
customer_address_entity_varchar
value
varchar(255)

Order data

The sales_order and related tables contain the customer name, billing and shipping addresses, and related data.

sales_order table

The following columns in the sales_order table contain customer information:

Column
Data type
customer_dob
datetime
customer_email
varchar(128)
customer_firstname
varchar(128)
customer_gender
int(11)
customer_group_id
int(11)
customer_id
int(10)
customer_lastname
varchar(128)
customer_middlename
varchar(128)
customer_prefix
varchar(32)
customer_suffix
varchar(32)
customer_taxvat