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.

Sign up for GitHub

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

Jump to bottom

Say the suggestions for handling new ancillary personal data are examples. #435

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Say the suggestions for handling new ancillary personal data are examples. #435

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1349,8 +1349,8 @@

Some [=ancillary uses=] don't require their data to be related to a person, but
the useful aggregations across many people are difficult to design into a web
API, or they might require new technologies to be invented. API designers have a
few choices in this situation:
API, or they might require new technologies to be invented. Some ways API
designers can handle this situation include:

* Sometimes an API can [=de-identify=] the data instead, but this is difficult
if a web page has any input into the data that's collected.
Expand All @@ -1361,9 +1361,9 @@
<a href="#unavoidable-information-exposure">unavoidably</a> revealed
by <a data-cite="dom#interface-event">DOM event</a> timing.
* [=User agents=] can ask their users' permission to enable this class of API.
To reduce [=privacy labor=], a [=user agent=] could use a first-run dialog to
ask the user whether they generally support sharing this data, rather than
asking for each use of the APIs.
This risks increasing [=privacy labor=], but as an example, a [=user agent=]
could use a first-run dialog to ask the user whether they generally support
sharing this data, rather than asking for each use of the APIs.

If an API had to make one of these choices, and then something else about the
API needs to change, designers should consider replacing the whole API with one
Expand Down