The Census Bureau has conducted a new analysis that purports to show that swapping is ineffective for the prevention of reidentification attacks. /1
www2.census.gov/about/partners…
The new analysis completely misses the point, and actually provides a useful demonstration of the gross misrepresentation of the Census Bureau’s “Database Reconstruction Experiment.” /2
The Census Bureau claimed that without swapping, they could “putatively re-identify” 44.60 of the population. /3
As @dcvanriper and I explained, you would expect to find that result 40.9% of the time even if you assign age and sex randomly and then assign the modal race and ethnicity of the block./4 assets.ipums.org/_files/mpc/wp2…
What that means is that this isn’t re-identification at all—one would expect to almost as many matches between the reconstructed data and the real data purely by chance. This would be laughable if it were not so sad./5
The so called “confirmed reidentifications” are even more disingenuous. All they mean is that only about some 38% of the population in commercial data sources can actually be located in the Census file, which means that either the commercial data or the Census are really bad./6
So now in the new experiment they add swapping, and find that it doesn’t change the results. Even if you swap 50% of the population, it hardly affects the percentage of “putative” or “confirmed” reidentifications. How could that possibly be?/7
Could it be that swapping for some mysterious reason is completely ineffective, even when you swap out half of the entire population?/8
The real answer is obvious—they were never reidentifying at all, they were just getting random matches. You could swap 100% and the results would still come out the same!!/9
This is an excellent illustration of how the Census Bureau database reconstruction experiment was egregiously misrepresented, and never represented the slightest threat./10
This is a truly embarrassing moment for the Census Bureau. /end.
P.S. The Census Bureau is presenting this on Friday, in case anyone cares to sho up and ask a few wuestions: census.gov/data/academy/w…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Steven Ruggles

Steven Ruggles Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @HistDem

21 May
/1. Yesterday at the ACS Data Users Conference, the Census Bureau described its plans to replace the American Community Survey (ACS) microdata with “fully synthetic” data over the next three years.
/2. Details of the methodology have not been disclosed, but the idea is to develop models describing the interrelationships of all the variables in the ACS, and then construct a simulated population consistent with those models.
/3. Such modeled data captures relationships between variables only if they have been intentionally included in the model. Accordingly, synthetic data are poorly suited to studying unanticipated relationships, which impedes new discovery.
Read 30 tweets
19 May
/1. @samwang misinterprets the second declaration of John Abowd in Alabama v. Department of Commerce.
/2. Abowd states that in tiny blocks, if you “reconstruct” age and it matches someone who lives on the on the block in the commercial database, and then look up the names of those people in the census, the census recorded the same people 72.24% off the time.
/2. Everyone on the block in the commercial database ought to be found on the same block in the census.
Read 13 tweets
15 May
/1. The Census Bureau plans to add intentional errors to the 2020 census to protect the confidentiality of census respondents. The Census Bureau insists that the intentional error is necessary to combat the threat of “database reconstruction.”
/2. Database reconstruction is a process for inferring individual-level responses from tabular data. The Chief Scientist of the Census Bureau asserts that database reconstruction “is the death knell for traditional data publication.”
/3. To demonstrate the threat Census conducted a database reconstruction experiment that attempted to infer the age, sex, race, and Hispanic or Non-Hispanic ethnicity for every individual in each of the 6.3 million inhabited census blocks in the 2010 census.
Read 20 tweets
20 Apr
1.I prepared a report for the Plaintiffs in the Alabama v. Department of Commerce lawsuit over differential privacy in the census, available here: users.hist.umn.edu/~ruggles/censi…
2.I argue that the database reconstruction experiment did not demonstrate a convincing threat to confidentiality, because the results reported by the Census Bureau can be largely explained by chance.
3. Any randomly-chosen age-sex combination would be expected to be found on any given block more than 50% of the time.
Read 9 tweets
5 Jul 19
What we have learned about the Census Bureau’s implementation of differential privacy.

In September 2020, the Census Bureau announced new confidentiality standards that mark a “sea change for the way that official statistics are produced and published.” 1/
The new system, known as Differential Privacy (DP), will be applied first to 2020, and “will then be adapted to protect publications from the American Community Survey and eventually all of our statistical releases.” 2/
I am increasingly convinced that DP will degrade the quality of data available about the population, and will make scientifically useful public use microdata impossible. 3/
Read 26 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(