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

Personal Data Anonymisation & Removal tool for analytics raw data - GDPR compliance #12641

Closed
mattab opened this issue Mar 23, 2018 · 2 comments
Labels
c: Privacy For issues that impact or improve the privacy.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Mar 23, 2018

As part of our effort to build-in Privacy in our product and for upcoming GDPR compliance #12600 we would like to release a new privacy tool.

  • A raw data anonymisation tool where you will configure a date range, for example, "Remove Personal data fields for all Raw data older than 6 months"
  • The tool would remove or full anonymise a few key attributes such as:
    • IP Address
    • Visitor ID
    • Fingerprint config ID
    • Location data including lat/long
    • One or several custom dimensions, and/or custom variables
    • User ID

The new tool could be available in the existing Administration> Privacy. It would record a "Request to Remove personal data" which would be executed during the scheduled tasks.

@mattab mattab added the c: Privacy For issues that impact or improve the privacy. label Mar 23, 2018
@mattab mattab added this to the 3.5.0 milestone Mar 23, 2018
@mattab mattab changed the title Raw data Anonymisation tool - GDPR compliance Personal Data Anonymisation & Removal tool for analytics raw data - GDPR compliance Mar 23, 2018
@tsteur
Copy link
Member

tsteur commented Mar 29, 2018

FYI: Unsetting eg all idaction_event_category values may result in many more pageviews to be reported because the Actions-Archiver basically says where idaction_event_category is null and idaction_content_name is null => must be a page view. So when such data is removed, it may really result in wrong reporting data or even weird action types that aren't maybe unexpected because suddenly behind action.type might be an ID 10 instead of an expected 1 for the page view.

@mattab mattab modified the milestones: 3.6.0, 3.5.0 Apr 9, 2018
@mattab
Copy link
Member Author

mattab commented Apr 23, 2018

The data anonymisation tool is now available under Administration > Privacy > Anonymise data > Anonymize previously tracked raw data.

This is fixed in #12558 along with other GDPR improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Privacy For issues that impact or improve the privacy.
Projects
None yet
Development

No branches or pull requests

2 participants