User Tracking - Revision history

Tom: /* Other Material */

2025-06-12T01:38:13Z

‎Other Material

2025-06-12T01:35:40Z

‎References

2025-05-15T20:47:37Z

‎European Approach

2025-05-15T20:46:17Z

‎OpenID impact

2025-05-10T15:52:42Z

‎Terminology

2025-05-10T15:51:52Z

‎Terminology

2025-05-10T15:49:35Z

‎Context

2025-05-10T15:44:04Z

‎Google Analytics (GA4)=

2025-05-10T15:43:39Z

‎Context

2025-05-10T15:41:29Z

‎Full Title or Meme

@@ Line 65: / Line 65: @@
 ===Other Material===
 * See wiki on [[Tracking Devices]]
 [[Category: User Experience]]
 [[Category: Browser]]
 [[Category: Privacy]]

@@ Line 62: / Line 62: @@
 ==References==
 [[Category: User Experience]]
 [[Category: Browser]]
 [[Category: Privacy]]

@@ Line 44: / Line 44: @@
 # The user asked to have the account closed. - unknown impact.
 ===European Approach===
-* 2025-05-14 EU ruling: tracking-based advertising by Google, Microsoft, Amazon, X, across Europe has no legal basis
+* 2025-05-14 EU ruling: tracking-based advertising by Google, Microsoft, Amazon, X, across Europe has no legal basis [https://www.iccl.ie/wp-content/uploads/2025/05/Arrest-Marktenhof-14-05-2025-en.pdf Download the judgement in English (machine translation)]
 ** GDPR Article 5(1)f, Article 25, and Article 32 = The Court found that TCF fails to ensure personal data are kept secure and confidential
 ** GDPR Article 5(1)a and Article 6 - The Court found that fails to properly request consent. It also finds that the TCF may use legitimate interest, which is not permissible because of the severe risk posed by online tracking-based "Real-Time Bidding" advertising
 ** GDPR Articles 12, 13, and 14 - The Court found that TCF fails to provide transparency about data processing
 ===OpenID impact===
 * As written [[OpenID Connect]] has no problems with the elimination of user tracking as it is all 1P. The problem arises when a redirect occurs as the cookie deposited on the user's [[Browser]] is expected to be available to a 3P client. See following section for impact on Federation connection sign-in.

@@ Line 43: / Line 43: @@
 # The user is asked for demographics besides the call-back. The is now a PII CONTROLLER and assumes lots of responsibility. (The user state in the web site changes to "PII PRINCIPAL", browser doesn't understand.)
 # The user asked to have the account closed. - unknown impact.
 ===OpenID impact===
 * As written [[OpenID Connect]] has no problems with the elimination of user tracking as it is all 1P. The problem arises when a redirect occurs as the cookie deposited on the user's [[Browser]] is expected to be available to a 3P client. See following section for impact on Federation connection sign-in.

@@ Line 17: / Line 17: @@
 # Second Party (2P) = actions by a native app on the user's device.
 # Third Party (3P) = some other web site brought onto the UX via the 1P.
-# Data Broker = a company whose primary purpose is collecting data for sale to others. It can include all of the above methods.
+# Data Broker = a company whose primary purpose is collecting data for sale to others. It can use any of the above methods.
 Distributed Tracking is, for example, when the user has a device, like a smartphone, that can track the user that is not centralized until an infection individual is identified.

@@ Line 14: / Line 14: @@
 ===Terminology===
 Just to be sure we are all talking about the same thing for at least the duration of this wiki page. The designation for first party (1P) is very web-centric, but seems common, so let's stick with it.
-# First Party (1P) - the web site the user navigated to.
+# First Party (1P) = the web site the user navigated to.
-# Second Party (2P) - actions by a native app on the user's device.
+# Second Party (2P) = actions by a native app on the user's device.
-# Third Party (3P) - some other web site brought onto the UX via the 1P.
+# Third Party (3P) = some other web site brought onto the UX via the 1P.
 Distributed Tracking is, for example, when the user has a device, like a smartphone, that can track the user that is not centralized until an infection individual is identified.

@@ Line 3: / Line 3: @@
 ==Context==
-* This wiki page deals exclusively with the [[User Experience]] (UX) of a web browser chosen by the user to navigate the web. And by UX is meant the entire experience including that may happen months later from some some action that the user took in the past.
+* This wiki page deals primarily with the [[User Experience]] (UX) of a web browser chosen by the user to navigate the web.
 * Some comments and terminology my need to be framed in terms of the behavior of the web site in that [[User Experience]] in order to understand the entirety of the problem.
 * REST, or representative State

@@ Line 48: / Line 48: @@
 ===Death of Third Party Cookies===
-===Google Analytics (GA4)====
+===Google Analytics (GA4)===
 * [https://www.digitl.net/insights/mastering-cross-domain-tracking Mastering Cross-Domain Tracking in GA4: A Simplified Approach] 2024-01-04

@@ Line 8: / Line 8: @@
 * Tracking can be a huge benefit to society for problems like epidemic control, until suddenly it become a huge liability when it is used for governmental control of citizens.
 ** [https://www.youtube.com/watch?v=xjn36ZMMTpI&feature=emb_logo See the ethnographic study of COVID-19.]
-* It is also possible to use [[Device Tracking]] which used a smart phone, computer or tag as a stand-in for a user identifier.  Click on the link for details.
+* It is also possible to use [[Tracking Devices]] which ubckye a smart phone, computer or tag as a stand-in for a user identifier.  Click on the link for details.
 ===Terminology===
 Just to be sure we are all talking about the same thing for at least the duration of this wiki page. The designation for first party (1P) is very web-centric, but seems common, so let's stick with it.

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-Nearly all [[Website]]s track users at some level. There is generally some level at which users object which is dependent on the site's behavior.
+Nearly all [[Web Site]]s track users at some level. There is generally some level at which users object which is dependent on the site's behavior.
 ==Context==