{"id":53200,"date":"2025-03-24T02:42:06","date_gmt":"2025-03-24T06:42:06","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=53200"},"modified":"2025-03-24T02:42:06","modified_gmt":"2025-03-24T06:42:06","slug":"best-private-browser-in-2025","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/best-private-browser-in-2025\/53200\/","title":{"rendered":"Privacy under attack: nasty surprises in Chrome, Edge, and Firefox"},"content":{"rendered":"<p>Over the past few weeks, there\u2019s been a series of unpleasant news items on advertising and user privacy in with regard to every major browser developer \u2014 except Apple: Google allowing ad tracking through digital fingerprinting; powerful ad blockers ceasing to work in both Edge and Chrome, and Mozilla revising its license agreement seemingly showing far more interest in user data than it used to. What does each of these new developments mean, and how can we now achieve a high level of privacy?<\/p>\n<h2>Google greenlights tracking fingerprints<\/h2>\n<p>Driven by regulators and user pressure, the internet giant spent years working on ways to track ad performance and deliver relevant ads without using the outdated and much-hated tracking methods: <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-block-cookies-in-chrome-safari-firefox-edge\/43505\/\" target=\"_blank\" rel=\"noopener nofollow\">third-party cookies<\/a> and <a href=\"https:\/\/www.kaspersky.com\/blog\/rc3-fpmon-browser-fingerprinting\/38369\/\" target=\"_blank\" rel=\"noopener nofollow\">browser fingerprinting<\/a>. Google proposed <a href=\"https:\/\/www.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/49154\/\" target=\"_blank\" rel=\"noopener nofollow\">FLoC, Ad Topics, and Privacy Sandbox<\/a> as replacements, but they\u2019ve probably have fallen short of the target. Therefore, the company <a href=\"https:\/\/privacysandbox.com\/news\/privacy-sandbox-update\/\" target=\"_blank\" rel=\"nofollow noopener\">backtracked on removing support for third-party cookies<\/a> from Chrome. Meanwhile, Google\u2019s ad network, the world\u2019s most expansive, <a href=\"https:\/\/support.google.com\/platformspolicy\/answer\/15738904\" target=\"_blank\" rel=\"nofollow noopener\">has allowed<\/a> the collection of digital fingerprint data \u2014 <a href=\"https:\/\/support.google.com\/marketingplatform\/answer\/15732590?hl=en\" target=\"_blank\" rel=\"nofollow noopener\">including the user\u2019s IP address<\/a> \u2014 when displaying ads, as of February 2025. What this implies is that user browsers can be identified irrespective of cookie settings, incognito mode, or similar privacy measures. Digital fingerprinting is highly precise, and altering or disabling a fingerprint is a challenge.<\/p>\n<h2>Chrome and Edge pull the plug on extensions that block ads and tracking<\/h2>\n<p>Chrome is based on the open-source Chromium browser, which is fully financed by Google. You could say that Chrome is Chromium with Google services built into it, but dozens of other browsers \u2014 including Edge and Opera \u2014 are also based on Chromium.<\/p>\n<p>Chromium developers have been gradually transitioning the browser extension platform from the Manifest V2 framework to the new Manifest V3 for years. The platform consists of several components, but the most important is the complete list of functions and capabilities provided to the extension by the browser.<\/p>\n<p>V3 has several advantages, but it also cuts Chrome\/Edge\/Opera\/Vivaldi extensions off from certain useful features that are vital for content blockers. Although popular plug-ins such as uBlock Origin and Adblock Plus already have a Manifest V3 implementation, <a href=\"https:\/\/www.eff.org\/deeplinks\/2021\/12\/chrome-users-beware-manifest-v3-deceitful-and-threatening\" target=\"_blank\" rel=\"nofollow noopener\">only the V2 version does a good of job blocking ads<\/a>.<\/p>\n<p>The Chrome Web Store has long stopped approving extensions based on Manifest V2. Since late fall of 2024, new versions of Chrome first <a href=\"https:\/\/www.neowin.net\/news\/google-to-begin-phasing-out-manifest-v2-extensions-in-chrome-on-june-3\/\" target=\"_blank\" rel=\"nofollow noopener\">started displaying warnings<\/a> that installed Manifest V2 extensions had to be disabled, and then began to <a href=\"https:\/\/www.theregister.com\/2025\/02\/24\/google_v2_eol_v3_rollout\/\" target=\"_blank\" rel=\"nofollow noopener\">deactivate them automatically<\/a>. The user can still re-enable them, but it obviously won\u2019t last long.<\/p>\n<p>Microsoft Edge was <a href=\"https:\/\/www.neowin.net\/news\/microsoft-begins-turning-off-ublock-origin-and-other-extensions-in-edge\/\" target=\"_blank\" rel=\"nofollow noopener\">caught doing the same thing<\/a> in February. If Google\u2019s current plan holds, even enterprise Chrome users will see Manifest V2 extensions shut down by June 2025, which likely will be followed by Manifest V2 support pulled entirely from Chromium.<\/p>\n<p>What are the developers of dozens of Chromium-based browsers going to do? Well, they\u2019ll inevitably have to kill Manifest V2 support. And without it, your favorite ad blockers and privacy enhancers will stop working.<\/p>\n<h2>Mozilla sets its sights on the ad market, too<\/h2>\n<p>The non-profit Mozilla Foundation and its subsidiary Mozilla Corporation have always been in an awkward position, as their main source of income was partnerships with search engines \u2014 primarily Google. The current Mozilla management mainly consists of alumni from companies like Meta and eBay, which mainly rely on advertising for their revenue. It\u2019s hardly surprising that as of late, Firefox development updates have increasingly angered fans of the browser\u2019s privacy features.<\/p>\n<p>Since version 128, Firefox has incorporated the <a href=\"https:\/\/www.kaspersky.com\/blog\/mozilla-privacy-preserving-attribution-explained\/51997\/\" target=\"_blank\" rel=\"nofollow noopener\">Privacy-Preserving Attribution<\/a> (PPA) system, which it\u2019s testing in partnership with Facebook. And at the end of February 2025, the following notice appeared in the updated Firefox Terms of Use: \u201cWhen you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox\u201d.<\/p>\n<p>Users were <a href=\"https:\/\/connect.mozilla.org\/t5\/discussions\/an-update-on-our-terms-of-use\/m-p\/89041#M34394\" target=\"_blank\" rel=\"nofollow noopener\">furious<\/a>. They interpreted this clause as explicit permission to resell their data and introduce other forms of tracking. Under public pressure, Mozilla <a href=\"https:\/\/blog.mozilla.org\/en\/products\/firefox\/update-on-terms-of-use\/\" target=\"_blank\" rel=\"nofollow noopener\">amended the language<\/a> to \u201cYou give Mozilla the rights necessary to operate Firefox\u201d. The company\u2019s argument that it had merely codified something the browser was already doing \u2014 and actually always had \u2014 left users unconvinced. After all, suspicious changes also occurred in other parts of the FAQ: for example, clauses that promised Firefox would never sell data to advertisers were removed.<\/p>\n<p>That said, there were no <em>actual<\/em> changes to any of the browser\u2019s relevant functionality. So it\u2019s still safe to use Firefox for the time being. However, keep a close eye on any new features in each update. Consider disabling them or looking for an alternative to Firefox. If you want to be the first to know, subscribe to <a href=\"https:\/\/www.kaspersky.com\/blog\/subscribe\/\" target=\"_blank\" rel=\"noopener nofollow\">our blog<\/a>, or follow our <a href=\"https:\/\/t.me\/+hfDEDRUTiLJlOGE8\" target=\"_blank\" rel=\"noopener nofollow\">Telegram channel<\/a>.<\/p>\n<h2>Nothing changes with Apple\u2019s Safari<\/h2>\n<p>The vast majority of Apple users use the stock Safari browser, based on the WebKit engine. It has its own extension system \u2014 available through the App Store and utilizing Apple\u2019s special mechanisms for blocking content in the browser. While Safari might miss out on the most powerful extensions like uBlock Origin and NoScript, robust day-to-day tools for blocking ads and tracking are available both in the form of <a href=\"https:\/\/support.apple.com\/en-il\/guide\/safari\/sfri40732\/mac\" target=\"_blank\" rel=\"nofollow noopener\">Safari\u2019s standard settings<\/a> and extensions such as Ghostery.<\/p>\n<p>Apple continues to emphasize privacy as its key differentiator from other platforms, so no alarming concessions to the advertising industry have been observed in Safari. Unfortunately, although you can still install this browser on Windows, <a href=\"https:\/\/support.apple.com\/en-us\/102665\" target=\"_blank\" rel=\"nofollow noopener\">it stopped updating back in 2010<\/a>, so Windows users face a tough choice in the next section\u2026<\/p>\n<h2>The best browser for privacy protection in 2025<\/h2>\n<p>Starting in June, the popular browsers Chrome and Edge will become largely ineffective for privacy-minded users \u2014 no matter what extensions or settings they may have used. The same is true for most other Chromium-based browsers.<\/p>\n<p>As for Firefox, despite Mozilla\u2019s dubious statements, the browser still supports Manifest V2 extensions, and the developers have said they\u2019d <a href=\"https:\/\/blog.mozilla.org\/addons\/2024\/05\/14\/manifest-v3-updates\/\" target=\"_blank\" rel=\"nofollow noopener\">maintain this support<\/a> for the foreseeable future. Still, if you want to stop worrying about controversial features like \u201cattribution\u201d being turned on semi-covertly, you could always migrate to a browser that uses the Firefox source code but is more focused on keeping things private. The main options here are <a href=\"https:\/\/www.kaspersky.com\/blog\/what-you-need-to-know-about-tor-browser-and-anonymity\/52549\/\" target=\"_blank\" rel=\"noopener nofollow\">Tor Browser<\/a>, and popular Firefox forks such as Waterfox and LibreWolf.<\/p>\n<p>Despite its \u201cdark-web browser\u201d image, Tor Browser is also perfectly suitable for viewing ordinary websites \u2014 although its default privacy settings are so stringent they can cause many websites to display oddly or be partially non-functional. This is easy to fix by switching the cookie and script settings to a less paranoid mode.<\/p>\n<p>Waterfox is a reasonable middle-of-the-road between Firefox and Tor Browser: no developer telemetry, no built-in services like Pocket, and Firefox ESRs (extended support releases) are used as the source code. The downsides include a small development team, so Waterfox lags behind Mozilla in terms of security patches (although not by much).<\/p>\n<p>Focused on privacy, LibreWolf is positioned as Firefox without all the extras. The browser never \u201ccalls home\u201d (it excludes all types of manufacturer reports and telemetry), and it features the popular ad blocker uBlock Origin out of the box. LibreWolf closely follows Firefox in terms of updates, and it\u2019s available on Windows, macOS, and several flavors of Linux.<\/p>\n<p>The Chromium-based Brave browser, which has built-in privacy tools even before you add any extensions, remains a popular option. Its <a href=\"https:\/\/brave.com\/blog\/brave-shields-manifest-v3\/\" target=\"_blank\" rel=\"nofollow noopener\">developers have pledged<\/a> to keep a number of key Manifest V2 extensions on life support: AdGuard AdBlocker, NoScript, uBlock Origin, and uMatrix. However, Brave has several controversial extras, such as a built-in crypto wallet and an AI assistant named \u201cLeo\u201d.<\/p>\n<p>In short, there\u2019s no such thing as a perfect browser, but if you try ranking these options from the most private but least user-friendly to the easiest to use but still private, your chart should look like this: Tor Browser, LibreWolf, Waterfox, Brave, and Firefox.<\/p>\n<p>Any browser, except Tor and LibreWolf, will require a secure configuration and a couple of the aforementioned extensions to <a href=\"https:\/\/www.kaspersky.com\/blog\/web-beacons-explained-and-how-to-stop-them\/47281\/\" target=\"_blank\" rel=\"noopener nofollow\">block trackers and scripts<\/a> for maximum privacy.<\/p>\n<p>In Brave and Firefox, you can also enable \u201cTell websites not to sell or share my data\u201d \u2014 a feature established under the new <a href=\"https:\/\/globalprivacycontrol.org\/\" target=\"_blank\" rel=\"nofollow noopener\">Global Privacy Control<\/a> initiative. Certain jurisdictions, such as the European Union, the United Kingdom, California, Colorado, and Connecticut, legally require websites to respect this flag, but this safeguard is administrative rather than technical in nature.<\/p>\n<p>Your easiest option, and one that significantly enhances online privacy when using <em>any<\/em> browser, is installing a <a href=\"https:\/\/www.kaspersky.com\/home-security?icid=gl_kdailyplacehold_acq_ona_smm__onl_b2c_blo_lnk_sm-team______\" target=\"_blank\" rel=\"noopener nofollow\">Kaspersky security solution for home users<\/a>\u00a0and activating <a href=\"https:\/\/support.kaspersky.com\/kaspersky-for-windows\/21.20\/92436\" target=\"_blank\" rel=\"noopener\"><strong>Private Browsing<\/strong><\/a>. By default, the feature runs in detection mode only, without blocking anything: it detects, counts, and logs attempts at collecting data. If you activate blocking mode, data collection is blocked by default on all sites, with the following exceptions:<\/p>\n<ul>\n<li>webites you\u2019ve added as exclusions<\/li>\n<li>Kaspersky and its partner websites<\/li>\n<li>websites that we know may be rendered inoperable as a result of tracking services being blocked<\/li>\n<\/ul>\n<p>You can still configure the component to block data collection on the above sites too. <strong>Private Browsing<\/strong> <a href=\"https:\/\/support.kaspersky.com\/kaspersky-for-windows\/21.20\/93724\" target=\"_blank\" rel=\"noopener\">has certain limitations<\/a>. You can manage it both from the Kaspersky application and using the Kaspersky Protection extension for most browsers.<\/p>\n<blockquote><p>Want to learn more about how browsers track your activity and how to minimize this tracking? More on the topic:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/private-browsers-beginners-guide\/48066\/\" target=\"_blank\" rel=\"noopener nofollow\">Private browsers: a beginner\u2019s guide<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-control-your-cookies\/43303\/\" target=\"_blank\" rel=\"noopener nofollow\">How to control cookies: A real-world experiment<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-block-cookies-in-chrome-safari-firefox-edge\/43505\/\" target=\"_blank\" rel=\"noopener nofollow\">How to block cookies in your browser<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/rc3-fpmon-browser-fingerprinting\/38369\/\" target=\"_blank\" rel=\"noopener nofollow\">How to tell if a website is taking your (browser) fingerprints<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/adult-content-privacy-security\/35315\/\" target=\"_blank\" rel=\"noopener nofollow\">How to watch porn safely and discreetly<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/googerteller-sound-of-trackers\/51186\/\" target=\"_blank\" rel=\"noopener nofollow\">The sound of online trackers<\/a><\/li>\n<\/ul>\n<\/blockquote>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-geek\">\n","protected":false},"excerpt":{"rendered":"<p>How to counter new privacy invasions by browser developers<\/p>\n","protected":false},"author":2722,"featured_media":53201,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1788,9],"tags":[810,1278,16,404,2745,1499,21,22,38,43,1202,768,131,812],"class_list":{"0":"post-53200","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"category-tips","9":"tag-ads","10":"tag-browsers","11":"tag-chrome","12":"tag-cookies","13":"tag-edge","14":"tag-extensions","15":"tag-firefox","16":"tag-google","17":"tag-microsoft","18":"tag-privacy","19":"tag-private-browsing","20":"tag-surveillance","21":"tag-tips","22":"tag-tracking"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/best-private-browser-in-2025\/53200\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/best-private-browser-in-2025\/28690\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/best-private-browser-in-2025\/23929\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/best-private-browser-in-2025\/12337\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/best-private-browser-in-2025\/28806\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/best-private-browser-in-2025\/28007\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/best-private-browser-in-2025\/30846\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/best-private-browser-in-2025\/29543\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/best-private-browser-in-2025\/39272\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/best-private-browser-in-2025\/13233\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/best-private-browser-in-2025\/22668\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/best-private-browser-in-2025\/23519\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/best-private-browser-in-2025\/32028\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/best-private-browser-in-2025\/28958\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/best-private-browser-in-2025\/34755\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/best-private-browser-in-2025\/34384\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/browsers\/","name":"browsers"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/53200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2722"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=53200"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/53200\/revisions"}],"predecessor-version":[{"id":53204,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/53200\/revisions\/53204"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/53201"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=53200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=53200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=53200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}