LogoLogo
Support
Product Discovery Developer Guide
Product Discovery Developer Guide
  • Product Discovery Developer Guide
  • 🛒Item catalog management
    • What is the Items API?
    • How to work with Items
      • Item Schema
        • Attributes
        • Nested Item Schemas
        • Using the Item Schema API
        • DefaultLocale API
        • Onboarding on/migrating to Fredhopper
        • List of Reserved Attributes
      • Category Tree
        • Using the Category Tree API
        • Onboarding on XO
      • Item Catalog
        • Using the Catalog API
      • Items
        • Using the streaming Items API
        • Using the batch Items API
    • Step by Step guide
      • Step by step guide for Fredhopper customers
    • Feedback
      • Using the Feedback API
    • Authorization to APIs
    • Troubleshooting API errors
  • 🎯XO Recommendations
    • Introduction
    • Using the Recommendations API
    • Setting up the Chrome extension
    • Micro-segmentation
    • XO Legacy APIs
  • 🔎XO Search
    • Introduction
    • Getting started
    • API Reference
      • Search API
      • Autocomplete API (Beta)
      • Product Suggest API
    • API Parameters
      • Search
      • Pagination
      • Faceting
      • Sorting
      • Grouping
      • Filtering
      • Disable features
      • Response mask
      • Context
    • Configuration limitation
  • 🧪A/B testing
    • Fredhopper A/B testing
      • Integration steps for a non-caching solution
      • Integration steps for a caching solution
        • Java SDK Integration
          • Setup
          • Retrieve running A/B tests - Java SDK
          • Filter and request variant - Java SDK
          • Extending the SDK
        • Manual A/B tests integration
          • Retrieve running A/B tests
          • Filter out irrelevant A/B tests
          • Assign variants to user
          • Request variant for page
        • Limitations and Best Practices
  • 📚Resources
    • Glossary
    • Best Practices
      • Tracker Best Practices
      • Items API Best Practices
      • Fredhopper Data Configuration Best Practices
      • Fredhopper Query Response Best Practices
      • Fredhopper Merchandising Studio Best Practices
    • Privacy Notice
  • Archived Pages
    • FHR Tracking plan
    • XO Tracking plan
    • The Tracking API and JS Library
      • What to Track
        • Generic Actions
          • View
          • Click
          • Add to Cart
          • Remove from Cart
          • Purchase
        • Custom Actions
      • Initializing the JavaScript Library
      • REST API Technical Documentation
Powered by GitBook

Copyright @ 2024 Crownpeak Technology, Inc. All rights reserved.

On this page
  • Browser cookie
  • Server side data processing
  • Collected data
  • Personal data removal policies
  • Security measures
  • Place of processing
  1. Resources

Privacy Notice

Browser cookie

The Crownpeak Product Discovery activities SDK uses persistent cookies (browser local storage) to store the session id of a user or a boolean representing the opt out option of the user. The session id is either provided or generated by the SDK. When generated, it will be represented by a UUID.

The cookie is persisted until the user clears the browser cache.

Server side data processing

Collected data

Data points
Purpose
Data processor

Session id and the anonymized logged in user id (email, username, user id)

Cookie matching feature and calculation of user journeys

Attraqt

User traits (you decide what exact information is being sent)

Enables the use of personalization algorithms

Attraqt

Users IP addresses

Operational monitoring (capability to implement active protection and to do post-mortem security reports in case of attacks and breaches)

Attraqt

Personal data removal policies

Activity events data

User information is anonymized, and impossible to retro-match to an individual user. All users activity data will be stored on the Attraqt platform as long as the client contract dictates the access to services.

Operational data

The policy for operational logging is as follows:

  • Online log analysis sub-system (ELK) - rolling window of 2 months.

  • Backup of logs - 2 years. Purging occurs on regular monthly basis.

Security measures

  • Segregation

    • Changing security settings - privileged administrator access only for dedicated and trained team.

  • Encryption applied to logging storage.

  • Communication over Internet uses secure transport protocol (HTTPS/SSH).

Place of processing

User data (ids, traits, IPs) is stored and processed in EU. Activity events are stored and processed in EU and the same region as FHR or XO.

FAS/XO region
User data (ids, traits, IPs)
Activity data

EU

EU

EU

US

EU

US + EU

AP

EU

AP + EU

PreviousFredhopper Merchandising Studio Best PracticesNextArchived Pages

Last updated 7 months ago

📚