Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to the k-anonymity server explainer #406

Merged
merged 3 commits into from
Dec 15, 2022

Conversation

kgraney
Copy link
Contributor

@kgraney kgraney commented Dec 2, 2022

No description provided.

@kgraney
Copy link
Contributor Author

kgraney commented Dec 2, 2022

Hi @michaelkleber, here's another update to the k-anonymity explainer.

[k-anonymity](https://en.wikipedia.org/wiki/K-anonymity) is a privacy concept
that provides some protection against users being individually reidentified
within a data set. The concept itself is simple: to meet a k-anonymity
threshold at least $k$ different users must be present in the same data set.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I don't think this is quite what you mean — you can have lots of different people "present in the same dataset" without getting any k-anonymity.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarified that we count users per-object not users present per dataset.


The [FLEDGE](FLEDGE.md) proposal calls for k-anonymity thresholds on several
features. The first threshold is before interest groups are updated. A browser
should not request an interest group update unless there are at least $k$
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's say "...should not request an interest group update from an untrusted server unless..."
Since #333 is about the possibility of using trusted servers for this, let's be clear on that as an alternative to k-anonymity.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, added that qualifier.

FLEDGE_k_anonymity_server.md Show resolved Hide resolved
Each of these use cases is aggregating counts of users towards $k$ across
many browsers. They require taking local browser state, i.e. data generated
within browser platform APIs, counting aggregates among the set of all browsers
and users, and reporting back to all browsers the results of this counting.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, not to all browsers!...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarified that this is only some browsers that are contributing to counts and/or interested in them.

@michaelkleber michaelkleber merged commit 78d5889 into WICG:main Dec 15, 2022
github-actions bot added a commit that referenced this pull request Dec 15, 2022
SHA: 78d5889
Reason: push, by michaelkleber

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants