diff --git a/index.html b/index.html index 0f7314c1..a2c5326b 100644 --- a/index.html +++ b/index.html @@ -741,6 +741,15 @@ "href": "https://www.yalelawjournal.org/feature/a-relational-theory-of-data-governance", "publisher": "Yale Law Journal", "id": "relational-governance" + }, + "web-without-3p-cookies": { + "title": "Improving the web without third-party cookies", + "authors": [ + "Amy Guy" + ], + "href": "https://www.w3.org/2001/tag/doc/web-without-3p-cookies/", + "publisher": "W3C", + "id": "web-without-3p-cookies" } }, "publishISODate": "2023-06-28T00:00:00.000Z", @@ -1642,14 +1651,13 @@
These principles don't describe exactly how to distinguish acceptable - information from information we'd rather not expose. API designers instead - need to balance the harm to users from exposing information against the harm - to users from blocking that exposure. When in doubt, designers should ensure - that different user agents can help their users balance the costs in - different ways.
+Some functionality of the web has historically been provided using functional primitives (e.g. +third-party cookies) that can undermine people's privacy. As explained in Improving the web +without third-party cookies ([web-without-3p-cookies]), "It is better to approach [these +use cases] with replacement technologies that are designed-for-purpose and built to respect user +privacy."
The following subsections discuss how to review an API proposal that exposes data that
provides a new way to infer each of the above categories of information. They explain how
to leave the web better than you
@@ -2688,6 +2696,8 @@ Privacy Principles
Understanding Privacy. Daniel Solove. Harvard University Press. URL: https://www.hup.harvard.edu/catalog.php?isbn=9780674035072