Chrome9/5/2023 The □-anonymity server is an incremental step towards the full implementation of FLEDGE. With data being relayed through an OHTTP relay, Google □-anonymity servers do not receive the IP addresses of end users. This is why we are improving Chrome’s privacy measures by partnering with Fastly, an edge cloud platform that provides content delivery, edge compute, security, and observability services, to operate an Oblivious HTTP relay (OHTTP relay) as part of FLEDGE’s □-anonymity server. While the □-anonymity service provides a key privacy protection, it also could expose sensitive user data to this centralized server, such as IP address and the browser's User-Agent string. When requests for the ads are made to the advertising company, the IP address is visible to them. When sites request FLEDGE ads, Google's □-anonymity server ensures ads can only be shown if they pass the □-anonymity threshold. You can check out our explainer for further details on the □-threshold, and how the □-anonymity service is designed within FLEDGE. Once a creative meets the minimum threshold, it is cleared to be rendered to users. This protection is referred to as □-anonymity, and is enabled by a centralized server operated by Google that maintains global counts. This also helps protect users from cross-site tracking by preventing reporting rendered URLs that don't meet the minimum threshold. We will require a crowd of 50 users per creative within the past 7 days before the ad can be rendered. The browser will provide protection against microtargeting, by only rendering an ad if the same rendering URL is being shown to a sufficiently large number of people. FLEDGE is a Privacy Sandbox proposal to serve remarketing and custom audience use cases, designed with the intent of preventing third-parties from tracking user browsing behavior across sites.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |