{"id":23185,"date":"2024-08-19T19:22:35","date_gmt":"2024-08-19T15:22:35","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/?p=23185"},"modified":"2024-08-19T19:22:35","modified_gmt":"2024-08-19T15:22:35","slug":"mozilla-privacy-preserving-attribution-explained","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/mozilla-privacy-preserving-attribution-explained\/23185\/","title":{"rendered":"Privacy-Preserving Attribution technology by Mozilla"},"content":{"rendered":"<p>In July 2024, with the <a href=\"https:\/\/www.mozilla.org\/en-US\/firefox\/128.0\/releasenotes\/\" target=\"_blank\" rel=\"nofollow noopener\">latest version<\/a> of its Firefox browser, Mozilla introduced a technology called Privacy-Preserving Attribution (PPA) \u2014 designed to track how effective online advertising is. The feature is enabled by default in Firefox 128.<\/p>\n<p>This has already caught the eye of online privacy advocates, and led to headlines like \u201cNow Mozilla too is selling user data\u201d. The clamor got so loud that Firefox CTO, Bobby Holley, had to <a href=\"https:\/\/old.reddit.com\/r\/firefox\/comments\/1e43w7v\/a_word_about_private_attribution_in_firefox\/\" target=\"_blank\" rel=\"nofollow noopener\">take to Reddit<\/a> to explain to users what Mozilla actually did and why.<\/p>\n<p>Now\u2019s the time to take a closer look at what PPA is, why it\u2019s needed in the first place, and why it\u2019s appeared now.<\/p>\n<h2>Google Ad Topics and Facebook Link History<\/h2>\n<p>First, a bit of backstory. As you may recall, way back in 2019 the developers of the world\u2019s most popular browser \u2014 Google Chrome \u2014 began hatching plans to completely disable support for third-party cookies.<\/p>\n<p>These tiny files have been tracking user actions online for 30 years now. The technology is both the backbone of the online advertising industry, and the chief <a href=\"https:\/\/www.kaspersky.com\/blog\/googerteller-sound-of-trackers\/51186\/\" target=\"_blank\" rel=\"noopener nofollow\">means of violating users\u2019 privacy<\/a>.<\/p>\n<p>Some time ago, as a replacement, Google unveiled an in-house development called <a href=\"https:\/\/www.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/49154\/\" target=\"_blank\" rel=\"noopener nofollow\">Ad Topics<\/a>. With this technology, tracking is based on users\u2019 Chrome browser history, and interaction history with Android apps. The rollout of Ad Topics was expected to be followed by the phasing out of support for third-party cookies in Chrome in H2 2024.<\/p>\n<p>Another major digital advertising player to develop its own user-tracking technology is Meta, which likewise relies on third-party cookies. Called <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-turn-off-facebook-link-history\/50328\/\" target=\"_blank\" rel=\"noopener nofollow\">Link History<\/a>, it makes sure that all external links in the Facebook mobile apps now get opened in its built-in browser \u2014 where the company can still snoop on your actions.<\/p>\n<p>The bottom line is that ending support for third-party cookies hands even more control over to Google and Meta \u2014 owner of the world\u2019s most popular browser and mobile OS, and of the world\u2019s most popular social network, respectively \u2014 while smaller players will become even more dependent on them.<\/p>\n<p>At the same time, user data continues to be collected on an industrial scale, and primarily by the usual suspects when it comes to claims of privacy violation: yes, Google and Facebook.<\/p>\n<p>The question arises: is it not possible to develop some mechanism to allow advertisers to track the effectiveness of advertising without mass collection of user data? The answer comes in the shape of Privacy-Preserving Attribution.<\/p>\n<h2>Meet Prio, a privacy-preserving aggregation system<\/h2>\n<p>To better understand the history of this technology, we have to go back a bit in time \u2014 to 2017, when cryptographers Henry Corrigan-Gibbs and Dan Boneh of Stanford University presented a <a href=\"https:\/\/crypto.stanford.edu\/prio\/paper.pdf\" target=\"_blank\" rel=\"nofollow noopener\">research paper<\/a>. In it, they described a privacy-oriented system for collecting aggregated statistics, which they called Prio.<\/p>\n<p>To greatly simplify matters, Prio is based on the following mechanism. Let\u2019s say you\u2019re interested in the average age of a certain number of users, but you want to preserve their privacy. You set up two (or more) piggy banks and ask each user to count out the number of coins corresponding to their age and, without showing them to anyone, randomly drop the coins into different money boxes.<\/p>\n<p>Then you tip the coins out of the piggy banks into a pile, count them and divide by the number of users. The result is what you wanted: the average age of the users. And if at least one of the piggy banks keeps its secret (i.e., doesn\u2019t tell anyone what went into it), then it\u2019s impossible to determine how many coins any one user put into the boxes.<\/p>\n<div id=\"attachment_52001\" style=\"width: 1940px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2024\/08\/19191327\/mozilla-privacy-preserving-attribution-explained-01.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-52001\" class=\"size-full wp-image-52001\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2024\/08\/19191327\/mozilla-privacy-preserving-attribution-explained-01.png\" alt=\"Prio's operating principle \" width=\"1930\" height=\"400\"><\/a><p id=\"caption-attachment-52001\" class=\"wp-caption-text\">Prio\u2019s main stages of information processing. <a href=\"https:\/\/crypto.stanford.edu\/prio\/paper.pdf\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>Prio overlays this basic mechanism with a lot of cryptography to protect information from interception and ensure the validity of data received. There\u2019s no way for users to slip answers into the system, for whatever reason, that could distort the results. The main concept lies in the use of two or more aggregators that collect random shares of the sought information.<\/p>\n<p>Prio\u2019s algorithms have another key feature: they greatly improve system performance compared to previous methods of reliable anonymized data collection \u2014 by 50\u2013100 times, say the researchers.<\/p>\n<h2>Distributed Aggregation Protocol<\/h2>\n<p>Mozilla got interested in Prio back in 2018. The first fruit of this interest was its <a href=\"https:\/\/blog.mozilla.org\/security\/2019\/06\/06\/next-steps-in-privacy-preserving-telemetry-with-prio\/\" target=\"_blank\" rel=\"nofollow noopener\">development of the experimental system<\/a> Firefox Origin Telemetry \u2014 based on Prio. Notably, this system was designed to privately gather telemetry on the browser\u2019s ability to combat ad trackers.<\/p>\n<p>Then, in February 2022, Mozilla <a href=\"https:\/\/blog.mozilla.org\/en\/mozilla\/privacy-preserving-attribution-for-advertising\/\" target=\"_blank\" rel=\"nofollow noopener\">unveiled<\/a> Interoperable Private Attribution (IPA) technology, developed jointly with Meta, which, it seems, served as the prototype to PPA.<\/p>\n<p>May 2022 saw the <a href=\"https:\/\/www.ietf.org\/archive\/id\/draft-ietf-ppm-dap-02.html\" target=\"_blank\" rel=\"nofollow noopener\">publication<\/a> of a zero draft of the Prio-based Distributed Aggregation Protocol (DAP). The draft was authored by representatives of Mozilla and the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Internet_Security_Research_Group\" target=\"_blank\" rel=\"nofollow noopener\">Internet Security Research Group (ISRG)<\/a> \u2014 a non-profit known for the Let\u2019s Encrypt project to democratize the use of HTTPS \u2014 as well as two Cloudflare employees.<\/p>\n<p>While working on the protocol, ISRG was also building a DAP-based system for collecting anonymized statistics, known as <a href=\"https:\/\/divviup.org\/about\/\" target=\"_blank\" rel=\"nofollow noopener\">Divvi Up<\/a>. This system is primarily intended to collect various technical telemetry to improve website performance, such as page load-time.<\/p>\n<div id=\"attachment_52002\" style=\"width: 1610px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2024\/08\/19191355\/mozilla-privacy-preserving-attribution-explained-02.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-52002\" class=\"wp-image-52002 size-full\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2024\/08\/19191355\/mozilla-privacy-preserving-attribution-explained-02.png\" alt=\"DAP operating principle \" width=\"1600\" height=\"450\"><\/a><p id=\"caption-attachment-52002\" class=\"wp-caption-text\">Schematic of the basic operating principle of the DAP protocol. <a href=\"https:\/\/divviup.org\/blog\/horizontal\/\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>Finally, in October 2023, <a href=\"https:\/\/divviup.org\/blog\/divvi-up-in-firefox\/\" target=\"_blank\" rel=\"nofollow noopener\">Divvi Up<\/a> and <a href=\"https:\/\/blog.mozilla.org\/en\/products\/firefox\/partnership-ohttp-prio\/\" target=\"_blank\" rel=\"nofollow noopener\">Mozilla<\/a> announced a collaboration to implement DAP in the Firefox browser. As part of this joint effort, a system of two aggregators was created \u2014 one of which operates on the Mozilla side, the other on the Divvi Up side.<\/p>\n<h2>How PPA works<\/h2>\n<p>It\u2019s this Divvi Up\/Mozilla system that\u2019s currently being <a href=\"https:\/\/support.mozilla.org\/en-US\/kb\/privacy-preserving-attribution\" target=\"_blank\" rel=\"nofollow noopener\">deployed<\/a> with PPA technology. So far, it\u2019s just an experiment involving a limited number of sites.<\/p>\n<p>In general outline, it works as follows:<\/p>\n<ul>\n<li>The website asks the browser to remember instances of successful ad views.<\/li>\n<li>If the user performs some action that the site considers useful (for example, buys a product), the site queries the browser to find out if the user saw the ad.<\/li>\n<li>The browser doesn\u2019t tell the site anything, but sends information through the DAP protocol to the aggregation servers.<\/li>\n<li>All such reports are accumulated in aggregators, and the site periodically receives a summary.<\/li>\n<\/ul>\n<p>As a result, the site learns that out of <em>X<\/em> number of users who saw a certain ad, <em>Y<\/em> number of users performed actions deemed useful for the site. But neither the site nor the aggregation system knows anything about who these users were, what else they did online, etc.<\/p>\n<h2>Why we need PPA<\/h2>\n<p>In the above-mentioned <a href=\"https:\/\/old.reddit.com\/r\/firefox\/comments\/1e43w7v\/a_word_about_private_attribution_in_firefox\/\" target=\"_blank\" rel=\"nofollow noopener\">statement on Reddit<\/a>, Firefox\u2019s CTO explained what Mozilla was aiming for by introducing PPA along with the new version of its browser.<\/p>\n<p>The company\u2019s reasoning is roughly the following. Online advertising, at least at this stage of the internet\u2019s development, is a necessary evil. And it\u2019s understandable that advertisers want to be able to measure its effectiveness. But the tools currently used for this disregard user privacy.<\/p>\n<p>Meanwhile, any talk about how to somehow restrict advertisers\u2019 tracking of users\u2019 actions is met with protests from the former. No data collection, they argue, means they\u2019re deprived of a tool for assessing online advertising.<\/p>\n<p>Basically, PPA is an experimental tool that allows advertisers to get the feedback they need without collecting and storing data on what users did.<\/p>\n<p>If the experiment shows the technology can satisfy advertisers\u2019 needs, it will give privacy advocates a weighty argument in future dealings with regulators and lawmakers. Broadly speaking, it will prove that total online surveillance is unnecessary, and should be limited by law.<\/p>\n<h2>Block third-party cookies now<\/h2>\n<p>As it happens, almost immediately after the uproar surrounding Mozilla\u2019s new rollout, Google <a href=\"https:\/\/privacysandbox.com\/news\/privacy-sandbox-update\/\" target=\"_blank\" rel=\"nofollow noopener\">announced<\/a> a complete reversal of its plans to disable third-party cookies. Getting rid of stale technology can be harder than it might seem \u2014 as Microsoft found out when trying to <a href=\"https:\/\/www.kaspersky.com\/blog\/zero-day-in-internet-explorer\/51698\/\" target=\"_blank\" rel=\"noopener nofollow\">bury Internet Explorer<\/a>.<\/p>\n<p>The good news is that, unlike Internet Explorer, which is indeed hard to weed out of Windows, third-party cookies are something that users can handle on their own. All modern browsers make it easy to block them \u2014 see our <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-block-cookies-in-chrome-safari-firefox-edge\/43505\/\" target=\"_blank\" rel=\"noopener nofollow\">guide for full details<\/a>.<\/p>\n<p>Bear in mind that Google\u2019s refusal to get rid of cookies doesn\u2019t spell the end of Ad Topics \u2014 the company intends to continue the experiment. So we recommend disabling this feature too, and <a href=\"https:\/\/www.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/49154\/\" target=\"_blank\" rel=\"noopener nofollow\">here\u2019s<\/a> how to do it in Chrome and Android.<\/p>\n<p>And if you use the Facebook mobile app, it\u2019s worth turning off Link History. Again, <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-turn-off-facebook-link-history\/50328\/\" target=\"_blank\" rel=\"noopener nofollow\">our guide explains how<\/a>.<\/p>\n<p>Also, you can and should make use of the Private Browsing feature in our <a href=\"https:\/\/me-en.kaspersky.com\/standard?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kstand___\" target=\"_blank\" rel=\"noopener\">Kaspersky Standard<\/a>, <a href=\"https:\/\/me-en.kaspersky.com\/plus?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kplus___\" target=\"_blank\" rel=\"noopener\">Kaspersky Plus<\/a> and <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">Kaspersky Premium<\/a> subscription plans to block ad trackers (by no means all of which use cookies).<\/p>\n<p>Lastly, we recommend using our free <a href=\"https:\/\/privacy.kaspersky.com\" target=\"_blank\" rel=\"nofollow noopener\">Privacy Checker<\/a> service, where you can find instructions on setting up privacy for the most common applications, services and social networks for different operating systems.<\/p>\n<p>As for PPA, the technology looks pretty useful. If you think otherwise, <a href=\"https:\/\/support.mozilla.org\/en-US\/kb\/privacy-preserving-attribution\" target=\"_blank\" rel=\"nofollow noopener\">here<\/a> are simple instructions to disable it in Firefox. As for me, I prefer to support the development of this technology, so will continue to use it in my browser.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-geek\">\n","protected":false},"excerpt":{"rendered":"<p>In the wake of Google and Facebook, Mozilla has introduced its own technology for replacing third-party cookies: let&#8217;s take a look at how privacy-preserving attribution works.<\/p>\n","protected":false},"author":2726,"featured_media":23187,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1225,1226],"tags":[781,1172,1636,16,2540,404,20,21,22,135,43,1144,783],"class_list":{"0":"post-23185","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"category-technology","9":"tag-ads","10":"tag-advertising","11":"tag-browsers","12":"tag-chrome","13":"tag-cookie","14":"tag-cookies","15":"tag-facebook","16":"tag-firefox","17":"tag-google","18":"tag-mozilla","19":"tag-privacy","20":"tag-technologies","21":"tag-tracking"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/mozilla-privacy-preserving-attribution-explained\/23185\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/mozilla-privacy-preserving-attribution-explained\/27889\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/mozilla-privacy-preserving-attribution-explained\/12030\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/mozilla-privacy-preserving-attribution-explained\/28066\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/mozilla-privacy-preserving-attribution-explained\/27617\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/mozilla-privacy-preserving-attribution-explained\/30316\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/mozilla-privacy-preserving-attribution-explained\/29160\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/mozilla-privacy-preserving-attribution-explained\/38076\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/mozilla-privacy-preserving-attribution-explained\/12665\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/mozilla-privacy-preserving-attribution-explained\/51997\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/mozilla-privacy-preserving-attribution-explained\/22125\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/mozilla-privacy-preserving-attribution-explained\/22894\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/mozilla-privacy-preserving-attribution-explained\/31606\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/mozilla-privacy-preserving-attribution-explained\/37019\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/mozilla-privacy-preserving-attribution-explained\/28204\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/mozilla-privacy-preserving-attribution-explained\/33998\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/mozilla-privacy-preserving-attribution-explained\/33661\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/privacy\/","name":"privacy"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23185","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2726"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=23185"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23185\/revisions"}],"predecessor-version":[{"id":23188,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23185\/revisions\/23188"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/23187"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=23185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=23185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=23185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}