<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Iii</id>
	<title>Consumer Rights Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Iii"/>
	<link rel="alternate" type="text/html" href="https://consumerrights.wiki/w/Special:Contributions/Iii"/>
	<updated>2026-06-06T18:37:24Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Mark_Zuckerberg&amp;diff=56313</id>
		<title>Mark Zuckerberg</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Mark_Zuckerberg&amp;diff=56313"/>
		<updated>2026-06-06T01:11:10Z</updated>

		<summary type="html">&lt;p&gt;Iii: linked FTC and added intro to abbreviation, changed to &amp;quot;Reflist&amp;quot; template, and minor formatting changes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{InfoboxPerson&lt;br /&gt;
| Name = Mark Zuckerberg&lt;br /&gt;
| Nationality = American&lt;br /&gt;
| DOB  = 1984-05-14&lt;br /&gt;
| Industry = Social media&lt;br /&gt;
| Official website = https://www.facebook.com/zuck&lt;br /&gt;
| Image = Mark Zuckerberg.jpg&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;[[wikipedia:Mark_Zuckerberg|Mark Elliot Zuckerberg]]&#039;&#039; was born on May 14, 1984, and raised in Dobbs Ferry, New York.&lt;br /&gt;
&lt;br /&gt;
==Professional background==&lt;br /&gt;
Zuckerberg is the co-founder, chairman, and CEO of [[Meta]] Platforms Inc., which is the parent company of Facebook, [[Instagram]], [[WhatsApp]], and other digital services. He launched &amp;quot;TheFacebook&amp;quot; on February 4, 2004, while he was studying psychology and computer science at Harvard University. Facebook, originally a campus directory to connect Harvard students, expanded rapidly, reaching one million users within a year and becoming the world’s largest social network by 2009.&lt;br /&gt;
&lt;br /&gt;
==Stance on consumer rights==&lt;br /&gt;
Zuckerberg’s stance on consumer rights is marked by a pattern of reactive concessions under legal pressure rather than proactive protection. In 2002, he hacked Harvard&#039;s security system. He accessed students&#039; ID photos to populate a website that would allow users to rate students by looks, FaceMash, which was shut down three days later by the University.&amp;lt;ref&amp;gt;{{Cite web |last=Bellis |first=Mary |title=The History of Facebook and How It Was Invented |url=https://www.thoughtco.com/who-invented-facebook-1991791 |website=ThoughtCo. |archive-url=http://web.archive.org/web/20260114175736/https://www.thoughtco.com/who-invented-facebook-1991791 |archive-date=14 Jan 2026}}&amp;lt;/ref&amp;gt; Publicly advocating for limited regulatory reforms, his actions regarding data privacy, antitrust, and civil rights prioritize Meta’s business model over consumer welfare. While he has consistently emphasized user control over privacy settings, his actions and business model reveal a pattern of undermining genuine data autonomy. &lt;br /&gt;
&lt;br /&gt;
===Public statements supporting consumer control===&lt;br /&gt;
*2004: &amp;quot;People have very good control over who can see their information.&amp;quot;&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite news |last=Balakrishnan |first=Anita |last2=Salinas |first2=Sara |last3=Hunter |first3=Matt |date=April 9, 2018 |title=Mark Zuckerberg has been talking about privacy for 15 years - here’s almost everything he’s said |url=https://www.cnbc.com/2018/03/21/facebook-ceo-mark-zuckerbergs-statements-on-privacy-2003-2018.html |work=CNBC |archive-url=http://web.archive.org/web/20250608014833/https://www.cnbc.com/2018/03/21/facebook-ceo-mark-zuckerbergs-statements-on-privacy-2003-2018.html |archive-date=8 Jun 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite news |last=Salinas |first=Sara |last2=Balakrishnan |first2=Anita |date=December 19, 2018 |title=Mark Zuckerberg has been talking and apologizing about privacy since 2003 - here’s a reminder of what he’s said |url=https://www.cnbc.com/2018/12/19/facebook-ceo-mark-zuckerberg-privacy-apologies.html |work=CNBC |archive-url=http://web.archive.org/web/20260204015031/https://www.cnbc.com/2018/12/19/facebook-ceo-mark-zuckerberg-privacy-apologies.html |archive-date=4 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*2010, &amp;quot;What people want isn’t complete privacy. It’s control over what they share&amp;quot;.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite news |last=Clifford |first=Catherine |date=October 24, 2019 |title=19-year-old Mark Zuckerberg: ‘Issues about violating people’s privacy don’t seem to be surmountable’ |url=https://www.cnbc.com/2019/10/24/19-year-old-mark-zuckerberg-on-privacy-issues-versus-today.html |work=CNBC |archive-url=http://web.archive.org/web/20250927222001/https://www.cnbc.com/2019/10/24/19-year-old-mark-zuckerberg-on-privacy-issues-versus-today.html |archive-date=27 Sep 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*In 2019, he acknowledged Facebook’s poor privacy reputation but pledged to build a &amp;quot;privacy-focused platform&amp;quot;.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite news |last=Hern |first=Alex |date=March 7, 2019 |title=Mark Zuckerberg&#039;s privacy blogpost: what he did and didn&#039;t say |url=https://www.theguardian.com/technology/2019/mar/07/mark-zuckerbergs-privacy-blogpost-what-he-said-and-what-he-didnt |url-status=live |archive-url=https://web.archive.org/web/20260225145423/https://www.theguardian.com/technology/2019/mar/07/mark-zuckerbergs-privacy-blogpost-what-he-said-and-what-he-didnt |archive-date=25 Feb 2026 |work=The Guardian}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, these statements often frame control narrowly, focusing on visibility settings rather than limiting Facebook’s own data collection or third-party sharing.&lt;br /&gt;
&lt;br /&gt;
===Actions undermining control===&lt;br /&gt;
*Lax Data Policies: [[The Cambridge Analytica Scandal]] revealed that Facebook allowed third-party apps to harvest data from millions without explicit consent. Zuckerberg admitted, &amp;quot;[w]e simply did a bad job&amp;quot;.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; Emails later suggested he was aware of privacy risks, but prioritized growth.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
*Deceptive Practices: The [[Federal Trade Commission]] (FTC) found Facebook violated a 2012 consent decree by misleading users about data sharing.&amp;lt;ref&amp;gt;{{Cite news |last=Rushe |first=Dominic |date=June 12, 2019 |title=Facebook emails seem to show Zuckerberg knew of privacy issues, report claims |url=https://www.theguardian.com/technology/2019/jun/12/facebook-mark-zuckerberg-privacy-emails-report |url-status=live |archive-url=https://web.archive.org/web/20260318032701/https://www.theguardian.com/technology/2019/jun/12/facebook-mark-zuckerberg-privacy-emails-report |archive-date=18 Mar 2026 |work=The Guardian}}&amp;lt;/ref&amp;gt; Attorney General Racine’s lawsuit accused Zuckerberg of personally enabling policies that exposed user data.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |title=AG Racine Sues Mark Zuckerberg for Failing to Protect Millions of Users&#039; Data, Misleading Privacy Practices |url=https://oag.dc.gov/release/ag-racine-sues-mark-zuckerberg-failing-protect |archive-url=http://web.archive.org/web/20251108122756/https://oag.dc.gov/release/ag-racine-sues-mark-zuckerberg-failing-protect |archive-date=8 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Opaque Controls: Privacy settings are buried and confusing. As critics note, &amp;quot;[o]ffering tools doesn’t help if they’re hard to find.&amp;quot; One such example is ad-targeting controls being hidden under unrelated menus.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite news |last=Barrett |first=Brian |date=April 10, 2010 |title=Mark Zuckerberg&#039;s Privacy Shell Game |url=https://www.wired.com/story/mark-zuckerbergs-privacy-shell-game/ |work=Wired |archive-url=http://web.archive.org/web/20260108183133/https://www.wired.com/story/mark-zuckerbergs-privacy-shell-game/ |archive-date=8 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Revenue relies on monetizing user data.&lt;br /&gt;
**&amp;quot;Zuckerberg’s Law&amp;quot;: He predicted users would share twice as much data yearly, pushing openness over privacy.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&lt;br /&gt;
**Data Hoarding: Despite [[General Data Protection Regulation]] (GDPR) style pledges, Facebook resists limits on data collection, such as opposing regulations that would curb microtargeting.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Wheeler |first=Tom |date=2019-04-03 |title=Mark Zuckerberg’s call for internet rules only goes part way |url=https://www.brookings.edu/articles/mark-zuckerbergs-call-for-internet-rules-only-goes-part-way/ |website=The Brookings Institution |archive-url=http://web.archive.org/web/20260211234240/https://www.brookings.edu/articles/mark-zuckerbergs-call-for-internet-rules-only-goes-part-way/ |archive-date=11 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Major consumer protection incidents==&lt;br /&gt;
===Cambridge Analytica data scandal===&lt;br /&gt;
The Cambridge Analytica scandal came to light when a former employee, Christopher Wylie, leaked internal documents to journalists. These documents demonstrated the uninformed consent for the collection of personal data from up to 87 million Facebook profiles, which served political advertising purposes through Facebook&#039;s Open Graph Platform and the Facebook application &amp;quot;This is Your Digital Life,&amp;quot; developed by data scientist Aleksandr Kogan at Global Science Research.&amp;lt;ref&amp;gt;[https://www.cnbc.com/2018/04/10/facebook-cambridge-analytica-a-timeline-of-the-data-hijacking-scandal.html &amp;quot;Facebook-Cambridge Analytica: A timeline of the data hijacking scandal&amp;quot;] - cnbc.com - accessed 2025-02-03 ([http://web.archive.org/web/20260117062336/https://www.cnbc.com/2018/04/10/facebook-cambridge-analytica-a-timeline-of-the-data-hijacking-scandal.html Archived])&amp;lt;/ref&amp;gt; The appropriated personal data was used in the 2016 US Presidential election for Ted Cruz&#039;s and Donald Trump&#039;s campaigns.&amp;lt;ref&amp;gt;[https://www.businessinsider.com/cambridge-analytica-facebook-scandal-trump-cruz-operatives-2018-3 &amp;quot;There&#039;s an open secret about Cambridge Analytica in the political world: It doesn&#039;t have the &#039;secret sauce&#039; it claims&amp;quot;] - businessinsider.com - accessed 2025-02-03 ([http://web.archive.org/web/20260217160805/https://www.businessinsider.com/cambridge-analytica-facebook-scandal-trump-cruz-operatives-2018-3 Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Deceptive Marketing&#039;&#039;&#039;&lt;br /&gt;
In 2011, the FTC found Facebook guilty of deceptive practices, including sharing data with third-party apps without user consent and misrepresenting its privacy controls. Despite a 20-year consent order, Facebook continued to face allegations of similar violations, including post-2018 complaints about lax data policies.&lt;br /&gt;
&lt;br /&gt;
A photo of Zuckerberg revealed in 2016 that he keeps his own laptop camera covered with tape.&amp;lt;ref&amp;gt;{{Cite web |date=2016-06-22 |title=Mark Zuckerberg Puts Tape Over His Webcam |url=https://abcnews.go.com/Technology/mark-zuckerberg-puts-tape-webcam/story?id=40040340 |access-date=2025-03-18 |website=abc News |archive-url=http://web.archive.org/web/20251012141042/https://abcnews.go.com/Technology/mark-zuckerberg-puts-tape-webcam/story?id=40040340 |archive-date=12 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Regulatory response==&lt;br /&gt;
*Fines: Facebook paid five billion dollars to the FTC for privacy violations and faced lawsuits for deceptive practices.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
*Whistleblower Allegations: Internal documents show Zuckerberg prioritized engagement over safety, undermining claims of user control.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Current status==&lt;br /&gt;
As of June 2025, Mark Zuckerberg remains the CEO and Chairman of Meta Platforms, Inc. (formerly Facebook). He continues to lead the company&#039;s focus on the &#039;&#039;metaverse&#039;&#039;, [[artificial intelligence]], and other emerging technologies.&lt;br /&gt;
&lt;br /&gt;
===Recent developments===&lt;br /&gt;
&lt;br /&gt;
*Meta&#039;s AI and Metaverse Push&#039;&#039;&#039;:&#039;&#039;&#039; Meta is heavily investing in AI, including large language models (like LLaMA) and AI-driven products across Facebook, Instagram, and WhatsApp.&lt;br /&gt;
*Threads and social media: &#039;&#039;Threads&#039;&#039;, Meta&#039;s answer to [[X Corp|X]] (formerly &#039;&#039;Twitter), continues&#039;&#039; to grow, integrating more deeply with Instagram and the Fediverse (a decentralized social networking platform).&lt;br /&gt;
*Regulatory and Legal Issues&#039;&#039;&#039;:&#039;&#039;&#039; Zuckerberg and Meta still face scrutiny over data privacy, antitrust concerns, and content moderation policies worldwide.&lt;br /&gt;
&lt;br /&gt;
==Impact on consumer protection==&lt;br /&gt;
Mark Zuckerberg has significantly influenced consumer rights, both positively and negatively. His decisions have shaped digital privacy, data control, competition, and transparency, often sparking regulatory and public backlash.&lt;br /&gt;
*Data privacy and surveillance:&lt;br /&gt;
**Negative: Facebook (now Meta) has faced numerous scandals involving unauthorized data collection, including Cambridge Analytica (2018), where 87 million users’ data was harvested without consent.&amp;lt;ref&amp;gt;{{Cite news |last=Cadwalladr |first=Carole |last2=Graham-Harrison |first2=Emma |date=March 17, 2018 |title=Revealed: 50 million Facebook profiles harvested for Cambridge Analytica in major data breach |url=https://www.theguardian.com/news/2018/mar/17/cambridge-analytica-facebook-influence-us-election |url-status=live |archive-url=https://web.archive.org/web/20260403133731/https://www.theguardian.com/news/2018/mar/17/cambridge-analytica-facebook-influence-us-election |archive-date=3 Apr 2026 |work=The Guardian}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
**Positive: Meta introduced privacy tools and supported GDPR compliance in the EU, after the scandals.&lt;br /&gt;
*Algorithmic manipulation and mental health concerns:&lt;br /&gt;
**Negative: Studies revealed that Meta’s algorithms promoted harmful content, affecting mental health and spreading misinformation.&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite news |last=Wells |first=Georgia |last2=Horwitz |first2=Jeff |last3=Seetharaman |first3=Deepa |date=September 14, 2021 |title=Facebook Knows Instagram Is Toxic for Teen Girls, Company Documents Show |url=https://www.wsj.com/articles/facebook-knows-instagram-is-toxic-for-teen-girls-company-documents-show-11631620739 |work=The Wall Street Journal |archive-url=http://web.archive.org/web/20250626231438/https://www.wsj.com/articles/facebook-knows-instagram-is-toxic-for-teen-girls-company-documents-show-11631620739 |archive-date=26 Jun 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
**Positive: Meta has since introduced wellbeing features, such as screen time limits and content warnings.&lt;br /&gt;
*Monopoly power and reduced consumer choice:&lt;br /&gt;
**Negative: Meta’s acquisitions of Instagram and WhatsApp led to antitrust lawsuits, limiting competition and consumer alternatives.&amp;lt;ref&amp;gt;{{Cite web |date=December 9, 2020 |title=FTC Sues Facebook for Illegal Monopolization |url=https://www.ftc.gov/news-events/news/press-releases/2020/12/ftc-sues-facebook-illegal-monopolization |website=Federal Trade Commission |archive-url=http://web.archive.org/web/20260126022633/https://www.ftc.gov/news-events/news/press-releases/2020/12/ftc-sues-facebook-illegal-monopolization |archive-date=26 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
**Positive: Some argue Meta’s ecosystem (Facebook, Instagram, WhatsApp) provides convenience through integrated services.{{Citation needed|reason=Who is arguing this?}}&lt;br /&gt;
*Transparency and accountability:&lt;br /&gt;
**Negative: Facebook historically resisted transparency, including hiding internal research on harms.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&lt;br /&gt;
**Positive: Meta now publishes quarterly transparency reports on content moderation and government requests.&amp;lt;ref&amp;gt;{{Cite web |title=Transparency Center |url=https://transparency.fb.com/ |website=transparency.fb.com |archive-url=http://web.archive.org/web/20240411083133/https://transparency.fb.com/ |archive-date=11 Apr 2024}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Ad targeting and consumer exploitation:&lt;br /&gt;
**Negative: Facebook’s micro-targeting has been criticized for enabling discriminatory ads &amp;lt;ref&amp;gt;{{Cite news |last=Angwin |first=Julia |last2=Parris Jr. |first2=Terry |date=October 28, 2016 |title=Facebook Lets Advertisers Exclude Users by Race |url=https://www.propublica.org/article/facebook-lets-advertisers-exclude-users-by-race |work=ProPublica |archive-url=http://web.archive.org/web/20260216064119/https://www.propublica.org/article/facebook-lets-advertisers-exclude-users-by-race |archive-date=16 Feb 2026}}&amp;lt;/ref&amp;gt; and exploiting user behavior.&lt;br /&gt;
**Positive: Meta has restricted some ad-targeting categories (e.g., race, religion) in response to criticism.&lt;br /&gt;
The impact Mark and Meta have had on consumer rights is mixed. Meta has introduced some privacy and transparency improvements, but Zuckerberg&#039;s history of data exploitation, monopolistic behavior, and algorithmic harms has significantly weakened consumer trust. Regulatory pressure continues to shape Meta’s policies, but critics argue that more systemic changes are needed.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Individuals]]&lt;br /&gt;
[[Category:Meta]]&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google&amp;diff=56311</id>
		<title>Google</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google&amp;diff=56311"/>
		<updated>2026-06-06T00:43:40Z</updated>

		<summary type="html">&lt;p&gt;Iii: removed extra links inline with wiki&amp;#039;s style guide, changed to &amp;quot;Reflist&amp;quot; template, changed a link&amp;#039;s formatting under &amp;quot;See also&amp;quot; heading&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup|Issue 1=Article formatting should follow [[Template:CompanyPreload]]. With Google&#039;s history, it may be useful to use tabling for incidents.|Issue 2=Citations need to follow proper formatting. See [[Template:Cite web]].|Issue 3=Citations should be placed after punctuation.|Issue 4=Make sure that section headers are in sentence case where applicable.}}&lt;br /&gt;
{{CompanyCargo&lt;br /&gt;
|Founded=1998&lt;br /&gt;
|Industry=Technology&lt;br /&gt;
|Logo=Google.webp&lt;br /&gt;
|ParentCompany=Alphabet Inc.&lt;br /&gt;
|Type=Subsidiary&lt;br /&gt;
|Description=Google is one of the most influential technology companies in the world, originally known for developing the most widely used search engine.&lt;br /&gt;
|Website=https://www.google.com/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;{{Wplink|Google|Google LLC}}&#039;&#039;&#039;, founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.&amp;lt;ref&amp;gt;{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com |archive-url=http://web.archive.org/web/20260222070659/https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |archive-date=22 Feb 2026}}&amp;lt;/ref&amp;gt; Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.&amp;lt;ref&amp;gt;{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025 |archive-url=http://web.archive.org/web/20260128182647/https://about.google/products/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Google Search| Google&#039;s search engine]] remains its most well-known service, but the company has significantly diversified its offerings. Key products include the [[Android]] operating system, the [[Google Chrome]] web browser, [[Google Drive]] for cloud storage, [https://wikipedia.org/wiki/Google_Maps Google Maps], [[YouTube]], and [[wikipedia:Google_Play|Google Play]].&amp;lt;ref&amp;gt;{{Cite web |title=Helpful products, built with you in mind |url=https://about.google/intl/ALL_us/products/ |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20260205114442/https://about.google/intl/ALL_us/products/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;{{Citation needed}} Additionally, the company provides digital advertising services through Google Ads, generating the majority of its revenue.&amp;lt;ref&amp;gt;{{Cite web |date=4 Feb 2025 |title=Alphabet Announces Fourth Quarter and Fiscal Year 2024 Results |url=https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251002181452/https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |archive-date=2 Oct 2025}}&amp;lt;/ref&amp;gt; In recent years, Google has also developed hardware products such as the Pixel smartphone and Nest smart home devices.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
Google has faced ongoing scrutiny related to data privacy, competition, and its dominant position in the market, such concerns have stretched as far back as 2012.&amp;lt;ref&amp;gt;{{Cite web |last=Cohen |first=Adam |date=5 Mar 2012 |title=Will We Ever Get Strong Internet Privacy Rules? |url=https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |url-status=live |access-date=5 Apr 2025 |website=Time |archive-url=http://web.archive.org/web/20260205121437/https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=6 Sep 2023 |title=REPORT: Google at 25: From “Don’t Be Evil” To ¯\_(ツ)_/¯ |url=https://techoversight.org/2023/09/06/google-at-25/ |url-status=live |access-date=5 Apr 2025 |website=The Tech Oversight Project |archive-url=http://web.archive.org/web/20251004223929/https://techoversight.org/2023/09/06/google-at-25/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; The company has been the subject of various legal and regulatory challenges, particularly concerning antitrust issues, the use of personal data, and its impact on consumer choice.{{Citation needed}} The US government is currently engaged in an antitrust lawsuit against Google, with a decision expected early 2025.&amp;lt;ref&amp;gt;{{Cite web |date=25 Nov 2024 |title=Closing Arguments, November 25: Once, Twice, Three Times a Monopolist |url=https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |url-status=live |access-date=5 Apr 2025 |website=US v Google |archive-url=http://web.archive.org/web/20250906103632/https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |archive-date=6 Sep 2025}}&amp;lt;/ref&amp;gt; {{UpdateNeeded|date={{subst:August}} {{subst:2025}}|reason=We need updates on this situation.}}&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
In December 2024, Google announced to organisations that use its advertising products, that from 16 February 2025, it will no longer prohibit them from employing [[wikipedia:Fingerprint_(computing)|fingerprinting]] techniques.&amp;lt;ref&amp;gt;{{Cite web |last=Almond |first=Stephen |date=19 Dec 2024 |title=Our response to Google’s policy change on fingerprinting |url=https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |url-status=live |access-date=5 Apr 2025 |website=ico. |archive-url=http://web.archive.org/web/20260128163957/https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===User freedom===&lt;br /&gt;
Google has a long history of patronizing their user base by taking away options or not giving users a choice in the first place.&lt;br /&gt;
&lt;br /&gt;
For example, in 2014, Google removed normal MicroSD write access on Android 4.4,&amp;lt;ref&amp;gt;{{cite news |first=Cody |last=Toombs |url=https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |title=External Blues: Google Has Brought Big Changes To SD Cards In KitKat, And Even Samsung Is Implementing Them |url-status=live |date=17 Feb 2014 |url-status=live |website=Android Police |archive-url=https://web.archive.org/web/20140218064033/https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |archive-date=2014-02-18}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |date=23 Feb 2014 |title=Re: What about removable SD card in 4.4 |website=Google Groups |archive-url=https://web.archive.org/web/20260209114224/https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |archive-date=2026-02-09 }}&amp;lt;/ref&amp;gt; limiting each application to their own dedicated folder, arguing that this makes it easy to remove all files left by the app during uninstallation, given that no app can leave files outside their own dedicated folder.&lt;br /&gt;
&lt;br /&gt;
No menu option to change this behaviour was given to the user, therefore users who wanted to restore normal write access were forced to resort to unofficial methods involving bootloader unlocking and rooting.&lt;br /&gt;
&lt;br /&gt;
It should be noted that Google&#039;s own Android smartphones and tablet computers (Nexus and Pixel devices) never featured a memory card slot. Similar restrictions were later added to USB on-the-go storage.&amp;lt;ref name=android-traditional-storage&amp;gt;{{cite web |title=Traditional storage &amp;amp;#124; Android Open Source Project |url=https://source.android.com/docs/core/storage/traditional |url-status=live |website=Android}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2018, Google added a clipboard manager to their keyboard app, Gboard.&amp;lt;ref&amp;gt;{{cite web |url=https://www.xda-developers.com/gboard-clipboard-manager/ |title=Gboard 7.7 adds a Clipboard Manager feature to Google&#039;s keyboard app |date=22 Oct 2018 |first=Mishaal |last=Rahman |url-status=live |website=XDA Developers |archive-url=https://web.archive.org/web/20190119233536/https://www.xda-developers.com/gboard-clipboard-manager/ |archive-date=2019-01-19}}&amp;lt;/ref&amp;gt; But in 2022, Google decided on behalf of their users that they don&#039;t need to retain clipboard items for any longer than one hour. Therefore, they added a one-hour time limit, meaning any clipboard item older than one hour is automatically deleted, with no option to change this behaviour. The only way to retain clipboard items for more than one hour is to manually mark them as &amp;quot;pinned&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |first=Ethan |last=Gillian |title=Remember: Android 13 clears clipboard 1 hour after copying |url=https://techzle.com/remember-android-13-clears-clipboard-1-hour-after-copying |url-status=live |website=Techzle |date=17 Aug 2022}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2019, Google took away the ability to turn off the &amp;quot;pull-to-refresh&amp;quot; gesture on the mobile edition of their Chrome web browser, following by refusing to reinstate the option after an abnormally high number of complaints that the gesture causes accidental refreshes. See [[Google_Chrome#Mandatory_pull-to-refresh|Google Chrome § Mandatory pull-to-refresh]].&lt;br /&gt;
&lt;br /&gt;
Google lets app developers arbitrarily [[screenshot blocking|prevent device owners from capturing screenshots and screen recordings]] on Android. While the original intention was to prevent sensitive information in banking apps from getting outside, it has been severely overused by app developers and prevents legitimate uses such as asking for help in forums and bug reports. Google provided no option for device owners to override it, so the only way is to unlock the bootloader and modify the operating system.&amp;lt;ref&amp;gt;{{cite web |url=https://www.howtogeek.com/why-screenshots-dont-always-work-especially-in-secure-apps/ |website=How To Geek |author=Faisal Rasool |title=Why Your Phone Blocks Screenshots in Secure Apps |date=2025-08-23 |access-date=2026-05-26 }}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=konradkar |url=https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |website=[[Reddit]] |title=Booking.com app disallow to take screenshot, can I bypass this? |date=2020-02-14 |access-date=2026-05-26 |archive-url=https://web.archive.org/web/20230615071612/https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |archive-date=2023-06-15}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{excerpt|Android Developer Verification}}&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
===Account lockouts===&lt;br /&gt;
Google has been reported to have randomly locked people out of their accounts due to ostensible security reasons, which are not lifted even if the user had provided the correct credentials and/or even if the user have correctly followed all the verification prompts such as SMS verification. These have caused anguishes for many affected users who are unable to access their contents, emails and services as a result. Furthermore, some had reported that they are forced to undergo SMS verification even when recovery email addresses are already configured to their accounts, thereby likely constituting instances of [[Forced identification|forced verification]] in broad senses.&amp;lt;ref&amp;gt;{{cite web |url=https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |date=5 May 2021 |author=Feniks_Gaming |title=Mike Rose (No More Robots Publisher) Locked out of Gmail, speaks to google support to find out their own staff are locked out of their personal Gmail too... |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210505101632/https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |archive-date=2021-05-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |first=Mike |last=Rose |url-status=dead |date=4 May 2021 |title=This morning, I was locked out of my Google account |website=Nitter |archive-url=https://web.archive.org/web/20220908195211/https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |archive-date=2022-09-08}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |title=FYI: Google can lock you out of your account for no reason |author=danielrosehill |date=5 Aug 2021 |url=https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210805030048/https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |archive-date=2021-08-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=LegitimateAttempt4 |date=20 Jul 2023 |title=DAE noticed that Google had taken security account lockouts to a zealotic level? |url-status=live |url=https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |website=[[Reddit]] |archive-url=http://web.archive.org/web/20230720181226/https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |archive-date=2023-07-20}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Deletion of inactive accounts===&lt;br /&gt;
In May 2023, Google announced that [[Inactive account deletion|deletion of inactive user accounts]] would occur starting in December 2023, citing security reasons, noting that old and unused accounts are more likely to be compromised. Google claimed that &amp;quot;Forgotten or unattended accounts often rely on old or re-used passwords that may have been compromised, have not had two factor authentication set up, and receive fewer security checks by the user,&amp;quot; while saying that Google &amp;quot;has no plans to delete YouTube videos&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |last1=Lawler |first1=Richard |title=Google might delete your Gmail account if you haven&#039;t logged in for two years |url=https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |website=The Verge |access-date=21 December 2023 |language=en |date=16 May 2023 |archive-url=http://web.archive.org/web/20260205121216/https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Porter |first1=Jon |title=Reminder: Google is about to start purging inactive accounts |url=https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |website=The Verge |access-date=21 December 2023 |language=en |date=28 November 2023 |archive-url=http://web.archive.org/web/20251212230239/https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Amadeo |first1=Ron |title=Google&#039;s new &amp;quot;inactive account&amp;quot; policy won&#039;t delete years of YouTube videos |url=https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |website=Ars Technica |access-date=21 December 2023 |language=en-us |date=17 May 2023 |archive-url=http://web.archive.org/web/20251212092014/https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt; The decision to delete inactive accounts has sparked some criticism and backlash. The cited security rationale behind such decision was ridiculed and was compared to a hypothetical scenario where a bank should be burned down if it is not secure against robbers.&amp;lt;ref&amp;gt;{{cite web |last1=Novet |first1=Jordan |title=Google&#039;s plan to purge inactive accounts isn&#039;t sitting well with some users |url=https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |website=CNBC |access-date=21 December 2023 |language=en |date&lt;br /&gt;
=19 August 2023 |archive-url=http://web.archive.org/web/20250831223936/https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |archive-date=31 Aug 2025}}&amp;lt;/ref&amp;gt; Such policies could adversely affect those who had good reasons to become inactive for a long time, such as hospitalization, prison incarceration, and being in totalitarian countries which have prolonged internet shutdowns. Moreover, the Anonymous hacktivist collective has protested against the decision to delete inactive accounts multiple times, describing them as &amp;quot;harsh&amp;quot; and saying that the decision will &amp;quot;destroy history&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |date=18 Jul 2023 |title=Anonymous puts Taiwan flag, national anthem on 2 UN websites |url=https://www.taiwannews.com.tw/en/news/4946597 |first=Keoni |last=Everington |url-status=live |access-date=21 Dec 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20231014070719/https://www.taiwannews.com.tw/en/news/4946597 |archive-date=2023-10-14}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=18 Oct 2023 |title=&#039;Anonymous&#039; hacks Chinese government site to protest Israel–Hamas war |url-status=live |url=https://www.taiwannews.com.tw/en/news/5022840 |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240221120716/https://www.taiwannews.com.tw/en/news/5022840 |archive-date=2024-02-21}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=8 Dec 2023 |title=Anonymous posts Taiwan flag on UN site |website=Taiwan News |url=https://www.taiwannews.com.tw/en/news/5055454 |url-status=live |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240228035811/https://www.taiwannews.com.tw/en/news/5055454 |archive-date=2024-02-28}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anti-competitive practices===&lt;br /&gt;
Google has a great history of anti-competitive practices. For example, in 2020 the company was sued for practices involving pushing off relevant search results in order to favor advertisements and the inclusion of [[bloatware]] on Android devices.&amp;lt;ref&amp;gt;{{Cite web |publisher=Eaton Business School|date=31 Aug 2021 |title=Google - A display of anti-competitive behaviour|url=https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |url-status=live |archive-url=https://web.archive.org/web/20250523013602/https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |archive-date=2025-05-23 |access-date=25 May 2026 |website=Eaton Business School}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The [[Android Developer Verification]] program prevents sideloading and external app stores, such as [[F-Droid]] to be an available alternative to the Google Play Store.&lt;br /&gt;
&lt;br /&gt;
===Google device repair program restrictions===&lt;br /&gt;
{{Main|Google asserts the right to seize your phone during a repair}}&lt;br /&gt;
Google&#039;s Service &amp;amp; Repair Program terms explicitly state that any device containing non-Google-authorized parts &amp;quot;will not be returned&amp;quot; to the customer.&lt;br /&gt;
&lt;br /&gt;
===Target API level requirements for Google Play apps===&lt;br /&gt;
Google has a policy that requires apps for Android to target recent API levels, in order to appear in the Play Store, depending on a user&#039;s device&#039;s version of Android, or if it is a new app.&amp;lt;ref&amp;gt;{{Cite web |date=31 Aug 2024 |title=Policy Center |url=https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |access-date=May 9, 2025 |website=Play Console Help |archive-url=http://web.archive.org/web/20260215054419/https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; This creates a continuous cycle of maintenance and redevelopment that can be especially burdensome for smaller developers, indie creators, and consumers.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
The requirement for apps to target newer APIs each year serves some legitimate security and feature purposes. However, it also effectively functions as a form of forced obsolescence. Even perfectly functional apps that don&#039;t need technical updates must be regularly reworked just to remain visible on the Play Store.&lt;br /&gt;
&lt;br /&gt;
This creates several issues:&lt;br /&gt;
&lt;br /&gt;
*Development resources must be allocated to updating apps rather than creating new features&lt;br /&gt;
*Smaller teams and individual developers are placed at a disadvantage attempting to keep up with the constant update cycle&lt;br /&gt;
*Legacy apps that are no longer actively maintained disappear, even if they&#039;re still useful&lt;br /&gt;
*The cost of maintaining apps increases, potentially making some projects financially nonviable&lt;br /&gt;
*Losing access to previously purchased apps when upgrading devices&lt;br /&gt;
*Users being unable to reinstall older apps that worked perfectly well for their needs&lt;br /&gt;
*Facing unexpected costs to replace functionality they&#039;ve already paid for&lt;br /&gt;
*Dealing with the frustration of discovering favorite apps have disappeared&lt;br /&gt;
&lt;br /&gt;
While Google argues this approach improves the Android ecosystem&#039;s security and functionality, it does place a significant burden on developers and can lead to the premature &amp;quot;death&amp;quot; of otherwise functional applications.&lt;br /&gt;
&lt;br /&gt;
This creates a troubling disconnect in digital ownership. Consumers reasonably expect that when they purchase an app, they should maintain access to it across their devices over time. Instead, they discover their digital purchases can effectively vanish due to policy decisions beyond their control.&lt;br /&gt;
&lt;br /&gt;
===Ban on third-party tech support ads===&lt;br /&gt;
Google prohibits tech support ads on their platform if they are not authorized by the manufacturer.&amp;lt;ref&amp;gt;{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google |archive-url=http://web.archive.org/web/20251112170608/https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |archive-date=12 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===The chargeback incident===&lt;br /&gt;
In November 2022, a Google customer accidentally purchased two Google Pixel smartphones instead of one, directly from Google (no third-party reseller), and tried to return one package to Google for a refund, but the shipping was unsuccessful.&lt;br /&gt;
&lt;br /&gt;
A Google customer support person suggested the customer to perform a chargeback. The customer acted accordingly without understanding the implications, resulting in the termination of their Google account shortly after. The account was 15 years old at that time.&amp;lt;ref&amp;gt;{{cite web |first=Noel |last=Santos |website=Virtual Curiosities |date=8 Dec 2024 |url=https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |url-status=live |title=DANGER!!!: Chargeback = ACCOUNT PERMANENTLY BANNED |archive-url=http://web.archive.org/web/20260205120523/https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |archive-date=2026-02-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=justAnotherLedditor |date=16 Dec 2022 |url=https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |url-status=live |title=TIFU by accidentally buying two Google Pixels and ended up getting my 15 year old Google Account permanently banned. |website=[[Reddit]] |archive-url=http://web.archive.org/web/20260113140546/https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |archive-date=2026-01-13}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===AI integrations in Google Search===&lt;br /&gt;
On may 19th, 2026, Google announced modifications for [[Google Search]] to include more AI integrations involving inclusion of [[Google Gemini]] Flash 3.5 and integration of AI agents. These changes have sparked several controversies, including for example critizicing the reliability of searching using AI because of hallucinations, inabilities of AIs to detect malicious web sites and possibilities to use AI to control results obtained on searches. &amp;lt;ref&amp;gt;{{Cite web |last=Yildrim |first=Ece |date=19 May 2026 |title=Google Search Is Dead. Welcome to the Era of the ‘Intelligent Search Box’ |url=https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |url-status=live |archive-url=https://web.archive.org/web/20260519204100/https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |archive-date=2026-05-19 |access-date=21 May 2026 |website=Gizmodo}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Reid|first=Elizabeth |date=19 May 2026 |title=A new era for AI Search |url=https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |url-status=live |archive-url=https://web.archive.org/web/20260519181835/https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |archive-date=2026-05-19 |access-date=21 May 2026 |website=Google Blog}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Service shutdowns===&lt;br /&gt;
====Google Play Music shutdown (Dec 2020)====&lt;br /&gt;
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store &amp;amp; Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223929/https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20251214224205/https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |archive-date=14 Dec 2025}}&amp;lt;/ref&amp;gt; Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.&amp;lt;ref&amp;gt;{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek |archive-url=http://web.archive.org/web/20251004223929/https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.&amp;lt;ref&amp;gt;{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz |archive-url=http://web.archive.org/web/20250805235415/https://www.technobezz.com/buy-music-google-play |archive-date=5 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google |archive-url=http://web.archive.org/web/20250708163846/https://9to5google.com/2020/12/03/google-play-music-dead/ |archive-date=8 Jul 2025}}&amp;lt;/ref&amp;gt; This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |author=The YouTube Team |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog |archive-url=http://web.archive.org/web/20260201140126/https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the shut down, users lost access to the music they paid for, with no way to download them. Google justified this by transferring all playlists and purchase history to YouTube Music, and only refunding songs that were not directly available,&amp;lt;ref&amp;gt;{{Cite web |author=Garry |date=10 Oct 2023 |title=What happened to my songs on Google Music? |url=https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |url-status=live |access-date=5 Apr 2025 |website=Darwin&#039;s Data |archive-url=http://web.archive.org/web/20251004223930/https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Chaney |first=Sarah |date=5 Feb 2022 |title=What Happened to Google Play Music? |url=https://www.makeuseof.com/what-happened-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=MUO |archive-url=http://web.archive.org/web/20260205111318/https://www.makeuseof.com/what-happened-to-google-play-music/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; with no guarantee that the songs will remain available through the new service. Users found that their purchased songs were no longer able to stream at 320kbps on YouTube Music compared to Google Play Music unless they paid for the monthly subscription.&amp;lt;ref&amp;gt;{{Cite web |last=Cutlack |first=Gary |date=23 Dec 2012 |title=Google Music UK: everything you need to know |url=https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |url-status=live |access-date=5 Apr 2025 |website=TechRadar |archive-url=http://web.archive.org/web/20251221115733/https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |archive-date=21 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=L. Hald |first=Nicole |date=24 Mar 2025 |title=How Is YouTube Music Sound Quality in 2025? Is It Any Good? |url=https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |url-status=live |access-date=5 Apr 2025 |website=NoteBurner |archive-url=http://web.archive.org/web/20260217143252/https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |archive-date=17 Feb 2026}}&amp;lt;/ref&amp;gt; If a user failed to initiate the transfer of their music library or locally download their songs by 24th February 2021, then they lost all access and all data associated with Google Play Music.&amp;lt;ref&amp;gt;{{Cite web |last=Sodhi |first=Tanishka |date=8 Feb 2021 |title=Google Play Music Data Will Be Deleted on February 24: Here’s How to Transfer to YouTube Music |url=https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |url-status=live |access-date=5 Apr 2025 |website=Gadgets 360 |archive-url=http://web.archive.org/web/20260205112610/https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; YouTube Music does not provide the option to download songs as MP3s, with local downloads requiring an internet connection every 30 days to continue working offline.&amp;lt;ref&amp;gt;{{Cite web |title=Download music and podcasts to listen to offline |url=https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223930/https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Stadia shutdown (Jan 2023)====&lt;br /&gt;
In January 2023, Google announced the shutdown of its cloud gaming service, Stadia, which was launched in November 2019.&amp;lt;ref&amp;gt;{{Cite web |author=Verge Staff |title=RIP Google Stadia: the latest news on the discontinued cloud gaming service |url=https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |url-status=live |access-date=5 Apr 2025 |website=The Verge |archive-url=http://web.archive.org/web/20260101185119/https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |archive-date=1 Jan 2026}}&amp;lt;/ref&amp;gt; Stadia required users to purchase games individually, unlike other gaming platforms that offer subscription-based access. Upon the service&#039;s closure, Google promised to refund consumers for their purchases, including both games and hardware. The refunds for games and software were issued automatically.&amp;lt;ref&amp;gt;{{Cite web |last=Ravenscraft |first=Erin |date=10 Nov 2022 |title=Stadia Is Dying. Here’s What’s in Your Refund and How to Get It |url=https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |url-status=live |access-date=5 Apr 2025 |website=Wired |archive-url=http://web.archive.org/web/20260205115111/https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stadia users were effectively renting access to games, as the platform did not allow for traditional ownership or offline play. With the service discontinued, consumers were left without access to the content they had purchased. Stadia users who had bought controllers and other peripherals for the service were also impacted by the shutdown. While Google offered refunds to customers, many Stadia consumers were left with equipment that no longer performs the advertised functions and limited recourse for repurposing or reselling their devices.&amp;lt;ref&amp;gt;{{Cite web |last=Ashworth |first=Mack |date=5 Oct 2022 |title=Stadia Shut Down: How To Use Your Hardware Now Google’s Shutting It Down |url=https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |url-status=live |access-date=5 Apr 2025 |website=Game Revolution |archive-url=http://web.archive.org/web/20251004224131/https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.&amp;lt;ref&amp;gt;{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here&#039;s how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central |archive-url=http://web.archive.org/web/20251109164004/https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |archive-date=9 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Assistant third-party list support (Jun 2023)====&lt;br /&gt;
On June 20th, 2023, Google disabled third-party list support for Google Assistant.&amp;lt;ref&amp;gt;{{Cite web |access-date=2025-09-16 |title=Where are my old lists? |url=https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-url=https://web.archive.org/web/20250427212604/https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-date=2025-04-27}}&amp;lt;/ref&amp;gt; This feature allowed lists through third-party services, such as AnyList or Todoist, to be managed via Google Assistant. After this change, the only list provider available through Google Assistant, was Google&#039;s own list service, Google Keep.&amp;lt;ref&amp;gt;{{Cite web |last=Mathur |first=Chandraveer |website=Android Police |date=2023-05-31 |title=Google Assistant is killing support for notes and lists integration with third-party apps |url=https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-url=http://web.archive.org/web/20251218051543/https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-date=18 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Jamboard shutdown (Dec 2024)====&lt;br /&gt;
{{Main|Google Jamboard}}&lt;br /&gt;
In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.&lt;br /&gt;
&lt;br /&gt;
The Jamboard product was a $5,000 device that Google pitched as a collaborative tool through its Google Workspace service. After the service no longer existed, however, the device became a brick and the users as well as the buyers were left unsupported and uncompensated.&lt;br /&gt;
&lt;br /&gt;
Situations like this highlight the vulnerability of the consumer market since proprietary products are completely at the hands of developers who can cut services on a whim. Thus, consumer protection must be taken to another level to ensure that no matter what companies get rid of, support and compensatory avenues exist.&lt;br /&gt;
&lt;br /&gt;
====Manifest V2 shutdown (Jul 2025)====&lt;br /&gt;
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users as well as making Chromium (a browser that many other browsers use as their base) switch to Manifest V3, and disabled the ability to turn them back on.&amp;lt;ref&amp;gt;{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manifest V3 disabled the &amp;lt;code&amp;gt;webRequestBlocking&amp;lt;/code&amp;gt; permission in the &amp;lt;code&amp;gt;webRequest&amp;lt;/code&amp;gt; API,&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}&amp;lt;/ref&amp;gt; preventing many ad content blockers (such as uBlock Origin) from working.&amp;lt;ref&amp;gt;{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}&amp;lt;/ref&amp;gt; Google cites performance reasons,&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote=&amp;quot;In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with.&amp;quot;}}&amp;lt;/ref&amp;gt; but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.&lt;br /&gt;
&lt;br /&gt;
===Google Pixel===&lt;br /&gt;
====Pixel devices bricked due to confusing reasons====&lt;br /&gt;
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs, or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.&amp;lt;ref&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won&#039;t help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}&amp;lt;/ref&amp;gt; The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung&#039;s EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or [[wikipedia:Fastboot|Fastboot]], making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.&lt;br /&gt;
&lt;br /&gt;
This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special &amp;quot;USB boot&amp;quot; bit flag set to 1.&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, this recovery bootloader is inaccessible to the public, and is not possible to recreate it without Google&#039;s private keys. This makes it impossible to repair a device in this state, other than to do a technically challenging repair involving desoldering the UFS chip to repopulate its contents or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.&lt;br /&gt;
&lt;br /&gt;
Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue. Even with there being a sizable post on their bug tracker,&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20251004223929/https://issuetracker.google.com/issues/437705274 |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; and despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Pixel 4a battery reduction update (Jan 2025)====&lt;br /&gt;
{{Main|Pixel 4a Battery Performance Program}}&lt;br /&gt;
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on &amp;quot;Impacted Devices&amp;quot;. Not all units were affected. It&#039;s speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.&lt;br /&gt;
&lt;br /&gt;
As compensation, Google offered a free battery replacement only in select countries. In other countries, you could choose between a $50 USD payment or $100 USD worth of Google Store credits. However, some users reported difficulty obtaining their compensation.&lt;br /&gt;
&lt;br /&gt;
===User freedom incidents===&lt;br /&gt;
====Banning domain-blockers from Play Store (2013)====&lt;br /&gt;
Since 2013, Google has taken down all apps on G-Play that can block connections to arbitrary [[wikipedia:Domain_Name_System|domain-names]] via [https://developer.android.com/develop/connectivity/vpn the official VPN API], most of those apps being marketed as ad-blockers.&amp;lt;ref&amp;gt;{{ cite news |first=Liam |last=Tung |date=14 Mar 2013 |website=ZDNET |title=Google kicks ad-blocker apps off Play store |url=https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |url-status=live |archive-url=https://web.archive.org/web/20150625111914/https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |archive-date=2015-06-25}}&amp;lt;/ref&amp;gt; This forced apps such as AdGuard and NetGuard to distribute their ad-blocking features elsewhere.&amp;lt;ref&amp;gt;{{cite web |first=Ekaterina |last=Kachalova |title=Why is AdGuard not on Google Play? |date=17 Aug 2023 |website=AdGuard |url=https://adguard.com/en/blog/adguard-google-play-removal.html |url-status=live |archive-url=https://web.archive.org/web/20230822100645/https://adguard.com/en/blog/adguard-google-play-removal.html |archive-date=2023-08-22}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;netguard&amp;quot;&amp;gt;{{cite web |author=NetGuard |website=[[GitHub]] |title=NetGuard/ADBLOCKING.md |url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L6 |url-status=live |archive-url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md |archive-date=2026-03-29}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
*Line 6: &amp;quot;ad blocking is not possible with the Play store version because Google does not allow ad blocking apps in the Play store&amp;quot;.&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
*Line 106: &amp;quot;Please do not mention this feature in Google Play store comments, since Google does not allow ad blocking applications in the Google Play store&amp;quot;.&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google cites their own Developer Distribution Agreement (terms of service for devs), claiming that those apps are &amp;quot;disruptive&amp;quot;, as if to imply hacking or cracking. Many people claim that&#039;s an invalid excuse, and that the ulterior motive was to increase ad-revenue.&lt;br /&gt;
&lt;br /&gt;
====Phone number requirement for new accounts (2020)====&lt;br /&gt;
Since 2020, Google has increasingly forced users to verify phone-numbers via SMS during account registration,&amp;lt;ref&amp;gt;{{cite web |website=Google Support |url=https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |date=20 Mar 2020 |title=Cannot create a new Google account, it is requiring a phone number (Forced phone verification) |author=FB3 Network |url-status=live |archive-url=https://web.archive.org/web/20260509050746/https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |archive-date=2026-05-09}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=DarknessMoonlight |date=30 Jun 2021 |title=Does Google now require a phone number to make new Gmail accounts? |url=https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |url-status=live |website=[[Reddit]] |archive-url=https://web.archive.org/web/20260427144651/https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |archive-date=2026-04-27}}&amp;lt;/ref&amp;gt; in an effort to &amp;quot;mitigate spam, bot activity, and account abuse&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |author=CLRN |date=2025-07-25 |title=How to skip phone verification while creating Gmail account? |url=https://www.clrn.org/how-to-skip-phone-verification-while-creating-gmail-account/ |url-status=live |access-date=2026-05-05 |website=California Learning Resource Network}}&amp;lt;/ref&amp;gt; They have a system that immediately detects reuse of numbers, so no accounts can have the same associated number.{{Citation needed}} This, paired with [[YouTube#Forced sign-in|YouTube&#039;s sign-in requirement]], makes it impossible for users to share a single &amp;quot;guest&amp;quot; account, as is typically the case for families sharing a smart TV.&lt;br /&gt;
&lt;br /&gt;
====Blocking sideloading of unverified Android apps (Aug 2025)====&lt;br /&gt;
{{Main|Google blocking sideloading of unverified Android apps}}&lt;br /&gt;
On 25 August 2025, &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog |archive-url=http://web.archive.org/web/20260128013331/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20260119211509/https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt; This marks a significant change to Android&#039;s long-standing support for sideloading apps.&lt;br /&gt;
&lt;br /&gt;
Devices without [[Google Mobile Services]] or running [[wikipedia:List_of_custom_Android_distributions|custom ROMs]] are exempt.&amp;lt;ref name=&amp;quot;:22&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}&amp;lt;/ref&amp;gt; Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |author=JohnC_21 |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=https://web.archive.org/web/20250825210732/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=2025-08-25}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Lawsuit==&lt;br /&gt;
===Privacy violations===&lt;br /&gt;
====&#039;&#039;Rodriguez v. Google LLC&#039;&#039; (&#039;&#039;May 2021—September 2025&#039;&#039;)====&lt;br /&gt;
Google&#039;s &amp;quot;Web &amp;amp; App Activity&amp;quot; (WAA) setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.&amp;lt;ref&amp;gt;{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251011171640/https://googlewebappactivitylawsuit.com/Home/FAQ |archive-date=11 Oct 2025}}&amp;lt;/ref&amp;gt; Google collected mobile device data for eight years from users who opted out of tracking under the WAA.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |last=Staab |first=Theresa |date=18 Sep 2025 |title=Someone is Always Watching: Implications of Google&#039;s WAA Privacy Case |url=https://lawreview.syr.edu/someone-is-always-watching-implications-of-googles-waa-privacy-case/ |access-date=26 Mar 2026 |website=Syracuse Law Review}}&amp;lt;/ref&amp;gt; The dates of use/activity in question were between July 1, 2016 and September 23, 2024.&amp;lt;ref&amp;gt;{{Cite web |date=23 Oct 2024 |title=FAQs: Google Web App Activity lawsuit |url=https://help.wfu.edu/support/solutions/articles/13000825158-faqs-google-web-app-activity-lawsuit |url-status=live |access-date=26 Mar 2026 |website=Wake Forest University}}&amp;lt;/ref&amp;gt; On September 3, 2025, the San Francisco Federal Court jury held Google liable two of three claims of privacy invasion. The plaintiffs were awarded $425.7 million in compensatory damages for invasion of privacy, totaling around $4 per person for the approximate 98 million affected users, but since the jury found that Google did not act with malicious intent, no punitive damages were awarded.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite news |last=Mollman |first=Brittney |last2=Sosnicki |first2=Luke |date=2025-09-05 |title=Federal Jury Awards $425.7 Million in Google Privacy Case: Key Takeaways on Consent Design and Litigation Risk |url=https://www.thompsoncoburn.com/insights/federal-jury-awards-425-7-million-in-google-privacy-case-key-takeaways-on-consent-design-and-litigation-risk/ |url-status=live |access-date=2026-05-05 |work=Thompson Coburn LLP}}&amp;lt;/ref&amp;gt; Google filed an appeal to this verdict &amp;quot;on the basis that the jury misunderstood the functionality of its privacy tools and that users were adequately informed through layered disclosures and consent flows&amp;quot;.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt; Claim submission may begin once the appeals process finishes.&amp;lt;ref&amp;gt;{{Cite web |date=2025-11-05 |title=$425M Verdict in Google Web &amp;amp; App Activity Privacy Class Action Lawsuit — Do You Qualify? |url=https://openclassactions.com/settlements/google-web-and-app-activity-privacy-class-action-lawsuit.php |url-status=live |access-date=2026-05-05 |website=OpenClassActions}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;Thele v. Google LLC&#039;&#039; (&#039;&#039;November 2025—&#039;&#039;)====&lt;br /&gt;
On the 11th of November, 2025, Thomas Thele filed a demand for jury trial in a class action complaint against Google LLC. In the filing it states that &amp;quot;on or about October 10, 2025, Google secretly turned on Gemini for all its users’ Gmail, Chat, and Meet accounts, enabling AI to track its users’ private communications contained in those platforms without the users’ knowledge or consent&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |last=Wolfson |first=Tina |last2=Ahdoot |first2=Robert |last3=Maya |first3=Theodore |last4=Brown |first4=Alyssa |date=2025-11-11 |title=UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA - CLASS ACTION COMPLAINT DEMAND FOR JURY TRIAL |url=https://www.classaction.org/media/thele-v-google-complaint_2.pdf |url-status=live |access-date=2026-05-05 |website=ClassAction}}&amp;lt;/ref&amp;gt; The suit &amp;quot;alleges that Google is violating the California Invasion of Privacy Act&amp;quot;,&amp;lt;ref&amp;gt;{{Cite web |last=Burnson |first=Robert |date=2025-11-12 |title=Google sued for allegedly using Gemini AI to secretly track user data |url=https://www.business-standard.com/technology/tech-news/google-sued-for-allegedly-using-gemini-ai-to-secretly-track-user-data-125111200603_1.html |url-status=live |access-date=2026-05-05 |website=Business Standard}}&amp;lt;/ref&amp;gt; a law enacted in 1967 which dictates the terms by which advances in technology can be used for the purpose of invading the privacy of citizens.&amp;lt;ref&amp;gt;{{Cite web |date=1967 |title=CHAPTER 1.5. Invasion of Privacy |url=https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=PEN&amp;amp;part=1.&amp;amp;title=15.&amp;amp;chapter=1.5 |url-status=live |access-date=2026-05-05 |website=California Legislative Information}}&amp;lt;/ref&amp;gt; The defendant, Google LLC, filed a Motion to Dismiss which is scheduled to be heard on May 1, 2026.&amp;lt;ref&amp;gt;{{Cite web |date=2026-04-27 |title=Thele v. Google LLC |url=https://www.pacermonitor.com/public/case/61129560/Thele_v_Google_LLC |url-status=live |access-date=2026-05-05 |website=PacerMonitor}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anti-competitive behavior===&lt;br /&gt;
====&#039;&#039;Epic Games, Inc. v. Google Inc.&#039;&#039; (&#039;&#039;August 2020—May 2025&#039;&#039;)====&lt;br /&gt;
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].&amp;lt;ref&amp;gt;{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam&#039;s 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com |archive-url=http://web.archive.org/web/20251211034837/https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |archive-date=11 Dec 2025}}&amp;lt;/ref&amp;gt; On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of &#039;&#039;Fortnite&#039;&#039; to redirect users to Epic Games&#039; storefront to purchase in-game currency (&amp;quot;V-Bucks&amp;quot;) alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google&#039;s storefronts, and &#039;&#039;Fortnite&#039;&#039; was removed from both app stores the same day.&lt;br /&gt;
&lt;br /&gt;
Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behavior. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.&amp;lt;ref&amp;gt;{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111151936/https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |archive-date=11 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Social media addiction bellwether trials===&lt;br /&gt;
====Los Angeles Superior Court, JCCP 5255 (&#039;&#039;2026&#039;&#039;)====&lt;br /&gt;
Starting in January of 2026, [[Meta]] (Facebook and [[Instagram]]) and Google (YouTube) faced legal claims of their platforms being intentionally addictive and harmful to children. [[ByteDance]] ([[TikTok]]) and Snap ([[Snapchat]]) were named initially, but settled for undisclosed terms before the trial began. A 19-year-old girl, referred to by the initials &amp;quot;KGM&amp;quot; or Kaley, and two other plaintiffs were selected for bellwether trials—test cases tried as part of an MDL.&amp;lt;ref&amp;gt;{{Cite web |last=Huamani |first=Kaitlyn |last2=Ortutay |first2=Barbara |date=9 Feb 2026 |title=Landmark trial accusing tech giants of harming children with addictive social media begins |url=https://www.pbs.org/newshour/nation/landmark-trial-accusing-tech-giants-of-harming-children-with-addictive-social-media-begins |url-status=live |access-date=25 Mar 2026 |website=PBS News}}&amp;lt;/ref&amp;gt;  On March 25, 2026, the California jury concluded in KGM&#039;s case that Meta and Google were guilty of negligent for their apps—Instagram, Facebook, and YouTube—being deliberately built to be addictive, which the companies&#039; executives knew this and failed to protect their youngest users.&amp;lt;ref&amp;gt;{{Cite web |last=Allyn |first=Bobby |date=25 Mar 2026 |title=Jury finds Meta and Google negligent in social media harms trial |url=https://www.npr.org/2026/03/25/nx-s1-5746125/meta-youtube-social-media-trial-verdict |url-status=live |access-date=26 Mar 2026 |website=npr}}&amp;lt;/ref&amp;gt; Meta was charged to pay $4.2 million for compensatory and punitive damages, and charged Google $1.8 million.&amp;lt;ref&amp;gt;{{Cite web |last=Kang |first=Cecilia |last2=Mac |first2=Ryan |last3=Tan |first3=Eli |date=25 Mar 2026 |title=Meta and YouTube Found Negligent in Landmark Social Media Addiction Case |url=https://www.nytimes.com/2026/03/25/technology/social-media-trial-verdict.html |url-status=live |access-date=26 Mar 2026 |website=The New York Times}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[List of Google products]]&lt;br /&gt;
*[[Advertising overload]]&lt;br /&gt;
*[[Google asserts the right to seize phones during repairs]]&lt;br /&gt;
*[[Google Nest Protect forced to use Google app]]&lt;br /&gt;
*[[Google Nest thermostat smart features disabled]]&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]]&lt;br /&gt;
&lt;br /&gt;
==External links==&lt;br /&gt;
*&amp;quot;[https://www.jwz.org/xscreensaver/google.html XScreenSaver: Google Store Privacy Policy]&amp;quot;. Google pretending to care about privacy by forcing a fully-local (no internet) minimal-permission screen-saver app to specify a privacy-policy. That blog-post contains many sources on Google&#039;s anti-consumer practices&lt;br /&gt;
*[https://theywillbanyou.com/| They Will Ban You - Cases of user accounts banned for unfair reasons]&lt;br /&gt;
*[https://killedbygoogle.com/ Killed by Google - Dead products list]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google| ]]&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Amazon&amp;diff=56308</id>
		<title>Amazon</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Amazon&amp;diff=56308"/>
		<updated>2026-06-06T00:02:51Z</updated>

		<summary type="html">&lt;p&gt;Iii: moved Louis Rossmann video section from &amp;quot;Products&amp;quot; to &amp;quot;See also&amp;quot; heading&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{CompanyCargo&lt;br /&gt;
| Founded       = 1994&lt;br /&gt;
| Industry      = Technology&lt;br /&gt;
| Logo          = Amazon.svg&lt;br /&gt;
| ParentCompany = &lt;br /&gt;
| Type          = Public&lt;br /&gt;
| Website       = https://amazon.com/&lt;br /&gt;
| Description   = Major e-commerce platform which has allowed fraudulent listings, removed functionality and purchased products from Kindle devices, and more.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;{{Wplink|Amazon (company)|Amazon.com, Inc.}}&#039;&#039;&#039; is a global leader in e-commerce, cloud computing, and digital streaming founded in 1994 by Jeff Bezos. Originally launched as an online bookstore, Amazon quickly expanded into a marketplace offering a wide range of products, including - but not limited to - electronics, clothing, household goods, and groceries. Today, it is one of the largest companies in the world, with a dominant presence in retail, technology, and logistics.&lt;br /&gt;
&lt;br /&gt;
In addition to its e-commerce platform, Amazon is a major player in cloud computing through Amazon Web Services (AWS), which provides cloud infrastructure and services to businesses globally. The company also offers a variety of digital services, such as Amazon Prime - which provides streaming video and music - and Alexa; its voice-activated virtual assistant. Amazon has also developed consumer products like the Kindle e-reader, Fire tablets, and Echo smart speakers.&lt;br /&gt;
&lt;br /&gt;
Amazon has faced significant scrutiny and criticism, particularly concerning its treatment of workers, marketplace practices, data privacy issues, and its impact on small businesses. It has been involved in various regulatory and legal challenges related to anti-competitive behavior, safety, and consumer protection, with calls for increased oversight on its business operations.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
====Business model====&lt;br /&gt;
Amazon gets a majority of its revenue from seller fees and Amazon Prime memberships. In addition, Amazon has a &amp;quot;subscribe and save&amp;quot; option for some products. With this, the page to manage these subscriptions is obfuscated for the user, intentional or not.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
File:Amazon subscribe and save example 1.jpg|No &amp;quot;subscribe and save&amp;quot; option available.&lt;br /&gt;
File:Amazon subscribe and save example 2.jpg|The option appears in the &amp;quot;buy again&amp;quot; section.&lt;br /&gt;
File:Amazon subscribe and save example 3.jpg&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this company. Any incidents not mentioned here can be found in the [[:Category:Amazon|Amazon category]]. &lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
!Controversy&lt;br /&gt;
!Year&lt;br /&gt;
!Background info&lt;br /&gt;
!Aftermath&lt;br /&gt;
!Related article(s)&lt;br /&gt;
!Related video(s)&lt;br /&gt;
|-&lt;br /&gt;
|Amazon Prime Music including advertisements and removing downloads&lt;br /&gt;
|2026&lt;br /&gt;
|Amazon announced that In select countries such as &#039;&#039;&#039;India&#039;&#039;&#039;, the Amazon Prime Music subscription will now contain Advertisements remove download functionality for users.&lt;br /&gt;
|Ongoing.&lt;br /&gt;
|&amp;lt;!-- Remember to remove Left4Code&#039;s article (#2) when these are merged! - Left4Code. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#[[Amazon Prime Music ad insertion and download removal (2026)]]&lt;br /&gt;
#[[Amazon Prime Music including advertisements and removing downloads]]&lt;br /&gt;
|N/A&lt;br /&gt;
|-&lt;br /&gt;
|Amazon ends support for older Kindle devices.&lt;br /&gt;
|2026&lt;br /&gt;
|In early April 2026, a Reddit user posted about an email announcement from Amazon saying their device would not be able to download new content after May 20th, 2026.&lt;br /&gt;
|Starting May 20th, 2026, Amazon will end support for for Kindle e-readers and Fire tablets released before 2013. Although users will still be able to read existing books on their devices, they will no longer be able to download new content to the device.&lt;br /&gt;
|https://www.techrepublic.com/article/news-amazon-ends-support-older-kindles-2026/&lt;br /&gt;
|https://www.youtube.com/watch?v=Qtk7ERwlIAk&amp;amp;t=246s&lt;br /&gt;
|-&lt;br /&gt;
|Amazon increases the price to not see ads&lt;br /&gt;
|2026&lt;br /&gt;
|&amp;quot;...on April 10, 2026, Prime Video Ad Free will become Prime Video Ultra with enhanced viewing features, and your subscription price will increase by $4.99/month.&lt;br /&gt;
... From 04-14-2026, your subscription will automatically renew at $4.99/month, unless you cancel.&amp;quot;&lt;br /&gt;
|The price to not see ads in Prime Video will be increased. The users are notified by email that the subscription price is increased automatically unless extra action is taken.&lt;br /&gt;
|http://aboutamazon.com/news/entertainment/prime-video-ultra-ad-free-streaming-subscription&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon removing kindle books from old devices.&lt;br /&gt;
|2025&lt;br /&gt;
|As of May 26, 2025 Kindle for Android app versions released prior to March 2022 (v8.51 or earlier) no longer support Kindle content downloads.&lt;br /&gt;
|Old android devices (such as Galaxy Tab 4) that are not compatible with Android OS v.9.0+ are no longer able to download Kindle ebooks. Furthermore, Amazon &#039;forcibly&#039; removed any ebooks downloaded to the kindle app on those devices the next time they connected to the internet, without warning that this would occur.&lt;br /&gt;
|https://www.androidauthority.com/kindle-app-drm-loophole-3554844/&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon removing ability to download Kindle books&lt;br /&gt;
|2025&lt;br /&gt;
|Starting on February 26, 2025, Amazon removed a feature from its website allowing users to download purchased books to a computer and then copy them manually to a Kindle over USB.&lt;br /&gt;
|Starting February 26, 2025, the ‘Download &amp;amp; Transfer via USB’ option will no longer be available.&lt;br /&gt;
|[[Amazon Kindle removes download feature of purchased books]]&lt;br /&gt;
|[https://www.youtube.com/watch?v=KMoCzeGnIss &#039;&#039;&#039;Amazon are changing the way you own your Kindle books - you have 10 days to react&#039;&#039;&#039;]&lt;br /&gt;
&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=18 Feb 2025 |title=Amazon revokes the concept of owning books, can edit books you already bought; PIRACY IS THE ANSWER! |url=https://youtube.com/watch?v=XfcoUdWCB9M |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=XfcoUdWCB9M |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon Fresh/Go Stores&lt;br /&gt;
(Convenience &amp;amp; Grocery Brick and Mortar Stores)&lt;br /&gt;
|2024&lt;br /&gt;
|Revealed in 2024, Amazon&#039;s convenience stores powered by &amp;quot;AI&amp;quot; is really just human contractors from India watching people shop.&lt;br /&gt;
|&lt;br /&gt;
|[https://futurism.com/the-byte/amazon-abandons-ai-stores Amazon Abandons Grocery Stores Where You Just Walk Out With Stuff After It Turns Out Its “AI” Was Powered by 1,000 Human Contractors]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon sells lethal litterboxes&lt;br /&gt;
|2024&lt;br /&gt;
|Amazon sold knockoffs of Whisker brand &amp;quot;Litter-Robot&amp;quot; litterboxes that were designed in a unsafe way that led to the deaths of multiple cats, and posed a danger to young children.&lt;br /&gt;
|The responsible knockoff product was delisted, yet many other variants of the same product exist on the site.&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=10 Sep 2024 |title=Amazon litterbox fatally harms cat; this is the sad end result of what I&#039;ve talked about all year :( |url=https://youtube.com/watch?v=p6Y19nSPvC4 |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=p6Y19nSPvC4 |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon adds ads to premium subscription&lt;br /&gt;
|2023 – Present&lt;br /&gt;
|Amazon added advertisements to previously ad free subscriptions for Prime Video and Echo Show frames.&lt;br /&gt;
|Continues to occur.&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=26 Aug 2024 |title=Amazon charges extra to avoid ads, says &amp;quot;lol jk&amp;quot; &amp;amp; adds them anyway |url=https://youtube.com/watch?v=RSi6g5-xUaY |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=RSi6g5-xUaY |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=2 May 2024 |title=Amazon Hikes Profits by Forcing Ads on PAID Prime Subscribers |url=https://youtube.com/watch?v=ua_QL9YysHQ |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=ua_QL9YysHQ |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=28 Dec 2023 |title=Ads on Amazon Prime Video: Paying More for Less? 😒 |url=https://youtube.com/watch?v=VLFpU9aqtXc |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=VLFpU9aqtXc |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon allows fraudulent listings&lt;br /&gt;
|2014 – Present&lt;br /&gt;
|&lt;br /&gt;
|Fraudulent listings continue to be added, some removed.&lt;br /&gt;
|[[Amazon allows fraudulent product page after manual review]]&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=5 Aug 2024 |title=Amazon allows fraudulent product page after manual review! Deep dive on Amazon&#039;s support of scams |url=https://youtube.com/watch?v=qZCMislL6_I |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=qZCMislL6_I |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=14 Jan 2024 |title=Amazon&#039;s Reckless Bet: Hazardous Items Unfazed by Viral Scare |url=https://youtube.com/watch?v=7trdHLtsFKM |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=7trdHLtsFKM |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=30 Dec 2023 |title=Amazon Sells Fake Electrical Fuses |url=https://youtube.com/watch?v=B90_SNNbcoU |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=B90_SNNbcoU |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=21 Dec 2023 |title=Amazon&#039;s Illusion of Quality: How Dangerous Products Get Top Ratings! |url=https://youtube.com/watch?v=DiKflg8Uko4 |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=DiKflg8Uko4 |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=16 Dec 2023 |title=Amazon Sells Dangerous Electrical Crimps |url=https://youtube.com/watch?v=y83BS_mK9GE |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=y83BS_mK9GE |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=5 Aug 2023 |title=Amazon sells EOL devices as new after banning independents for quality control 🤣 |url=https://youtube.com/watch?v=Rhb0ID9z4aE |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=Rhb0ID9z4aE |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=24 Feb 2022 |title=Amazon has a credibility problem brewing |url=https://youtube.com/watch?v=XZNn2mO3dNQ |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=XZNn2mO3dNQ |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=24 Apr 2014 |title=Group Vertical eBay/Amazon Macbook screens are garbage; see for yourself! |url=https://youtube.com/watch?v=C0YNLWdj9sQ |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=C0YNLWdj9sQ |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon allows sellers to bribe customers for better ratings&lt;br /&gt;
|2016 – Present&lt;br /&gt;
|Amazon sellers give customers gift cards in exchange for positive product reviews; Amazon does nothing to stop this.&lt;br /&gt;
|Continues to occur.&lt;br /&gt;
|[[Amazon&#039;s history of seller bribery]]&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=16 Jul 2024 |title=Amazon sellers bribe customers for good reviews; Amazon does nothing |url=https://youtube.com/watch?v=eS698R-bxuc |website=Youtube |url-status=live |archive-url=https://preservetube.com/watch?v=eS698R-bxuc |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon has bad marketplace algorithms&lt;br /&gt;
|2023 – Present&lt;br /&gt;
|&lt;br /&gt;
|Algorithms still seem to be nonbeneficial.&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=4 Jan 2024 |title=Beyond Algorithms: Why Amazon&#039;s Automated Systems Fail Sellers &amp;amp; Customers |url=https://youtube.com/watch?v=tAaSXz8CBMc |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=tAaSXz8CBMc |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon trashes refurbished market&lt;br /&gt;
|2022 – 2023&lt;br /&gt;
|&lt;br /&gt;
|Unknown&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=18 Jul 2023 |title=Apple &amp;amp; Amazon pay a fine for trashing the refurbished market |url=https://youtube.com/watch?v=h3qgbvq2SWs |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=h3qgbvq2SWs |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=8 Sep 2022 |title=eBay follows amazon&#039;s lead, consolidating &amp;amp; destroying the refurbished marketplace |url=https://youtube.com/watch?v=qzUXmeaZsIQ |url-status=live |website=Youtube |archive-url=https://www.preservetube.com/watch?v=qzUXmeaZsIQ |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon cancels associate account after recent negative media coverage, with a different reason&lt;br /&gt;
|2023&lt;br /&gt;
|&lt;br /&gt;
|Unknown&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=22 Jun 2023 |title=Amazon cancelled my account after exposing their wrongful lockout of a paying customer |url=https://youtube.com/watch?v=Kcohq313q00 |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=Kcohq313q00 |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon wrongfully suspends account of home owner&lt;br /&gt;
|2023&lt;br /&gt;
|A home owner was locked out of their Amazon account for nearly a week, after a delivery driver from Amazon misheard an automated message from their Eufy doorbell.&lt;br /&gt;
|Account reinstated.&lt;br /&gt;
|[[Amazon locks home owner out of Amazon account over allegation by Amazon delivery driver|Amazon locks home owner out of amazon account over allegation by amazon delivery driver]]&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=18 Jun 2023 |title=Man locked out of amazon account over his doorbell gets account back, but no apology |url=https://youtube.com/watch?v=SyEgD-5GK9c |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=SyEgD-5GK9c |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=12 Jun 2023 |title=Amazon accuses customer of racism &amp;amp; shuts down their smart home - enough cloud junk |url=https://youtube.com/watch?v=NfiIXooD77s |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=NfiIXooD77s |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon engages in anticompetitive behavior&lt;br /&gt;
|2021 – 2022&lt;br /&gt;
|&lt;br /&gt;
|Unknown&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=18 Sep 2022 |title=Amazon forces sellers to keep prices high on other platforms |url=https://youtube.com/watch?v=YBJoSGWdP0Y |website=Youtube |url-status=live |archive-url=https://www.preservetube.com/watch?v=YBJoSGWdP0Y |archive-date=21 Nov 2025}}&amp;lt;/ref&amp;gt; &amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=15 Feb 2026 |title=Amazon copying products/rigging search results |url=https://youtube.com/watch?v=XCLx4mVJ4gk |url-status=live |website=Youtube |archive-url=https://www.preservetube.com/watch?v=XCLx4mVJ4gk |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon sells fake electrical fuses&lt;br /&gt;
|2023 – Present&amp;lt;!-- Year may be wrong, just following the video release year --&amp;gt;&lt;br /&gt;
|Fuses are being sold that do not blow when supplied more power than it is intended to handle, which is a major safety risk.&lt;br /&gt;
|These fuses are still being sold to this day.&lt;br /&gt;
|[[Amazon allows fraudulent product page after manual review! Deep dive on Amazons support of scams]]&lt;br /&gt;
|&amp;lt;ref group=&amp;quot;Video References&amp;quot;&amp;gt;{{Cite web |last=Rossmann |first=Louis |date=30 Dec 2023 |title=Amazon Sells Fake Electrical Fuses |url=https://youtube.com/watch?v=B90_SNNbcoU |url-status=live |website=Youtube |archive-url=https://preservetube.com/watch?v=B90_SNNbcoU |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Amazon PhotosPlus discontinuation&lt;br /&gt;
|2024&lt;br /&gt;
|&lt;br /&gt;
|Since September 2024, it is no longer possible to use the Amazon Echo Show 8 as a digital frame without advertisements.&lt;br /&gt;
|[[Amazon PhotosPlus discontinuation]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon uses [[dark patterns]] for its premium subscription&lt;br /&gt;
|2023 – Present&lt;br /&gt;
|Systematically designing the cancelling steps to be complicated and long; using tricks to enroll users into the subscription.&amp;lt;ref&amp;gt;{{cite web |date=2023-06-21 |title=FTC Takes Action Against Amazon for Enrolling Consumers in Amazon Prime Without Consent and Sabotaging Their Attempts to Cancel |url=https://www.ftc.gov/news-events/news/press-releases/2023/06/ftc-takes-action-against-amazon-enrolling-consumers-amazon-prime-without-consent-sabotaging-their |url-status=live |archive-url=https://web.archive.org/web/20250129015417/https://www.ftc.gov/news-events/news/press-releases/2023/06/ftc-takes-action-against-amazon-enrolling-consumers-amazon-prime-without-consent-sabotaging-their |archive-date=2025-01-29 |website=[[Federal Trade Commission]]}}&amp;lt;/ref&amp;gt; See &amp;quot;Project Illiad&amp;quot;.&lt;br /&gt;
|Continues to occur.&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon removes option to lend Kindle e-books&lt;br /&gt;
|2022&lt;br /&gt;
|E-books marked with &amp;quot;lending enabled&amp;quot; could be lent to other Kindle users for a period of time during which the title is unavailable to the sender.&lt;br /&gt;
|Since August 2022, it is not possible to borrow Kindle books.&lt;br /&gt;
|&lt;br /&gt;
|[https://www.youtube.com/watch?v=hAvFmnuZZMI &#039;&#039;&#039;Amazon Discontinues Lending Kindle e-Books&#039;&#039;&#039;]&lt;br /&gt;
|-&lt;br /&gt;
|Amazon removes option not to send voice recordings from Echo devices&lt;br /&gt;
|2025&lt;br /&gt;
|In March 2025, Echo customers with the option &amp;quot;Do Not Send Voice Recordings&amp;quot; enabled received an e-mail that local processing will no longer be supported on their device.&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-18 |title=TechLinked – Microsoft’s Big Oopsie – Echo voice recordings, Gemini watermarks |url=https://youtu.be/DhXH83O6pXc?t=268 |url-status=live |archive-url=https://preservetube.com/watch?v=DhXH83O6pXc |archive-date=2025-03-18 |access-date=2025-03-18 |website=YouTube – TechLinked}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|&lt;br /&gt;
|[[Amazon Echo changes terms of voice usage]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon discontinues Appstore for Android devices&lt;br /&gt;
|2025&lt;br /&gt;
|On August 20, 2025, Amazon will remove Android devices&#039; access to the Amazon Appstore.&lt;br /&gt;
|Android apps downloaded through the Amazon Appstore will cease to function.&lt;br /&gt;
|[[Amazon revokes access to their Appstore on non-Amazon devices|Amazon pulls the plug on its Android app store that you never used anyway]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon removes kindle books from user libraries.&lt;br /&gt;
|2009&lt;br /&gt;
|In 2009, Amazon removed 2 illegally published books, Animal Farm and 1984, from sale and user libraries, along with any notes and annotations made by the reader. Others have also reported missing books from their libraries.&lt;br /&gt;
|Those affected have been given refunds and there haven&#039;t been any further documented cases of books being removed from readers&#039; libraries, although user reports are still prevalent.&amp;lt;ref&amp;gt;{{Cite web |last=A |first=Georgie |date=13 Nov 2022 |title=Bought books removed by Amazon. |url=https://www.amazonforum.com/s/question/0D56Q0000ALx14HSQR/bought-books-removed-by-amazon |url-status=live |archive-url=http://web.archive.org/web/20250813120836/https://www.amazonforum.com/s/question/0D56Q0000ALx14HSQR/bought-books-removed-by-amazon |archive-date=13 Aug 2025|access-date=12 Aug 2025 |website=Amazon}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|[https://archive.nytimes.com/www.nytimes.com/2009/07/18/technology/companies/18amazon.html Amazon Erases Orwell Books From Kindle]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon purposely delays assisting customers with lost packages&lt;br /&gt;
|2025&lt;br /&gt;
|Amazon has been found delaying assistance to customers who contact customer service to report issues with a order (i.e., a missing package). Amazon states they are unable to take any action until a certain date, delaying the resolution process further in hopes the customer will not contact them again to request a refund.&lt;br /&gt;
|Unknown&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon adds ads on the lockscreen&#039;s of Amazon Fire Tablets &amp;amp; Amazon Kindle&lt;br /&gt;
|2012 - Present&lt;br /&gt;
|Amazon shows ads on both the Kindle &amp;amp; Fire Tablets lockscreen&#039;s to get money out of your purchases makes you pay a fee to remove them. This only applies to the cheaper models.&lt;br /&gt;
|This practice still occurs, but is very easy to remove through a quick search.&lt;br /&gt;
|[https://xdaforums.com/t/windows-linux-tool-fire-toolbox-v42-1.3889604/ Fire Toolbox] &lt;br /&gt;
[https://www.amazon.com/gp/help/customer/display.html?nodeId=T70xcAGUDQ4cR5PwPR Learn More About Ads On Kindle Fire and Fire Tablet - Amazon]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon ends support for Fire TV Blaster&#039;s making them unusable&lt;br /&gt;
|2026&lt;br /&gt;
|Amazon ends support for the Fire TV Blaster on January 31, 2026&lt;br /&gt;
|&lt;br /&gt;
|[https://www.heise.de/en/news/Amazon-makes-Fire-TV-Blaster-unusable-11145570.html Amazon makes Fire TV Blaster&#039;s unusable]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Amazon cancels order, and requiring age verification to reorder&lt;br /&gt;
|2026&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|https://www.youtube.com/watch?v=wKDpMel08LM&lt;br /&gt;
|-&lt;br /&gt;
|Amazon Luna removes access to purchased games, offers no refunds&lt;br /&gt;
|2026&lt;br /&gt;
|Starting April 10, 2026, Amazon Luna ceased offering individual game purchases and third-party subscriptions (EA, Ubisoft+, GOG, Jackbox). The &amp;quot;Bring Your Own Library&amp;quot; feature, allowing users to stream games from linked accounts on Luna, was also removed.&lt;br /&gt;
|Purchased games remain &#039;&#039;&#039;playable via streaming only until June 10, 2026, after which they become inaccessible on Luna&#039;&#039;&#039;. Amazon explicitly stated it will not offer refunds for a-la-carte game purchases, contrasting with Google&#039;s full-refund policy when it shut down Stadia. Amazon offered Luna Premium subscriptions only to &amp;quot;qualifying&amp;quot; users.&lt;br /&gt;
|[https://www.theverge.com/tech/910025/amazon-luna-third-party-games-subscriptions Amazon Luna axes third Party game purchases] &lt;br /&gt;
[https://kotaku.com/amazons-luna-service-removing-access-to-purchased-games-and-is-offering-no-refunds-2000686688 Amazon&#039;s Game streaming service removing access to Purchased Games And Offering no refunds]&lt;br /&gt;
&lt;br /&gt;
[https://alternativeto.net/news/2026/4/amazon-luna-is-slowly-starting-to-die-killing-game-purchases-and-third-party-subscriptions/ Amazon Luna in its demise is slowly killing game purchases]&lt;br /&gt;
&lt;br /&gt;
[https://www.siliconera.com/amazon-luna-purchased-games-will-be-unplayable-after-june-2026/ Amazon Luna purchased games will be unplayable After June 2026]&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Products==&amp;lt;!-- Considering the sheer amount of products Amazon has, we should consider the table format --&amp;gt;&lt;br /&gt;
===Amazon Prime (&#039;&#039;2005–Present&#039;&#039;)===&lt;br /&gt;
Amazon uses [[dark patterns]] for its subscription services, including tricking users into subscribing and making it very complicated to cancel. Moreover, some features of the service, such as free deliveries, are region locked to where you initially subscribed, forcing you to buy another subscription to be able to use the service.&amp;lt;ref&amp;gt;{{Cite web |last=Mabood |first=Wasay |date=2023-02-22 |title=Geo-block Content Using Amazon Location and Edge Services |url=https://aws.amazon.com/de/blogs/networking-and-content-delivery/geo-block-content-using-amazon-location-and-edge-services/ |url-status=live |archive-url=https://web.archive.org/web/20260415190723/https://aws.amazon.com/de/blogs/networking-and-content-delivery/geo-block-content-using-amazon-location-and-edge-services/ |archive-date=2026-04-15 |access-date=2026-04-06 |website=[[Amazon Web Services (AWS)]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Prime video further only allows for HD streaming on Windows and MacOS, despite streaming services such as Netflix allowing HD streaming on Linux &amp;lt;ref&amp;gt;{{Cite web |title=Prime Video System Requirements for Computers |url=https://www.amazon.com/gp/help/customer/display.html/ref=atv_unsupported_systems_bannerlink?nodeId=GUVGB3QMQRYRERYW |archive-url=https://web.archive.org/web/20260214133717/https://www.amazon.com/gp/help/customer/display.html?nodeId=GUVGB3QMQRYRERYW |archive-date=2026-02-14}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Amazon Kindle (&#039;&#039;2007–Present&#039;&#039;)===&lt;br /&gt;
Amazon has progressively removed options for products purchased through the Kindle, effectively changing the meaning of purchases and ownership. It first removed the ability of users to lend e-books to one another, and later removed the ability to download purchased e-books to a computer.&lt;br /&gt;
&lt;br /&gt;
===Amazon Appstore (&#039;&#039;2011–Present&#039;&#039;)===&lt;br /&gt;
Amazon Appstore is the primary app store for Amazon&#039;s Fire devices, and is also available on other Android devices. On August 20, 2025, Amazon has removed access to the app store for all non-Fire devices. Apps installed on non-Fire devices from the Amazon Appstore have ceased to function but Fire devices are still to be able to access the Amazon Appstore.&amp;lt;ref&amp;gt;{{Cite web |last=Doffman |first=Zak |date=17 Aug 2025 |title=Amazon’s App Store Deadline—Stop Using Your Apps In 48 Hours |url=https://www.forbes.com/sites/zakdoffman/2025/08/17/amazons-app-store-decision-48-hours-to-delete-your-apps/ |url-status=live |archive-url=http://web.archive.org/web/20251122155445/https://www.forbes.com/sites/zakdoffman/2025/08/17/amazons-app-store-decision-48-hours-to-delete-your-apps/ |archive-date=22 Nov 2025|access-date=30 Nov 2025 |website=Forbes}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Ravi |first=Nandika |date=20 Feb 2025 |title=Amazon will suspend support for its Appstore on Android |url=https://www.androidcentral.com/apps-software/amazon-will-suspend-support-for-its-appstore-on-android |url-status=live |archive-url=http://web.archive.org/web/20260222204353/https://www.androidcentral.com/apps-software/amazon-will-suspend-support-for-its-appstore-on-android |archive-date=22 Feb 2026|access-date=30 Nov 2025 |website=Android Central}}&amp;lt;/ref&amp;gt; There was no restitution for non-Fire users who may have purchased paid apps through the Amazon Appstore.&amp;lt;ref&amp;gt;{{Cite web |title=Amazon Appstore on Android has been discontinued. |url=https://www.amazon.com/b?node=210942225011 |url-status=live |website=Amazon}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Maruccia |first=Alfonso |date=2025-02-21 |title=Amazon pulls the plug on its Android app store after 14 years |url=https://www.techspot.com/news/106872-amazon-appstore-android-discontinued-summer.html |url-status=live |website=TECHSPOT}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Powel |first=James |date=2025-08-17 |title=The Amazon Appstore shuts down on Androids Aug. 20. Will you get a refund? |url=https://www.aol.com/amazon-appstore-shuts-down-androids-212404113.html |url-status=live |website=AOL / USA Today}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Amazon Alexa (&#039;&#039;2013–Present&#039;&#039;)===&lt;br /&gt;
On July 1st 2024, Amazon removed third-party list support from the Alexa service, resulting in only lists hosted by Amazon being supported&amp;lt;ref&amp;gt;{{Cite web |access-date=2025-09-16 |title=Deprecated Features |website=Amazon Developer Documentation |url=https://developer.amazon.com/en-US/docs/alexa/ask-overviews/deprecated-features.html#shopping-lists |archive-url=https://web.archive.org/web/20250522134122/https://developer.amazon.com/en-US/docs/alexa/ask-overviews/deprecated-features.html#shopping-lists |archive-date=2025-05-22 }}&amp;lt;/ref&amp;gt;. While it is still possible to manage lists via Alexa skills, these now require the skill activation phrase to be used (e.g. &amp;quot;Alexa, ask AnyList to add XYZ to my shopping list&amp;quot;). This followed from a [[Google#Google Assistant 3rd Party List Support|similar move by Google]] in 2023.&lt;br /&gt;
&lt;br /&gt;
Sometime in 2025 Amazon added an upgrade nag widget to Alexa for &amp;quot;Alexa+&amp;quot; that is impossible to turn off. In some cases the upgrade was automatic, and users had to opt-out&amp;lt;ref&amp;gt;{{Cite web |last=Campbell-Hicks |first=Jennifer |date=2026-01-13 |title=Amazon is automatically upgrading Prime members to Alexa+. Here&#039;s how to opt out |url=https://www.12news.com/article/news/nation-world/amazon-automatic-upgrade-alexa-plus-how-to-opt-out/507-3105c319-0f52-421a-b741-9ad6919f22e5 |url-status=live |archive-url=https://ghostarchive.org/archive/eAbrI |archive-date=2026-04-15 |website=[[12news]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Amazon Echo (&#039;&#039;2014–Present&#039;&#039;)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Amazon Luna (&#039;&#039;2020—2026&#039;&#039;)===&lt;br /&gt;
Amazon Luna is Amazon&#039;s cloud gaming service, launched in 2020 as a competitor to Xbox Cloud Gaming and Google Stadia. In April 2026, Amazon abruptly ended support for individual game purchases and third-party storefronts including EA, GOG, and Ubisoft, stripping the platform of its &amp;quot;own your games&amp;quot; model. Previously purchased games will be rendered unplayable via Luna as of June 10, 2026, with no refunds offered. Save-game data can be downloaded until September 8th, 2026.  &lt;br /&gt;
&lt;br /&gt;
Amazon is switching to a subscription model called Luna Premium, which does not allow purchases of individual video games.  &lt;br /&gt;
&lt;br /&gt;
Support article: https://www.amazon.com/gp/help/customer/display.html?nodeId=TY9Z4zZ7vgVwLA0b7C&lt;br /&gt;
&lt;br /&gt;
===Amazon PhotosPlus (&#039;&#039;2023–2024&#039;&#039;)===&lt;br /&gt;
Amazon sold physical devices that could displaying photos stored in its Amazon Photos cloud storage through its PhotosPlus service. Less than one year later, it cancelled the service, which [[Retroactively amended purchase|changed the functionality]] of the devices, including showing advertisements every few hours.&amp;lt;ref&amp;gt;{{Cite web |last=Roth |first=Emma |date=21 Aug 2024 |title=Amazon cancels the Echo Show 8 Photos Edition’s main feature — focusing on photos |url=https://www.theverge.com/2024/8/21/24225149/amazon-end-photosplus-subscription-echo-show-8-photos-edition |url-status=live |archive-url=http://web.archive.org/web/20251216124644/https://www.theverge.com/2024/8/21/24225149/amazon-end-photosplus-subscription-echo-show-8-photos-edition |archive-date=16 Dec 2025|access-date=4 Apr 2025 |website=The Verge}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
===All Louis Rossmann videos covering Amazon===&lt;br /&gt;
&amp;lt;references group=&amp;quot;Video References&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=User:Iii&amp;diff=56195</id>
		<title>User:Iii</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=User:Iii&amp;diff=56195"/>
		<updated>2026-06-05T01:32:53Z</updated>

		<summary type="html">&lt;p&gt;Iii: created my user page, with a few details about me&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi! I am new to this wiki.&lt;br /&gt;
&lt;br /&gt;
I came here after I started increasingly watching more and more of Louis Rossmann&#039;s videos.&lt;br /&gt;
&lt;br /&gt;
I live in Australia. My time zone is AEST or AEDT, depending on the time of year.&lt;br /&gt;
&lt;br /&gt;
I have some previous wiki experience on an entertainment/media related wiki (on wiki.gg).&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google&amp;diff=56192</id>
		<title>Google</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google&amp;diff=56192"/>
		<updated>2026-06-05T01:13:52Z</updated>

		<summary type="html">&lt;p&gt;Iii: Style/grammar edits, and edits to section &amp;quot;Target API level requirements for Google Play apps&amp;quot;.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup|Issue 1=Article formatting should follow [[Template:CompanyPreload]]. With Google&#039;s history, it may be useful to use tabling for incidents.|Issue 2=Citations need to follow proper formatting. See [[Template:Cite web]].|Issue 3=Citations should be placed after punctuation.|Issue 4=Make sure that section headers are in sentence case where applicable.}}&lt;br /&gt;
{{CompanyCargo&lt;br /&gt;
|Founded=1998&lt;br /&gt;
|Industry=Technology&lt;br /&gt;
|Logo=Google.webp&lt;br /&gt;
|ParentCompany=Alphabet Inc.&lt;br /&gt;
|Type=Subsidiary&lt;br /&gt;
|Description=Google is one of the most influential technology companies in the world, originally known for developing the most widely used search engine.&lt;br /&gt;
|Website=https://www.google.com/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;{{Wplink|Google|Google LLC}}&#039;&#039;&#039;, founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.&amp;lt;ref&amp;gt;{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com |archive-url=http://web.archive.org/web/20260222070659/https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |archive-date=22 Feb 2026}}&amp;lt;/ref&amp;gt; Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.&amp;lt;ref&amp;gt;{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025 |archive-url=http://web.archive.org/web/20260128182647/https://about.google/products/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Google Search| Google&#039;s search engine]] remains its most well-known service, but the company has significantly diversified its offerings. Key products include the [[Android]] operating system, the [[Google Chrome]] web browser, [[Google Drive]] for cloud storage, [https://wikipedia.org/wiki/Google_Maps Google Maps], [[YouTube]], and [[wikipedia:Google_Play|Google Play]].&amp;lt;ref&amp;gt;{{Cite web |title=Helpful products, built with you in mind |url=https://about.google/intl/ALL_us/products/ |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20260205114442/https://about.google/intl/ALL_us/products/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;{{Citation needed}} Additionally, the company provides digital advertising services through Google Ads, generating the majority of its revenue.&amp;lt;ref&amp;gt;{{Cite web |date=4 Feb 2025 |title=Alphabet Announces Fourth Quarter and Fiscal Year 2024 Results |url=https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251002181452/https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |archive-date=2 Oct 2025}}&amp;lt;/ref&amp;gt; In recent years, Google has also developed hardware products such as the Pixel smartphone and Nest smart home devices.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
Google has faced ongoing scrutiny related to data privacy, competition, and its dominant position in the market, such concerns have stretched as far back as 2012.&amp;lt;ref&amp;gt;{{Cite web |last=Cohen |first=Adam |date=5 Mar 2012 |title=Will We Ever Get Strong Internet Privacy Rules? |url=https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |url-status=live |access-date=5 Apr 2025 |website=Time |archive-url=http://web.archive.org/web/20260205121437/https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=6 Sep 2023 |title=REPORT: Google at 25: From “Don’t Be Evil” To ¯\_(ツ)_/¯ |url=https://techoversight.org/2023/09/06/google-at-25/ |url-status=live |access-date=5 Apr 2025 |website=The Tech Oversight Project |archive-url=http://web.archive.org/web/20251004223929/https://techoversight.org/2023/09/06/google-at-25/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; The company has been the subject of various legal and regulatory challenges, particularly concerning antitrust issues, the use of personal data, and its impact on consumer choice.{{Citation needed}} The US government is currently engaged in an antitrust lawsuit against Google, with a decision expected early 2025.&amp;lt;ref&amp;gt;{{Cite web |date=25 Nov 2024 |title=Closing Arguments, November 25: Once, Twice, Three Times a Monopolist |url=https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |url-status=live |access-date=5 Apr 2025 |website=US v Google |archive-url=http://web.archive.org/web/20250906103632/https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |archive-date=6 Sep 2025}}&amp;lt;/ref&amp;gt; {{UpdateNeeded|date={{subst:August}} {{subst:2025}}|reason=We need updates on this situation.}}&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
In December 2024, Google announced to organisations that use its advertising products, that from 16 February 2025, it will no longer prohibit them from employing [[wikipedia:Fingerprint_(computing)|fingerprinting]] techniques.&amp;lt;ref&amp;gt;{{Cite web |last=Almond |first=Stephen |date=19 Dec 2024 |title=Our response to Google’s policy change on fingerprinting |url=https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |url-status=live |access-date=5 Apr 2025 |website=ico. |archive-url=http://web.archive.org/web/20260128163957/https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===User freedom===&lt;br /&gt;
Google has a long history of patronizing their user base by taking away options or not giving users a choice in the first place.&lt;br /&gt;
&lt;br /&gt;
For example, in 2014, Google removed normal MicroSD write access on Android 4.4,&amp;lt;ref&amp;gt;{{cite news |first=Cody |last=Toombs |url=https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |title=External Blues: Google Has Brought Big Changes To SD Cards In KitKat, And Even Samsung Is Implementing Them |url-status=live |date=17 Feb 2014 |url-status=live |website=Android Police |archive-url=https://web.archive.org/web/20140218064033/https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |archive-date=2014-02-18}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |date=23 Feb 2014 |title=Re: What about removable SD card in 4.4 |website=Google Groups |archive-url=https://web.archive.org/web/20260209114224/https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |archive-date=2026-02-09 }}&amp;lt;/ref&amp;gt; limiting each application to their own dedicated folder, arguing that this makes it easy to remove all files left by the app during uninstallation, given that no app can leave files outside their own dedicated folder.&lt;br /&gt;
&lt;br /&gt;
No menu option to change this behaviour was given to the user, therefore users who wanted to restore normal write access were forced to resort to unofficial methods involving bootloader unlocking and rooting.&lt;br /&gt;
&lt;br /&gt;
It should be noted that Google&#039;s own Android smartphones and tablet computers (Nexus and Pixel devices) never featured a memory card slot. Similar restrictions were later added to USB on-the-go storage.&amp;lt;ref name=android-traditional-storage&amp;gt;{{cite web |title=Traditional storage &amp;amp;#124; Android Open Source Project |url=https://source.android.com/docs/core/storage/traditional |url-status=live |website=Android}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2018, Google added a clipboard manager to their keyboard app, Gboard.&amp;lt;ref&amp;gt;{{cite web |url=https://www.xda-developers.com/gboard-clipboard-manager/ |title=Gboard 7.7 adds a Clipboard Manager feature to Google&#039;s keyboard app |date=22 Oct 2018 |first=Mishaal |last=Rahman |url-status=live |website=XDA Developers |archive-url=https://web.archive.org/web/20190119233536/https://www.xda-developers.com/gboard-clipboard-manager/ |archive-date=2019-01-19}}&amp;lt;/ref&amp;gt; But in 2022, Google decided on behalf of their users that they don&#039;t need to retain clipboard items for any longer than one hour. Therefore, they added a one-hour time limit, meaning any clipboard item older than one hour is automatically deleted, with no option to change this behaviour. The only way to retain clipboard items for more than one hour is to manually mark them as &amp;quot;pinned&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |first=Ethan |last=Gillian |title=Remember: Android 13 clears clipboard 1 hour after copying |url=https://techzle.com/remember-android-13-clears-clipboard-1-hour-after-copying |url-status=live |website=Techzle |date=17 Aug 2022}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2019, Google took away the ability to turn off the &amp;quot;pull-to-refresh&amp;quot; gesture on the mobile edition of their Chrome web browser, following by refusing to reinstate the option after an abnormally high number of complaints that the gesture causes accidental refreshes. See [[Google_Chrome#Mandatory_pull-to-refresh|Google Chrome § Mandatory pull-to-refresh]].&lt;br /&gt;
&lt;br /&gt;
Google lets app developers arbitrarily [[screenshot blocking|prevent device owners from capturing screenshots and screen recordings]] on Android. While the original intention was to prevent sensitive information in banking apps from getting outside, it has been severely overused by app developers and prevents legitimate uses such as asking for help in forums and bug reports. Google provided no option for device owners to override it, so the only way is to unlock the bootloader and modify the operating system.&amp;lt;ref&amp;gt;{{cite web |url=https://www.howtogeek.com/why-screenshots-dont-always-work-especially-in-secure-apps/ |website=How To Geek |author=Faisal Rasool |title=Why Your Phone Blocks Screenshots in Secure Apps |date=2025-08-23 |access-date=2026-05-26 }}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=konradkar |url=https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |website=[[Reddit]] |title=Booking.com app disallow to take screenshot, can I bypass this? |date=2020-02-14 |access-date=2026-05-26 |archive-url=https://web.archive.org/web/20230615071612/https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |archive-date=2023-06-15}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{excerpt|Android Developer Verification}}&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
===Account lockouts===&lt;br /&gt;
Google has been reported to have randomly locked people out of their accounts due to ostensible security reasons, which are not lifted even if the user had provided the correct credentials and/or even if the user have correctly followed all the verification prompts such as SMS verification. These have caused anguishes for many affected users who are unable to access their contents, emails and services as a result. Furthermore, some had reported that they are forced to undergo SMS verification even when recovery email addresses are already configured to their accounts, thereby likely constituting instances of [[Forced identification|forced verification]] in broad senses.&amp;lt;ref&amp;gt;{{cite web |url=https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |date=5 May 2021 |author=Feniks_Gaming |title=Mike Rose (No More Robots Publisher) Locked out of Gmail, speaks to google support to find out their own staff are locked out of their personal Gmail too... |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210505101632/https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |archive-date=2021-05-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |first=Mike |last=Rose |url-status=dead |date=4 May 2021 |title=This morning, I was locked out of my Google account |website=Nitter |archive-url=https://web.archive.org/web/20220908195211/https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |archive-date=2022-09-08}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |title=FYI: Google can lock you out of your account for no reason |author=danielrosehill |date=5 Aug 2021 |url=https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210805030048/https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |archive-date=2021-08-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=LegitimateAttempt4 |date=20 Jul 2023 |title=DAE noticed that Google had taken security account lockouts to a zealotic level? |url-status=live |url=https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |website=[[Reddit]] |archive-url=http://web.archive.org/web/20230720181226/https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |archive-date=2023-07-20}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Deletion of inactive accounts===&lt;br /&gt;
In May 2023, Google announced that [[Inactive account deletion|deletion of inactive user accounts]] would occur starting in December 2023, citing security reasons, noting that old and unused accounts are more likely to be compromised. Google claimed that &amp;quot;Forgotten or unattended accounts often rely on old or re-used passwords that may have been compromised, have not had two factor authentication set up, and receive fewer security checks by the user,&amp;quot; while saying that Google &amp;quot;has no plans to delete [[YouTube]] videos&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |last1=Lawler |first1=Richard |title=Google might delete your Gmail account if you haven&#039;t logged in for two years |url=https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |website=The Verge |access-date=21 December 2023 |language=en |date=16 May 2023 |archive-url=http://web.archive.org/web/20260205121216/https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Porter |first1=Jon |title=Reminder: Google is about to start purging inactive accounts |url=https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |website=The Verge |access-date=21 December 2023 |language=en |date=28 November 2023 |archive-url=http://web.archive.org/web/20251212230239/https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Amadeo |first1=Ron |title=Google&#039;s new &amp;quot;inactive account&amp;quot; policy won&#039;t delete years of YouTube videos |url=https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |website=Ars Technica |access-date=21 December 2023 |language=en-us |date=17 May 2023 |archive-url=http://web.archive.org/web/20251212092014/https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt; The decision to delete inactive accounts has sparked some criticism and backlash. The cited security rationale behind such decision was ridiculed and was compared to a hypothetical scenario where a bank should be burned down if it is not secure against robbers.&amp;lt;ref&amp;gt;{{cite web |last1=Novet |first1=Jordan |title=Google&#039;s plan to purge inactive accounts isn&#039;t sitting well with some users |url=https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |website=CNBC |access-date=21 December 2023 |language=en |date&lt;br /&gt;
=19 August 2023 |archive-url=http://web.archive.org/web/20250831223936/https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |archive-date=31 Aug 2025}}&amp;lt;/ref&amp;gt; Such policies could adversely affect those who had good reasons to become inactive for a long time, such as hospitalization, prison incarceration, and being in totalitarian countries which have prolonged internet shutdowns. Moreover, the Anonymous hacktivist collective has protested against the decision to delete inactive accounts multiple times, describing them as &amp;quot;harsh&amp;quot; and saying that the decision will &amp;quot;destroy history&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |date=18 Jul 2023 |title=Anonymous puts Taiwan flag, national anthem on 2 UN websites |url=https://www.taiwannews.com.tw/en/news/4946597 |first=Keoni |last=Everington |url-status=live |access-date=21 Dec 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20231014070719/https://www.taiwannews.com.tw/en/news/4946597 |archive-date=2023-10-14}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=18 Oct 2023 |title=&#039;Anonymous&#039; hacks Chinese government site to protest Israel–Hamas war |url-status=live |url=https://www.taiwannews.com.tw/en/news/5022840 |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240221120716/https://www.taiwannews.com.tw/en/news/5022840 |archive-date=2024-02-21}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=8 Dec 2023 |title=Anonymous posts Taiwan flag on UN site |website=Taiwan News |url=https://www.taiwannews.com.tw/en/news/5055454 |url-status=live |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240228035811/https://www.taiwannews.com.tw/en/news/5055454 |archive-date=2024-02-28}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anti-competitive practices===&lt;br /&gt;
Google has a great history of anti-competitive practices. For example, in 2020 the company was sued for practices involving pushing off relevant search results in order to favor advertisements and the inclusion of [[bloatware]] on Android devices.&amp;lt;ref&amp;gt;{{Cite web |publisher=Eaton Business School|date=31 Aug 2021 |title=Google - A display of anti-competitive behaviour|url=https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |url-status=live |archive-url=https://web.archive.org/web/20250523013602/https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |archive-date=2025-05-23 |access-date=25 May 2026 |website=Eaton Business School}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The [[Android Developer Verification]] program prevents sideloading and external app stores, such as [[F-Droid]] to be an available alternative to the Google Play Store.&lt;br /&gt;
&lt;br /&gt;
===Google device repair program restrictions===&lt;br /&gt;
{{Main|Google asserts the right to seize your phone during a repair}}&lt;br /&gt;
Google&#039;s Service &amp;amp; Repair Program terms explicitly state that any device containing non-Google-authorized parts &amp;quot;will not be returned&amp;quot; to the customer.&lt;br /&gt;
&lt;br /&gt;
===Target API level requirements for Google Play apps===&lt;br /&gt;
Google has a policy that requires apps for Android to target recent API levels, in order to appear in the Play Store, depending on a user&#039;s device&#039;s version of Android, or if it is a new app.&amp;lt;ref&amp;gt;{{Cite web |date=31 Aug 2024 |title=Policy Center |url=https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |access-date=May 9, 2025 |website=Play Console Help |archive-url=http://web.archive.org/web/20260215054419/https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; This creates a continuous cycle of maintenance and redevelopment that can be especially burdensome for smaller developers, indie creators, and consumers.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
The requirement for apps to target newer APIs each year serves some legitimate security and feature purposes. However, it also effectively functions as a form of forced obsolescence. Even perfectly functional apps that don&#039;t need technical updates must be regularly reworked just to remain visible on the Play Store.&lt;br /&gt;
&lt;br /&gt;
This creates several issues:&lt;br /&gt;
&lt;br /&gt;
*Development resources must be allocated to updating apps rather than creating new features&lt;br /&gt;
*Smaller teams and individual developers are placed at a disadvantage attempting to keep up with the constant update cycle&lt;br /&gt;
*Legacy apps that are no longer actively maintained disappear, even if they&#039;re still useful&lt;br /&gt;
*The cost of maintaining apps increases, potentially making some projects financially nonviable&lt;br /&gt;
*Losing access to previously purchased apps when upgrading devices&lt;br /&gt;
*Users being unable to reinstall older apps that worked perfectly well for their needs&lt;br /&gt;
*Facing unexpected costs to replace functionality they&#039;ve already paid for&lt;br /&gt;
*Dealing with the frustration of discovering favorite apps have disappeared&lt;br /&gt;
&lt;br /&gt;
While Google argues this approach improves the Android ecosystem&#039;s security and functionality, it does place a significant burden on developers and can lead to the premature &amp;quot;death&amp;quot; of otherwise functional applications.&lt;br /&gt;
&lt;br /&gt;
This creates a troubling disconnect in digital ownership. Consumers reasonably expect that when they purchase an app, they should maintain access to it across their devices over time. Instead, they discover their digital purchases can effectively vanish due to policy decisions beyond their control.&lt;br /&gt;
&lt;br /&gt;
===Ban on third-party tech support ads===&lt;br /&gt;
Google prohibits tech support ads on their platform if they are not authorized by the manufacturer.&amp;lt;ref&amp;gt;{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google |archive-url=http://web.archive.org/web/20251112170608/https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |archive-date=12 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===The chargeback incident===&lt;br /&gt;
In November 2022, a Google customer accidentally purchased two Google Pixel smartphones instead of one, directly from Google (no third-party reseller), and tried to return one package to Google for a refund, but the shipping was unsuccessful.&lt;br /&gt;
&lt;br /&gt;
A Google customer support person suggested the customer to perform a chargeback. The customer acted accordingly without understanding the implications, resulting in the termination of their Google account shortly after. The account was 15 years old at that time.&amp;lt;ref&amp;gt;{{cite web |first=Noel |last=Santos |website=Virtual Curiosities |date=8 Dec 2024 |url=https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |url-status=live |title=DANGER!!!: Chargeback = ACCOUNT PERMANENTLY BANNED |archive-url=http://web.archive.org/web/20260205120523/https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |archive-date=2026-02-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=justAnotherLedditor |date=16 Dec 2022 |url=https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |url-status=live |title=TIFU by accidentally buying two Google Pixels and ended up getting my 15 year old Google Account permanently banned. |website=[[Reddit]] |archive-url=http://web.archive.org/web/20260113140546/https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |archive-date=2026-01-13}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===AI integrations in Google Search===&lt;br /&gt;
On may 19th, 2026, Google announced modifications for [[Google Search]] to include more AI integrations involving inclusion of [[Google Gemini]] Flash 3.5 and integration of AI agents. These changes have sparked several controversies, including for example critizicing the reliability of searching using AI because of hallucinations, inabilities of AIs to detect malicious web sites and possibilities to use AI to control results obtained on searches. &amp;lt;ref&amp;gt;{{Cite web |last=Yildrim |first=Ece |date=19 May 2026 |title=Google Search Is Dead. Welcome to the Era of the ‘Intelligent Search Box’ |url=https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |url-status=live |archive-url=https://web.archive.org/web/20260519204100/https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |archive-date=2026-05-19 |access-date=21 May 2026 |website=Gizmodo}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Reid|first=Elizabeth |date=19 May 2026 |title=A new era for AI Search |url=https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |url-status=live |archive-url=https://web.archive.org/web/20260519181835/https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |archive-date=2026-05-19 |access-date=21 May 2026 |website=Google Blog}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Service shutdowns===&lt;br /&gt;
====Google Play Music shutdown (Dec 2020)====&lt;br /&gt;
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store &amp;amp; Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223929/https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20251214224205/https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |archive-date=14 Dec 2025}}&amp;lt;/ref&amp;gt; Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.&amp;lt;ref&amp;gt;{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek |archive-url=http://web.archive.org/web/20251004223929/https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.&amp;lt;ref&amp;gt;{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz |archive-url=http://web.archive.org/web/20250805235415/https://www.technobezz.com/buy-music-google-play |archive-date=5 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google |archive-url=http://web.archive.org/web/20250708163846/https://9to5google.com/2020/12/03/google-play-music-dead/ |archive-date=8 Jul 2025}}&amp;lt;/ref&amp;gt; This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |author=The YouTube Team |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog |archive-url=http://web.archive.org/web/20260201140126/https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the shut down, users lost access to the music they paid for, with no way to download them. Google justified this by transferring all playlists and purchase history to YouTube Music, and only refunding songs that were not directly available,&amp;lt;ref&amp;gt;{{Cite web |author=Garry |date=10 Oct 2023 |title=What happened to my songs on Google Music? |url=https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |url-status=live |access-date=5 Apr 2025 |website=Darwin&#039;s Data |archive-url=http://web.archive.org/web/20251004223930/https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Chaney |first=Sarah |date=5 Feb 2022 |title=What Happened to Google Play Music? |url=https://www.makeuseof.com/what-happened-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=MUO |archive-url=http://web.archive.org/web/20260205111318/https://www.makeuseof.com/what-happened-to-google-play-music/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; with no guarantee that the songs will remain available through the new service. Users found that their purchased songs were no longer able to stream at 320kbps on YouTube Music compared to Google Play Music unless they paid for the monthly subscription.&amp;lt;ref&amp;gt;{{Cite web |last=Cutlack |first=Gary |date=23 Dec 2012 |title=Google Music UK: everything you need to know |url=https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |url-status=live |access-date=5 Apr 2025 |website=TechRadar |archive-url=http://web.archive.org/web/20251221115733/https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |archive-date=21 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=L. Hald |first=Nicole |date=24 Mar 2025 |title=How Is YouTube Music Sound Quality in 2025? Is It Any Good? |url=https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |url-status=live |access-date=5 Apr 2025 |website=NoteBurner |archive-url=http://web.archive.org/web/20260217143252/https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |archive-date=17 Feb 2026}}&amp;lt;/ref&amp;gt; If a user failed to initiate the transfer of their music library or locally download their songs by 24th February 2021, then they lost all access and all data associated with Google Play Music.&amp;lt;ref&amp;gt;{{Cite web |last=Sodhi |first=Tanishka |date=8 Feb 2021 |title=Google Play Music Data Will Be Deleted on February 24: Here’s How to Transfer to YouTube Music |url=https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |url-status=live |access-date=5 Apr 2025 |website=Gadgets 360 |archive-url=http://web.archive.org/web/20260205112610/https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; YouTube Music does not provide the option to download songs as MP3s, with local downloads requiring an internet connection every 30 days to continue working offline.&amp;lt;ref&amp;gt;{{Cite web |title=Download music and podcasts to listen to offline |url=https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223930/https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Stadia shutdown (Jan 2023)====&lt;br /&gt;
In January 2023, Google announced the shutdown of its cloud gaming service, Stadia, which was launched in November 2019.&amp;lt;ref&amp;gt;{{Cite web |author=Verge Staff |title=RIP Google Stadia: the latest news on the discontinued cloud gaming service |url=https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |url-status=live |access-date=5 Apr 2025 |website=The Verge |archive-url=http://web.archive.org/web/20260101185119/https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |archive-date=1 Jan 2026}}&amp;lt;/ref&amp;gt; Stadia required users to purchase games individually, unlike other gaming platforms that offer subscription-based access. Upon the service&#039;s closure, Google promised to refund consumers for their purchases, including both games and hardware. The refunds for games and software were issued automatically.&amp;lt;ref&amp;gt;{{Cite web |last=Ravenscraft |first=Erin |date=10 Nov 2022 |title=Stadia Is Dying. Here’s What’s in Your Refund and How to Get It |url=https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |url-status=live |access-date=5 Apr 2025 |website=Wired |archive-url=http://web.archive.org/web/20260205115111/https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stadia users were effectively renting access to games, as the platform did not allow for traditional ownership or offline play. With the service discontinued, consumers were left without access to the content they had purchased. Stadia users who had bought controllers and other peripherals for the service were also impacted by the shutdown. While Google offered refunds to customers, many Stadia consumers were left with equipment that no longer performs the advertised functions and limited recourse for repurposing or reselling their devices.&amp;lt;ref&amp;gt;{{Cite web |last=Ashworth |first=Mack |date=5 Oct 2022 |title=Stadia Shut Down: How To Use Your Hardware Now Google’s Shutting It Down |url=https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |url-status=live |access-date=5 Apr 2025 |website=Game Revolution |archive-url=http://web.archive.org/web/20251004224131/https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.&amp;lt;ref&amp;gt;{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here&#039;s how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central |archive-url=http://web.archive.org/web/20251109164004/https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |archive-date=9 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Assistant third-party list support (Jun 2023)====&lt;br /&gt;
On June 20th, 2023, Google disabled third-party list support for Google Assistant.&amp;lt;ref&amp;gt;{{Cite web |access-date=2025-09-16 |title=Where are my old lists? |url=https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-url=https://web.archive.org/web/20250427212604/https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-date=2025-04-27}}&amp;lt;/ref&amp;gt; This feature allowed lists through third-party services, such as AnyList or Todoist, to be managed via Google Assistant. After this change, the only list provider available through Google Assistant, was Google&#039;s own list service, Google Keep.&amp;lt;ref&amp;gt;{{Cite web |last=Mathur |first=Chandraveer |website=Android Police |date=2023-05-31 |title=Google Assistant is killing support for notes and lists integration with third-party apps |url=https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-url=http://web.archive.org/web/20251218051543/https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-date=18 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Jamboard shutdown (Dec 2024)====&lt;br /&gt;
{{Main|Google Jamboard}}&lt;br /&gt;
In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.&lt;br /&gt;
&lt;br /&gt;
The Jamboard product was a $5,000 device that Google pitched as a collaborative tool through its Google Workspace service. After the service no longer existed, however, the device became a brick and the users as well as the buyers were left unsupported and uncompensated.&lt;br /&gt;
&lt;br /&gt;
Situations like this highlight the vulnerability of the consumer market since proprietary products are completely at the hands of developers who can cut services on a whim. Thus, consumer protection must be taken to another level to ensure that no matter what companies get rid of, support and compensatory avenues exist.&lt;br /&gt;
&lt;br /&gt;
====Manifest V2 shutdown (Jul 2025)====&lt;br /&gt;
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users as well as making Chromium (a browser that many other browsers use as their base) switch to Manifest V3, and disabled the ability to turn them back on.&amp;lt;ref&amp;gt;{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manifest V3 disabled the &amp;lt;code&amp;gt;webRequestBlocking&amp;lt;/code&amp;gt; permission in the &amp;lt;code&amp;gt;webRequest&amp;lt;/code&amp;gt; API,&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}&amp;lt;/ref&amp;gt; preventing many ad content blockers (such as uBlock Origin) from working.&amp;lt;ref&amp;gt;{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}&amp;lt;/ref&amp;gt; Google cites performance reasons,&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote=&amp;quot;In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with.&amp;quot;}}&amp;lt;/ref&amp;gt; but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.&lt;br /&gt;
&lt;br /&gt;
===Google Pixel===&lt;br /&gt;
====Pixel devices bricked due to confusing reasons====&lt;br /&gt;
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs, or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.&amp;lt;ref&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won&#039;t help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}&amp;lt;/ref&amp;gt; The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung&#039;s EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or [[wikipedia:Fastboot|Fastboot]], making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.&lt;br /&gt;
&lt;br /&gt;
This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special &amp;quot;USB boot&amp;quot; bit flag set to 1.&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, this recovery bootloader is inaccessible to the public, and is not possible to recreate it without Google&#039;s private keys. This makes it impossible to repair a device in this state, other than to do a technically challenging repair involving desoldering the UFS chip to repopulate its contents or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.&lt;br /&gt;
&lt;br /&gt;
Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue. Even with there being a sizable post on their bug tracker,&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20251004223929/https://issuetracker.google.com/issues/437705274 |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; and despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Pixel 4a battery reduction update (Jan 2025)====&lt;br /&gt;
{{Main|Pixel 4a Battery Performance Program}}&lt;br /&gt;
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on &amp;quot;Impacted Devices&amp;quot;. Not all units were affected. It&#039;s speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.&lt;br /&gt;
&lt;br /&gt;
As compensation, Google offered a free battery replacement only in select countries. In other countries, you could choose between a $50 USD payment or $100 USD worth of Google Store credits. However, some users reported difficulty obtaining their compensation.&lt;br /&gt;
&lt;br /&gt;
===User freedom incidents===&lt;br /&gt;
====Banning domain-blockers from Play Store (2013)====&lt;br /&gt;
Since 2013, Google has taken down all apps on G-Play that can block connections to arbitrary [[wikipedia:Domain_Name_System|domain-names]] via [https://developer.android.com/develop/connectivity/vpn the official VPN API], most of those apps being marketed as ad-blockers.&amp;lt;ref&amp;gt;{{ cite news |first=Liam |last=Tung |date=14 Mar 2013 |website=ZDNET |title=Google kicks ad-blocker apps off Play store |url=https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |url-status=live |archive-url=https://web.archive.org/web/20150625111914/https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |archive-date=2015-06-25}}&amp;lt;/ref&amp;gt; This forced apps such as AdGuard and NetGuard to distribute their ad-blocking features elsewhere.&amp;lt;ref&amp;gt;{{cite web |first=Ekaterina |last=Kachalova |title=Why is AdGuard not on Google Play? |date=17 Aug 2023 |website=AdGuard |url=https://adguard.com/en/blog/adguard-google-play-removal.html |url-status=live |archive-url=https://web.archive.org/web/20230822100645/https://adguard.com/en/blog/adguard-google-play-removal.html |archive-date=2023-08-22}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;netguard&amp;quot;&amp;gt;{{cite web |author=NetGuard |website=[[GitHub]] |title=NetGuard/ADBLOCKING.md |url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L6 |url-status=live |archive-url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md |archive-date=2026-03-29}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
*Line 6: &amp;quot;ad blocking is not possible with the Play store version because Google does not allow ad blocking apps in the Play store&amp;quot;.&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
*Line 106: &amp;quot;Please do not mention this feature in Google Play store comments, since Google does not allow ad blocking applications in the Google Play store&amp;quot;.&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google cites their own Developer Distribution Agreement (terms of service for devs), claiming that those apps are &amp;quot;disruptive&amp;quot;, as if to imply hacking or cracking. Many people claim that&#039;s an invalid excuse, and that the ulterior motive was to increase ad-revenue.&lt;br /&gt;
&lt;br /&gt;
====Phone number requirement for new accounts (2020)====&lt;br /&gt;
Since 2020, Google has increasingly forced users to verify phone-numbers via SMS during account registration,&amp;lt;ref&amp;gt;{{cite web |website=Google Support |url=https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |date=20 Mar 2020 |title=Cannot create a new Google account, it is requiring a phone number (Forced phone verification) |author=FB3 Network |url-status=live |archive-url=https://web.archive.org/web/20260509050746/https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |archive-date=2026-05-09}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=DarknessMoonlight |date=30 Jun 2021 |title=Does Google now require a phone number to make new Gmail accounts? |url=https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |url-status=live |website=[[Reddit]] |archive-url=https://web.archive.org/web/20260427144651/https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |archive-date=2026-04-27}}&amp;lt;/ref&amp;gt; in an effort to &amp;quot;mitigate spam, bot activity, and account abuse&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |author=CLRN |date=2025-07-25 |title=How to skip phone verification while creating Gmail account? |url=https://www.clrn.org/how-to-skip-phone-verification-while-creating-gmail-account/ |url-status=live |access-date=2026-05-05 |website=California Learning Resource Network}}&amp;lt;/ref&amp;gt; They have a system that immediately detects reuse of numbers, so no accounts can have the same associated number.{{Citation needed}} This, paired with [[YouTube#Forced sign-in|YouTube&#039;s sign-in requirement]], makes it impossible for users to share a single &amp;quot;guest&amp;quot; account, as is typically the case for families sharing a smart TV.&lt;br /&gt;
&lt;br /&gt;
====Blocking sideloading of unverified Android apps (Aug 2025)====&lt;br /&gt;
{{Main|Google blocking sideloading of unverified Android apps}}&lt;br /&gt;
On 25 August 2025, &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog |archive-url=http://web.archive.org/web/20260128013331/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20260119211509/https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt; This marks a significant change to Android&#039;s long-standing support for sideloading apps.&lt;br /&gt;
&lt;br /&gt;
Devices without [[Google Mobile Services]] or running [[wikipedia:List_of_custom_Android_distributions|custom ROMs]] are exempt.&amp;lt;ref name=&amp;quot;:22&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}&amp;lt;/ref&amp;gt; Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |author=JohnC_21 |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=https://web.archive.org/web/20250825210732/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=2025-08-25}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Lawsuit==&lt;br /&gt;
===Privacy violations===&lt;br /&gt;
====&#039;&#039;Rodriguez v. Google LLC&#039;&#039; (&#039;&#039;May 2021—September 2025&#039;&#039;)====&lt;br /&gt;
Google&#039;s &amp;quot;Web &amp;amp; App Activity&amp;quot; (WAA) setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.&amp;lt;ref&amp;gt;{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251011171640/https://googlewebappactivitylawsuit.com/Home/FAQ |archive-date=11 Oct 2025}}&amp;lt;/ref&amp;gt; Google collected mobile device data for eight years from users who opted out of tracking under the WAA.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |last=Staab |first=Theresa |date=18 Sep 2025 |title=Someone is Always Watching: Implications of Google&#039;s WAA Privacy Case |url=https://lawreview.syr.edu/someone-is-always-watching-implications-of-googles-waa-privacy-case/ |access-date=26 Mar 2026 |website=Syracuse Law Review}}&amp;lt;/ref&amp;gt; The dates of use/activity in question were between July 1, 2016 and September 23, 2024.&amp;lt;ref&amp;gt;{{Cite web |date=23 Oct 2024 |title=FAQs: Google Web App Activity lawsuit |url=https://help.wfu.edu/support/solutions/articles/13000825158-faqs-google-web-app-activity-lawsuit |url-status=live |access-date=26 Mar 2026 |website=Wake Forest University}}&amp;lt;/ref&amp;gt; On September 3, 2025, the San Francisco Federal Court jury held Google liable two of three claims of privacy invasion. The plaintiffs were awarded $425.7 million in compensatory damages for invasion of privacy, totaling around $4 per person for the approximate 98 million affected users, but since the jury found that Google did not act with malicious intent, no punitive damages were awarded.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite news |last=Mollman |first=Brittney |last2=Sosnicki |first2=Luke |date=2025-09-05 |title=Federal Jury Awards $425.7 Million in Google Privacy Case: Key Takeaways on Consent Design and Litigation Risk |url=https://www.thompsoncoburn.com/insights/federal-jury-awards-425-7-million-in-google-privacy-case-key-takeaways-on-consent-design-and-litigation-risk/ |url-status=live |access-date=2026-05-05 |work=Thompson Coburn LLP}}&amp;lt;/ref&amp;gt; Google filed an appeal to this verdict &amp;quot;on the basis that the jury misunderstood the functionality of its privacy tools and that users were adequately informed through layered disclosures and consent flows&amp;quot;.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt; Claim submission may begin once the appeals process finishes.&amp;lt;ref&amp;gt;{{Cite web |date=2025-11-05 |title=$425M Verdict in Google Web &amp;amp; App Activity Privacy Class Action Lawsuit — Do You Qualify? |url=https://openclassactions.com/settlements/google-web-and-app-activity-privacy-class-action-lawsuit.php |url-status=live |access-date=2026-05-05 |website=OpenClassActions}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;Thele v. Google LLC&#039;&#039; (&#039;&#039;November 2025—&#039;&#039;)====&lt;br /&gt;
On the 11th of November, 2025, Thomas Thele filed a demand for jury trial in a class action complaint against Google LLC. In the filing it states that &amp;quot;on or about October 10, 2025, Google secretly turned on Gemini for all its users’ Gmail, Chat, and Meet accounts, enabling AI to track its users’ private communications contained in those platforms without the users’ knowledge or consent&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |last=Wolfson |first=Tina |last2=Ahdoot |first2=Robert |last3=Maya |first3=Theodore |last4=Brown |first4=Alyssa |date=2025-11-11 |title=UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA - CLASS ACTION COMPLAINT DEMAND FOR JURY TRIAL |url=https://www.classaction.org/media/thele-v-google-complaint_2.pdf |url-status=live |access-date=2026-05-05 |website=ClassAction}}&amp;lt;/ref&amp;gt; The suit &amp;quot;alleges that Google is violating the California Invasion of Privacy Act&amp;quot;,&amp;lt;ref&amp;gt;{{Cite web |last=Burnson |first=Robert |date=2025-11-12 |title=Google sued for allegedly using Gemini AI to secretly track user data |url=https://www.business-standard.com/technology/tech-news/google-sued-for-allegedly-using-gemini-ai-to-secretly-track-user-data-125111200603_1.html |url-status=live |access-date=2026-05-05 |website=Business Standard}}&amp;lt;/ref&amp;gt; a law enacted in 1967 which dictates the terms by which advances in technology can be used for the purpose of invading the privacy of citizens.&amp;lt;ref&amp;gt;{{Cite web |date=1967 |title=CHAPTER 1.5. Invasion of Privacy |url=https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=PEN&amp;amp;part=1.&amp;amp;title=15.&amp;amp;chapter=1.5 |url-status=live |access-date=2026-05-05 |website=California Legislative Information}}&amp;lt;/ref&amp;gt; The defendant, Google LLC, filed a Motion to Dismiss which is scheduled to be heard on May 1, 2026.&amp;lt;ref&amp;gt;{{Cite web |date=2026-04-27 |title=Thele v. Google LLC |url=https://www.pacermonitor.com/public/case/61129560/Thele_v_Google_LLC |url-status=live |access-date=2026-05-05 |website=PacerMonitor}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anti-competitive behavior===&lt;br /&gt;
====&#039;&#039;Epic Games, Inc. v. Google Inc.&#039;&#039; (&#039;&#039;August 2020—May 2025&#039;&#039;)====&lt;br /&gt;
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].&amp;lt;ref&amp;gt;{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam&#039;s 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com |archive-url=http://web.archive.org/web/20251211034837/https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |archive-date=11 Dec 2025}}&amp;lt;/ref&amp;gt; On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of &#039;&#039;Fortnite&#039;&#039; to redirect users to Epic Games&#039; storefront to purchase in-game currency (&amp;quot;V-Bucks&amp;quot;) alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google&#039;s storefronts, and &#039;&#039;Fortnite&#039;&#039; was removed from both app stores the same day.&lt;br /&gt;
&lt;br /&gt;
Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behavior. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.&amp;lt;ref&amp;gt;{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111151936/https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |archive-date=11 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Social media addiction bellwether trials===&lt;br /&gt;
====Los Angeles Superior Court, JCCP 5255 (&#039;&#039;2026&#039;&#039;)====&lt;br /&gt;
Starting in January of 2026, [[Meta]] (Facebook and [[Instagram]]) and [[Google]] ([[YouTube]]) faced legal claims of their platforms being intentionally addictive and harmful to children. [[ByteDance]] ([[TikTok]]) and Snap ([[Snapchat]]) were named initially, but settled for undisclosed terms before the trial began. A 19-year-old girl, referred to by the initials &amp;quot;KGM&amp;quot; or Kaley, and two other plaintiffs were selected for bellwether trials—test cases tried as part of an MDL.&amp;lt;ref&amp;gt;{{Cite web |last=Huamani |first=Kaitlyn |last2=Ortutay |first2=Barbara |date=9 Feb 2026 |title=Landmark trial accusing tech giants of harming children with addictive social media begins |url=https://www.pbs.org/newshour/nation/landmark-trial-accusing-tech-giants-of-harming-children-with-addictive-social-media-begins |url-status=live |access-date=25 Mar 2026 |website=PBS News}}&amp;lt;/ref&amp;gt;  On March 25, 2026, the California jury concluded in KGM&#039;s case that [[Meta]] and Google were guilty of negligent for their apps—[[Instagram]], Facebook, and [[YouTube]]—being deliberately built to be addictive, which the companies&#039; executives knew this and failed to protect their youngest users.&amp;lt;ref&amp;gt;{{Cite web |last=Allyn |first=Bobby |date=25 Mar 2026 |title=Jury finds Meta and Google negligent in social media harms trial |url=https://www.npr.org/2026/03/25/nx-s1-5746125/meta-youtube-social-media-trial-verdict |url-status=live |access-date=26 Mar 2026 |website=npr}}&amp;lt;/ref&amp;gt; [[Meta]] was charged to pay $4.2 million for compensatory and punitive damages, and charged Google $1.8 million.&amp;lt;ref&amp;gt;{{Cite web |last=Kang |first=Cecilia |last2=Mac |first2=Ryan |last3=Tan |first3=Eli |date=25 Mar 2026 |title=Meta and YouTube Found Negligent in Landmark Social Media Addiction Case |url=https://www.nytimes.com/2026/03/25/technology/social-media-trial-verdict.html |url-status=live |access-date=26 Mar 2026 |website=The New York Times}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*{{Main|List of Google products}}&lt;br /&gt;
&lt;br /&gt;
*[[Advertising overload]]&lt;br /&gt;
*[[Google asserts the right to seize phones during repairs]]&lt;br /&gt;
*[[Google Nest Protect forced to use Google app]]&lt;br /&gt;
*[[Google Nest thermostat smart features disabled]]&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]]&lt;br /&gt;
&lt;br /&gt;
==External links==&lt;br /&gt;
&lt;br /&gt;
*&amp;quot;[https://www.jwz.org/xscreensaver/google.html XScreenSaver: Google Store Privacy Policy]&amp;quot;. Google pretending to care about privacy by forcing a fully-local (no internet) minimal-permission screen-saver app to specify a privacy-policy. That blog-post contains many sources on Google&#039;s anti-consumer practices&lt;br /&gt;
*[https://theywillbanyou.com/| They Will Ban You - Cases of user accounts banned for unfair reasons]&lt;br /&gt;
*[https://killedbygoogle.com/ Killed by Google - Dead products list]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Google| ]]&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google&amp;diff=56180</id>
		<title>Google</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google&amp;diff=56180"/>
		<updated>2026-06-05T00:41:17Z</updated>

		<summary type="html">&lt;p&gt;Iii: edits for wiki style policy (references after punctuation), and grammatical/readability edits&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup|Issue 1=Article formatting should follow [[Template:CompanyPreload]]. With Google&#039;s history, it may be useful to use tabling for incidents.|Issue 2=Citations need to follow proper formatting. See [[Template:Cite web]].|Issue 3=Citations should be placed after punctuation.|Issue 4=Make sure that section headers are in sentence case where applicable.}}&lt;br /&gt;
{{CompanyCargo&lt;br /&gt;
|Founded=1998&lt;br /&gt;
|Industry=Technology&lt;br /&gt;
|Logo=Google.webp&lt;br /&gt;
|ParentCompany=Alphabet Inc.&lt;br /&gt;
|Type=Subsidiary&lt;br /&gt;
|Description=Google is one of the most influential technology companies in the world, originally known for developing the most widely used search engine.&lt;br /&gt;
|Website=https://www.google.com/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;{{Wplink|Google|Google LLC}}&#039;&#039;&#039;, founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.&amp;lt;ref&amp;gt;{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com |archive-url=http://web.archive.org/web/20260222070659/https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |archive-date=22 Feb 2026}}&amp;lt;/ref&amp;gt; Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.&amp;lt;ref&amp;gt;{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025 |archive-url=http://web.archive.org/web/20260128182647/https://about.google/products/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Google Search| Google&#039;s search engine]] remains its most well-known service, but the company has significantly diversified its offerings. Key products include the [[Android]] operating system, the [[Google Chrome]] web browser, [[Google Drive]] for cloud storage, [https://wikipedia.org/wiki/Google_Maps Google Maps], [[YouTube]], and [[wikipedia:Google_Play|Google Play]].&amp;lt;ref&amp;gt;{{Cite web |title=Helpful products, built with you in mind |url=https://about.google/intl/ALL_us/products/ |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20260205114442/https://about.google/intl/ALL_us/products/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;{{Citation needed}} Additionally, the company provides digital advertising services through Google Ads, generating the majority of its revenue.&amp;lt;ref&amp;gt;{{Cite web |date=4 Feb 2025 |title=Alphabet Announces Fourth Quarter and Fiscal Year 2024 Results |url=https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251002181452/https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |archive-date=2 Oct 2025}}&amp;lt;/ref&amp;gt; In recent years, Google has also developed hardware products such as the Pixel smartphone and Nest smart home devices.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
Google has faced ongoing scrutiny related to data privacy, competition, and its dominant position in the market, such concerns have stretched as far back as 2012.&amp;lt;ref&amp;gt;{{Cite web |last=Cohen |first=Adam |date=5 Mar 2012 |title=Will We Ever Get Strong Internet Privacy Rules? |url=https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |url-status=live |access-date=5 Apr 2025 |website=Time |archive-url=http://web.archive.org/web/20260205121437/https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=6 Sep 2023 |title=REPORT: Google at 25: From “Don’t Be Evil” To ¯\_(ツ)_/¯ |url=https://techoversight.org/2023/09/06/google-at-25/ |url-status=live |access-date=5 Apr 2025 |website=The Tech Oversight Project |archive-url=http://web.archive.org/web/20251004223929/https://techoversight.org/2023/09/06/google-at-25/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; The company has been the subject of various legal and regulatory challenges, particularly concerning antitrust issues, the use of personal data, and its impact on consumer choice.{{Citation needed}} The US government is currently engaged in an antitrust lawsuit against Google, with a decision expected early 2025.&amp;lt;ref&amp;gt;{{Cite web |date=25 Nov 2024 |title=Closing Arguments, November 25: Once, Twice, Three Times a Monopolist |url=https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |url-status=live |access-date=5 Apr 2025 |website=US v Google |archive-url=http://web.archive.org/web/20250906103632/https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |archive-date=6 Sep 2025}}&amp;lt;/ref&amp;gt; {{UpdateNeeded|date={{subst:August}} {{subst:2025}}|reason=We need updates on this situation.}}&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
In December 2024, Google announced to organisations that use its advertising products, that from 16 February 2025, it will no longer prohibit them from employing [[wikipedia:Fingerprint_(computing)|fingerprinting]] techniques.&amp;lt;ref&amp;gt;{{Cite web |last=Almond |first=Stephen |date=19 Dec 2024 |title=Our response to Google’s policy change on fingerprinting |url=https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |url-status=live |access-date=5 Apr 2025 |website=ico. |archive-url=http://web.archive.org/web/20260128163957/https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===User freedom===&lt;br /&gt;
Google has a long history of patronizing their user base by taking away options or not giving users a choice in the first place.&lt;br /&gt;
&lt;br /&gt;
For example, in 2014, Google removed normal MicroSD write access on Android 4.4,&amp;lt;ref&amp;gt;{{cite news |first=Cody |last=Toombs |url=https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |title=External Blues: Google Has Brought Big Changes To SD Cards In KitKat, And Even Samsung Is Implementing Them |url-status=live |date=17 Feb 2014 |url-status=live |website=Android Police |archive-url=https://web.archive.org/web/20140218064033/https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |archive-date=2014-02-18}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |date=23 Feb 2014 |title=Re: What about removable SD card in 4.4 |website=Google Groups |archive-url=https://web.archive.org/web/20260209114224/https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |archive-date=2026-02-09 }}&amp;lt;/ref&amp;gt; limiting each application to their own dedicated folder, arguing that this makes it easy to remove all files left by the app during uninstallation, given that no app can leave files outside their own dedicated folder.&lt;br /&gt;
&lt;br /&gt;
No menu option to change this behaviour was given to the user, therefore users who wanted to restore normal write access were forced to resort to unofficial methods involving bootloader unlocking and rooting.&lt;br /&gt;
&lt;br /&gt;
It should be noted that Google&#039;s own Android smartphones and tablet computers (Nexus and Pixel devices) never featured a memory card slot. Similar restrictions were later added to USB on-the-go storage.&amp;lt;ref name=android-traditional-storage&amp;gt;{{cite web |title=Traditional storage &amp;amp;#124; Android Open Source Project |url=https://source.android.com/docs/core/storage/traditional |url-status=live |website=Android}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2018, Google added a clipboard manager to their keyboard app, Gboard.&amp;lt;ref&amp;gt;{{cite web |url=https://www.xda-developers.com/gboard-clipboard-manager/ |title=Gboard 7.7 adds a Clipboard Manager feature to Google&#039;s keyboard app |date=22 Oct 2018 |first=Mishaal |last=Rahman |url-status=live |website=XDA Developers |archive-url=https://web.archive.org/web/20190119233536/https://www.xda-developers.com/gboard-clipboard-manager/ |archive-date=2019-01-19}}&amp;lt;/ref&amp;gt; But in 2022, Google decided on behalf of their users that they don&#039;t need to retain clipboard items for any longer than one hour. Therefore, they added a one-hour time limit, meaning any clipboard item older than one hour is automatically deleted, with no option to change this behaviour. The only way to retain clipboard items for more than one hour is to manually mark them as &amp;quot;pinned&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |first=Ethan |last=Gillian |title=Remember: Android 13 clears clipboard 1 hour after copying |url=https://techzle.com/remember-android-13-clears-clipboard-1-hour-after-copying |url-status=live |website=Techzle |date=17 Aug 2022}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2019, Google took away the ability to turn off the &amp;quot;pull-to-refresh&amp;quot; gesture on the mobile edition of their Chrome web browser, following by refusing to reinstate the option after an abnormally high number of complaints that the gesture causes accidental refreshes. See [[Google_Chrome#Mandatory_pull-to-refresh|Google Chrome § Mandatory pull-to-refresh]].&lt;br /&gt;
&lt;br /&gt;
Google lets app developers arbitrarily [[screenshot blocking|prevent device owners from capturing screenshots and screen recordings]] on Android. While the original intention was to prevent sensitive information in banking apps from getting outside, it has been severely overused by app developers and prevents legitimate uses such as asking for help in forums and bug reports. Google provided no option for device owners to override it, so the only way is to unlock the bootloader and modify the operating system.&amp;lt;ref&amp;gt;{{cite web |url=https://www.howtogeek.com/why-screenshots-dont-always-work-especially-in-secure-apps/ |website=How To Geek |author=Faisal Rasool |title=Why Your Phone Blocks Screenshots in Secure Apps |date=2025-08-23 |access-date=2026-05-26 }}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=konradkar |url=https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |website=[[Reddit]] |title=Booking.com app disallow to take screenshot, can I bypass this? |date=2020-02-14 |access-date=2026-05-26 |archive-url=https://web.archive.org/web/20230615071612/https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |archive-date=2023-06-15}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{excerpt|Android Developer Verification}}&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
===Account lockouts===&lt;br /&gt;
Google has been reported to have randomly locked people out of their accounts due to ostensible security reasons, which are not lifted even if the user had provided the correct credentials and/or even if the user have correctly followed all the verification prompts such as SMS verification. These have caused anguishes for many affected users who are unable to access their contents, emails and services as a result. Furthermore, some had reported that they are forced to undergo SMS verification even when recovery email addresses are already configured to their accounts, thereby likely constituting instances of [[Forced identification|forced verification]] in broad senses.&amp;lt;ref&amp;gt;{{cite web |url=https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |date=5 May 2021 |author=Feniks_Gaming |title=Mike Rose (No More Robots Publisher) Locked out of Gmail, speaks to google support to find out their own staff are locked out of their personal Gmail too... |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210505101632/https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |archive-date=2021-05-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |first=Mike |last=Rose |url-status=dead |date=4 May 2021 |title=This morning, I was locked out of my Google account |website=Nitter |archive-url=https://web.archive.org/web/20220908195211/https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |archive-date=2022-09-08}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |title=FYI: Google can lock you out of your account for no reason |author=danielrosehill |date=5 Aug 2021 |url=https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210805030048/https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |archive-date=2021-08-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=LegitimateAttempt4 |date=20 Jul 2023 |title=DAE noticed that Google had taken security account lockouts to a zealotic level? |url-status=live |url=https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |website=[[Reddit]] |archive-url=http://web.archive.org/web/20230720181226/https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |archive-date=2023-07-20}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Deletion of inactive accounts===&lt;br /&gt;
In May 2023, Google announced that [[Inactive account deletion|deletion of inactive user accounts]] would occur starting in December 2023, citing security reasons, noting that old and unused accounts are more likely to be compromised. Google claimed that &amp;quot;Forgotten or unattended accounts often rely on old or re-used passwords that may have been compromised, have not had two factor authentication set up, and receive fewer security checks by the user,&amp;quot; while saying that Google &amp;quot;has no plans to delete [[YouTube]] videos&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |last1=Lawler |first1=Richard |title=Google might delete your Gmail account if you haven&#039;t logged in for two years |url=https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |website=The Verge |access-date=21 December 2023 |language=en |date=16 May 2023 |archive-url=http://web.archive.org/web/20260205121216/https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Porter |first1=Jon |title=Reminder: Google is about to start purging inactive accounts |url=https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |website=The Verge |access-date=21 December 2023 |language=en |date=28 November 2023 |archive-url=http://web.archive.org/web/20251212230239/https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Amadeo |first1=Ron |title=Google&#039;s new &amp;quot;inactive account&amp;quot; policy won&#039;t delete years of YouTube videos |url=https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |website=Ars Technica |access-date=21 December 2023 |language=en-us |date=17 May 2023 |archive-url=http://web.archive.org/web/20251212092014/https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt; The decision to delete inactive accounts has sparked some criticism and backlash. The cited security rationale behind such decision was ridiculed and was compared to a hypothetical scenario where a bank should be burned down if it is not secure against robbers.&amp;lt;ref&amp;gt;{{cite web |last1=Novet |first1=Jordan |title=Google&#039;s plan to purge inactive accounts isn&#039;t sitting well with some users |url=https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |website=CNBC |access-date=21 December 2023 |language=en |date&lt;br /&gt;
=19 August 2023 |archive-url=http://web.archive.org/web/20250831223936/https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |archive-date=31 Aug 2025}}&amp;lt;/ref&amp;gt; Such policies could adversely affect those who had good reasons to become inactive for a long time, such as hospitalization, prison incarceration, and being in totalitarian countries which have prolonged internet shutdowns. Moreover, the Anonymous hacktivist collective has protested against the decision to delete inactive accounts multiple times, describing them as &amp;quot;harsh&amp;quot; and saying that the decision will &amp;quot;destroy history&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |date=18 Jul 2023 |title=Anonymous puts Taiwan flag, national anthem on 2 UN websites |url=https://www.taiwannews.com.tw/en/news/4946597 |first=Keoni |last=Everington |url-status=live |access-date=21 Dec 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20231014070719/https://www.taiwannews.com.tw/en/news/4946597 |archive-date=2023-10-14}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=18 Oct 2023 |title=&#039;Anonymous&#039; hacks Chinese government site to protest Israel–Hamas war |url-status=live |url=https://www.taiwannews.com.tw/en/news/5022840 |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240221120716/https://www.taiwannews.com.tw/en/news/5022840 |archive-date=2024-02-21}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=8 Dec 2023 |title=Anonymous posts Taiwan flag on UN site |website=Taiwan News |url=https://www.taiwannews.com.tw/en/news/5055454 |url-status=live |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240228035811/https://www.taiwannews.com.tw/en/news/5055454 |archive-date=2024-02-28}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anticompetitive practices===&lt;br /&gt;
Google has a great history of anticompetitive practices. For example, in 2020 the company was sued for practices involving pushing off relevant search results in order to favor advertisements and the inclusion of [[bloatware]] on Android devices.&amp;lt;ref&amp;gt;{{Cite web |publisher=Eaton Business School|date=31 Aug 2021 |title=Google - A display of anti-competitive behaviour|url=https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |url-status=live |archive-url=https://web.archive.org/web/20250523013602/https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |archive-date=2025-05-23 |access-date=25 May 2026 |website=Eaton Business School}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The [[Android Developer Verification]] program prevents sideloading and external app stores, such as [[F-Droid]] to be an available alternative to the Google Play Store.&lt;br /&gt;
&lt;br /&gt;
===Google device repair program restrictions===&lt;br /&gt;
{{Main|Google asserts the right to seize your phone during a repair}}&lt;br /&gt;
Google&#039;s Service &amp;amp; Repair Program terms explicitly state that any device containing non-Google-authorized parts &amp;quot;will not be returned&amp;quot; to the customer.&lt;br /&gt;
&lt;br /&gt;
===Target API level requirements for Google Play apps===&lt;br /&gt;
Google&#039;s policy of requiring apps for Android to target recent API levels, in order to appear in the Play Store,&amp;lt;ref&amp;gt;{{Cite web |date=31 Aug 2024 |title=Policy Center |url=https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |access-date=May 9, 2025 |website=Play Console Help |archive-url=http://web.archive.org/web/20260215054419/https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; creates a continuous cycle of maintenance and redevelopment that can be especially burdensome for smaller developers, indie creators, and consumers.&lt;br /&gt;
&lt;br /&gt;
The requirement for apps to target newer APIs each year serves some legitimate security and feature purposes. However, it also effectively functions as a form of forced obsolescence. Even perfectly functional apps that don&#039;t need technical updates must be regularly reworked just to remain visible on the Play Store.&lt;br /&gt;
&lt;br /&gt;
This creates several issues:&lt;br /&gt;
&lt;br /&gt;
*Development resources must be allocated to updating apps rather than creating new features&lt;br /&gt;
*Smaller teams and individual developers are placed at a disadvantage attempting to keep up with the constant update cycle&lt;br /&gt;
*Legacy apps that are no longer actively maintained disappear, even if they&#039;re still useful&lt;br /&gt;
*The cost of maintaining apps increases, potentially making some projects financially nonviable&lt;br /&gt;
*Losing access to previously purchased apps when upgrading devices&lt;br /&gt;
*Users being unable to reinstall older apps that worked perfectly well for their needs&lt;br /&gt;
*Facing unexpected costs to replace functionality they&#039;ve already paid for&lt;br /&gt;
*Dealing with the frustration of discovering favorite apps have disappeared&lt;br /&gt;
&lt;br /&gt;
While Google argues this approach improves the Android ecosystem&#039;s security and functionality, it does place a significant burden on developers and can lead to the premature &amp;quot;death&amp;quot; of otherwise functional applications.&lt;br /&gt;
&lt;br /&gt;
This creates a troubling disconnect in digital ownership. Consumers reasonably expect that when they purchase an app, they should maintain access to it across their devices over time. Instead, they discover their digital purchases can effectively vanish due to policy decisions beyond their control.&lt;br /&gt;
&lt;br /&gt;
===Ban on third-party tech support ads===&lt;br /&gt;
Google prohibits tech support ads on their platform if they are not authorized by the manufacturer.&amp;lt;ref&amp;gt;{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google |archive-url=http://web.archive.org/web/20251112170608/https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |archive-date=12 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===The chargeback incident===&lt;br /&gt;
In November 2022, a Google customer accidentally purchased two Google Pixel smartphones instead of one, directly from Google (no third-party reseller), and tried to return one package to Google for a refund, but the shipping was unsuccessful.&lt;br /&gt;
&lt;br /&gt;
A Google customer support person suggested the customer to perform a chargeback. The customer acted accordingly without understanding the implications, resulting in the termination of their Google account shortly after. The account was 15 years old at that time.&amp;lt;ref&amp;gt;{{cite web |first=Noel |last=Santos |website=Virtual Curiosities |date=8 Dec 2024 |url=https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |url-status=live |title=DANGER!!!: Chargeback = ACCOUNT PERMANENTLY BANNED |archive-url=http://web.archive.org/web/20260205120523/https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |archive-date=2026-02-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=justAnotherLedditor |date=16 Dec 2022 |url=https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |url-status=live |title=TIFU by accidentally buying two Google Pixels and ended up getting my 15 year old Google Account permanently banned. |website=[[Reddit]] |archive-url=http://web.archive.org/web/20260113140546/https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |archive-date=2026-01-13}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===AI integrations in Google Search===&lt;br /&gt;
On may 19th, 2026, Google announced modifications for [[Google Search]] to include more AI integrations involving inclusion of [[Google Gemini]] Flash 3.5 and integration of AI agents. These changes have sparked several controversies, including for example critizicing the reliability of searching using AI because of hallucinations, inabilities of AIs to detect malicious web sites and possibilities to use AI to control results obtained on searches. &amp;lt;ref&amp;gt;{{Cite web |last=Yildrim |first=Ece |date=19 May 2026 |title=Google Search Is Dead. Welcome to the Era of the ‘Intelligent Search Box’ |url=https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |url-status=live |archive-url=https://web.archive.org/web/20260519204100/https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |archive-date=2026-05-19 |access-date=21 May 2026 |website=Gizmodo}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Reid|first=Elizabeth |date=19 May 2026 |title=A new era for AI Search |url=https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |url-status=live |archive-url=https://web.archive.org/web/20260519181835/https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |archive-date=2026-05-19 |access-date=21 May 2026 |website=Google Blog}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===Service shutdowns===&lt;br /&gt;
&lt;br /&gt;
====Google Play Music shutdown (Dec 2020)====&lt;br /&gt;
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store &amp;amp; Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223929/https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20251214224205/https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |archive-date=14 Dec 2025}}&amp;lt;/ref&amp;gt; Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.&amp;lt;ref&amp;gt;{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek |archive-url=http://web.archive.org/web/20251004223929/https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.&amp;lt;ref&amp;gt;{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz |archive-url=http://web.archive.org/web/20250805235415/https://www.technobezz.com/buy-music-google-play |archive-date=5 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google |archive-url=http://web.archive.org/web/20250708163846/https://9to5google.com/2020/12/03/google-play-music-dead/ |archive-date=8 Jul 2025}}&amp;lt;/ref&amp;gt; This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |author=The YouTube Team |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog |archive-url=http://web.archive.org/web/20260201140126/https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the shut down, users lost access to the music they paid for, with no way to download them. Google justified this by transferring all playlists and purchase history to YouTube Music, and only refunding songs that were not directly available,&amp;lt;ref&amp;gt;{{Cite web |author=Garry |date=10 Oct 2023 |title=What happened to my songs on Google Music? |url=https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |url-status=live |access-date=5 Apr 2025 |website=Darwin&#039;s Data |archive-url=http://web.archive.org/web/20251004223930/https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Chaney |first=Sarah |date=5 Feb 2022 |title=What Happened to Google Play Music? |url=https://www.makeuseof.com/what-happened-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=MUO |archive-url=http://web.archive.org/web/20260205111318/https://www.makeuseof.com/what-happened-to-google-play-music/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; with no guarantee that the songs will remain available through the new service. Users found that their purchased songs were no longer able to stream at 320kbps on YouTube Music compared to Google Play Music unless they paid for the monthly subscription.&amp;lt;ref&amp;gt;{{Cite web |last=Cutlack |first=Gary |date=23 Dec 2012 |title=Google Music UK: everything you need to know |url=https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |url-status=live |access-date=5 Apr 2025 |website=TechRadar |archive-url=http://web.archive.org/web/20251221115733/https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |archive-date=21 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=L. Hald |first=Nicole |date=24 Mar 2025 |title=How Is YouTube Music Sound Quality in 2025? Is It Any Good? |url=https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |url-status=live |access-date=5 Apr 2025 |website=NoteBurner |archive-url=http://web.archive.org/web/20260217143252/https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |archive-date=17 Feb 2026}}&amp;lt;/ref&amp;gt; If a user failed to initiate the transfer of their music library or locally download their songs by 24th February 2021, then they lost all access and all data associated with Google Play Music.&amp;lt;ref&amp;gt;{{Cite web |last=Sodhi |first=Tanishka |date=8 Feb 2021 |title=Google Play Music Data Will Be Deleted on February 24: Here’s How to Transfer to YouTube Music |url=https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |url-status=live |access-date=5 Apr 2025 |website=Gadgets 360 |archive-url=http://web.archive.org/web/20260205112610/https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; YouTube Music does not provide the option to download songs as MP3s, with local downloads requiring an internet connection every 30 days to continue working offline.&amp;lt;ref&amp;gt;{{Cite web |title=Download music and podcasts to listen to offline |url=https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223930/https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Stadia shutdown (Jan 2023)====&lt;br /&gt;
In January 2023, Google announced the shutdown of its cloud gaming service, Stadia, which was launched in November 2019.&amp;lt;ref&amp;gt;{{Cite web |author=Verge Staff |title=RIP Google Stadia: the latest news on the discontinued cloud gaming service |url=https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |url-status=live |access-date=5 Apr 2025 |website=The Verge |archive-url=http://web.archive.org/web/20260101185119/https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |archive-date=1 Jan 2026}}&amp;lt;/ref&amp;gt; Stadia required users to purchase games individually, unlike other gaming platforms that offer subscription-based access. Upon the service&#039;s closure, Google promised to refund consumers for their purchases, including both games and hardware. The refunds for games and software were issued automatically.&amp;lt;ref&amp;gt;{{Cite web |last=Ravenscraft |first=Erin |date=10 Nov 2022 |title=Stadia Is Dying. Here’s What’s in Your Refund and How to Get It |url=https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |url-status=live |access-date=5 Apr 2025 |website=Wired |archive-url=http://web.archive.org/web/20260205115111/https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stadia users were effectively renting access to games, as the platform did not allow for traditional ownership or offline play. With the service discontinued, consumers were left without access to the content they had purchased. Stadia users who had bought controllers and other peripherals for the service were also impacted by the shutdown. While Google offered refunds to customers, many Stadia consumers were left with equipment that no longer performs the advertised functions and limited recourse for repurposing or reselling their devices.&amp;lt;ref&amp;gt;{{Cite web |last=Ashworth |first=Mack |date=5 Oct 2022 |title=Stadia Shut Down: How To Use Your Hardware Now Google’s Shutting It Down |url=https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |url-status=live |access-date=5 Apr 2025 |website=Game Revolution |archive-url=http://web.archive.org/web/20251004224131/https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.&amp;lt;ref&amp;gt;{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here&#039;s how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central |archive-url=http://web.archive.org/web/20251109164004/https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |archive-date=9 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Assistant third-party list support (Jun 2023)====&lt;br /&gt;
On June 20th, 2023, Google disabled third-party list support for Google Assistant.&amp;lt;ref&amp;gt;{{Cite web |access-date=2025-09-16 |title=Where are my old lists? |url=https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-url=https://web.archive.org/web/20250427212604/https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-date=2025-04-27}}&amp;lt;/ref&amp;gt; This feature allowed lists through third-party services, such as AnyList or Todoist, to be managed via Google Assistant. After this change, the only list provider available through Google Assistant, was Google&#039;s own list service, Google Keep.&amp;lt;ref&amp;gt;{{Cite web |last=Mathur |first=Chandraveer |website=Android Police |date=2023-05-31 |title=Google Assistant is killing support for notes and lists integration with third-party apps |url=https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-url=http://web.archive.org/web/20251218051543/https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-date=18 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Jamboard shutdown (Dec 2024)====&lt;br /&gt;
{{Main|Google Jamboard}}&lt;br /&gt;
In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.&lt;br /&gt;
&lt;br /&gt;
The Jamboard product was a $5,000 device that Google pitched as a collaborative tool through its Google Workspace service. After the service no longer existed, however, the device became a brick and the users as well as the buyers were left unsupported and uncompensated.&lt;br /&gt;
&lt;br /&gt;
Situations like this highlight the vulnerability of the consumer market since proprietary products are completely at the hands of developers who can cut services on a whim. Thus, consumer protection must be taken to another level to ensure that no matter what companies get rid of, support and compensatory avenues exist.&lt;br /&gt;
&lt;br /&gt;
====Manifest V2 shutdown (Jul 2025)====&lt;br /&gt;
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users as well as making Chromium (a browser that many other browsers use as their base) switch to Manifest V3, and disabled the ability to turn them back on.&amp;lt;ref&amp;gt;{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manifest V3 disabled the &amp;lt;code&amp;gt;webRequestBlocking&amp;lt;/code&amp;gt; permission in the &amp;lt;code&amp;gt;webRequest&amp;lt;/code&amp;gt; API,&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}&amp;lt;/ref&amp;gt; preventing many ad content blockers (such as uBlock Origin) from working.&amp;lt;ref&amp;gt;{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}&amp;lt;/ref&amp;gt; Google cites performance reasons,&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote=&amp;quot;In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with.&amp;quot;}}&amp;lt;/ref&amp;gt; but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.&lt;br /&gt;
&lt;br /&gt;
===Google Pixel===&lt;br /&gt;
====Pixel devices bricked due to confusing reasons====&lt;br /&gt;
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs, or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.&amp;lt;ref&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won&#039;t help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}&amp;lt;/ref&amp;gt; The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung&#039;s EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or [[wikipedia:Fastboot|Fastboot]], making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.&lt;br /&gt;
&lt;br /&gt;
This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special &amp;quot;USB boot&amp;quot; bit flag set to 1.&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, this recovery bootloader is inaccessible to the public, and is not possible to recreate it without Google&#039;s private keys. This makes it impossible to repair a device in this state, other than to do a technically challenging repair involving desoldering the UFS chip to repopulate its contents or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.&lt;br /&gt;
&lt;br /&gt;
Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue. Even with there being a sizable post on their bug tracker,&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20251004223929/https://issuetracker.google.com/issues/437705274 |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; and despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Pixel 4a battery reduction update (Jan 2025)====&lt;br /&gt;
{{Main|Pixel 4a Battery Performance Program}}&lt;br /&gt;
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on &amp;quot;Impacted Devices&amp;quot;. Not all units were affected. It&#039;s speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.&lt;br /&gt;
&lt;br /&gt;
As compensation, Google offered a free battery replacement only in select countries. In other countries, you could choose between a $50 USD payment or $100 USD worth of Google Store credits. However, some users reported difficulty obtaining their compensation.&lt;br /&gt;
&lt;br /&gt;
===User freedom incidents===&lt;br /&gt;
====Banning domain-blockers from Play Store (2013)====&lt;br /&gt;
Since 2013, Google has taken down all apps on G-Play that can block connections to arbitrary [[wikipedia:Domain_Name_System|domain-names]] via [https://developer.android.com/develop/connectivity/vpn the official VPN API], most of those apps being marketed as ad-blockers.&amp;lt;ref&amp;gt;{{ cite news |first=Liam |last=Tung |date=14 Mar 2013 |website=ZDNET |title=Google kicks ad-blocker apps off Play store |url=https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |url-status=live |archive-url=https://web.archive.org/web/20150625111914/https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |archive-date=2015-06-25}}&amp;lt;/ref&amp;gt; This forced apps such as AdGuard and NetGuard to distribute their ad-blocking features elsewhere.&amp;lt;ref&amp;gt;{{cite web |first=Ekaterina |last=Kachalova |title=Why is AdGuard not on Google Play? |date=17 Aug 2023 |website=AdGuard |url=https://adguard.com/en/blog/adguard-google-play-removal.html |url-status=live |archive-url=https://web.archive.org/web/20230822100645/https://adguard.com/en/blog/adguard-google-play-removal.html |archive-date=2023-08-22}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;netguard&amp;quot;&amp;gt;{{cite web |author=NetGuard |website=[[GitHub]] |title=NetGuard/ADBLOCKING.md |url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L6 |url-status=live |archive-url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md |archive-date=2026-03-29}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
*Line 6: ad blocking is not possible with the Play store version because Google does not allow ad blocking apps in the Play store&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
*Line 106: Please do not mention this feature in Google Play store comments, since Google does not allow ad blocking applications in the Google Play store.&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google cites their own Developer Distribution Agreement (terms of service for devs), claiming that those apps are &amp;quot;disruptive&amp;quot;, as if to imply hacking or cracking. Many people claim that&#039;s an invalid excuse, and that the ulterior motive was to increase ad-revenue.&lt;br /&gt;
&lt;br /&gt;
====Phone number requirement for new accounts (2020)====&lt;br /&gt;
Since 2020, Google has increasingly forced users to verify phone-numbers via SMS during account registration,&amp;lt;ref&amp;gt;{{cite web |website=Google Support |url=https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |date=20 Mar 2020 |title=Cannot create a new Google account, it is requiring a phone number (Forced phone verification) |author=FB3 Network |url-status=live |archive-url=https://web.archive.org/web/20260509050746/https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |archive-date=2026-05-09}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=DarknessMoonlight |date=30 Jun 2021 |title=Does Google now require a phone number to make new Gmail accounts? |url=https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |url-status=live |website=[[Reddit]] |archive-url=https://web.archive.org/web/20260427144651/https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |archive-date=2026-04-27}}&amp;lt;/ref&amp;gt; in an effort to &amp;quot;mitigate spam, bot activity, and account abuse&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |author=CLRN |date=2025-07-25 |title=How to skip phone verification while creating Gmail account? |url=https://www.clrn.org/how-to-skip-phone-verification-while-creating-gmail-account/ |url-status=live |access-date=2026-05-05 |website=California Learning Resource Network}}&amp;lt;/ref&amp;gt; They have a system that immediately detects reuse of numbers, so no accounts can have the same associated number.{{Citation needed}} This, paired with [[YouTube#Forced sign-in|YouTube&#039;s sign-in requirement]], makes it impossible for users to share a single &amp;quot;guest&amp;quot; account, as is typically the case for families sharing a smart TV.&lt;br /&gt;
&lt;br /&gt;
====Blocking sideloading of unverified Android apps (Aug 2025)====&lt;br /&gt;
{{Main|Google blocking sideloading of unverified Android apps}}&lt;br /&gt;
On 25 August 2025, &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog |archive-url=http://web.archive.org/web/20260128013331/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20260119211509/https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt; This marks a significant change to Android&#039;s long-standing support for sideloading apps.&lt;br /&gt;
&lt;br /&gt;
Devices without [[Google Mobile Services]] or running [[wikipedia:List_of_custom_Android_distributions|custom ROMs]] are exempt.&amp;lt;ref name=&amp;quot;:22&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}&amp;lt;/ref&amp;gt; Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |author=JohnC_21 |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=https://web.archive.org/web/20250825210732/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=2025-08-25}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Lawsuit==&lt;br /&gt;
===Privacy violations===&lt;br /&gt;
====&#039;&#039;Rodriguez v. Google LLC&#039;&#039; (&#039;&#039;May 2021—September 2025&#039;&#039;)====&lt;br /&gt;
Google&#039;s &amp;quot;Web &amp;amp; App Activity&amp;quot; (WAA) setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.&amp;lt;ref&amp;gt;{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251011171640/https://googlewebappactivitylawsuit.com/Home/FAQ |archive-date=11 Oct 2025}}&amp;lt;/ref&amp;gt; Google collected mobile device data for eight years from users who opted out of tracking under the WAA.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |last=Staab |first=Theresa |date=18 Sep 2025 |title=Someone is Always Watching: Implications of Google&#039;s WAA Privacy Case |url=https://lawreview.syr.edu/someone-is-always-watching-implications-of-googles-waa-privacy-case/ |access-date=26 Mar 2026 |website=Syracuse Law Review}}&amp;lt;/ref&amp;gt; The dates of use/activity in question were between July 1, 2016 and September 23, 2024.&amp;lt;ref&amp;gt;{{Cite web |date=23 Oct 2024 |title=FAQs: Google Web App Activity lawsuit |url=https://help.wfu.edu/support/solutions/articles/13000825158-faqs-google-web-app-activity-lawsuit |url-status=live |access-date=26 Mar 2026 |website=Wake Forest University}}&amp;lt;/ref&amp;gt; On September 3, 2025, the San Francisco Federal Court jury held Google liable two of three claims of privacy invasion. The plaintiffs were awarded $425.7 million in compensatory damages for invasion of privacy, totaling around $4 per person for the approximate 98 million affected users, but since the jury found that Google did not act with malicious intent, no punitive damages were awarded.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite news |last=Mollman |first=Brittney |last2=Sosnicki |first2=Luke |date=2025-09-05 |title=Federal Jury Awards $425.7 Million in Google Privacy Case: Key Takeaways on Consent Design and Litigation Risk |url=https://www.thompsoncoburn.com/insights/federal-jury-awards-425-7-million-in-google-privacy-case-key-takeaways-on-consent-design-and-litigation-risk/ |url-status=live |access-date=2026-05-05 |work=Thompson Coburn LLP}}&amp;lt;/ref&amp;gt; Google filed an appeal to this verdict &amp;quot;on the basis that the jury misunderstood the functionality of its privacy tools and that users were adequately informed through layered disclosures and consent flows&amp;quot;.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt; Claim submission may begin once the appeals process finishes.&amp;lt;ref&amp;gt;{{Cite web |date=2025-11-05 |title=$425M Verdict in Google Web &amp;amp; App Activity Privacy Class Action Lawsuit — Do You Qualify? |url=https://openclassactions.com/settlements/google-web-and-app-activity-privacy-class-action-lawsuit.php |url-status=live |access-date=2026-05-05 |website=OpenClassActions}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;Thele v. Google LLC&#039;&#039; (&#039;&#039;November 2025—&#039;&#039;)====&lt;br /&gt;
On the 11th of November, 2025, Thomas Thele filed a demand for jury trial in a class action complaint against Google LLC. In the filing it states that &amp;quot;on or about October 10, 2025, Google secretly turned on Gemini for all its users’ Gmail, Chat, and Meet accounts, enabling AI to track its users’ private communications contained in those platforms without the users’ knowledge or consent&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |last=Wolfson |first=Tina |last2=Ahdoot |first2=Robert |last3=Maya |first3=Theodore |last4=Brown |first4=Alyssa |date=2025-11-11 |title=UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA - CLASS ACTION COMPLAINT DEMAND FOR JURY TRIAL |url=https://www.classaction.org/media/thele-v-google-complaint_2.pdf |url-status=live |access-date=2026-05-05 |website=ClassAction}}&amp;lt;/ref&amp;gt; The suit &amp;quot;alleges that Google is violating the California Invasion of Privacy Act&amp;quot;,&amp;lt;ref&amp;gt;{{Cite web |last=Burnson |first=Robert |date=2025-11-12 |title=Google sued for allegedly using Gemini AI to secretly track user data |url=https://www.business-standard.com/technology/tech-news/google-sued-for-allegedly-using-gemini-ai-to-secretly-track-user-data-125111200603_1.html |url-status=live |access-date=2026-05-05 |website=Business Standard}}&amp;lt;/ref&amp;gt; a law enacted in 1967 which dictates the terms by which advances in technology can be used for the purpose of invading the privacy of citizens.&amp;lt;ref&amp;gt;{{Cite web |date=1967 |title=CHAPTER 1.5. Invasion of Privacy |url=https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=PEN&amp;amp;part=1.&amp;amp;title=15.&amp;amp;chapter=1.5 |url-status=live |access-date=2026-05-05 |website=California Legislative Information}}&amp;lt;/ref&amp;gt; The defendant, Google LLC, filed a Motion to Dismiss which is scheduled to be heard on May 1, 2026.&amp;lt;ref&amp;gt;{{Cite web |date=2026-04-27 |title=Thele v. Google LLC |url=https://www.pacermonitor.com/public/case/61129560/Thele_v_Google_LLC |url-status=live |access-date=2026-05-05 |website=PacerMonitor}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anti-competitive behavior===&lt;br /&gt;
====&#039;&#039;Epic Games, Inc. v. Google Inc.&#039;&#039; (&#039;&#039;August 2020—May 2025&#039;&#039;)====&lt;br /&gt;
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].&amp;lt;ref&amp;gt;{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam&#039;s 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com |archive-url=http://web.archive.org/web/20251211034837/https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |archive-date=11 Dec 2025}}&amp;lt;/ref&amp;gt; On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of &#039;&#039;Fortnite&#039;&#039; to redirect users to Epic Games&#039; storefront to purchase in-game currency (&amp;quot;V-Bucks&amp;quot;) alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google&#039;s storefronts, and &#039;&#039;Fortnite&#039;&#039; was removed from both app stores the same day.&lt;br /&gt;
&lt;br /&gt;
Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behavior. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.&amp;lt;ref&amp;gt;{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111151936/https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |archive-date=11 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Social media addiction bellwether trials===&lt;br /&gt;
====Los Angeles Superior Court, JCCP 5255 (&#039;&#039;2026&#039;&#039;)====&lt;br /&gt;
Starting in January of 2026, [[Meta]] (Facebook and [[Instagram]]) and [[Google]] ([[YouTube]]) faced legal claims of their platforms being intentionally addictive and harmful to children. [[ByteDance]] ([[TikTok]]) and Snap ([[Snapchat]]) were named initially, but settled for undisclosed terms before the trial began. A 19-year-old girl, referred to by the initials &amp;quot;KGM&amp;quot; or Kaley, and two other plaintiffs were selected for bellwether trials—test cases tried as part of an MDL.&amp;lt;ref&amp;gt;{{Cite web |last=Huamani |first=Kaitlyn |last2=Ortutay |first2=Barbara |date=9 Feb 2026 |title=Landmark trial accusing tech giants of harming children with addictive social media begins |url=https://www.pbs.org/newshour/nation/landmark-trial-accusing-tech-giants-of-harming-children-with-addictive-social-media-begins |url-status=live |access-date=25 Mar 2026 |website=PBS News}}&amp;lt;/ref&amp;gt;  On March 25, 2026, the California jury concluded in KGM&#039;s case that [[Meta]] and Google were guilty of negligent for their apps—[[Instagram]], Facebook, and [[YouTube]]—being deliberately built to be addictive, which the companies&#039; executives knew this and failed to protect their youngest users.&amp;lt;ref&amp;gt;{{Cite web |last=Allyn |first=Bobby |date=25 Mar 2026 |title=Jury finds Meta and Google negligent in social media harms trial |url=https://www.npr.org/2026/03/25/nx-s1-5746125/meta-youtube-social-media-trial-verdict |url-status=live |access-date=26 Mar 2026 |website=npr}}&amp;lt;/ref&amp;gt; [[Meta]] was charged to pay $4.2 million for compensatory and punitive damages, and charged Google $1.8 million.&amp;lt;ref&amp;gt;{{Cite web |last=Kang |first=Cecilia |last2=Mac |first2=Ryan |last3=Tan |first3=Eli |date=25 Mar 2026 |title=Meta and YouTube Found Negligent in Landmark Social Media Addiction Case |url=https://www.nytimes.com/2026/03/25/technology/social-media-trial-verdict.html |url-status=live |access-date=26 Mar 2026 |website=The New York Times}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*{{Main|List of Google products}}&lt;br /&gt;
&lt;br /&gt;
*[[Advertising overload]]&lt;br /&gt;
*[[Google asserts the right to seize phones during repairs]]&lt;br /&gt;
*[[Google Nest Protect forced to use Google app]]&lt;br /&gt;
*[[Google Nest thermostat smart features disabled]]&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]]&lt;br /&gt;
&lt;br /&gt;
==External links==&lt;br /&gt;
&lt;br /&gt;
*&amp;quot;[https://www.jwz.org/xscreensaver/google.html XScreenSaver: Google Store Privacy Policy]&amp;quot;. Google pretending to care about privacy by forcing a fully-local (no internet) minimal-permission screen-saver app to specify a privacy-policy. That blog-post contains many sources on Google&#039;s anti-consumer practices&lt;br /&gt;
*[https://theywillbanyou.com/| They Will Ban You - Cases of user accounts banned for unfair reasons]&lt;br /&gt;
*[https://killedbygoogle.com/ Killed by Google - Dead products list]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Google| ]]&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google&amp;diff=56174</id>
		<title>Google</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google&amp;diff=56174"/>
		<updated>2026-06-04T23:41:30Z</updated>

		<summary type="html">&lt;p&gt;Iii: edits for wiki style policy, and grammatical/readability edits&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup|Issue 1=Article formatting should follow [[Template:CompanyPreload]]. With Google&#039;s history, it may be useful to use tabling for incidents.|Issue 2=Citations need to follow proper formatting. See [[Template:Cite web]].|Issue 3=Citations should be placed after punctuation.|Issue 4=Make sure that section headers are in sentence case where applicable.}}&lt;br /&gt;
{{CompanyCargo&lt;br /&gt;
|Founded=1998&lt;br /&gt;
|Industry=Technology&lt;br /&gt;
|Logo=Google.webp&lt;br /&gt;
|ParentCompany=Alphabet Inc.&lt;br /&gt;
|Type=Subsidiary&lt;br /&gt;
|Description=Google is one of the most influential technology companies in the world, originally known for developing the most widely used search engine.&lt;br /&gt;
|Website=https://www.google.com/&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;{{Wplink|Google|Google LLC}}&#039;&#039;&#039;, founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.&amp;lt;ref&amp;gt;{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com |archive-url=http://web.archive.org/web/20260222070659/https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |archive-date=22 Feb 2026}}&amp;lt;/ref&amp;gt; Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.&amp;lt;ref&amp;gt;{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025 |archive-url=http://web.archive.org/web/20260128182647/https://about.google/products/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Google Search| Google&#039;s search engine]] remains its most well-known service, but the company has significantly diversified its offerings. Key products include the [[Android]] operating system, the [[Google Chrome]] web browser, [[Google Drive]] for cloud storage, [https://wikipedia.org/wiki/Google_Maps Google Maps], [[YouTube]], and [[wikipedia:Google_Play|Google Play]].&amp;lt;ref&amp;gt;{{Cite web |title=Helpful products, built with you in mind |url=https://about.google/intl/ALL_us/products/ |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20260205114442/https://about.google/intl/ALL_us/products/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;{{Citation needed}} Additionally, the company provides digital advertising services through Google Ads, generating the majority of its revenue.&amp;lt;ref&amp;gt;{{Cite web |date=4 Feb 2025 |title=Alphabet Announces Fourth Quarter and Fiscal Year 2024 Results |url=https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251002181452/https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |archive-date=2 Oct 2025}}&amp;lt;/ref&amp;gt; In recent years, Google has also developed hardware products such as the Pixel smartphone and Nest smart home devices.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
Google has faced ongoing scrutiny related to data privacy, competition, and its dominant position in the market, such concerns have stretched as far back as 2012.&amp;lt;ref&amp;gt;{{Cite web |last=Cohen |first=Adam |date=5 Mar 2012 |title=Will We Ever Get Strong Internet Privacy Rules? |url=https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |url-status=live |access-date=5 Apr 2025 |website=Time |archive-url=http://web.archive.org/web/20260205121437/https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=6 Sep 2023 |title=REPORT: Google at 25: From “Don’t Be Evil” To ¯\_(ツ)_/¯ |url=https://techoversight.org/2023/09/06/google-at-25/ |url-status=live |access-date=5 Apr 2025 |website=The Tech Oversight Project |archive-url=http://web.archive.org/web/20251004223929/https://techoversight.org/2023/09/06/google-at-25/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; The company has been the subject of various legal and regulatory challenges, particularly concerning antitrust issues, the use of personal data, and its impact on consumer choice.{{Citation needed}} The US government is currently engaged in an antitrust lawsuit against Google, with a decision expected early 2025.&amp;lt;ref&amp;gt;{{Cite web |date=25 Nov 2024 |title=Closing Arguments, November 25: Once, Twice, Three Times a Monopolist |url=https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |url-status=live |access-date=5 Apr 2025 |website=US v Google |archive-url=http://web.archive.org/web/20250906103632/https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |archive-date=6 Sep 2025}}&amp;lt;/ref&amp;gt; {{UpdateNeeded|date={{subst:August}} {{subst:2025}}|reason=We need updates on this situation.}}&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
In December 2024, Google announced to organisations that use its advertising products, that from 16 February 2025, it will no longer prohibit them from employing [[wikipedia:Fingerprint_(computing)|fingerprinting]] techniques.&amp;lt;ref&amp;gt;{{Cite web |last=Almond |first=Stephen |date=19 Dec 2024 |title=Our response to Google’s policy change on fingerprinting |url=https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |url-status=live |access-date=5 Apr 2025 |website=ico. |archive-url=http://web.archive.org/web/20260128163957/https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===User freedom===&lt;br /&gt;
Google has a long history of patronizing their user base by taking away options or not giving users a choice in the first place.&lt;br /&gt;
&lt;br /&gt;
For example, in 2014, Google removed normal MicroSD write access on Android 4.4&amp;lt;ref&amp;gt;{{cite news |first=Cody |last=Toombs |url=https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |title=External Blues: Google Has Brought Big Changes To SD Cards In KitKat, And Even Samsung Is Implementing Them |url-status=live |date=17 Feb 2014 |url-status=live |website=Android Police |archive-url=https://web.archive.org/web/20140218064033/https://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/ |archive-date=2014-02-18}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |date=23 Feb 2014 |title=Re: What about removable SD card in 4.4 |website=Google Groups |archive-url=https://web.archive.org/web/20260209114224/https://groups.google.com/g/android-platform/c/14VUiIgwUjY/m/UsxMYwu02z0J |archive-date=2026-02-09 }}&amp;lt;/ref&amp;gt;, limiting each application to their own dedicated folder, arguing that this makes it easy to remove all files left by the app during uninstallation, given that no app can leave files outside their own dedicated folder.&lt;br /&gt;
&lt;br /&gt;
No menu option to change this behaviour was given to the user, therefore users who wanted to restore normal write access were forced to resort to unofficial methods involving bootloader unlocking and rooting.&lt;br /&gt;
&lt;br /&gt;
It should be noted that Google&#039;s own Android smartphones and tablet computers (Nexus and Pixel devices) never featured a memory card slot. Similar restrictions were later added to USB on-the-go storage.&amp;lt;ref name=android-traditional-storage&amp;gt;{{cite web |title=Traditional storage &amp;amp;#124; Android Open Source Project |url=https://source.android.com/docs/core/storage/traditional |url-status=live |website=Android}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2018, Google added a clipboard manager to their keyboard app, Gboard.&amp;lt;ref&amp;gt;{{cite web |url=https://www.xda-developers.com/gboard-clipboard-manager/ |title=Gboard 7.7 adds a Clipboard Manager feature to Google&#039;s keyboard app |date=22 Oct 2018 |first=Mishaal |last=Rahman |url-status=live |website=XDA Developers |archive-url=https://web.archive.org/web/20190119233536/https://www.xda-developers.com/gboard-clipboard-manager/ |archive-date=2019-01-19}}&amp;lt;/ref&amp;gt; But in 2022, Google decided on behalf of their users that they don&#039;t need to retain clipboard items for any longer than one hour. Therefore, they added a one-hour time limit, meaning any clipboard item older than one hour is automatically deleted, with no option to change this behaviour. The only way to retain clipboard items for more than one hour is to manually mark them as &amp;quot;pinned&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |first=Ethan |last=Gillian |title=Remember: Android 13 clears clipboard 1 hour after copying |url=https://techzle.com/remember-android-13-clears-clipboard-1-hour-after-copying |url-status=live |website=Techzle |date=17 Aug 2022}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2019, Google took away the ability to turn off the &amp;quot;pull-to-refresh&amp;quot; gesture on the mobile edition of their Chrome web browser, following by refusing to reinstate the option after an abnormally high number of complaints that the gesture causes accidental refreshes. See [[Google_Chrome#Mandatory_pull-to-refresh|Google Chrome § Mandatory pull-to-refresh]].&lt;br /&gt;
&lt;br /&gt;
Google lets app developers arbitrarily [[screenshot blocking|prevent device owners from capturing screenshots and screen recordings]] on Android. While the original intention was to prevent sensitive information in banking apps from getting outside, it has been severely overused by app developers and prevents legitimate uses such as asking for help in forums and bug reports. Google provided no option for device owners to override it, so the only way is to unlock the bootloader and modify the operating system.&amp;lt;ref&amp;gt;{{cite web |url=https://www.howtogeek.com/why-screenshots-dont-always-work-especially-in-secure-apps/ |website=How To Geek |author=Faisal Rasool |title=Why Your Phone Blocks Screenshots in Secure Apps |date=2025-08-23 |access-date=2026-05-26 }}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=konradkar |url=https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |website=[[Reddit]] |title=Booking.com app disallow to take screenshot, can I bypass this? |date=2020-02-14 |access-date=2026-05-26 |archive-url=https://web.archive.org/web/20230615071612/https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |archive-date=2023-06-15}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{excerpt|Android Developer Verification}}&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
===Account lockouts===&lt;br /&gt;
Google has been reported to have randomly locked people out of their accounts due to ostensible security reasons, which are not lifted even if the user had provided the correct credentials and/or even if the user have correctly followed all the verification prompts such as SMS verification. These have caused anguishes for many affected users who are unable to access their contents, emails and services as a result. Furthermore, some had reported that they are forced to undergo SMS verification even when recovery email addresses are already configured to their accounts, thereby likely constituting instances of [[Forced identification|forced verification]] in broad senses.&amp;lt;ref&amp;gt;{{cite web |url=https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |date=5 May 2021 |author=Feniks_Gaming |title=Mike Rose (No More Robots Publisher) Locked out of Gmail, speaks to google support to find out their own staff are locked out of their personal Gmail too... |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210505101632/https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ |archive-date=2021-05-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |url=https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |first=Mike |last=Rose |url-status=dead |date=4 May 2021 |title=This morning, I was locked out of my Google account |website=Nitter |archive-url=https://web.archive.org/web/20220908195211/https://nitter.dark.fail/RaveofRavendale/status/1389507928269393921 |archive-date=2022-09-08}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |title=FYI: Google can lock you out of your account for no reason |author=danielrosehill |date=5 Aug 2021 |url=https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |url-status=live |website=[[Reddit]] |archive-url=http://web.archive.org/web/20210805030048/https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ |archive-date=2021-08-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=LegitimateAttempt4 |date=20 Jul 2023 |title=DAE noticed that Google had taken security account lockouts to a zealotic level? |url-status=live |url=https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |website=[[Reddit]] |archive-url=http://web.archive.org/web/20230720181226/https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ |archive-date=2023-07-20}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Deletion of inactive accounts===&lt;br /&gt;
In May 2023, Google announced that [[Inactive account deletion|deletion of inactive user accounts]] would occur starting in December 2023, citing security reasons, noting that old and unused accounts are more likely to be compromised. Google claimed that &amp;quot;Forgotten or unattended accounts often rely on old or re-used passwords that may have been compromised, have not had two factor authentication set up, and receive fewer security checks by the user,&amp;quot; while saying that Google &amp;quot;has no plans to delete [[YouTube]] videos&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |last1=Lawler |first1=Richard |title=Google might delete your Gmail account if you haven&#039;t logged in for two years |url=https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |website=The Verge |access-date=21 December 2023 |language=en |date=16 May 2023 |archive-url=http://web.archive.org/web/20260205121216/https://www.theverge.com/2023/5/16/23725438/google-gmail-deleting-inactive-accounts |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Porter |first1=Jon |title=Reminder: Google is about to start purging inactive accounts |url=https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |website=The Verge |access-date=21 December 2023 |language=en |date=28 November 2023 |archive-url=http://web.archive.org/web/20251212230239/https://www.theverge.com/2023/11/28/23979178/google-inactive-accounts-deletion-december-2023-psa-reminder |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |last1=Amadeo |first1=Ron |title=Google&#039;s new &amp;quot;inactive account&amp;quot; policy won&#039;t delete years of YouTube videos |url=https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |website=Ars Technica |access-date=21 December 2023 |language=en-us |date=17 May 2023 |archive-url=http://web.archive.org/web/20251212092014/https://arstechnica.com/google/2023/05/googles-new-inactive-account-policy-wont-delete-years-of-youtube-videos/ |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt; The decision to delete inactive accounts has sparked some criticism and backlash. The cited security rationale behind such decision was ridiculed and was compared to a hypothetical scenario where a bank should be burned down if it is not secure against robbers.&amp;lt;ref&amp;gt;{{cite web |last1=Novet |first1=Jordan |title=Google&#039;s plan to purge inactive accounts isn&#039;t sitting well with some users |url=https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |website=CNBC |access-date=21 December 2023 |language=en |date&lt;br /&gt;
=19 August 2023 |archive-url=http://web.archive.org/web/20250831223936/https://www.cnbc.com/2023/08/19/google-faces-criticism-of-plan-to-purge-inactive-accounts.html |archive-date=31 Aug 2025}}&amp;lt;/ref&amp;gt; Such policies could adversely affect those who had good reasons to become inactive for a long time, such as hospitalization, prison incarceration, and being in totalitarian countries which have prolonged internet shutdowns. Moreover, the Anonymous hacktivist collective has protested against the decision to delete inactive accounts multiple times, describing them as &amp;quot;harsh&amp;quot; and saying that the decision will &amp;quot;destroy history&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |date=18 Jul 2023 |title=Anonymous puts Taiwan flag, national anthem on 2 UN websites |url=https://www.taiwannews.com.tw/en/news/4946597 |first=Keoni |last=Everington |url-status=live |access-date=21 Dec 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20231014070719/https://www.taiwannews.com.tw/en/news/4946597 |archive-date=2023-10-14}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=18 Oct 2023 |title=&#039;Anonymous&#039; hacks Chinese government site to protest Israel–Hamas war |url-status=live |url=https://www.taiwannews.com.tw/en/news/5022840 |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240221120716/https://www.taiwannews.com.tw/en/news/5022840 |archive-date=2024-02-21}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |first=Keoni |last=Everington |date=8 Dec 2023 |title=Anonymous posts Taiwan flag on UN site |website=Taiwan News |url=https://www.taiwannews.com.tw/en/news/5055454 |url-status=live |access-date=21 December 2023 |website=Taiwan News |archive-url=http://web.archive.org/web/20240228035811/https://www.taiwannews.com.tw/en/news/5055454 |archive-date=2024-02-28}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anticompetitive practices===&lt;br /&gt;
Google has a great history of anticompetitive practices. For example, in 2020 the company was sued for practices involving pushing off relevant search results in order to favor advertisements and the inclusion of [[bloatware]] on Android devices.&amp;lt;ref&amp;gt;{{Cite web |publisher=Eaton Business School|date=31 Aug 2021 |title=Google - A display of anti-competitive behaviour|url=https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |url-status=live |archive-url=https://web.archive.org/web/20250523013602/https://ebsedu.org/blog/google-a-display-of-anti-competitive-behavior |archive-date=2025-05-23 |access-date=25 May 2026 |website=Eaton Business School}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The [[Android Developer Verification]] program prevents sideloading and external app stores, such as [[F-Droid]] to be an available alternative to the Google Play Store.&lt;br /&gt;
&lt;br /&gt;
===Google device repair program restrictions===&lt;br /&gt;
{{Main|Google asserts the right to seize your phone during a repair}}&lt;br /&gt;
Google&#039;s Service &amp;amp; Repair Program terms explicitly state that any device containing non-Google-authorized parts &amp;quot;will not be returned&amp;quot; to the customer.&lt;br /&gt;
&lt;br /&gt;
===Target API level requirements for Google Play apps===&lt;br /&gt;
Google&#039;s policy of requiring apps for Android to target recent API levels to appear in the Play Store&amp;lt;ref&amp;gt;{{Cite web |date=31 Aug 2024 |title=Policy Center |url=https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |access-date=May 9, 2025 |website=Play Console Help |archive-url=http://web.archive.org/web/20260215054419/https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt; creates a continuous cycle of maintenance and redevelopment that can be especially burdensome for smaller developers, indie creators, and consumers.&lt;br /&gt;
&lt;br /&gt;
The requirement for apps to target newer APIs each year serves some legitimate security and feature purposes. However, it also effectively functions as a form of forced obsolescence. Even perfectly functional apps that don&#039;t need technical updates must be regularly reworked just to remain visible on the Play Store.&lt;br /&gt;
&lt;br /&gt;
This creates several issues:&lt;br /&gt;
&lt;br /&gt;
*Development resources must be allocated to updating apps rather than creating new features&lt;br /&gt;
*Smaller teams and individual developers are placed at a disadvantage attempting to keep up with the constant update cycle&lt;br /&gt;
*Legacy apps that are no longer actively maintained disappear, even if they&#039;re still useful&lt;br /&gt;
*The cost of maintaining apps increases, potentially making some projects financially nonviable&lt;br /&gt;
*Losing access to previously purchased apps when upgrading devices&lt;br /&gt;
*Users being unable to reinstall older apps that worked perfectly well for their needs&lt;br /&gt;
*Facing unexpected costs to replace functionality they&#039;ve already paid for&lt;br /&gt;
*Dealing with the frustration of discovering favorite apps have disappeared&lt;br /&gt;
&lt;br /&gt;
While Google argues this approach improves the Android ecosystem&#039;s security and functionality, it does place a significant burden on developers and can lead to the premature &amp;quot;death&amp;quot; of otherwise functional applications.&lt;br /&gt;
&lt;br /&gt;
This creates a troubling disconnect in digital ownership. Consumers reasonably expect that when they purchase an app, they should maintain access to it across their devices over time. Instead, they discover their digital purchases can effectively vanish due to policy decisions beyond their control.&lt;br /&gt;
&lt;br /&gt;
===Ban on third-party tech support ads===&lt;br /&gt;
Google prohibits tech support ads on their platform if they are not authorized by the manufacturer.&amp;lt;ref&amp;gt;{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google |archive-url=http://web.archive.org/web/20251112170608/https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |archive-date=12 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===The chargeback incident===&lt;br /&gt;
In November 2022, a Google customer accidentally purchased two Google Pixel smartphones instead of one, directly from Google (no third-party reseller), and tried to return one package to Google for a refund, but the shipping was unsuccessful.&lt;br /&gt;
&lt;br /&gt;
A Google customer support person suggested the customer to perform a chargeback. The customer acted accordingly without understanding the implications, resulting in the termination of their Google account shortly after. The account was 15 years old at that time.&amp;lt;ref&amp;gt;{{cite web |first=Noel |last=Santos |website=Virtual Curiosities |date=8 Dec 2024 |url=https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |url-status=live |title=DANGER!!!: Chargeback = ACCOUNT PERMANENTLY BANNED |archive-url=http://web.archive.org/web/20260205120523/https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned |archive-date=2026-02-05}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=justAnotherLedditor |date=16 Dec 2022 |url=https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |url-status=live |title=TIFU by accidentally buying two Google Pixels and ended up getting my 15 year old Google Account permanently banned. |website=[[Reddit]] |archive-url=http://web.archive.org/web/20260113140546/https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ |archive-date=2026-01-13}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===AI integrations in Google Search===&lt;br /&gt;
On may 19th, 2026, Google announced modifications for [[Google Search]] to include more AI integrations involving inclusion of [[Google Gemini]] Flash 3.5 and integration of AI agents. These changes have sparked several controversies, including for example critizicing the reliability of searching using AI because of hallucinations, inabilities of AIs to detect malicious web sites and possibilities to use AI to control results obtained on searches. &amp;lt;ref&amp;gt;{{Cite web |last=Yildrim |first=Ece |date=19 May 2026 |title=Google Search Is Dead. Welcome to the Era of the ‘Intelligent Search Box’ |url=https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |url-status=live |archive-url=https://web.archive.org/web/20260519204100/https://gizmodo.com/google-search-is-dead-welcome-to-the-era-of-the-intelligent-search-box-2000760626 |archive-date=2026-05-19 |access-date=21 May 2026 |website=Gizmodo}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Reid|first=Elizabeth |date=19 May 2026 |title=A new era for AI Search |url=https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |url-status=live |archive-url=https://web.archive.org/web/20260519181835/https://blog.google/products-and-platforms/products/search/search-io-2026/#powerful-ai |archive-date=2026-05-19 |access-date=21 May 2026 |website=Google Blog}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===Service shutdowns===&lt;br /&gt;
&lt;br /&gt;
====Google Play Music shutdown (Dec 2020)====&lt;br /&gt;
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store &amp;amp; Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223929/https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20251214224205/https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |archive-date=14 Dec 2025}}&amp;lt;/ref&amp;gt; Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.&amp;lt;ref&amp;gt;{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek |archive-url=http://web.archive.org/web/20251004223929/https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt; Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.&amp;lt;ref&amp;gt;{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz |archive-url=http://web.archive.org/web/20250805235415/https://www.technobezz.com/buy-music-google-play |archive-date=5 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google |archive-url=http://web.archive.org/web/20250708163846/https://9to5google.com/2020/12/03/google-play-music-dead/ |archive-date=8 Jul 2025}}&amp;lt;/ref&amp;gt; This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |author=The YouTube Team |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog |archive-url=http://web.archive.org/web/20260201140126/https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the shut down, users lost access to the music they paid for, with no way to download them. Google justified this by transferring all playlists and purchase history to YouTube Music, and only refunding songs that were not directly available,&amp;lt;ref&amp;gt;{{Cite web |author=Garry |date=10 Oct 2023 |title=What happened to my songs on Google Music? |url=https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |url-status=live |access-date=5 Apr 2025 |website=Darwin&#039;s Data |archive-url=http://web.archive.org/web/20251004223930/https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Chaney |first=Sarah |date=5 Feb 2022 |title=What Happened to Google Play Music? |url=https://www.makeuseof.com/what-happened-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=MUO |archive-url=http://web.archive.org/web/20260205111318/https://www.makeuseof.com/what-happened-to-google-play-music/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; with no guarantee that the songs will remain available through the new service. Users found that their purchased songs were no longer able to stream at 320kbps on YouTube Music compared to Google Play Music unless they paid for the monthly subscription.&amp;lt;ref&amp;gt;{{Cite web |last=Cutlack |first=Gary |date=23 Dec 2012 |title=Google Music UK: everything you need to know |url=https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |url-status=live |access-date=5 Apr 2025 |website=TechRadar |archive-url=http://web.archive.org/web/20251221115733/https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |archive-date=21 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=L. Hald |first=Nicole |date=24 Mar 2025 |title=How Is YouTube Music Sound Quality in 2025? Is It Any Good? |url=https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |url-status=live |access-date=5 Apr 2025 |website=NoteBurner |archive-url=http://web.archive.org/web/20260217143252/https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |archive-date=17 Feb 2026}}&amp;lt;/ref&amp;gt; If a user failed to initiate the transfer of their music library or locally download their songs by 24th February 2021, then they lost all access and all data associated with Google Play Music.&amp;lt;ref&amp;gt;{{Cite web |last=Sodhi |first=Tanishka |date=8 Feb 2021 |title=Google Play Music Data Will Be Deleted on February 24: Here’s How to Transfer to YouTube Music |url=https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |url-status=live |access-date=5 Apr 2025 |website=Gadgets 360 |archive-url=http://web.archive.org/web/20260205112610/https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; YouTube Music does not provide the option to download songs as MP3s, with local downloads requiring an internet connection every 30 days to continue working offline.&amp;lt;ref&amp;gt;{{Cite web |title=Download music and podcasts to listen to offline |url=https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223930/https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Stadia shutdown (Jan 2023)====&lt;br /&gt;
In January 2023, Google announced the shutdown of its cloud gaming service, Stadia, which was launched in November 2019.&amp;lt;ref&amp;gt;{{Cite web |author=Verge Staff |title=RIP Google Stadia: the latest news on the discontinued cloud gaming service |url=https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |url-status=live |access-date=5 Apr 2025 |website=The Verge |archive-url=http://web.archive.org/web/20260101185119/https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |archive-date=1 Jan 2026}}&amp;lt;/ref&amp;gt; Stadia required users to purchase games individually, unlike other gaming platforms that offer subscription-based access. Upon the service&#039;s closure, Google promised to refund consumers for their purchases, including both games and hardware. The refunds for games and software were issued automatically.&amp;lt;ref&amp;gt;{{Cite web |last=Ravenscraft |first=Erin |date=10 Nov 2022 |title=Stadia Is Dying. Here’s What’s in Your Refund and How to Get It |url=https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |url-status=live |access-date=5 Apr 2025 |website=Wired |archive-url=http://web.archive.org/web/20260205115111/https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stadia users were effectively renting access to games, as the platform did not allow for traditional ownership or offline play. With the service discontinued, consumers were left without access to the content they had purchased. Stadia users who had bought controllers and other peripherals for the service were also impacted by the shutdown. While Google offered refunds to customers, many Stadia consumers were left with equipment that no longer performs the advertised functions and limited recourse for repurposing or reselling their devices.&amp;lt;ref&amp;gt;{{Cite web |last=Ashworth |first=Mack |date=5 Oct 2022 |title=Stadia Shut Down: How To Use Your Hardware Now Google’s Shutting It Down |url=https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |url-status=live |access-date=5 Apr 2025 |website=Game Revolution |archive-url=http://web.archive.org/web/20251004224131/https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.&amp;lt;ref&amp;gt;{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here&#039;s how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central |archive-url=http://web.archive.org/web/20251109164004/https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |archive-date=9 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Assistant third-party list support (Jun 2023)====&lt;br /&gt;
On June 20th, 2023, Google disabled third-party list support for Google Assistant.&amp;lt;ref&amp;gt;{{Cite web |access-date=2025-09-16 |title=Where are my old lists? |url=https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-url=https://web.archive.org/web/20250427212604/https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-date=2025-04-27}}&amp;lt;/ref&amp;gt; This feature allowed lists through third-party services, such as AnyList or Todoist, to be managed via Google Assistant. After this change, the only list provider available through Google Assistant, was Google&#039;s own list service, Google Keep.&amp;lt;ref&amp;gt;{{Cite web |last=Mathur |first=Chandraveer |website=Android Police |date=2023-05-31 |title=Google Assistant is killing support for notes and lists integration with third-party apps |url=https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-url=http://web.archive.org/web/20251218051543/https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-date=18 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Jamboard shutdown (Dec 2024)====&lt;br /&gt;
{{Main|Google Jamboard}}&lt;br /&gt;
In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.&lt;br /&gt;
&lt;br /&gt;
The Jamboard product was a $5,000 device that Google pitched as a collaborative tool through its Google Workspace service. After the service no longer existed, however, the device became a brick and the users as well as the buyers were left unsupported and uncompensated.&lt;br /&gt;
&lt;br /&gt;
Situations like this highlight the vulnerability of the consumer market since proprietary products are completely at the hands of developers who can cut services on a whim. Thus, consumer protection must be taken to another level to ensure that no matter what companies get rid of, support and compensatory avenues exist.&lt;br /&gt;
&lt;br /&gt;
====Manifest V2 shutdown (Jul 2025)====&lt;br /&gt;
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users as well as making Chromium (a browser that many other browsers use as their base) switch to Manifest V3, and disabled the ability to turn them back on.&amp;lt;ref&amp;gt;{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manifest V3 disabled the &amp;lt;code&amp;gt;webRequestBlocking&amp;lt;/code&amp;gt; permission in the &amp;lt;code&amp;gt;webRequest&amp;lt;/code&amp;gt; API&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}&amp;lt;/ref&amp;gt;, preventing many ad content blockers (such as uBlock Origin) from working.&amp;lt;ref&amp;gt;{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}&amp;lt;/ref&amp;gt; Google cites performance reasons &amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote=&amp;quot;In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with.&amp;quot;}}&amp;lt;/ref&amp;gt;, but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.&lt;br /&gt;
&lt;br /&gt;
===Google Pixel===&lt;br /&gt;
====Pixel devices bricked due to confusing reasons====&lt;br /&gt;
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs, or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.&amp;lt;ref&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won&#039;t help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}&amp;lt;/ref&amp;gt; The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung&#039;s EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or [[wikipedia:Fastboot|Fastboot]], making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.&lt;br /&gt;
&lt;br /&gt;
This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special &amp;quot;USB boot&amp;quot; bit flag set to 1. &amp;lt;ref&amp;gt;{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, this recovery bootloader is inaccessible to the public, and is not possible to recreate it without Google&#039;s private keys. This makes it impossible to repair a device in this state, other than to do a technically challenging repair involving desoldering the UFS chip to repopulate its contents or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.&lt;br /&gt;
&lt;br /&gt;
Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue, despite there being a sizable post on their bug tracker.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20251004223929/https://issuetracker.google.com/issues/437705274 |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}&amp;lt;/ref&amp;gt; despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Pixel 4a battery reduction update (Jan 2025)====&lt;br /&gt;
{{Main|Pixel 4a Battery Performance Program}}&lt;br /&gt;
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on &amp;quot;Impacted Devices&amp;quot;. Not all units were affected. It&#039;s speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.&lt;br /&gt;
&lt;br /&gt;
As compensation, Google offered a free battery replacement only in select countries. In other countries, you could choose between a $50 USD payment or $100 USD worth of Google Store credits. However, some users reported difficulty obtaining their compensation.&lt;br /&gt;
&lt;br /&gt;
===User freedom incidents===&lt;br /&gt;
====Banning domain-blockers from Play Store (2013)====&lt;br /&gt;
Since 2013, Google has taken down all apps on G-Play that can block connections to arbitrary [[wikipedia:Domain_Name_System|domain-names]] via [https://developer.android.com/develop/connectivity/vpn the official VPN API], most of those apps being marketed as ad-blockers.&amp;lt;ref&amp;gt;{{ cite news |first=Liam |last=Tung |date=14 Mar 2013 |website=ZDNET |title=Google kicks ad-blocker apps off Play store |url=https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |url-status=live |archive-url=https://web.archive.org/web/20150625111914/https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/ |archive-date=2015-06-25}}&amp;lt;/ref&amp;gt; This forced apps such as AdGuard and NetGuard to distribute their ad-blocking features elsewhere.&amp;lt;ref&amp;gt;{{cite web |first=Ekaterina |last=Kachalova |title=Why is AdGuard not on Google Play? |date=17 Aug 2023 |website=AdGuard |url=https://adguard.com/en/blog/adguard-google-play-removal.html |url-status=live |archive-url=https://web.archive.org/web/20230822100645/https://adguard.com/en/blog/adguard-google-play-removal.html |archive-date=2023-08-22}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;netguard&amp;quot;&amp;gt;{{cite web |author=NetGuard |website=[[GitHub]] |title=NetGuard/ADBLOCKING.md |url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L6 |url-status=live |archive-url=https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md |archive-date=2026-03-29}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
*Line 6: ad blocking is not possible with the Play store version because Google does not allow ad blocking apps in the Play store&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
*Line 106: Please do not mention this feature in Google Play store comments, since Google does not allow ad blocking applications in the Google Play store.&amp;lt;ref name=&amp;quot;netguard&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google cites their own Developer Distribution Agreement (terms of service for devs), claiming that those apps are &amp;quot;disruptive&amp;quot;, as if to imply hacking or cracking. Many people claim that&#039;s an invalid excuse, and that the ulterior motive was to increase ad-revenue.&lt;br /&gt;
&lt;br /&gt;
====Phone number requirement for new accounts (2020)====&lt;br /&gt;
Since 2020, Google has increasingly forced users to verify phone-numbers via SMS during account registration,&amp;lt;ref&amp;gt;{{cite web |website=Google Support |url=https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |date=20 Mar 2020 |title=Cannot create a new Google account, it is requiring a phone number (Forced phone verification) |author=FB3 Network |url-status=live |archive-url=https://web.archive.org/web/20260509050746/https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification |archive-date=2026-05-09}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |author=DarknessMoonlight |date=30 Jun 2021 |title=Does Google now require a phone number to make new Gmail accounts? |url=https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |url-status=live |website=[[Reddit]] |archive-url=https://web.archive.org/web/20260427144651/https://old.reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/ |archive-date=2026-04-27}}&amp;lt;/ref&amp;gt; in an effort to &amp;quot;mitigate spam, bot activity, and account abuse&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |author=CLRN |date=2025-07-25 |title=How to skip phone verification while creating Gmail account? |url=https://www.clrn.org/how-to-skip-phone-verification-while-creating-gmail-account/ |url-status=live |access-date=2026-05-05 |website=California Learning Resource Network}}&amp;lt;/ref&amp;gt;. They have a system that immediately detects reuse of numbers, so no accounts can have the same associated number.{{Citation needed}} This, paired with [[YouTube#Forced sign-in|YouTube&#039;s sign-in requirement]], makes it impossible for users to share a single &amp;quot;guest&amp;quot; account, as is typically the case for families sharing a smart TV.&lt;br /&gt;
&lt;br /&gt;
====Blocking sideloading of unverified Android apps (Aug 2025)====&lt;br /&gt;
{{Main|Google blocking sideloading of unverified Android apps}}&lt;br /&gt;
On 25 August 2025, &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog |archive-url=http://web.archive.org/web/20260128013331/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20260119211509/https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt; This marks a significant change to Android&#039;s long-standing support for sideloading apps.&lt;br /&gt;
&lt;br /&gt;
Devices without [[Google Mobile Services]] or running [[wikipedia:List_of_custom_Android_distributions|custom ROMs]] are exempt.&amp;lt;ref name=&amp;quot;:22&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}&amp;lt;/ref&amp;gt; Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |author=JohnC_21 |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=https://web.archive.org/web/20250825210732/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=2025-08-25}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Lawsuit==&lt;br /&gt;
===Privacy violations===&lt;br /&gt;
====&#039;&#039;Rodriguez v. Google LLC&#039;&#039; (&#039;&#039;May 2021—September 2025&#039;&#039;)====&lt;br /&gt;
Google&#039;s &amp;quot;Web &amp;amp; App Activity&amp;quot; (WAA) setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.&amp;lt;ref&amp;gt;{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251011171640/https://googlewebappactivitylawsuit.com/Home/FAQ |archive-date=11 Oct 2025}}&amp;lt;/ref&amp;gt; Google collected mobile device data for eight years from users who opted out of tracking under the WAA.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |last=Staab |first=Theresa |date=18 Sep 2025 |title=Someone is Always Watching: Implications of Google&#039;s WAA Privacy Case |url=https://lawreview.syr.edu/someone-is-always-watching-implications-of-googles-waa-privacy-case/ |access-date=26 Mar 2026 |website=Syracuse Law Review}}&amp;lt;/ref&amp;gt; The dates of use/activity in question were between July 1, 2016 and September 23, 2024.&amp;lt;ref&amp;gt;{{Cite web |date=23 Oct 2024 |title=FAQs: Google Web App Activity lawsuit |url=https://help.wfu.edu/support/solutions/articles/13000825158-faqs-google-web-app-activity-lawsuit |url-status=live |access-date=26 Mar 2026 |website=Wake Forest University}}&amp;lt;/ref&amp;gt; On September 3, 2025, the San Francisco Federal Court jury held Google liable two of three claims of privacy invasion. The plaintiffs were awarded $425.7 million in compensatory damages for invasion of privacy, totaling around $4 per person for the approximate 98 million affected users, but since the jury found that Google did not act with malicious intent, no punitive damages were awarded.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite news |last=Mollman |first=Brittney |last2=Sosnicki |first2=Luke |date=2025-09-05 |title=Federal Jury Awards $425.7 Million in Google Privacy Case: Key Takeaways on Consent Design and Litigation Risk |url=https://www.thompsoncoburn.com/insights/federal-jury-awards-425-7-million-in-google-privacy-case-key-takeaways-on-consent-design-and-litigation-risk/ |url-status=live |access-date=2026-05-05 |work=Thompson Coburn LLP}}&amp;lt;/ref&amp;gt; Google filed an appeal to this verdict &amp;quot;on the basis that the jury misunderstood the functionality of its privacy tools and that users were adequately informed through layered disclosures and consent flows&amp;quot;&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;. Claim submission may begin once the appeals process finishes&amp;lt;ref&amp;gt;{{Cite web |date=2025-11-05 |title=$425M Verdict in Google Web &amp;amp; App Activity Privacy Class Action Lawsuit — Do You Qualify? |url=https://openclassactions.com/settlements/google-web-and-app-activity-privacy-class-action-lawsuit.php |url-status=live |access-date=2026-05-05 |website=OpenClassActions}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;Thele v. Google LLC&#039;&#039; (&#039;&#039;November 2025—&#039;&#039;)====&lt;br /&gt;
On the 11th of November, 2025, Thomas Thele filed a demand for jury trial in a class action complaint against Google LLC. In the filing it states that &amp;quot;on or about October 10, 2025, Google secretly turned on Gemini for all its users’ Gmail, Chat, and Meet accounts, enabling AI to track its users’ private communications contained in those platforms without the users’ knowledge or consent&amp;quot; &amp;lt;ref&amp;gt;{{Cite web |last=Wolfson |first=Tina |last2=Ahdoot |first2=Robert |last3=Maya |first3=Theodore |last4=Brown |first4=Alyssa |date=2025-11-11 |title=UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA - CLASS ACTION COMPLAINT DEMAND FOR JURY TRIAL |url=https://www.classaction.org/media/thele-v-google-complaint_2.pdf |url-status=live |access-date=2026-05-05 |website=ClassAction}}&amp;lt;/ref&amp;gt;. The suit &amp;quot;alleges that Google is violating the California Invasion of Privacy Act&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |last=Burnson |first=Robert |date=2025-11-12 |title=Google sued for allegedly using Gemini AI to secretly track user data |url=https://www.business-standard.com/technology/tech-news/google-sued-for-allegedly-using-gemini-ai-to-secretly-track-user-data-125111200603_1.html |url-status=live |access-date=2026-05-05 |website=Business Standard}}&amp;lt;/ref&amp;gt;, a law enacted in 1967 which dictates the terms by which advances in technology can be used for the purpose of invading the privacy of citizens&amp;lt;ref&amp;gt;{{Cite web |date=1967 |title=CHAPTER 1.5. Invasion of Privacy |url=https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=PEN&amp;amp;part=1.&amp;amp;title=15.&amp;amp;chapter=1.5 |url-status=live |access-date=2026-05-05 |website=California Legislative Information}}&amp;lt;/ref&amp;gt;. The defendant, Google LLC, filed a Motion to Dismiss which is scheduled to be heard on May 1, 2026&amp;lt;ref&amp;gt;{{Cite web |date=2026-04-27 |title=Thele v. Google LLC |url=https://www.pacermonitor.com/public/case/61129560/Thele_v_Google_LLC |url-status=live |access-date=2026-05-05 |website=PacerMonitor}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Anti-competitive behavior===&lt;br /&gt;
====&#039;&#039;Epic Games, Inc. v. Google Inc.&#039;&#039; (&#039;&#039;August 2020—May 2025&#039;&#039;)====&lt;br /&gt;
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].&amp;lt;ref&amp;gt;{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam&#039;s 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com |archive-url=http://web.archive.org/web/20251211034837/https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |archive-date=11 Dec 2025}}&amp;lt;/ref&amp;gt; On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of &#039;&#039;Fortnite&#039;&#039; to redirect users to Epic Games&#039; storefront to purchase in-game currency (&amp;quot;V-Bucks&amp;quot;) alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google&#039;s storefronts, and &#039;&#039;Fortnite&#039;&#039; was removed from both app stores the same day.&lt;br /&gt;
&lt;br /&gt;
Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behavior. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.&amp;lt;ref&amp;gt;{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111151936/https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |archive-date=11 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Social media addiction bellwether trials===&lt;br /&gt;
====Los Angeles Superior Court, JCCP 5255 (&#039;&#039;2026&#039;&#039;)====&lt;br /&gt;
Starting in January of 2026, [[Meta]] (Facebook and [[Instagram]]) and [[Google]] ([[YouTube]]) faced legal claims of their platforms being intentionally addictive and harmful to children. [[ByteDance]] ([[TikTok]]) and Snap ([[Snapchat]]) were named initially, but settled for undisclosed terms before the trial began. A 19-year-old girl, referred to by the initials &amp;quot;KGM&amp;quot; or Kaley, and two other plaintiffs were selected for bellwether trials—test cases tried as part of an MDL.&amp;lt;ref&amp;gt;{{Cite web |last=Huamani |first=Kaitlyn |last2=Ortutay |first2=Barbara |date=9 Feb 2026 |title=Landmark trial accusing tech giants of harming children with addictive social media begins |url=https://www.pbs.org/newshour/nation/landmark-trial-accusing-tech-giants-of-harming-children-with-addictive-social-media-begins |url-status=live |access-date=25 Mar 2026 |website=PBS News}}&amp;lt;/ref&amp;gt;  On March 25, 2026, the California jury concluded in KGM&#039;s case that [[Meta]] and Google were guilty of negligent for their apps—[[Instagram]], Facebook, and [[YouTube]]—being deliberately built to be addictive, which the companies&#039; executives knew this and failed to protect their youngest users.&amp;lt;ref&amp;gt;{{Cite web |last=Allyn |first=Bobby |date=25 Mar 2026 |title=Jury finds Meta and Google negligent in social media harms trial |url=https://www.npr.org/2026/03/25/nx-s1-5746125/meta-youtube-social-media-trial-verdict |url-status=live |access-date=26 Mar 2026 |website=npr}}&amp;lt;/ref&amp;gt; [[Meta]] was charged to pay $4.2 million for compensatory and punitive damages, and charged Google $1.8 million.&amp;lt;ref&amp;gt;{{Cite web |last=Kang |first=Cecilia |last2=Mac |first2=Ryan |last3=Tan |first3=Eli |date=25 Mar 2026 |title=Meta and YouTube Found Negligent in Landmark Social Media Addiction Case |url=https://www.nytimes.com/2026/03/25/technology/social-media-trial-verdict.html |url-status=live |access-date=26 Mar 2026 |website=The New York Times}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*{{Main|List of Google products}}&lt;br /&gt;
&lt;br /&gt;
*[[Advertising overload]]&lt;br /&gt;
*[[Google asserts the right to seize phones during repairs]]&lt;br /&gt;
*[[Google Nest Protect forced to use Google app]]&lt;br /&gt;
*[[Google Nest thermostat smart features disabled]]&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]]&lt;br /&gt;
&lt;br /&gt;
==External links==&lt;br /&gt;
&lt;br /&gt;
*&amp;quot;[https://www.jwz.org/xscreensaver/google.html XScreenSaver: Google Store Privacy Policy]&amp;quot;. Google pretending to care about privacy by forcing a fully-local (no internet) minimal-permission screen-saver app to specify a privacy-policy. That blog-post contains many sources on Google&#039;s anti-consumer practices&lt;br /&gt;
*[https://theywillbanyou.com/| They Will Ban You - Cases of user accounts banned for unfair reasons]&lt;br /&gt;
*[https://killedbygoogle.com/ Killed by Google - Dead products list]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Google| ]]&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Digital_Millennium_Copyright_Act&amp;diff=56138</id>
		<title>Digital Millennium Copyright Act</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Digital_Millennium_Copyright_Act&amp;diff=56138"/>
		<updated>2026-06-04T22:35:23Z</updated>

		<summary type="html">&lt;p&gt;Iii: linked FTC and added intro to abbreviation&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Post-audit revision: 2026-04-05. Issues fixed: 25. Claims removed: 0. Keith-proof review: 2026-04-05. Mismatches fixed: 9 of 9. Post-keith fixes: 2026-04-05. EFF over-citation cleaned (4 refs removed), FAI attribution restructured, OpenSecrets qualifier fixed. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- MODIFIED SECTIONS: Legislative history, Title I: Anti-circumvention (Section 1201), Title IV: Miscellaneous provisions, Title V: Vessel hull designs, Section 512 in practice, Takedown abuse, Key court cases, The 2020 Copyright Office study, Academic criticism, iFixit &amp;amp; the Repair Association, Public Knowledge, Section 1201 reform, Section 512 reform, State workarounds, Industry lobbying --&amp;gt;&lt;br /&gt;
{{#seo:&lt;br /&gt;
|description=The Digital Millennium Copyright Act (DMCA) criminalizes circumventing digital locks &amp;amp; creates safe harbor for platforms. Section 1201 restricts repair &amp;amp; security research.&lt;br /&gt;
}}&lt;br /&gt;
The &#039;&#039;&#039;Digital Millennium Copyright Act&#039;&#039;&#039; (DMCA) is a United States copyright law enacted on October 28, 1998, as Public Law 105-304.&amp;lt;ref name=&amp;quot;plaw&amp;quot;&amp;gt;{{Cite web |title=Public Law 105-304 - Digital Millennium Copyright Act |url=https://www.govinfo.gov/content/pkg/PLAW-105publ304/pdf/PLAW-105publ304.pdf |website=GovInfo |access-date=5 April 2026}}&amp;lt;/ref&amp;gt; The statute amended Title 17 of the U.S. Code to implement two 1996 World Intellectual Property Organization (WIPO) treaties, criminalize the circumvention of [[digital rights management|digital locks]], &amp;amp; create safe harbor protections for online service providers.&amp;lt;ref name=&amp;quot;hr2281&amp;quot;&amp;gt;{{Cite web |title=H.R.2281 - Digital Millennium Copyright Act |url=https://www.congress.gov/bill/105th-congress/house-bill/2281 |website=Congress.gov |access-date=5 April 2026}}&amp;lt;/ref&amp;gt; Its most controversial provision, [[DMCA Section 1201]], has been used by manufacturers to block [[right to repair|independent repair]], suppress security research, &amp;amp; prevent [[interoperability]] with third-party products, extending the law&#039;s reach well beyond its original anti-piracy purpose.&amp;lt;!-- CITATION NEEDED: EFF or repair advocacy source for Section 1201 repair/interoperability claims --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Legislative history==&lt;br /&gt;
&lt;br /&gt;
The DMCA originated from the 1996 WIPO diplomatic conference in Geneva, which produced the WIPO Copyright Treaty (WCT) &amp;amp; the WIPO Performances and Phonograms Treaty (WPPT). Both treaties required signatory nations to provide legal protection against circumvention of technological protection measures (TPMs) on copyrighted works.&amp;lt;ref&amp;gt;WIPO Copyright Treaty, Art. 11 (1996); WIPO Performances and Phonograms Treaty, Art. 18 (1996).&amp;lt;/ref&amp;gt; The Clinton Administration championed both treaties &amp;amp; urged Congress to pass implementing legislation, arguing that strong digital copyright protections were necessary for the growth of the digital economy.&lt;br /&gt;
&lt;br /&gt;
Rep. Howard Coble (R-NC) introduced H.R. 2281, titled the &amp;quot;WIPO Copyright Treaties Implementation Act,&amp;quot; on July 29, 1997. Sen. Orrin Hatch (R-UT) introduced the Senate counterpart, S. 2037.&amp;lt;ref name=&amp;quot;hr2281&amp;quot; /&amp;gt; During committee hearings, a coalition of 62 law professors warned Congress that the proposed anti-circumvention rules would create unprecedented &amp;quot;paracopyright&amp;quot; regulations governing conduct traditionally outside copyright law.&amp;lt;!-- CITATION NEEDED: H.R. Rep. No. 105-551 pt. 2 at 24, or yjolt.org for 62 law professors coalition --&amp;gt; Prof. Pamela Samuelson of UC Berkeley described the provisions as creating an entirely new property right distinct from any existing right under the Copyright Act.&amp;lt;ref name=&amp;quot;samuelson&amp;quot;&amp;gt;Pamela Samuelson, &#039;&#039;Intellectual Property and the Digital Economy: Why the Anti-Circumvention Regulations Need to Be Revised&#039;&#039;, 14 Berkeley Tech. L.J. 519 (1999).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Senate passed S. 2037 by a 99-0 roll call vote on May 14, 1998. The House passed H.R. 2281 by voice vote under suspension of the rules on August 4, 1998. A conference committee reconciled the two versions, filing Conference Report 105-796 on October 8, 1998.&amp;lt;ref name=&amp;quot;plaw&amp;quot; /&amp;gt; President Clinton signed the bill on October 28, 1998.&lt;br /&gt;
&lt;br /&gt;
Congress intended a &amp;quot;grand bargain&amp;quot;: content creators received legal protections for their digital locks, while online service providers received safe harbors shielding them from secondary liability for user-uploaded content.&amp;lt;!-- CITATION NEEDED: source for &amp;quot;grand bargain&amp;quot; characterization --&amp;gt; In practice, the anti-circumvention provisions have been used to restrict repair markets &amp;amp; block third-party compatibility, while the safe harbor takedown system has been used for censorship &amp;amp; anti-competitive purposes.&amp;lt;!-- CITATION NEEDED: EFF or Copyright Office 512 study for takedown system abuse --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Structure of the law==&lt;br /&gt;
&lt;br /&gt;
The DMCA contains five titles, each addressing different aspects of digital copyright.&amp;lt;ref name=&amp;quot;plaw&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Title I: Anti-circumvention (Section 1201)===&lt;br /&gt;
&lt;br /&gt;
{{Main|DMCA Section 1201}}&lt;br /&gt;
&lt;br /&gt;
Title I added Sections 1201 &amp;amp; 1202 to the Copyright Act. Section 1201 prohibits circumventing TPMs that control access to copyrighted works &amp;amp; bans the distribution of tools designed to do so.&amp;lt;ref&amp;gt;17 U.S.C. § 1201.&amp;lt;/ref&amp;gt; Section 1202 protects Copyright Management Information (CMI), making it illegal to remove or alter digital watermarks or identifying metadata with the intent to enable infringement.&amp;lt;ref&amp;gt;17 U.S.C. § 1202.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Section 1201 is the DMCA&#039;s most litigated &amp;amp; most criticized provision. Congress included a &amp;quot;fail-safe&amp;quot; mechanism: every three years, the U.S. Copyright Office conducts a rulemaking to grant temporary exemptions from the circumvention ban.&amp;lt;ref&amp;gt;17 U.S.C. § 1201(a)(1)(C).&amp;lt;/ref&amp;gt; Nine rulemaking cycles have been completed since 2000,&amp;lt;!-- CITATION NEEDED: Copyright Office rulemaking index for cycle count --&amp;gt; granting exemptions for smartphone jailbreaking, vehicle repair, medical device repair, &amp;amp; security research, among others. All exemptions expire automatically &amp;amp; must be renewed.&amp;lt;ref&amp;gt;17 U.S.C. § 1201(a)(1)(B)-(D).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The most consequential limitation is the &amp;quot;tools gap.&amp;quot; &#039;&#039;&#039;The Librarian of Congress can only exempt the &#039;&#039;act&#039;&#039; of circumvention; the anti-trafficking provisions in 1201(a)(2) remain untouched. A consumer may have the legal right to bypass a software lock but no legal way to obtain the tool needed to do so.&#039;&#039;&#039;&amp;lt;ref&amp;gt;17 U.S.C. § 1201(a)(1)(C)-(D) (granting exemption authority only for the act of circumvention, not for trafficking in tools).&amp;lt;/ref&amp;gt; The [https://fulu.org FULU Foundation]&#039;s repair bounty program paid a developer $20,000 to bypass software locks on [[Echelon fitness firmware lockout|Echelon exercise bikes]], but distributing the resulting tool in the United States violates Section 1201.&amp;lt;ref&amp;gt;{{Cite web |last=Koebler |first=Jason |date=27 August 2025 |title=Developer Unlocks Newly Enshittified Echelon Exercise Bikes, But Can&#039;t Legally Release His Software |url=https://www.404media.co/developer-unlocks-newly-enshittified-echelon-exercise-bikes-but-cant-legally-release-his-software/ |website=404 Media |access-date=5 April 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Title II: Safe harbor (Section 512)===&lt;br /&gt;
&lt;br /&gt;
Title II created Section 512 of the Copyright Act, establishing four safe harbors for online service providers (OSPs) against copyright infringement liability.&amp;lt;ref name=&amp;quot;sec512&amp;quot;&amp;gt;17 U.S.C. § 512.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Section 512(a)&#039;&#039;&#039; protects ISPs acting as conduits for data transmission. &#039;&#039;&#039;Section 512(b)&#039;&#039;&#039; covers system caching. &#039;&#039;&#039;Section 512(c)&#039;&#039;&#039;, the most frequently invoked safe harbor, protects platforms hosting user-generated content (YouTube, social media) from liability provided they lack actual knowledge of specific infringing material, receive no direct financial benefit from the infringement where they can control it, &amp;amp; remove content promptly upon receiving a valid notice.&amp;lt;ref name=&amp;quot;sec512&amp;quot; /&amp;gt; &#039;&#039;&#039;Section 512(d)&#039;&#039;&#039; covers search engines &amp;amp; directories that link to infringing material.&lt;br /&gt;
&lt;br /&gt;
To qualify for any safe harbor, an OSP must adopt &amp;amp; &amp;quot;reasonably implement&amp;quot; a policy for terminating repeat infringers under Section 512(i), &amp;amp; must register a designated agent with the Copyright Office to receive takedown notices.&amp;lt;ref name=&amp;quot;sec512&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Notice-and-takedown procedure====&lt;br /&gt;
&lt;br /&gt;
Section 512 established an extrajudicial mechanism for copyright enforcement. A copyright holder sends a written notice to the OSP&#039;s designated agent identifying the infringed work, the infringing material (usually by URL), &amp;amp; a statement of good faith belief that the use is unauthorized, signed under penalty of perjury.&amp;lt;ref name=&amp;quot;sec512&amp;quot; /&amp;gt; The OSP must &amp;quot;expeditiously&amp;quot; remove the material to maintain safe harbor immunity.&lt;br /&gt;
&lt;br /&gt;
The affected user may file a counter-notification, stating under penalty of perjury that the material was removed by mistake or misidentification. Once a valid counter-notice is filed, the OSP must restore the material within 10 to 14 business days unless the copyright holder files a federal lawsuit.&amp;lt;ref name=&amp;quot;sec512&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Section 512(f) creates liability for knowingly material misrepresentations in takedown notices or counter-notices. In practice, courts have set the bar for 512(f) claims so high that the provision provides little deterrent against fraudulent takedowns.&amp;lt;!-- CITATION NEEDED: case law or EFF analysis on 512(f) enforcement difficulty --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Title III: Computer maintenance===&lt;br /&gt;
&lt;br /&gt;
Title III amended Section 117 of the Copyright Act to allow making copies of a computer program during the maintenance or repair of a machine, provided the copy is made solely by activating the machine &amp;amp; is destroyed immediately afterward.&amp;lt;ref&amp;gt;17 U.S.C. § 117(c).&amp;lt;/ref&amp;gt; Congress enacted this to overturn &#039;&#039;MAI Systems Corp. v. Peak Computer, Inc.&#039;&#039; (9th Cir. 1993), which held that loading software into RAM during computer repair constituted copyright infringement.&amp;lt;ref&amp;gt;&#039;&#039;MAI Systems Corp. v. Peak Computer, Inc.&#039;&#039;, 991 F.2d 511 (9th Cir. 1993).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Title IV: Miscellaneous provisions===&lt;br /&gt;
&lt;br /&gt;
Congress also directed the Copyright Office to study digital distance education under Title IV, which contains several amendments relevant to libraries, education, &amp;amp; broadcasting. That study led to the Technology, Education, and Copyright Harmonization (TEACH) Act of 2002.&amp;lt;ref name=&amp;quot;plaw&amp;quot; /&amp;gt; Title IV also expanded the library &amp;amp; archives preservation exemption &amp;amp; addressed ephemeral recordings for sound recordings.&lt;br /&gt;
&lt;br /&gt;
===Title V: Vessel hull designs===&lt;br /&gt;
&lt;br /&gt;
Chapter 13 of Title 17 received a &#039;&#039;sui generis&#039;&#039; protection regime for boat hull designs under Title V.&amp;lt;ref name=&amp;quot;plaw&amp;quot; /&amp;gt; It has minimal consumer rights relevance.&lt;br /&gt;
&lt;br /&gt;
==Section 512 in practice==&lt;br /&gt;
&lt;br /&gt;
===Takedown volume===&lt;br /&gt;
&lt;br /&gt;
The scale of DMCA takedowns has grown exponentially since the statute&#039;s passage. By late 2016, Google had processed 1 billion URL removal requests. As of early 2026, Google has received over 16.5 billion takedown requests, processing roughly 50 million per week.&amp;lt;ref name=&amp;quot;google-transparency&amp;quot;&amp;gt;{{Cite web |title=Google Transparency Report: Copyright |url=https://transparencyreport.google.com/copyright/overview |website=Google |access-date=12 April 2026}}&amp;lt;/ref&amp;gt; The Lumen Database, a research project at Harvard Law School, has archived over 67 million takedown notices submitted by copyright holders across platforms.&amp;lt;ref name=&amp;quot;lumen&amp;quot;&amp;gt;{{Cite web |title=About Lumen |url=https://lumendatabase.org/pages/about |website=Lumen Database, Harvard Law School |access-date=12 April 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Takedown abuse===&lt;br /&gt;
&lt;br /&gt;
The automated &amp;amp; rapid nature of the system has enabled widespread abuse.&amp;lt;!-- CITATION NEEDED: EFF, Copyright Office 512 study, or Lumen Database research for takedown system abuse --&amp;gt; Because OSPs face liability if they fail to remove content, they err on the side of takedown, creating a presumption of removal for users.&lt;br /&gt;
&lt;br /&gt;
In 2009, the U.S. Chamber of Commerce filed a DMCA takedown against a parody website created by the activist group The Yes Men, temporarily disabling 400 other websites hosted on the same ISP.&amp;lt;ref&amp;gt;{{Cite web |title=U.S. Chamber of Commerce uses the DMCA to silence critic |url=https://publicknowledge.org/u-s-chamber-of-commerce-uses-the-dmca-to-silence-critic/ |website=Public Knowledge |date=27 October 2009 |access-date=5 April 2026}}&amp;lt;/ref&amp;gt; Film critics &amp;amp; video essayists relying on fair use routinely have their YouTube accounts suspended via automated copyright strikes. Academic researchers using the Lumen Database identified nearly 34,000 coordinated fraudulent notices using backdated &amp;quot;fake original&amp;quot; URLs on dummy websites to delist legitimate news sites from search results.&amp;lt;!-- CITATION NEEDED: Shreya Tewari research paper via walledculture.org or techdirt.com for 34,000 fraudulent notices figure --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
YouTube&#039;s Content ID system, which goes beyond the statutory requirements of Section 512, automatically demonetizes or blocks videos without conducting fair use analysis. Small creators cannot fight claims from media conglomerates with dedicated enforcement teams. Content ID processes over 700 million claims per year.&amp;lt;!-- CITATION NEEDED: supplemental non-JS source for Content ID volume (e.g., uppbeat.io or medialake.ai) --&amp;gt;&amp;lt;ref name=&amp;quot;google-transparency&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Key court cases===&lt;br /&gt;
&lt;br /&gt;
Three appellate decisions define the modern scope of Section 512.&lt;br /&gt;
&lt;br /&gt;
In &#039;&#039;Viacom International, Inc. v. YouTube, Inc.&#039;&#039; (2nd Cir. 2012), Viacom sued YouTube for $1 billion, alleging YouTube built its business on unauthorized hosting of Viacom&#039;s content. The Second Circuit ruled that general awareness of ubiquitous infringement on a platform does not strip safe harbor protection; a copyright holder must show the OSP had &amp;quot;actual knowledge&amp;quot; of specific infringing clips or &amp;quot;red flag&amp;quot; awareness where specific infringement was objectively obvious.&amp;lt;ref&amp;gt;&#039;&#039;Viacom International, Inc. v. YouTube, Inc.&#039;&#039;, 676 F.3d 19 (2d Cir. 2012).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In &#039;&#039;Capitol Records, LLC v. Vimeo, LLC&#039;&#039; (2nd Cir. 2016), the court held that Section 512(c) safe harbor applies to pre-1972 sound recordings &amp;amp; that Vimeo employees viewing or &amp;quot;liking&amp;quot; user-uploaded videos containing copyrighted music did not establish &amp;quot;red flag&amp;quot; knowledge.&amp;lt;ref&amp;gt;&#039;&#039;Capitol Records, LLC v. Vimeo, LLC&#039;&#039;, 826 F.3d 78 (2d Cir. 2016).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;BMG Rights Management v. Cox Communications&#039;&#039; (4th Cir. 2018) established that safe harbor requires genuine implementation of a repeat infringer policy. Cox had a 13-strike policy but never terminated paying subscribers; it routinely deleted millions of notices &amp;amp; blacklisted copyright monitors. The Fourth Circuit stripped Cox&#039;s safe harbor, ruling that &amp;quot;repeat infringers&amp;quot; means anyone who repeatedly infringes, not only those adjudicated liable in court.&amp;lt;ref&amp;gt;&#039;&#039;BMG Rights Management, LLC v. Cox Communications, Inc.&#039;&#039;, 881 F.3d 293 (4th Cir. 2018).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===The 2020 Copyright Office study===&lt;br /&gt;
&lt;br /&gt;
After a five-year investigation, the U.S. Copyright Office released a 250-page report in May 2020 evaluating the effectiveness of Section 512.&amp;lt;ref name=&amp;quot;512study&amp;quot;&amp;gt;{{Cite web |title=Section 512 of Title 17: A Report of the Register of Copyrights |url=https://www.copyright.gov/policy/section512/section-512-full-report.pdf |website=U.S. Copyright Office |date=May 2020 |access-date=5 April 2026}}&amp;lt;/ref&amp;gt; The Office concluded that the original balance Congress intended has been &amp;quot;unbalanced,&amp;quot; overwhelmingly favoring OSPs at the expense of content creators. The burden of policing the internet for identical re-uploads falls entirely on rights holders.&lt;br /&gt;
&lt;br /&gt;
The Office recommended legislative &amp;quot;fine-tuning&amp;quot; but explicitly declined to recommend European-style &amp;quot;notice-and-staydown&amp;quot; mandates or site-blocking, citing the need for additional study of &amp;quot;potential non-copyright implications.&amp;quot; Recommendations included clarifying the distinction between &amp;quot;actual&amp;quot; &amp;amp; &amp;quot;red flag&amp;quot; knowledge, adjusting the 10-to-14-day counter-notice waiting period, &amp;amp; tightening eligibility requirements for repeat infringer policies.&amp;lt;ref name=&amp;quot;512study&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Criticism==&lt;br /&gt;
&lt;br /&gt;
===Academic criticism===&lt;br /&gt;
&lt;br /&gt;
Prof. Pamela Samuelson has argued that the DMCA&#039;s anti-circumvention provisions represent an unprecedented departure into &amp;quot;paracopyright,&amp;quot; regulating conduct outside the traditional sphere of intellectual property.&amp;lt;ref name=&amp;quot;samuelson&amp;quot; /&amp;gt; Legal scholars have argued that Section 512 has created a private, extrajudicial removal regime that bypasses the procedural due process inherent in the court system. Content is removed first, with the burden on the affected party to contest the removal after the fact.&amp;lt;!-- CITATION NEEDED: academic source on Section 512 as extrajudicial removal regime (e.g., Wendy Seltzer, Stanford Law Review, or Copyright Office 512 study) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Electronic Frontier Foundation===&lt;br /&gt;
&lt;br /&gt;
The EFF has challenged Section 1201 since the statute&#039;s passage. It argues that the anti-circumvention provisions pose &amp;quot;a serious threat that jeopardizes fair use,&amp;quot; chilling free expression &amp;amp; security research by criminalizing the act of bypassing digital locks even for lawful purposes.&amp;lt;ref name=&amp;quot;eff-dmca&amp;quot;&amp;gt;{{Cite web |title=DMCA |url=https://www.eff.org/issues/dmca |website=Electronic Frontier Foundation |access-date=5 April 2026}}&amp;lt;/ref&amp;gt; On Section 512, the EFF defends the existence of safe harbors as essential to the internet&#039;s functioning but criticizes the abuse of the takedown system by corporations seeking to silence speech.&amp;lt;!-- CITATION NEEDED: specific EFF blog post or legal filing on 512(f) enforcement and takedown abuse --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===iFixit &amp;amp; the Repair Association===&lt;br /&gt;
&lt;br /&gt;
For hardware repair advocates, the DMCA is a tool for corporate monopolization through software locks. Because modern devices run software, manufacturers can use Section 1201 digital locks to prevent independent shops &amp;amp; owners from fixing their own property.&amp;lt;!-- CITATION NEEDED: iFixit blog post or repair.org publication on Section 1201 and repair restrictions --&amp;gt; [[John Deere]] has been a prominent example: the Foundation for American Innovation documented how the company uses copyright law to prevent farmers from repairing their own tractors.&amp;lt;ref&amp;gt;{{Cite web |title=How John Deere Hijacked Copyright Law To Keep You From Tinkering With Your Tractor |url=https://www.thefai.org/posts/how-john-deere-hijacked-copyright-law-to-keep-you-from-tinkering-with-your-tractor |last=Hogg |first=Luke |date=8 January 2024 |website=Foundation for American Innovation |access-date=5 April 2026}}&amp;lt;/ref&amp;gt; Kyle Wiens, CEO of iFixit, testified before the House Judiciary Subcommittee on Courts, Intellectual Property, and the Internet on July 18, 2023, describing the triennial exemption process as requiring citizens to spend tens of thousands of dollars in legal fees every three years to request permission to repair their own equipment.&amp;lt;!-- CITATION NEEDED: judiciary.house.gov hearing page for Kyle Wiens July 18, 2023 testimony --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Public Knowledge===&lt;br /&gt;
&lt;br /&gt;
Critics of the triennial rulemaking process have called it a &amp;quot;Rube Goldberg contraption&amp;quot; that cannot keep pace with technological change.&amp;lt;!-- CITATION NEEDED: Re:Create Coalition press release, October 2015, or other primary source for &amp;quot;Rube Goldberg contraption&amp;quot; quote originally attributed to Adam Eisgrau of the American Library Association --&amp;gt; Public Knowledge opposed the SMART Copyright Act, warning that giving the Copyright Office the power to mandate internet-wide upload filtering would endanger free expression &amp;amp; internet infrastructure.&lt;br /&gt;
&lt;br /&gt;
==Reform proposals==&lt;br /&gt;
&lt;br /&gt;
===Section 1201 reform===&lt;br /&gt;
&lt;br /&gt;
Multiple bills have sought to reform the anti-circumvention provisions. None have passed. The &#039;&#039;&#039;Unlocking Technology Act&#039;&#039;&#039; (H.R. 1892, 113th Congress; H.R. 1587, 114th Congress&amp;lt;!-- CITATION NEEDED: congress.gov for H.R. 1587 (114th Congress) --&amp;gt;), introduced by Rep. Zoe Lofgren (D-CA) with Rep. Thomas Massie (R-KY) as original cosponsor, would have made circumvention illegal only when tied to actual copyright infringement &amp;amp; legalized distribution of tools for non-infringing uses. Both versions died in committee.&amp;lt;ref&amp;gt;{{Cite web |title=H.R.1892 - Unlocking Technology Act of 2013 |url=https://www.congress.gov/bill/113th-congress/house-bill/1892 |website=Congress.gov |access-date=5 April 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sen. Ron Wyden (D-OR) introduced the &#039;&#039;&#039;Breaking Down Barriers to Innovation Act&#039;&#039;&#039; (S. 990, 114th Congress), which would have automatically renewed triennial exemptions &amp;amp; expanded protections for security research, repair, &amp;amp; accessibility. Rep. Jared Polis (D-CO) introduced a companion bill, H.R. 1883, in the House.&amp;lt;!-- CITATION NEEDED: congress.gov for H.R. 1883 (114th Congress) --&amp;gt; Both died in committee.&amp;lt;ref&amp;gt;{{Cite web |title=S.990 - Breaking Down Barriers to Innovation Act of 2015 |url=https://www.congress.gov/bill/114th-congress/senate-bill/990 |website=Congress.gov |access-date=5 April 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Rep. Mondaire Jones (D-NY), with Rep. Victoria Spartz (R-IN) as original cosponsor, introduced the &#039;&#039;&#039;Freedom to Repair Act&#039;&#039;&#039; (H.R. 6566, 117th Congress), which would have exempted circumvention for repair &amp;amp; permitted trafficking in repair tools. It died in committee.&amp;lt;ref&amp;gt;{{Cite web |title=H.R.6566 - Freedom to Repair Act |url=https://www.congress.gov/bill/117th-congress/house-bill/6566 |website=Congress.gov |access-date=5 April 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The only legislative success has been the &#039;&#039;&#039;Unlocking Consumer Choice and Wireless Competition Act of 2014&#039;&#039;&#039;, which restored the phone unlocking exemption after the Copyright Office revoked it in 2012 &amp;amp; uniquely allowed third-party unlocking assistance.&amp;lt;ref&amp;gt;Pub. L. 113-144, Unlocking Consumer Choice and Wireless Competition Act (2014).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Section 512 reform===&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;SMART Copyright Act&#039;&#039;&#039; (S. 3880, 117th Congress), introduced by Sen. Thom Tillis (R-NC) &amp;amp; Sen. Patrick Leahy (D-VT), moved in the opposite direction from 1201 reform bills. It would have mandated &amp;quot;Standard Technical Measures&amp;quot; that platforms must accommodate to retain safe harbor, effectively requiring government-approved upload filtering. Digital rights groups, startups, &amp;amp; library associations opposed it. It died in committee.&amp;lt;ref&amp;gt;{{Cite web |title=S. 3880 - SMART Copyright Act of 2022 |url=https://www.congress.gov/bill/117th-congress/senate-bill/3880 |website=Congress.gov |access-date=5 April 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;CASE Act&#039;&#039;&#039;, passed on December 27, 2020, as part of the Consolidated Appropriations Act of 2021, created the Copyright Claims Board (CCB), a voluntary small-claims tribunal within the Copyright Office for copyright disputes capped at $30,000 in damages.&amp;lt;ref&amp;gt;Pub. L. 116-260, Title II, Subtitle B (Copyright Alternative in Small-Claims Enforcement Act of 2020).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===State workarounds===&lt;br /&gt;
&lt;br /&gt;
State law cannot override federal copyright law, so state [[right to repair]] bills work around Section 1201 by requiring manufacturers to bypass their own locks rather than authorizing consumers to do so. Colorado&#039;s HB22-1031 (2022) requires powered wheelchair manufacturers to provide repair tools, passwords, &amp;amp; documentation needed for repair.&amp;lt;ref&amp;gt;Colorado HB22-1031 (2022).&amp;lt;/ref&amp;gt; Oregon&#039;s SB 1596 banned [[part pairing]] entirely, prohibiting manufacturers from using software locks to disable non-OEM replacement parts.&amp;lt;ref&amp;gt;Oregon SB 1596 (2024).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Executive actions===&lt;br /&gt;
&lt;br /&gt;
President Biden&#039;s July 2021 Executive Order on Promoting Competition directed the [[Federal Trade Commission]] (FTC) to draft rules preventing manufacturer repair restrictions.&amp;lt;ref&amp;gt;Executive Order 14036, &#039;&#039;Promoting Competition in the American Economy&#039;&#039; (July 9, 2021).&amp;lt;/ref&amp;gt; The FTC&#039;s May 2021 &#039;&#039;Nixing the Fix&#039;&#039; report examined anti-competitive repair restrictions &amp;amp; noted Congressional concern about their impact on consumers&#039; rights under the [[Magnuson-Moss Warranty Act]]. The FTC stated it &amp;quot;stands ready to work with lawmakers&amp;quot; on repair restriction enforcement.&amp;lt;ref&amp;gt;{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |url=https://www.ftc.gov/reports/nixing-fix-ftc-report-congress-repair-restrictions |website=Federal Trade Commission |date=May 2021 |access-date=5 April 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Industry lobbying==&lt;br /&gt;
&lt;br /&gt;
The Recording Industry Association of America (RIAA) has spent millions annually on lobbying since 1998.&amp;lt;!-- figures unverifiable from JS-rendered source --&amp;gt;&amp;lt;ref name=&amp;quot;opensecrets&amp;quot;&amp;gt;{{Cite web |title=Lobbying Profile: Recording Industry Assn of America |url=https://www.opensecrets.org/orgs/recording-industry-assn-of-america/lobbying?id=D000000581 |website=OpenSecrets |access-date=5 April 2026}}&amp;lt;/ref&amp;gt; The Entertainment Software Association (ESA) reported $4.83 million in federal lobbying in 2012&amp;lt;!-- CITATION NEEDED: gamesindustry.biz or OpenSecrets ESA lobbying page for ESA 2012 lobbying figure --&amp;gt; &amp;amp; has consistently opposed game preservation exemptions that would allow remote access to archived titles.&amp;lt;!-- CITATION NEEDED: news coverage of ESA opposition to game preservation exemptions --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A documented revolving door exists between the Copyright Office &amp;amp; copyright industry groups. Karyn Temple went from the RIAA&#039;s litigation department to Register of Copyrights, then to General Counsel of the Motion Picture Association (MPA).&amp;lt;!-- CITATION NEEDED: MPA website (motionpictures.org) or columbia.edu bio for Karyn Temple career path --&amp;gt; Maria Pallante went from Register of Copyrights to President and CEO of the Association of American Publishers.&amp;lt;!-- CITATION NEEDED: publishers.org or copyrightsociety.org for Maria Pallante career path --&amp;gt; Former Senator Chris Dodd became Chairman and CEO of the MPAA after leaving the Senate.&amp;lt;!-- CITATION NEEDED: news coverage (Screen Daily, LAist, or Variety) for Chris Dodd career path --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==DMCA outside of the United States==&lt;br /&gt;
DMCA is implementation of two [[wikipedia:World Intellectual Property Organization|World Intellectual Property Organization (WIPO)]] &amp;quot;internet treaties&amp;quot;: [[wikipedia:WIPO Copyright Treaty|WIPO Copyright Treaty]] and [[wikipedia:WIPO Performances and Phonograms Treaty|WIPO Performances and Phonograms Treaty]]. As of August 2023, the treaties have 115 and 112 contracting parties, respectively.&lt;br /&gt;
&lt;br /&gt;
[[European Union]] Directives which largely cover the subject matter of the treaty are:&lt;br /&gt;
* Directive 91/250/EC, creating copyright protection for software&lt;br /&gt;
* Directive 96/9/EC on copyright protection for databases&lt;br /&gt;
* Directive 2001/29/EC, prohibiting devices for circumventing &amp;quot;technical protection measures&amp;quot;, such as digital rights management (also known as DRM) &lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[DMCA Section 1201]]&lt;br /&gt;
*[[Right to repair]]&lt;br /&gt;
*[[Right to own]]&lt;br /&gt;
*[[Part pairing]]&lt;br /&gt;
*[[Digital rights management]]&lt;br /&gt;
*[[Feature ransom]]&lt;br /&gt;
*[[Discontinuation bricking]]&lt;br /&gt;
*[[Planned obsolescence]]&lt;br /&gt;
*[[Magnuson-Moss Warranty Act]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Legislation]]&lt;br /&gt;
[[Category:International legislation]]&lt;br /&gt;
[[Category:American legislation]]&lt;br /&gt;
[[Category:Digital rights management]]&lt;/div&gt;</summary>
		<author><name>Iii</name></author>
	</entry>
</feed>