Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GDPR: no data should be stored on the device until consent is given #4701

Closed
1 task done
benjaminclot opened this issue Jan 8, 2020 · 4 comments
Closed
1 task done
Labels
bug pinned won't be closed by stalebot

Comments

@benjaminclot
Copy link
Contributor

benjaminclot commented Jan 8, 2020

Type of issue

  • Bug

Description

Today, when no consent is explicitly given through an IAB-compliant CMP (e.g. Quantcast) or when consent is "off", data is still being stored on the user device. We are beginning to receive complaints from official government organizations and need a quick resolution so that GDPR is enforced for each and every module.

List of modules that seem to store cookies no matter what the consent is:

  • userid: Criteo
  • userid: ID5
  • userid: PubCommonID
  • AdYouLike
  • AppNexus
  • Criteo (also stores data in the LocalStorage)
  • Improve Digital
  • Index Exchange
  • JustPremium
  • OpenX

Steps to reproduce

  1. Go to any website with an IAB-compliant CMP (and possibly usersync enabled)
  2. Do not scroll or give consent and wait for the CMP timeout for bids to be sent (and for userync to trigger)
  3. Data is stored on the device (some 1st party, some 3rd party)

Expected results

No data should be stored (or read...).

Actual results

Data (mainly cookies) is stored.

Other information

May be related to issue #4572 ? Should usersync be disabled in the absence of consent?

@jsnellbaker jsnellbaker added the pinned won't be closed by stalebot label Jan 8, 2020
@jsnellbaker
Copy link
Collaborator

Tagging a few people to help comment on this topic.
@bretg @harpere @mkendall07

We could implement some temporary changes to the userId module and the userSync feature to disable the syncs to be on the safe side. May also want to look at this logic for the recent USP/CCPA as well (really to see if it applies, since the default state of consent is different than GDPR).

@jsnellbaker jsnellbaker added the bug label Jan 8, 2020
@bretg
Copy link
Collaborator

bretg commented Jan 10, 2020

We will discuss.

@bretg
Copy link
Collaborator

bretg commented Jan 14, 2020

FYI - discussions are underway. Will update by Thurs.

@bretg
Copy link
Collaborator

bretg commented Jan 17, 2020

@benjaminclot - if you're satisfied that #4747 generally addresses the issue here, please close this issue and feel free to comment in the other thread. Thanks for bringing it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug pinned won't be closed by stalebot
Projects
None yet
Development

No branches or pull requests

3 participants