Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114)

@marcoscaceres commented on this pull request.



> @@ -816,18 +817,29 @@ <h3>
             This can be useful for analytics and possibly other customizations.
             However, it is also conceivable that developers could encode
             strings into the start_url that uniquely identify the user (e.g., a
-            server assigned <abbr>UUID</abbr>). This is fingerprinting/privacy
-            sensitive information that the user might not be aware of.
+            server-assigned <abbr>UUID</abbr> such as `"?user=123"`,
+            `"/user/123/"`, or `"https://user123.foo.bar"`). This is
+            fingerprinting/privacy sensitive information that the user might
+            not be aware of.
+          </p>
+          <p class="note">
+            It would be irresponsible for a developer to use the [=start URL=]
+            to include information that uniquely identifies a user, as it would
+            represent a fingerprint that is not cleared when the user clears
+            site data. However, nothing in this specification can practically
+            prevent developers from doing this.

Maybe we should just make the above some may... that the user agent MAY strip out any personally identifiable information or IDs from start URLs. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1114#discussion_r1585930163
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1114/review/2033100112@github.com>