- From: CVS User npdoty <cvsmail@w3.org>
- Date: Mon, 26 May 2014 03:46:55 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv28769
Modified Files:
tracking-compliance.html
Log Message:
remove geolocation restriction; add note about geolocation in deidentified section; related to issue-202
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/05/26 03:27:19 1.114
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/05/26 03:46:55 1.115
@@ -197,7 +197,11 @@
re-identify the data.
</li>
</ol>
+ <p class="note">
+ Note that geolocation data (of a certain precision or over a period of time) may itself identify otherwise deidentified data.
+ </p>
<p class="issue" data-number="188" title="Definition of de-identified (or previously, unlinkable) data"></p>
+ <p class="issue" data-number="202" title="Limitations on geolocation by third parties"></p>
</section>
<section id="tracking">
<h3>Tracking</h3>
@@ -344,18 +348,6 @@
one of the permitted uses MUST NOT place a unique identifier in cookies
or other browser-based local storage mechanisms.
</p>
- <section id="geolocation">
- <h3>Third Party Geolocation Compliance</h3>
- <p>
- If a third party to a given user action receives a
- <code>DNT:1</code> signal in a related network interaction, then that
- party MUST NOT use geolocation data in that interaction at any level more
- granular than postal code, unless specific consent has been granted
- for the use of more granular location data.
- </p>
- <p class="issue" data-number="202" title="Limitations on geolocation by third parties"></p>
- </section>
-
<section id="permitted-use-requirements">
<h4>General Principles for Permitted Uses</h4>
Received on Monday, 26 May 2014 03:46:56 UTC