First-Party Sets User Education

[MatiasLFranco]

We recommend that Chrome educate users about the First-Party Sets proposal. There is a risk that users will not understand how information is shared across domains within a First-Party Set. This could lead to users feeling that their privacy is being compromised, even though it is not.

This will also help to minimize the ecosystem's feeling that users will not understand how information is shared across domains within a First-Party Set and help the ecosystem to approve a larger number of domains in the Associated Subset.

A best-in-class example of this was the transition from HTTP to HTTPS. Chrome was very clear with users (e.g. using a different color lock icon in the address bar) and website owners about the benefits of HTTPS, and this helped to drive adoption of the new standard.

A well-run education program could incentivize companies to adopt the First-Party Sets API. By giving users confidence that their information is being shared by companies that have openly declared a set of domains, more companies would see the value in adopting the API. This could be a strong signal for users, indicating that the website they are visiting is part of a larger organization. This would allow users to make more informed decisions about the websites they visit.

For example, if a user is visiting a website that they are not familiar with, they may want to know if the website is part of a larger organization. This information could help the user to assess the trustworthiness of the website.

This is just my two cents, I'm no expert, but I thought it would be worth sharing...