User Consent for Data

For GDPR, ePrivacy Directive, CCPA and similar compliance it is important that your system, and by extension Fanplayr, respects users choice in how their data is stored and processed.

An example of this is where you may want Fanplayr to be included in your "essential" services on your site.

Data storage and processing

In normal operation Fanplayr will:

1. track users with a cookie that is kept between sessions

2. use tracked data to segment user and do actions ie display Creative

3. store tracked data once a session is complete

When consent mode is activated, and consent status disabled (consent not given) then the only thing that happens is item 2 from above:

• use tracked data to segment user and do actions ie display Creative

• do not use cookie between sessions

• do not store data once a session is complete

States

The three main states you will want to set on both page tracking and order tracking are:

Disabled

{
  ..
  userConsentMode: false, // or undefined, null
  ..
}

In this state userConsentStatus is ignored, and it is assumed that consent has been given to store data.

Enabled / No consent given

{
  ..
  userConsentMode: true,
  userConsentStatus: false,  // or undefined, null
  ..
}

In this state no data is tored.

Enabled / Consent given

{
  ..
  userConsentMode: true,
  userConsentStatus: true,
  ..
}

In this state data is again stored as user consent has been given.

How to implement

Many people implement this with a third party consent manager.

The variables

userConsentMode

Determines whether Fanplayr is required to consider the user's consent in order to store their data.

• Enabled: only set to true

• Disabled: If any value other than true ie false or undefined

userConsentStatus

If userConsentMode is set to true then this will define wether the user has consented to have their data stored.

• User consent given: only set to true

• User consent not given: If any value other than true ie false or undefined