Re:Open-Sourcing our GDPR Compliance Preparation For Article...
by stingraycharles on Saturday May 19, 2018 @04:10PM
(#17109523)
As soon as you could reasonably pinpoint it to a certain person, it becomes PII. A classic example includes a combination of zipcode, gender and age. While individually they would not be a problem, it’s the combination of these different parameters that allow you to narrow the pool so much it can reasonably assumed to be PII.
Re:Open-Sourcing our GDPR Compliance Preparation For Article...
by dominotw on Saturday May 19, 2018 @04:49PM
(#17109655)
> . While individually they would not be a problem, it’s the combination of these different parameters that allow you to narrow the pool so much it can reasonably assumed to be PII.
There are zipcodes in USA with only 1 person. So storing just zipcode would be ID information. Its an extereme example but how can machine check whats 'reasonable' in this case, go off of some census data for zipcode?
I wonder if there are any real world ( as opposed to things like ingame points) information that can be considered not PII .
Re:Open-Sourcing our GDPR Compliance Preparation For Article...
by punnerud on Saturday May 19, 2018 @06:57PM
(#17110176)
There is also the interpretation of when is it PD or AD.
In Norway the ‘The Norwegian Data Protection Authority‘ states 4 or less is personal, no way to link to less than 5 is anonymous.
customer_ID -> address
I can zero in that its someone that lives in that house but not who it is.
What about
customerID -> IpAdress
I can look up ipaddress at a later point to and identify a subset of ppl with that IP.
Whould that be considered personal data.