In a bid to make your internet experience more secure, Google has introduced new policies that require extensions to request only the permissions needed to implement their features. Starting January 2021, each extension’s detail page on Google Chrome Web Store will also showcase developer-provided information on the data they collected by their extension. Developers can begin using data disclosure collection tool right away.  

COMMERCIAL BREAK
SCROLL TO CONTINUE READING

This will help users make a more informed decision about the extensions they want to install and use. Apart from a more detailed page, Google has also introduced an additional policy that aims to limit how extension developers access users’ data.  

“Today, we are announcing changes that build upon those protections with an update to our developer policy that limits what extension developers can do with the data they collect. The new policy also requires developers to certify their data use practices, and display that information directly on the Chrome Web Store listing to help users understand an extension’s privacy practices,” the tech giant said in a blog. 

The policy also reiterates developers cannot sell user data. It also bars the use of the data collected for personalised advertising. It also bars developers from using user data for “creditworthiness or any form of lending qualification and to data brokers or other information resellers.” 

Chrome extension pages will now also feature a display to inform users whether the developer has complied with the abovementioned policies or not. 

“Protecting users and their data is a fundamental aspect of the work we do on Chrome. Last year, as part of Google’s Project Strobe, we announced an important set of policies for extensions to protect users and their data. These policies require extensions to request only the permissions needed to implement their features. Additionally, we required more extensions to post privacy policies and handle user data securely,” Alexandre Blondin and Mark M. Jaycox, Chrome Product & Policy wrote in the blog.