Data collection

HCL Commerce provides various sample store pages, store functions, and other features that your site can customize and use to create your custom store. If your site customizes and uses these templates, your site can be set up to collect personal data about shoppers and other users that browse and shop within your custom store.

IBM itself does not collect, access, or process any data for your site. The collection, storage, processing, and security of any personal data for your site users is the responsibility of your organization.

By default, HCL Commerce includes marketing and promotion features and order, shipping, and payment processes that can be used to collect or process personal data. If your site uses customized versions of the provided sample store pages, your site can collect personal data when a user registers for your store and when they submit an order. If your site uses store locator function or uses marketing activities and segments that rely on tracking shopper behavior, your store can collect additional data about a user. Some of your customizations might also collect personal data.

The following data is the only data that is classified as personal data that can be collected by default with the store pages and functions that is provided with HCL Commerce. If your site uses customized versions of the provided store pages, functions, and features, your site can collect the following types of personal data. Depending on the pages and functions that your site uses, the data that is collected can be different. You are responsible for customizing your store so that you only collect the data that your site needs.

Personal identity data

This data can be collected and used to uniquely identify an individual. By default, store pages can collect the following data when a user is registering for a store, updating their account page, or submitting an order. Administrators can enter the data for internal users when the administrator is creating the user's account.
  • Logon ID
  • Name
    • First name
    • Last name
    • Middle name
    • Initials
    • Nickname
  • Address (shipping and billing)
    • Street address
    • Town or City
    • Province or State
    • Country
    • Postal Code or Zip Code
  • Email
  • Phone number (home / mobile)
  • Birthday
  • Gender
  • Preferred language
  • Preferred currency
  • Demographic information

Access and authentication credentials

Authentication data can be collected and used to uniquely identify an individual when a user registers for a store. By default, store pages can collect the following data when a user is registering for a store. For internal users, the data can be collected when administrators create user accounts.
  • Password
  • Password challenge answer

Payment and financial data

Payment and financial data can be collected and used to process orders and to pass to third-party services for processing payments and orders. By default, sample pages can collect the following data when a user is registering for a store or submitting an order.
  • Billing address
  • Payment (Credit card) details

Behavioral data

Your site can collect data about how your customers browse and interact with your store. This data can be collected as customers browse and use your store. This data can be used to customize advertisements, recommend products, and more. The collection and processing of this data might require consent by a customer before the data is collected. By default, HCL Commerce can be set up to collect the following behavioral data:
  • Shopper browsing behavior
  • Search history
  • Referral URL

Location data

If your site uses location-based features, such as store locator capabilities, you can collect data on the near-term location of an individual. This data can be used to determine the store to display to a user.

Order history

This data is collected when a customer submits an order. Depending on how your site processes orders, order data can be sent to a third-party system, such as an integrated order management system. Collected order data might need to be retained for auditing and other business purposes, such as to handle returns, recurring orders, and warranty claims.

Wish lists

This data is collected when a customer creates or updates a wish list.

When you are customizing your site to collect and process data, collect and process only the minimum amount of personal data that is needed.