Live data from Hacker News

Simulating identification by zip code, sex, and birthdate

johndcook.com

21–30 of 39 posts

Re: Simulating identification by zip code, sex, and birthdate

#21
post #4

Earlier quoted context omitted.

I think that your alteration of the title is good, but why did you change "sex" to "gender"?! The study appears to be about sex as a matter of public record, so you've added inaccuracy, or at least ambiguity, to the title.

Oh good point. I don't know, I was writing from memory. I didn't mean any offense by it and didn't think about the implied difference between the two terms. Sorry!

In some cultures, sex is what you do, gender is what you have. So for me, when asked for sex, my answer is "yes, please". When asked for gender it's M/F.

I understand that the US is different in this regard.

Re: Simulating identification by zip code, sex, and birthdate

#22
I've worked in probablistic data-linking quite substantially over the past ten years. See https://github.com/DJMelksham/IcarusDataLinkingSystem for example.

While the principal is broadly correct, in real life you've got to worry about a host of other things.

Firstly, while you can come up with a theoretical number of persons who are uniquely identified, its harder to establish who IS uniquely identified. This might seem like splitting hairs but its quite fundamental: imagine you knew you could identify 50% of the population uniquely, unless you know which 50% of the population, have you really identified anyone? Clearly knowing someone's sex, age and location gives me analytical information about them I can use to make predictions (a 5 year old female in california is going to be fundamentally different from a 85 year old male in alabama) but is it really identification yet and do we even need identification to make useful predictions?

Secondly, what you presumably care about in 'identification' is not 'single source' probability issues per se. In the real world what most people care about is multiple-source identifiability: not the odds of one piece of data uniquely identifying someone (just by collecting gender I might eventually uniquely identify someone in some remote geography for example), but the odds of uniquely identifying someone in TWO (or more) data sources that were previously 'unlinked', because that's what's required to expand your current information set (you didn't know this person was identifiable on two data sources, and now you do, so you can bring together more information than what you already held originally).

This second point is extremely important, because in the real world, you have to worry about transcription errors, recording formats, corruption, temporal changes and time, and scope of the two data sources. Most people do not get to work with total accurate census' of the population at two points in time in a population that doesn't change.

From my own practical experience, something like the zip code, sex and birthdate combination is powerful, and yes, you'll be able to uniquely identify some people with such information (especially in smaller geographical areas), but the practical rate will be far far less than 87%. But for many modelling purposes, it doesn't need to be spectacularly accurate to be useful anyway.

Re: Simulating identification by zip code, sex, and birthdate

#23
post #4

I editorialized the title a bit - the author's title is "Simulating identification by zip code, sex and birthdate." Instead I've used the salient conclusion of the article, which is pretty interesting. This article is a footnote to another front page submission by the same author, "No funding for uncomfortable results." While that article is sobering, I find this one to be technically cooler. The author uses a simple…

I think that your alteration of the title is good, but why did you change "sex" to "gender"?! The study appears to be about sex as a matter of public record, so you've added inaccuracy, or at least ambiguity, to the title.

Is sex male/female and gender "what I identify as"? I've always thought of them in this context as meaning the same thing...

Re: Simulating identification by zip code, sex, and birthdate

#24

Earlier quoted context omitted.

Oh good point. I don't know, I was writing from memory. I didn't mean any offense by it and didn't think about the implied difference between the two terms. Sorry!

In some cultures, sex is what you do, gender is what you have. So for me, when asked for sex, my answer is "yes, please". When asked for gender it's M/F. I understand that the US is different in this regard.

I agree sex is a verb and also an attribute...

Re: Simulating identification by zip code, sex, and birthdate

#25
post #16

While this is intended as just a proof of concept, I think this technique is mathematically flawed. You can't just use the average number of people in each zipcode, because if there is great variation in the number of people per zipcode, a randomly sampled person is more likely to be in a "large" zipcode than a small one. Consider the case where we have 100000 people, and 10 zipcodes, each with an average of 10000 pe…

That's an excellent counterpoint. Non-uniformity is the great bane of straightforward statistical analysis.

Re: Simulating identification by zip code, sex, and birthdate

#26
post #16

While this is intended as just a proof of concept, I think this technique is mathematically flawed. You can't just use the average number of people in each zipcode, because if there is great variation in the number of people per zipcode, a randomly sampled person is more likely to be in a "large" zipcode than a small one. Consider the case where we have 100000 people, and 10 zipcodes, each with an average of 10000 pe…

I work with this type of data and I assure you that the results are quite plausible. The original hypothesis was tested against US census data. See "Experiment B" here:

https://dataprivacylab.org/projects/identifiability/paper1.p...

I'll add that there are far fewer live births, per day, in the US than there are zip codes. I agree that some highly populated areas that are problematic, but this may be the only reason that 87.1% number isn't 100%!

Re: Simulating identification by zip code, sex, and birthdate

#27

Earlier quoted context omitted.

Oh good point. I don't know, I was writing from memory. I didn't mean any offense by it and didn't think about the implied difference between the two terms. Sorry!

In some cultures, sex is what you do, gender is what you have. So for me, when asked for sex, my answer is "yes, please". When asked for gender it's M/F. I understand that the US is different in this regard.

It's generally understood that sex is biological and gender is social, or grammatical: it makes sense for those two to go together as in many languages, including standard English, you need to know a person's gender in order to talk about them easily.

In the UK, at least, official documents specify "sex", not "gender". We may be slowly moving towards a world in which sex is officially recorded only in medical records, while gender is an optional field in social media accounts and the like.

Re: Simulating identification by zip code, sex, and birthdate

#28
post #4

Earlier quoted context omitted.

I think that your alteration of the title is good, but why did you change "sex" to "gender"?! The study appears to be about sex as a matter of public record, so you've added inaccuracy, or at least ambiguity, to the title.

Is sex male/female and gender "what I identify as"? I've always thought of them in this context as meaning the same thing...

In medical and demographic datasets where there is a need to differentiate between biological sex and self-identified gender then yes, they are used that way.

But in other settings they are usually conflated.

Re: Simulating identification by zip code, sex, and birthdate

#29

surprised that gender is that useful for this

Well if you work with even smaller data sets every additional attribute narrows the field quite a bit unless it is ubiquitous. Adding a species field to employee records or "doesn't have Marfan's syndrome" wouldn't narrow much but cummulative divisions of N help a lot with scaling.

Re: Simulating identification by zip code, sex, and birthdate

#30
post #16

While this is intended as just a proof of concept, I think this technique is mathematically flawed. You can't just use the average number of people in each zipcode, because if there is great variation in the number of people per zipcode, a randomly sampled person is more likely to be in a "large" zipcode than a small one. Consider the case where we have 100000 people, and 10 zipcodes, each with an average of 10000 pe…

Another point that people forget is that real world population is not only not evenly distributed in geography, but geographical distributions are not then evenly distributed in terms of age.

The real distribution of birth days within a neighborhood is almost always far less spread than an assumption of uniformity across the entire probability distribution (because schools, dinks, retirees, students, workers, etc all trend to cluster in real life).

This tendency of demographics to cluster makes de-identification harder than the theoretical models, and in some ways even protects it aa bit, because researchers who don't test their models assume greater accuracy than they actually achieve.

Of course, this might not be as protecting as one might assume, because for a lot of activities, even if people do casually link you to someone else, odds are pretty good you have similar modelled outcomes as someone very close to you in properties anyway...

Post reply on HN