From f2747ffab1093d38fc239a877c97b8c6c321fe78 Mon Sep 17 00:00:00 2001 From: Nick Doty Date: Tue, 1 Aug 2023 12:08:10 -0400 Subject: [PATCH 1/3] Cite RFC6772, noting that low-granularity information can still reveal precise information and some of the conditions for why less emphatic about the sensitivity difference --- index.html | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index e315f76d..97440114 100644 --- a/index.html +++ b/index.html @@ -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. Reducing granularity of location information may not hide precise location information from +an [=actor=], however, particularly if location information is repeatedly requested over time or if +the [=actor=] has other relevant information about the [=person=] [RFC6772]. When considering whether a class of information is likely to be sensitive to a person, consider at least these factors: From 9da50ca9949a56dfca980d7f97274d320fc1f13c Mon Sep 17 00:00:00 2001 From: Nick Doty Date: Tue, 1 Aug 2023 13:07:51 -0400 Subject: [PATCH 2/3] caveat phrasing Co-authored-by: Jeffrey Yasskin --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 97440114..9a51fc09 100644 --- a/index.html +++ b/index.html @@ -1328,8 +1328,8 @@ 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 less sensitive for many -people. Reducing granularity of location information may not hide precise location information from -an [=actor=], however, particularly if location information is repeatedly requested over time or if +people. Beware that reducing granularity of location information may not hide precise location information from +an [=actor=], particularly if location information is repeatedly requested over time or if the [=actor=] has other relevant information about the [=person=] [RFC6772]. From 8f7ddf53c14f00f2d4503a5bbbe9d516af129b79 Mon Sep 17 00:00:00 2001 From: Nick Doty Date: Tue, 1 Aug 2023 14:16:55 -0400 Subject: [PATCH 3/3] avoiding normative language for clarity Co-authored-by: Jeffrey Yasskin --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 9a51fc09..aa222805 100644 --- a/index.html +++ b/index.html @@ -1328,7 +1328,7 @@ 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 less sensitive for many -people. Beware that reducing granularity of location information may not hide precise location information from +people. Beware that reducing granularity of location information might not hide precise location information from an [=actor=], particularly if location information is repeatedly requested over time or if the [=actor=] has other relevant information about the [=person=] [RFC6772].