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

Cite RFC6772 #339

Merged
merged 3 commits into from
Aug 2, 2023
Merged

Cite RFC6772 #339

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f2747ff
Cite RFC6772, noting that low-granularity information can still reveal
npdoty Aug 1, 2023
9da50ca
caveat phrasing
npdoty Aug 1, 2023
8f7ddf5
avoiding normative language for clarity
npdoty Aug 1, 2023
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
7 changes: 5 additions & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1327,8 +1327,11 @@
information can be extremely sensitive (because it's identifying, because it
allows for in-person intrusions, because it can reveal detailed information
about a person's life) but it might also be public and not sensitive at all, or
it might be low-enough granularity that it is much less sensitive for many
people.
it might be low-enough granularity that it is less sensitive for many
people. Beware that reducing granularity of location information may not hide precise location information from
npdoty marked this conversation as resolved.
Show resolved Hide resolved
an [=actor=], particularly if location information is repeatedly requested over time or if
the [=actor=] has other relevant information about the [=person=] [<a
data-cite="RFC6772#section-13.5">RFC6772</a>].

When considering whether a class of information is likely to be sensitive to
a person, consider at least these factors:
Expand Down