Skip to main content
RichRelevance

Integration: Privacy

Overview

This document will provide an overview of available integration touch points for respecting your shopper's privacy. European Union law and many national regulations require opt-out availability to prevent the tracking of user information and behavior. 

Audience

All clients should be aware of the options available to respect the privacy of their customers.

General Data Protection Regulation

This is designed for the EU General Data Protection Regulation (GDPR) and specifically the user's right to be forgotten. For more information, see: https://www.eugdpr.org/the-regulation.html

Privacy Touch points:

  1. The Profile Command API allows an organization to Opt Out on behalf their users.
  2. And each individual request to Recommend and Engage can be anonymized by enabling private mode on the request.
  • For client-side javascript integrations:

R3_COMMON.setPrivateMode();

  • For server side recsForPlacement calls, add a query string parameter

privm=t

Using private mode has the same impact as not passing the user ID on the request.

Access to User Profile Data

The RichRelevance dashboard provides a method to access an individual's user profile. By entering the user id the profile data is presented from the User Profile Service for that user. The user profile data can be exported to a csv file. 

Screen Shot 2020-02-13 at 2.29.59 PM.png

Notes

An anonymous user (no user ID or in private mode) will still get personalization based on the session ID that is passed. So throughout a session, the Recommend and Engage responses will use the context of the session to add personalization. But when a user id is passed that has opted out, no personalization will take place.

  • Was this article helpful?