Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Brave
Brave Browser release info
Message
<blockquote data-quote="oldschool" data-source="post: 866768" data-attributes="member: 71262"><p>Here's some informative post from the Brave Community:</p><p></p><p>Specifically re: Google Tag Manager</p><ul> <li data-xf-list-type="ul">Privacy and security risks in permitting 3rd party network requests to Google through the Google Tag Manager service, within the Google Marketing Platform.</li> <li data-xf-list-type="ul">The request to Google’s marketing servers is made without the user being aware of the invocation.</li> <li data-xf-list-type="ul">For added context, these are the measures we take to protect the user from leaking network requests to Google from the core browser code: <a href="https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)#what-chromium-features-are-removed-for-privacysecurity-reasons" target="_blank">brave/brave-browser</a></li> </ul><p>Addt’l security and privacy issues from custom script execution through GTM services:</p><ul> <li data-xf-list-type="ul"><a href="https://blog.sucuri.net/2018/04/malicious-activities-google-tag-manager.html" target="_blank">https://blog.sucuri.net/2018/04/malicious-activities-google-tag-manager.html</a></li> <li data-xf-list-type="ul"><a href="https://blog.littledata.io/2018/11/24/stop-gtm-being-hacking/" target="_blank">https://blog.littledata.io/2018/11/24/stop-gtm-being-hacking/ 1</a></li> </ul><p><strong>More broadly re: publisher tag solutions, options, etc.</strong></p><p>Brave ships with strong default privacy protection from multiple levels, but the user has agency over their global and site-level protection settings. We make these settings accessible from the URL bar, and include a link directly to global settings.</p><p>Our users expect a stronger level of default privacy protection and security from our product, and our mission is to execute and deliver new business lines that can operate and scale with the platform.</p><p>The first-order is to provide default privacy in a way that can scale for mainstream users without wrecking the experience.</p><p>In parallel, we’ve introduced <a href="https://github.com/brave/brave-browser/wiki/Security-and-privacy-model-for-ad-confirmations" target="_blank">new alternative protocols</a>, and deployed them across millions of browsers in the wild. This is the groundwork that can help drive broader privacy protocol adoption, but the fundamentals must function for users first. Otherwise, we’d likely be on a short path to being the neatest science experiment for privacy collecting dust on a shelf.</p><p>As we scale, the growth becomes of higher interest to publishers, and becomes a forcing-function to continue to adapt existing platforms to accept new protocols. We’re already doing this from the advertising side. We have +400K creators and publishers that have verified to accept revenue from our platform (<a href="https://batgrowth.com/" target="_blank">https://batgrowth.com 1</a>). Interest and experimentation from publishers has been growing with our user base.</p><p>There are a handful of different privacy approaches being introduced in-market. iTP has an impact in a major way. Google is trying a lighter approach. We have been consistently leading and executing on one of the strongest privacy approaches, and are aiming to prove out the revenue model for publishers at scale, as we scale.</p><p>Hope this wasn’t too vague, but the privacy model is a bit different. Hope it helps with context.</p></blockquote><p></p>
[QUOTE="oldschool, post: 866768, member: 71262"] Here's some informative post from the Brave Community: Specifically re: Google Tag Manager [LIST] [*]Privacy and security risks in permitting 3rd party network requests to Google through the Google Tag Manager service, within the Google Marketing Platform. [*]The request to Google’s marketing servers is made without the user being aware of the invocation. [*]For added context, these are the measures we take to protect the user from leaking network requests to Google from the core browser code: [URL="https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)#what-chromium-features-are-removed-for-privacysecurity-reasons"]brave/brave-browser[/URL] [/LIST] Addt’l security and privacy issues from custom script execution through GTM services: [LIST] [*][URL]https://blog.sucuri.net/2018/04/malicious-activities-google-tag-manager.html[/URL] [*][URL='https://blog.littledata.io/2018/11/24/stop-gtm-being-hacking/']https://blog.littledata.io/2018/11/24/stop-gtm-being-hacking/ 1[/URL] [/LIST] [B]More broadly re: publisher tag solutions, options, etc.[/B] Brave ships with strong default privacy protection from multiple levels, but the user has agency over their global and site-level protection settings. We make these settings accessible from the URL bar, and include a link directly to global settings. Our users expect a stronger level of default privacy protection and security from our product, and our mission is to execute and deliver new business lines that can operate and scale with the platform. The first-order is to provide default privacy in a way that can scale for mainstream users without wrecking the experience. In parallel, we’ve introduced [URL='https://github.com/brave/brave-browser/wiki/Security-and-privacy-model-for-ad-confirmations']new alternative protocols[/URL], and deployed them across millions of browsers in the wild. This is the groundwork that can help drive broader privacy protocol adoption, but the fundamentals must function for users first. Otherwise, we’d likely be on a short path to being the neatest science experiment for privacy collecting dust on a shelf. As we scale, the growth becomes of higher interest to publishers, and becomes a forcing-function to continue to adapt existing platforms to accept new protocols. We’re already doing this from the advertising side. We have +400K creators and publishers that have verified to accept revenue from our platform ([URL='https://batgrowth.com/']https://batgrowth.com 1[/URL]). Interest and experimentation from publishers has been growing with our user base. There are a handful of different privacy approaches being introduced in-market. iTP has an impact in a major way. Google is trying a lighter approach. We have been consistently leading and executing on one of the strongest privacy approaches, and are aiming to prove out the revenue model for publishers at scale, as we scale. Hope this wasn’t too vague, but the privacy model is a bit different. Hope it helps with context. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
