From a5d71ff6a3ad0688c58dbd2b8a0d71fbbd91e476 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Fri, 6 Dec 2019 09:02:29 -0800 Subject: [PATCH 01/54] Data Flow Images Copied existing data flow images to new privacy folder. --- src/compliance/privacy/backend-data-access-points.svg | 1 + src/compliance/privacy/backend-data-entry-points.svg | 1 + src/compliance/privacy/frontend-data-access-points.svg | 1 + src/compliance/privacy/frontend-data-entry-points.svg | 1 + 4 files changed, 4 insertions(+) create mode 120000 src/compliance/privacy/backend-data-access-points.svg create mode 120000 src/compliance/privacy/backend-data-entry-points.svg create mode 120000 src/compliance/privacy/frontend-data-access-points.svg create mode 120000 src/compliance/privacy/frontend-data-entry-points.svg diff --git a/src/compliance/privacy/backend-data-access-points.svg b/src/compliance/privacy/backend-data-access-points.svg new file mode 120000 index 00000000000..41a13ad2cba --- /dev/null +++ b/src/compliance/privacy/backend-data-access-points.svg @@ -0,0 +1 @@ +../../../../guides/v2.2/architecture/gdpr/backend-data-access-points.svg \ No newline at end of file diff --git a/src/compliance/privacy/backend-data-entry-points.svg b/src/compliance/privacy/backend-data-entry-points.svg new file mode 120000 index 00000000000..53b057f3ad4 --- /dev/null +++ b/src/compliance/privacy/backend-data-entry-points.svg @@ -0,0 +1 @@ +../../../../guides/v2.2/architecture/gdpr/backend-data-entry-points.svg \ No newline at end of file diff --git a/src/compliance/privacy/frontend-data-access-points.svg b/src/compliance/privacy/frontend-data-access-points.svg new file mode 120000 index 00000000000..882dbebb7a7 --- /dev/null +++ b/src/compliance/privacy/frontend-data-access-points.svg @@ -0,0 +1 @@ +../../../../guides/v2.2/architecture/gdpr/frontend-data-access-points.svg \ No newline at end of file diff --git a/src/compliance/privacy/frontend-data-entry-points.svg b/src/compliance/privacy/frontend-data-entry-points.svg new file mode 120000 index 00000000000..171a28942b6 --- /dev/null +++ b/src/compliance/privacy/frontend-data-entry-points.svg @@ -0,0 +1 @@ +../../../../guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg \ No newline at end of file From 3dd5569c8d67c42ca063e1060a151f5bf61bd9b6 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Fri, 6 Dec 2019 09:06:01 -0800 Subject: [PATCH 02/54] Privacy regulation Intro topics Introduction to CCPA and GDPR. These link to agnostic PI Reference topics with data flow and database entity mapping info for M2 & M1. --- src/compliance/privacy/ccpa.md | 7 +++++++ src/compliance/privacy/gdpr.md | 25 +++++++++++++++++++++++++ 2 files changed, 32 insertions(+) create mode 100644 src/compliance/privacy/ccpa.md create mode 100644 src/compliance/privacy/gdpr.md diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md new file mode 100644 index 00000000000..d228717ce4c --- /dev/null +++ b/src/compliance/privacy/ccpa.md @@ -0,0 +1,7 @@ +--- +group: functional-areas +title: California Consumer Privacy Act +--- + +# California Consumer Privacy Act + diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md new file mode 100644 index 00000000000..671ce66d8ba --- /dev/null +++ b/src/compliance/privacy/gdpr.md @@ -0,0 +1,25 @@ +--- +group: functional-areas +title: General Data Protection Regulation +--- + +# General Data Protection Regulation + +The European Union (EU) enacted [General Data Protection Regulation](https://www.eugdpr.org/) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. + +System integrators can use the data flow diagrams and database information in the Personal Information Reference to build scripts to resolve use cases similar to the following: + +* A shopper asks for a copy of the data the merchant has stored about her +* A shopper requests that all information about him be deleted + +## Personal Information Reference + +The following topics contain data flow diagrams and database information for Magento version 2.x and Magento version 1.x. + +- [Personal Information Reference for Magento 2.x]({{ site.baseurl }}{% link compliance/privacy-regulations/pi-reference-m2.md %}) +- [Personal Information Reference for Magento 1.x]({{ site.baseurl }}{% link compliance/privacy-regulations/pi-reference-m1.md %}) + +For more information about how Magento helps merchants comply with GDPR, see the following: + +- [GDPR Compliance]{https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html} +- [Magento is Ready for GDPR](https://magento.com/gdpr) \ No newline at end of file From 19f987731bd4d72a1febd1f28a8f95ffdcdbd3ad Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Fri, 6 Dec 2019 09:06:44 -0800 Subject: [PATCH 03/54] Personal Informtion Reference topics Agnostic PI Reference topics with data flow and database entity mapping info for M2 & M1. --- src/compliance/privacy/pi-reference-m1.md | 296 ++++++++++++++++++++ src/compliance/privacy/pi-reference-m2.md | 326 ++++++++++++++++++++++ 2 files changed, 622 insertions(+) create mode 100644 src/compliance/privacy/pi-reference-m1.md create mode 100644 src/compliance/privacy/pi-reference-m2.md diff --git a/src/compliance/privacy/pi-reference-m1.md b/src/compliance/privacy/pi-reference-m1.md new file mode 100644 index 00000000000..a22292abf81 --- /dev/null +++ b/src/compliance/privacy/pi-reference-m1.md @@ -0,0 +1,296 @@ +--- +group: functional-areas +title: Personal Information Reference (Magento 1.x) +--- + +# Personal Information Reference (Magento 1.x) + +Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: + +- [GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) +- [CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) + +## Dataflow diagrams + +The data flow diagrams show the types of data that customers and administrators can enter and retrieve on 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-entry-points.svg) + +### Frontend data access points + +Magento loads customer information when the customer logs in and views several different pages or checks out. + +![Frontend data access points](frontend-data-access-points.svg) + +### Backend data entry points + +A merchant can enter customer, address, and payment information from the Admin to create a customer or order. + +![Backend data entry points](backend-data-entry-points.svg) + +### Backend data access points + +Magento 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](backend-data-access-points.svg) + +## Database entities + +Magento 1 stores customer information in customer, sales, and other database tables. + +### Customer data {#customer-data} + +Magento 1 stores customer information in the `customer_entity` and `customer_address_entity` tables. Both of these tables have several reference tables that can contain custom customer attributes. + +#### `customer_entity` and reference tables + +The following columns in the `customer_entity`table contain customer information: + +Column | Data type +--- | --- +`email` | varchar(255) + +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_address_entity` and reference tables + +The following 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_flat_order` and related tables contain the customer's name, billing and shipping addresses, and related information. + +#### `sales_flat_order` table + +The following columns in the `sales_order` table contain customer information: + +Column | Data type +--- | --- +`customer_id` | int(10) +`customer_email` | varchar(128) +`customer_firstname` | varchar(128) +`customer_gender` | int(11) +`customer_lastname` | varchar(128) +`customer_middlename` | varchar(128) +`customer_prefix` | varchar(32) +`customer_suffix` | varchar(32) +`customer_taxvat` | varchar(32) +`remote_ip` | varchar(32) + +#### `sales_flat_order_address` table + +The `sales_flat_order_address` table contains the customer's address. + +Column | Data type +--- | --- +`customer_id` | int(10) +`fax` | varchar(255) +`region` | varchar(255) +`postcode` | varchar(255) +`lastname` | varchar(255) +`street` | varchar(255) +`city` | varchar(255) +`email` | varchar(255) +`telephone` | varchar(255) +`firstname` | varchar(255) +`prefix` | varchar(255) +`suffix` | varchar(255) +`middlename` | varchar(255) +`company` | varchar(255) +`vat_id`| text + +#### `sales_flat_order_grid` table + +The following columns in the `sales_flat_order_grid` table contain customer information: + +Column | Data type +--- | --- +`customer_id` | int(10) +`shipping_name` | varchar(255) +`billing_name` | varchar(255) + +#### `sales_flat_order_payment` table + +The following columns in the `sales_flat_order_payment` table contain customer information: + +Column | Data type +--- | --- +`cc_exp_month` | varchar(255) +`cc_ss_start_year` | varchar(255) +`echeck_bank_name` | varchar(128) +`echeck_type` | varchar(255) +`cc_ss_start_month` | varchar(255) +`cc_owner` | varchar(255) +`cc_exp_year` | varchar(255) +`echeck_routing_number` | varchar(255) +`echeck_account_name` | varchar(255) + +### Quote data + +Quotes contain a customer's name, email, address, and related information. + +#### `sales_flat_quote` table + +The following columns in the `sales_flat_quote` table contain customer information: + +Column | Data type +--- | --- +`customer_id` | int(10) +`customer_tax_class_id` | int(10) +`customer_group_id` | int(10) +`customer_email` | varchar(255) +`customer_prefix` | varchar(40) +`customer_firstname` | varchar(255) +`customer_middlename` | varchar(40) +`customer_lastname` | varchar(255) +`customer_suffix` | varchar(40) +`customer_dob` | datetime +`customer_note` | varchar(255) +`remote_ip` | varchar(255) +`customer_gender` | varchar(255) + +#### `sales_flat_quote_address` table + +The following columns in the `sales_flat_quote_address` table contain customer information: + +Column | Data type +--- | --- +`email` | varchar(255) +`prefix` | varchar(40) +`firstname` | varchar(255) +`middlename` | varchar(40) +`lastname` | varchar(255) +`suffix` | varchar(40) +`company` | varchar(255) +`street` | varchar(255) +`city` | varchar(255) +`region` | varchar(255) +`postcode` | varchar(255) +`fax` | varchar(255) + +#### `sales_flat_quote_payment` table + +The `sales_flat_quote_payment` table includes credit card information and other transactional information. + +Column | Data type +--- | --- +`cc_last_4` | varchar(255) +`cc_owner` | varchar(255) +`cc_exp_month` | smallint(5) +`cc_exp_year` | smallint(5) +`cc_ss_owner` | varchar(255) +`cc_ss_start_month` | smallint(5) +`cc_ss_start_year` | smallint(5) + +### Archive data + +The following tables and columns contain customer information: + +Table | Column | Data type +--- | --- | --- +`enterprise_sales_creditmemo_grid_archive` | `billing_name` | varchar(255) +`enterprise_sales_invoice_grid_archive` | `billing_name` | varchar(255) +`enterprise_sales_order_grid_archive` | `billing_name` | varchar(255) +`enterprise_sales_order_grid_archive` | `customer_id` | int(10) +`enterprise_sales_order_grid_archive` | `shipping_name` | varchar(255) +`enterprise_sales_shipment_grid_archive` | `shipping_name` | varchar(255) + +### Sales data + +The following tables and columns contain customer information: + +Table | Column | Data type +--- | --- | --- +`sales_flat_creditmemo_grid` | `billing_name` | varchar(255) +`sales_flat_invoice_grid` | `billing_name` | varchar(255) + +### RMA data + +The following RMA tables and columns contain customer information: + +Table | Column | Data type +--- | --- | --- +`enterprise_rma` | `customer_custom_email` | varchar(255) +`enterprise_rma_grid` | `customer_id` | int(10) +`enterprise_rma_grid` | `customer_name` | varchar(255) + +### Miscellaneous data + +The following tables and columns contain customer information: + +Table | Column | Data type +--- | --- | --- +`core_email_queue_recipients` | `recipient_email` | varchar(128) +`core_email_queue_recipients` | `recipient_name` | varchar(255) +`customer_flowpassword` | `email` | varchar(255) +`customer_flowpassword` | `ip` | varchar(50) +`enterprise_giftregistry_person` | `email` | varchar(150) +`enterprise_giftregistry_person` | `firstname` | varchar(100) +`enterprise_giftregistry_person` | `lastname` | varchar(100) +`enterprise_giftregistry_person` | `middlename` | text +`enterprise_invitation` | `customer_id` | int(10) +`enterprise_invitation` | `email` | varchar(255) +`enterprise_invitation` | `referral_id` | int(10) +`enterprise_reminder_rule_coupon` | `customer_id` | int(10) +`enterprise_reminder_rule_coupon` | `emails_failed` | smallint(5) +`enterprise_scheduled_operations` | `email_receiver` | varchar(150) +`enterprise_scheduled_operations` | `email_sender` | varchar(150) +`gift_message` | `customer_id` | int(10) +`gift_message` | `recipient` | varchar(255) +`gift_message` | `sender` | varchar(255) +`newsletter_subscriber` | `customer_id` | int(10) +`newsletter_subscriber` | `subscriber_email` | varchar(150) +`persistent_session` | `customer_id` | int(10) +`persistent_session` | `info` | text +`poll_vote` | `customer_id` | int(10) +`poll_vote` | `ip_address` | varbinary(16) +`rating_option_vote` | `customer_id` | int(10) +`rating_option_vote` | `remote_ip` | varchar(50) +`rating_option_vote` | `remote_ip_long` | varbinary(516) +`send_friend_log` | `ip` | varbinary(16) + +Other tables that reference Customer: + +- `catalog_compare_item` +- `downloadable_link_purchased` +- `enterprise_customerbalance` +- `enterprise_customersegment_customer` +- `enterprise_giftregistry_entity` +- `enterprise_reminder_rule_log` +- `enterprise_reward` +- `log_customer` +- `log_visitor_online` +- `oauth_token` +- `product_alert_price` +- `product_alert_stock` +- `report_compared_product_index` +- `report_viewed_product_index` +- `review_detail` +- `sales_billing_agreement` +- `sales_flat_shipment` +- `sales_recurring_profile` +- `salesrule_coupon_usage` +- `salesrule_customer` +- `tag` +- `tag_relation` +- `wishlist` diff --git a/src/compliance/privacy/pi-reference-m2.md b/src/compliance/privacy/pi-reference-m2.md new file mode 100644 index 00000000000..3ebcfd28f4d --- /dev/null +++ b/src/compliance/privacy/pi-reference-m2.md @@ -0,0 +1,326 @@ +--- +group: functional-areas +title: Personal Information Reference (Magento 2.x) +--- + +# Personal Information Reference (Magento 2.x) + +Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: + +- [GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) +- [CCPA]({{ site.baseurl }}{% link compliance/orivacy/ccpa.md %}) + +## Data flow diagrams + +The data flow 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-entry-points.svg) + +### Frontend data access points + +Magento loads customer information when the customer logs in and views several different pages, or checks out. + +![Frontend data access points](frontend-data-access-points.svg) + +### 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-entry-points.svg) + +### Backend data access points + +Magento 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](backend-data-access-points.svg) + +## Database entities + +Magento 2 primarily stores customer-specific information in customer, address, order, quote, and payment tables. Other tables contain references to the customer ID. + +### Customer data {#customer-data} + +Magento 2 stores the following customer attributes: + +- Date of Birth +- Email +- First Name +- Gender +- Last Name +- Middle Name/Initial +- Name Prefix +- Name Suffix + +#### `customer_entity` and reference tables + +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 + +Magento 2 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 reference tables + +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's 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` | varchar(32) +`quote_address_id` | int(11) +`remote_ip` | varchar(32) +`x_forwarded_for` | varchar(32) + +#### `sales_order_address` table + +The `sales_order_address` table contains the customer's address. + +Column | Data type +--- | --- +`customer_address_id` | int(11) +`quote_address_id` | int(11) +`region_id` | int(11) +`customer_id` | int(11) +`fax` | varchar(255) +`region` | varchar(255) +`postcode` | varchar(255) +`lastname` | varchar(255) +`street` | varchar(255) +`city` | varchar(255) +`email` | varchar(255) +`telephone` | varchar(255) +`country_id` | varchar(2) +`firstname` | varchar(255) +`suffix` | varchar(255) +`company` | varchar(255) + +#### `sales_order_grid` table + +The following columns in the `sales_order_grid` table contain customer information: + +Column | Data type +--- | --- +`customer_id` | int(10) +`shipping_name` | varchar(255) +`billing_name` | varchar(255) +`billing_address` | varchar(255) +`shipping_address` | varchar(255) +`shipping_information` | varchar(255) +`customer_email` | varchar(255) +`customer_name` | varchar(255) + +### Quote data + +Quotes contain a customer's name, email, address, and related information. + +#### `quote` table + +The following columns in the `quote` table contain customer information: + +Column | Data type +--- | --- +`customer_id` | int(10) +`customer_email` | varchar(255) +`customer_prefix` | varchar(40) +`customer_firstname` | varchar(255) +`customer_middlename` | varchar(40) +`customer_lastname` | varchar(255) +`customer_dob` | datetime +`remote_ip` | varchar(32) +`customer_taxvat` | varchar(255) +`customer_gender` | varchar(255) + +#### `quote_address` table + +The following columns in the `quote_address` table contain customer information: + +Column | Data type +--- | --- +`customer_id` | int(10) +`email` | varchar(255) +`prefix` | varchar(40) +`firstname` | varchar(255) +`middlename` | varchar(40) +`lastname` | varchar(255) +`suffix` | varchar(40) +`company` | varchar(255) +`street` | varchar(255) +`city` | varchar(255) +`region` | varchar(255) +`region_id` | int(10) +`postcode` | varchar(20) +`country_id` | varchar(30) +`telephone` | varchar(255) +`fax` | varchar(255) + +### Payment data + +The `sales_order_payment` table includes credit card information and other transactional information. + +Column | Data type +--- | --- +`cc_exp_month` | varchar(12) +`echeck_bank_name` | varchar(128) +`cc_last_4` | varchar(100) +`cc_owner` | varchar(128) +`po_number` | varchar(32) +`cc_exp_year` | varchar(4) +`echeck_routing_number` | varchar(32) +`cc_debug_response_body` | varchar(32) +`echeck_account_name` | varchar(32) +`cc_number_enc` | varchar(128) +`additional_information` | text + +### Invitation data + +Magento can be configured so that customers can send invitations to private sales and events. + +#### `magento_invitation` table + +The `magento_invitation` table contains the customer ID, email, and referral ID. + +Column | Data type +--- | --- +`customer_id` | int(10) +`email` | varchar(255) +`referral_id` | int(10) + +#### `magento_invitation_track` table + +The `magento_invitation_track` table also contains customer information. + +Column | Data type +--- | --- +`inviter_id` | int(10) +`referral_id` | int(10) + +### Miscellaneous tables that reference customer + +The following tables contain a `customer_id` column: + +- `catalog_compare_item` +- `catalog_product_frontend_action` +- `downloadable_link_purchased` +- `magento_customerbalance` +- `magento_customersegment_customer` +- `magento_reward` +- `magento_rma` +- `oauth_token` +- `paypal_billing_agreement` +- `persistent_session` +- `product_alert_price` +- `product_stock_alert` +- `report_compared_product_index` +- `report_viewed_product_index` +- `review_detail` +- `salesrule_coupon_usage` +- `salesrule_customer` +- `wishlist` From 341feadb8dcf1b3e87f04842dd64e295be8d56eb Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Fri, 6 Dec 2019 09:07:37 -0800 Subject: [PATCH 04/54] Industry Compliance overview Parent toipc for new Compliance section. --- src/compliance/industry-compliance.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 src/compliance/industry-compliance.md diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md new file mode 100644 index 00000000000..46561b4fc38 --- /dev/null +++ b/src/compliance/industry-compliance.md @@ -0,0 +1,12 @@ +--- +group: compliance +title: Industry Compliance +--- +# Industry Compliance + +Merchants are responsible to meet industry guidelines for maintaining a secure environment, legal requirements, and best practices for online commerce in their jurisdiction. For a high-level overview, see the [Industry Compliance]{https://docs.magento.com/m2/ee/user_guide/stores/compliance-industry.html) section in the Magento User Guide. The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific legislation. + +## Privacy Legislation + +- [California Consumer Privacy Act (CCPA)]({{ site.baseurl }}{% link privacy/ccpa.md %}) +- [General Data Protection Regulation (GDPR)]({{ site.baseurl }}{% link privacy/gdpr.md %}) From a193428a6de96e673a104135202cb37193c2065d Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Fri, 6 Dec 2019 09:08:00 -0800 Subject: [PATCH 05/54] Update main-nav.yml New Compliance section --- src/_data/main-nav.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/_data/main-nav.yml b/src/_data/main-nav.yml index 722af640b60..b5a4a32f8e1 100644 --- a/src/_data/main-nav.yml +++ b/src/_data/main-nav.yml @@ -190,6 +190,9 @@ - label: Checkout url: /howdoi/checkout/checkout_overview.html + - label: Compliance + url: /compliance/industry-compliance.html + - label: Inventory Management url: /inventory/index.html exclude_versions: ['2.0', '2.1', '2.2'] From d3c22f95eac7fa73a212444272666de79282b67d Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Fri, 6 Dec 2019 14:34:52 -0800 Subject: [PATCH 06/54] Update industry-compliance.md Parent topic for new Compliance section. --- src/compliance/industry-compliance.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md index 46561b4fc38..c965d0b2d31 100644 --- a/src/compliance/industry-compliance.md +++ b/src/compliance/industry-compliance.md @@ -4,9 +4,11 @@ title: Industry Compliance --- # Industry Compliance -Merchants are responsible to meet industry guidelines for maintaining a secure environment, legal requirements, and best practices for online commerce in their jurisdiction. For a high-level overview, see the [Industry Compliance]{https://docs.magento.com/m2/ee/user_guide/stores/compliance-industry.html) section in the Magento User Guide. The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific legislation. +Merchants are obligated to meet industry guidelines for maintaining a secure environment, legal requirements in their jurisdiction, and best practices for online commerce. To learn more, see the [Industry Compliance]{https://docs.magento.com/m2/ee/user_guide/stores/compliance-industry.html) section in the Magento User Guide. ## Privacy Legislation -- [California Consumer Privacy Act (CCPA)]({{ site.baseurl }}{% link privacy/ccpa.md %}) -- [General Data Protection Regulation (GDPR)]({{ site.baseurl }}{% link privacy/gdpr.md %}) +The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific privacy legistlation. Some of the recent privacy regulations require additional development effort on the part of the merchant. See the following topics for the technical information you need to support your clients who have Magento installations. + +- [California Consumer Privacy Act (CCPA)]({% link privacy/ccpa.md %}) +- [General Data Protection Regulation (GDPR)]({% link privacy/gdpr.md %}) From a0f576203a043b5fcd4aaf9c761639ba5c102d0b Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Fri, 6 Dec 2019 14:35:48 -0800 Subject: [PATCH 07/54] Update ccpa.md Overview of developer role on a merdhant's compliance team. --- src/compliance/privacy/ccpa.md | 41 ++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index d228717ce4c..51f14ca8cdb 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -5,3 +5,44 @@ title: California Consumer Privacy Act # California Consumer Privacy Act +The [California Consumer Protection Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. + +The CCPA grants the following new rights to consumers: + +- **Right to know** the categories of personal information about them that is collected, used, shared, or sold in the past 12 months. +- **Right to delete** certain types of personal information that is held by a business and/or their service provider(s). +- **Right to opt out** of the sale of their personal information. +- **Right to non-discrimination** in terms of price or service for having exercised a privacy right under CCPA. + +## Read the CCPA Compliance Guide + +A coordinated effort is required to develop and implement a plan to address CCPA compliance. Merchants are encouraged to use the roadmap in the CCPA Compliance Guide to mobilize resources and prioritize tasks so they can move ahead on multiple fronts. + +The CCPA Compliance Guide presents a role-based team approach from the perspective of the merchant's business to: + +1. Assemble a cross-functional team to address CCPA compliance. + +1. **Take inventory of digital properties.** + +1. **Map the customer journey and data collection processes.** + +1. **Establish procedures and mechanisms to respond to customer requests.** + +1. **Write the content for the required CCPA customer notifications.** + +1. Review agreements with service providers. + +1. Update the privacy policy. + +1. Document all CCPA-related procedures and maintain records. + +As a software developer, you might be asked to participate as a stakeholder on a merchant's cross-functional compliance team, with emphasis on steps 2 - 5. + +[1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act + +## Study the Personal Information Reference + +Become familiar with the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. + +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-reference-m2.md -%}) +- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-reference-m1.md -%}) From 28afcfb4d7a887d85a30670e0864e4487ca16692 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 9 Dec 2019 08:19:38 -0800 Subject: [PATCH 08/54] Renamed Files re3named dat5a reference files --- .../privacy/{pi-reference-m1.md => pi-data-reference-m1.md} | 6 +++--- .../privacy/{pi-reference-m2.md => pi-data-reference-m2.md} | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) rename src/compliance/privacy/{pi-reference-m1.md => pi-data-reference-m1.md} (98%) rename src/compliance/privacy/{pi-reference-m2.md => pi-data-reference-m2.md} (98%) diff --git a/src/compliance/privacy/pi-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md similarity index 98% rename from src/compliance/privacy/pi-reference-m1.md rename to src/compliance/privacy/pi-data-reference-m1.md index a22292abf81..b40eb0f20a4 100644 --- a/src/compliance/privacy/pi-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -1,9 +1,9 @@ --- -group: functional-areas -title: Personal Information Reference (Magento 1.x) +group: compliance +title: Personal Information Data Reference (Magento 1.x) --- -# Personal Information Reference (Magento 1.x) +# Personal Information Data Reference (Magento 1.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: diff --git a/src/compliance/privacy/pi-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md similarity index 98% rename from src/compliance/privacy/pi-reference-m2.md rename to src/compliance/privacy/pi-data-reference-m2.md index 3ebcfd28f4d..314d7661df5 100644 --- a/src/compliance/privacy/pi-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -1,9 +1,9 @@ --- -group: functional-areas -title: Personal Information Reference (Magento 2.x) +group: compliance +title: Personal Information Data Reference (Magento 2.x) --- -# Personal Information Reference (Magento 2.x) +# Personal Information Data Reference (Magento 2.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: From b76afa9bdc30570b9de79710eb4ec7e7a35180b6 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 9 Dec 2019 08:20:49 -0800 Subject: [PATCH 09/54] Updated links & mete data Addee greoup: compliance to meta data; updated links to renamed references. --- src/compliance/privacy/ccpa.md | 6 +++--- src/compliance/privacy/gdpr.md | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 51f14ca8cdb..9a73986d993 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -1,5 +1,5 @@ --- -group: functional-areas +group: compliance title: California Consumer Privacy Act --- @@ -44,5 +44,5 @@ As a software developer, you might be asked to participate as a stakeholder on a Become familiar with the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-reference-m2.md -%}) -- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-reference-m1.md -%}) +- [PI Data Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +- [PI Data Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index 671ce66d8ba..bb27a08e524 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -1,5 +1,5 @@ --- -group: functional-areas +group: conpliance title: General Data Protection Regulation --- @@ -12,12 +12,12 @@ System integrators can use the data flow diagrams and database information in th * A shopper asks for a copy of the data the merchant has stored about her * A shopper requests that all information about him be deleted -## Personal Information Reference +## Personal Information References The following topics contain data flow diagrams and database information for Magento version 2.x and Magento version 1.x. -- [Personal Information Reference for Magento 2.x]({{ site.baseurl }}{% link compliance/privacy-regulations/pi-reference-m2.md %}) -- [Personal Information Reference for Magento 1.x]({{ site.baseurl }}{% link compliance/privacy-regulations/pi-reference-m1.md %}) +- [PI Data Reference for Magento 2.x]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m2.md %}) +- [PI Data Reference for Magento 1.x]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m1.md %}) For more information about how Magento helps merchants comply with GDPR, see the following: From de1287dab60c7d77db19a1b3fc1daad7fa8f4f90 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 9 Dec 2019 08:21:17 -0800 Subject: [PATCH 10/54] Create compliance.yml TOC for new Compliance section. --- src/_data/toc/compliance.yml | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 src/_data/toc/compliance.yml diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml new file mode 100644 index 00000000000..84601374fda --- /dev/null +++ b/src/_data/toc/compliance.yml @@ -0,0 +1,22 @@ +label: Compliance +pages: + - label: Industry Compliance + url: /compliance/industry-compliance.html + + children: + + - label: Privacy Regulations + + children: + + - CCPA + url: /compliance/ccpa.html + + - GDPR + url: /compliance/gdpr.html + + - PI Data Reference (M2) + url: /compliance/pi-data-reference-m2.html + + - PI Data Reference (M1) + url: /compliance/pi-data-reference-m1.html From f98434891c783f63267d67e4484e9452fb5d337c Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 9 Dec 2019 08:44:33 -0800 Subject: [PATCH 11/54] SVG data flow images Uploading the SVG data flow images. (The earlier upload included aliases to each image rather than the actual images.) --- src/compliance/privacy/backend-data-access-points.svg | 2 +- src/compliance/privacy/backend-data-entry-points.svg | 2 +- src/compliance/privacy/frontend-data-access-points.svg | 2 +- src/compliance/privacy/frontend-data-entry-points.svg | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) mode change 120000 => 100644 src/compliance/privacy/backend-data-access-points.svg mode change 120000 => 100644 src/compliance/privacy/backend-data-entry-points.svg mode change 120000 => 100644 src/compliance/privacy/frontend-data-access-points.svg mode change 120000 => 100644 src/compliance/privacy/frontend-data-entry-points.svg diff --git a/src/compliance/privacy/backend-data-access-points.svg b/src/compliance/privacy/backend-data-access-points.svg deleted file mode 120000 index 41a13ad2cba..00000000000 --- a/src/compliance/privacy/backend-data-access-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/backend-data-access-points.svg \ No newline at end of file diff --git a/src/compliance/privacy/backend-data-access-points.svg b/src/compliance/privacy/backend-data-access-points.svg new file mode 100644 index 00000000000..d70140eee4c --- /dev/null +++ b/src/compliance/privacy/backend-data-access-points.svg @@ -0,0 +1 @@ +MagentoCustomerDataAddressDataCustomerPaymentDataAdminDashboardOrdersGrid/ViewInvoicesGrid/ViewShipmentGrid/ViewCreditMemoGrid/ViewCustomersGrid/ViewReturnsGrid/ViewBillingAgreementGrid/ViewTransactionsGrid/ViewNewsletterSubscribersMarketingInvitationsMarketingEventsAbandonedCartsReportSystemExportCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataOrderHistoryCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataCustomerDataCustomerDataCustomerDataCustomerDataAddressDataCustomerDataEmailUser \ No newline at end of file diff --git a/src/compliance/privacy/backend-data-entry-points.svg b/src/compliance/privacy/backend-data-entry-points.svg deleted file mode 120000 index 53b057f3ad4..00000000000 --- a/src/compliance/privacy/backend-data-entry-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/backend-data-entry-points.svg \ No newline at end of file diff --git a/src/compliance/privacy/backend-data-entry-points.svg b/src/compliance/privacy/backend-data-entry-points.svg new file mode 100644 index 00000000000..f04c4170275 --- /dev/null +++ b/src/compliance/privacy/backend-data-entry-points.svg @@ -0,0 +1 @@ +AdminAddressDataCustomerDataCustomerDataCustomerDataCustomerPaymentDataMagentoNewOrderNewCustomerCustomerViewAddressDataAddressData \ No newline at end of file diff --git a/src/compliance/privacy/frontend-data-access-points.svg b/src/compliance/privacy/frontend-data-access-points.svg deleted file mode 120000 index 882dbebb7a7..00000000000 --- a/src/compliance/privacy/frontend-data-access-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/frontend-data-access-points.svg \ No newline at end of file diff --git a/src/compliance/privacy/frontend-data-access-points.svg b/src/compliance/privacy/frontend-data-access-points.svg new file mode 100644 index 00000000000..75ab9bd675b --- /dev/null +++ b/src/compliance/privacy/frontend-data-access-points.svg @@ -0,0 +1 @@ +MagentoCustomerAccountDashboardCustomerAccountOrderViewCustomerAccountInformationCustomerAccountAddressBookCheckoutCustomerDataAddressDataOrderHistoryCustomerDataOrderDataAddressDataAddressDataOrderDataOrderDataOrderDataUser \ No newline at end of file diff --git a/src/compliance/privacy/frontend-data-entry-points.svg b/src/compliance/privacy/frontend-data-entry-points.svg deleted file mode 120000 index 171a28942b6..00000000000 --- a/src/compliance/privacy/frontend-data-entry-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg \ No newline at end of file diff --git a/src/compliance/privacy/frontend-data-entry-points.svg b/src/compliance/privacy/frontend-data-entry-points.svg new file mode 100644 index 00000000000..50dcda2adbc --- /dev/null +++ b/src/compliance/privacy/frontend-data-entry-points.svg @@ -0,0 +1 @@ +UserAddressDataCustomerDataCustomerDataAddressDataCustomerDataCustomerPaymentDataMagentoCheckoutCustomerRegistrationCustomerAccountInfoCustomerAccountAddressBookPaymentAuthRequestPaymentGateways \ No newline at end of file From f3b1b89c9794d79f8c13fff573becfc8ec97c62d Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 9 Dec 2019 11:25:34 -0800 Subject: [PATCH 12/54] Update compliance.yml Corrrected spacing --- src/_data/toc/compliance.yml | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index 84601374fda..7d8cd2b0b68 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -2,21 +2,19 @@ label: Compliance pages: - label: Industry Compliance url: /compliance/industry-compliance.html - children: - - label: Privacy Regulations + - label: Privacy Regulations + children: - children: + - label: CCPA + url: /compliance/privacy/ccpa.html - - CCPA - url: /compliance/ccpa.html + - label: GDPR + url: /compliance/privacy/gdpr.html - - GDPR - url: /compliance/gdpr.html + - label: PI Data Reference (M2) + url: /compliance/privacy/pi-data-reference-m2.html - - PI Data Reference (M2) - url: /compliance/pi-data-reference-m2.html - - - PI Data Reference (M1) - url: /compliance/pi-data-reference-m1.html + - label: PI Data Reference (M1) + url: /compliance/privacy/pi-data-reference-m1.html From fc7ebdb1b9590294c247406891cfb6f78483347b Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 9 Dec 2019 11:25:53 -0800 Subject: [PATCH 13/54] Update industry-compliance.md trying to resolve links --- src/compliance/industry-compliance.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md index c965d0b2d31..d9de78022ab 100644 --- a/src/compliance/industry-compliance.md +++ b/src/compliance/industry-compliance.md @@ -8,7 +8,11 @@ Merchants are obligated to meet industry guidelines for maintaining a secure env ## Privacy Legislation -The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific privacy legistlation. Some of the recent privacy regulations require additional development effort on the part of the merchant. See the following topics for the technical information you need to support your clients who have Magento installations. +The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific privacy legislation. Some of the recent privacy regulations require additional development effort on the part of the merchant. See the following topics for the technical information you need to support your clients who have Magento installations. -- [California Consumer Privacy Act (CCPA)]({% link privacy/ccpa.md %}) -- [General Data Protection Regulation (GDPR)]({% link privacy/gdpr.md %}) + +- [California Consumer Privacy Act (CCPA)]{{ site.baseurl }}/compliance/privacy/ccpa.md %} +- [General Data Protection Regulation (GDPR)]{{ site.baseurl }}/compliance/privacy/gdpr.md %} From 6206d89a7eb8c35a02115f2569d876326c2898d0 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 08:27:30 -0800 Subject: [PATCH 14/54] Update main-nav.yml fixed path --- src/_data/main-nav.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_data/main-nav.yml b/src/_data/main-nav.yml index b5a4a32f8e1..69a66a31e5e 100644 --- a/src/_data/main-nav.yml +++ b/src/_data/main-nav.yml @@ -191,7 +191,7 @@ url: /howdoi/checkout/checkout_overview.html - label: Compliance - url: /compliance/industry-compliance.html + url: ../../../compliance/industry-compliance.html - label: Inventory Management url: /inventory/index.html From 8509b200895338eec73010ded6c8b4df1c2647c6 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 08:27:42 -0800 Subject: [PATCH 15/54] Update compliance.yml fixed paths --- src/_data/toc/compliance.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index 7d8cd2b0b68..0a19523c2da 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -1,20 +1,20 @@ label: Compliance pages: - label: Industry Compliance - url: /compliance/industry-compliance.html + url: ../../../compliance/industry-compliance.html children: - label: Privacy Regulations children: - label: CCPA - url: /compliance/privacy/ccpa.html + url: ../../../compliance/privacy/ccpa.html - label: GDPR - url: /compliance/privacy/gdpr.html + url: ../../../compliance/privacy/gdpr.html - label: PI Data Reference (M2) - url: /compliance/privacy/pi-data-reference-m2.html + url: ../../../compliance/privacy/pi-data-reference-m2.html - label: PI Data Reference (M1) - url: /compliance/privacy/pi-data-reference-m1.html + url: ../../../compliance/privacy/pi-data-reference-m1.html From a2ce7e7527d5ddd5c74ed2932d03da2a2c53e61b Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 08:29:09 -0800 Subject: [PATCH 16/54] Fixed titles Removed duplicate title; corrected link syntax. --- src/compliance/privacy/ccpa.md | 19 +++++++------------ src/compliance/privacy/gdpr.md | 6 ++---- 2 files changed, 9 insertions(+), 16 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 9a73986d993..ade6eae5119 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -3,8 +3,6 @@ group: compliance title: California Consumer Privacy Act --- -# California Consumer Privacy Act - The [California Consumer Protection Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. The CCPA grants the following new rights to consumers: @@ -14,11 +12,9 @@ The CCPA grants the following new rights to consumers: - **Right to opt out** of the sale of their personal information. - **Right to non-discrimination** in terms of price or service for having exercised a privacy right under CCPA. -## Read the CCPA Compliance Guide - -A coordinated effort is required to develop and implement a plan to address CCPA compliance. Merchants are encouraged to use the roadmap in the CCPA Compliance Guide to mobilize resources and prioritize tasks so they can move ahead on multiple fronts. +## CCPA Compliance Guide -The CCPA Compliance Guide presents a role-based team approach from the perspective of the merchant's business to: +A coordinated effort is required to develop and implement a plan to address CCPA compliance. Merchants are encouraged to assemble a cross-functional team and follow the roadmap outlined in [CCPA Compliance Guide][2]{: target="_blank"} to bring their company into compliance with the regulation. As a software developer, you might be asked to participate as a stakeholder on a cross-functional compliance team with particular emphasis on steps 2 - 5. 1. Assemble a cross-functional team to address CCPA compliance. @@ -36,13 +32,12 @@ The CCPA Compliance Guide presents a role-based team approach from the perspecti 1. Document all CCPA-related procedures and maintain records. -As a software developer, you might be asked to participate as a stakeholder on a merchant's cross-functional compliance team, with emphasis on steps 2 - 5. - -[1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act +## Personal Information Data Reference -## Study the Personal Information Reference - -Become familiar with the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. +For technical information, see the data flow diagrams and database entity mappings in the PI Data Reference that applies to the version(s) of Magento that you support. - [PI Data Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) - [PI Data Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) + +[1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act +[2]: https://docs.magento.com/m2/ee/user_guide/stores/compliance-ccpa-guide.html diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index bb27a08e524..097e0261f2b 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -3,9 +3,7 @@ group: conpliance title: General Data Protection Regulation --- -# General Data Protection Regulation - -The European Union (EU) enacted [General Data Protection Regulation](https://www.eugdpr.org/) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. +The European Union (EU) enacted [General Data Protection Regulation](https://ec.europa.eu/info/law/law-topic/data-protection_en) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. System integrators can use the data flow diagrams and database information in the Personal Information Reference to build scripts to resolve use cases similar to the following: @@ -21,5 +19,5 @@ The following topics contain data flow diagrams and database information for Mag For more information about how Magento helps merchants comply with GDPR, see the following: -- [GDPR Compliance]{https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html} +- [GDPR Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html) - [Magento is Ready for GDPR](https://magento.com/gdpr) \ No newline at end of file From a07e8faa3c3115eccdeaa871f8936cb1ddfa8ef0 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 08:30:04 -0800 Subject: [PATCH 17/54] Update industry-compliance.md removed commented out links --- src/compliance/industry-compliance.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md index d9de78022ab..5ce6651031f 100644 --- a/src/compliance/industry-compliance.md +++ b/src/compliance/industry-compliance.md @@ -2,17 +2,10 @@ group: compliance title: Industry Compliance --- -# Industry Compliance Merchants are obligated to meet industry guidelines for maintaining a secure environment, legal requirements in their jurisdiction, and best practices for online commerce. To learn more, see the [Industry Compliance]{https://docs.magento.com/m2/ee/user_guide/stores/compliance-industry.html) section in the Magento User Guide. -## Privacy Legislation - The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific privacy legislation. Some of the recent privacy regulations require additional development effort on the part of the merchant. See the following topics for the technical information you need to support your clients who have Magento installations. - -- [California Consumer Privacy Act (CCPA)]{{ site.baseurl }}/compliance/privacy/ccpa.md %} -- [General Data Protection Regulation (GDPR)]{{ site.baseurl }}/compliance/privacy/gdpr.md %} +- [California Consumer Privacy Act (CCPA)]({% link compliance/privacy/ccpa.md %}) +- [General Data Protection Regulation (GDPR)]({% link compliance/privacy/gdpr.md %}) From 7d6c499b2829f5e792bd5adde78f7d50181e2d92 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 08:31:41 -0800 Subject: [PATCH 18/54] Removed duplicate title Removed duplicate title; resolved link syntax issue. --- src/compliance/privacy/pi-data-reference-m1.md | 2 -- src/compliance/privacy/pi-data-reference-m2.md | 4 +--- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index b40eb0f20a4..38108fdf390 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -3,8 +3,6 @@ group: compliance title: Personal Information Data Reference (Magento 1.x) --- -# Personal Information Data Reference (Magento 1.x) - Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: - [GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index 314d7661df5..8bd8cc06d0b 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -3,12 +3,10 @@ group: compliance title: Personal Information Data Reference (Magento 2.x) --- -# Personal Information Data Reference (Magento 2.x) - Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: - [GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) -- [CCPA]({{ site.baseurl }}{% link compliance/orivacy/ccpa.md %}) +- [CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) ## Data flow diagrams From 5214b6293a007ba4b9b62c4e871fcdc0270521df Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 08:47:48 -0800 Subject: [PATCH 19/54] Title Changed Changed title to Personal Information Reference. --- src/_data/toc/compliance.yml | 4 ++-- src/compliance/privacy/ccpa.md | 4 ++-- src/compliance/privacy/gdpr.md | 4 ++-- src/compliance/privacy/pi-data-reference-m1.md | 2 +- src/compliance/privacy/pi-data-reference-m2.md | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index 0a19523c2da..4f383277bbd 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -13,8 +13,8 @@ pages: - label: GDPR url: ../../../compliance/privacy/gdpr.html - - label: PI Data Reference (M2) + - label: Personal Information Reference (M2) url: ../../../compliance/privacy/pi-data-reference-m2.html - - label: PI Data Reference (M1) + - label: Personal Information Reference (M1) url: ../../../compliance/privacy/pi-data-reference-m1.html diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index ade6eae5119..59a5f216cfa 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -36,8 +36,8 @@ A coordinated effort is required to develop and implement a plan to address CCPA For technical information, see the data flow diagrams and database entity mappings in the PI Data Reference that applies to the version(s) of Magento that you support. -- [PI Data Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) -- [PI Data Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) [1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act [2]: https://docs.magento.com/m2/ee/user_guide/stores/compliance-ccpa-guide.html diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index 097e0261f2b..fd03075bcdc 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -14,8 +14,8 @@ System integrators can use the data flow diagrams and database information in th The following topics contain data flow diagrams and database information for Magento version 2.x and Magento version 1.x. -- [PI Data Reference for Magento 2.x]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m2.md %}) -- [PI Data Reference for Magento 1.x]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m1.md %}) +- [Personal Information Reference (Magento 2.x)]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m2.md %}) +- [Personal Information Reference (Magento 1.x)]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m1.md %}) For more information about how Magento helps merchants comply with GDPR, see the following: diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index 38108fdf390..2f97ff46dcf 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -1,6 +1,6 @@ --- group: compliance -title: Personal Information Data Reference (Magento 1.x) +title: Personal Information Reference (Magento 1.x) --- Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index 8bd8cc06d0b..01533568e73 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -1,6 +1,6 @@ --- group: compliance -title: Personal Information Data Reference (Magento 2.x) +title: Personal Information Reference (Magento 2.x) --- Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: From 241cb9dd1c31c9c5f2ab6e2390721e2a038453a3 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 12:06:38 -0800 Subject: [PATCH 20/54] Update compliance.yml Shortened option name. --- src/_data/toc/compliance.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index 4f383277bbd..e3794788d28 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -13,8 +13,8 @@ pages: - label: GDPR url: ../../../compliance/privacy/gdpr.html - - label: Personal Information Reference (M2) + - label: PI Reference (M2.x) url: ../../../compliance/privacy/pi-data-reference-m2.html - - label: Personal Information Reference (M1) + - label: PI Reference (M1.x) url: ../../../compliance/privacy/pi-data-reference-m1.html From 330b94708be94e247f3477d8b30fbbc2334ff08f Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 12:08:01 -0800 Subject: [PATCH 21/54] Update gdpr.md Added redirect; changed Personal Informaiton Reference section to match CCPA topic. --- src/compliance/privacy/gdpr.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index fd03075bcdc..74d9c7f0b2a 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -1,6 +1,11 @@ --- -group: conpliance +group: compliance title: General Data Protection Regulation +redirect_from: + - /guides/v2.3/architecture/gdpr/magento-2x.html + - /guides/v2.3/architecture/gdpr/magento-1x.html + - /guides/v2.2/architecture/gdpr/magento-2x.html + - /guides/v2.2/architecture/gdpr/magento-1x.html --- The European Union (EU) enacted [General Data Protection Regulation](https://ec.europa.eu/info/law/law-topic/data-protection_en) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. @@ -10,14 +15,14 @@ System integrators can use the data flow diagrams and database information in th * A shopper asks for a copy of the data the merchant has stored about her * A shopper requests that all information about him be deleted -## Personal Information References +## Personal Information Reference -The following topics contain data flow diagrams and database information for Magento version 2.x and Magento version 1.x. +For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -- [Personal Information Reference (Magento 2.x)]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m2.md %}) -- [Personal Information Reference (Magento 1.x)]({{ site.baseurl }}{% link compliance/privacy/pi-data-reference-m1.md %}) +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) For more information about how Magento helps merchants comply with GDPR, see the following: - [GDPR Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html) -- [Magento is Ready for GDPR](https://magento.com/gdpr) \ No newline at end of file +- [Magento is Ready for GDPR](https://magento.com/gdpr) From a446cb239152755b22c5a1074df0e609676f4f97 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 12:09:15 -0800 Subject: [PATCH 22/54] Update ccpa.md reworked sentence (line 17); updated Personal Information Reference section. --- src/compliance/privacy/ccpa.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 59a5f216cfa..ff3ec5f26a0 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -14,7 +14,7 @@ The CCPA grants the following new rights to consumers: ## CCPA Compliance Guide -A coordinated effort is required to develop and implement a plan to address CCPA compliance. Merchants are encouraged to assemble a cross-functional team and follow the roadmap outlined in [CCPA Compliance Guide][2]{: target="_blank"} to bring their company into compliance with the regulation. As a software developer, you might be asked to participate as a stakeholder on a cross-functional compliance team with particular emphasis on steps 2 - 5. +A coordinated effort is required to develop and implement a plan to address CCPA compliance. Merchants are encouraged to assemble a cross-functional team, and follow the roadmap outlined in [CCPA Compliance Guide][2]{: target="_blank"} to bring their company into compliance with the regulation. As a developer, you might be invited to participate as a stakeholder with an emphasis on steps 2 - 5 of the process. See the CCPA Compliance Guide for more information. 1. Assemble a cross-functional team to address CCPA compliance. @@ -32,9 +32,9 @@ A coordinated effort is required to develop and implement a plan to address CCPA 1. Document all CCPA-related procedures and maintain records. -## Personal Information Data Reference +## Personal Information Reference -For technical information, see the data flow diagrams and database entity mappings in the PI Data Reference that applies to the version(s) of Magento that you support. +For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. - [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) - [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) From 807a12de3a6bf45b286d24c1a0607d6dedaa632e Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 12:10:21 -0800 Subject: [PATCH 23/54] Deleted Images Deleted images which were moved to compliance/privacy. --- src/guides/v2.2/architecture/gdpr/backend-data-access-points.svg | 1 - src/guides/v2.2/architecture/gdpr/backend-data-entry-points.svg | 1 - .../v2.2/architecture/gdpr/frontend-data-access-points.svg | 1 - src/guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg | 1 - 4 files changed, 4 deletions(-) delete mode 100644 src/guides/v2.2/architecture/gdpr/backend-data-access-points.svg delete mode 100644 src/guides/v2.2/architecture/gdpr/backend-data-entry-points.svg delete mode 100644 src/guides/v2.2/architecture/gdpr/frontend-data-access-points.svg delete mode 100644 src/guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg diff --git a/src/guides/v2.2/architecture/gdpr/backend-data-access-points.svg b/src/guides/v2.2/architecture/gdpr/backend-data-access-points.svg deleted file mode 100644 index d70140eee4c..00000000000 --- a/src/guides/v2.2/architecture/gdpr/backend-data-access-points.svg +++ /dev/null @@ -1 +0,0 @@ -MagentoCustomerDataAddressDataCustomerPaymentDataAdminDashboardOrdersGrid/ViewInvoicesGrid/ViewShipmentGrid/ViewCreditMemoGrid/ViewCustomersGrid/ViewReturnsGrid/ViewBillingAgreementGrid/ViewTransactionsGrid/ViewNewsletterSubscribersMarketingInvitationsMarketingEventsAbandonedCartsReportSystemExportCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataOrderHistoryCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataAddressDataCustomerPaymentDataCustomerDataCustomerDataCustomerDataCustomerDataCustomerDataAddressDataCustomerDataEmailUser \ No newline at end of file diff --git a/src/guides/v2.2/architecture/gdpr/backend-data-entry-points.svg b/src/guides/v2.2/architecture/gdpr/backend-data-entry-points.svg deleted file mode 100644 index f04c4170275..00000000000 --- a/src/guides/v2.2/architecture/gdpr/backend-data-entry-points.svg +++ /dev/null @@ -1 +0,0 @@ -AdminAddressDataCustomerDataCustomerDataCustomerDataCustomerPaymentDataMagentoNewOrderNewCustomerCustomerViewAddressDataAddressData \ No newline at end of file diff --git a/src/guides/v2.2/architecture/gdpr/frontend-data-access-points.svg b/src/guides/v2.2/architecture/gdpr/frontend-data-access-points.svg deleted file mode 100644 index 75ab9bd675b..00000000000 --- a/src/guides/v2.2/architecture/gdpr/frontend-data-access-points.svg +++ /dev/null @@ -1 +0,0 @@ -MagentoCustomerAccountDashboardCustomerAccountOrderViewCustomerAccountInformationCustomerAccountAddressBookCheckoutCustomerDataAddressDataOrderHistoryCustomerDataOrderDataAddressDataAddressDataOrderDataOrderDataOrderDataUser \ No newline at end of file diff --git a/src/guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg b/src/guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg deleted file mode 100644 index 50dcda2adbc..00000000000 --- a/src/guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg +++ /dev/null @@ -1 +0,0 @@ -UserAddressDataCustomerDataCustomerDataAddressDataCustomerDataCustomerPaymentDataMagentoCheckoutCustomerRegistrationCustomerAccountInfoCustomerAccountAddressBookPaymentAuthRequestPaymentGateways \ No newline at end of file From 9a824c70ef880b44f7d0ee843d23bf178f42e3ea Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 12:11:33 -0800 Subject: [PATCH 24/54] Deleted topics These have been redirected to compliance/privacy topics. --- .../v2.2/architecture/gdpr/magento-1x.md | 299 ---------------- .../v2.2/architecture/gdpr/magento-2x.md | 329 ------------------ .../v2.3/architecture/gdpr/magento-1x.md | 1 - .../v2.3/architecture/gdpr/magento-2x.md | 1 - 4 files changed, 630 deletions(-) delete mode 100644 src/guides/v2.2/architecture/gdpr/magento-1x.md delete mode 100644 src/guides/v2.2/architecture/gdpr/magento-2x.md delete mode 120000 src/guides/v2.3/architecture/gdpr/magento-1x.md delete mode 120000 src/guides/v2.3/architecture/gdpr/magento-2x.md diff --git a/src/guides/v2.2/architecture/gdpr/magento-1x.md b/src/guides/v2.2/architecture/gdpr/magento-1x.md deleted file mode 100644 index 2a37b467e89..00000000000 --- a/src/guides/v2.2/architecture/gdpr/magento-1x.md +++ /dev/null @@ -1,299 +0,0 @@ ---- -group: architecture-guide ---- - -# General Data Protection Regulation - -The European Union (EU) enacted [General Data Protection Regulation](https://www.eugdpr.org/) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. - -We are publishing this compliance information to help our merchants and their system integrators with GDPR compliance. A system integrator can use the data flow diagrams and database information to build scripts to resolve use cases similar to the following: - -* A shopper asks for a copy of the data the merchant has stored about her -* A shopper requests that all information about him be deleted - -See the corporate [Magento website](https://magento.com/gdpr) for more information about how Magento helps merchants comply with GDPR. - -## Dataflow diagrams - -The data flow diagrams show the types of data that customers and administrators can enter and retrieve on the storefront and in 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-entry-points.svg) - -### Frontend data access points - -Magento loads customer information when the customer logs in and views several different pages or checks out. - -![Frontend data access points](frontend-data-access-points.svg) - -### Backend data entry points - -A merchant can enter customer, address, and payment information when using Admin to create a customer or order. - -![Backend data entry points](backend-data-entry-points.svg) - -### Backend data access points - -Magento 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](backend-data-access-points.svg) - -## Database entities - -Magento 1 stores customer information in customer, sales, and other database tables. - -### Customer data {#customer-data} - -Magento 1 stores customer information in the `customer_entity` and `customer_address_entity` tables. Both of these tables have several reference tables that can contain custom customer attributes. - -#### `customer_entity` and reference tables - -The following columns in the `customer_entity`table contain customer information: - -Column | Data type ---- | --- -`email` | varchar(255) - -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_address_entity` and reference tables - -The following 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_flat_order` and related tables contain the customer's name, billing and shipping addresses, and related information. - -#### `sales_flat_order` table - -The following columns in the `sales_order` table contain customer information: - -Column | Data type ---- | --- -`customer_id` | int(10) -`customer_email` | varchar(128) -`customer_firstname` | varchar(128) -`customer_gender` | int(11) -`customer_lastname` | varchar(128) -`customer_middlename` | varchar(128) -`customer_prefix` | varchar(32) -`customer_suffix` | varchar(32) -`customer_taxvat` | varchar(32) -`remote_ip` | varchar(32) - -#### `sales_flat_order_address` table - -The `sales_flat_order_address` table contains the customer's address. - -Column | Data type ---- | --- -`customer_id` | int(10) -`fax` | varchar(255) -`region` | varchar(255) -`postcode` | varchar(255) -`lastname` | varchar(255) -`street` | varchar(255) -`city` | varchar(255) -`email` | varchar(255) -`telephone` | varchar(255) -`firstname` | varchar(255) -`prefix` | varchar(255) -`suffix` | varchar(255) -`middlename` | varchar(255) -`company` | varchar(255) -`vat_id`| text - -#### `sales_flat_order_grid` table - -The following columns in the `sales_flat_order_grid` table contain customer information: - -Column | Data type ---- | --- -`customer_id` | int(10) -`shipping_name` | varchar(255) -`billing_name` | varchar(255) - -#### `sales_flat_order_payment` table - -The following columns in the `sales_flat_order_payment` table contain customer information: - -Column | Data type ---- | --- -`cc_exp_month` | varchar(255) -`cc_ss_start_year` | varchar(255) -`echeck_bank_name` | varchar(128) -`echeck_type` | varchar(255) -`cc_ss_start_month` | varchar(255) -`cc_owner` | varchar(255) -`cc_exp_year` | varchar(255) -`echeck_routing_number` | varchar(255) -`echeck_account_name` | varchar(255) - -### Quote data - -Quotes contain a customer's name, email, address, and related information. - -#### `sales_flat_quote` table - -The following columns in the `sales_flat_quote` table contain customer information: - -Column | Data type ---- | --- -`customer_id` | int(10) -`customer_tax_class_id` | int(10) -`customer_group_id` | int(10) -`customer_email` | varchar(255) -`customer_prefix` | varchar(40) -`customer_firstname` | varchar(255) -`customer_middlename` | varchar(40) -`customer_lastname` | varchar(255) -`customer_suffix` | varchar(40) -`customer_dob` | datetime -`customer_note` | varchar(255) -`remote_ip` | varchar(255) -`customer_gender` | varchar(255) - -#### `sales_flat_quote_address` table - -The following columns in the `sales_flat_quote_address` table contain customer information: - -Column | Data type ---- | --- -`email` | varchar(255) -`prefix` | varchar(40) -`firstname` | varchar(255) -`middlename` | varchar(40) -`lastname` | varchar(255) -`suffix` | varchar(40) -`company` | varchar(255) -`street` | varchar(255) -`city` | varchar(255) -`region` | varchar(255) -`postcode` | varchar(255) -`fax` | varchar(255) - -#### `sales_flat_quote_payment` table - -The `sales_flat_quote_payment` table includes credit card information and other transactional information. - -Column | Data type ---- | --- -`cc_last_4` | varchar(255) -`cc_owner` | varchar(255) -`cc_exp_month` | smallint(5) -`cc_exp_year` | smallint(5) -`cc_ss_owner` | varchar(255) -`cc_ss_start_month` | smallint(5) -`cc_ss_start_year` | smallint(5) - -### Archive data - -The following tables and columns contain customer information: - -Table | Column | Data type ---- | --- | --- -`enterprise_sales_creditmemo_grid_archive` | `billing_name` | varchar(255) -`enterprise_sales_invoice_grid_archive` | `billing_name` | varchar(255) -`enterprise_sales_order_grid_archive` | `billing_name` | varchar(255) -`enterprise_sales_order_grid_archive` | `customer_id` | int(10) -`enterprise_sales_order_grid_archive` | `shipping_name` | varchar(255) -`enterprise_sales_shipment_grid_archive` | `shipping_name` | varchar(255) - -### Sales data - -The following tables and columns contain customer information: - -Table | Column | Data type ---- | --- | --- -`sales_flat_creditmemo_grid` | `billing_name` | varchar(255) -`sales_flat_invoice_grid` | `billing_name` | varchar(255) - -### RMA data - -The following RMA tables and columns contain customer information: - -Table | Column | Data type ---- | --- | --- -`enterprise_rma` | `customer_custom_email` | varchar(255) -`enterprise_rma_grid` | `customer_id` | int(10) -`enterprise_rma_grid` | `customer_name` | varchar(255) - -### Miscellaneous data - -The following tables and columns contain customer information: - -Table | Column | Data type ---- | --- | --- -`core_email_queue_recipients` | `recipient_email` | varchar(128) -`core_email_queue_recipients` | `recipient_name` | varchar(255) -`customer_flowpassword` | `email` | varchar(255) -`customer_flowpassword` | `ip` | varchar(50) -`enterprise_giftregistry_person` | `email` | varchar(150) -`enterprise_giftregistry_person` | `firstname` | varchar(100) -`enterprise_giftregistry_person` | `lastname` | varchar(100) -`enterprise_giftregistry_person` | `middlename` | text -`enterprise_invitation` | `customer_id` | int(10) -`enterprise_invitation` | `email` | varchar(255) -`enterprise_invitation` | `referral_id` | int(10) -`enterprise_reminder_rule_coupon` | `customer_id` | int(10) -`enterprise_reminder_rule_coupon` | `emails_failed` | smallint(5) -`enterprise_scheduled_operations` | `email_receiver` | varchar(150) -`enterprise_scheduled_operations` | `email_sender` | varchar(150) -`gift_message` | `customer_id` | int(10) -`gift_message` | `recipient` | varchar(255) -`gift_message` | `sender` | varchar(255) -`newsletter_subscriber` | `customer_id` | int(10) -`newsletter_subscriber` | `subscriber_email` | varchar(150) -`persistent_session` | `customer_id` | int(10) -`persistent_session` | `info` | text -`poll_vote` | `customer_id` | int(10) -`poll_vote` | `ip_address` | varbinary(16) -`rating_option_vote` | `customer_id` | int(10) -`rating_option_vote` | `remote_ip` | varchar(50) -`rating_option_vote` | `remote_ip_long` | varbinary(516) -`send_friend_log` | `ip` | varbinary(16) - -Other tables that reference Customer: - -* `catalog_compare_item` -* `downloadable_link_purchased` -* `enterprise_customerbalance` -* `enterprise_customersegment_customer` -* `enterprise_giftregistry_entity` -* `enterprise_reminder_rule_log` -* `enterprise_reward` -* `log_customer` -* `log_visitor_online` -* `oauth_token` -* `product_alert_price` -* `product_alert_stock` -* `report_compared_product_index` -* `report_viewed_product_index` -* `review_detail` -* `sales_billing_agreement` -* `sales_flat_shipment` -* `sales_recurring_profile` -* `salesrule_coupon_usage` -* `salesrule_customer` -* `tag` -* `tag_relation` -* `wishlist` \ No newline at end of file diff --git a/src/guides/v2.2/architecture/gdpr/magento-2x.md b/src/guides/v2.2/architecture/gdpr/magento-2x.md deleted file mode 100644 index 2a9b98cfad3..00000000000 --- a/src/guides/v2.2/architecture/gdpr/magento-2x.md +++ /dev/null @@ -1,329 +0,0 @@ ---- -group: architecture-guide ---- - -# General Data Protection Regulation - -The European Union (EU) enacted [General Data Protection Regulation](https://www.eugdpr.org/) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. - -We are publishing this GDPR compliance information to help our merchants and their system integrators with GDPR compliance. A system integrator can use the data flow diagrams and database information to build scripts to resolve use cases similar to the following: - -* A shopper asks for a copy of the data the merchant has stored about her -* A shopper requests that all information about him be deleted - -See the corporate [Magento website](https://magento.com/gdpr) for more information about how Magento helps merchants comply with GDPR. - -## Data flow diagrams - -The data flow diagrams show the types of data that customers and administrators can enter and retrieve on the storefront and in 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-entry-points.svg) - -### Frontend data access points - -Magento loads customer information when the customer logs in and views several different pages or checks out. - -![Frontend data access points](frontend-data-access-points.svg) - -### Backend data entry points - -A merchant can enter customer information, address data, and payment data when using Admin to create a customer or order. - -![Backend data entry points](backend-data-entry-points.svg) - -### Backend data access points - -Magento 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](backend-data-access-points.svg) - -## Database entities - -Magento 2 primarily stores customer-specific information in customer, address, order, quote, and payment tables. Other tables contain references to the customer ID. - -### Customer data {#customer-data} - -Magento 2 stores these customer attributes: - -* Date of Birth -* Email -* First Name -* Gender -* Last Name -* Middle Name/Initial -* Name Prefix -* Name Suffix - -#### `customer_entity` and reference tables - -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 - -Magento 2 stores these 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 reference tables - -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's 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` | varchar(32) -`quote_address_id` | int(11) -`remote_ip` | varchar(32) -`x_forwarded_for` | varchar(32) - -#### `sales_order_address` table - -The `sales_order_address` table contains the customer's address. - -Column | Data type ---- | --- -`customer_address_id` | int(11) -`quote_address_id` | int(11) -`region_id` | int(11) -`customer_id` | int(11) -`fax` | varchar(255) -`region` | varchar(255) -`postcode` | varchar(255) -`lastname` | varchar(255) -`street` | varchar(255) -`city` | varchar(255) -`email` | varchar(255) -`telephone` | varchar(255) -`country_id` | varchar(2) -`firstname` | varchar(255) -`suffix` | varchar(255) -`company` | varchar(255) - -#### `sales_order_grid` table - -The following columns in the `sales_order_grid` table contain customer information: - -Column | Data type ---- | --- -`customer_id` | int(10) -`shipping_name` | varchar(255) -`billing_name` | varchar(255) -`billing_address` | varchar(255) -`shipping_address` | varchar(255) -`shipping_information` | varchar(255) -`customer_email` | varchar(255) -`customer_name` | varchar(255) - -### Quote data - -Quotes contain a customer's name, email, address, and related information. - -#### `quote` table - -The following columns in the `quote` table contain customer information: - -Column | Data type ---- | --- -`customer_id` | int(10) -`customer_email` | varchar(255) -`customer_prefix` | varchar(40) -`customer_firstname` | varchar(255) -`customer_middlename` | varchar(40) -`customer_lastname` | varchar(255) -`customer_dob` | datetime -`remote_ip` | varchar(32) -`customer_taxvat` | varchar(255) -`customer_gender` | varchar(255) - -#### `quote_address` table - -The following columns in the `quote_address` table contain customer information: - -Column | Data type ---- | --- -`customer_id` | int(10) -`email` | varchar(255) -`prefix` | varchar(40) -`firstname` | varchar(255) -`middlename` | varchar(40) -`lastname` | varchar(255) -`suffix` | varchar(40) -`company` | varchar(255) -`street` | varchar(255) -`city` | varchar(255) -`region` | varchar(255) -`region_id` | int(10) -`postcode` | varchar(20) -`country_id` | varchar(30) -`telephone` | varchar(255) -`fax` | varchar(255) - -### Payment data - -The `sales_order_payment` table includes credit card information and other transactional information. - -Column | Data type ---- | --- -`cc_exp_month` | varchar(12) -`echeck_bank_name` | varchar(128) -`cc_last_4` | varchar(100) -`cc_owner` | varchar(128) -`po_number` | varchar(32) -`cc_exp_year` | varchar(4) -`echeck_routing_number` | varchar(32) -`cc_debug_response_body` | varchar(32) -`echeck_account_name` | varchar(32) -`cc_number_enc` | varchar(128) -`additional_information` | text - -### Invitation data - -Magento can be configured so that customers can send invitations to private sales and events. - -#### `magento_invitation` table - -The `magento_invitation` table contains the customer ID, email, and referral ID. - -Column | Data type ---- | --- -`customer_id` | int(10) -`email` | varchar(255) -`referral_id` | int(10) - -#### `magento_invitation_track` table - -The `magento_invitation_track` table also contains customer information. - -Column | Data type ---- | --- -`inviter_id` | int(10) -`referral_id` | int(10) - -### Miscellaneous tables that reference customer - -The following tables contain a `customer_id` column: - -* `catalog_compare_item` -* `catalog_product_frontend_action` -* `downloadable_link_purchased` -* `magento_customerbalance` -* `magento_customersegment_customer` -* `magento_reward` -* `magento_rma` -* `oauth_token` -* `paypal_billing_agreement` -* `persistent_session` -* `product_alert_price` -* `product_stock_alert` -* `report_compared_product_index` -* `report_viewed_product_index` -* `review_detail` -* `salesrule_coupon_usage` -* `salesrule_customer` -* `wishlist` \ No newline at end of file diff --git a/src/guides/v2.3/architecture/gdpr/magento-1x.md b/src/guides/v2.3/architecture/gdpr/magento-1x.md deleted file mode 120000 index b55b70c1059..00000000000 --- a/src/guides/v2.3/architecture/gdpr/magento-1x.md +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/magento-1x.md \ No newline at end of file diff --git a/src/guides/v2.3/architecture/gdpr/magento-2x.md b/src/guides/v2.3/architecture/gdpr/magento-2x.md deleted file mode 120000 index f48fdd9c59a..00000000000 --- a/src/guides/v2.3/architecture/gdpr/magento-2x.md +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/magento-2x.md \ No newline at end of file From c3597c7edb050d59d3da0955e46f18c8636c89b5 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 12:12:18 -0800 Subject: [PATCH 25/54] Deleted images These images were moved to compliance/privacy --- src/guides/v2.3/architecture/gdpr/backend-data-access-points.svg | 1 - src/guides/v2.3/architecture/gdpr/backend-data-entry-points.svg | 1 - .../v2.3/architecture/gdpr/frontend-data-access-points.svg | 1 - src/guides/v2.3/architecture/gdpr/frontend-data-entry-points.svg | 1 - 4 files changed, 4 deletions(-) delete mode 120000 src/guides/v2.3/architecture/gdpr/backend-data-access-points.svg delete mode 120000 src/guides/v2.3/architecture/gdpr/backend-data-entry-points.svg delete mode 120000 src/guides/v2.3/architecture/gdpr/frontend-data-access-points.svg delete mode 120000 src/guides/v2.3/architecture/gdpr/frontend-data-entry-points.svg diff --git a/src/guides/v2.3/architecture/gdpr/backend-data-access-points.svg b/src/guides/v2.3/architecture/gdpr/backend-data-access-points.svg deleted file mode 120000 index 41a13ad2cba..00000000000 --- a/src/guides/v2.3/architecture/gdpr/backend-data-access-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/backend-data-access-points.svg \ No newline at end of file diff --git a/src/guides/v2.3/architecture/gdpr/backend-data-entry-points.svg b/src/guides/v2.3/architecture/gdpr/backend-data-entry-points.svg deleted file mode 120000 index 53b057f3ad4..00000000000 --- a/src/guides/v2.3/architecture/gdpr/backend-data-entry-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/backend-data-entry-points.svg \ No newline at end of file diff --git a/src/guides/v2.3/architecture/gdpr/frontend-data-access-points.svg b/src/guides/v2.3/architecture/gdpr/frontend-data-access-points.svg deleted file mode 120000 index 882dbebb7a7..00000000000 --- a/src/guides/v2.3/architecture/gdpr/frontend-data-access-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/frontend-data-access-points.svg \ No newline at end of file diff --git a/src/guides/v2.3/architecture/gdpr/frontend-data-entry-points.svg b/src/guides/v2.3/architecture/gdpr/frontend-data-entry-points.svg deleted file mode 120000 index 171a28942b6..00000000000 --- a/src/guides/v2.3/architecture/gdpr/frontend-data-entry-points.svg +++ /dev/null @@ -1 +0,0 @@ -../../../../guides/v2.2/architecture/gdpr/frontend-data-entry-points.svg \ No newline at end of file From 8b18fb129e552357119a838d1d6cae1bd14c80bb Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 13:17:38 -0800 Subject: [PATCH 26/54] Removed spaces cleaned up --- src/compliance/industry-compliance.md | 4 +- src/compliance/privacy/ccpa.md | 16 ++-- src/compliance/privacy/gdpr.md | 20 ++--- .../privacy/pi-data-reference-m1.md | 52 +++++------ .../privacy/pi-data-reference-m2.md | 88 +++++++++---------- 5 files changed, 90 insertions(+), 90 deletions(-) diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md index 5ce6651031f..539e202d551 100644 --- a/src/compliance/industry-compliance.md +++ b/src/compliance/industry-compliance.md @@ -7,5 +7,5 @@ Merchants are obligated to meet industry guidelines for maintaining a secure env The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific privacy legislation. Some of the recent privacy regulations require additional development effort on the part of the merchant. See the following topics for the technical information you need to support your clients who have Magento installations. -- [California Consumer Privacy Act (CCPA)]({% link compliance/privacy/ccpa.md %}) -- [General Data Protection Regulation (GDPR)]({% link compliance/privacy/gdpr.md %}) +-[California Consumer Privacy Act (CCPA)]({% link compliance/privacy/ccpa.md %}) +-[General Data Protection Regulation (GDPR)]({% link compliance/privacy/gdpr.md %}) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index ff3ec5f26a0..5765c01bfaa 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -3,14 +3,14 @@ group: compliance title: California Consumer Privacy Act --- -The [California Consumer Protection Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. +The [California Consumer Protection Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. The CCPA grants the following new rights to consumers: -- **Right to know** the categories of personal information about them that is collected, used, shared, or sold in the past 12 months. -- **Right to delete** certain types of personal information that is held by a business and/or their service provider(s). -- **Right to opt out** of the sale of their personal information. -- **Right to non-discrimination** in terms of price or service for having exercised a privacy right under CCPA. +-**Right to know** the categories of personal information about them that is collected, used, shared, or sold in the past 12 months. +-**Right to delete** certain types of personal information that is held by a business and/or their service provider(s). +-**Right to opt out** of the sale of their personal information. +-**Right to non-discrimination** in terms of price or service for having exercised a privacy right under CCPA. ## CCPA Compliance Guide @@ -36,8 +36,8 @@ A coordinated effort is required to develop and implement a plan to address CCPA For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) -- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +-[Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +-[Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) -[1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act +[1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act [2]: https://docs.magento.com/m2/ee/user_guide/stores/compliance-ccpa-guide.html diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index 74d9c7f0b2a..a1381f81794 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -1,28 +1,28 @@ --- group: compliance title: General Data Protection Regulation -redirect_from: +redirect_from: - /guides/v2.3/architecture/gdpr/magento-2x.html - - /guides/v2.3/architecture/gdpr/magento-1x.html + - /guides/v2.3/architecture/gdpr/magento-1x.html - /guides/v2.2/architecture/gdpr/magento-2x.html - - /guides/v2.2/architecture/gdpr/magento-1x.html + - /guides/v2.2/architecture/gdpr/magento-1x.html --- The European Union (EU) enacted [General Data Protection Regulation](https://ec.europa.eu/info/law/law-topic/data-protection_en) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. System integrators can use the data flow diagrams and database information in the Personal Information Reference to build scripts to resolve use cases similar to the following: -* A shopper asks for a copy of the data the merchant has stored about her -* A shopper requests that all information about him be deleted +-A shopper asks for a copy of the data the merchant has stored about her +-A shopper requests that all information about him be deleted ## Personal Information Reference -For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. +For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) -- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +-[Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +-[Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) For more information about how Magento helps merchants comply with GDPR, see the following: -- [GDPR Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html) -- [Magento is Ready for GDPR](https://magento.com/gdpr) +-[GDPR Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html) +-[Magento is Ready for GDPR](https://magento.com/gdpr) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index 2f97ff46dcf..3fc1ebc73ae 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -1,12 +1,12 @@ --- group: compliance -title: Personal Information Reference (Magento 1.x) +title: Personal Information Reference (Magento 1.x) --- Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: -- [GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) -- [CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) +-[GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) +-[CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) ## Dataflow diagrams @@ -269,26 +269,26 @@ Table | Column | Data type Other tables that reference Customer: -- `catalog_compare_item` -- `downloadable_link_purchased` -- `enterprise_customerbalance` -- `enterprise_customersegment_customer` -- `enterprise_giftregistry_entity` -- `enterprise_reminder_rule_log` -- `enterprise_reward` -- `log_customer` -- `log_visitor_online` -- `oauth_token` -- `product_alert_price` -- `product_alert_stock` -- `report_compared_product_index` -- `report_viewed_product_index` -- `review_detail` -- `sales_billing_agreement` -- `sales_flat_shipment` -- `sales_recurring_profile` -- `salesrule_coupon_usage` -- `salesrule_customer` -- `tag` -- `tag_relation` -- `wishlist` +-`catalog_compare_item` +-`downloadable_link_purchased` +-`enterprise_customerbalance` +-`enterprise_customersegment_customer` +-`enterprise_giftregistry_entity` +-`enterprise_reminder_rule_log` +-`enterprise_reward` +-`log_customer` +-`log_visitor_online` +-`oauth_token` +-`product_alert_price` +-`product_alert_stock` +-`report_compared_product_index` +-`report_viewed_product_index` +-`review_detail` +-`sales_billing_agreement` +-`sales_flat_shipment` +-`sales_recurring_profile` +-`salesrule_coupon_usage` +-`salesrule_customer` +-`tag` +-`tag_relation` +-`wishlist` diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index 01533568e73..e340c050612 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -1,12 +1,12 @@ --- group: compliance -title: Personal Information Reference (Magento 2.x) +title: Personal Information Reference (Magento 2.x) --- Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: -- [GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) -- [CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) +-[GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) +-[CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) ## Data flow diagrams @@ -44,14 +44,14 @@ Magento 2 primarily stores customer-specific information in customer, address, o Magento 2 stores the following customer attributes: -- Date of Birth -- Email -- First Name -- Gender -- Last Name -- Middle Name/Initial -- Name Prefix -- Name Suffix +-Date of Birth +-Email +-First Name +-Gender +-Last Name +-Middle Name/Initial +-Name Prefix +-Name Suffix #### `customer_entity` and reference tables @@ -105,21 +105,21 @@ Column | Data type Magento 2 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 +-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 reference tables @@ -304,21 +304,21 @@ Column | Data type The following tables contain a `customer_id` column: -- `catalog_compare_item` -- `catalog_product_frontend_action` -- `downloadable_link_purchased` -- `magento_customerbalance` -- `magento_customersegment_customer` -- `magento_reward` -- `magento_rma` -- `oauth_token` -- `paypal_billing_agreement` -- `persistent_session` -- `product_alert_price` -- `product_stock_alert` -- `report_compared_product_index` -- `report_viewed_product_index` -- `review_detail` -- `salesrule_coupon_usage` -- `salesrule_customer` -- `wishlist` +-`catalog_compare_item` +-`catalog_product_frontend_action` +-`downloadable_link_purchased` +-`magento_customerbalance` +-`magento_customersegment_customer` +-`magento_reward` +-`magento_rma` +-`oauth_token` +-`paypal_billing_agreement` +-`persistent_session` +-`product_alert_price` +-`product_stock_alert` +-`report_compared_product_index` +-`report_viewed_product_index` +-`review_detail` +-`salesrule_coupon_usage` +-`salesrule_customer` +-`wishlist` From 037d88bb7d210a6c91cce0103607d3b1cabd550b Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 14:02:03 -0800 Subject: [PATCH 27/54] Update ccpa.md Removed space. --- src/compliance/privacy/ccpa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 5765c01bfaa..903d5882650 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -34,7 +34,7 @@ A coordinated effort is required to develop and implement a plan to address CCPA ## Personal Information Reference -For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. +For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -[Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) -[Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) From d50e9981cf37d3942c07ac1fed9efdd022c75e97 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 14:50:44 -0800 Subject: [PATCH 28/54] Corrected link syntax Removed site.baseurl syntax --- .../privacy/pi-data-reference-m1.md | 4 +- .../privacy/pi-data-reference-m2.md | 312 +++++++++--------- 2 files changed, 158 insertions(+), 158 deletions(-) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index 3fc1ebc73ae..e8cecc6f10c 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -5,8 +5,8 @@ title: Personal Information Reference (Magento 1.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: --[GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) --[CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) +-[GDPR]({% link compliance/privacy/gdpr.md -%}) +-[CCPA]({% link compliance/privacy/ccpa.md -%}) ## Dataflow diagrams diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index e340c050612..3622cd21ec6 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -5,8 +5,8 @@ title: Personal Information Reference (Magento 2.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: --[GDPR]({{ site.baseurl }}{% link compliance/privacy/gdpr.md %}) --[CCPA]({{ site.baseurl }}{% link compliance/privacy/ccpa.md %}) +-[GDPR]({% link compliance/privacy/gdpr.md -%}) +-[CCPA]({% link compliance/privacy/ccpa.md -%}) ## Data flow diagrams @@ -57,49 +57,49 @@ Magento 2 stores the following customer attributes: 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) +| 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) +| 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) +| 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 @@ -125,32 +125,32 @@ Magento 2 stores the following customer attributes: 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) +| 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) +| 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 @@ -160,60 +160,60 @@ The `sales_order` and related tables contain the customer's name, billing and sh 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` | varchar(32) -`quote_address_id` | int(11) -`remote_ip` | varchar(32) -`x_forwarded_for` | varchar(32) +| 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` | varchar(32) | +| `quote_address_id` | int(11) | +| `remote_ip` | varchar(32) | +| `x_forwarded_for` | varchar(32) | #### `sales_order_address` table The `sales_order_address` table contains the customer's address. -Column | Data type ---- | --- -`customer_address_id` | int(11) -`quote_address_id` | int(11) -`region_id` | int(11) -`customer_id` | int(11) -`fax` | varchar(255) -`region` | varchar(255) -`postcode` | varchar(255) -`lastname` | varchar(255) -`street` | varchar(255) -`city` | varchar(255) -`email` | varchar(255) -`telephone` | varchar(255) -`country_id` | varchar(2) -`firstname` | varchar(255) -`suffix` | varchar(255) -`company` | varchar(255) +| Column | Data type | +| --------------------- | ------------ | +| `customer_address_id` | int(11) | +| `quote_address_id` | int(11) | +| `region_id` | int(11) | +| `customer_id` | int(11) | +| `fax` | varchar(255) | +| `region` | varchar(255) | +| `postcode` | varchar(255) | +| `lastname` | varchar(255) | +| `street` | varchar(255) | +| `city` | varchar(255) | +| `email` | varchar(255) | +| `telephone` | varchar(255) | +| `country_id` | varchar(2) | +| `firstname` | varchar(255) | +| `suffix` | varchar(255) | +| `company` | varchar(255) | #### `sales_order_grid` table The following columns in the `sales_order_grid` table contain customer information: -Column | Data type ---- | --- -`customer_id` | int(10) -`shipping_name` | varchar(255) -`billing_name` | varchar(255) -`billing_address` | varchar(255) -`shipping_address` | varchar(255) -`shipping_information` | varchar(255) -`customer_email` | varchar(255) -`customer_name` | varchar(255) +| Column | Data type | +| ---------------------- | ------------ | +| `customer_id` | int(10) | +| `shipping_name` | varchar(255) | +| `billing_name` | varchar(255) | +| `billing_address` | varchar(255) | +| `shipping_address` | varchar(255) | +| `shipping_information` | varchar(255) | +| `customer_email` | varchar(255) | +| `customer_name` | varchar(255) | ### Quote data @@ -223,59 +223,59 @@ Quotes contain a customer's name, email, address, and related information. The following columns in the `quote` table contain customer information: -Column | Data type ---- | --- -`customer_id` | int(10) -`customer_email` | varchar(255) -`customer_prefix` | varchar(40) -`customer_firstname` | varchar(255) -`customer_middlename` | varchar(40) -`customer_lastname` | varchar(255) -`customer_dob` | datetime -`remote_ip` | varchar(32) -`customer_taxvat` | varchar(255) -`customer_gender` | varchar(255) +| Column | Data type | +| --------------------- | ------------ | +| `customer_id` | int(10) | +| `customer_email` | varchar(255) | +| `customer_prefix` | varchar(40) | +| `customer_firstname` | varchar(255) | +| `customer_middlename` | varchar(40) | +| `customer_lastname` | varchar(255) | +| `customer_dob` | datetime | +| `remote_ip` | varchar(32) | +| `customer_taxvat` | varchar(255) | +| `customer_gender` | varchar(255) | #### `quote_address` table The following columns in the `quote_address` table contain customer information: -Column | Data type ---- | --- -`customer_id` | int(10) -`email` | varchar(255) -`prefix` | varchar(40) -`firstname` | varchar(255) -`middlename` | varchar(40) -`lastname` | varchar(255) -`suffix` | varchar(40) -`company` | varchar(255) -`street` | varchar(255) -`city` | varchar(255) -`region` | varchar(255) -`region_id` | int(10) -`postcode` | varchar(20) -`country_id` | varchar(30) -`telephone` | varchar(255) -`fax` | varchar(255) +| Column | Data type | +| ------------- | ------------ | +| `customer_id` | int(10) | +| `email` | varchar(255) | +| `prefix` | varchar(40) | +| `firstname` | varchar(255) | +| `middlename` | varchar(40) | +| `lastname` | varchar(255) | +| `suffix` | varchar(40) | +| `company` | varchar(255) | +| `street` | varchar(255) | +| `city` | varchar(255) | +| `region` | varchar(255) | +| `region_id` | int(10) | +| `postcode` | varchar(20) | +| `country_id` | varchar(30) | +| `telephone` | varchar(255) | +| `fax` | varchar(255) | ### Payment data The `sales_order_payment` table includes credit card information and other transactional information. -Column | Data type ---- | --- -`cc_exp_month` | varchar(12) -`echeck_bank_name` | varchar(128) -`cc_last_4` | varchar(100) -`cc_owner` | varchar(128) -`po_number` | varchar(32) -`cc_exp_year` | varchar(4) -`echeck_routing_number` | varchar(32) -`cc_debug_response_body` | varchar(32) -`echeck_account_name` | varchar(32) -`cc_number_enc` | varchar(128) -`additional_information` | text +| Column | Data type | +| ------------------------ | ------------ | +| `cc_exp_month` | varchar(12) | +| `echeck_bank_name` | varchar(128) | +| `cc_last_4` | varchar(100) | +| `cc_owner` | varchar(128) | +| `po_number` | varchar(32) | +| `cc_exp_year` | varchar(4) | +| `echeck_routing_number` | varchar(32) | +| `cc_debug_response_body` | varchar(32) | +| `echeck_account_name` | varchar(32) | +| `cc_number_enc` | varchar(128) | +| `additional_information` | text | ### Invitation data @@ -285,20 +285,20 @@ Magento can be configured so that customers can send invitations to private sale The `magento_invitation` table contains the customer ID, email, and referral ID. -Column | Data type ---- | --- -`customer_id` | int(10) -`email` | varchar(255) -`referral_id` | int(10) +| Column | Data type | +| ------------- | ------------ | +| `customer_id` | int(10) | +| `email` | varchar(255) | +| `referral_id` | int(10) | #### `magento_invitation_track` table The `magento_invitation_track` table also contains customer information. -Column | Data type ---- | --- -`inviter_id` | int(10) -`referral_id` | int(10) +| Column | Data type | +| ------------- | --------- | +| `inviter_id` | int(10) | +| `referral_id` | int(10) | ### Miscellaneous tables that reference customer From a107778a73f05a59830781eada59757556a7f8c6 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Tue, 10 Dec 2019 15:24:03 -0800 Subject: [PATCH 29/54] Fixed list syntax Added blank line after each bullted link. --- src/compliance/privacy/ccpa.md | 1 + src/compliance/privacy/gdpr.md | 2 ++ src/compliance/privacy/pi-data-reference-m1.md | 1 + 3 files changed, 4 insertions(+) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 903d5882650..ec42154d8b6 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -37,6 +37,7 @@ A coordinated effort is required to develop and implement a plan to address CCPA For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -[Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) + -[Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) [1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index a1381f81794..d1adacb3d7f 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -20,9 +20,11 @@ System integrators can use the data flow diagrams and database information in th For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -[Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) + -[Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) For more information about how Magento helps merchants comply with GDPR, see the following: -[GDPR Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html) + -[Magento is Ready for GDPR](https://magento.com/gdpr) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index e8cecc6f10c..eeaed98f3e0 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -6,6 +6,7 @@ title: Personal Information Reference (Magento 1.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: -[GDPR]({% link compliance/privacy/gdpr.md -%}) + -[CCPA]({% link compliance/privacy/ccpa.md -%}) ## Dataflow diagrams From 9ae3505492b1a96e1ab3d35da2e7808b9fa9a2f3 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Wed, 11 Dec 2019 07:36:28 -0800 Subject: [PATCH 30/54] Fixed Spacing Restored correct spacing to list markers --- src/compliance/industry-compliance.md | 4 +- src/compliance/privacy/ccpa.md | 13 ++- src/compliance/privacy/gdpr.md | 14 ++- .../privacy/pi-data-reference-m1.md | 51 ++++++----- .../privacy/pi-data-reference-m2.md | 86 +++++++++---------- 5 files changed, 82 insertions(+), 86 deletions(-) diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md index 539e202d551..10b634a5514 100644 --- a/src/compliance/industry-compliance.md +++ b/src/compliance/industry-compliance.md @@ -7,5 +7,5 @@ Merchants are obligated to meet industry guidelines for maintaining a secure env The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific privacy legislation. Some of the recent privacy regulations require additional development effort on the part of the merchant. See the following topics for the technical information you need to support your clients who have Magento installations. --[California Consumer Privacy Act (CCPA)]({% link compliance/privacy/ccpa.md %}) --[General Data Protection Regulation (GDPR)]({% link compliance/privacy/gdpr.md %}) +- [California Consumer Privacy Act (CCPA)]({% link compliance/privacy/ccpa.md %}) +- [General Data Protection Regulation (GDPR)]({% link compliance/privacy/gdpr.md %}) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index ec42154d8b6..a2ad3db7078 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -7,10 +7,10 @@ The [California Consumer Protection Act][1]{: target="_blank"} (CCPA) expands th The CCPA grants the following new rights to consumers: --**Right to know** the categories of personal information about them that is collected, used, shared, or sold in the past 12 months. --**Right to delete** certain types of personal information that is held by a business and/or their service provider(s). --**Right to opt out** of the sale of their personal information. --**Right to non-discrimination** in terms of price or service for having exercised a privacy right under CCPA. +- **Right to know** the categories of personal information about them that is collected, used, shared, or sold in the past 12 months. +- **Right to delete** certain types of personal information that is held by a business and/or their service provider(s). +- **Right to opt out** of the sale of their personal information. +- **Right to non-discrimination** in terms of price or service for having exercised a privacy right under CCPA. ## CCPA Compliance Guide @@ -36,9 +36,8 @@ A coordinated effort is required to develop and implement a plan to address CCPA For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. --[Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) - --[Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) [1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act [2]: https://docs.magento.com/m2/ee/user_guide/stores/compliance-ccpa-guide.html diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index d1adacb3d7f..c829ac572b2 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -12,19 +12,17 @@ The European Union (EU) enacted [General Data Protection Regulation](https://ec. System integrators can use the data flow diagrams and database information in the Personal Information Reference to build scripts to resolve use cases similar to the following: --A shopper asks for a copy of the data the merchant has stored about her --A shopper requests that all information about him be deleted +- A shopper asks for a copy of the data the merchant has stored about her +- A shopper requests that all information about him be deleted ## Personal Information Reference For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. --[Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) - --[Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) For more information about how Magento helps merchants comply with GDPR, see the following: --[GDPR Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html) - --[Magento is Ready for GDPR](https://magento.com/gdpr) +- [GDPR Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-gdpr.html) +- [Magento is Ready for GDPR](https://magento.com/gdpr) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index eeaed98f3e0..b27fea93c0b 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -5,9 +5,8 @@ title: Personal Information Reference (Magento 1.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: --[GDPR]({% link compliance/privacy/gdpr.md -%}) - --[CCPA]({% link compliance/privacy/ccpa.md -%}) +- [GDPR]({% link compliance/privacy/gdpr.md -%}) +- [CCPA]({% link compliance/privacy/ccpa.md -%}) ## Dataflow diagrams @@ -270,26 +269,26 @@ Table | Column | Data type Other tables that reference Customer: --`catalog_compare_item` --`downloadable_link_purchased` --`enterprise_customerbalance` --`enterprise_customersegment_customer` --`enterprise_giftregistry_entity` --`enterprise_reminder_rule_log` --`enterprise_reward` --`log_customer` --`log_visitor_online` --`oauth_token` --`product_alert_price` --`product_alert_stock` --`report_compared_product_index` --`report_viewed_product_index` --`review_detail` --`sales_billing_agreement` --`sales_flat_shipment` --`sales_recurring_profile` --`salesrule_coupon_usage` --`salesrule_customer` --`tag` --`tag_relation` --`wishlist` +- `catalog_compare_item` +- `downloadable_link_purchased` +- `enterprise_customerbalance` +- `enterprise_customersegment_customer` +- `enterprise_giftregistry_entity` +- `enterprise_reminder_rule_log` +- `enterprise_reward` +- `log_customer` +- `log_visitor_online` +- `oauth_token` +- `product_alert_price` +- `product_alert_stock` +- `report_compared_product_index` +- `report_viewed_product_index` +- `review_detail` +- `sales_billing_agreement` +- `sales_flat_shipment` +- `sales_recurring_profile` +- `salesrule_coupon_usage` +- `salesrule_customer` +- `tag` +- `tag_relation` +- `wishlist` diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index 3622cd21ec6..77064803d51 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -5,8 +5,8 @@ title: Personal Information Reference (Magento 2.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: --[GDPR]({% link compliance/privacy/gdpr.md -%}) --[CCPA]({% link compliance/privacy/ccpa.md -%}) +- [GDPR]({% link compliance/privacy/gdpr.md -%}) +- [CCPA]({% link compliance/privacy/ccpa.md -%}) ## Data flow diagrams @@ -44,14 +44,14 @@ Magento 2 primarily stores customer-specific information in customer, address, o Magento 2 stores the following customer attributes: --Date of Birth --Email --First Name --Gender --Last Name --Middle Name/Initial --Name Prefix --Name Suffix +- Date of Birth +- Email +- First Name +- Gender +- Last Name +- Middle Name/Initial +- Name Prefix +- Name Suffix #### `customer_entity` and reference tables @@ -105,21 +105,21 @@ The following columns in the `customer_grid_flat` table contain customer informa Magento 2 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 +- 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 reference tables @@ -304,21 +304,21 @@ The `magento_invitation_track` table also contains customer information. The following tables contain a `customer_id` column: --`catalog_compare_item` --`catalog_product_frontend_action` --`downloadable_link_purchased` --`magento_customerbalance` --`magento_customersegment_customer` --`magento_reward` --`magento_rma` --`oauth_token` --`paypal_billing_agreement` --`persistent_session` --`product_alert_price` --`product_stock_alert` --`report_compared_product_index` --`report_viewed_product_index` --`review_detail` --`salesrule_coupon_usage` --`salesrule_customer` --`wishlist` +- `catalog_compare_item` +- `catalog_product_frontend_action` +- `downloadable_link_purchased` +- `magento_customerbalance` +- `magento_customersegment_customer` +- `magento_reward` +- `magento_rma` +- `oauth_token` +- `paypal_billing_agreement` +- `persistent_session` +- `product_alert_price` +- `product_stock_alert` +- `report_compared_product_index` +- `report_viewed_product_index` +- `review_detail` +- `salesrule_coupon_usage` +- `salesrule_customer` +- `wishlist` From 02d786f12c3eb19bb8111b18929428ff23a6ba9e Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 08:28:04 -0800 Subject: [PATCH 31/54] Update src/compliance/privacy/ccpa.md Co-Authored-By: Jeff Matthews --- src/compliance/privacy/ccpa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index a2ad3db7078..35ca2e462d8 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -37,7 +37,7 @@ A coordinated effort is required to develop and implement a plan to address CCPA For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. - [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) -- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +- [Personal Information Reference (Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md %}) [1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act [2]: https://docs.magento.com/m2/ee/user_guide/stores/compliance-ccpa-guide.html From 1984a214a6cac230194ec3378d5d3d942eccfae5 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 08:30:26 -0800 Subject: [PATCH 32/54] Update compliance.yml Added "versionless: true", corrected paths --- src/_data/toc/compliance.yml | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index e3794788d28..c088def8664 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -1,20 +1,27 @@ label: Compliance pages: - label: Industry Compliance - url: ../../../compliance/industry-compliance.html + url: compliance/industry-compliance.html + versionless: true children: - label: Privacy Regulations + versionless: true + children: - label: CCPA - url: ../../../compliance/privacy/ccpa.html + versionless: true + url: compliance/privacy/ccpa.html - label: GDPR - url: ../../../compliance/privacy/gdpr.html + versionless: true + url: compliance/privacy/gdpr.html - label: PI Reference (M2.x) - url: ../../../compliance/privacy/pi-data-reference-m2.html + versionless: true + url: compliance/privacy/pi-data-reference-m2.html - label: PI Reference (M1.x) - url: ../../../compliance/privacy/pi-data-reference-m1.html + versionless: true + url: compliance/privacy/pi-data-reference-m1.html From ca1d7458e561c8e32ed92f06fa5edc77c32658f4 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 08:32:07 -0800 Subject: [PATCH 33/54] Update ccpa.md Removed hyphen at end of link "-%})" --- src/compliance/privacy/ccpa.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index a2ad3db7078..d249c595d17 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -36,8 +36,8 @@ A coordinated effort is required to develop and implement a plan to address CCPA For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) -- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md %}) +- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md %}) [1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act [2]: https://docs.magento.com/m2/ee/user_guide/stores/compliance-ccpa-guide.html From 8a59a272e30a600b9e63f6ebeccdd72f2d188e66 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 08:34:02 -0800 Subject: [PATCH 34/54] Update src/compliance/privacy/ccpa.md Co-Authored-By: Jeff Matthews --- src/compliance/privacy/ccpa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 35ca2e462d8..c23cf91ec49 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -36,7 +36,7 @@ A coordinated effort is required to develop and implement a plan to address CCPA For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. -- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md %}) - [Personal Information Reference (Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md %}) [1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act From 1f3c5a4f432cffb755fd15ce41bf9affcdf6968c Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 09:10:41 -0800 Subject: [PATCH 35/54] Update ccpa.md Reworked opening paragraph; added link to second reference to CCPA Compliance Guide; removed unnecessary hyphen from link syntax. --- src/compliance/privacy/ccpa.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index cab9463d664..33dc1277495 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -14,7 +14,7 @@ The CCPA grants the following new rights to consumers: ## CCPA Compliance Guide -A coordinated effort is required to develop and implement a plan to address CCPA compliance. Merchants are encouraged to assemble a cross-functional team, and follow the roadmap outlined in [CCPA Compliance Guide][2]{: target="_blank"} to bring their company into compliance with the regulation. As a developer, you might be invited to participate as a stakeholder with an emphasis on steps 2 - 5 of the process. See the CCPA Compliance Guide for more information. +Developing and implementing a CCPA compliance plan requires a coordinated effort. We encourage merchants to assemble a cross-functional team, and follow the roadmap outlined in [CCPA Compliance Guide][2]{: target="_blank"} to bring their company into compliance with the regulation. As a developer, you might be invited to participate as a stakeholder with an emphasis on steps 2 - 5 of the process. See the [CCPA Compliance Guide][2]{: target="_blank"} for more information. 1. Assemble a cross-functional team to address CCPA compliance. @@ -34,7 +34,7 @@ A coordinated effort is required to develop and implement a plan to address CCPA ## Personal Information Reference -For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. +For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to each version of Magento that you support. - [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md %}) - [Personal Information Reference (Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md %}) From 2d6d7b4a6a0e515478feca9c5fc2f08800e571c5 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 09:11:59 -0800 Subject: [PATCH 36/54] Update gdpr.md Reworked sentence to remove "version(s)"; removed unnecessary hyphen from link syntax. --- src/compliance/privacy/gdpr.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index c829ac572b2..a683ebc174f 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -17,10 +17,10 @@ System integrators can use the data flow diagrams and database information in th ## Personal Information Reference -For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to the version(s) of Magento that you support. +For technical information, see the data flow diagrams and database entity mappings in the Personal Information Reference that applies to each version of Magento that you support. -- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md -%}) -- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md -%}) +- [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md %}) +- [Personal Information Reference Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md %}) For more information about how Magento helps merchants comply with GDPR, see the following: From 6a09d4939acf57b2129c1c7e228a211d6da249a7 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 09:12:19 -0800 Subject: [PATCH 37/54] Update pi-data-reference-m1.md Removed unnecessary hyphen from link syntax. --- src/compliance/privacy/pi-data-reference-m1.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index b27fea93c0b..54f87c0622b 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -5,8 +5,8 @@ title: Personal Information Reference (Magento 1.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: -- [GDPR]({% link compliance/privacy/gdpr.md -%}) -- [CCPA]({% link compliance/privacy/ccpa.md -%}) +- [GDPR]({% link compliance/privacy/gdpr.md %}) +- [CCPA]({% link compliance/privacy/ccpa.md %}) ## Dataflow diagrams From 7bd870ca7202338be9efee8c6236f7ce8dcc1368 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 09:16:09 -0800 Subject: [PATCH 38/54] Update pi-data-reference-m2.md Updated heading; changed customer's from possessive to singular. --- src/compliance/privacy/pi-data-reference-m2.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index 77064803d51..9e965bb80f0 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -5,8 +5,8 @@ title: Personal Information Reference (Magento 2.x) Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: -- [GDPR]({% link compliance/privacy/gdpr.md -%}) -- [CCPA]({% link compliance/privacy/ccpa.md -%}) +- [GDPR]({% link compliance/privacy/gdpr.md %}) +- [CCPA]({% link compliance/privacy/ccpa.md %}) ## Data flow diagrams @@ -53,7 +53,7 @@ Magento 2 stores the following customer attributes: - Name Prefix - Name Suffix -#### `customer_entity` and reference tables +#### `customer_entity` and 'customer_entity' references The following columns in the `customer_entity` table contain customer information: @@ -154,7 +154,7 @@ These tables reference `customer_address_entity` and can contain custom customer ### Order data -The `sales_order` and related tables contain the customer's name, billing and shipping addresses, and related data. +The `sales_order` and related tables contain the customer name, billing and shipping addresses, and related data. #### `sales_order` table From 1ad4428e7a647027ec0659ca2f13d1101e641198 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 10:53:49 -0800 Subject: [PATCH 39/54] Update compliance.yml removed unnecessary line. --- src/_data/toc/compliance.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index c088def8664..22308951c58 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -6,7 +6,6 @@ pages: children: - label: Privacy Regulations - versionless: true children: From 30c44b8faf59ba4da045120e4878a09cdd9a0139 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 11:56:06 -0800 Subject: [PATCH 40/54] Update compliance.yml added forward slash to fix path --- src/_data/toc/compliance.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index 22308951c58..25ac7b64093 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -1,7 +1,7 @@ label: Compliance pages: - label: Industry Compliance - url: compliance/industry-compliance.html + url: /compliance/industry-compliance.html versionless: true children: @@ -11,16 +11,16 @@ pages: - label: CCPA versionless: true - url: compliance/privacy/ccpa.html + url: /compliance/privacy/ccpa.html - label: GDPR versionless: true - url: compliance/privacy/gdpr.html + url: /compliance/privacy/gdpr.html - label: PI Reference (M2.x) versionless: true - url: compliance/privacy/pi-data-reference-m2.html + url: /compliance/privacy/pi-data-reference-m2.html - label: PI Reference (M1.x) versionless: true - url: compliance/privacy/pi-data-reference-m1.html + url: /compliance/privacy/pi-data-reference-m1.html From d1ae053778ae65f9d954ec719e515f2c554f0d4b Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 12:04:38 -0800 Subject: [PATCH 41/54] Update main-nav.yml Fixed path; added versionless=true --- src/_data/main-nav.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/_data/main-nav.yml b/src/_data/main-nav.yml index 60a330d1759..7f6026ba662 100644 --- a/src/_data/main-nav.yml +++ b/src/_data/main-nav.yml @@ -197,7 +197,8 @@ url: /howdoi/checkout/checkout_overview.html - label: Compliance - url: ../../../compliance/industry-compliance.html + url: /compliance/industry-compliance.html + versionless: true - label: Inventory Management url: /inventory/index.html From 37d06d58aaa73c64bd67043db5b0ab3bf93c185c Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Mon, 16 Dec 2019 13:47:25 -0800 Subject: [PATCH 42/54] Update ccpa.md Corrected link label and url. --- src/compliance/privacy/ccpa.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 33dc1277495..c48b2e6e491 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -3,7 +3,7 @@ group: compliance title: California Consumer Privacy Act --- -The [California Consumer Protection Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. +The [California Consumer Privacy Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. The CCPA grants the following new rights to consumers: @@ -39,5 +39,5 @@ For technical information, see the data flow diagrams and database entity mappin - [Personal Information Reference (Magento 2.x)]({% link compliance/privacy/pi-data-reference-m2.md %}) - [Personal Information Reference (Magento 1.x)]({% link compliance/privacy/pi-data-reference-m1.md %}) -[1]: https://en.wikipedia.org/wiki/Online_Privacy_Protection_Act +[1]: https://oag.ca.gov/privacy/ccpa [2]: https://docs.magento.com/m2/ee/user_guide/stores/compliance-ccpa-guide.html From fc7ed45acb0a6f291d416ccc9b82c084134a0810 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Wed, 18 Dec 2019 07:31:15 -0800 Subject: [PATCH 43/54] Updated callout Updated callouts for consistency with user guide. --- src/compliance/privacy/ccpa.md | 3 +++ src/compliance/privacy/gdpr.md | 3 +++ src/compliance/privacy/pi-data-reference-m1.md | 3 +++ src/compliance/privacy/pi-data-reference-m2.md | 3 +++ 4 files changed, 12 insertions(+) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index c48b2e6e491..28a0ad98cc3 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -3,6 +3,9 @@ group: compliance title: California Consumer Privacy Act --- +{: .bs-callout .bs-callout-info} +This is one in a series of topics to help Magento merchants and developers understand the implications of the California Consumer Privacy Act (CCPA). The information is intended for informational purposes only and should not be construed as legal advice. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. + The [California Consumer Privacy Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. The CCPA grants the following new rights to consumers: diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index a683ebc174f..169b0fda3fb 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -8,6 +8,9 @@ redirect_from: - /guides/v2.2/architecture/gdpr/magento-1x.html --- +{: .bs-callout .bs-callout-info} +This is one in a series of topics to help Magento merchants and developers understand the implications of the General Data Protection Regulation (GDPR). The information is intended for informational purposes only and should not be construed as legal advice. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. + The European Union (EU) enacted [General Data Protection Regulation](https://ec.europa.eu/info/law/law-topic/data-protection_en) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. System integrators can use the data flow diagrams and database information in the Personal Information Reference to build scripts to resolve use cases similar to the following: diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index 54f87c0622b..87c00d36260 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -3,6 +3,9 @@ group: compliance title: Personal Information Reference (Magento 1.x) --- +{: .bs-callout .bs-callout-info} +This is one in a series of topics to help Magento merchants and developers prepare for compliance with privacy regulations. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. + Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: - [GDPR]({% link compliance/privacy/gdpr.md %}) diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index 9e965bb80f0..eb080068cc1 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -3,6 +3,9 @@ group: compliance title: Personal Information Reference (Magento 2.x) --- +{: .bs-callout .bs-callout-info} +This is one in a series of topics to help Magento merchants and developers prepare for compliance with privacy regulations. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. + Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: - [GDPR]({% link compliance/privacy/gdpr.md %}) From 855ad7fea0d022009483a76466d24d5da14c445b Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Wed, 18 Dec 2019 09:37:25 -0800 Subject: [PATCH 44/54] Update industry-compliance.md Applied edits from review. --- src/compliance/industry-compliance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md index 10b634a5514..a74502f0b29 100644 --- a/src/compliance/industry-compliance.md +++ b/src/compliance/industry-compliance.md @@ -3,9 +3,9 @@ group: compliance title: Industry Compliance --- -Merchants are obligated to meet industry guidelines for maintaining a secure environment, legal requirements in their jurisdiction, and best practices for online commerce. To learn more, see the [Industry Compliance]{https://docs.magento.com/m2/ee/user_guide/stores/compliance-industry.html) section in the Magento User Guide. +Merchants are obligated to meet industry guidelines for maintaining a secure environment, legal requirements in their jurisdiction, and best practices for online commerce. To learn more from a business perspective, see the [Industry Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-industry.html) section in the _Magento User Guide_. -The topics in this section provide the technical information necessary to help merchants comply with the requirements of specific privacy legislation. Some of the recent privacy regulations require additional development effort on the part of the merchant. See the following topics for the technical information you need to support your clients who have Magento installations. +This compliance documentation provides the technical information to ensure that Magento Commerce installations comply with the requirements of specific privacy legislation. Some of these requirements require merchants to complete additional development work to achieve compliance. See the following topics for details: - [California Consumer Privacy Act (CCPA)]({% link compliance/privacy/ccpa.md %}) - [General Data Protection Regulation (GDPR)]({% link compliance/privacy/gdpr.md %}) From 0554cd5ecf43dd48576cf661c5fbb1722354fbb3 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Wed, 18 Dec 2019 09:38:54 -0800 Subject: [PATCH 45/54] Update ccpa.md Edits from review - remoced 'target="; corrected tense; --- src/compliance/privacy/ccpa.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 28a0ad98cc3..85352a1d755 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -6,18 +6,18 @@ title: California Consumer Privacy Act {: .bs-callout .bs-callout-info} This is one in a series of topics to help Magento merchants and developers understand the implications of the California Consumer Privacy Act (CCPA). The information is intended for informational purposes only and should not be construed as legal advice. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. -The [California Consumer Privacy Act][1]{: target="_blank"} (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. +The [California Consumer Privacy Act][1] (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. The CCPA grants the following new rights to consumers: -- **Right to know** the categories of personal information about them that is collected, used, shared, or sold in the past 12 months. +- **Right to know** the categories of personal information about them that was collected, used, shared, or sold in the past 12 months. - **Right to delete** certain types of personal information that is held by a business and/or their service provider(s). - **Right to opt out** of the sale of their personal information. - **Right to non-discrimination** in terms of price or service for having exercised a privacy right under CCPA. ## CCPA Compliance Guide -Developing and implementing a CCPA compliance plan requires a coordinated effort. We encourage merchants to assemble a cross-functional team, and follow the roadmap outlined in [CCPA Compliance Guide][2]{: target="_blank"} to bring their company into compliance with the regulation. As a developer, you might be invited to participate as a stakeholder with an emphasis on steps 2 - 5 of the process. See the [CCPA Compliance Guide][2]{: target="_blank"} for more information. +Developing and implementing a CCPA compliance plan requires a coordinated effort. We encourage merchants to assemble a cross-functional team, and follow the roadmap outlined in [CCPA Compliance Guide][2] to bring their company into compliance with the regulation. As a developer, you might be invited to participate as a stakeholder with an emphasis on steps 2 - 5 of the process. See the [CCPA Compliance Guide][2] for more information. 1. Assemble a cross-functional team to address CCPA compliance. From faa3713662222cd154e7b5c40c06d02c27dc8ed9 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Wed, 18 Dec 2019 09:51:15 -0800 Subject: [PATCH 46/54] Update pi-data-reference-m2.md Clarified the header. --- src/compliance/privacy/pi-data-reference-m2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index eb080068cc1..ceb81a70b9a 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -124,7 +124,7 @@ Magento 2 stores the following customer attributes: - VAT Number - Zip/Postal Code -#### `customer_address_entity` and reference tables +#### `customer_address_entity` and `customer_address_entity` references The following columns in the `customer_address_entity` table contain customer information: From 8a2d4c892c17c86118d46c6b0d4ce74b830fa82b Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 07:16:08 -0800 Subject: [PATCH 47/54] Update src/compliance/privacy/gdpr.md Co-Authored-By: Kevin Harper --- src/compliance/privacy/gdpr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index 169b0fda3fb..56e5732e36a 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -8,7 +8,7 @@ redirect_from: - /guides/v2.2/architecture/gdpr/magento-1x.html --- -{: .bs-callout .bs-callout-info} +{: .bs-callout-info} This is one in a series of topics to help Magento merchants and developers understand the implications of the General Data Protection Regulation (GDPR). The information is intended for informational purposes only and should not be construed as legal advice. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. The European Union (EU) enacted [General Data Protection Regulation](https://ec.europa.eu/info/law/law-topic/data-protection_en) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU. From 0918c608d3bf288d7796c6802aadeab073778c26 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 07:16:24 -0800 Subject: [PATCH 48/54] Update src/compliance/privacy/pi-data-reference-m1.md Co-Authored-By: Kevin Harper --- src/compliance/privacy/pi-data-reference-m1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index 87c00d36260..ba7ea4a95c1 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -3,7 +3,7 @@ group: compliance title: Personal Information Reference (Magento 1.x) --- -{: .bs-callout .bs-callout-info} +{: .bs-callout-info} This is one in a series of topics to help Magento merchants and developers prepare for compliance with privacy regulations. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. Use the following data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: From dfacfe34d31a93b3a104f1122a191d8fb9e0967f Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 07:17:04 -0800 Subject: [PATCH 49/54] Update src/compliance/privacy/pi-data-reference-m1.md Co-Authored-By: Kevin Harper --- src/compliance/privacy/pi-data-reference-m1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md index ba7ea4a95c1..c63ee39bc20 100644 --- a/src/compliance/privacy/pi-data-reference-m1.md +++ b/src/compliance/privacy/pi-data-reference-m1.md @@ -4,7 +4,7 @@ title: Personal Information Reference (Magento 1.x) --- {: .bs-callout-info} -This is one in a series of topics to help Magento merchants and developers prepare for compliance with privacy regulations. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. +This is one in a series of topics to help Magento 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 data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: From a5ef709969d1a38f49bfce7334866d13ebcc4323 Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 07:17:33 -0800 Subject: [PATCH 50/54] Update src/compliance/privacy/pi-data-reference-m2.md Co-Authored-By: Kevin Harper --- src/compliance/privacy/pi-data-reference-m2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index ceb81a70b9a..c26c07f780a 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -4,7 +4,7 @@ title: Personal Information Reference (Magento 2.x) --- {: .bs-callout .bs-callout-info} -This is one in a series of topics to help Magento merchants and developers prepare for compliance with privacy regulations. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. +This is one in a series of topics to help Magento 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 data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: From cc16e6e20c430a3f9581420ec4f13ecf3be401af Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 07:17:56 -0800 Subject: [PATCH 51/54] Update src/compliance/privacy/ccpa.md Co-Authored-By: Kevin Harper --- src/compliance/privacy/ccpa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 85352a1d755..7240a4de50c 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -3,7 +3,7 @@ group: compliance title: California Consumer Privacy Act --- -{: .bs-callout .bs-callout-info} +{:.bs-callout-info} This is one in a series of topics to help Magento merchants and developers understand the implications of the California Consumer Privacy Act (CCPA). The information is intended for informational purposes only and should not be construed as legal advice. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. The [California Consumer Privacy Act][1] (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. From b80cf1b4ddf43b65cb59d285218f0e69404c3dfe Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 07:21:05 -0800 Subject: [PATCH 52/54] Update pi-data-reference-m2.md Updated callout syntax --- src/compliance/privacy/pi-data-reference-m2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index c26c07f780a..d4526674733 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -3,7 +3,7 @@ group: compliance title: Personal Information Reference (Magento 2.x) --- -{: .bs-callout .bs-callout-info} +{{:.bs-callout-info} This is one in a series of topics to help Magento 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 data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: From 18cf66c81b8bad4c9af8818658d2973d06077aeb Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 09:20:05 -0800 Subject: [PATCH 53/54] Update pi-data-reference-m2.md Fixed callout syntax --- src/compliance/privacy/pi-data-reference-m2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md index d4526674733..4c01ab480eb 100644 --- a/src/compliance/privacy/pi-data-reference-m2.md +++ b/src/compliance/privacy/pi-data-reference-m2.md @@ -3,7 +3,7 @@ group: compliance title: Personal Information Reference (Magento 2.x) --- -{{:.bs-callout-info} +{: .bs-callout-info} This is one in a series of topics to help Magento 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 data flow diagrams and database entity mappings for reference when developing compliance programs for privacy regulations such as: From 6f60e3dd7149ae87c8f2bf5d34bbc3643f5864ef Mon Sep 17 00:00:00 2001 From: Claire Condra Date: Thu, 19 Dec 2019 09:41:44 -0800 Subject: [PATCH 54/54] Removed "please" Consult with your... --- src/compliance/privacy/ccpa.md | 2 +- src/compliance/privacy/gdpr.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md index 7240a4de50c..6c652610407 100644 --- a/src/compliance/privacy/ccpa.md +++ b/src/compliance/privacy/ccpa.md @@ -4,7 +4,7 @@ title: California Consumer Privacy Act --- {:.bs-callout-info} -This is one in a series of topics to help Magento merchants and developers understand the implications of the California Consumer Privacy Act (CCPA). The information is intended for informational purposes only and should not be construed as legal advice. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. +This is one in a series of topics to help Magento merchants and developers understand the implications of the California Consumer Privacy Act (CCPA). The information is intended for informational purposes only and should not be construed as legal advice. Consult with your legal counsel to determine whether and how your business should comply with any legal obligations. The [California Consumer Privacy Act][1] (CCPA) expands the rights of consumers in California to determine how their personal information is collected, stored, and used, with an emphasis on protecting consumers from the unauthorized sale or exchange or their personal information. The CCPA was enacted in 2018 and is effective as of January 1, 2020. diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md index 56e5732e36a..6aff7565e4f 100644 --- a/src/compliance/privacy/gdpr.md +++ b/src/compliance/privacy/gdpr.md @@ -9,7 +9,7 @@ redirect_from: --- {: .bs-callout-info} -This is one in a series of topics to help Magento merchants and developers understand the implications of the General Data Protection Regulation (GDPR). The information is intended for informational purposes only and should not be construed as legal advice. Please consult with your legal counsel to determine whether and how your business should comply with any legal obligations. +This is one in a series of topics to help Magento merchants and developers understand the implications of the General Data Protection Regulation (GDPR). The information is intended for informational purposes only and should not be construed as legal advice. Consult with your legal counsel to determine whether and how your business should comply with any legal obligations. The European Union (EU) enacted [General Data Protection Regulation](https://ec.europa.eu/info/law/law-topic/data-protection_en) (GDPR) to give its citizens more control over their personal data. GDPR applies to any organization operating within the EU. It also applies to organizations outside of the EU that offer goods or services to customers or businesses in the EU.