From c81ac7f9470621ecb7623a07e810a0f5fefa65d3 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Wed, 31 Jul 2024 15:04:47 +0100 Subject: [PATCH 1/2] removing references to 3PCD --- README.md | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 29fc82c..43f649c 100644 --- a/README.md +++ b/README.md @@ -1,15 +1,14 @@ # PSAT Demos -PSAT Demos is a web application that showcases various demos and scenarios related to privacy sandbox. +PSAT Demos is a web application that showcases various demos and scenarios related to Privacy Sandbox. ## Description -PSAT Demos is a web application built using Node.js and Express. It demonstrates different privacy-related -technologies and scenarios through various demos and use cases. +PSAT Demos is a web application built using Node.js and Express. It demonstrates different privacy-related technologies and scenarios through various demos and use cases. The project is structured into two main sections: -1. **Demo Types**: These are categorized demos, each showcasing a specific privacy sandbox technology. +1. **Demo Types**: These are categorized demos showcasing a specific privacy sandbox technology. 2. **Scenarios**: These demos represent real-world scenarios where privacy technologies can be applied. ## Getting Started @@ -75,9 +74,7 @@ cookies as partitioned cookies tied to the top-level site where it's initially s ### **Analytics - Cross-Domain Tracking** -This demo showcases the ability to track user interactions using third-party cookies when third-party services are -utilized. The demo consists of three domains - a first-party domain utilizing a third-party service, another first-party -domain also utilizing the third-party service, and the third-party analytics service domain. +This demo showcases the ability to track user interactions using third-party cookies when third-party services are utilized. The demo consists of three domains - a first-party domain utilizing a third-party service, another first-party domain also utilizing the third-party service, and the third-party analytics service domain. **Domain Information** @@ -103,7 +100,7 @@ sequenceDiagram DomainB->>DomainC: Retrieves unique ID from cookie DomainC->>User: Recognizes as the same User - Note over User,DomainC: After Third-party Cookie Deprecation + Note over User,DomainC: After blocking third-party cookies User->>DomainA: Visits DomainA->>DomainC: Unable to assign unique ID @@ -151,7 +148,7 @@ sequenceDiagram DomainC->>DomainC: Fetches cart data from cookie DomainC->>User: Displays cart contents (Product 1 and Product 2) - Note over User,DomainC: After third-party cookie deprecation + Note over User,DomainC: After blocking third-party cookies User->>DomainA: Access homepage again DomainA->>User: Render homepage with embedded iframe to DomainC/products @@ -202,7 +199,7 @@ sequenceDiagram User->>YouTube: Observe "watch later" button presence - Note over User,YouTube: After third-party cookie deprecation + Note over User,YouTube: After blocking third-party cookies User->>DomainA: Navigate to DomainA/embedded-video DomainA->>YouTube: Load YouTube video @@ -254,7 +251,7 @@ sequenceDiagram DomainC->>DomainB: Confirm user is logged in DomainB->>User: Render profile page - Note over User,DomainC: After Third-Party Cookies Deprecation + Note over User,DomainC: After blocking third-Party cookies User->>DomainA: Visit domain-aaa.com DomainA->>User: Render sign-in page From ddeac32b1f125960e5a7e0c6fd99c88fb66fda29 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Wed, 31 Jul 2024 15:14:55 +0100 Subject: [PATCH 2/2] adding small fixes --- README.md | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index 43f649c..f7339b7 100644 --- a/README.md +++ b/README.md @@ -103,24 +103,24 @@ sequenceDiagram Note over User,DomainC: After blocking third-party cookies User->>DomainA: Visits - DomainA->>DomainC: Unable to assign unique ID + DomainA->>DomainC: Unable to assign a unique ID DomainC-->>User: Cannot store ID (no cookie) User->>DomainB: Visits - DomainB->>DomainC: Cannot retrieve unique ID + DomainB->>DomainC: Cannot retrieve the unique ID DomainC-->>User: Treats as a new User ``` ### **E-Commerce - Cross-Domain Shopping Cart** This demo showcases the use of third-party cookies to store shopping cart information across domains while -utilizing a third-party ecommerce service. The primary goal is to test whether third-party ecommerce services can +utilizing a third-party e-commerce service. The primary goal is to test whether third-party e-commerce services can still use third-party cookies to manage cart information across different domains. **Domain Setup** -* **domain-aaa.com** - First-party domain utilizing the third-party ecommerce service. -* **domain-bbb.com** - Another first-party domain also utilizing the third-party ecommerce service. -* **domain-ccc.com** - The third-party ecommerce service domain. +* **domain-aaa.com** - First-party domain utilizing the third-party e-commerce service. +* **domain-bbb.com** - Another first-party domain also utilizing the third-party e-commerce service. +* **domain-ccc.com** - The third-party e-commerce service domain. **Sequence Diagram** @@ -150,11 +150,11 @@ sequenceDiagram Note over User,DomainC: After blocking third-party cookies - User->>DomainA: Access homepage again + User->>DomainA: Access the homepage again DomainA->>User: Render homepage with embedded iframe to DomainC/products User->>DomainC: Clicks on "Add to cart" for Product 3 DomainC-->>DomainC: Cannot set/update cart cookie - DomainC->>User: Fails to update cart icon count or displays incorrect count + DomainC->>User: Fails to update cart icon count or displays the incorrect count User->>DomainB: Navigates to domain-bbb.com again DomainB->>User: Render homepage with embedded iframe to DomainC/products User->>DomainC: Observes cart icon with no items @@ -167,7 +167,7 @@ sequenceDiagram This demo is designed to showcase the behavior of third-party cookies within embedded content across different domains. We use an embedded YouTube video as an example of third-party content. The demonstration helps users and developers -understand how third-party cookies function when interacting with content embedded from other domains. +understand how third-party cookies function when interacting with content embedded in other domains. **Domains Used:** @@ -218,13 +218,12 @@ sequenceDiagram ### **Single Sign-On - Cross-Domain Single Sign-On** -This demo showcases a basic implementation of a Single Sign-On (SSO) scenario where third-party cookies are used to -share login information across different domains. +This demo showcases a basic implementation of a Single Sign-On (SSO) scenario where third-party cookies are used to share login information across different domains. **Domains Used:** -* **domain-aaa.com** - The first party domain using the third party service. -* **domain-bbb.com** - Another first party domain using the third party service. +* **domain-aaa.com** - The first-party domain using the third-party service. +* **domain-bbb.com** - Another first-party domain using the third-party service. * **domain-ccc.com** - The third-party single sign-on service. **Sequence Diagram**