Google password manager overrides third-party autofill

❗Article Status Notice: This Article is a stub

---

This article is underdeveloped, and needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Learn more ▼

Issues may include:

• This article needs to be expanded to provide meaningful information
• This article requires additional verifiable evidence to demonstrate systemic impact
• More documentation is needed to establish how this reflects broader consumer protection concerns
• The connection between individual incidents and company-wide practices needs to be better established
• The article is simply too short, and lacks sufficient content

How you can help:

• Add documented examples with verifiable sources
• Provide evidence of similar incidents affecting other consumers
• Include relevant company policies or communications that demonstrate systemic practices
• Link to credible reporting that covers these issues
• Flesh out the article with relevant information

This notice will be removed once the article is sufficiently developed. Once you believe the article is ready to have its notice removed, please visit the Moderator's noticeboard, or the Discord (join here) and post to the #appeals channel, or mention its status on the article's talk page.

Users of the Google Chrome Android app have reported that Google's password manager has blocked alternate password managers to be used on Chrome. This does not occur on other Android web browsers or on phones without android.

Background

Google's password manager is used for storing passwords to autofill. This has competition, with other companies making their own password managers. This leads to healthy competition, where consumers have a variety of password managers to choose from.

Consumer response

Consumers have voiced their concerns over this, often not noticing that Google is the one blocking their password manager.