Git-Mirrors/privacyguides.org
1
0
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2025-07-19 21:08:57 -04:00
Code Issues Projects Releases Packages Wiki Activity

add example Table

Browse source
This commit is contained in:
fria 2025-07-08 09:11:30 -05:00 • committed by GitHub
parent f6c344393f
commit fc2c321bee
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 14 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

15
blog/posts/differential-privacy.md
View file

@ -49,7 +49,20 @@ Analyst [Nathan Ruser](https://x.com/Nrg8000/status/957318498102865920) indicate
It was also possible to [deanonymize](https://steveloughran.blogspot.com/2018/01/advanced-denanonymization-through-strava.html) individual users in some circumstances.
####
#### Randomized Response
One of the earliest ideas for anonymizing data was [randomized response](https://uvammm.github.io/docs/randomizedresponse.pdf), first introduced all the way back in 1965 in a paper by Stanley L. Warner. The idea behind it is quite clever.
For certain questions like "have you committed tax fraud?", respondents will likely be hesitant to answer truthfully. The solution? Have the respondent flip a coin. If the coin is tails, answer yes. If the coin lands on heads, answer truthfully.
| Respondent | Answer | Coin Flip (not included in the actual dataset just here for illustration) |
| --- | --- |
| 1 | Yes | Tails (Answer Yes) |
| 2 | No | Heads (Answer Truthfully) |
| 3 | Yes | Heads (Answer Truthfully) |
| 4 | Yes | Tails (Answer Yes) |
| 5 | No | Heads (Answer Truthfully) |
#### Problems with k-anonymity