BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH
BEGIN:VEVENT
DTSTAMP:20260519T190236Z
DESCRIPTION:Click for Latest Location Information: http://edw2020chicago.da
 taversity.net/sessionPop.cfm?confid=143&proposalid=12333\nResearch shows th
 at traditional de-identification of data is not working as expected.&nbsp;C
 urrent research shows that a data set with 15 demographic attributes can ma
 ke 99.98% of the state of Massachusetts unique. In smaller areas it is,&nbs
 p;of course,&nbsp;much less.&nbsp;Examples of re-identified data include Ne
 tflix in 2008 and data leaked to the public, as well as&nbsp;home addresses
  of New York taxi drivers from an anonymous data set of individual trips in
  the city.&nbsp;This presentation will detail exactly what GDPR and CCPA re
 quire in data protection and the shortcomings of some current de-identifica
 tion techniques.&nbsp;Additionally covered will be techniques to properly i
 dentify data,&nbsp;which include purposely fuzzing data so that data report
 ed is not actually accurate.&nbsp;The data would be &quot;skewed&quot; in a
  standard way.&nbsp;Other options include encryption techniques where the d
 ata cannot be decrypted except by the owner.&nbsp;&nbsp;\nAttendees will le
 arn:\n\n	Why and how data is re-identified\n	What GDPR and CCPA require\n
 Examples of re-identification\n
 Best solutions to properly de-identify data\n
 Companies that are doing a better job of de-identification of data\n
DTSTART:20201021T083000
SUMMARY:Why "De-Identification" Will NOT Satisfy GDPR and CCPA Solutions
DTEND:20201021T091959
LOCATION: See Description
END:VEVENT
END:VCALENDAR