What data does Constructor store in cookies, local storage, and session storage?

Constructor uses a number of attributes to provide its personalized product discovery services to users. Below is a list of the attributes stored.

Cookies

• ConstructorioID_client_id
  Stores Constructor's randomly generated anonymous client identifier. This cannot be tied back to any personally identifiable information (PII).
  
  
• ConstructorioID_session andConstructorioID_session_id
  These are used to store incrementing session counts. The counter is incremented after 30 minutes of inactivity. May not be present depending on the type of integration.

Local Storage

• _constructorio_search_session and_constructorio_search_session_id
  These are used to store incrementing session counts. The counter is incremented after 30 minutes of inactivity. May not be present depending on the type of integration.
  
  
• _constructorio_requests
  Some Constructor tracking events cannot be immediately dispatched, as there is a chance they may be lost (for instance, if the browser is currently unloading). Request data is stored in this cookie temporarily until it can be safely transmitted to our servers.
  
  
• _constructorio_recent_searches
  Utilized to keep a history of a user's recent searches, to help with de-duplication of tracking events related to search results.

Session Storage

• _constructorio_url_stack
  Utilized to keep a history of a user's visited pages, to help with de-duplication of tracking events related to search results.
  
  
• _constructorio_is_human
  Constructor uses intelligent logic to differentiate human traffic vs. bot traffic in order to ensure the data we consume is genuine. Once a user has shown that they are not exhibiting bot-like traffic, this cookie is set to avoid the need to re-detect this logic on every request.
  
  
• _constructorio_search_term
  Stores the current search term in search result contexts for use with tracking.
  
  
• _constructorio_purchase_order_ids
  Utilized to keep a history of order id's associated with user purchases, to help with de-duplication of tracking events related to purchase tracking.