<?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=Tracerneo</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=Tracerneo"/>
	<link rel="alternate" type="text/html" href="https://consumerrights.wiki/w/Special:Contributions/Tracerneo"/>
	<updated>2026-06-28T19:32:34Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Microsoft_Office_2019_and_2021_for_Mac_view-only_conversion_(2026)&amp;diff=56108</id>
		<title>Microsoft Office 2019 and 2021 for Mac view-only conversion (2026)</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Microsoft_Office_2019_and_2021_for_Mac_view-only_conversion_(2026)&amp;diff=56108"/>
		<updated>2026-06-04T16:17:35Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat, link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{IncidentCargo&lt;br /&gt;
|Company=Microsoft&lt;br /&gt;
|Product=Office 2019 for Mac; Office 2021 for Mac&lt;br /&gt;
|StartDate=2026-05-14&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=Scheduled&lt;br /&gt;
|Description=July 13, 2026 certificate expiry converts perpetual Office 2019 &amp;amp; 2021 for Mac to view-only after Microsoft&#039;s 2023 &#039;continue to function&#039; promise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Microsoft Office 2019 and 2021 for Mac view-only conversion (2026)&#039;&#039;&#039; is a scheduled remote degradation of perpetually-licensed [[Microsoft Office 2019 for Mac|Microsoft Office software for macOS and iOS]], set for July 13, 2026 when a license-validation certificate used by the Office apps expires.&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot;&amp;gt;{{Cite web |url=https://learn.microsoft.com/en-us/microsoft-365-apps/mac/certificate-update-mac-ios |title=Certificate update for Microsoft 365 apps on managed macOS and iOS devices |website=Microsoft Learn |publisher=Microsoft |date=2026-05-14 |access-date=2026-05-29}}&amp;lt;/ref&amp;gt; After Office 2019 for Mac reached end of support in October 2023, Microsoft assured customers their installed apps would &#039;&#039;&amp;quot;continue to function.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;ms-eos-archive&amp;quot;&amp;gt;{{Cite web |url=https://support.microsoft.com/en-us/office/end-of-support-for-office-2019-for-mac-f2cbba0a-0773-4b2c-b417-b20b5bb2c757 |title=End of support for Office 2019 for Mac |website=Microsoft Support |publisher=Microsoft |archive-url=https://web.archive.org/web/20230603010125/https://support.microsoft.com/en-us/office/end-of-support-for-office-2019-for-mac-f2cbba0a-0773-4b2c-b417-b20b5bb2c757 |archive-date=2023-06-03 |access-date=2026-05-30 |url-status=live}}&amp;lt;/ref&amp;gt; The July 13, 2026 conversion instead drops the apps into a Microsoft-defined &#039;&#039;&amp;quot;reduced functionality mode,&amp;quot;&#039;&#039; in which files can be opened and viewed but not edited or saved.&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;ms-support&amp;quot;&amp;gt;{{Cite web |url=https://support.microsoft.com/en-us/office/update-microsoft-365-or-office-on-your-macos-or-ios-device-f418ae5d-bb5f-4078-b3d9-9340f5dd084e |title=Update Microsoft 365 or Office on your macOS or iOS device |website=Microsoft Support |publisher=Microsoft |date=May 2026 |access-date=2026-05-29}}&amp;lt;/ref&amp;gt; By May 30, 2026, the original 2023 end-of-support page had been re-dated and rewritten on Microsoft&#039;s site; the &#039;&#039;&amp;quot;continue to function&amp;quot;&#039;&#039; clause was removed.&amp;lt;ref name=&amp;quot;ms-eos-live&amp;quot;&amp;gt;{{Cite web |url=https://support.microsoft.com/en-us/office/end-of-support-for-office-2019-for-mac-f2cbba0a-0773-4b2c-b417-b20b5bb2c757 |title=End of support for Office 2019 for Mac |website=Microsoft Support |publisher=Microsoft |access-date=2026-05-30}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;ms-eos-archive&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
Microsoft announced general availability of Office 2019 for Windows and Mac on September 24, 2018. In the launch blog post, Microsoft&#039;s Jared Spataro wrote that &#039;&#039;&amp;quot;Office 2019 is a one-time release and won&#039;t receive future feature updates,&amp;quot;&#039;&#039; positioning the product as the on-premises alternative to the Office 365 subscription.&amp;lt;ref name=&amp;quot;ms-blog-2018&amp;quot;&amp;gt;{{Cite web |url=https://www.microsoft.com/en-us/microsoft-365/blog/2018/09/24/office-2019-is-now-available-for-windows-and-mac/ |title=Office 2019 is now available for Windows and Mac |last=Spataro |first=Jared |website=Microsoft 365 Blog |publisher=Microsoft |date=2018-09-24 |access-date=2026-05-29}}&amp;lt;/ref&amp;gt; Contemporary Microsoft Store pages marketed Office Home &amp;amp; Student 2019 as a &#039;&#039;&amp;quot;One-time purchase for 1 PC or Mac&amp;quot;&#039;&#039; at $149.99, with copy that explicitly contrasted the perpetual product against the Office 365 subscription model: &#039;&#039;&amp;quot;One-time purchases don&#039;t have an upgrade option, which means if you plan to upgrade to the next major release, you&#039;ll have to buy it at full price.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;wayback-2019-product&amp;quot;&amp;gt;{{Cite web |url=https://www.microsoft.com/en-us/p/office-home-student-2019/cfq7ttc0k7c8 |title=Buy Office Home &amp;amp; Student 2019 |website=Microsoft Store |publisher=Microsoft |archive-url=https://web.archive.org/web/20200105214853/https://www.microsoft.com/en-us/p/office-home-student-2019/cfq7ttc0k7c8 |archive-date=2020-01-05 |access-date=2026-05-29 |url-status=dead}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Office 2021 for Mac became generally available on October 5, 2021 under the same one-time-purchase model &amp;amp; is scheduled to reach end of support on October 13, 2026 per the Microsoft Lifecycle Policy.&amp;lt;ref name=&amp;quot;ms-lifecycle-2021&amp;quot;&amp;gt;{{Cite web |url=https://learn.microsoft.com/en-us/lifecycle/products/office-2021 |title=Office 2021 - Microsoft Lifecycle |website=Microsoft Learn |publisher=Microsoft |access-date=2026-05-29}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Office 2019 for Mac reached end of support on October 10, 2023.&amp;lt;ref name=&amp;quot;ms-support&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Microsoft&#039;s edited end-of-support assurance ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery mode=&amp;quot;packed&amp;quot; heights=&amp;quot;220px&amp;quot; caption=&amp;quot;Microsoft&#039;s end-of-support page for Office 2019 for Mac, before and after the 2026 edit&amp;quot;&amp;gt;&lt;br /&gt;
File:MS Office 2019 EOS page archived 2023.png|Internet Archive snapshot of the page from June 3, 2023; originally published April 12, 2023.&amp;lt;ref name=&amp;quot;ms-eos-archive&amp;quot; /&amp;gt;&lt;br /&gt;
File:MS Office 2019 EOS page live 2026-05-30.png|The same Microsoft URL captured on May 30, 2026, re-dated &#039;&#039;Published: May 15th, 2026&#039;&#039;.&amp;lt;ref name=&amp;quot;ms-eos-live&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The June 3, 2023 snapshot of Microsoft&#039;s end-of-support page contained this passage:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&#039;&#039;Support for Office 2019 for Mac will end on October 10, 2023. Rest assured that all your Office 2019 apps will continue to function—they won&#039;t disappear from your Mac, nor will you lose any data. However, you could expose yourself to serious and potentially harmful security risks.&#039;&#039;&amp;lt;ref name=&amp;quot;ms-eos-archive&amp;quot; /&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By May 30, 2026, the same URL carried a new publication date of &#039;&#039;May 15th, 2026&#039;&#039; and a shorter passage:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&#039;&#039;Support for Office 2019 for Mac ended on October 10, 2023. Rest assured that all your Office 2019 apps won&#039;t lose any data. Your data can be accessed on any supported Microsoft 365 or Office product. However, you could expose yourself to serious and potentially harmful security risks.&#039;&#039;&amp;lt;ref name=&amp;quot;ms-eos-live&amp;quot; /&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The 2023 assurance that the apps would &#039;&#039;&amp;quot;continue to function&amp;quot;&#039;&#039; was removed; the data-safety clause was kept; a new sentence pointing owners to &#039;&#039;&amp;quot;any supported Microsoft 365 or Office product&amp;quot;&#039;&#039; was added.&amp;lt;ref name=&amp;quot;ms-eos-archive&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;ms-eos-live&amp;quot; /&amp;gt; The 2023 wording was resurfaced in May 2026 by JimmyTech, a San Francisco IT consultancy, which characterized the July 2026 conversion as Microsoft &#039;&#039;&amp;quot;breaking that promise.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;jimmytech&amp;quot;&amp;gt;{{Cite web |url=https://jimmytechsf.com/blog/office-2019-mac-disabled-july-2026 |title=Microsoft is disabling Office 2019 for Mac on July 13, 2026 |last=Obomsawin |first=Jimmy |website=JimmyTech |date=2026-05-21 |access-date=2026-05-29}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Certificate expiry mechanism ==&lt;br /&gt;
&lt;br /&gt;
Microsoft&#039;s administrator documentation states that &#039;&#039;&amp;quot;Microsoft 365 apps use a digital certificate to validate licensing. The certificate currently in use expires on July 13, 2026. Apps that are updated to the minimum required versions already include the renewed certificate and continue to function normally. Apps on older versions enter reduced functionality mode after the certificate expires.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot; /&amp;gt; The minimum required builds are version 16.83 on macOS and version 2.93 on iOS, &amp;amp; those builds in turn require macOS 12 (Monterey) or later, or iOS 17.0 or later.&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Office 2019 has no fix. The product line is bounded by a hard build cap below the 16.83 threshold, and Microsoft&#039;s own support documentation states the issue &#039;&#039;&amp;quot;cannot be resolved by updating or reinstalling Office 2019 for Mac.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;ms-support&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;jimmytech&amp;quot; /&amp;gt; Office 2021 for Mac, by contrast, is still receiving updates through its October 13, 2026 retirement date &amp;amp; can reach 16.83 on supported macOS versions.&amp;lt;ref name=&amp;quot;ms-lifecycle-2021&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;ms-support&amp;quot; /&amp;gt; Windows and Android versions of Office are not affected by the certificate expiry.&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Reduced functionality mode ==&lt;br /&gt;
&lt;br /&gt;
After July 13, 2026, affected installs of Word, Excel, PowerPoint, Outlook, and OneNote on Mac, iPhone, and iPad will enter reduced functionality mode, in which Microsoft says users &#039;&#039;&amp;quot;can open and view files but can&#039;t edit, save, or access full features.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot; /&amp;gt; Office 2021 for Mac and Microsoft 365 for Mac users on macOS 12 (Monterey) or later can avoid the conversion by updating to build 16.83.&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot; /&amp;gt; Office 2019 for Mac users have no update path.&amp;lt;ref name=&amp;quot;ms-support&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== May 2026 customer notification ==&lt;br /&gt;
&lt;br /&gt;
Microsoft began emailing affected customers in mid-May 2026 about the upcoming change.&amp;lt;ref name=&amp;quot;jimmytech&amp;quot; /&amp;gt; PiunikaWeb, which published the earliest press coverage on May 16, 2026, characterized the user response as &#039;&#039;&amp;quot;largely negative.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;piunikaweb&amp;quot;&amp;gt;{{Cite web |url=https://piunikaweb.com/2026/05/16/microsoft-apps-older-versions-read-only/ |title=Using an older Apple device? Microsoft Office is taking away editing features soon |last=K |first=Sudhanshu |website=PiunikaWeb |date=2026-05-16 |access-date=2026-05-29}}&amp;lt;/ref&amp;gt; The email included an offer of a free Microsoft 365 Personal trial that requires a payment method and converts to a paid subscription if not cancelled.&amp;lt;ref name=&amp;quot;ms-support&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;piunikaweb&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Microsoft&#039;s response ==&lt;br /&gt;
&lt;br /&gt;
Microsoft directs affected users to three options: continuing to use the apps in view-only mode, switching to the free [[Microsoft 365]] web apps, or paying for a Microsoft 365 subscription or a new perpetual Office Home 2024 license.&amp;lt;ref name=&amp;quot;ms-support&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;ms-learn-cert&amp;quot; /&amp;gt; Microsoft has issued no public statement reconciling the July 2026 conversion with the 2023 &#039;&#039;&amp;quot;continue to function&amp;quot;&#039;&#039; assurance.&amp;lt;ref name=&amp;quot;ms-eos-archive&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Consumer response ==&lt;br /&gt;
&lt;br /&gt;
AppleInsider&#039;s Amber Neely, in a May 28, 2026 article, wrote that Microsoft &#039;&#039;&amp;quot;will be effectively bricking the standalone Office 2019 for Mac, iPad, and iPhone users on July 13, 2026.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;appleinsider&amp;quot;&amp;gt;{{Cite web |url=https://appleinsider.com/articles/26/05/28/microsoft-is-killing-office-2019-for-mac-and-iphone-and-you-cant-do-much-about-it |title=Microsoft is killing Office 2019 for Mac and iPhone, and you can&#039;t do much about it |last=Neely |first=Amber |website=AppleInsider |date=2026-05-28 |access-date=2026-05-29}}&amp;lt;/ref&amp;gt; JimmyTech framed the choice as discretionary:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&#039;&#039;But certificates can get renewed. The fact that Microsoft is using this expiration as a deadline that retires older versions of Office, rather than quietly renewing the certificate, is a choice.&#039;&#039;&amp;lt;/blockquote&amp;gt;&amp;lt;ref name=&amp;quot;jimmytech&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TidBITS Talk and PiunikaWeb commenters discussed migrating to LibreOffice, OnlyOffice, and Apple&#039;s Pages.&amp;lt;ref name=&amp;quot;tidbits-talk&amp;quot;&amp;gt;{{Cite web |url=https://talk.tidbits.com/t/office-2019-switching-to-view-only-mode-what-to-do/33495 |title=Office 2019 switching to view-only mode, what to do? |website=TidBITS Talk |date=2026-05-16 |access-date=2026-05-29}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;piunikaweb&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
* [[Microsoft]]&lt;br /&gt;
* [[Microsoft 365]]&lt;br /&gt;
* [[Adobe Creative Suite activation]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Microsoft Office]]&lt;br /&gt;
[[Category:Planned obsolescence]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Template:Main_Page/Consumer_Tools&amp;diff=55666</id>
		<title>Template:Main Page/Consumer Tools</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Template:Main_Page/Consumer_Tools&amp;diff=55666"/>
		<updated>2026-06-02T14:53:00Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: fix&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- whitespace needed for correct rendering --&amp;gt;&lt;br /&gt;
=====Ad &amp;amp; tracking blockers=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://pi-hole.net/ Pi-hole] – Self-hosted network-based ad blocker.&lt;br /&gt;
* [https://github.com/gorhill/uBlock uBlock Origin] – Efficient browser-based ad and tracker blocker.&lt;br /&gt;
* [https://adnauseam.io/ Adnauseum] - Browser-based ad and tracker blocker built off of uBlock Origin that also clicks ads to obscure your digital fingerprint.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Anti-scam resources=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://haveibeenpwned.com/ Have I Been Pwned] – Check if your email/password was exposed in a breach.&lt;br /&gt;
* [https://www.consumerfinance.gov/ CFPB] – File complaints and view alerts about financial services.&lt;br /&gt;
* [https://virustotal.com/ VirusTotal] / [https://hybrid-analysis.com Hybrid Analysis] – Scan files for potential malware.&lt;br /&gt;
* [https://tria.ge/ Triage] – Online sandbox for analyzing executables.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Archival tools=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://archive.org Wayback Machine] – World&#039;s largest internet archival service&lt;br /&gt;
* [https://ghostarchive.org/ Ghost Archive] – Secondary archival service.&lt;br /&gt;
* [https://megalodon.jp/ Megalodon] – Secondary, Japanese archival service. Can archive YouTube comments.&lt;br /&gt;
* [https://preservetube.com/ PreserveTube] – Specifically for archiving YouTube videos.&lt;br /&gt;
* [https://www.getsinglefile.com/ SingleFile] – Browser extension to save website EULA/privacy policy as html locally&lt;br /&gt;
* [http://archivebox.io/ ArchiveBox] – Self-hosted website archival tool&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Corporate accountability &amp;amp; recalls=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.bbb.org/ Better Business Bureau (BBB)] – Lookup business complaints and file your own.&lt;br /&gt;
* [https://www.saferproducts.gov/ SaferProducts.gov] – U.S. product recall and complaint site.&lt;br /&gt;
* [https://www.fda.gov/safety/recalls-market-withdrawals-safety-alerts FDA Recalls] – Drug and food recall database.&lt;br /&gt;
* [https://ec.europa.eu/safety-gate/#/screen/home Safety Gate] – [[European Union|EU]] product recall and report site.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Legal &amp;amp; complaint filing=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.consumerreports.org/ Consumer Reports] – Independent product reviews and ratings.&lt;br /&gt;
* [https://www.ripoffreport.com/ Ripoff Report] – Public consumer complaint database.&lt;br /&gt;
* [https://www.classaction.org/ ClassAction.org] – View or join consumer class-action lawsuits.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Repair &amp;amp; Open designs=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.ifixit.com iFixit] – Open repository of device repair instructions.&lt;br /&gt;
* [https://www.opensourceecology.org/gvcs/gvcs-machine-index/ Open Source Ecology] – Open source machinery designs.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Price &amp;amp; product transparency=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://camelcamelcamel.com/ CamelCamelCamel] – Amazon price tracker to detect deceptive price drops.&lt;br /&gt;
* [https://keepa.com/ Keepa] – Detailed price history and deals on Amazon products.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Privacy &amp;amp; surveillance tools=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://simpleoptout.com/ SimpleOptOut] – Direct links to opt out of data brokers.&lt;br /&gt;
* &#039;&#039;&#039;[$]&#039;&#039;&#039; &#039;&#039;[https://easyoptouts.com/ EasyOptOuts]&#039;&#039; – Automated data broker opt-out service.&lt;br /&gt;
* [https://exodus-privacy.eu.org/en/ Exodus Privacy] - Analyzes privacy concerns in Android applications. Discover unwanted permissions and tracking libraries in common apps.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Subscription &amp;amp; dark pattern tracking=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.asktrim.com/ Trim] – Finds and cancels unwanted subscriptions.&lt;br /&gt;
* &#039;&#039;&#039;[$]&#039;&#039;&#039; &#039;&#039;[https://goodbudget.com Goodbudget]&#039;&#039; – Budgeting app with debt tracker.&lt;br /&gt;
* [https://tosdr.org/ Terms of Service; Didn&#039;t Read] / [https://privacyspy.org/ PrivacySpy] – Summarizes privacy policies and rates companies by trustworthiness.&lt;br /&gt;
* [https://www.deceptive.design/ Deceptive Design] – Defines, identifies, and catalogs dark patterns and deceptive design practices in various software and services.&lt;br /&gt;
* [https://www.darkpattern.games/ Dark Pattern Games] – A game review website devoted to helping you find games that don&#039;t use psychological tricks to manipulate you into becoming an addicted gamer.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;&#039;&#039;&#039;[$]&#039;&#039;&#039; – paid service, subscription needed&amp;lt;/small&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Template:Main_Page/Consumer_Tools&amp;diff=55665</id>
		<title>Template:Main Page/Consumer Tools</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Template:Main_Page/Consumer_Tools&amp;diff=55665"/>
		<updated>2026-06-02T14:51:55Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: Convert to headings, unbulleted lists, mark paid services in more compact way&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=====Ad &amp;amp; tracking blockers=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://pi-hole.net/ Pi-hole] – Self-hosted network-based ad blocker.&lt;br /&gt;
* [https://github.com/gorhill/uBlock uBlock Origin] – Efficient browser-based ad and tracker blocker.&lt;br /&gt;
* [https://adnauseam.io/ Adnauseum] - Browser-based ad and tracker blocker built off of uBlock Origin that also clicks ads to obscure your digital fingerprint.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Anti-scam resources=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://haveibeenpwned.com/ Have I Been Pwned] – Check if your email/password was exposed in a breach.&lt;br /&gt;
* [https://www.consumerfinance.gov/ CFPB] – File complaints and view alerts about financial services.&lt;br /&gt;
* [https://virustotal.com/ VirusTotal] / [https://hybrid-analysis.com Hybrid Analysis] – Scan files for potential malware.&lt;br /&gt;
* [https://tria.ge/ Triage] – Online sandbox for analyzing executables.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Archival tools=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://archive.org Wayback Machine] – World&#039;s largest internet archival service&lt;br /&gt;
* [https://ghostarchive.org/ Ghost Archive] – Secondary archival service.&lt;br /&gt;
* [https://megalodon.jp/ Megalodon] – Secondary, Japanese archival service. Can archive YouTube comments.&lt;br /&gt;
* [https://preservetube.com/ PreserveTube] – Specifically for archiving YouTube videos.&lt;br /&gt;
* [https://www.getsinglefile.com/ SingleFile] – Browser extension to save website EULA/privacy policy as html locally&lt;br /&gt;
* [http://archivebox.io/ ArchiveBox] – Self-hosted website archival tool&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Corporate accountability &amp;amp; recalls=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.bbb.org/ Better Business Bureau (BBB)] – Lookup business complaints and file your own.&lt;br /&gt;
* [https://www.saferproducts.gov/ SaferProducts.gov] – U.S. product recall and complaint site.&lt;br /&gt;
* [https://www.fda.gov/safety/recalls-market-withdrawals-safety-alerts FDA Recalls] – Drug and food recall database.&lt;br /&gt;
* [https://ec.europa.eu/safety-gate/#/screen/home Safety Gate] – [[European Union|EU]] product recall and report site.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Legal &amp;amp; complaint filing=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.consumerreports.org/ Consumer Reports] – Independent product reviews and ratings.&lt;br /&gt;
* [https://www.ripoffreport.com/ Ripoff Report] – Public consumer complaint database.&lt;br /&gt;
* [https://www.classaction.org/ ClassAction.org] – View or join consumer class-action lawsuits.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Repair &amp;amp; Open designs=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.ifixit.com iFixit] – Open repository of device repair instructions.&lt;br /&gt;
* [https://www.opensourceecology.org/gvcs/gvcs-machine-index/ Open Source Ecology] – Open source machinery designs.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Price &amp;amp; product transparency=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://camelcamelcamel.com/ CamelCamelCamel] – Amazon price tracker to detect deceptive price drops.&lt;br /&gt;
* [https://keepa.com/ Keepa] – Detailed price history and deals on Amazon products.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Privacy &amp;amp; surveillance tools=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://simpleoptout.com/ SimpleOptOut] – Direct links to opt out of data brokers.&lt;br /&gt;
* &#039;&#039;&#039;[$]&#039;&#039;&#039; &#039;&#039;[https://easyoptouts.com/ EasyOptOuts]&#039;&#039; – Automated data broker opt-out service.&lt;br /&gt;
* [https://exodus-privacy.eu.org/en/ Exodus Privacy] - Analyzes privacy concerns in Android applications. Discover unwanted permissions and tracking libraries in common apps.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=====Subscription &amp;amp; dark pattern tracking=====&lt;br /&gt;
{{ubl|&lt;br /&gt;
* [https://www.asktrim.com/ Trim] – Finds and cancels unwanted subscriptions.&lt;br /&gt;
* &#039;&#039;&#039;[$]&#039;&#039;&#039; &#039;&#039;[https://goodbudget.com Goodbudget]&#039;&#039; – Budgeting app with debt tracker.&lt;br /&gt;
* [https://tosdr.org/ Terms of Service; Didn&#039;t Read] / [https://privacyspy.org/ PrivacySpy] – Summarizes privacy policies and rates companies by trustworthiness.&lt;br /&gt;
* [https://www.deceptive.design/ Deceptive Design] – Defines, identifies, and catalogs dark patterns and deceptive design practices in various software and services.&lt;br /&gt;
* [https://www.darkpattern.games/ Dark Pattern Games] – A game review website devoted to helping you find games that don&#039;t use psychological tricks to manipulate you into becoming an addicted gamer.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;&#039;&#039;&#039;[$]&#039;&#039;&#039; – paid service, subscription needed&amp;lt;/small&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Template:Ubl&amp;diff=55662</id>
		<title>Template:Ubl</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Template:Ubl&amp;diff=55662"/>
		<updated>2026-06-02T14:45:21Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: ubl → Unbulleted list&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Template:Unbulleted list]]&lt;br /&gt;
&lt;br /&gt;
{{Rcat shell|&lt;br /&gt;
{{R from template shortcut}}&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Template:Unbulleted_list&amp;diff=55659</id>
		<title>Template:Unbulleted list</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Template:Unbulleted_list&amp;diff=55659"/>
		<updated>2026-06-02T14:43:59Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: Unbulleted list&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{&amp;lt;includeonly&amp;gt;safesubst:&amp;lt;/includeonly&amp;gt;#invoke:list|unbulleted}}&amp;lt;noinclude&amp;gt;&lt;br /&gt;
{{documentation}}&lt;br /&gt;
&amp;lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&amp;gt;&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Anthropic%27s_Claude_Code_source_leak&amp;diff=54943</id>
		<title>Anthropic&#039;s Claude Code source leak</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Anthropic%27s_Claude_Code_source_leak&amp;diff=54943"/>
		<updated>2026-05-27T11:37:36Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: irrelevant?&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{IncidentCargo&lt;br /&gt;
|Company=Anthropic&lt;br /&gt;
|StartDate=2026-03-31&lt;br /&gt;
|Status=Resolved&lt;br /&gt;
|Product=Claude Code&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Type=Source Code, Artificial Intelligence&lt;br /&gt;
|Description=Source code leak&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The proprietary source code of Anthropic’s Claude Code command-line tool was unintentionally exposed in a source map file inside their npm package.&lt;br /&gt;
&lt;br /&gt;
==Claude Code map file references the source code==&lt;br /&gt;
On 31 March 2026, the proprietary source code of Anthropic’s Claude Code command-line tool was unintentionally exposed after version 2.1.88 of the npm package &#039;@anthropic-ai/claude-code&#039; which was released with a source map file &#039;cli.js.map&#039; referencing the fully unobfuscated TypeScript source code, downloadable as a zip from Anthropic&#039;s R2 storage bucket. The leak was identified by Chaofan Shou, security researcher at Solayer Labs.&amp;lt;ref&amp;gt;{{cite web |first=Chaofan |last=Shou |website=X |title=Claude code source code has been leaked via a map file in their npm registry! |url=https://x.com/Fried_rice/status/2038894956459290963 |date=31 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260527101141/https://nitter.catsarch.com/Fried_rice/status/2038894956459290963#m |archive-date=2026-05-27}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
The leak totaled approximately to 1900 files and 512000 lines of code or their terminal GUI and included a draft blog post that detailed upcoming models named &amp;quot;Mythos&amp;quot; and &amp;quot;Capybara&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Copies of the source code have spread rapidly through mirrors and forks on [[GitHub]] and other coding platforms which prompted Anthropic to file takedown requests.&lt;br /&gt;
&lt;br /&gt;
===Anthropic&#039;s response===&lt;br /&gt;
Anthropic emailed a statement on the same day of the incident, categorizing the incident as human error and not a security breach.&amp;lt;ref&amp;gt;{{cite web |first=Shirin |last=Ghaffary |first2=Mark |last2=Anderson |title=Anthropic accidentally leaked thousands of lines of code |url=https://www.latimes.com/business/story/2026-04-01/anthropic-accidentally-leaked-thousands-of-lines-of-code |date=1 Apr 2026 |archive-url=https://web.archive.org/web/20260401185132/https://www.latimes.com/business/story/2026-04-01/anthropic-accidentally-leaked-thousands-of-lines-of-code |archive-date=2026-04-01}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Earlier today, a Claude Code release included some internal source code. No sensitive customer data or credentials were involved or exposed [...] This was a release packaging issue caused by human error, not a security breach.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On 1 April 2026, GitHub reported&amp;lt;ref&amp;gt;{{cite web |website=[[GitHub]] |title=2026-03-31-anthropic.md |url=https://github.com/github/dmca/blob/master/2026/03/2026-03-31-anthropic.md |url-status=live |date=2026-03-31 |archive-url=https://web.archive.org/web/20260401010452/https://github.com/github/dmca/blob/master/2026/03/2026-03-31-anthropic.md |archive-date=2026-04-01}}&amp;lt;/ref&amp;gt; that Anthropic&#039;s takedown request was executed against 8100 repositories, including legitimate forks of Anthropic&#039;s public repositories.&amp;lt;ref&amp;gt;{{cite web |website=TechCrunch |first=Tim |last=Fernholz |title=Anthropic took down thousands of GitHub repos trying to yank its leaked source code — a move the company says was an accident |url=https://techcrunch.com/2026/04/01/anthropic-took-down-thousands-of-github-repos-trying-to-yank-its-leaked-source-code-a-move-the-company-says-was-an-accident/ |url-status=live |date=1 Apr 2026 |archive-url=https://web.archive.org/web/20260401222629/https://techcrunch.com/2026/04/01/anthropic-took-down-thousands-of-github-repos-trying-to-yank-its-leaked-source-code-a-move-the-company-says-was-an-accident/ |archive-date=2026-04-01}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |website=X |first=Robert |last=McLaws |title=Illegitimate DMCA Takedown |url=https://x.com/robertmclaws/status/2039129333428871463 |url-status=live |date=1 Apr 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
Anthropic walked back on the takedown requests due to accidental deletion of legitimate repositories.&amp;lt;ref&amp;gt;{{cite web |first=Boris |last=Cherny |website=X |title=Unintentional takedowns comment |url=https://x.com/bcherny/status/2039426466094731289 |date=1 Apr 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;The repo named in the notice was part of a fork network connected to our own public Claude Code repo, so the takedown reached more repositories than intended [...] We retracted the notice for everything except the one repo we named, and GitHub has restored access to the affected forks.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Irrelevant|no consumer rights implications}}&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Anthropic]]&lt;br /&gt;
*[[ChatGPT]]&lt;br /&gt;
*[[Google Gemini]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Revolut&amp;diff=54786</id>
		<title>Revolut</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Revolut&amp;diff=54786"/>
		<updated>2026-05-25T19:03:52Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: /* App explicitly blocked on Android ROMs claiming data security reasons (2024 - Present): */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Description=Financial technology company known for its free and subscription-based digital banking services&lt;br /&gt;
|Type=Private&lt;br /&gt;
|Category=Digital Banking&lt;br /&gt;
|Company=Revolut Group Holdings Ltd&lt;br /&gt;
|Website=https://revolut.com&lt;br /&gt;
|Industry=Digital Banking&lt;br /&gt;
|Logo=Revolut logo.svg&lt;br /&gt;
|Founded=2015-07-00}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Revolut&#039;&#039;&#039; is a global financial technology company headquartered in London and founded in July 2015 by Nik Storonskiy and  Vlad Yatsenko. As of March 2026, Revolut has over 70 million customers and supports transfers across more than 160 countries and regions. It was valued at $75 billion in November 2025. Its services include bank accounts, debit cards, credit cards, currency exchange, stock trading, cryptocurrency exchange and peer to peer payments.&lt;br /&gt;
&lt;br /&gt;
==Consumer-impact summary==&lt;br /&gt;
&lt;br /&gt;
===Forced app download===&lt;br /&gt;
The web experience cannot be used to make purchases, but only to check account balance, limited transaction history, control cards freezing, PIN lock, and other card security settings. This effectively forces the user to make use of the mobile app.&amp;lt;ref&amp;gt;{{Cite news |last=Gory |first=Colm |date=1 Dec 2020 |title=Revolut launches ‘highly requested’ web app for desktop users |url=https://www.siliconrepublic.com/business/revolut-web-app-desktop-laptop |url-status=live |archive-url=https://web.archive.org/web/20250211014949/https://www.siliconrepublic.com/business/revolut-web-app-desktop-laptop |archive-date=11 Feb 2025 |access-date=27 Mar 2026 |work=Silicon Republic |pages=3}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Freemium with personal data concerns===&lt;br /&gt;
Revolut earns money from subscriptions plans to access extra features. Most prominent being bigger withdrawal limits and travel insurance.&amp;lt;ref&amp;gt;{{Cite web |last=Emmanuel Chijioke |first=Peter |last2=Hipolito |first2=Mirjan |date=10 Feb 2025 |editor-last=Johnson |editor-first=BJ |title=Revolut Fees Review |url=https://tradersunion.com/brokers/digital-banks/view/revolut/fees/ |url-status=live |archive-url=https://web.archive.org/web/20250831230304/https://tradersunion.com/brokers/digital-banks/view/revolut/fees/ |archive-date=31 Aug 2025 |access-date=27 Mar 2026 |website=Traders Union}}&amp;lt;/ref&amp;gt; Regardless of subscription status, Revolut optionally suggests that customers link their bank accounts to &amp;quot;give a complete picture of your spending and saving.&amp;quot; While this access is read-only, it poses serious privacy concerns.&amp;lt;ref&amp;gt;{{Cite web |last=Dunne |first=Eithne |date=14 Mar 2021 |title=Put overspending to bed with a bank syncing app |url=https://www.thetimes.com/business/economics/article/put-overspending-to-bed-with-a-bank-syncing-app-2r85t8kqq |url-status=live |archive-url=https://web.archive.org/web/20251221134625/https://www.thetimes.com/business/economics/article/put-overspending-to-bed-with-a-bank-syncing-app-2r85t8kqq |archive-date=21 Dec 2025 |access-date=27 Mar 2026 |website=The Times and The Sunday Times}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |date=12 Oct 2025 |title=Revolut |url=https://reports.exodus-privacy.eu.org/en/reports/com.revolut.revolut/latest/ |url-status=live |archive-url=https://web.archive.org/web/20251012101646/https://reports.exodus-privacy.eu.org/en/reports/com.revolut.revolut/latest/ |archive-date=12 Oct 2025 |access-date=12 Oct 2025 |website=εxodus}}&amp;lt;/ref&amp;gt; Financial services are required by law to implement extensive Know Your Customer ([[wikipedia:Know_your_customer|KYC]]), but the issue of extracting &#039;&#039;more information than needed&#039;&#039; reflects a broader trend in the digital industry to lure customers into free services where sharing their personal information becomes the revenue strategy, effectively forcing unknowing customers to &amp;quot;pay with their data&amp;quot;.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Batista |first=Hugo |date=18 Apr 2020 |title=Revolut is sharing your data with Facebook. Here’s what you need to know. |url=https://medium.com/swlh/revolut-is-sharing-your-data-with-facebook-heres-what-you-need-to-know-cc511c7ab639 |url-status=live |archive-url=https://web.archive.org/web/20260214222032/https://medium.com/swlh/revolut-is-sharing-your-data-with-facebook-heres-what-you-need-to-know-cc511c7ab639 |archive-date=14 Feb 2026 |access-date=27 Mar 2026 |website=Medium}}&amp;lt;/ref&amp;gt; Data which includes:&lt;br /&gt;
*Phone number&lt;br /&gt;
*Date of birth&lt;br /&gt;
*Email address&lt;br /&gt;
*Full legal name&lt;br /&gt;
*Home address&lt;br /&gt;
*Aircode&lt;br /&gt;
*ID&lt;br /&gt;
*Microphone permissions without disclosure as to why&lt;br /&gt;
&lt;br /&gt;
=====Further data Collected:=====&lt;br /&gt;
&lt;br /&gt;
*&amp;quot;details of the device you use (for example, your phone, computer or tablet)&amp;quot;&lt;br /&gt;
*IP address&lt;br /&gt;
*Browser type and version&lt;br /&gt;
*Time zone setting&lt;br /&gt;
*Device language&lt;br /&gt;
*Operating system and platform&lt;br /&gt;
*Type of device used&lt;br /&gt;
*Whether a virtual private network (VPN) is used&lt;br /&gt;
*A unique device identifier&lt;br /&gt;
*Mobile network information&lt;br /&gt;
*Mobile operating system&lt;br /&gt;
*Type of mobile browser you use&lt;br /&gt;
*Links clicked on the website or Revolut app (including date and time stamp)&lt;br /&gt;
*Length of visits to certain pages&lt;br /&gt;
*Page interaction information (such as scrolling and clicks)&lt;br /&gt;
*Methods used to browse away from the page&lt;br /&gt;
*Types of apps and other metadata about the device&lt;br /&gt;
*Information from devices contacts list&lt;br /&gt;
*Behavioural biometric data&lt;br /&gt;
*Detailed device settings&lt;br /&gt;
*GPS location &amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |date=1 Jan 2025 |title=Revolut Privacy Policy |url=https://www.revolut.com/legal/privacy/ |url-status=live |archive-url=https://web.archive.org/web/20260220102621/https://www.revolut.com/legal/privacy/ |archive-date=20 Feb 2026 |access-date=27 Mar 2026 |website=Revolut}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===App explicitly blocked on Android ROMs claiming data security reasons (&#039;&#039;2024 - Present&#039;&#039;)===&lt;br /&gt;
{{Main|Revolut blocked access for users with custom OS}}&lt;br /&gt;
In November 2024, Revolut pushed an update that removed support to users with custom OS on their device. The change was announced through an in-app message, which was shown after a user tried to log in. The change also affected users whom already had an account and funds at the Company.&lt;br /&gt;
&lt;br /&gt;
===Revolut verify ID email spam===&lt;br /&gt;
{{Main|Revolut verify ID email spam}}&lt;br /&gt;
When a customer does not complete their account setup Revolut sends them 7 emails to pressure them to finish account setup.&lt;br /&gt;
&lt;br /&gt;
===Revolut blocking Lyca Mobile automated payment blocking===&lt;br /&gt;
{{Main|Revolut blocking Lyca Mobile automated payment blocking}}&lt;br /&gt;
Revolut explicitly disables the option to end automated payments to Lyca Mobile&lt;br /&gt;
&lt;br /&gt;
==Repeated failure to prevent fraud==&lt;br /&gt;
Revolut has a repeated history of being one the most frequently named financial institutions in UK fraud complaints.&amp;lt;ref&amp;gt;{{Cite news |date=2024-08-14 |title=‘I lost £165k to fraud in an hour’ - customers say they were let down by Revolut |url=https://www.bbc.com/news/articles/cj6epzxdd77o |url-status=live |archive-url=https://web.archive.org/web/20260217213403/https://www.bbc.com/news/articles/cj6epzxdd77o |archive-date=2026-02-17 |access-date=2026-03-31 |work=BBC}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite news |date=2024-04-24 |title=Revolut fraud complaints to Ombudsman outstrip all banks |url=https://www.which.co.uk/news/article/revolut-fraud-complaints-to-ombudsman-outstrip-all-banks-aNVWh6O36Jfw |url-status=live |archive-url=https://web.archive.org/web/20260304131535/https://www.which.co.uk/news/article/revolut-fraud-complaints-to-ombudsman-outstrip-all-banks-aNVWh6O36Jfw |archive-date=2026-03-04 |access-date=2026-03-31 |work=Which?}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=DRN-4189491 |url=https://www.financial-ombudsman.org.uk/decision/DRN-4189491.pdf |url-status=live |archive-url=https://web.archive.org/web/20250827233450/https://www.financial-ombudsman.org.uk/decision/DRN-4189491.pdf |archive-date=2025-08-27 |access-date=2026-03-31 |website=Financial Ombudsman Service (UK)}}&amp;lt;/ref&amp;gt; The number of complaints of fraud reported to [https://www.reportfraud.police.uk/ Action Fraud], the UK reporting centre for fraud and cybercrime, by Revolut customers rose from 567 in February 2023 to 1,086 for February 2024.&amp;lt;ref&amp;gt;{{Cite news |title=I&#039;m a victim of scammers. But Revolut says &#039;no&#039; to a refund |url=https://www.theguardian.com/money/2024/apr/10/im-a-victim-of-scammers-but-revolut-says-no-to-a-refund |url-status=live |archive-url=https://web.archive.org/web/20251201233704/https://www.theguardian.com/money/2024/apr/10/im-a-victim-of-scammers-but-revolut-says-no-to-a-refund |archive-date=2025-12-01 |access-date=2026-03-31 |work=The Guardian}}&amp;lt;/ref&amp;gt; According to the Financial Ombudsman Service (FOS), it issued 3,458 fraud and scam-related &#039;views&#039; to Revolut and its customers in 2023 surpassing any other provider.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; These issues arose in spite of the efforts in to combat fraud, by doubling the number of employs tasked to deal with the matter between 2021 and 2023.&amp;lt;ref&amp;gt;{{Cite news |date=2023-10-31 |title=Revolut doubles financial crime headcount since 2021 to combat fraud |url=https://www.rte.ie/news/business/2023/1031/1413840-revolut-doubles-financial-crime-headcount-since-2021/ |url-status=live |archive-url=https://web.archive.org/web/20250915090530/https://www.rte.ie/news/business/2023/1031/1413840-revolut-doubles-financial-crime-headcount-since-2021/ |archive-date=2025-09-15 |access-date=2026-03-31 |work=RTE}}&amp;lt;/ref&amp;gt; These issues persisted into 2024 with 3,242 cases escalated by consumers over Authorized Push Payment (APP) fraud&amp;lt;ref&amp;gt;{{Cite web |title=Revolut’s Security Weaknesses and Fraud Reimbursement Failures (2020–Present) |url=https://revolutscamalert.com/revolut-security-and-refund-failures/ |url-status=live |access-date=2026-05-27}}&amp;lt;/ref&amp;gt; and 2025 with 1,875 new cases on Revolut being more than 700 cases ahead of Barclays, this is whilst Revolut serves a significantly smaller customer base of around 12-13 million whilst Barclays serves more than 20 million.&amp;lt;ref&amp;gt;{{Cite news |last=Cavaglieri |first=Chiara |date=2025-10-01 |title=Revolut still the worst UK firm for fraud complaints, warns Which? |url=https://www.which.co.uk/news/article/revolut-still-the-worst-uk-firm-for-fraud-complaints-warns-which-axqr43W94wLn |url-status=live |archive-url=https://web.archive.org/web/20260424055527/https://www.which.co.uk/news/article/revolut-still-the-worst-uk-firm-for-fraud-complaints-warns-which-axqr43W94wLn |archive-date=2026-04-24 |access-date=2026-05-04 |work=Which?}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite news |last=O&#039;Connor |first=Kieran |date=2025-10-02 |title=Rising fraud disputes put Revolut back in the spotlight |url=https://paymentexpert.com/2025/10/02/app-fraud-disputes-revolut-uk/ |url-status=live |archive-date= |access-date=2025-10-02 |work=Payment Expert}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Furthermore these issues spark concerns surrounding the aforementioned extensive data collection&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; not being effective in preventing fraud.&lt;br /&gt;
&lt;br /&gt;
==Poor customer support==&lt;br /&gt;
Whilst a broad trend in most industries, Revolut customer support is widely considered severely lacking. According to users most of the time they are put into a conversation with a bot and even if they manage to get through to a human their issues such as fraud will often be ignored&amp;lt;ref&amp;gt;{{Cite web |date=2026-04-26 |title=Revolut is the absolute pits when something goes wrong |url=https://www.reddit.com/r/ireland/comments/1stx2dg/revolut_is_the_absolute_pits_when_something_goes/ |url-status=live |archive-url=https://web.archive.org/web/20260504081220/https://www.reddit.com/r/ireland/comments/1stx2dg/revolut_is_the_absolute_pits_when_something_goes/?solution=53118598e5ad0f7953118598e5ad0f79&amp;amp;js_challenge=1&amp;amp;token=bbbe4bf1c9a2b5160829c4be34da58617f0226add79df55361ad99316696a63a&amp;amp;jsc_orig_r= |archive-date=2026-05-04 |access-date=2026-05-04 |website=Reddit}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2025-07-01 |title=Revolut acts like they&#039;ll help in public, but will do nothing regardless. This is how they treat their customers. Be warned. |url=https://www.reddit.com/r/Revolut/comments/1m1lq79/revolut_acts_like_theyll_help_in_public_but_will/?solution=0a17fa3c36299e110a17fa3c36299e11&amp;amp;js_challenge=1&amp;amp;token=bbbe4bf1c9a2b5160829c4be34da5861b421f053ed82652cadb23b3e88730080&amp;amp;jsc_orig_r= |url-status=live |access-date=2026-05-27 |website=Reddit}}&amp;lt;/ref&amp;gt; or they will be continuously told to escalate the ticket where this would repeat.&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |date=2025-08-01 |title=Has anyone had bad experiences with Revolut? |url=https://www.reddit.com/r/CasualIreland/comments/1nbsmnu/has_anyone_had_bad_experiences_with_revolut/ |url-status=live |archive-url=https://web.archive.org/web/20260504075218/https://www.reddit.com/r/CasualIreland/comments/1nbsmnu/has_anyone_had_bad_experiences_with_revolut/?solution=36349442c3f7bef136349442c3f7bef1&amp;amp;js_challenge=1&amp;amp;token=bbbe4bf1c9a2b5160829c4be34da58616e08d8168d7144b1cca4aef7f2b3d72f&amp;amp;jsc_orig_r= |archive-date=2026-05-04 |access-date=2026-05-04 |website=Reddit}}&amp;lt;/ref&amp;gt; In some cases customers claimed that support would poorly handle procedures such as transferring car insurance to another vehicle reportedly &amp;quot;two weeks after [the customer] returned it.&amp;quot;&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Chase Bank]]&lt;br /&gt;
*[[PayPal]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_asserts_the_right_to_seize_phones_during_repairs&amp;diff=54778</id>
		<title>Google asserts the right to seize phones during repairs</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_asserts_the_right_to_seize_phones_during_repairs&amp;diff=54778"/>
		<updated>2026-05-25T13:29:15Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Irrelevant}}&lt;br /&gt;
{{IncidentCargo&lt;br /&gt;
|Company=&lt;br /&gt;
|StartDate=&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|Product=&lt;br /&gt;
|ArticleType=&lt;br /&gt;
|Type=&lt;br /&gt;
|Description=&lt;br /&gt;
}}&lt;br /&gt;
==Google device repair program restrictions==&lt;br /&gt;
&lt;br /&gt;
Google&#039;s self-repair program contains contractual requirements that raise concerns about consumer rights and property ownership. Most notably, &#039;&#039;&#039;Google&#039;s Service &amp;amp; Repair Program terms&#039;&#039;&#039; explicitly state that any device containing non-Google-authorized parts &amp;quot;&#039;&#039;&#039;will not be returned&#039;&#039;&#039;&amp;quot; to the customer.&amp;lt;blockquote&amp;gt;&#039;&#039;&amp;quot;You will not send in a Device containing non-Google-authorized parts – if You do, Your Device will not be returned to you.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |date=19 Jul 2023 |title=Service &amp;amp; Repair Program Terms &amp;amp; Conditions |url=https://store.google.com/intl/ALL_us/about/device-repair/ |url-status=deviated |archive-url=https://web.archive.org/web/20240603115733/store.google.com/intl/ALL_us/about/device-repair/ |archive-date=3 Jun 2024 |access-date=5 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&#039;&#039;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This means that &#039;&#039;&#039;if a consumer unknowingly sends in a device with an aftermarket part, Google claims the right to keep it.&#039;&#039;&#039; This policy raises concerns regarding ownership and property rights.&lt;br /&gt;
&lt;br /&gt;
===Economic barriers===&lt;br /&gt;
&lt;br /&gt;
The pricing structure of manufacturer self-repair programs frequently makes repairs economically impractical. For example, a &#039;&#039;&#039;Google Pixel 6 Pro screen costs $259.99 for parts only&#039;&#039;&#039;{{cite web|url=https://www.ifixit.com/products/google-pixel-6-pro-screen-genuine|title=Google Pixel 6 Pro Screen - Genuine|publisher=iFixit |archive-url=http://web.archive.org/web/20251214170527/https://www.ifixit.com/products/google-pixel-6-pro-screen-genuine |archive-date=14 Dec 2025}}.&lt;br /&gt;
&lt;br /&gt;
By comparison, &#039;&#039;&#039;used&#039;&#039;&#039; replacement devices are often available at a lower price:&lt;br /&gt;
*&#039;&#039;&#039;Used Google Pixel 6 Pro:&#039;&#039;&#039; $152–$249 on eBay{{cite web|url=https://www.ebay.com/sch/i.html?_nkw=pixel+6+pro+&amp;amp;_sacat=0|title=Pixel 6 Pro for Sale - eBay|publisher=eBay |archive-url=http://web.archive.org/web/20250708173403/https://www.ebay.com/sch/i.html?_nkw=pixel+6+pro+&amp;amp;_sacat=0 |archive-date=8 Jul 2025}}&lt;br /&gt;
&lt;br /&gt;
===Impact===&lt;br /&gt;
&lt;br /&gt;
The limitations imposed by Google&#039;s repair program result in:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Punitive measures against third-party repairs&#039;&#039;&#039; – Programs that refuse to return devices act as &#039;&#039;&#039;de facto monopolies on repair services&#039;&#039;&#039;.&lt;br /&gt;
*&#039;&#039;&#039;Economic disincentives to repair&#039;&#039;&#039; – The artificially high cost of official parts makes &#039;&#039;&#039;repairing older devices less financially practical.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Services]]&lt;br /&gt;
[[Category:Google Pixel]]&lt;br /&gt;
[[Category:Right to repair]]&lt;br /&gt;
[[Category:Consumer rights]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=List_of_Google_products&amp;diff=54773</id>
		<title>List of Google products</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=List_of_Google_products&amp;diff=54773"/>
		<updated>2026-05-25T13:12:00Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following is a non-exhaustive list of products, services and software provided by [[Google]]. The list includes products that have been announced, are in production or discontinued. Discontinued products are marked in &amp;lt;s&amp;gt;strikethrough&amp;lt;/s&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Search and Information:===&lt;br /&gt;
&lt;br /&gt;
*{{wplink|Google Arts &amp;amp; Culture}}&lt;br /&gt;
*{{wplink|Google Books}}&lt;br /&gt;
*{{wplink|Google Earth}}&lt;br /&gt;
*{{wplink|Google Flights}}&lt;br /&gt;
*{{wplink|Google Images}}&lt;br /&gt;
*{{wplink|Google Maps}}&lt;br /&gt;
*{{wplink|Google News}}&lt;br /&gt;
*{{wplink|Google Scholar}}&lt;br /&gt;
*[[Google Search]]&lt;br /&gt;
&lt;br /&gt;
===Communication and Collaboration:===&lt;br /&gt;
&lt;br /&gt;
*{{wplink|Gmail}}&lt;br /&gt;
*&amp;lt;s&amp;gt;{{wplink|Google+}}&amp;lt;/s&amp;gt;&lt;br /&gt;
*{{wplink|Google Calendar}}&lt;br /&gt;
*{{wplink|Google Chat}}&lt;br /&gt;
*{{wplink|Google Docs}}&lt;br /&gt;
*[[Google Drive]]&lt;br /&gt;
*{{wplink|Google Forms}}&lt;br /&gt;
*{{wplink|Google Groups}}&lt;br /&gt;
*{{wplink|Google Meet}}&lt;br /&gt;
*{{wplink|Google Sheets}}&lt;br /&gt;
*{{wplink|Google Sites}}&lt;br /&gt;
*{{wplink|Google Slides}}&lt;br /&gt;
&lt;br /&gt;
===Entertainment:===&lt;br /&gt;
&lt;br /&gt;
*{{wplink|Google Play Books}}&lt;br /&gt;
*{{wplink|Google Play Games}}&lt;br /&gt;
*&amp;lt;s&amp;gt;{{wplink|Google Play Music}}&amp;lt;/s&amp;gt;&lt;br /&gt;
*{{wplink|Google TV (service)|Google TV}}&lt;br /&gt;
*&amp;lt;s&amp;gt;[[Stadia]]&amp;lt;/s&amp;gt;&lt;br /&gt;
*[[YouTube]]&lt;br /&gt;
*{{wplink|YouTube Kids}}&lt;br /&gt;
*{{wplink|YouTube Music}}&lt;br /&gt;
*{{wplink|YouTube TV}}&lt;br /&gt;
&lt;br /&gt;
===Operating Systems and Devices:===&lt;br /&gt;
&lt;br /&gt;
*[[Android]]&lt;br /&gt;
*{{wplink|Android Automotive}}&lt;br /&gt;
*{{wplink|Android TV}}&lt;br /&gt;
*&amp;lt;s&amp;gt;{{wplink|Chromecast}}&amp;lt;/s&amp;gt;&lt;br /&gt;
*{{wplink|ChromeOS}}&lt;br /&gt;
*{{wplink|Fitbit}}&lt;br /&gt;
*&amp;lt;s&amp;gt;{{wplink|Google Daydream}}&amp;lt;/s&amp;gt; (VR phone adapter)&lt;br /&gt;
*{{wplink|Google Nest}} (speakers, displays, thermostats, cameras)&lt;br /&gt;
*&amp;lt;s&amp;gt;{{wplink|Google Nexus}}&amp;lt;/s&amp;gt;&lt;br /&gt;
*[[Google Pixel]] (earbuds, laptops, smartphones, smartwatches, tablets)&lt;br /&gt;
*[[Google Chromebook]] (laptop)&lt;br /&gt;
*{{wplink|Google TV Streamer}}&lt;br /&gt;
*{{wplink|Wear OS}}&lt;br /&gt;
&lt;br /&gt;
===Advertising and Business:===&lt;br /&gt;
&lt;br /&gt;
*{{wplink|Google Ads}}&lt;br /&gt;
*{{wplink|Google AdSense}}&lt;br /&gt;
*{{wplink|Google Analytics}}&lt;br /&gt;
*{{wplink|Google Cloud Platform}}&lt;br /&gt;
*{{wplink|Google Workspace}} (includes Gmail, Drive, Docs, Sheets, Slides, Meet, etc.)&lt;br /&gt;
*[[reCAPTCHA]]&lt;br /&gt;
&lt;br /&gt;
===AI and Research:===&lt;br /&gt;
*{{wplink|Google AI}}&lt;br /&gt;
*[[Google Gemini]]&lt;br /&gt;
*{{wplink|TensorFlow}}&lt;br /&gt;
&lt;br /&gt;
===Other Services and Products:===&lt;br /&gt;
&lt;br /&gt;
*[[Google Chrome]]&lt;br /&gt;
*{{wplink|Google Domains}}&lt;br /&gt;
*{{wplink|Google Fi Wireless}}&lt;br /&gt;
*{{wplink|Google Fonts}}&lt;br /&gt;
*{{wplink|Google One}}&lt;br /&gt;
*{{wplink|Google Pay (payment method)|Google Pay}}&lt;br /&gt;
*{{wplink|Google Play}}&lt;br /&gt;
*{{wplink|Google Photos}}&lt;br /&gt;
*{{wplink|Google Translate}}&lt;br /&gt;
*{{wplink|Google Travel}}&lt;br /&gt;
*{{wplink|Google Wallet}}&lt;br /&gt;
[[Category:Google|*]]&lt;br /&gt;
[[Category:Lists]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=YouTube&amp;diff=54772</id>
		<title>YouTube</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=YouTube&amp;diff=54772"/>
		<updated>2026-05-25T13:10:18Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ProductLineCargo&lt;br /&gt;
|ArticleType=Service&lt;br /&gt;
|Category=Streaming, Video&lt;br /&gt;
|Company=Google&lt;br /&gt;
|Description=YouTube is a video-sharing platform founded in 2005.&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|Logo=YouTube.png&lt;br /&gt;
|ReleaseYear=2005&lt;br /&gt;
|Website=https://youtube.com&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;{{Wplink|YouTube}}&#039;&#039;&#039;, founded in 2005 by Steve Chen, Chad Hurley, and Jawed Karim, is a global video-sharing platform and one of the most visited websites in the world. Acquired by [[Google]] in 2006, YouTube has since become the dominant platform for sharing videos on the internet.&lt;br /&gt;
&lt;br /&gt;
YouTube&#039;s business model is built around advertising revenue, with creators earning money through ad views, subscriptions, and other monetization options. The platform hosts a wide range of content, including music videos, tutorials, news, video logs (&amp;quot;vlogs&amp;quot;), and live streams. YouTube has also begun offering subscription services, such as YouTube Premium and YouTube TV, for ad-free experiences, exclusive content, and live television.&lt;br /&gt;
&lt;br /&gt;
YouTube has faced criticism and regulatory scrutiny on multiple fronts. Concerns have been raised about content moderation policies, the platform&#039;s role in the spread of misinformation, and its impact on user privacy, particularly in relation to data collection practices. Additionally, YouTube has been under fire for its algorithms, which some argue promote harmful or divisive content to maximize engagement.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
*&#039;&#039;&#039;User freedom:&#039;&#039;&#039; Questionable and highly contradictory due rampant bots, falsely accusing others of using their intellectual properties or “IP” for short (although it’s usually either others’ IPs, or it’s criticism, parodies, documentation, commentary, or other fair uses), and [[Elsagate]] suggest negligent moderation.&lt;br /&gt;
*&#039;&#039;&#039;User privacy:&#039;&#039;&#039; Poor; Since August 2025, accessing mature content without identification is a gamble. User data is also sold to advertisers and the site is owned by [[Google]].&lt;br /&gt;
*&#039;&#039;&#039;Business model:&#039;&#039;&#039; [[Advertising overload|Excessive advertising]], YouTube Premium, YouTube Premium Lite&lt;br /&gt;
*&#039;&#039;&#039;Market competition:&#039;&#039;&#039; Despite several platforms that follow its niche, such as Odysee, [[PeerTube]], and [[DailyMotion]], they provide no significant competition.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Elsagate===&lt;br /&gt;
{{Main|Elsagate}}&lt;br /&gt;
&lt;br /&gt;
The first &amp;quot;Elsagate&amp;quot; incident arose sometime during the mid-2010s on YouTube, though it was not discovered and named until 2016. It has since been used as a catch-all term for content that appears child-friendly at first glance but, in actuality, contains suggestive or outright illicit material targeted at minors. This is accomplished by using major intellectual properties for children, such as the Elsa character from the 2013 [[Disney]] film &#039;&#039;{{Wplink|Frozen (2013 film)|Frozen}}&#039;&#039; and [[Minecraft]].&lt;br /&gt;
&lt;br /&gt;
Although the problem is not unique to the YouTube platform, its dominance in the video sphere makes it an attractive target.&lt;br /&gt;
&lt;br /&gt;
===Restricting users that don&#039;t share their personal information===&lt;br /&gt;
{{Main|YouTube age verification}}&lt;br /&gt;
&lt;br /&gt;
On 30 July 2025, in response to the [[UK Online Safety Act]], YouTube announced a verification update that asks for either a government-issued ID, a photo, or credit card, otherwise they could not access content.&amp;lt;ref&amp;gt;{{Cite web |last=Ingram |first=Michael |title=YouTube is Rolling Out A New Controversial Feature |url=https://gamerant.com/youtube-new-age-verification-feature-id-recognition/ |website=GameRant |date=30 Jul 2025 |access-date=14 Aug 2025 |url-status=live |archive-url=https://web.archive.org/web/20250730234131/https://gamerant.com/youtube-new-age-verification-feature-id-recognition/ |archive-date=30 Jul 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
YouTube will estimate the age of a user from various sources, including the videos watched, and will ask for previously mentioned personal information when it believes that the user falls below 18.&lt;br /&gt;
&lt;br /&gt;
===Advertising overload on YouTube===&lt;br /&gt;
{{Main|Advertising overload}}&lt;br /&gt;
&lt;br /&gt;
Advertisements are YouTube&#039;s primary source of revenue.&amp;lt;ref&amp;gt;{{Cite web |author= |title=How YouTube Works |url=https://www.youtube.com/howyoutubeworks/our-commitments/sharing-revenue/ |website=YouTube |date= |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260101140008/https://www.youtube.com/howyoutubeworks/creator-economy/ |archive-date=1 Jan 2026}}&amp;lt;/ref&amp;gt; This has led to advertisements becoming more pervasive on the platform&amp;lt;ref&amp;gt;{{Cite web |last=Brown |first=Jordan |date=20 Jan 2024 |title=Why YouTube Has So Many Ads (and Why There Will Probably Be More) |url=https://www.33rdsquare.com/software-app/why-youtube-has-so-many-ads-and-why-there-will-probably-be-more/ |url-status=live |archive-url=https://ghostarchive.org/archive/GjC82 |archive-date=24 Feb 2026 |access-date=12 Jul 2025 |website=33rd Square}}&amp;lt;/ref&amp;gt; such as an increasing number of spaces for static ads, longer ad breaks (which some users have documented being longer than the videos they watch&amp;lt;ref&amp;gt;{{Cite web |last=Siddiqui |first=Aamir |title=Frustrated YouTube viewers seek explanation for hour-long unskippable ads (Updated: Clarification) |url=https://www.androidauthority.com/youtube-long-unskippable-ads-problem-3519957/ |website=Android Authority |date=27 Jan 2025 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20250128162022/https://www.androidauthority.com/youtube-long-unskippable-ads-problem-3519957/ |archive-date=28 Jan 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Dirscherl |first=Hans-Christian |last2=Lee |first2=Joel |title=Hours-long unskippable ads spotted on YouTube. What’s going on? |url=https://www.pcworld.com/article/2590352/hours-long-unskippable-ads-spotted-on-youtube-whats-going-on.html |website=PCWorld |date=28 Jan 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250129183554/https://www.pcworld.com/article/2590352/hours-long-unskippable-ads-spotted-on-youtube-whats-going-on.html |archive-date=29 Jan 2025}}&amp;lt;/ref&amp;gt; and most prevalent on YouTube TV&amp;lt;ref&amp;gt;{{Cite web |last=Adegbola |first=Anu&lt;br /&gt;
|title=YouTube tests longer CTV ad breaks |url=https://searchengineland.com/youtube-tests-longer-ad-breaks-ctv-445248 |website=Search Engine Land |date=16 Aug 2024 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20240816143812/https://searchengineland.com/youtube-tests-longer-ad-breaks-ctv-445248 |archive-date=16 Aug 2024}}&amp;lt;/ref&amp;gt;), increased ad frequency in videos,&amp;lt;ref&amp;gt;{{Cite web |last=Wright |first=Arol |title=YouTube is Adding Even More Ads |url=https://www.howtogeek.com/youtube-is-adding-even-more-ads/ |website=How-To-Geek |date=26 Apr 2024 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20240426192258/https://www.howtogeek.com/youtube-is-adding-even-more-ads/ |archive-date=26 Apr 2024}}&amp;lt;/ref&amp;gt; and poorer quality ads.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |author=T3rr0r |title=BAD Mobile Game Ads |url=https://www.youtube.com/watch?v=dRjGn54O4Zg |website=YouTube |date=17 Oct 2021 |access-date=12 Jul 2025 |url-status=live |archive-url=https://preservetube.com/watch?v=dRjGn54O4Zg |archive-date=26 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite web |last=Knoblauch |first=Max |title=Why are mobile game ads so weird and bad? |url=https://sherwood.news/business/mobile-game-ads-industry-fake-misleading/ |website=Sherwood News |date=14 Jun 2024 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20240614151756/https://sherwood.news/business/mobile-game-ads-industry-fake-misleading/ |archive-date=14 Jun 2024}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:7&amp;quot;&amp;gt;{{Cite web |author=Saberspark |title=The DISGUSTING State of Mobile Game Ads (and why YouTube LOVES IT) |url=https://www.youtube.com/watch?v=KsKlfN9phAs |website=YouTube |date=18 Sep 2021 |access-date=12 Jul 2025 |url-status=live |archive-url=https://preservetube.com/watch?v=KsKlfN9phAs |archive-date=26 Jan 2026}}&amp;lt;/ref&amp;gt; Practices are also put into place in order to force non-paying users into seeing these ads as well, such as subscription-gating playing videos in the background.&amp;lt;ref&amp;gt;{{Cite web |author= |title=YouTube Premium |url=https://www.youtube.com/premium?ybp=Sg0IBhIJdW5saW1pdGVk4AEC |website=YouTube |date= |access-date=6 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260206072120/https://www.youtube.com/premium?ybp=Sg0IBhIJdW5saW1pdGVk4AED |archive-date=6 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Furthermore, even if a user pays for YouTube premium, they do not necessarily receive an ad-free experience&amp;lt;ref&amp;gt;{{Cite web |author=CaptainMystery_123 |title=I have YouTube premium, why am I getting adds. |url=https://old.reddit.com/r/youtube/comments/18ll7y6/i_have_youtube_premium_why_am_i_getting_adds/ |website=[[Reddit]] |date=18 Dec 2023 |access-date=12 Jul 2025 |url-status=live&lt;br /&gt;
|archive-url=https://web.archive.org/web/20250525154227/https://old.reddit.com/r/youtube/comments/18ll7y6/i_have_youtube_premium_why_am_i_getting_adds/ |archive-date=25 May 2025}}&amp;lt;/ref&amp;gt; — they may still see ads within the video they watch, such as sponsored segments.&amp;lt;ref&amp;gt;{{Cite web |last=Sharma |first=Adamya |title=Can you still see ads if you have YouTube Premium? Here&#039;s what Google has to say |url=https://www.androidauthority.com/remove-youtube-premium-ads-3384953/ |website=Android Authority |date=10 May 2024 |access-date=11 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20251211123241/https://www.androidauthority.com/remove-youtube-premium-ads-3384953/ |archive-date=11 Dec 2025}}&amp;lt;/ref&amp;gt; YouTube has added a &amp;quot;skip&amp;quot; feature, but it has been reported that this does not work consistently.&amp;lt;ref&amp;gt;{{Cite web |last=Singh |first=Anurag |title=YouTube now lets you skip sponsored segments — but you’ll have to pay for it |url=https://www.dexerto.com/youtube/youtube-now-lets-you-skip-sponsored-segments-but-youll-have-to-pay-for-it-2872784/ |website=Dexerto |date=22 Aug 2024 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20240822211151/https://www.dexerto.com/youtube/youtube-now-lets-you-skip-sponsored-segments-but-youll-have-to-pay-for-it-2872784/ |archive-date=22 Aug 2024}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Refusal to handle malicious ads====&lt;br /&gt;
A common phenomenon on YouTube&#039;s advertisements is content that is mature and/or malicious in nature.&amp;lt;ref&amp;gt;{{Cite web |author=Beyond The Internet |title=YouTube Ads are inappropriate... |url=https://www.youtube.com/watch?v=_B2KdIoRVo8 |website=YouTube |date=22 Feb 2025 |access-date=12 Jul 2025 |url-status=dead |archive-url=https://preservetube.com/watch?v=_B2KdIoRVo8 |archive-date=23 Feb 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:8&amp;quot;&amp;gt;{{Cite web |last=Sharma |first=Adamya |title=Explicit ads are plaguing YouTube, and it’s only getting worse&lt;br /&gt;
|url=https://www.androidauthority.com/youtube-explicit-ads-problem-3520285/ |website=Android Authority |date=27 Jan 2025 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20250127062033/https://www.androidauthority.com/youtube-explicit-ads-problem-3520285/ |archive-date=27 Jan 2025}}&amp;lt;/ref&amp;gt; The content of these advertisements include pornography,&amp;lt;ref&amp;gt;{{Cite web |author=Saberspark |title=YouTube&#039;s Ads Have Hit A New Low...(it&#039;s literally p*rn) |url=https://www.youtube.com/watch?v=cW4On_gWAvI |website=YouTube |date=31 Mar 2025 |access-date=12 Jul 2025 |url-status=live |archive-url=https://preservetube.com/watch?v=cW4On_gWAvI |archive-date=2 Apr 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; false advertising,&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:7&amp;quot; /&amp;gt; scams,&amp;lt;ref&amp;gt;{{Cite web |author=Jakob_G |title=YouTube doesn&#039;t want to take down scam ads |url=https://old.reddit.com/r/youtube/comments/18gjiqy/youtube_doesnt_want_to_take_down_scam_ads/ |website=[[Reddit]] |date=12 Dec 2023 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20231217150604/https://old.reddit.com/r/youtube/comments/18gjiqy/youtube_doesnt_want_to_take_down_scam_ads/ |archive-date=17 Dec 2023}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=JerryRigEverything |title=I CAUGHT THE YOUTUBE SCAMMER - $1000 dollars EVERY DAY?! |url=https://www.youtube.com/watch?v=iROF9Dd7FXA |website=YouTube |date=9 Mar 2023 |access-date=11 Feb 2026 |url-status=live |archive-url=https://preservetube.com/watch?v=iROF9Dd7FXA |archive-date=26 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=LoganAH |title=Why does YouTube run blatant scams as advertisements? |url=https://old.reddit.com/r/youtube/comments/18osjs6/why_does_youtube_run_blatant_scams_as/ |website=[[Reddit]] |date=22 Dec 2023 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20250713054442/https://old.reddit.com/r/youtube/comments/18osjs6/why_does_youtube_run_blatant_scams_as/ |archive-date=13 Jul 2025}}&amp;lt;/ref&amp;gt; and far more. Rather than working towards clearing these ads, or acknowledging this advertising content that has been harming consumers on the platform, YouTube moderation has only cut the revenue for these videos that attempt to call out these ads,&amp;lt;ref&amp;gt;{{Cite web |author=Deep Humor |title=Watch This Before YouTube Deletes It. |url=https://www.youtube.com/watch?v=QRpECEQ0-hg |website=YouTube |date=24 Feb 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://preservetube.com/watch?v=QRpECEQ0-hg |archive-date=26 Feb 2025}}&amp;lt;/ref&amp;gt; which has been known to make said videos be less-showcased.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |author=Sealow |title=Extensive evidence of algorithm censorship of demonetised videos |url=https://www.youtube.com/watch?v=n3H8D2LrLHc |website=YouTube |date=29 Nov 2017 |access-date=11 Feb 2026 |url-status=live |archive-url=https://preservetube.com/watch?v=n3H8D2LrLHc |archive-date=26 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |author=Karlaplan |title=Monetisation analysis / research |url=https://docs.google.com/document/d/155yNpfR7dGKuN-4rbrvbJLcJkhGa_HqvVuyPK7UEfPo/edit?tab=t.0#heading=h.jou9rc5d49jl |website=[[Google]] |date=20 Nov 2017 |access-date=3 Apr 2026 |url-status=live |archive-url=https://consumerrights.wiki/images/5/5c/Karlaplan_Monetisation_analysis_research.pdf |archive-date=11 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Demonetization and censorship===&lt;br /&gt;
Since at least 2016, YouTube has had an extensive record of censoring content that is demonetized.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; Within understandable circumstances, legitimately malicious or offensive videos would be demonetized and should not be shown on the platform; however, how videos are considered to be demonetized has had a harmful impact upon both viewers and content creators. Transgender creators on YouTube, for example, have experienced unfair censorship via demonetization since 2018.&amp;lt;ref&amp;gt;{{Cite web |last=Disney |first=Malia |title=Trans YouTubers Say They Are Being Censored. Is It The Algorithm? |url=https://archive.yr.media/journalism/outloud/trans-youtubers-say-they-are-being-censored-and-an-algorithm-may-be-to-blame/ |website=Youth Radio Media&lt;br /&gt;
|date=4 May 2018 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20230130035845/https://archive.yr.media/journalism/outloud/trans-youtubers-say-they-are-being-censored-and-an-algorithm-may-be-to-blame/ |archive-date=30 Jan 2023}}&amp;lt;/ref&amp;gt; Content creators affected by this unfairly balanced moderation via algorithms&amp;lt;ref&amp;gt;{{Cite web |last=Cantz |first=Randy |title=Adpocalypse: How YouTube Demonetization Imperils the Future of Free Speech |url=https://bpr.studentorg.berkeley.edu/2018/05/01/adpocalypse-how-youtube-demonetization-imperils-the-future-of-free-speech/ |website=Berkeley Political Review |date=1 May 2018 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20240424095310/https://bpr.studentorg.berkeley.edu/2018/05/01/adpocalypse-how-youtube-demonetization-imperils-the-future-of-free-speech/ |archive-date=24 Apr 2024}}&amp;lt;/ref&amp;gt; have dubbed these events as &amp;quot;adpocalypses&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |last=Alexander |first=Julia |title=YouTubers fear looming ‘adpocalypse’ after child exploitation controversy&lt;br /&gt;
|url=https://www.theverge.com/2019/2/20/18231561/youtube-child-exploitation-predators-controversy-creators-adpocalypse |website=The Verge |date=20 Feb 2019 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20190220205927/https://www.theverge.com/2019/2/20/18231561/youtube-child-exploitation-predators-controversy-creators-adpocalypse |archive-date=20 Feb 2019}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Irresponsibly automated moderation====&lt;br /&gt;
When YouTube integrated the ability to take down videos via the [[Digital Millennium Copyright Act]] (DMCA), they decided to often handle take-down requests in an automated manner.&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |last=Jines |first=Chuck |title=ABUSE – How DMCA automated takedown notices violate free speech |url=https://www.chuckjines.com/abuse-dmac-automated-takedown-notices-and-free-speech/ |website=Chuck Jines |date=4 Mar 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250303201747/https://www.chuckjines.com/abuse-dmac-automated-takedown-notices-and-free-speech/ |archive-date=3 Mar 2025}}&amp;lt;/ref&amp;gt; This automation has led to an excess in fraudulent DMCA take-downs of content,&amp;lt;ref&amp;gt;{{Cite web |author=itanshi |title=I&#039;d like to talk about the problem with anonymous DMCA take down notices. |url=https://old.reddit.com/r/youtube/comments/5zzr9c/id_like_to_talk_about_the_problem_with_anonymous/ |website=[[Reddit]] |date=27 Mar 2017 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20230606184354/https://old.reddit.com/r/youtube/comments/5zzr9c/id_like_to_talk_about_the_problem_with_anonymous/ |archive-date=6 Jun 2023}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=The Last Civil Rights Lawyer |title=“Lackluster” Gets a Fraudulent Copyright Strike for Dashcam Footage and Now We Sue |url=https://www.youtube.com/watch?v=rPqtT88PT9Y |website=YouTube |date=21 Jul 2021 |access-date=11 Feb 2026 |url-status=live |archive-url=https://preservetube.com/watch?v=rPqtT88PT9Y |archive-date=2 Feb 2026}}&amp;lt;/ref&amp;gt; even going so far as to have [[Bungie]] call out YouTube in a legal case for their negligence.&amp;lt;ref&amp;gt;{{Cite web |last=Brodkin&lt;br /&gt;
|first=John |title=Bungie slams YouTube’s DMCA system in lawsuit against &#039;&#039;Destiny&#039;&#039; takedown fraudsters |url=https://arstechnica.com/tech-policy/2022/03/bungie-slams-youtubes-dmca-system-in-lawsuit-against-destiny-takedown-fraudsters/ |website=Ars Technica |date=28 Mar 2022 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20220329203809/https://arstechnica.com/tech-policy/2022/03/bungie-slams-youtubes-dmca-system-in-lawsuit-against-destiny-takedown-fraudsters/ |archive-date=29 Mar 2022}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Maxwell |first=Andy |title=Digital Trails: How Bungie Identified a Mass Sender of Fake DMCA Notices |url=https://torrentfreak.com/digital-trails-how-bungie-identified-a-mass-sender-of-fake-dmca-notices-220624/ |website=TorrentFreak |date=24 Jun 2022 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20220624070824/https://torrentfreak.com/digital-trails-how-bungie-identified-a-mass-sender-of-fake-dmca-notices-220624/ |archive-date=24 Jun 2022}}&amp;lt;/ref&amp;gt; These take-down requests have ranged from users impersonating corporations, to users impersonating other users.&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===Crackdown against ad-blockers===&lt;br /&gt;
&amp;lt;!-- Needs citations --&amp;gt;&lt;br /&gt;
The prevalence of advertising on the platform, coupled with the repeated appearance of harmful and deceptive ads within YouTube&#039;s advertising system, led a significant number of users to employ ad-blocking tools to facilitate their viewing experience.&lt;br /&gt;
&lt;br /&gt;
In response, Google initiated technical countermeasures to limit the functionality of these tools. This has resulted in an ongoing cycle where ad-blocker developers adapt to new restrictions, and the platform subsequently implements further detection methods. A key strategy in this effort involves the implementation of advanced code integrity checks designed to ensure ad content is delivered to viewers.&lt;br /&gt;
&lt;br /&gt;
However, these measures typically exhibit limited efficacy before ad-blocking tools develop new methods of circumvention,&amp;lt;ref&amp;gt;{{Cite web |last=O&#039;Flaherty |first=Kate |title=YouTube’s Ad Blocker Ban Just Got Even Bigger |url=https://www.forbes.com/sites/kateoflahertyuk/2024/06/20/youtubes-ad-blocker-ban-just-got-even-bigger/ |url-access=subscription |website=Forbes |date=20 Jun 2024 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20240620123932/https://www.forbes.com/sites/kateoflahertyuk/2024/06/20/youtubes-ad-blocker-ban-just-got-even-bigger/ |archive-date=20 Jun 2024}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Harding |first=Scharon |title=YouTube’s ad blocker crackdown escalates, aggravating users |url=https://arstechnica.com/google/2023/11/youtube-tries-to-kill-ad-blockers-in-push-for-ad-dollars-premium-subs/ |website=Ars Technica |date=1 Nov 2023 |access-date=12 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20231101170643/https://arstechnica.com/google/2023/11/youtube-tries-to-kill-ad-blockers-in-push-for-ad-dollars-premium-subs/ |archive-date=1 Nov 2023}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Rossmann |first=Louis |title=YouTube blocks adblockers; will this be their downfall? |url=https://www.youtube.com/watch?v=DMaFH4KzOVg |website=YouTube |date=12 Oct 2023 |access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=DMaFH4KzOVg |archive-date=13 Oct 2023}}&amp;lt;/ref&amp;gt; a dynamic that some analysts suggest exemplifies the {{Wplink|Streisand effect}}.&amp;lt;ref&amp;gt;{{Cite web |author=phub |title=Brave no longer blocking youtube ads as of March 27, 2024 |url=https://community.brave.com/t/brave-no-longer-blocking-youtube-ads-as-of-march-27-2024/540032 |website=Brave |date=27 Mar 2024 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20240801101510/https://community.brave.com/t/brave-no-longer-blocking-youtube-ads-as-of-march-27-2024/540032 |archive-date=1 Aug 2024}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Rossmann |first=Louis |title=YouTube&#039;s adblock war is backfiring in the worst way possible 🤣 |url=https://www.youtube.com/watch?v=_GARcKCaUfI |website=YouTube |date=5 Nov 2023 |access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=_GARcKCaUfI |archive-date=5 Nov 2023}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Additional strategies have involved the integration of advertisements directly into video streams. This approach has impaired the functionality of certain browser extensions, including SponsorBlock, a community-driven tool designed to skip sponsored segments within videos. The extension relies on user-submitted timestamps to identify these segments; its effectiveness is significantly reduced when personalized advertisements, which vary in duration and placement for each viewer, are embedded into the stream itself.&amp;lt;ref&amp;gt;{{Cite web |last=Rossmann |first=Louis&lt;br /&gt;
|title=Youtube is dedicated to making this website worse; destroys sponsorblock with ad injection changes |url=https://www.youtube.com/watch?v=weP62wPEjRw |website=YouTube |date=18 Jun 2024&lt;br /&gt;
|access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=weP62wPEjRw |archive-date=28 Jul 2024}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google has publicly acknowledged implementing code that degrades the user experience for individuals using ad blockers. This includes introducing artificial latency, which has been documented to slow page load times, a measure that also affected users of the Firefox browser.&amp;lt;ref&amp;gt;{{Cite web |last=Rossmann |first=Louis |title=Youtube confirms intentional slowdown of adblock users 🤦‍♂️ |url=https://www.youtube.com/watch?v=KMLMQRS3Krk |website=YouTube |date=23 Nov 2023 |access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=KMLMQRS3Krk |archive-date=23 Nov 2023}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Rossmann |first=Louis |title=Is Youtube making firefox load slow on purpose? |url=https://www.youtube.com/watch?v=_x7NSw0Irc0 |website=YouTube |date=21 Nov 2023 |access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=_x7NSw0Irc0 |archive-date=21 Nov 2023}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Offline video DRM===&lt;br /&gt;
The YouTube Mobile application permits users with a YouTube Premium subscription to download videos for offline viewing. However, the downloaded content is protected by [[Digital rights management|Digital Rights Management]] (DRM) that [[Forced cloud|requires the application to establish an online connection]] with YouTube&#039;s servers at least once every 48 hours to maintain playback functionality. This requirement is not prominently featured on the primary YouTube Premium marketing page and is detailed instead within the platform&#039;s support documentation.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |author= |date= |title=YouTube Premium |url=https://www.youtube.com/premium |url-status=live |archive-url=https://web.archive.org/web/20251111004845/https://www.youtube.com/premium |archive-date=11 Nov 2025 |access-date=2 Feb 2026 |website=YouTube}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author= |title=Watch videos offline on mobile in selected countries and regions |url=https://support.google.com/youtube/answer/6141269 |website=[[Google]] |date=13 Jul 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250719175650/https://support.google.com/youtube/answer/6141269 |archive-date=19 Jul 2025}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Saved videos are forcibly deleted after 29 days. [[Data_lock-in#Videos_downloaded_inside_the_YouTube_app|Data lock-in and proprietary encoding]] prevents the user from making permanent copies of videos, even those licensed under Creative Commons.&amp;lt;ref&amp;gt;{{Cite web |last=Santos |first=Noel |title=Warning: Youtube Premium &amp;quot;Downloads&amp;quot; aren&#039;t MP4 Files |url=https://www.virtualcuriosities.com/articles/3383/warning-youtube-premium-downloads-arent-mp4-files |website=Virtual Curiosities |date=7 Dec 2024 |access-date=2 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20251126100053/https://www.virtualcuriosities.com/articles/3383/warning-youtube-premium-downloads-arent-mp4-files |archive-date=26 Nov 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=Mental Outlaw |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |website=YouTube |date=28 Aug 2025 |access-date=2 Feb 2026 |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=29 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Universal DRM testing and violation of Creative Commons licenses===&lt;br /&gt;
YouTube on TV is an {{Wplink|HTML5}} web interface from Google to allow supported devices — such as game consoles which do not have a native YouTube app — to view content via YouTube. An {{Wplink|A/B testing|A/B experiment}} has begun which protects all video and audio content regardless of bit-rate or format via the YouTube on TV platform with DRM.&amp;lt;ref&amp;gt;{{Cite web |author=coletdjnz |title=[YouTube] DRM on ALL videos with tv (TVHTML5) client #12563 |url=https://github.com/yt-dlp/yt-dlp/issues/12563 |website=GitHub |date=8 Mar 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250330031529/https://github.com/yt-dlp/yt-dlp/issues/12563 |archive-date=30 Mar 2025}}&amp;lt;/ref&amp;gt; A number of content creators license their work uploaded to YouTube via the {{Wplink|Creative Commons}} licenses. The universal implementation of DRM to restrict a user&#039;s ability to exercise their rights granted by the license is a violation of the aforementioned licenses.&amp;lt;ref&amp;gt;{{Cite web |author= |title=License Versions |url=https://wiki.creativecommons.org/wiki/License_Versions#Application_of_effective_technological_measures_by_users_of_CC-licensed_works_prohibited |website=Creative Commons |date=13 Jul 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250101062938/https://wiki.creativecommons.org/wiki/License_Versions#Application_of_effective_technological_measures_by_users_of_CC-licensed_works_prohibited |archive-date=1 Jan 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Pay-walling standard browser features===&lt;br /&gt;
Another premium feature of the YouTube mobile app is the ability to play videos in the background.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; Without a premium subscription, neither the app nor a web browser will play YouTube videos in the background. However, the default HTML5 video player supports this with no extra effort needed from the developer.&lt;br /&gt;
&lt;br /&gt;
On 7 February 2026, it was reported that YouTube Music was testing a feature that would paywall song lyrics, which were previously a free feature since 2020.&amp;lt;ref&amp;gt;{{Cite web |last=Hardwick |first=Tim |title=YouTube Music lyrics now require a Premium subscription |url=https://9to5google.com/2026/02/07/youtube-music-lyrics-premium/ |website=9TO5Google |date=7 Feb 2026 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260208225137/https://9to5google.com/2026/02/07/youtube-music-lyrics-premium/ |archive-date=8 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Removal of the dislike count on videos===&lt;br /&gt;
On 10 November 2021, YouTube removed the public dislike count from all of its videos. Creators are still be able to view dislike counts on their videos through the YouTube Studio website and app.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |author= |title=An update to dislikes on YouTube |url=https://blog.youtube/news-and-events/update-to-youtube/ |website=YouTube Official Blog |date=10 Nov 2021 |access-date=13 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20211110173333/https://blog.youtube/news-and-events/update-to-youtube/ |archive-date=10 Nov 2021}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
According to YouTube, this was implemented after user testing revealed that users were less likely to feel incentivized to actively try and manipulate the dislike count on videos if the dislike count was not visible to them.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; This spurred the creation of &amp;quot;Return YouTube Dislike&amp;quot; by Dmitry Selivanov, a third-party web browser extension to expose the dislike count again. YouTube discontinued the related {{Wplink|API}}, upon which the extension relied, on 13 December 2021. From thereon &amp;quot;Return YouTube Dislike&amp;quot; switched &amp;quot;to using a combination of archived dislike stats, estimates extrapolated from extension user data and estimates based on view/like ratios for videos whose dislikes weren&#039;t archived and for outdated dislike archives.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |last=Can |first=Michael |title=Browser Extension Brings Back Dislike Count to YouTube Videos |url=https://www.pcmag.com/news/browser-extension-brings-back-dislike-count-to-youtube-videos &lt;br /&gt;
|website=PC Mag |date=29 Nov 2021 |access-date=13 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20211130001311/https://www.pcmag.com/news/browser-extension-brings-back-dislike-count-to-youtube-videos |archive-date=30 Nov 2021}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Removal of chronological searching===&lt;br /&gt;
In January 2026, YouTube removed the ability to search videos by the most recently uploaded, as well as the &amp;quot;last hour&amp;quot; search filter. The &amp;quot;last day&amp;quot; search filter is the narrowest remaining time filter.&lt;br /&gt;
&lt;br /&gt;
A Google employee stated that this change is intended to &amp;quot;improve content discovery&amp;quot; and that they are &amp;quot;simplifying and reorganizing the filter menu to make it more intuitive and improve the overall search experience&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |author=Hank (TeamYouTube) |title=Changes to YouTube Search Filters to Improve Content Discovery |url=https://support.google.com/youtube/thread/400586735/changes-to-youtube-search-filters-to-improve-content-discovery |website=[[Google]] |date=8 Jan 2026 |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260108225453/https://support.google.com/youtube/thread/400586735/changes-to-youtube-search-filters-to-improve-content-discovery |archive-date=8 Jan 2026}}&amp;lt;/ref&amp;gt; However, it was noted that this makes it more difficult to discover eye-witness stories that are alternatives to mainstream news outlets, and makes it harder for watchers to discover channels with low subscriber counts.&amp;lt;ref&amp;gt;{{Cite web |last=Cubbins |first=Dwayne |title=YouTube may be testing removal of Upload date filter from search on web |url=https://piunikaweb.com/2026/01/06/youtube-upload-date-filter-removal-test-web/ |website=PiunikaWeb |date=6 Jan 2026 |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260329221637/https://piunikaweb.com/2026/01/06/youtube-upload-date-filter-removal-test-web/ |archive-date=29 Mar 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Melchner |first=Felix |title=Why did YouTube remove the &amp;quot;last hour&amp;quot; filter? |url=https://www.recentreborn.com/blog/why-did-youtube-remove-the-last-hour-filter |website=RecentReborn |date= |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260311025955/https://www.recentreborn.com/blog/why-did-youtube-remove-the-last-hour-filter |archive-date=11 Mar 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=Jack_P_1337 |title=Youtube removes the &amp;quot;Sort by Upload Date&amp;quot; option pretending it didn&#039;t work, the reality? They want absolute control of the information you are allowed to get from the site |url=https://old.reddit.com/r/youtube/comments/1q8szsr/youtube_removes_the_sort_by_upload_date_option/ |website=[[Reddit]] |date=10 Jan 2026 |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260329174114/https://old.reddit.com/r/youtube/comments/1q8szsr/youtube_removes_the_sort_by_upload_date_option/ |archive-date=29 Mar 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Anti-features and dark patterns to trick the user into staying longer===&lt;br /&gt;
YouTube&#039;s algorithm was engineered to make the user watch more videos than they intended, to earn more ad revenue.&amp;lt;ref&amp;gt;{{Cite web |last=Nicas |first=Jack |title=How YouTube Drives People to the Internet’s Darkest Corners |url=https://www.wsj.com/articles/how-youtube-drives-viewers-to-the-internets-darkest-corners-1518020478 |url-access=subscription |website=The Wall Street Journal. |date=7 Feb 2018 |access-date=29 Jan 2026 |url-status=live |archive-url=https://web.archive.org/web/20181208091112/https://www.wsj.com/articles/how-youtube-drives-viewers-to-the-internets-darkest-corners-1518020478 |archive-date=8 Dec 2018 |quote=YouTube engineered its algorithm several years ago to make the site “sticky”—to recommend videos that keep users staying to watch still more, said current and former YouTube engineers who helped build it. The site earns money selling ads that run before and during videos.}}&amp;lt;/ref&amp;gt; This is on top of a feature called Autoplay, which queues another video (chosen by Youtube&#039;s algorithm) and plays that automatically after a short delay so you keep watching more. Through this mechanism, children will especially have their attention extracted for several hours.&amp;lt;ref name=&amp;quot;:9&amp;quot;&amp;gt;{{Cite web |author= |title=James Bridle: What Do Kids&#039; Videos on YouTube Reveal About the Internet&#039;s Dark Side? |others=NPR/TED Staff |url=https://www.npr.org/transcripts/662612151 |website=NPR |date=2 Nov 2018 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250620234159/https://www.npr.org/transcripts/662612151 |archive-date=20 Jun 2025 |quote=&amp;quot;And also, on the other side of the screen, there still are these little kids watching this stuff - right? - their full attention grabbed by these weird mechanisms. And so there&#039;s autoplay, where it just keeps playing these videos over and over and over on a loop, endlessly, for hours and hours at a time. And there&#039;s so much weirdness in the system now that autoplay takes you to some pretty strange places. This is how within, like, a dozen steps, you can go from a cute video of a counting train to masturbating Mickey Mouse.&amp;quot;}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default, this feature is enabled.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Autoplay videos - YouTube Help |url=https://support.google.com/youtube/answer/6327615?hl=en |website=[[Google]] |date=4 Apr 2025 |access-date=13 Jul 2025 |url-status=live |archive-url=https://web.archive.org/web/20250401080124/https://support.google.com/youtube/answer/6327615?hl=en |archive-date=1 Apr 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Crackdown against third-party front-ends===&lt;br /&gt;
&amp;lt;!--Still want to include more examples of front-ends breaking--&amp;gt;&lt;br /&gt;
Since the beginning of 2025, users have been reporting issues with third-party front-ends accessing the platform.&amp;lt;ref&amp;gt;{{Cite web |author=Fijxu |title=Youtube changed something, again! |url=https://nadeko.net/announcements/invidious-02-20/ |website=nadeko |date=16 Feb 2025 |access-date=16 Aug 2025 |url-status=live |archive-url=https://web.archive.org/web/20250816014757/https://nadeko.net/announcements/invidious-02-20/ |archive-date=16 Aug 2025}}&amp;lt;/ref&amp;gt; For FreeTube, there has been a heightened amount of people receiving {{Wplink|HTTP 403|403 errors}} associated with IP blocks when attempting to view videos via this front-end.&amp;lt;ref&amp;gt;{{Cite web |author=Gevaarlijk |title=[Bug]: [BAD_HTTP_STATUS: 403] Potential causes: IP block or streaming URL deciphering failed #6701 |url=https://github.com/FreeTubeApp/FreeTube/issues/6701 |website=[[GitHub]] |date=31 Jan 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20260105144421/https://github.com/FreeTubeApp/FreeTube/issues/6701 |archive-date=5 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===AI filtering without consent===&lt;br /&gt;
YouTube is testing an experiment on Shorts content that enhances a video&#039;s detail without the creator&#039;s consent.&amp;lt;ref&amp;gt;{{Cite web |last=Reisner |first=Alex |title=YouTube’s Sneaky AI ‘Experiment’&lt;br /&gt;
|url=https://www.theatlantic.com/technology/archive/2025/08/youtube-shorts-ai-upscaling/683946/ |website=The Atlantic |date=22 Aug 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250822194955/https://www.theatlantic.com/technology/archive/2025/08/youtube-shorts-ai-upscaling/683946/ |archive-date=22 Aug 2025}}&amp;lt;/ref&amp;gt; The resulting output tends to look plastic. This change has been observed as early as 27 June 2025&amp;lt;ref&amp;gt;{{Cite web |author=Ulincsys |title=YouTube Shorts are almost certainly being AI upscaled |url=https://old.reddit.com/r/youtube/comments/1lllnse/youtube_shorts_are_almost_certainly_being_ai/ |website=[[Reddit]] |date=27 Jun 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20250827144146/https://old.reddit.com/r/youtube/comments/1lllnse/youtube_shorts_are_almost_certainly_being_ai/ |archive-date=27 Aug 2025}}&amp;lt;/ref&amp;gt; and affects creators who especially intend the video to be viewed in a certain way, such as the &amp;quot;{{Wplink|VHS}} look&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |author=dolanbriese |title=YouTube Shorts are becoming AI upscaled without consent from creators |url=https://old.reddit.com/r/youtube/comments/1m5y7zu/youtube_shorts_are_becoming_ai_upscaled_without/ |website=[[Reddit]] |date=21 Jul 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20251003103832/https://old.reddit.com/r/youtube/comments/1m5y7zu/youtube_shorts_are_becoming_ai_upscaled_without/ |archive-date=3 Oct 2025}}&amp;lt;/ref&amp;gt; Rhett Shull, in his video, opines such a change &amp;quot;will inevitably erode viewers trust in my content [...] or any of the other creators on this platform that we all watch and we all follow&amp;quot; due to implications that the creator may be using AI, and &amp;quot;also erodes my trust in the platform.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |last=Shull |first=Rhett |title=YouTube Is Using AI to Alter Content (and not telling us) |url=https://www.youtube.com/watch?v=86nhP8tvbLY |website=YouTube |date=14 Aug 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=86nhP8tvbLY |archive-date=16 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Artist Sam Yang uploaded a video on 30 August 2025, following up on the issue using his own work for comparison, testing the claims that this is merely compression scaling, adding an artist&#039;s eye and commentary to the issue.&amp;lt;ref&amp;gt;{{Cite web |last=Yang |first=Sam |title=Youtube is Using AI on Your Shorts Without Consent.. |url=https://www.youtube.com/watch?v=tjnQ-s7LW-g |website=YouTube |date=30 Aug 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=tjnQ-s7LW-g |archive-date=26 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users also complained about a dangerous flickering that happens under some videos. Some forwarded this issue to YouTube scientist Anton Petrov, to which he replicated the issue and showed it under a video uploaded 25 October 2025, noting it happens on one of his devices, more specifically a mobile phone.&amp;lt;ref&amp;gt;{{Cite web |last=Petrov |first=Anton |title=YouTube AI Filter Is Making My Videos Dangerous To Watch |url=https://www.youtube.com/watch?v=2HY-nREvVu4 |website=YouTube |date=25 Oct 2025 |access-date=11 Feb 2026 |url-status=live |archive-url=https://www.preservetube.com/watch?v=2HY-nREvVu4 |archive-date=26 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Wave of channel terminations (&#039;&#039;2025&#039;&#039;)===&lt;br /&gt;
In November 2025, multiple YouTube channels, including Enderman, Scratchit Gaming, and 4096 were reportedly terminated in a massive ban wave under false reasons, such as association with a Japanese-language channel &amp;quot;椛のスターレイル遊び&amp;quot; which translates roughly as &amp;quot;Momiji plays Honkai: Star Rail Adventures,&amp;quot; a reference to a Japanese role-playing game. Some have blamed the ban wave on the malfunctions of YouTube&#039;s AI-powered moderation system.&amp;lt;ref&amp;gt;{{Cite web |last=Binder |first=Matt |title=Big YouTube channels are being banned. YouTubers are blaming AI. |url=https://mashable.com/article/big-youtube-channels-terminated-creators-blame-ai |website=Mashable |date=4 Nov 2025 |access-date=2 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20260221125020/https://mashable.com/article/big-youtube-channels-terminated-creators-blame-ai |archive-date=21 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===API restrictions===&lt;br /&gt;
In June 2023, YouTube forced Matt Wright, maintainer of the YouTube Metadata tool, to remove the exporting feature which let people export YouTube metadata such as video descriptions into a file. This did not include the videos themselves. It can be assumed that this is the &amp;quot;tip of an iceberg&amp;quot; and YouTube made many such requests without them being publicly documented.&amp;lt;ref&amp;gt;{{Cite web |last=Ingram |first=Benjamin |title=Export Feature? #150 |url=https://github.com/mattwright324/youtube-metadata/discussions/150 |website=[[GitHub]] |date=5 Jun 2023 |access-date=12 Apr 2026 |url-status=live |archive-url=http://web.archive.org/web/20251214094758/https://github.com/mattwright324/youtube-metadata/discussions/150 |archive-date=14 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Prevention of offline video preservation (downloading)===&lt;br /&gt;
Creating permanent local copies of videos is strongly discouraged by YouTube.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Vsauce Answers the 100 Most Googled Questions {{!}} WIRED (timestamps 7:20 and 8:57) |url=https://www.youtube.com/watch?v=gkojLslXg5M |website=YouTube |date=19 Jun 2017 |access-date=12 Apr 2026 |url-status=live |archive-url=https://preservetube.com/watch?v=gkojLslXg5M |archive-date=31 Jan 2024}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Schmoyer |first=Tim |title=How To Legally Download YouTube Videos |url=https://www.youtube.com/watch?v=IVPriyYwd-E |website=YouTube |date=18 Aug 2016 |access-date=12 Apr 2026 |url-status=live |archive-url=https://preservetube.com/watch?v=IVPriyYwd-E |archive-date=5 Mar 2026}}&amp;lt;!-- NOTE: Clickbait; it is an advertisement for &amp;quot;YouTube Red&amp;quot;, the earlier name of &amp;quot;YouTube Premium&amp;quot;, and only shows the built-in &amp;quot;downloading&amp;quot; feature of YouTube Studio that lets channel owners download only their own uploaded videos. Used to prove the point about YouTube&#039;s hostility. --&amp;gt;&amp;lt;/ref&amp;gt; YouTube is taking measures to prevent people from backing up videos locally. From a YouTube help center article:&lt;br /&gt;
&amp;lt;blockquote&amp;gt;In order to protect the YouTube community, we may prevent signed-out users from accessing YouTube videos when they&#039;re attempting to download material for offline use.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Troubleshoot YouTube video errors |url=https://support.google.com/youtube/answer/3037019#zippy=%2Ccheck-that-youre-signed-in-to-youtube |website=[[Google]] |date= |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260323195048/https://support.google.com/youtube/answer/3037019 |archive-date=23 Mar 2026}}&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is not specified what preventing offline use is intended to protect against.&lt;br /&gt;
&lt;br /&gt;
YouTube also regularly purges tutorial videos that show how to create local copies of videos.&amp;lt;ref&amp;gt;{{Cite web |author=ifxman |title=How To Download Convert YouTube Videos 2 Anything |url=http://www.youtube.com/watch?v=xkyqFiUrhTc |website=YouTube |date=26 Apr 2008 |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20120813001114/http://www.youtube.com/watch?v=xkyqFiUrhTc |archive-date=13 Aug 2012}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=Ritace40 |title=How to download youtube videos without any software |url=https://www.youtube.com/watch?v=0XLLOij1GSQ |website=YouTube |date=18 Dec 2011 |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20120713154012/https://www.youtube.com/watch?v=0XLLOij1GSQ |archive-date=13 Jul 2012}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=MKBHD |title=Download Youtube Videos Free -- No Software! |url=https://www.youtube.com/watch?v=5xf6uukCHmk |website=YouTube |date=18 Aug 2010 |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20121003225255/https://www.youtube.com/watch?v=5xf6uukCHmk |archive-date=3 Oct 2012}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Instead, YouTube wants its users to pay monthly for its subscription service, YouTube Premium, to have any form of offline access to videos. YouTube Premium comes with a &amp;quot;download&amp;quot; feature, but it is useless for long-term archival of videos given that it only lets users store temporary local copies of YouTube videos that are forcibly deleted after 29 days. In addition, to thwart any permanent preservation, the videos are stored with [[Data lock-in#Videos downloaded inside the YouTube app|data lock-in]] and proprietary encoding in a format only recognized by the YouTube app, to prevent local copying.&amp;lt;ref&amp;gt;{{Cite web |author=Mental Outlaw |title=Google is Locking Down Android (timestamp 6:41) |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |website=YouTube |date=29 Aug 2025 |access-date=12 Apr 2026 |url-status=live |archive-url=https://ghostarchive.org/varchive/L1S0SiBuJN8 |archive-date=29 Aug 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author= |title=YouTube videos offline FAQs |url=https://support.google.com/youtube/answer/7381437 |website=[[Google]] |date= |access-date=12 Apr 2026 |url-status=live |archive-url=http://web.archive.org/web/20260207132551/https://support.google.com/youtube/answer/7381437 |archive-date=7 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;VirtualCuriosities&amp;quot;&amp;gt;{{Cite web |last=Santos |first=Noel |title=Warning: Youtube Premium &amp;quot;Downloads&amp;quot; aren&#039;t MP4 Files |url=https://www.virtualcuriosities.com/articles/3383/warning-youtube-premium-downloads-arent-mp4-files |website=Virtual Curiosities |date=7 Dec 2024 |access-date=12 Apr 2026 |url-status=live |archive-url=http://web.archive.org/web/20251126100053/https://www.virtualcuriosities.com/articles/3383/warning-youtube-premium-downloads-arent-mp4-files |archive-date=26 Nov 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author= |title=What&#039;s Wrong with YouTube |url=https://www.gnu.org/philosophy/whats-wrong-with-youtube.html |website=GNU |date= |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260216041246/https://www.gnu.org/philosophy/whats-wrong-with-youtube.html |archive-date=16 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=squabbledMC |title=YouTube downloads not working - Megathread |url=https://old.reddit.com/r/cobalt_tools/comments/1lhmlqx/youtube_downloads_not_working_megathread/ |website=[[Reddit]] |date=22 Jun 2025 |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260322015608/https://old.reddit.com/r/cobalt_tools/comments/1lhmlqx/youtube_downloads_not_working_megathread/ |archive-date=22 Mar 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
While YouTube can advertise its Premium service as technically allowing &amp;quot;downloading&amp;quot;, the deceptive marketing comes from exploiting the fact that the user expects so-called &amp;quot;downloading&amp;quot; to result in a file stored in the web browser&#039;s Download folder, accessible from other software, instead of the [[data lock-in]] that YouTube Premium actually has. The 29-day storage limit coupled with data lock-in render the built-in &amp;quot;downloading&amp;quot; feature of YouTube Premium useless for any long-term archival.&amp;lt;ref name=&amp;quot;VirtualCuriosities&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Downloading local copies of YouTube videos through &amp;quot;unofficial&amp;quot; and &amp;quot;unapproved&amp;quot; means is the only recourse against the loss of Internet history caused by videos being unpublished by channel owners or YouTube, and against a future shutdown of YouTube. As of 2026, there is no certainty that YouTube will be operating by the year 2050, for instance.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Whenever I tell people that we need to plan for the day when YouTube goes offline, I mostly receive weird reactions. It seems to be the case that people can&#039;t think of YouTube being gone. Unfortunately, I&#039;m convinced that most people will face the day when we lose this enormous library of videos. — Karl Voit&amp;lt;ref&amp;gt;{{Cite web |last=Voit |first=Karl |title=My Dependencies on the Cloud |url=https://karl-voit.at/cloud-dependencies/ |website=Karl Voit |date= |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260216041319/https://karl-voit.at/cloud-dependencies/ |archive-date=16 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Videos can disappear from YouTube for a variety of reasons. In fact, less than half of the videos that were publicly available on YouTube as of 2010 were still available as of 2021, according to a long-time study from a sample of 105 million videos.&amp;lt;ref&amp;gt;{{Cite web |author=themadprogramer |title=YouTube was made for Reuploads |url=https://datahorde.org/youtube-was-made-for-reuploads/ |website=Data Horde |date=28 Jul 2021 |access-date=12 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20220714224416/https://datahorde.org/youtube-was-made-for-reuploads/ |archive-date=14 Jul 2022}}&amp;lt;/ref&amp;gt; Sometimes, channel owners decide to &amp;quot;move on&amp;quot; and delete (or otherwise unpublish) their entire history of uploads. Sometimes, videos contain something Google doesn&#039;t like for whatever reason and they take them down, one example being &amp;quot;Android is losing a big feature&amp;quot; by comedian Sam Tucker (SAMTIME).&amp;lt;ref&amp;gt;{{Cite web |author=SAMTIME |title=Android is losing a big feature |url=https://www.youtube.com/watch?v=dfccCB2Vz-M |website=YouTube |date=18 Sep 2024 |access-date= |url-status=dead |archive-url=https://preservetube.com/watch?v=dfccCB2Vz-M |archive-date=19 Sep 2024}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Sometimes YouTube&#039;s community guidelines grow stricter and retroactively affect existing content, with entire channels being taken down due to strikes on only a few videos, resulting in the collateral loss of all other videos, with one famous example being Mumkey Jones.&amp;lt;ref&amp;gt;{{Cite web |author=j aubrey |title=Mumkey Jones: YouTube&#039;s Most Wanted |url=https://www.youtube.com/watch?v=Te8-ETSDgcs |website=YouTube |date=21 Jan 2019 |access-date=12 Apr 2026 |url-status=live |archive-url=https://ghostarchive.org/varchive/Te8-ETSDgcs |archive-date=23 Jan 2024}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Forced sign-in===&lt;br /&gt;
Since 2025, the Android app and the web-app sometimes [[Forced account|require users to login]] to their Google accounts to &amp;quot;confirm you&#039;re not a bot&amp;quot;.{{Citation needed}} They could require solving a [[CAPTCHA]], but they don&#039;t that. This, paired with [[Google#Phone number requirement for new accounts|Google&#039;s phone-number 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;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:YouTube| ]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Category:Google_Play_Store&amp;diff=54771</id>
		<title>Category:Google Play Store</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Category:Google_Play_Store&amp;diff=54771"/>
		<updated>2026-05-25T13:09:18Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Google|Play]]&lt;br /&gt;
[[Category:App stores]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Category:Google_Pixel&amp;diff=54770</id>
		<title>Category:Google Pixel</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Category:Google_Pixel&amp;diff=54770"/>
		<updated>2026-05-25T13:08:52Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Google|Pixel]]&lt;br /&gt;
[[Category:Smartphones]]&lt;br /&gt;
[[Category:Earphones]]&lt;br /&gt;
[[Category:Smartwatches]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Category:Google_Nest&amp;diff=54769</id>
		<title>Category:Google Nest</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Category:Google_Nest&amp;diff=54769"/>
		<updated>2026-05-25T13:08:30Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Google|Nest]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Search&amp;diff=54768</id>
		<title>Google Search</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Search&amp;diff=54768"/>
		<updated>2026-05-25T13:07:48Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|ReleaseYear=1998&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Service&lt;br /&gt;
|Category=Search Engine&lt;br /&gt;
|Logo=Google.webp&lt;br /&gt;
|Website=https://www.google.com&lt;br /&gt;
|Description=Google Search is the most used search engine in the world known for controversies involving integration of ads, AI, and the decline of platform&#039;s quality over time&lt;br /&gt;
}}&lt;br /&gt;
Google Search is a search engine created and developed by [[Google|Google LLC]]. It was released on September 27th, 1998.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
*&#039;&#039;&#039;User privacy:&#039;&#039;&#039; Google Search stores long-term cookies to save user&#039;s preferences, something that has raised privacy concerns.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;User freedom:&#039;&#039;&#039; Some features such as disabling AI overview or AI mode cannot be disabled. The user cannot change the ranking of results other than by crafting queries and changing keywords. Google adds positive bias for ads and partner sites such as [[Reddit]].&amp;lt;ref&amp;gt;{{Cite web |title=Expanding our Partnership with Google |url=https://redditinc.com/news/reddit-and-google-expand-partnership |url-status=live |website=[[Reddit]] |date=22 Feb 2024 |archive-url=https://web.archive.org/web/20251213184611/https://redditinc.com/news/reddit-and-google-expand-partnership |archive-date=2025-12-13 |access-date=12 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=An expanded partnership with Reddit |url=https://blog.google/company-news/inside-google/company-announcements/expanded-reddit-partnership/ |url-status=live |website=Google Blog |first=Rajan |last=Patel |date=22 Feb 2024 |archive-url=https://web.archive.org/web/20260112081436/https://blog.google/company-news/inside-google/company-announcements/expanded-reddit-partnership/ |archive-date=2026-01-12 |access-date=12 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Business model:&#039;&#039;&#039; Google Search engine gets revenue from ads shown at the top of search results.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Market control:&#039;&#039;&#039; Google Search engine is the most used search engine in the world. According to StatCounter, Google Search has a 90.2% market share as of April 2026.&amp;lt;ref&amp;gt;{{Cite web |publisher=StatCounter |date=Apr 2026 |title=Search Engine Market Share Worldwide |url=https://gs.statcounter.com/search-engine-market-share |url-status=live |archive-url=https://web.archive.org/web/20260518141238/https://gs.statcounter.com/search-engine-market-share |archive-date=2026-05-18 |access-date=21 May 2026 |website=StatCounter}}&amp;lt;/ref&amp;gt; They pay [[Apple]] and [[Mozilla]] to be the default search engine on [[Safari]] and [[Firefox]], respectively.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===Integration of ads in the search engine===&lt;br /&gt;
The search engine didn&#039;t have any ads at the beginning, but since October 2000, Google integrated ads at the top of the search results, being easily differenciable from regular search links. Over time, the platform has modified the hyperlink ads appearence to disguise them better as regular links.&lt;br /&gt;
&lt;br /&gt;
Since 2000, these ads appeared at first in a yellow section, highlighting the hyperlinks inside that section were ads {{Citation needed}}. Later this was modified, and the yellow section was removed and hyperlinks that were ads showed a small &amp;quot;ad&amp;quot; label next to them {{Citation needed}}. In 2022, these labels were removed, and a &amp;quot;Sponsored&amp;quot; section was created. Links in this section have a similar appearence to links that are not ads. &amp;lt;ref&amp;gt;{{Cite web |publisher=ScaleUp Marketing Solutions |date=18 Oct 2022 |title=The word &amp;quot;ad&amp;quot; will no longer appear in Google search advertising, and company names and logos will also be added |url=https://www.linkedin.com/pulse/word-ad-longer-appear-google-search-advertising- |url-status=live |archive-url=https://web.archive.org/web/20260522031237/https://www.linkedin.com/pulse/word-ad-longer-appear-google-search-advertising- |archive-date=2026-05-22 |access-date=22 May 2026 |website=LinkedIn}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Priorization of showing sites with AI-generated content in Search results===&lt;br /&gt;
On January 30th 2026, Louis Rossmann uploaded a video on [[YouTube]] &amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=II2QF9JwtLc&amp;lt;/ref&amp;gt; evidencing how Google Search SEO (Search Engine Optimization) has been modified to penalize web sites that do not contain AI-generated text. On February 12, he uploaded another video, showing how he managed to make his website the first on the search results page by adding AI-generated text to the site. &amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=6uKZ84zwJI0&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Presence of malicious websites on search results===&lt;br /&gt;
&lt;br /&gt;
===AI Overview (2023)===&lt;br /&gt;
In May 2023, Google announced Search Generative Experience (SGE) for Google Search. AI Overview was released in May 2024 in the US, as an AI-powered feature that appears at the top of search results, showing an AI-generated summary of the search query. &lt;br /&gt;
&lt;br /&gt;
It has been critiziced for giving false information due to [[wikipedia:Hallucination_(artificial_intelligence)|hallucinations]] that even involved into suggesting to perform harmful activities.&amp;lt;ref&amp;gt;{{Cite web |last=McMahon|first=Lov |last2=Kleinman |first2=Zoe |date=24 May 2024 |title=Glue pizza and eat rocks: Google AI search errors go viral |url=https://www.bbc.com/news/articles/cd11gzejgz4o  |url-status=live |archive-url=https://web.archive.org/web/20241008234240/https://www.bbc.com/news/articles/cd11gzejgz4o |archive-date=2024-10-08|access-date=25 May 2026 |website=BBC}}&amp;lt;/ref&amp;gt; There&#039;s also criticism for its energy and resource consumption and how these summaries prevent people to access to web sites in order to get the information.&lt;br /&gt;
&lt;br /&gt;
The implementation of this feature has ended in some cases involving lawsuits due to the misinformation provided by hallucinations&amp;lt;ref&amp;gt;{{Cite web |last=Martin|first=Emmy |date=13 Jun 2025|title=Minnesota Solar Company Sues Google Over AI Summary |url=https://www.govtech.com/public-safety/minnesota-solar-company-sues-google-over-ai-summary |url-status=live|access-date=25 May 2026 |website=Government Technology}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://storage.courtlistener.com/recap/gov.uscourts.mnd.225722/gov.uscourts.mnd.225722.1.1.pdf&amp;lt;/ref&amp;gt; and site owners suing Google for copyright infringements and antitrust practices. &amp;lt;ref&amp;gt;{{Cite web |last=Meen|first=Andy |date=14 Sep 2025|title=Why Rolling Stone Owner Penske Media Just Declared War On Google|url=https://www.forbes.com/sites/andymeek/2025/09/14/why-rolling-stone-owner-penske-media-just-declared-war-on-google/ |url-status=live  |access-date=25 May 2026 |website=Forbes}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There&#039;s no official method to completely disable AI Overview from search results. However, adding &amp;lt;code&amp;gt;-ai&amp;lt;/code&amp;gt; at the end of search queries prevents the AI Overview to appear. &amp;lt;ref&amp;gt;{{Cite web |last=Stimac|first=Blake |date=20 Apr 2026 |title=How to Tell Google&#039;s AI Features to Leave You Alone, Once and for All |url=https://www.cnet.com/tech/services-and-software/how-to-tell-googles-ai-features-to-leave-you-alone-once-and-for-all/ |url-status=live |archive-url=https://web.archive.org/web/20260524051148/https://www.cnet.com/tech/services-and-software/how-to-tell-googles-ai-features-to-leave-you-alone-once-and-for-all/ |archive-date=2026-05-24 |access-date=25 May 2026 |website=CNet}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===AI Mode (2025)===&lt;br /&gt;
AI mode is a feature introduced for Google Search in 2025 as an alternative form to search information on the web. It uses a chat interface and [[artificial intelligence]] to search the web and find the content that might be relevant for the user. Like AI overview, there&#039;s no official way to disable this feature.&lt;br /&gt;
&lt;br /&gt;
In 2026, Google will introduce integrated ads into AI overview and AI mode. These ads might appear in the conversations with Google&#039;s AIs with a similar appearence  to a regular answer, but they contain a small &amp;quot;sponsored&amp;quot; tag at the top of the reply, something that might be hard do identify at first glance. This form of integration has raised privacy and concerns about the potential usage of AI for manipulation and potential integrations that might make nearly impossible to differentiate between content that is and isn&#039;t an ad. &amp;lt;ref&amp;gt;{{Cite web |last=Hawkins|first=Josh|date=21 May 2026|title=Google&#039;s new AI search ads are designed to look like helpful answers |url=https://www.makeuseof.com/googles-new-ai-search-will-have-ads-hidden-in-your-answers/ |url-status=live |archive-url=https://web.archive.org/web/20260522223816/https://www.makeuseof.com/googles-new-ai-search-will-have-ads-hidden-in-your-answers/ |archive-date=2026-05-22 |access-date=22 May 2026 |website=Make Use Of}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Additional AI integrations in Google Search (2026)===&lt;br /&gt;
On May 19th, 2026, during the Google I/O were announced additional AI integrations for the search engine. These integrations involve modifications of the Search box and integration of [[Google Gemini]] Flash 3.5, predictive algorithms and the integration of &amp;quot;Search Agents&amp;quot;, customizable AI agents dedicated to operate and search in user&#039;s behalf&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;.&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; &lt;br /&gt;
&lt;br /&gt;
These announcements sparked controversies involving AI mistakes, privacy concerns, integration of unnecessary features, environmental impact, reduction of human visits on websites and the possible control over the results a user can see.&lt;br /&gt;
&lt;br /&gt;
==Lawsuit==&lt;br /&gt;
===United States vs. Google (2020)===&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DuckDuckGo]]&lt;br /&gt;
*[[Bing]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google| ]]&lt;br /&gt;
[[Category:Products]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=AirPods_Max_moisture_issue&amp;diff=54767</id>
		<title>AirPods Max moisture issue</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=AirPods_Max_moisture_issue&amp;diff=54767"/>
		<updated>2026-05-25T13:05:18Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Consumer-impact summary==&lt;br /&gt;
Links necessary to make this article whole:&lt;br /&gt;
&lt;br /&gt;
https://discussions.apple.com/thread/252267540?sortBy=rank&lt;br /&gt;
&lt;br /&gt;
https://web.archive.org/web/20250119175742/https://www.reddit.com/r/Airpodsmax/comments/s64ztx/condensation_broke_my_device_apple_says_theres/&lt;br /&gt;
&lt;br /&gt;
[[AirPods]] summary&lt;br /&gt;
&lt;br /&gt;
- Left4Code&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
{{Ph-C-Inc}}&lt;br /&gt;
&lt;br /&gt;
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
===Example incident one (&#039;&#039;date&#039;&#039;)===&lt;br /&gt;
{{Main|link to the main CR Wiki article}}&lt;br /&gt;
Short summary of the incident (could be the same as the summary preceding the article).&lt;br /&gt;
===Example incident two (&#039;&#039;date&#039;&#039;)===&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
==Products==&lt;br /&gt;
{{Ph-C-P}}&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
{{Ph-C-SA}}&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Apple|AirPods]]&lt;br /&gt;
[[Category:Articles in need of additional work]]&lt;br /&gt;
[[Category:Articles with verification concerns or other deficiencies]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=AirPods_connection_vulnerability&amp;diff=54766</id>
		<title>AirPods connection vulnerability</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=AirPods_connection_vulnerability&amp;diff=54766"/>
		<updated>2026-05-25T13:04:38Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&lt;br /&gt;
{{Main|AirPods}}&lt;br /&gt;
&lt;br /&gt;
==Consumer-impact summary==&lt;br /&gt;
Links necessary to make this article whole:&lt;br /&gt;
&lt;br /&gt;
https://nvd.nist.gov/vuln/detail/CVE-2024-27867&lt;br /&gt;
&lt;br /&gt;
https://support.apple.com/en-us/120907&lt;br /&gt;
&lt;br /&gt;
[[AirPods]] summary&lt;br /&gt;
&lt;br /&gt;
- Left4code will gather more later&lt;br /&gt;
&lt;br /&gt;
All Sources need to make sweet article:&lt;br /&gt;
&lt;br /&gt;
- https://www.intego.com/mac-security-blog/apple-updates-airpods-and-beats-firmware-to-fix-headphone-hijacking-bug/&lt;br /&gt;
&lt;br /&gt;
- https://nvd.nist.gov/vuln/detail/CVE-2024-27867&lt;br /&gt;
&lt;br /&gt;
- https://seclists.org/fulldisclosure/2024/Jul/2&lt;br /&gt;
&lt;br /&gt;
- https://web.archive.org/web/20260224082150/https://support.apple.com/en-us/120907&lt;br /&gt;
&lt;br /&gt;
make sick article.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
{{Ph-C-Inc}}&lt;br /&gt;
&lt;br /&gt;
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
===Example incident one (&#039;&#039;date&#039;&#039;)===&lt;br /&gt;
{{Main|link to the main CR Wiki article}}&lt;br /&gt;
Short summary of the incident (could be the same as the summary preceding the article).&lt;br /&gt;
===Example incident two (&#039;&#039;date&#039;&#039;)===&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
==Products==&lt;br /&gt;
{{Ph-C-P}}&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
{{Ph-C-SA}}&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Apple|AirPods]]&lt;br /&gt;
[[Category:Articles in need of additional work]]&lt;br /&gt;
[[Category:Articles with verification concerns or other deficiencies]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Category:Google_Pixel&amp;diff=54765</id>
		<title>Category:Google Pixel</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Category:Google_Pixel&amp;diff=54765"/>
		<updated>2026-05-25T13:01:52Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Google]]&lt;br /&gt;
[[Category:Smartphones]]&lt;br /&gt;
[[Category:Earphones]]&lt;br /&gt;
[[Category:Smartwatches]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel_Watch&amp;diff=54764</id>
		<title>Google Pixel Watch</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel_Watch&amp;diff=54764"/>
		<updated>2026-05-25T13:00:23Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup}}&lt;br /&gt;
{{ProductLineCargo&lt;br /&gt;
|ArticleType  = Product&lt;br /&gt;
|Category     = Smartwatches&lt;br /&gt;
|Company      = Google&lt;br /&gt;
|Description  = &lt;br /&gt;
|InProduction = Yes&lt;br /&gt;
|Logo         = Google Pixel Watch.png&lt;br /&gt;
|ReleaseYear  = 2022&lt;br /&gt;
|Website      = https://store.google.com/us/product/pixel_watch_3&lt;br /&gt;
}}&lt;br /&gt;
The &#039;&#039;&#039;[[wikipedia:Google_Pixel#Smartwatches|Pixel Watch]]&#039;&#039;&#039; is a line of smartwatches developed and marketed by [[Google]]. The first-generation Pixel Watch was launched on October 13, 2022, and was first previewed in May 2022 during the Google I/O keynote. It integrated with Fitbit, which Google acquired in 2021. The smartwatches have the Google Assistant built-in and support Google Translate.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
===Repairability===&lt;br /&gt;
No repair options, designed as replacement-only devices.&lt;br /&gt;
&lt;br /&gt;
===Data Privacy Risks===&lt;br /&gt;
Different privacy policies due to the acquisition of Fitbit, in the past there were also data breaches.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
*[[Fitbit Sense and Versa 3 Battery Performance Program]] (2025): The Fitbit Sense and Versa 3 devices have reached their end of support. Google announced its Fitbit Sense and Versa 3 Battery Performance Program to users as a forced software update.&amp;lt;ref&amp;gt;{{Cite web |date=12 Jan 2025 |title=Sense and Versa 3 Battery Performance Program |url=https://support.google.com/fitbit/answer/15763108?hl=en&amp;amp;sjid=8585407520622055107 |url-status=live |archive-url=https://web.archive.org/web/20250717200451/https://support.google.com/fitbit/answer/15763108?hl=en |archive-date=2025-07-17 |access-date=2 Mar 2025 |website=Google Support}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]] (2023): The entire product line does not come with repair options, contrary to other product lines by Google, like with the [[Google Pixel]] smartphone, where spare parts are available and repairs are possible. They are designed as replacement-only devices. No spare parts are available for repair. Even simple repairs like screen replacements are impossible due to unavailable parts, even a year later.&amp;lt;ref&amp;gt;{{Cite web |last=Bhatia |first=Sanuj |date=20 August 2024 |title=Like clockwork, Google triples down on no-repair policy with Pixel Watch 3 |url=https://www.yahoo.com/tech/clockwork-google-triples-down-no-145204592.html |url-status=live |archive-url=http://web.archive.org/web/20250510152921/https://www.yahoo.com/tech/clockwork-google-triples-down-no-145204592.html |archive-date=10 May 2025|access-date=2 Mar 2025 |website=Yahoo tech}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*[[Fitbit user data exposed in wearable device data breach]] (2021): Data breach stemmed from GetHealth, a New York-based health and wellness company that allows users to unify their wearable device, medical device, and app data.&amp;lt;ref&amp;gt;{{Cite web |last=McKeon |first=Jill |date=16 Sep 2021 |title=61M Fitbit, Apple Users Had Data Exposed in Wearable Device Data Breach |url=https://www.techtarget.com/healthtechsecurity/news/366594948/61M-Fitbit-Apple-Users-Had-Data-Exposed-in-Wearable-Device-Data-Breach |url-status=live |archive-url=https://web.archive.org/web/20251112150519/https://www.techtarget.com/healthtechsecurity/news/366594948/61M-Fitbit-Apple-Users-Had-Data-Exposed-in-Wearable-Device-Data-Breach |archive-date=2025-11-12 |access-date=2 Mar 2025 |website=Informa TechTarget}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Products==&lt;br /&gt;
*&#039;&#039;&#039;[https://blog.google/products/pixel/google-pixel-watch/ Google Pixel Watch 1]&#039;&#039;&#039;(2022)&lt;br /&gt;
*&#039;&#039;&#039;[https://blog.google/products/pixel/google-pixel-watch-2/ Google Pixel Watch 2]&#039;&#039;&#039; (2023)&lt;br /&gt;
*&#039;&#039;&#039;[https://blog.google/products/pixel/google-pixel-watch-3/ Google Pixel Watch 3]&#039;&#039;&#039; (2024)&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel| ]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel_Watches_do_not_come_with_repair_options&amp;diff=54763</id>
		<title>Google Pixel Watches do not come with repair options</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel_Watches_do_not_come_with_repair_options&amp;diff=54763"/>
		<updated>2026-05-25T12:57:11Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete|Issue 1= This was originally an incident article about the google pixel watch 3 but this is an issue affecting the whole product line, so it has been renamed and edited to reflect that. Sources are needed to document this issue for all versions of the watch.}}&lt;br /&gt;
{{IncidentCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|StartDate=&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=&lt;br /&gt;
|ProductLine=Google Pixel&lt;br /&gt;
|Product=&lt;br /&gt;
|ArticleType=Prooduct&lt;br /&gt;
|Type=&lt;br /&gt;
|Description=&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;&#039;Google Pixel Watch&#039;&#039;&#039; is a smartwatch product line made by [[Google]]. The devices come with no warranty for damages and maintain a replacement-only policy for consumers. There are no spare parts made available for the devices.&amp;lt;ref&amp;gt;{{Cite web |last=Amadeo |first=Ron |date=15 Sep 2023 |title=Google says it can’t fix Pixel Watches, please just buy a new one |url=https://arstechnica.com/gadgets/2023/09/11-months-after-launch-googles-pixel-watch-still-has-no-path-to-repair/ |url-status=live |access-date=25 Mar 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20250724185728/https://arstechnica.com/gadgets/2023/09/11-months-after-launch-googles-pixel-watch-still-has-no-path-to-repair/ |archive-date=24 Jul 2025}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
This is contrary to other product lines by Google, like with the [[Google Pixel]] smartphone, where spare parts are available and repairs are possible.&amp;lt;ref&amp;gt;{{Cite web |title=Genuine Google Pixel Parts and Repair Kits |url=https://www.ifixit.com/Parts/Google_Phone |url-status=live |access-date=25 Mar 2025 |website=iFixit |archive-url=http://web.archive.org/web/20260125180230/https://www.ifixit.com/Parts/Google_Phone |archive-date=25 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=Get your Pixel phone repaired |url=https://support.google.com/pixelphone/answer/9004345 |url-status=live |access-date=25 Mar 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20260105214743/https://support.google.com/pixelphone/answer/9004345 |archive-date=5 Jan 2026}}&amp;lt;/ref&amp;gt; Instead, customers are encouraged to look at replacement options, not at repair options.&amp;lt;ref&amp;gt;{{Cite web |last=Song |first=Victoria |date=15 Sep 2023 |title=Google won’t repair cracked Pixel Watch screens |url=https://www.theverge.com/23874281/google-pixel-watch-cracks-no-repairs-warranty |url-status=live |access-date=25 Mar 2025 |website=The Verge |archive-url=http://web.archive.org/web/20251217215925/https://www.theverge.com/23874281/google-pixel-watch-cracks-no-repairs-warranty |archive-date=17 Dec 2025}}&amp;lt;/ref&amp;gt; A common repair for smartwatches is replacing the screen of the device, which can be done in a number of steps with the right parts available.&amp;lt;ref&amp;gt;{{Cite web |last=Schnabelrauch |first=Dominik |date=23 Jun 2024 |title=Google Pixel Watch Screen Replacement |url=https://it.ifixit.com/Guida/Google+Pixel+Watch+Screen+Replacement/160350 |url-status=live |access-date=25 Mar 2025 |website=iFixit |archive-url=http://web.archive.org/web/20250708172855/https://it.ifixit.com/Guida/Google+Pixel+Watch+Screen+Replacement/160350 |archive-date=8 Jul 2025}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==Google maintains replacement-only for consumers==&lt;br /&gt;
The parts however are not made available, which surprises customers as it does not give them many options if not under warranty.&amp;lt;ref&amp;gt;{{Cite web |date=13 Oct 2022 |title=I broke my Pixel Watch screen, but it simply cannot ever be replaced ? |url=https://support.google.com/googlepixelwatch/thread/183746659 |url-status=live |access-date=25 Mar 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20250427184555/https://support.google.com/googlepixelwatch/thread/183746659 |archive-date=27 Apr 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=10 Dec 2022 |title=Brand new Pixel watch, dropped once from waist height and screen shattered |url=https://support.google.com/googlepixelwatch/thread/192218456 |url-status=live |access-date=25 Mar 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20250505003304/https://support.google.com/googlepixelwatch/thread/192218456 |archive-date=5 May 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=4 May 2023 |title=What can I do if my Google Pixel Watch is cracked and I haven&#039;t had it a year. What can I do? |url=https://support.google.com/googlepixelwatch/thread/214139119 |url-status=live |access-date=25 Mar 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20250505054949/https://support.google.com/googlepixelwatch/thread/214139119 |archive-date=5 May 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=20 Jun 2023 |title=Pixel watch cracked screen. |url=https://support.google.com/googlepixelwatch/thread/221719013 |url-status=live |access-date=25 Mar 2025 |website=Google |archive-url=http://web.archive.org/web/20250428223818/https://support.google.com/googlepixelwatch/thread/221719013 |archive-date=28 Apr 2025}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===Google&#039;s response===&lt;br /&gt;
Customer support mentions that physical damage is not covered by warranty, so the advice for customers is to consult their own accidental damage protection if they have it on their purchase.&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
[https://www.youtube.com/watch?v=m8_IlmqqJyE Google admits to manufacturing unrepairable junk], Louis Rossmann, original video on youtube.com ([https://preservetube.com/watch?v=m8_IlmqqJyE Archived])&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel|Watch]]&lt;br /&gt;
[[Category:Right to repair]]&lt;br /&gt;
[[Category:Articles based on videos]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel_Watch&amp;diff=54762</id>
		<title>Google Pixel Watch</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel_Watch&amp;diff=54762"/>
		<updated>2026-05-25T12:56:54Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup}}&lt;br /&gt;
{{ProductLineCargo&lt;br /&gt;
|ArticleType  = Product&lt;br /&gt;
|Category     = Smartwatches&lt;br /&gt;
|Company      = Google&lt;br /&gt;
|Description  = &lt;br /&gt;
|InProduction = Yes&lt;br /&gt;
|Logo         = Google Pixel Watch.png&lt;br /&gt;
|ReleaseYear  = 2022&lt;br /&gt;
|Website      = https://store.google.com/us/product/pixel_watch_3&lt;br /&gt;
}}&lt;br /&gt;
The &#039;&#039;&#039;[[wikipedia:Google_Pixel#Smartwatches|Pixel Watch]]&#039;&#039;&#039; is a line of smartwatches developed and marketed by [[Google]]. The first-generation Pixel Watch was launched on October 13, 2022, and was first previewed in May 2022 during the Google I/O keynote. It integrated with Fitbit, which Google acquired in 2021. The smartwatches have the Google Assistant built-in and support Google Translate.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
===Repairability===&lt;br /&gt;
No repair options, designed as replacement-only devices.&lt;br /&gt;
&lt;br /&gt;
===Data Privacy Risks===&lt;br /&gt;
Different privacy policies due to the acquisition of Fitbit, in the past there were also data breaches.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
*[[Fitbit Sense and Versa 3 Battery Performance Program]] (2025): The Fitbit Sense and Versa 3 devices have reached their end of support. Google announced its Fitbit Sense and Versa 3 Battery Performance Program to users as a forced software update.&amp;lt;ref&amp;gt;{{Cite web |date=12 Jan 2025 |title=Sense and Versa 3 Battery Performance Program |url=https://support.google.com/fitbit/answer/15763108?hl=en&amp;amp;sjid=8585407520622055107 |url-status=live |archive-url=https://web.archive.org/web/20250717200451/https://support.google.com/fitbit/answer/15763108?hl=en |archive-date=2025-07-17 |access-date=2 Mar 2025 |website=Google Support}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]] (2023): The entire product line does not come with repair options, contrary to other product lines by Google, like with the [[Google Pixel]] smartphone, where spare parts are available and repairs are possible. They are designed as replacement-only devices. No spare parts are available for repair. Even simple repairs like screen replacements are impossible due to unavailable parts, even a year later.&amp;lt;ref&amp;gt;{{Cite web |last=Bhatia |first=Sanuj |date=20 August 2024 |title=Like clockwork, Google triples down on no-repair policy with Pixel Watch 3 |url=https://www.yahoo.com/tech/clockwork-google-triples-down-no-145204592.html |url-status=live |archive-url=http://web.archive.org/web/20250510152921/https://www.yahoo.com/tech/clockwork-google-triples-down-no-145204592.html |archive-date=10 May 2025|access-date=2 Mar 2025 |website=Yahoo tech}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*[[Fitbit user data exposed in wearable device data breach]] (2021): Data breach stemmed from GetHealth, a New York-based health and wellness company that allows users to unify their wearable device, medical device, and app data.&amp;lt;ref&amp;gt;{{Cite web |last=McKeon |first=Jill |date=16 Sep 2021 |title=61M Fitbit, Apple Users Had Data Exposed in Wearable Device Data Breach |url=https://www.techtarget.com/healthtechsecurity/news/366594948/61M-Fitbit-Apple-Users-Had-Data-Exposed-in-Wearable-Device-Data-Breach |url-status=live |archive-url=https://web.archive.org/web/20251112150519/https://www.techtarget.com/healthtechsecurity/news/366594948/61M-Fitbit-Apple-Users-Had-Data-Exposed-in-Wearable-Device-Data-Breach |archive-date=2025-11-12 |access-date=2 Mar 2025 |website=Informa TechTarget}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Products==&lt;br /&gt;
*&#039;&#039;&#039;[https://blog.google/products/pixel/google-pixel-watch/ Google Pixel Watch 1]&#039;&#039;&#039;(2022)&lt;br /&gt;
*&#039;&#039;&#039;[https://blog.google/products/pixel/google-pixel-watch-2/ Google Pixel Watch 2]&#039;&#039;&#039; (2023)&lt;br /&gt;
*&#039;&#039;&#039;[https://blog.google/products/pixel/google-pixel-watch-3/ Google Pixel Watch 3]&#039;&#039;&#039; (2024)&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel|Watch]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel_Buds_%22Touch_and_Hold%22_discontinuation&amp;diff=54761</id>
		<title>Google Pixel Buds &quot;Touch and Hold&quot; discontinuation</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel_Buds_%22Touch_and_Hold%22_discontinuation&amp;diff=54761"/>
		<updated>2026-05-25T12:55:09Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ToneWarning}}{{Incomplete|Issue 1=Citations not properly formatted|Issue 2=More info with more in-text citations}}&lt;br /&gt;
{{IncidentCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|StartDate=2024&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=Active, Pending Resolution, Resolved, Unresolved&lt;br /&gt;
|ProductLine=Pixel&lt;br /&gt;
|Product=Google Pixel Buds&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Type=Accessibility&lt;br /&gt;
|Description=With an update, Google removed an accessibility feature from the Pixel Buds.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Google displays an example of a [[Retroactively amended purchases|retroactively amended purchase]] by removing an accessibility feature of the [[Google Pixel Buds|Pixel Buds]] and failing to offer a reasonable alternative to customers who rely on it.&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
Google Pixel Buds are a line of Bluetooth earphones that integrate with Android smartphones. The Buds offer standard media and noise isolation controls via a touch sensitive surface.&lt;br /&gt;
&lt;br /&gt;
When the assistant is invoked without speaking to it, it will read out the time and read any unread notifications. On supported apps, the assistant feature could be used for text entry.&lt;br /&gt;
&lt;br /&gt;
==Removal of the &amp;quot;Touch and Hold&amp;quot; Feature==&lt;br /&gt;
In Early September of 2024, Google silently rolled out an update removing the &amp;quot;Touch and Hold&amp;quot; Gesture from the earbuds.&lt;br /&gt;
&lt;br /&gt;
Some users were suggested to ask the Google Assistant to read their notifications when attempting to invoke the gesture.&amp;lt;ref&amp;gt;https://9to5google.com/2024/09/17/pixel-buds-pro-notifications/ ([http://web.archive.org/web/20251214043711/https://9to5google.com/2024/09/17/pixel-buds-pro-notifications/ Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Google&#039;s response==&lt;br /&gt;
In a forum post, Google cited customer feedback for the removal but did not elaborate further. They suggest asking the assistant to read your notifications.&amp;lt;ref&amp;gt;https://support.google.com/assistant/thread/297016719/google-assistant-spoken-notifications-change-on-pixel-buds ([http://web.archive.org/web/20251214042610/https://support.google.com/assistant/thread/297016719/google-assistant-spoken-notifications-change-on-pixel-buds Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer response==&lt;br /&gt;
&lt;br /&gt;
A quick Google search reveals dozens of Reddit posts from owners disappointing by the fact it was removed completely instead of being made a toggleable option&amp;lt;ref&amp;gt;https://redlib.aosus.link/r/GooglePixel/comments/1fleu1g/google_is_taking_away_the_touch_and_hold_function/ ([https://web.archive.org/web/20260303183217/https://redlib.aosus.link/r/GooglePixel/comments/1fleu1g/google_is_taking_away_the_touch_and_hold_function/ Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://redlib.aosus.link/r/pixelbuds/comments/1fleksj/i_got_the_dreaded_touch_and_hold_is_going_away/ ([https://web.archive.org/web/20260303183433/https://redlib.aosus.link/r/pixelbuds/comments/1fleksj/i_got_the_dreaded_touch_and_hold_is_going_away/ Archived])&amp;lt;/ref&amp;gt;, some are looking for workarounds.&amp;lt;ref&amp;gt;https://redlib.aosus.link/r/pixelbuds/comments/1imf98p/anyone_tried_taskerautomate_to_mimic_touch_and/ ([https://web.archive.org/web/20260303183735/https://redlib.aosus.link/r/pixelbuds/comments/1imf98p/anyone_tried_taskerautomate_to_mimic_touch_and/ Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://redlib.aosus.link/r/pixelbuds/comments/1fefa3i/touch_and_hold_wont_read_notifications_anymore/ ([https://web.archive.org/web/20260303184019/https://redlib.aosus.link/r/pixelbuds/comments/1fefa3i/touch_and_hold_wont_read_notifications_anymore/ Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Google Pixel|Buds]]&lt;br /&gt;
[[Category:Retroactively amended purchase]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel_6a_Battery_Performance_Program&amp;diff=54760</id>
		<title>Google Pixel 6a Battery Performance Program</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel_6a_Battery_Performance_Program&amp;diff=54760"/>
		<updated>2026-05-25T12:54:15Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{IncidentCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|StartDate=2 July 2025&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=Active&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|Product=Pixel 6a&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Type=Forced Migration&lt;br /&gt;
|Description=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Google Pixel 6a&#039;&#039;&#039; is an [[Android]] smartphone designed, developed and marketed by [[Google]]. It was released on July 28, 2022. Android 16 is expected to be the last version supported with security updates expected to end sometime in 2027.&amp;lt;ref&amp;gt;{{Cite web |title=PiFixel 6a end of life date |url=https://endoflife.date/pixel |url-status=live |access-date=2025-07-03 |website=endoflife.date |archive-url=http://web.archive.org/web/20260118201513/https://endoflife.date/pixel |archive-date=18 Jan 2026}}&amp;lt;/ref&amp;gt; On July 2, 2025, Google announced its Pixel 6a Battery Performance Program to users:&lt;br /&gt;
&lt;br /&gt;
[[File:Google Pixel 6a email forced update lowering battery life.png|thumb|right|Email sent to users with a Pixel 6a.]]&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;quot;Google has determined that certain Pixel 6a phones (“Impacted Devices”) require a mandatory software update to reduce the risk of potential battery overheating which could pose a risk to users. The update will enable important battery management features that will reduce battery capacity and charging performance on Impacted Devices after the battery reaches 400 charge cycles. &lt;br /&gt;
&lt;br /&gt;
All Pixel 6a devices will receive a mandatory automatic software update to Android 16, with roll out starting July 8 2025, but only Impacted Devices will receive the battery management features. Some users will see changes sooner than others, because the battery management features activate only after an Impacted Device reaches 400 charge cycles.&lt;br /&gt;
&lt;br /&gt;
We want our customers to have the best possible experience with their products, so users of these Impacted Devices are eligible for support options from Google based upon country of purchase, location, and warranty status, subject to our terms and conditions below. Not all Pixel 6a devices are impacted by the reduction in battery capacity and charging performance. If your device is not impacted, your battery management features will remain the same as before, and you will not be eligible for these support options under this program.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;[https://support.google.com/pixelphone/answer/16340779? https://support.google.com/pixelphone/answer/16340779]&lt;br /&gt;
&lt;br /&gt;
Mirror, via the Wayback Machine: https://web.archive.org/web/20250703210308/https://support.google.com/pixelphone/answer/16340779&lt;br /&gt;
&amp;lt;/ref&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Google pixel needs certain battery replacements for 2025&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Compensation&amp;lt;!-- Written in present tense, as this situation is ongoing as of July 3, 2025. --&amp;gt;==&lt;br /&gt;
&lt;br /&gt;
===Request form sent out to users===&lt;br /&gt;
Google has asked users to provide the IMEI (International Mobile Equipment Identity) number of their Pixel 6a to determine whether their device is an &amp;quot;Impacted Device.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |title=Request a repair, payment, or future discount code |url=https://support.google.com/pixelphone/workflow/16310202 |url-status=live |archive-url=https://web.archive.org/web/20250703211550/https://support.google.com/pixelphone/workflow/16310202 |archive-date=2025-07-03 |access-date=2025-07-03}}&amp;lt;/ref&amp;gt; If the user&#039;s device is an &amp;quot;Impacted Device,&amp;quot; they may choose one of the following:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Free battery replacement&#039;&#039;&#039; (only available in: United States, Canada, United Kingdom, Germany, Singapore, and India)&lt;br /&gt;
*&#039;&#039;&#039;$150 USD&#039;&#039;&#039; (or local equivalent) &#039;&#039;&#039;discount code applicable towards the purchase of another Pixel phone&#039;&#039;&#039; on the Google Store (unavailable in certain countries)&lt;br /&gt;
*&#039;&#039;&#039;$100 USD&#039;&#039;&#039; (or local equivalent)&lt;br /&gt;
&lt;br /&gt;
Compensation&lt;br /&gt;
&lt;br /&gt;
===Payment-processing issues===&lt;br /&gt;
The $100 USD compensation option requires users to process payment through [[wikipedia:Payoneer|Payoneer]], which has many issues:&lt;br /&gt;
&lt;br /&gt;
*Users must provide sensitive personal information including Social Security numbers and bank details&lt;br /&gt;
*A $3 USD processing fee is deducted from the compensation&lt;br /&gt;
*An annual account fee of $29.95 USD is charged if the account balance does not exceed $2,000 USD in transactions within 12 months&amp;lt;nowiki&amp;gt;&amp;lt;ref&amp;gt;&amp;lt;/nowiki&amp;gt;{{Cite web |title=Annual account fee |url=https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |url-status=live |access-date=25 Mar 2025 |website=[[Payoneer]] |archive-url=http://web.archive.org/web/20251129174745/https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |archive-date=29 Nov 2025}}&amp;lt;nowiki&amp;gt;&amp;lt;/ref&amp;gt;&amp;lt;/nowiki&amp;gt; https://support.google.com/pixelphone/workflow/16310202&lt;br /&gt;
*Users report being advised to immediately delete their Payoneer account after receiving compensation to avoid fees&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |title=I have replaced battery in a local shop not supported by Google |url=https://www.reddit.com/r/Pixel4a/comments/1i1e4ds/i_have_replaced_battery_in_a_local_shop_not/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Store-credit limitations===&lt;br /&gt;
[[File:Pixel 6a support page for determining eligibility for program.png|thumb|alt=Screenshot of Google&#039;s compensation options for the Pixel 6a Battery Performance Program.|Screenshot of Google&#039;s compensation options for the Pixel 6a Battery Performance Program.]]&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
===Reimbursement===&lt;br /&gt;
There is an option if you have had your 6a battery replaced at an authorized service center prior to the program announcement.&lt;br /&gt;
[[File:Pixel 6a support page for determining eligibility for program - previously replaced battery.png|thumb|alt=Have you recently had your battery repaired at an authorized repair partner|Have you recently had your battery repaired at an authorized repair partner]]&lt;br /&gt;
&lt;br /&gt;
==Aftermath of software update==&lt;br /&gt;
After the update, users experience a battery cap of 80%, a message in the settings app&#039;s batttery section, Placeholder&lt;br /&gt;
&lt;br /&gt;
===Battery-performance issues===&lt;br /&gt;
Users have reported several issues following the update: Including inability to charge&amp;lt;ref&amp;gt;{{Cite web |date=19 Jul 2025 |title=My pixel 6a doesn&#039;t charge - at all - after update |url=https://old.reddit.com/r/pixel_phones/comments/1m42zn3/my_pixel_6a_doesnt_charge_at_all_after_update/ |url-status=live |archive-url=https://web.archive.org/web/20250721024418/https://old.reddit.com/r/pixel_phones/comments/1m42zn3/my_pixel_6a_doesnt_charge_at_all_after_update/ |archive-date=21 Jul 2025 |access-date=21 Jul 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=18 Jul 2025 |title=Will it charge? |url=https://old.reddit.com/r/Pixel6/comments/1m2xtlt/will_it_charge/ |url-status=live |archive-url=https://web.archive.org/web/20250721024834/https://old.reddit.com/r/Pixel6/comments/1m2xtlt/will_it_charge/ |archive-date=21 Jul 2025 |access-date=21 Jul 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
===Safety issue===&lt;br /&gt;
A Pixel 6a caught fire after the update, indicating the Battery Performance Program isn&#039;t enough to prevent overheating&amp;lt;ref&amp;gt;{{Cite web |last=Whitwam |first=Ryan |date=29 Jul 2025 |title=Another Google Pixel 6a catches fire after battery-nerfing update |url=https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/ |url-status=live |archive-url=https://web.archive.org/web/20250729114215/https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/ |archive-date=29 Jul 2025 |website=Arstechnica}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Battery-replacement complications===&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
===Technical evidence of battery changes===&lt;br /&gt;
The battery voltage has been dropped to below 4.0V after the update, reducing the actual battery capacity to below 60%&amp;lt;ref&amp;gt;{{Cite web |date=10 Jul 2025 |title=Thank you Google for Fast Charging Update /s |url=https://old.reddit.com/r/Pixel6aUsers/comments/1lwf3p5/thank_you_google_for_fast_charging_update_s/ |url-status=live |archive-url=https://web.archive.org/web/20250721025129/https://old.reddit.com/r/Pixel6aUsers/comments/1lwf3p5/thank_you_google_for_fast_charging_update_s/|archive-date=2025-07-21 |access-date=2025-07-20 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Possible technical rationale==&lt;br /&gt;
While Google has not provided detailed technical explanations for the update, there are several known factors about lithium-ion battery aging that could potentially justify such measures:&lt;br /&gt;
&lt;br /&gt;
===Aging lithium-ion batteries===&lt;br /&gt;
Lithium-ion batteries face degradation as they age:&lt;br /&gt;
*Loss of active lithium ions through repeated charge cycles&lt;br /&gt;
*Growth of the Solid Electrolyte Interphase (SEI) layer&lt;br /&gt;
*Physical expansion &amp;amp; contraction stress during charging cycles&lt;br /&gt;
*Potential for dendrite formation in aged cells&lt;br /&gt;
*Increased internal resistance over time&amp;lt;ref&amp;gt;{{Cite web |last=Chu |first=Tien-Fu |last2=Rajendran |first2=Raja |last3=Kuznetsova |first3=Iren |last4=Wang |first4=Gou-Jen |date=31 Mar 2020 |title=High-power, non-enzymatic glucose biofuel cell based on a nano/micro hybrid-structured Au anode |url=https://www.sciencedirect.com/science/article/abs/pii/S0378775320301476 |url-status=live |access-date=22 Mar 2025 |website=ScienceDirect}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Safety considerations===&lt;br /&gt;
Several factors specific to the Pixel 6a situation could indicate that this was a battery safety concern:&lt;br /&gt;
*The device was released in July 2022; many units are approaching 3 years of use&lt;br /&gt;
*The mandatory nature of the update suggests safety implications rather than performance optimization&lt;br /&gt;
*There have been reports of the device spontaneously catching on fire&lt;br /&gt;
===Precedent in mobile phones===&lt;br /&gt;
Similar battery-related interventions have occurred previously; Google&#039;s own Pixel 4a in January of 2025 and Apple&#039;s 2017 iPhone throttling was done to prevent unexpected shutdowns in devices with degraded batteries.&lt;br /&gt;
&lt;br /&gt;
===Potential manufacturing variables===&lt;br /&gt;
Several factors could explain why only certain devices are affected:&lt;br /&gt;
*Different battery suppliers or manufacturing batches&lt;br /&gt;
*Variations in battery cell chemistry or construction&lt;br /&gt;
*Manufacturing date ranges coinciding with specific material supplies&lt;br /&gt;
*Quality control variations between production runs&lt;br /&gt;
&lt;br /&gt;
==Media Articles==&lt;br /&gt;
https://9to5google.com/2025/07/02/pixel-6a-battery-update-details/&lt;br /&gt;
&lt;br /&gt;
https://www.androidauthority.com/pixel-6a-battery-limit-3573411/&lt;br /&gt;
&lt;br /&gt;
https://www.theverge.com/news/697103/google-android16-update-pixel-6a-battery-overheating-fix-july-8&lt;br /&gt;
&lt;br /&gt;
https://9to5google.com/2025/07/02/google-removes-pixel-6a-factory-images/&lt;br /&gt;
&lt;br /&gt;
https://www.techradar.com/phones/google-pixel-phones/the-pixel-6a-will-get-a-mandatory-update-that-will-reduce-battery-capacity-soon-and-other-pixel-phones-could-be-next&lt;br /&gt;
&lt;br /&gt;
==Criticism by community==&lt;br /&gt;
&lt;br /&gt;
#This update is an automatic update &#039;&#039;&#039;users can not opt&#039;&#039;&#039; &#039;&#039;&#039;out&#039;&#039;&#039; of.&lt;br /&gt;
#Despite claim, this update &#039;&#039;&#039;does not prevent&#039;&#039;&#039; the phone from overheating or catching fire, as shown by this user whose Pixel 6a that got the July update, caught fire while charging overnight&amp;lt;ref&amp;gt;{{Cite web |last=Whitwam |first=Ryan |date=29 Jul 2025 |title=Another Google Pixel 6a catches fire after battery-nerfing update |url=https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/?comments-page=1#comments |url-status=live |archive-url=https://web.archive.org/web/20250728172217/https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/ |archive-date=2025-07-28 |access-date=4 Aug 2025 |website=Ars Technica}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=27 Jul 2025 |title=I&#039;m the 3rd one posting this for this month. Pixel 6a caught on fire right next to me on the nightstand. |url=https://old.reddit.com/r/GooglePixel/comments/1ma6hpa/im_the_3rd_one_posting_this_for_this_month_pixel/ |url-status=live |archive-url=https://web.archive.org/web/20250728055102/https://old.reddit.com/r/GooglePixel/comments/1ma6hpa/im_the_3rd_one_posting_this_for_this_month_pixel/ |archive-date=2025-07-28 |access-date=28 Jul 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Restoring battery functionality==&lt;br /&gt;
&lt;br /&gt;
===Replacing the battery===&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
Google has removed all official images for the pixel 6a released prior to the date of this program&#039;s inception.&lt;br /&gt;
&lt;br /&gt;
===Rolling-back Android===&lt;br /&gt;
By editing android-info.txt file, Users are able to bypass the anti-rollback bootloader update and successfully downgrade Android 14 from Android 16&amp;lt;ref&amp;gt;{{Cite web |date=19 Jul 2025 |title=Hey guys! I just rollback to android14 success! |url=https://xdaforums.com/t/hey-guys-i-just-rollback-to-android14-success.4750539/ |url-status=live |archive-url=https://web.archive.org/web/20250721022623/https://xdaforums.com/t/hey-guys-i-just-rollback-to-android14-success.4750539/ |archive-date=21 Jul 2025 |access-date=21 Jul 2025 |website=XDA Developers}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel|Battery Performance Program]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Pixel_4a_Battery_Performance_Program&amp;diff=54759</id>
		<title>Pixel 4a Battery Performance Program</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Pixel_4a_Battery_Performance_Program&amp;diff=54759"/>
		<updated>2026-05-25T12:53:49Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Main|Battery Health Assistance}}&lt;br /&gt;
{{IncidentCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|StartDate=2025-01-06&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=Active&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|Product=Pixel 4a&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Type=Quality&lt;br /&gt;
|Description=The Pixel 4a received a mandatory software update that reduces battery performance for safety, alongside an appeasement offer.&lt;br /&gt;
}}&lt;br /&gt;
The Google Pixel 4a is an Android smartphone designed, developed and marketed by [[Google]]. It was released on August 20, 2020, and reached its end of support on August 5, 2023.&amp;lt;ref&amp;gt;{{Cite web |title=Pixel 4a end of life date |url=https://endoflife.date/pixel |url-status=live |access-date=25 Mar 2025 |website=endoflife.date |archive-url=http://web.archive.org/web/20260220223603/https://endoflife.date/pixel |archive-date=20 Feb 2026}}&amp;lt;/ref&amp;gt; On January 6, 2025, Google announced its Pixel 4a Battery Performance Program to users:&amp;lt;blockquote&amp;gt;&amp;quot;Google has determined that certain Pixel 4a phones require a software update to improve the stability of their battery&#039;s performance. An automatic update to Android 13 will roll out to all Pixel 4a devices starting January 8, 2025. For some devices (&amp;quot;Impacted Devices&amp;quot;), &#039;&#039;&#039;the software update reduces available battery capacity and impacts charging performance.&#039;&#039;&#039; [...] users of these Impacted Devices are eligible for an appeasement from Google.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;https://support.google.com/pixelphone/answer/15701861 ([https://web.archive.org/web/20250107002112/https://support.google.com/pixelphone/answer/15701861 Archived])&amp;lt;/ref&amp;gt;&#039;&#039;&amp;lt;ref&amp;gt;{{Cite web |date=6 Jan 2025 |title=Pixel 4a Battery Performance Program |url=https://support.google.com/pixelphone/answer/15701861 |url-status=deviated |archive-url=https://web.archive.org/web/20250107002112/https://support.google.com/pixelphone/answer/15701861 |archive-date=7 Jan 2025 |access-date=25 Mar 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google pixel needs certain battery replacements for 2025&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Compensation&amp;lt;!-- Written in present tense, as this situation is ongoing as of January 18, 2025. --&amp;gt;==&lt;br /&gt;
&lt;br /&gt;
===Request form sent out to users===&lt;br /&gt;
Google has asked users to provide the IMEI (International Mobile Equipment Identity) number of their Pixel 4a to determine whether their device is an &amp;quot;Impacted Device.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |title=Request a repair, payment, or future discount code |url=https://support.google.com/pixelphone/workflow/15642495 |url-status=live |archive-url=https://web.archive.org/web/20250107002104/https://support.google.com/pixelphone/workflow/15642495 |archive-date=7 Jan 2025 |access-date=25 Mar 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Davis |first=Wes |date=8 Jan 2025 |title=Google’s new Pixel 4A update is going to lower battery life for some owners |url=https://www.theverge.com/2025/1/7/24338566/google-pixel-4a-battery-stability-replacement-reduced-capacity |url-status=live |access-date=25 Mar 2025 |website=The Verge |archive-url=http://web.archive.org/web/20251220031303/https://www.theverge.com/2025/1/7/24338566/google-pixel-4a-battery-stability-replacement-reduced-capacity |archive-date=20 Dec 2025}}&amp;lt;/ref&amp;gt; If the user&#039;s device is an &amp;quot;Impacted Device,&amp;quot; they may choose one of the following:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Free battery replacement&#039;&#039;&#039; (only available in: United States, Canada, United Kingdom, Germany, Singapore, and India)&lt;br /&gt;
*&#039;&#039;&#039;$100 USD&#039;&#039;&#039; (or local equivalent) &#039;&#039;&#039;discount code applicable towards the purchase of another Pixel phone&#039;&#039;&#039; on the Google Store (unavailable in certain countries)&lt;br /&gt;
*&#039;&#039;&#039;$50 USD&#039;&#039;&#039; (or local equivalent)&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Compensation was no longer available after January 6, 2026.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Payment-processing issues===&lt;br /&gt;
The $50 USD compensation option requires users to process payment through [[wikipedia:Payoneer|Payoneer]], which has many issues:&lt;br /&gt;
*Users must provide sensitive personal information including Social Security numbers and bank details&lt;br /&gt;
*A $3 USD processing fee is deducted from the compensation&lt;br /&gt;
*An annual account fee of $29.95 USD is charged if the account balance does not exceed $2,000 USD in transactions within 12 months&amp;lt;ref&amp;gt;{{Cite web |title=Annual account fee |url=https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |url-status=live |archive-url=http://web.archive.org/web/20251129174745/https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |archive-date=29 Nov 2025 |access-date=25 Mar 2025 |website=Payoneer}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Users report being advised to immediately delete their Payoneer account after receiving compensation to avoid fees&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |title=I have replaced battery in a local shop not supported by Google |url=https://www.reddit.com/r/Pixel4a/comments/1i1e4ds/i_have_replaced_battery_in_a_local_shop_not/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250802034226/https://old.reddit.com/r/Pixel4a/ |archive-date=2 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Store-credit limitations===&lt;br /&gt;
The $100 USD Google Store credit option has restrictions:&lt;br /&gt;
*Must be used on full-price devices in most regions&lt;br /&gt;
*Available only for Pixel phone purchases&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
*Cannot be used in conjunction with trade-in offers&lt;br /&gt;
*Users cannot change their compensation choice after selecting this option&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |title=$100 Google Store voucher code cannot be combined with sale price apparently? |url=https://www.reddit.com/r/Pixel4a/comments/1i2zz4g/100_google_store_voucher_code_cannot_be_combined/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250214093659/https://old.reddit.com/r/Pixel4a/comments/1i2zz4g/100_google_store_voucher_code_cannot_be_combined/ |archive-date=14 Feb 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Editing of initial announcement===&lt;br /&gt;
By January 15, 2025 the following edit had been inserted into the original January 6 announcement:&amp;lt;blockquote&amp;gt;&amp;quot;&#039;&#039;&#039;Note:&#039;&#039;&#039; Carefully select your appeasement option as after you choose, you can&#039;t change it. You may have statutory rights available to you under laws of the country where you purchased the device. If available to you, you may alternatively make a claim pursuant to those.&amp;quot;&amp;lt;ref&amp;gt;January 7, 2025, via the Wayback Machine: https://web.archive.org/web/20250107002112/https://support.google.com/pixelphone/answer/15701861&lt;br /&gt;
&lt;br /&gt;
January 15, 2025, via the Wayback Machine: https://web.archive.org/web/20250115045948/https://support.google.com/pixelphone/answer/15701861&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Aftermath of software update==&lt;br /&gt;
Users with &amp;quot;Impacted Devices&amp;quot; who have received the update have reported severely decreased battery capacity &amp;amp; other performance issues.&lt;br /&gt;
&lt;br /&gt;
===Battery-performance issues===&lt;br /&gt;
Users have reported several issues following the update:&lt;br /&gt;
*Erratic battery percentage readings, including sudden jumps in charge levels&lt;br /&gt;
*Battery percentage remaining static despite continuous use&lt;br /&gt;
*Reduced charging speeds&lt;br /&gt;
*Permanent exclamation mark appearing in battery indicator&lt;br /&gt;
*Forced battery percentage display&lt;br /&gt;
*Severely reduced battery life, even with recently replaced batteries&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |title=I change my battery a month BEFORE the upgrade, but after, I got the ! mark ... any tips ? |url=https://www.reddit.com/r/Pixel4a/comments/1i2xm7c/i_change_my_battery_a_month_before_the_upgrade/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250802034226/https://old.reddit.com/r/Pixel4a/ |archive-date=2 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Battery-replacement complications===&lt;br /&gt;
Many users have reported that replacing the battery, either before or after the update, doesn&#039;t fix the performance limitations:&lt;br /&gt;
*Devices with new batteries still show warning indicators&lt;br /&gt;
*Performance remains capped even with official Google batteries&lt;br /&gt;
*Users who replaced batteries before the update experienced the same limitations as those with original batteries&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
*Google support has indicated this may be due to repairs being performed outside of authorized service centers&amp;lt;ref&amp;gt;{{Cite web |title=Replaced the battery, but still the warning. |url=https://www.reddit.com/r/Pixel4a/comments/1i19hxf/replaced_the_battery_but_still_the_warning/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250802034226/https://old.reddit.com/r/Pixel4a/ |archive-date=2 Aug 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In a Reddit poll posted on the [https://www.reddit.com/r/Pixel4a r/Pixel4a subreddit], 170 out 212 respondents stated that their device had been identified as an &amp;quot;Impacted Device&amp;quot; by Google.&amp;lt;ref&amp;gt;{{Cite web |title=Pixel 4a battery update: Google says &amp;quot;some&amp;quot; phones will be negatively affected. Let&#039;s see for ourselves what percentage is &amp;quot;some&amp;quot; |url=https://www.reddit.com/r/Pixel4a/comments/1hvmggd/pixel_4a_battery_update_google_says_some_phones/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250802034226/https://old.reddit.com/r/Pixel4a/ |archive-date=2 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Technical evidence of battery changes===&lt;br /&gt;
Hector Martin has analyzed the software update of the Pixel 4a. He determined that the battery profiles had changed such that &amp;quot;LSN&amp;quot; batteries (e.g. &amp;quot;Lishen&amp;quot;?) have a significantly lower charge limit.&amp;lt;ref&amp;gt;{{Cite web |last=Martin |first=Hector |title=So there&#039;s a bunch of noise going around a sneaky forced Google Pixel 4a update that seems to cripple batteries... and this is quite interesting. |url=https://social.treehouse.systems/@marcan/113914172433692339 |url-status=dead |archive-url=https://web.archive.org/web/20250204103910/https://social.treehouse.systems/@marcan/113914172433692339 |archive-date=4 Feb 2025 |access-date=25 Mar 2025 |website=Mastodon}}&amp;lt;/ref&amp;gt; Presumably this means that battery replacements will only restore battery performance if the battery is replaced with an &amp;quot;ATL&amp;quot; battery (&amp;quot;Amperex Technology Limited&amp;quot;). It is possible to differentiate between the manufactures by looking at the serial number on the battery. 8230015901 is ATL and 8230020501 is LSN. Note that these refer to the companies manufacturing the cells, not the batteries, so the brand name is not printed on the battery itself.&lt;br /&gt;
&lt;br /&gt;
==Possible technical rationale==&lt;br /&gt;
While Google has not provided detailed technical explanations for the update, there are several known factors about lithium-ion battery aging that could potentially justify such measures:&lt;br /&gt;
&lt;br /&gt;
===Aging lithium-ion batteries===&lt;br /&gt;
Lithium-ion batteries face degradation as they age:&lt;br /&gt;
*Loss of active lithium ions through repeated charge cycles&lt;br /&gt;
*Growth of the Solid Electrolyte Interphase (SEI) layer&lt;br /&gt;
*Physical expansion &amp;amp; contraction stress during charging cycles&lt;br /&gt;
*Potential for dendrite formation in aged cells&lt;br /&gt;
*Increased internal resistance over time&amp;lt;ref&amp;gt;{{Cite web |last=Chu |first=Tien-Fu |last2=Rajendran |first2=Raja |last3=Kuznetsova |first3=Iren |last4=Wang |first4=Gou-Jen |date=31 Mar 2020 |title=High-power, non-enzymatic glucose biofuel cell based on a nano/micro hybrid-structured Au anode |url=https://www.sciencedirect.com/science/article/abs/pii/S0378775320301476 |url-status=live |archive-url=https://archive.org/details/chu2020 |archive-date=20 May 2026 |access-date=20 May 2026 |website=ScienceDirect |doi=10.1016/j.jpowsour.2020.227844}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Safety considerations===&lt;br /&gt;
Several factors specific to the Pixel 4a situation could indicate that this was a battery safety concern:&lt;br /&gt;
*The device was released in August 2020; many units are approaching 4.5 years of use&lt;br /&gt;
*The mandatory nature of the update suggests safety implications rather than performance optimization&lt;br /&gt;
*The use of specialized shipping containers marked for &amp;quot;Damaged/Defective Lithium Ion Battery(s)&amp;quot; parallels procedures used for known hazardous devices&amp;lt;ref&amp;gt;{{Cite web |title=Certainly Seems Battery Defect-Related (vs Planned Obsolescence) |url=https://www.reddit.com/r/Pixel4a/comments/1hxyp6z/certainly_seems_battery_defectrelated_vs_planned/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250802034226/https://old.reddit.com/r/Pixel4a/ |archive-date=2 Aug 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://www.cultofmac.com/wp-content/uploads/2016/10/Note-7-return-kit.png Shipping container picture] ([http://web.archive.org/web/20250708174250/https://www.cultofmac.com/wp-content/uploads/2016/10/Note-7-return-kit.png Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*The update seems to target specific device serial numbers rather than all units; suggesting a manufacturing batch issue&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Precedent in mobile phones===&lt;br /&gt;
Similar battery-related interventions have occurred previously; Apple&#039;s 2017 iPhone throttling was done to prevent unexpected shutdowns in devices with degraded batteries.&lt;br /&gt;
&lt;br /&gt;
===Potential manufacturing variables===&lt;br /&gt;
Several factors could explain why only certain devices are affected:&lt;br /&gt;
*Different battery suppliers or manufacturing batches&lt;br /&gt;
*Variations in battery cell chemistry or construction&lt;br /&gt;
*Manufacturing date ranges coinciding with specific material supplies&lt;br /&gt;
*Quality control variations between production runs&lt;br /&gt;
&lt;br /&gt;
These technical considerations suggest the update may be a preventative measure against potential battery safety issues, rather than [[planned obsolescence]]. However, Google&#039;s limited transparency about the specific technical justification has left users unable to verify this interpretation.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |last=Purdy |first=Kevin |date=7 Jan 2025 |title=Google Pixel 4a gets an unexpected update: Lower battery life |url=https://arstechnica.com/gadgets/2025/01/good-news-bad-news-pixel-4a-is-getting-an-update-but-it-reduces-battery-life/ |url-status=live |access-date=25 Mar 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20260223044606/https://arstechnica.com/gadgets/2025/01/good-news-bad-news-pixel-4a-is-getting-an-update-but-it-reduces-battery-life/ |archive-date=23 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Criticism by community==&lt;br /&gt;
The following concerns have been raised regarding the Pixel 4a Battery Performance Program:&lt;br /&gt;
&lt;br /&gt;
#This update is an automatic update &#039;&#039;&#039;users can not opt&#039;&#039;&#039; &#039;&#039;&#039;out&#039;&#039;&#039; of.&lt;br /&gt;
#*While the update can be circumvented, it requires technical knowledge of Android phones, which an average user does not have.&lt;br /&gt;
#Google&#039;s communication on what the problem with &amp;quot;Impacted Devices&amp;quot; is and how the update seeks to remedy it has been vague.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&lt;br /&gt;
#*As Google has not publicly commented on the issue, users have been left to speculate on what the intent behind the update could be.&lt;br /&gt;
#Google Support has been giving out misleading or incorrect information&#039;&#039;&#039;.&#039;&#039;&#039;&lt;br /&gt;
#*Google Support initially stated that the $100 USD coupon code could not be used in combination with other sales. This has turned out to be false. This information may have affected the compensation option customers chose.&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=The Pixel discount DOES stack with the sale! |url=https://www.reddit.com/r/Pixel4a/comments/1i6ei4x/the_pixel_discount_does_stack_with_the_sale/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250802034226/https://old.reddit.com/r/Pixel4a/ |archive-date=2 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
#At least two users have reported Google Support telling them that their Pixel 4a&#039;s trade-in price would be lowered after the update&#039;s installation.&amp;lt;ref&amp;gt;{{Cite web |title=Does anyone know if they&#039;ll give full cashback for Pixel 4a after update |url=https://www.reddit.com/r/Pixel4a/comments/1i43nz3/does_anyone_know_if_theyll_give_full_cashback_for/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250118161515/https://old.reddit.com/r/Pixel4a/comments/1i43nz3/does_anyone_know_if_theyll_give_full_cashback_for/ |archive-date=18 Jan 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
#Google&#039;s use of Payoneer makes it impossible for people to receive the $50 that Google offered as an option. The most someone can receive is $47 if they share personal financial information with an unknown-to-them company including their Social Security number, and promptly cancel the Payoneer service to avoid additional fees.&lt;br /&gt;
&lt;br /&gt;
==Restoring battery functionality==&lt;br /&gt;
===This is a user-submitted guide. Follow at your own risk.===&lt;br /&gt;
===Replacing the battery===&lt;br /&gt;
[[#Technical evidence of battery changes|Initial reverse engineering efforts]] suggest that you can identify if your battery is bad by looking at the serial number. If you&#039;re going to replace the battery outside of Google&#039;s program with another OEM battery, look for one with the serial number &amp;quot;8230015901&amp;quot;. Make sure it does NOT have the bad serial number, &amp;quot;8230020501&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The serial number is printed on the battery, as marked in the following image:&lt;br /&gt;
&lt;br /&gt;
[[File:Pixel 4a battery serial.jpg|500px]]&lt;br /&gt;
&lt;br /&gt;
You may also be able to run the following command over [[wikipedia:Android_Debug_Bridge|ADB]] to retrieve the serial number:&amp;lt;ref&amp;gt;{{Cite web |date=30 Jan 2025 |title=Battery update analysis and way to detect affected battery |url=https://xdaforums.com/t/battery-update-analysis-and-way-to-detect-affected-battery.4716132/ |url-status=live |access-date=25 Mar 2025 |website=XDA Forums |archive-url=http://web.archive.org/web/20260212185150/https://xdaforums.com/t/battery-update-analysis-and-way-to-detect-affected-battery.4716132/ |archive-date=12 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 adb shell cat /sys/class/power_supply/battery/serial_number&lt;br /&gt;
&lt;br /&gt;
===Blocking the update or flashing older firmware===&lt;br /&gt;
&#039;&#039;&#039;Warning:&#039;&#039;&#039; please consider the [[Pixel 4a Battery Performance Program#Safety considerations|battery safety concerns]] before reverting  or ignoring updates. Users must evaluate battery health at own risk.&lt;br /&gt;
&lt;br /&gt;
Following the criticism, the community was quick to find workarounds to retain or restore previous battery capacity. Users can stop the update by blocking DNS requests to Google&#039;s OTA servers (&#039;&#039;ota.googlezip.net, ota-cache1.googlezip.net, ota-cache2.googlezip.net&#039;&#039;) via a DNS filtering application such as NextDNS, RethinkDNS, or AdAway&amp;lt;ref&amp;gt;{{Cite web |title=THE ONLY WORKING SOLUTION to stop the forced battery update - this works even if the update is currently downloading, or has already been downloaded and it&#039;s waiting for a restart to apply it |url=https://www.reddit.com/r/Pixel4a/comments/1i0zih0/the_only_working_solution_to_stop_the_forced/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250801111009/https://old.reddit.com/r/Pixel4a/comments/1i0zih0/the_only_working_solution_to_stop_the_forced/ |archive-date=1 Aug 2025}}&amp;lt;/ref&amp;gt;. Users can delete an already downloaded (and not yet installed) update: &#039;&#039;Settings -&amp;gt; Apps -&amp;gt; All Apps -&amp;gt; Google Play Services -&amp;gt; Storage and cache -&amp;gt; Manage Space&#039;&#039; and from there on delete all data through the &amp;quot;&#039;&#039;&#039;Clear all data&#039;&#039;&#039;&amp;quot; button. If the phone has already installed the Jan 2025 update, users can manually flash the previous firmware to restore functionality&amp;lt;ref&amp;gt;{{Cite web |date=17 Jan 2025 |title=How to: Undo the January 2025 update without losing data (unlocked devices only). |url=https://xdaforums.com/t/how-to-undo-the-january-2025-update-without-losing-data-unlocked-devices-only.4713980/ |url-status=live |access-date=25 Mar 2025 |website=XDA Forums |archive-url=http://web.archive.org/web/20251123184909/https://xdaforums.com/t/how-to-undo-the-january-2025-update-without-losing-data-unlocked-devices-only.4713980/ |archive-date=23 Nov 2025}}&amp;lt;/ref&amp;gt;. Flashing to the previous firmware requires unlocking the bootloader&amp;lt;ref&amp;gt;{{Cite web |date=25 Aug 2020 |title=[GUIDE] Unlock/Root/Safetynet for Pixel 4a |url=https://xdaforums.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/ |url-status=live |access-date=25 Mar 2025 |website=XDA Forums |archive-url=http://web.archive.org/web/20251128065836/https://xdaforums.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/ |archive-date=28 Nov 2025}}&amp;lt;/ref&amp;gt;, and a copy of the previous firmware from November 2023 (sunfish-tq3a.230805.001.s1-factory-82902ea9)&amp;lt;ref&amp;gt;{{Cite web |date=6 Jan 2025 |title=Changes coming to your Pixel 4a |url=https://xdaforums.com/t/changes-coming-to-your-pixel-4a.4712085/ |url-status=live |access-date=25 Mar 2025 |website=XDA Forums |archive-url=http://web.archive.org/web/20251217041347/https://xdaforums.com/t/changes-coming-to-your-pixel-4a.4712085/ |archive-date=17 Dec 2025}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Google has removed all official images for the pixel 4a except the jan 2025 update, effectively removing official images as an option for downgrades &amp;lt;ref&amp;gt;{{Cite web |title=Factory Images for Nexus and Pixel Devices |url=https://developers.google.com/android/images#sunfish |url-status=live |access-date=25 Mar 2025 |website=Google Play Services |archive-url=http://web.archive.org/web/20260128151240/https://developers.google.com/android/images |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Flashing a custom firmware===&lt;br /&gt;
&#039;&#039;&#039;Warning:&#039;&#039;&#039; please consider the [[Pixel 4a Battery Performance Program#Safety considerations|battery safety concerns]] before ignoring the battery update. Users must evaluate battery health at own risk.&lt;br /&gt;
&lt;br /&gt;
Another option is flashing a custom firmware (&amp;quot;ROM&amp;quot;) onto the device, such as [[wikipedia:LineageOS|LineageOS]], [[wikipedia:CalyxOS|CalyxOS]], or [[GrapheneOS]]. Custom ROMs have not adopted the closed source kernel changes that reduce the battery&#039;s capacity.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel|Battery Performance Program]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Battery_Health_Assistance&amp;diff=54758</id>
		<title>Battery Health Assistance</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Battery_Health_Assistance&amp;diff=54758"/>
		<updated>2026-05-25T12:52:23Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{IncidentCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|StartDate=&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=&lt;br /&gt;
|ProductLine=Google Pixel&lt;br /&gt;
|Product=&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Type=Planned Obsolescence&lt;br /&gt;
|Description=&lt;br /&gt;
}}&lt;br /&gt;
Battery Health Assistance is an anti-feature by [[Google]], used on [[Google Pixel]] smartphones since Pixel 6a and later. While on some models it can be disabled, it is not possible for the Pixel 9a and Pixel 10 series.&lt;br /&gt;
&lt;br /&gt;
Google claims Battery Health Assistance is to &amp;quot;stabilize performance and aging&amp;quot;, while its detractors point out the forced nature and performance degradation over time can be considered [[planned obsolescence]]. Users have reported &#039;&#039;worse&#039;&#039;, not better, battery health measured on both [[Android]] 16 and third-party software, contrary to Google&#039;s claim.&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
===Pixel 4a Battery Performance Program===&lt;br /&gt;
{{Main|Pixel 4a Battery Performance Program}}&lt;br /&gt;
Google is known for reducing the charging voltage of Pixel 4a from 4.4V to 3.95V via a software update, resulting in a 44% drop in theoretical usable charge.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Wojciechowska |first=Kamila |date=5 Feb 2025 |title=There is even more to the Google Pixel 4a&#039;s horrific battery update than we thought |url=https://www.androidauthority.com/pixel-4a-battery-update-explained-3522417/ |url-status=live |access-date=4 Apr 2025 |website=AndroidAuthority |archive-url=http://web.archive.org/web/20260221023026/https://www.androidauthority.com/pixel-4a-battery-update-explained-3522417/ |archive-date=21 Feb 2026}}&amp;lt;/ref&amp;gt; Pixel 4a users report much higher real-world runtime loss.&lt;br /&gt;
&lt;br /&gt;
===Pixel 6a Battery Performance Program===&lt;br /&gt;
{{Main|Google Pixel 6a Battery Performance Program}}&lt;br /&gt;
&lt;br /&gt;
On 11 June 2025, Google confirmed a Pixel 6a update would reduce capacity in response to multiple devices catching fire.&amp;lt;ref&amp;gt;{{Cite web |last=Rahman |first=Mishaal |date=11 Jun 2025 |title=Warning: Google will soon nerf the Pixel 6a’s battery due to an overheating issue |url=https://www.androidauthority.com/pixel-6a-battery-overheating-warning-3566640/ |url-status=live |archive-url=https://web.archive.org/web/20250613135314/https://www.androidauthority.com/pixel-6a-battery-overheating-warning-3566640/ |archive-date=13 Jun 2025 |access-date=16 Jun 2025 |website=Android Authority}}&amp;lt;/ref&amp;gt; The update shows a warning label when the cycle count reaches 375 and reduces the charging voltage after 400 cycles.&lt;br /&gt;
&lt;br /&gt;
===Pixel 9a===&lt;br /&gt;
The Google Pixel 9a is an Android smartphone designed, developed and marketed by [[Google]]. The release date was April 10 in US, Canada and UK.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Brecher |first=Hannes |last2=Fisher |first2=Jacob |date=2 Apr 2025 |title=Google Pixel 9a comes with new feature that weakens the battery after just 200 charging cycles |url=https://www.notebookcheck.net/Google-Pixel-9a-comes-with-new-feature-that-weakens-the-battery-after-just-200-charging-cycles.991310.0.html |url-status=live |access-date=2 Apr 2025 |website=Notebookcheck |archive-url=http://web.archive.org/web/20260201093806/https://www.notebookcheck.net/Google-Pixel-9a-comes-with-new-feature-that-weakens-the-battery-after-just-200-charging-cycles.991310.0.html |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt; On March 31, 2025, Google announced its Battery Health Assistance&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |date=1 Apr 2025 |title=Understand your Pixel battery |url=https://support.google.com/pixelphone/answer/15738128 |url-status=live |archive-url=https://web.archive.org/web/20250704165953/https://support.google.com/pixelphone/answer/15738128 |archive-date=4 Jul 2025 |access-date=4 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt; to users:&lt;br /&gt;
&amp;lt;blockquote&amp;gt;For Pixel 9a:&lt;br /&gt;
&lt;br /&gt;
Lithium-ion batteries are consumable components that eventually require replacement. Your Pixel 9a will receive a software update that automatically helps manage the long term health and performance of its battery as it ages. This software will adjust the battery&#039;s maximum voltage in stages that start at 200 charge cycles and continue gradually until 1000 charge cycles to help stabilize battery performance and aging.&lt;br /&gt;
&lt;br /&gt;
You may notice small decreases in your battery&#039;s runtime as your battery ages. Battery health assistance will also tune the phone&#039;s charging speed based on adjusted capacity. You may notice a slight change in battery charging performance. Battery health assistance settings on Pixel 9a are not customizable by the user.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google claimed that this Battery Health Assistance will be voluntary for previously launched devices.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=Abner |date=31 Mar 2025 |title=Google Pixel adding ‘Battery health assistance’ for long-term use, starting with Pixel 9a |url=https://9to5google.com/2025/03/31/pixel-battery-health-assistance/ |url-status=live |access-date=4 Apr 2025 |website=9to5Google |archive-url=http://web.archive.org/web/20251216091311/https://9to5google.com/2025/03/31/pixel-battery-health-assistance/ |archive-date=16 Dec 2025}}&amp;lt;/ref&amp;gt; It&#039;s confirmed that Battery Health Assistance cannot be turned off on Pixel 10 series.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=20 Aug 2025 |title=Google will throttle your Pixel 10&#039;s battery, and there&#039;s nothing you can do about it |url=https://www.androidauthority.com/google-pixel-10-battery-health-assistance-3585863/ |url-status=live |archive-url=https://web.archive.org/web/20250823225719/https://www.androidauthority.com/google-pixel-10-battery-health-assistance-3585863/ |archive-date=23 Aug 2025 |access-date=23 Aug 2025 |website=AndroidAuthority}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On 2 July 2025, an APK teardown of Google&#039;s Settings Services app version v1.1.0771997146 hints that Battery Health Assistance may no longer be optional on other models if battery health drops below a certain point. It&#039;s not confirmed whether this change is final and no official announcement has been made by Google.&amp;lt;ref&amp;gt;{{Cite web |last=Thomas |first=Chris |date=2 Jul 2025 |title=Google could force more Pixels to throttle charging and capacity as they age |url=https://www.androidpolice.com/battery-health-assistance-pixel-phones-mandatory/ |url-status=live |archive-url=https://web.archive.org/web/20250703034710/https://www.androidpolice.com/battery-health-assistance-pixel-phones-mandatory/ |archive-date=3 Jul 2025 |access-date=3 Jul 2025 |website=Android Police}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Siddiqui |first=Aamir |date=2 Jul 2025 |title=Mandatory battery throttling is coming for more Pixels with poor battery health (APK teardown) |url=https://www.androidauthority.com/pixel-battery-health-assistance-mandatory-apk-teardown-3573263/ |url-status=live |archive-url=https://web.archive.org/web/20250703035344/https://www.androidauthority.com/pixel-battery-health-assistance-mandatory-apk-teardown-3573263/ |archive-date=3 Jul 2025 |access-date=3 Jul 2025 |website=Android Authority}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Potential effects of software update==&lt;br /&gt;
Google has not provided detailed technical explanations for the update. The adjusted battery&#039;s maximum voltage and charging speed are yet to be disclosed.&lt;br /&gt;
&lt;br /&gt;
===Battery Performance issues===&lt;br /&gt;
Charging the battery at a lower voltage will not fully charge it. A partly charged battery exhibit shorter runtime. Lowering the charging voltage by 0.1V lowers the capacity by about 10%.&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |date=25 Oct 2021 |title=BU-409: Charging Lithium-ion |url=https://batteryuniversity.com/article/bu-409-charging-lithium-ion |url-status=live |access-date=4 Apr 2025 |website=Battery University |archive-url=http://web.archive.org/web/20260123215951/https://www.batteryuniversity.com/article/bu-409-charging-lithium-ion |archive-date=23 Jan 2026}}&amp;lt;/ref&amp;gt; Charging the battery at a lower current will increase the charging time.&lt;br /&gt;
&lt;br /&gt;
Google claimed that on Pixel 8a and later, the battery &amp;quot;should retain up to 80% capacity for about 1000 charge cycles&amp;quot;.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; However, Google also said that &amp;quot;your battery&#039;s actual lifespan depends on usage patterns and other factors&amp;quot;.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; The &amp;quot;Battery Health Assistance&amp;quot;, being a &amp;quot;factor&amp;quot;, potentially causes battery lifespan to be considerably worse than advertised after the first thousand charging cycles.&lt;br /&gt;
&lt;br /&gt;
====Analysis====&lt;br /&gt;
*Charging the battery in shorter capacity periods leads to less runtime.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&lt;br /&gt;
*Charging the battery at lower percentages slows down battery aging.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Both factors lead to two possible outcomes that need to be differentiated very clearly to prevent misunderstanding, improve battery usage and identify anti-consumer practices:&lt;br /&gt;
&lt;br /&gt;
*When the user recharges the battery to a lower percentage frequently (only charging to 100% when necessary), the battery is aged less, which ultimately results in better battery health and longer runtime should the user need 100% capacity, compared to always fully charging.&lt;br /&gt;
*The manufacturer blocked part of the available capacity &#039;&#039;after&#039;&#039; a certain amount of charging cycles, meaning that — after the user has degraded a certain amount of the battery — the manufacturer artificially limits its capabilities by further removing a second portion of the battery.&amp;lt;ref&amp;gt;{{Cite web |last=Bonggolto |first=Jay |date=25 Aug 2025 |title=The Pixel 10’s battery takes a hit after 200 cycles, courtesy of a feature you can’t switch off |url=https://www.androidcentral.com/phones/google-pixel/the-pixel-10s-battery-takes-a-hit-after-200-cycles-courtesy-of-a-feature-you-cant-switch-off |url-status=live |archive-url=https://web.archive.org/web/20250827074849/https://www.androidcentral.com/phones/google-pixel/the-pixel-10s-battery-takes-a-hit-after-200-cycles-courtesy-of-a-feature-you-cant-switch-off |archive-date=27 Aug 2025 |access-date=16 Sep 2025 |website=Android Central}}&amp;lt;/ref&amp;gt; In other words, Battery Health Assistance feature essentially reduces the phone&#039;s battery capacity &amp;lt;u&amp;gt;over and above&amp;lt;/u&amp;gt; standard degradation.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Possible technical rationale==&lt;br /&gt;
===Prolonging battery life===&lt;br /&gt;
Charging the battery at a lower percentage slows down battery degradation,&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;Xu, Bolun &amp;amp; Oudalov, Alexandre &amp;amp; Ulbig, Andreas &amp;amp; Andersson, Göran. (2016). [https://sci-hub.st/10.1109/TSG.2016.2578950 Modeling of Lithium-Ion Battery Degradation for Cell Life Assessment]. IEEE Transactions on Smart Grid. 99. 1-1. 10.1109/TSG.2016.2578950. [https://sci-hub.st/storage/zero/6755/4c35d017b1b4e67fee8566488c879767/xu2018.pdf Archived].&amp;lt;/ref&amp;gt; However, there are some key differences between &amp;quot;Charging Optimization&amp;quot; and the future &amp;quot;Battery Health Assistance&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Charging Optimization&#039;&#039;&#039; has two options, &amp;quot;Adaptive Charging&amp;quot; and &amp;quot;Limit to 80%&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |title=Get the most life from your Pixel phone battery |url=https://support.google.com/pixelphone/answer/6090612 |url-status=live |access-date=4 Apr 2025 |website=Pixel Phone Help |archive-url=http://web.archive.org/web/20260212115330/https://support.google.com/pixelphone/answer/6090612 |archive-date=12 Feb 2026}}&amp;lt;/ref&amp;gt; Adaptive Charging can prolong the life of the battery by fully charging it just before the user unplugs, reducing the time spent at high charge levels. The user can select Limit to 80% option to help extend the lifespan of the battery with a drawback of a reduced runtime. The smart phone can always resume maximum available capacity should the user disable the limit and charge it to 100%.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Battery Health Assistance&#039;&#039;&#039; lowers the battery&#039;s maximum voltage and charging current in stages, from 200 cycles to 1000 cycles.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; This is irreversible as the only way to use the full voltage of the battery again is to replace the battery itself.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; This reduces runtime further as only part of the remaining battery capacity is available, arguably defeating the purpose of preserving battery health.&lt;br /&gt;
&lt;br /&gt;
===Safety consideration===&lt;br /&gt;
Concerns arose over the delayed launch date of Pixel 9a due to &amp;quot;an unnamed component issue&amp;quot;, suspecting that the issue could be the battery.&amp;lt;ref&amp;gt;{{Cite web |last=Mundy |first=Jon |date=20 Mar 2025 |title=Pixel 9a flaw uncovered before it even hits shops |url=https://www.techadvisor.com/article/2643405/google-pixel-9a-delayed-due-to-component-issue.html |url-status=live |access-date=4 Apr 2025 |website=Tech Advisor |archive-url=http://web.archive.org/web/20250907134341/https://www.techadvisor.com/article/2643405/google-pixel-9a-delayed-due-to-component-issue.html |archive-date=7 Sep 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=11 Jun 2025 |title=The latest Android 16 beta now lets you throttle your Pixel&#039;s battery, charging |url=https://www.androidauthority.com/android-16-qpr1-beta-2-battery-health-assistance-3566396/ |url-status=live |archive-url=http://web.archive.org/web/20251218063757/https://www.androidauthority.com/android-16-qpr1-beta-2-battery-health-assistance-3566396/ |archive-date=18 Dec 2025}}&amp;lt;/ref&amp;gt; If the battery of the Pixel 9a is found to be defective, it might no longer be safe to charge at full voltage after 200 cycles.&lt;br /&gt;
&lt;br /&gt;
==Consumer reaction==&lt;br /&gt;
Current and former Pixel users condemned this program and compared it with Apple&#039;s &amp;quot;Batterygate&amp;quot; and the Pixel 4a Battery Performance Program, saying that Battery Health Assistance is &amp;quot;worse&amp;quot;, a &amp;quot;fancy name for [[planned obsolescence]]&amp;quot;,&amp;lt;ref&amp;gt;{{Cite web |title=This is worse than Apple |url=https://old.reddit.com/r/GooglePixel/comments/1jp883q/google_will_gradually_reduce_pixel_9a_battery/ml6m0y7/?context=3 |url-status=live |archive-url=https://web.archive.org/web/20250405011000/https://old.reddit.com/r/GooglePixel/comments/1jp883q/google_will_gradually_reduce_pixel_9a_battery/ml6m0y7/?context=3 |archive-date=5 Apr 2025 |access-date=5 Apr 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=16 Apr 2025 |title=Pixel reducing battery capacity after 200 charge cycles |url=https://old.reddit.com/r/GooglePixel/comments/1k0r54v/pixel_reducing_battery_capacity_after_200_charge/ |url-status=live |archive-url=https://web.archive.org/web/20250616031438/https://old.reddit.com/r/GooglePixel/comments/1k0r54v/pixel_reducing_battery_capacity_after_200_charge/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt; and the Pixel 4a incident is a &amp;quot;preview&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |date=2 Apr 2025 |title=Pixel 9a will have battery &amp;quot;optimised&amp;quot; after 200 cycles |url=https://www.reddit.com/r/Pixel4a/comments/1jpk1db/pixel_9a_will_have_battery_optimised_after_200/ |url-status=live |access-date=3 Apr 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250728225129/https://old.reddit.com/r/Pixel4a/comments/1jpk1db/pixel_9a_will_have_battery_optimised_after_200/ |archive-date=28 Jul 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users also found the wording of the support article on Google&#039;s website vague and lacking in consistency,&amp;lt;ref&amp;gt;{{Cite web |date=1 Apr 2024 |title=So they want to reduce the wear out of the battery by... doing exactly the same? What&#039;s logic behind this? |url=https://www.reddit.com/r/GooglePixel/comments/1jp883q/comment/mkzu6lc/ |url-status=dead |access-date=2 Apr 2025 |website=[[Reddit]] |archive-url=https://web.archive.org/web/20260223033622/https://old.reddit.com/r/GooglePixel/comments/1jp883q/deleted_by_user/mkzu6lc/ |archive-date=23 Feb 2026}}&amp;lt;/ref&amp;gt; saying the Google will &amp;quot;cause the thing they are supposedly trying to prevent&amp;quot;,&amp;lt;ref&amp;gt;{{Cite web |date=2 Apr 2025 |title=Deliberate weakening after only 200 charging cycles: Google Pixel 9a limits battery voltage according to a planned schedule |url=https://www.notebookchat.com/index.php?topic=225600.msg645716#msg645716 |url-status=live |access-date=5 Apr 2025 |website=NotebookCHECK - Notebook Forum |archive-url=http://web.archive.org/web/20250908110003/https://www.notebookchat.com/index.php?topic=225600.msg645716 |archive-date=8 Sep 2025}}&amp;lt;/ref&amp;gt; and forcing the user to replace the phone sooner that what would &amp;quot;naturally&amp;quot; happen.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users also reported shorter runtime,&amp;lt;ref&amp;gt;{{Cite web |date=14 Jun 2025 |title=Absolutely disappointed with Google and their latest updates including A16 |url=https://old.reddit.com/r/GooglePixel/comments/1lb4i26/absolutely_disappointed_with_google_and_their/ |url-status=live |archive-url=https://web.archive.org/web/20250616034347/https://old.reddit.com/r/GooglePixel/comments/1lb4i26/absolutely_disappointed_with_google_and_their/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt; slower charging speed,&amp;lt;ref&amp;gt;{{Cite web |date=13 Jun 2025 |title=Did you notice that Battery optimization feature is the one that is forced on P9a? |url=https://old.reddit.com/r/pixel_phones/comments/1laiiok/did_you_notice_that_battery_optimization_feature/ |url-status=live |archive-url=https://web.archive.org/web/20250616040147/https://old.reddit.com/r/pixel_phones/comments/1laiiok/did_you_notice_that_battery_optimization_feature/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt; and lower battery health&amp;lt;ref&amp;gt;{{Cite web |date=14 Jun 2025 |title=Is this how Battery Health function of A16 works ? |url=https://old.reddit.com/r/pixel_phones/comments/1lb38ll/is_this_how_battery_health_function_of_a16_works/ |url-status=live |archive-url=https://web.archive.org/web/20250616040252/https://old.reddit.com/r/pixel_phones/comments/1lb38ll/is_this_how_battery_health_function_of_a16_works/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt; after updating to Android 16. The &amp;quot;slight&amp;quot; change in battery charging performance was much more significant than indicated. The battery health can be increased to pre-update condition by switching off Battery Health Assistance.&lt;br /&gt;
&lt;br /&gt;
There was an ongoing discussion of whether using a [[wikipedia:List_of_custom_Android_distributions|custom &amp;quot;ROM&amp;quot;]] like [[GrapheneOS|Graphene OS]] could bypass Battery Health Assistance, which depends on whether this anti-feature works on software or firmware level. If Battery Health Assistance is baked into the firmware of Pixel 10 and later, a custom ROM will not work.&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite web |date=22 Aug 2025 |title=Google will throttle your Pixel 10&#039;s battery, and there&#039;s nothing you can do about it |url=https://old.reddit.com/r/GrapheneOS/comments/1mxgmq9/google_will_throttle_your_pixel_10s_battery_and/ |url-status=live |archive-url=https://web.archive.org/web/20250907084717/https://old.reddit.com/r/GrapheneOS/comments/1mxgmq9/google_will_throttle_your_pixel_10s_battery_and/ |archive-date=7 Sep 2025 |access-date=7 Sep 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel_Buds&amp;diff=54757</id>
		<title>Google Pixel Buds</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel_Buds&amp;diff=54757"/>
		<updated>2026-05-25T12:51:57Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{ProductLineCargo&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Audio&lt;br /&gt;
|Company=Google&lt;br /&gt;
|Description=&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|Logo=Google PixelBuds logo.png&lt;br /&gt;
|ReleaseYear=2017&lt;br /&gt;
|Website=https://store.google.com/product/google_pixel_buds &lt;br /&gt;
}}&lt;br /&gt;
The &#039;&#039;&#039;[[wikipedia:Pixel_Buds|Pixel Buds]]&#039;&#039;&#039; are a line of wireless earbuds developed and marketed by [[Google]]. The first-generation Pixel Buds were launched on October 4, 2017, at the Made by Google launch event, and became available for preorder on the Google Store the same day. They have the Google Assistant built in and support Google Translate.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
===Convenience===&lt;br /&gt;
Removing &amp;quot;Touch and Hold&amp;quot; as a feature is a loss in convenience for consumers.&lt;br /&gt;
&lt;br /&gt;
This was a feature advertised on the boxes of Pixel Bud Pros.&lt;br /&gt;
&lt;br /&gt;
===Sound quality===&lt;br /&gt;
Lack of high-quality codecs like LDAC.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===Google Pixel Buds &amp;quot;Touch and Hold&amp;quot; discontinuation (2024)===&lt;br /&gt;
{{Main|Google Pixel Buds &amp;quot;Touch and Hold&amp;quot; discontinuation}}&lt;br /&gt;
The user could hold down on the device to hear their notifications. The digital assistant on the device will no longer do that by this gesture due to a software update and instead requires users to ask it out loud with commands such as &amp;quot;Read my notifications.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Google Pixel Buds Pro 2 has limited codec support (2024)===&lt;br /&gt;
The Pixel Buds Pro 2 top out at AAC as the high-quality codec.&amp;lt;ref&amp;gt;{{Cite web |last=Bagnell |first=Juan Carlos |date=6 Feb 2025 |title=Google Pixel Buds Pro 2 Long Term Review: Smaller, But Not REALLY Smaller? |url=https://somegadgetguy.com/2025/02/06/google-pixel-buds-pro-2-long-term-review-smaller-but-not-really-smaller/ |access-date=2 Mar 2025 |website=SomeGadgetGuy |archive-url=http://web.archive.org/web/20250917200902/https://somegadgetguy.com/2025/02/06/google-pixel-buds-pro-2-long-term-review-smaller-but-not-really-smaller/ |archive-date=17 Sep 2025}}&amp;lt;/ref&amp;gt; These earbuds feature a new proprietary Tensor A1 chip, which does not support higher-quality formats like APTX HD, LDAC, or LHDC. Many premium earbuds in this price range typically support these higher-quality codecs, which Qualcomm chips would support.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Products==&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;[[Google Pixel Buds Pro 2]]&#039;&#039;&#039; (2024)&lt;br /&gt;
*&#039;&#039;&#039;[[Google Pixel Buds Pro 1]]&#039;&#039;&#039; (2022)&lt;br /&gt;
*&#039;&#039;&#039;[[Google Pixel Buds A-Series]]&#039;&#039;&#039; (2021)&lt;br /&gt;
*&#039;&#039;&#039;[[Google Pixel Buds Gen 2]]&#039;&#039;&#039; (2020)&lt;br /&gt;
*&#039;&#039;&#039;[[Google Pixel Buds Gen 1]]&#039;&#039;&#039; (2017)&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel| ]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel&amp;diff=54756</id>
		<title>Google Pixel</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel&amp;diff=54756"/>
		<updated>2026-05-25T12:51:08Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup}}&lt;br /&gt;
{{ProductLineCargo&lt;br /&gt;
|ArticleType  = Product&lt;br /&gt;
|Category     = Smartphones&lt;br /&gt;
|Company      = Google&lt;br /&gt;
|Description  = &lt;br /&gt;
|InProduction = Yes&lt;br /&gt;
|Logo         = Google Pixel logo.svg&lt;br /&gt;
|ReleaseYear  = 2013&lt;br /&gt;
|Website      = https://pixel.google.com&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;&#039;{{PAGENAME}}&#039;&#039;&#039; is a consumer electronic device that Google develops and equips with specialized versions of Android or ChromeOS.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
The Google Pixel line of smartphones have been plagued by a series of battery related issues ranging from worse battery performance to chances of fire.&amp;lt;ref name=&amp;quot;:42&amp;quot;&amp;gt;{{Cite web |title=I change my battery a month BEFORE the upgrade, but after, I got the ! mark ... any tips ? |url=https://www.reddit.com/r/Pixel4a/comments/1i2xm7c/i_change_my_battery_a_month_before_the_upgrade/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:12&amp;quot;&amp;gt;{{Cite web |date=1 Apr 2025 |title=Understand your Pixel battery |url=https://support.google.com/pixelphone/answer/15738128 |url-status=live |archive-url=https://web.archive.org/web/20250404092737/https://support.google.com/pixelphone/answer/15738128 |archive-date=4 Apr 2025 |access-date=4 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |last=erinelise28 |first= |date=2025-04-22 |title=Pixel 6a Caught on Fire, not sure I want another Pixel |url=https://support.google.com/pixelphone/thread/339876579/pixel-6a-caught-on-fire-not-sure-i-want-another-pixel |url-status=live |archive-url=https://web.archive.org/web/20250516162435/https://support.google.com/pixelphone/thread/339876579/pixel-6a-caught-on-fire-not-sure-i-want-another-pixel?hl=en |archive-date=2025-05-16 |access-date=2025-05-16 |website=Google Pixel Community}}&amp;lt;/ref&amp;gt; This has lead to some consumers being doubtful towards the brand and whether they will spend money with them again.&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A battery-limiting update was pushed automatically without user consent, and users cannot opt-out through normal means. Google removed access to previous firmware versions, effectively limiting users&#039; ability to restore their devices to full functionality.&lt;br /&gt;
&lt;br /&gt;
To receive compensation for the issue, users have to share sensitive personal information, including social security numbers and bank details, with Payoneer, a third-party payment processor. This forces users to choose between their privacy and receiving compensation for their degraded device.&lt;br /&gt;
&lt;br /&gt;
The compensation options favor users choosing to remain within the Google ecosystem ($100 store credit for new Pixel phones, or $50 through Payoneer with fees and privacy concerns).&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;https://support.google.com/pixelphone/answer/15701861 ([https://web.archive.org/web/20250107002112/https://support.google.com/pixelphone/answer/15701861 Archived])&lt;br /&gt;
&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=Request a repair, payment, or future discount code |url=https://support.google.com/pixelphone/workflow/15642495 |url-status=live |archive-url=https://web.archive.org/web/20250107002104/https://support.google.com/pixelphone/workflow/15642495 |archive-date=7 Jan 2025 |access-date=25 Mar 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Davis |first=Wes |date=8 Jan 2025 |title=Google’s new Pixel 4A update is going to lower battery life for some owners |url=https://www.theverge.com/2025/1/7/24338566/google-pixel-4a-battery-stability-replacement-reduced-capacity |url-status=live |access-date=25 Mar 2025 |website=The Verge |archive-url=http://web.archive.org/web/20251220031303/https://www.theverge.com/2025/1/7/24338566/google-pixel-4a-battery-stability-replacement-reduced-capacity |archive-date=20 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=Annual account fee |url=https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |url-status=live |archive-url=http://web.archive.org/web/20251129174745/https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |archive-date=29 Nov 2025 |access-date=25 Mar 2025 |website=Payoneer}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |title=I have replaced battery in a local shop not supported by Google |url=https://www.reddit.com/r/Pixel4a/comments/1i1e4ds/i_have_replaced_battery_in_a_local_shop_not/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google&#039;s support team at times have claimed that certain repairs were unsuccessful because they were performed outside of authorized service centers.&amp;lt;ref&amp;gt;{{Cite web |title=Replaced the battery, but still the warning. |url=https://www.reddit.com/r/Pixel4a/comments/1i19hxf/replaced_the_battery_but_still_the_warning/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:22&amp;quot;&amp;gt;{{Cite web |title=I have replaced battery in a local shop not supported by Google |url=https://www.reddit.com/r/Pixel4a/comments/1i1e4ds/i_have_replaced_battery_in_a_local_shop_not/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&amp;lt;!--*&#039;&#039;[[Example incident one]]&#039;&#039; (&#039;&#039;date&#039;&#039;): &#039;&#039;Short summary of the incident (could be the same as the summary preceding the article).&#039;&#039;&lt;br /&gt;
*&#039;&#039;[[Example incident two]]&#039;&#039; (&#039;&#039;date&#039;&#039;):--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Incidents affecting all of the company&#039;s products can be found in the company article: [[Google]]&lt;br /&gt;
&lt;br /&gt;
==Products==&lt;br /&gt;
This is a list of the products with articles on this wiki.&lt;br /&gt;
*&#039;&#039;&#039;[[Pixel 4a Battery Performance Program|Pixel 4a]] (&#039;&#039;2020-08-03&#039;&#039;):&#039;&#039;&#039; An update was pushed, without users&#039; consent, to limit the device&#039;s battery capacity and charging speed in an attempt to &amp;quot;improve the stability of their battery&#039;s performance&amp;quot;&lt;br /&gt;
*&#039;&#039;&#039;[[Pixel_5a|Pixel 5a]] (&#039;&#039;2024-07-01&#039;&#039;):&#039;&#039;&#039; Extended warranty to 2 years, due to a high incidence rate of motherboard failures&lt;br /&gt;
*&#039;&#039;&#039;[[Google Pixel 6a Battery Performance Program|Pixel 6a]] (&#039;&#039;2022-07-21&#039;&#039;):&#039;&#039;&#039; Google Pixel 6a Battery Performance Program&lt;br /&gt;
*&#039;&#039;&#039;[[Pixel 9a Battery Health Assistance|Pixel 9a]] (&#039;&#039;2025-04-10&#039;&#039;):&#039;&#039;&#039; Google announced its Battery Health Assistance, to limit the device&#039;s battery voltage and &amp;quot;manage long term health and performance of the battery&amp;quot;&lt;br /&gt;
*&#039;&#039;&#039;[[Google_Pixel_9_Pro_camera_bar_separates_from_phone_body|Pixel 9 Pro]] (&#039;&#039;2025-01-01&#039;&#039;):&#039;&#039;&#039; Google Pixel 9 Pro camera bar separates from phone body&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Apple]]&lt;br /&gt;
*[[Samsung]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel| ]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Pixel_6a_Battery_Performance_Program&amp;diff=54755</id>
		<title>Google Pixel 6a Battery Performance Program</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Pixel_6a_Battery_Performance_Program&amp;diff=54755"/>
		<updated>2026-05-25T12:50:40Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{IncidentCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|StartDate=2 July 2025&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=Active&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|Product=Pixel 6a&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Type=Forced Migration&lt;br /&gt;
|Description=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Google Pixel 6a&#039;&#039;&#039; is an [[Android]] smartphone designed, developed and marketed by [[Google]]. It was released on July 28, 2022. Android 16 is expected to be the last version supported with security updates expected to end sometime in 2027.&amp;lt;ref&amp;gt;{{Cite web |title=PiFixel 6a end of life date |url=https://endoflife.date/pixel |url-status=live |access-date=2025-07-03 |website=endoflife.date |archive-url=http://web.archive.org/web/20260118201513/https://endoflife.date/pixel |archive-date=18 Jan 2026}}&amp;lt;/ref&amp;gt; On July 2, 2025, Google announced its Pixel 6a Battery Performance Program to users:&lt;br /&gt;
&lt;br /&gt;
[[File:Google Pixel 6a email forced update lowering battery life.png|thumb|right|Email sent to users with a Pixel 6a.]]&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;quot;Google has determined that certain Pixel 6a phones (“Impacted Devices”) require a mandatory software update to reduce the risk of potential battery overheating which could pose a risk to users. The update will enable important battery management features that will reduce battery capacity and charging performance on Impacted Devices after the battery reaches 400 charge cycles. &lt;br /&gt;
&lt;br /&gt;
All Pixel 6a devices will receive a mandatory automatic software update to Android 16, with roll out starting July 8 2025, but only Impacted Devices will receive the battery management features. Some users will see changes sooner than others, because the battery management features activate only after an Impacted Device reaches 400 charge cycles.&lt;br /&gt;
&lt;br /&gt;
We want our customers to have the best possible experience with their products, so users of these Impacted Devices are eligible for support options from Google based upon country of purchase, location, and warranty status, subject to our terms and conditions below. Not all Pixel 6a devices are impacted by the reduction in battery capacity and charging performance. If your device is not impacted, your battery management features will remain the same as before, and you will not be eligible for these support options under this program.&amp;quot;&#039;&#039;&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;[https://support.google.com/pixelphone/answer/16340779? https://support.google.com/pixelphone/answer/16340779]&lt;br /&gt;
&lt;br /&gt;
Mirror, via the Wayback Machine: https://web.archive.org/web/20250703210308/https://support.google.com/pixelphone/answer/16340779&lt;br /&gt;
&amp;lt;/ref&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Google pixel needs certain battery replacements for 2025&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Compensation&amp;lt;!-- Written in present tense, as this situation is ongoing as of July 3, 2025. --&amp;gt;==&lt;br /&gt;
&lt;br /&gt;
===Request form sent out to users===&lt;br /&gt;
Google has asked users to provide the IMEI (International Mobile Equipment Identity) number of their Pixel 6a to determine whether their device is an &amp;quot;Impacted Device.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |title=Request a repair, payment, or future discount code |url=https://support.google.com/pixelphone/workflow/16310202 |url-status=live |archive-url=https://web.archive.org/web/20250703211550/https://support.google.com/pixelphone/workflow/16310202 |archive-date=2025-07-03 |access-date=2025-07-03}}&amp;lt;/ref&amp;gt; If the user&#039;s device is an &amp;quot;Impacted Device,&amp;quot; they may choose one of the following:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Free battery replacement&#039;&#039;&#039; (only available in: United States, Canada, United Kingdom, Germany, Singapore, and India)&lt;br /&gt;
*&#039;&#039;&#039;$150 USD&#039;&#039;&#039; (or local equivalent) &#039;&#039;&#039;discount code applicable towards the purchase of another Pixel phone&#039;&#039;&#039; on the Google Store (unavailable in certain countries)&lt;br /&gt;
*&#039;&#039;&#039;$100 USD&#039;&#039;&#039; (or local equivalent)&lt;br /&gt;
&lt;br /&gt;
Compensation&lt;br /&gt;
&lt;br /&gt;
===Payment-processing issues===&lt;br /&gt;
The $100 USD compensation option requires users to process payment through [[wikipedia:Payoneer|Payoneer]], which has many issues:&lt;br /&gt;
&lt;br /&gt;
*Users must provide sensitive personal information including Social Security numbers and bank details&lt;br /&gt;
*A $3 USD processing fee is deducted from the compensation&lt;br /&gt;
*An annual account fee of $29.95 USD is charged if the account balance does not exceed $2,000 USD in transactions within 12 months&amp;lt;nowiki&amp;gt;&amp;lt;ref&amp;gt;&amp;lt;/nowiki&amp;gt;{{Cite web |title=Annual account fee |url=https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |url-status=live |access-date=25 Mar 2025 |website=[[Payoneer]] |archive-url=http://web.archive.org/web/20251129174745/https://payoneer.custhelp.com/app/answers/detail/a_id/43738/~/annual-account-fee |archive-date=29 Nov 2025}}&amp;lt;nowiki&amp;gt;&amp;lt;/ref&amp;gt;&amp;lt;/nowiki&amp;gt; https://support.google.com/pixelphone/workflow/16310202&lt;br /&gt;
*Users report being advised to immediately delete their Payoneer account after receiving compensation to avoid fees&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |title=I have replaced battery in a local shop not supported by Google |url=https://www.reddit.com/r/Pixel4a/comments/1i1e4ds/i_have_replaced_battery_in_a_local_shop_not/ |url-status=live |access-date=25 Mar 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Store-credit limitations===&lt;br /&gt;
[[File:Pixel 6a support page for determining eligibility for program.png|thumb|alt=Screenshot of Google&#039;s compensation options for the Pixel 6a Battery Performance Program.|Screenshot of Google&#039;s compensation options for the Pixel 6a Battery Performance Program.]]&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
===Reimbursement===&lt;br /&gt;
There is an option if you have had your 6a battery replaced at an authorized service center prior to the program announcement.&lt;br /&gt;
[[File:Pixel 6a support page for determining eligibility for program - previously replaced battery.png|thumb|alt=Have you recently had your battery repaired at an authorized repair partner|Have you recently had your battery repaired at an authorized repair partner]]&lt;br /&gt;
&lt;br /&gt;
==Aftermath of software update==&lt;br /&gt;
After the update, users experience a battery cap of 80%, a message in the settings app&#039;s batttery section, Placeholder&lt;br /&gt;
&lt;br /&gt;
===Battery-performance issues===&lt;br /&gt;
Users have reported several issues following the update: Including inability to charge&amp;lt;ref&amp;gt;{{Cite web |date=19 Jul 2025 |title=My pixel 6a doesn&#039;t charge - at all - after update |url=https://old.reddit.com/r/pixel_phones/comments/1m42zn3/my_pixel_6a_doesnt_charge_at_all_after_update/ |url-status=live |archive-url=https://web.archive.org/web/20250721024418/https://old.reddit.com/r/pixel_phones/comments/1m42zn3/my_pixel_6a_doesnt_charge_at_all_after_update/ |archive-date=21 Jul 2025 |access-date=21 Jul 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=18 Jul 2025 |title=Will it charge? |url=https://old.reddit.com/r/Pixel6/comments/1m2xtlt/will_it_charge/ |url-status=live |archive-url=https://web.archive.org/web/20250721024834/https://old.reddit.com/r/Pixel6/comments/1m2xtlt/will_it_charge/ |archive-date=21 Jul 2025 |access-date=21 Jul 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
===Safety issue===&lt;br /&gt;
A Pixel 6a caught fire after the update, indicating the Battery Performance Program isn&#039;t enough to prevent overheating&amp;lt;ref&amp;gt;{{Cite web |last=Whitwam |first=Ryan |date=29 Jul 2025 |title=Another Google Pixel 6a catches fire after battery-nerfing update |url=https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/ |url-status=live |archive-url=https://web.archive.org/web/20250729114215/https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/ |archive-date=29 Jul 2025 |website=Arstechnica}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Battery-replacement complications===&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
===Technical evidence of battery changes===&lt;br /&gt;
The battery voltage has been dropped to below 4.0V after the update, reducing the actual battery capacity to below 60%&amp;lt;ref&amp;gt;{{Cite web |date=10 Jul 2025 |title=Thank you Google for Fast Charging Update /s |url=https://old.reddit.com/r/Pixel6aUsers/comments/1lwf3p5/thank_you_google_for_fast_charging_update_s/ |url-status=live |archive-url=https://web.archive.org/web/20250721025129/https://old.reddit.com/r/Pixel6aUsers/comments/1lwf3p5/thank_you_google_for_fast_charging_update_s/|archive-date=2025-07-21 |access-date=2025-07-20 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Possible technical rationale==&lt;br /&gt;
While Google has not provided detailed technical explanations for the update, there are several known factors about lithium-ion battery aging that could potentially justify such measures:&lt;br /&gt;
&lt;br /&gt;
===Aging lithium-ion batteries===&lt;br /&gt;
Lithium-ion batteries face degradation as they age:&lt;br /&gt;
*Loss of active lithium ions through repeated charge cycles&lt;br /&gt;
*Growth of the Solid Electrolyte Interphase (SEI) layer&lt;br /&gt;
*Physical expansion &amp;amp; contraction stress during charging cycles&lt;br /&gt;
*Potential for dendrite formation in aged cells&lt;br /&gt;
*Increased internal resistance over time&amp;lt;ref&amp;gt;{{Cite web |last=Chu |first=Tien-Fu |last2=Rajendran |first2=Raja |last3=Kuznetsova |first3=Iren |last4=Wang |first4=Gou-Jen |date=31 Mar 2020 |title=High-power, non-enzymatic glucose biofuel cell based on a nano/micro hybrid-structured Au anode |url=https://www.sciencedirect.com/science/article/abs/pii/S0378775320301476 |url-status=live |access-date=22 Mar 2025 |website=ScienceDirect}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Safety considerations===&lt;br /&gt;
Several factors specific to the Pixel 6a situation could indicate that this was a battery safety concern:&lt;br /&gt;
*The device was released in July 2022; many units are approaching 3 years of use&lt;br /&gt;
*The mandatory nature of the update suggests safety implications rather than performance optimization&lt;br /&gt;
*There have been reports of the device spontaneously catching on fire&lt;br /&gt;
===Precedent in mobile phones===&lt;br /&gt;
Similar battery-related interventions have occurred previously; Google&#039;s own Pixel 4a in January of 2025 and Apple&#039;s 2017 iPhone throttling was done to prevent unexpected shutdowns in devices with degraded batteries.&lt;br /&gt;
&lt;br /&gt;
===Potential manufacturing variables===&lt;br /&gt;
Several factors could explain why only certain devices are affected:&lt;br /&gt;
*Different battery suppliers or manufacturing batches&lt;br /&gt;
*Variations in battery cell chemistry or construction&lt;br /&gt;
*Manufacturing date ranges coinciding with specific material supplies&lt;br /&gt;
*Quality control variations between production runs&lt;br /&gt;
&lt;br /&gt;
==Media Articles==&lt;br /&gt;
https://9to5google.com/2025/07/02/pixel-6a-battery-update-details/&lt;br /&gt;
&lt;br /&gt;
https://www.androidauthority.com/pixel-6a-battery-limit-3573411/&lt;br /&gt;
&lt;br /&gt;
https://www.theverge.com/news/697103/google-android16-update-pixel-6a-battery-overheating-fix-july-8&lt;br /&gt;
&lt;br /&gt;
https://9to5google.com/2025/07/02/google-removes-pixel-6a-factory-images/&lt;br /&gt;
&lt;br /&gt;
https://www.techradar.com/phones/google-pixel-phones/the-pixel-6a-will-get-a-mandatory-update-that-will-reduce-battery-capacity-soon-and-other-pixel-phones-could-be-next&lt;br /&gt;
&lt;br /&gt;
==Criticism by community==&lt;br /&gt;
&lt;br /&gt;
#This update is an automatic update &#039;&#039;&#039;users can not opt&#039;&#039;&#039; &#039;&#039;&#039;out&#039;&#039;&#039; of.&lt;br /&gt;
#Despite claim, this update &#039;&#039;&#039;does not prevent&#039;&#039;&#039; the phone from overheating or catching fire, as shown by this user whose Pixel 6a that got the July update, caught fire while charging overnight&amp;lt;ref&amp;gt;{{Cite web |last=Whitwam |first=Ryan |date=29 Jul 2025 |title=Another Google Pixel 6a catches fire after battery-nerfing update |url=https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/?comments-page=1#comments |url-status=live |archive-url=https://web.archive.org/web/20250728172217/https://arstechnica.com/gadgets/2025/07/another-google-pixel-6a-catches-fire-after-battery-nerfing-update/ |archive-date=2025-07-28 |access-date=4 Aug 2025 |website=Ars Technica}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=27 Jul 2025 |title=I&#039;m the 3rd one posting this for this month. Pixel 6a caught on fire right next to me on the nightstand. |url=https://old.reddit.com/r/GooglePixel/comments/1ma6hpa/im_the_3rd_one_posting_this_for_this_month_pixel/ |url-status=live |archive-url=https://web.archive.org/web/20250728055102/https://old.reddit.com/r/GooglePixel/comments/1ma6hpa/im_the_3rd_one_posting_this_for_this_month_pixel/ |archive-date=2025-07-28 |access-date=28 Jul 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Restoring battery functionality==&lt;br /&gt;
&lt;br /&gt;
===Replacing the battery===&lt;br /&gt;
Placeholder&lt;br /&gt;
&lt;br /&gt;
Google has removed all official images for the pixel 6a released prior to the date of this program&#039;s inception.&lt;br /&gt;
&lt;br /&gt;
===Rolling-back Android===&lt;br /&gt;
By editing android-info.txt file, Users are able to bypass the anti-rollback bootloader update and successfully downgrade Android 14 from Android 16&amp;lt;ref&amp;gt;{{Cite web |date=19 Jul 2025 |title=Hey guys! I just rollback to android14 success! |url=https://xdaforums.com/t/hey-guys-i-just-rollback-to-android14-success.4750539/ |url-status=live |archive-url=https://web.archive.org/web/20250721022623/https://xdaforums.com/t/hey-guys-i-just-rollback-to-android14-success.4750539/ |archive-date=21 Jul 2025 |access-date=21 Jul 2025 |website=XDA Developers}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Pixel]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Nest_thermostat_smart_features_disabled&amp;diff=54754</id>
		<title>Google Nest thermostat smart features disabled</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Nest_thermostat_smart_features_disabled&amp;diff=54754"/>
		<updated>2026-05-25T12:49:54Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{IncidentCargo&lt;br /&gt;
|Company=Google, Nest&lt;br /&gt;
|StartDate=2025-10-25&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=Active&lt;br /&gt;
|ProductLine=Nest Learning Thermostat&lt;br /&gt;
|Product=1st generation 2011, 2nd generation 2012, 2nd generation Europe version 2014&lt;br /&gt;
|ArticleType=Incident&lt;br /&gt;
|Type=Abandonware, Service Termination&lt;br /&gt;
|Description=Google is ending support for 1st/2nd generation Nest thermostats October 2025, removing app control and safety features despite working hardware.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[Google]] has announced the discontinuation of cloud-based support for first and second-generation &#039;&#039;&#039;[[Google Nest]]&#039;&#039;&#039; Learning Thermostats, affecting devices purchased between 2011-2014. While the thermostats will continue basic operation, all smart features and remote capabilities will be permanently disabled.&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
Nest Labs launched the Nest Learning Thermostat in 2011, introducing smart thermostats to the mainstream market. The company was acquired by Google in 2014 for $3.2 billion. First and second-generation Nest thermostats were marketed as premium one-time purchases with cloud-based functionality as core features, including smartphone control, voice assistant integration, and home automation capabilities.&lt;br /&gt;
&lt;br /&gt;
==The discontinuation announcement==&lt;br /&gt;
On April 25, 2025, Google officially announced that support would end for the following devices on October 25, 2025:&amp;lt;ref name=&amp;quot;official&amp;quot;&amp;gt;{{Cite web |title=Support changes to our earliest generation Nest Learning Thermostats |url=https://www.googlenestcommunity.com/t5/Blog/Support-changes-to-our-earliest-generation-Nest-Learning-Thermostats/ba-p/713068 |date=2025-04-25 |access-date=2025-07-13 |website=Google Nest Community |archive-url=http://web.archive.org/web/20260127215416/https://www.googlenestcommunity.com/t5/Blog/Support-changes-to-our-earliest-generation-Nest-Learning-Thermostats/ba-p/713068 |archive-date=27 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;google-announcement&amp;quot;&amp;gt;[https://support.google.com/googlenest/answer/16233096 &amp;quot;Upcoming End of Support for Nest Learning Thermostats (1st and 2nd Gen) - Google Nest Help.&amp;quot;] Google.com, ([https://web.archive.org/web/20260227051701/https://support.google.com/googlenest/answer/16233096 Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Nest Learning Thermostat (1st generation, 2011)&lt;br /&gt;
*Nest Learning Thermostat (2nd generation, 2012)&lt;br /&gt;
*Nest Learning Thermostat (2nd generation, Europe version, 2014)&lt;br /&gt;
&lt;br /&gt;
===Features being discontinued===&lt;br /&gt;
After October 25, 2025, affected devices will lose:&amp;lt;ref name=&amp;quot;official&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;google-announcement&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Remote control via Nest and Google Home apps&lt;br /&gt;
*Google Assistant and third-party voice assistant integration&lt;br /&gt;
*Home/Away Assist functionality&lt;br /&gt;
*Push notifications&lt;br /&gt;
*Software and security updates&lt;br /&gt;
*All cloud-based features and connected services&lt;br /&gt;
&lt;br /&gt;
===Safety feature impact===&lt;br /&gt;
The discontinuation affects the Emergency Shutoff feature, which automatically shuts off heating systems when Nest Protect smoke detectors sense carbon monoxide.&amp;lt;ref name=&amp;quot;emergency-shutoff&amp;quot;&amp;gt;[https://support.google.com/googlenest/answer/9245889 &amp;quot;What you need for Emergency Shutoff to work - Google Nest Help.&amp;quot;] Google.com, ([https://web.archive.org/web/20260121043913/https://support.google.com/googlenest/answer/9245889 Archived])&amp;lt;/ref&amp;gt; Google has confirmed that &amp;quot;Nest Protects will also disconnect from the thermostat and Emergency Shut-off will no longer run.&amp;quot;&amp;lt;ref name=&amp;quot;google-announcement&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Remaining functionality===&lt;br /&gt;
Google states that basic thermostat functions accessible directly on the device will continue to work, including:&amp;lt;ref name=&amp;quot;google-announcement&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pre-set temperature schedules&lt;br /&gt;
*Manual temperature adjustments&lt;br /&gt;
*Mode switching (heat/cool)&lt;br /&gt;
*Auto-Schedule settings management&lt;br /&gt;
&lt;br /&gt;
==Harm to consumers==&lt;br /&gt;
The discontinuation removes core features that were primary selling points when consumers purchased these devices. Users who built smart home systems around these thermostats face the loss of functionality they paid for, with no option for local control or open-source alternatives. The removal of the carbon monoxide safety shutoff feature presents particular concern for consumer safety.&lt;br /&gt;
&lt;br /&gt;
==Company response and compensation==&lt;br /&gt;
Google cited the age of the hardware as the primary reason, stating it had become &amp;quot;increasingly challenging to continue to update these products.&amp;quot;&amp;lt;ref name=&amp;quot;official&amp;quot; /&amp;gt; The company offered limited-time discounts to affected customers:&lt;br /&gt;
&lt;br /&gt;
*United States: $130 off 4th generation Nest Learning Thermostat&lt;br /&gt;
*Canada: $160 off 4th generation model&lt;br /&gt;
*Europe: 50% off Tado Smart Thermostat X Starter Kit&amp;lt;ref name=&amp;quot;official&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
No options were provided for continuing use through open-source integrations, local control, or third-party services.&lt;br /&gt;
&lt;br /&gt;
==Public response==&lt;br /&gt;
The announcement generated significant criticism from consumers and technology commentators. Carl T. Bergstrom summarized the sentiment: &amp;quot;We&#039;re Google, and we&#039;re going to brick your perfectly functional thermostat after buying the company that made it.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |title=Carl T. Bergstrom on Bluesky |url=https://bsky.app/profile/carlbergstrom.com/post/3ltkvrz26tc2u |date=2025-07-09 |access-date=2025-07-13 |archive-url=http://web.archive.org/web/20251126232013/https://bsky.app/profile/carlbergstrom.com/post/3ltkvrz26tc2u |archive-date=26 Nov 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;chrome&amp;quot;&amp;gt;{{Cite web |title=Google ends support for Nest Learning Thermostat Gen 1 &amp;amp; 2 |url=https://chromeunboxed.com/your-old-nest-thermostat-is-going-to-lose-app-control-later-this-year/ |date=2025-04-29 |access-date=2025-07-13 |website=Chrome Unboxed |archive-url=http://web.archive.org/web/20251128071758/https://chromeunboxed.com/your-old-nest-thermostat-is-going-to-lose-app-control-later-this-year/ |archive-date=28 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Current status==&lt;br /&gt;
As of October 2025, the discontinuation happened. Affected consumers are advised to:&lt;br /&gt;
&lt;br /&gt;
*Document current device functionality and integrations&lt;br /&gt;
*Ensure alternative carbon monoxide safety measures are in place before the cutoff date&lt;br /&gt;
*Save all communications from Google/Nest regarding the discontinuation&lt;br /&gt;
*Consider filing complaints with consumer protection agencies if appropriate&lt;br /&gt;
*A community driven open source project has been created.&amp;lt;ref&amp;gt;{{Cite web |title=No Longer Evil Thermostat |url=https://nolongerevil.com/ |url-status=live |archive-url=https://web.archive.org/web/20260325163401/https://nolongerevil.com/ |archive-date=2026-03-25 |access-date=15 Apr 2026 |website=No Longer Evil}}&amp;lt;/ref&amp;gt; This gives owners the ability to flash a custom firmware on to the Gen 1 and 2 devices. Currently a free account is required as the firmware redirects the devices to the projects own servers. A full release of the API code is planned to allow users to create their own servers. This process, of course, carries the risk of bricking the device during the flashing process.  This initiative has been covered in an article on Toms Hardware Guide&amp;lt;ref&amp;gt;{{Cite web |last=Tyson |first=Mark |date=9 Nov 2025 |title=No Longer Evil Thermostat hack strips Google from Nest thermostat to heat your home better — open source project revives sunsetted hardware, gives more precise control |url=https://www.tomshardware.com/software/no-longer-evil-thermostat-heats-your-home-better-by-removing-google-revive-sunsetted-hardware-gain-more-precise-control-open-source |url-status=live |archive-url=https://web.archive.org/web/20260226012907/https://www.tomshardware.com/software/no-longer-evil-thermostat-heats-your-home-better-by-removing-google-revive-sunsetted-hardware-gain-more-precise-control-open-source |archive-date=2026-02-26 |website=Tom&#039;s Hardware}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Google Nest]]&lt;br /&gt;
[[Category:Smart home device obsolescence]]&lt;br /&gt;
[[Category:Cloud service dependency]]&lt;br /&gt;
[[Category:Remote deactivation]]&lt;br /&gt;
[[Category:Planned obsolescence]]&lt;br /&gt;
[[Category:Ownership revocation]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Nest&amp;diff=54753</id>
		<title>Google Nest</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Nest&amp;diff=54753"/>
		<updated>2026-05-25T12:48:59Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{Incomplete|Issue 1=Does not follow ProductLine format well|Issue 2=No citations are present}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[wikipedia:Google Nest|Google Nest]]&#039;&#039;&#039;, formerly branded &#039;&#039;&#039;Google Home&#039;&#039;&#039;, is a line of smart home products including smart speakers, smart displays, streaming devices, thermostats, smoke detectors, routers and security systems including smart doorbells, cameras and smart locks.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Google Nest thermostat smart features disabled===&lt;br /&gt;
{{Main|Google Nest thermostat smart features disabled}}&lt;br /&gt;
&lt;br /&gt;
===Google Nest Protect forced to use Google app===&lt;br /&gt;
{{Main|Google Nest Protect forced to use Google app}}&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
[[Category:Google Nest| ]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Chromecast&amp;diff=54752</id>
		<title>Google Chromecast</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Chromecast&amp;diff=54752"/>
		<updated>2026-05-25T12:48:28Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{SloppyAI}}&lt;br /&gt;
&lt;br /&gt;
{{ProductLineCargo&lt;br /&gt;
|Logo=Collection of Chromecast devices.jpg&lt;br /&gt;
|Company=Google|ReleaseYear=2013|InProduction=No|Description=Google Chromecast is a line of digital media players developed by Google. The devices, designed as small dongles, allow users with a mobile device or personal computer to play online content}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Google Chromecast&#039;&#039;&#039; is a line of digital media players developed by Google. The devices, designed as small dongles, allow users with a mobile device or personal computer to play online content on a high-definition television or home audio system through mobile and web apps that support the Google Cast technology.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
===User freedom===&lt;br /&gt;
Originally marketed as a simple, &amp;quot;plug-and-play&amp;quot; solution for streaming, Chromecast has increasingly moved toward a closed ecosystem. Early models allowed for basic setup via a PC or simple browser interface. However, Google transitioned to a mandatory requirement for the &#039;&#039;&#039;Google Home app&#039;&#039;&#039; on a compatible smartphone or tablet for setup and management. This shift forces users into the Google mobile ecosystem and creates a barrier for those without modern smartphones or those who wish to maintain a &amp;quot;decoupled&amp;quot; home theater setup.&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
As a hardware extension of the Google ecosystem, Chromecast acts as a significant data collection node. It tracks usage patterns, including which apps are used, the duration of viewing sessions, and the domains from which content is cast. Because it is managed via the Google Home app, this data is tied directly to a user&#039;s primary Google account, enabling detailed cross-device profiling for advertising purposes.&lt;br /&gt;
&lt;br /&gt;
===Business model===&lt;br /&gt;
The Chromecast business model transitioned from selling low-cost hardware to high-volume users to a service-based model. By integrating &#039;&#039;&#039;Google TV&#039;&#039;&#039; into later models, Google transformed the device from a passive receiver into an active content recommendation engine. This allows Google to capture revenue through featured placements, app subscriptions, and targeted advertising on the home screen.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===Mandatory Google Home App Requirement===&lt;br /&gt;
Initially, Chromecast devices could be set up using a laptop or a simple web interface. Google eventually deprecated these methods, making the &#039;&#039;&#039;Google Home app&#039;&#039;&#039; the exclusive way to set up and manage the hardware. This has significant implications for consumer rights:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Accessibility:&#039;&#039;&#039; Customers who do not own a smartphone or have older devices that cannot run the latest Google Home app are unable to use a product they purchased.&lt;br /&gt;
*&#039;&#039;&#039;Forced Ecosystem:&#039;&#039;&#039; Users are forced to agree to the Google Home Terms of Service and Privacy Policy simply to use the basic functions of their television hardware.&lt;br /&gt;
&lt;br /&gt;
===Feature Removal from Integrated TVs (e.g., Caixon EC43S1UA)===&lt;br /&gt;
The shift to app-only control has negatively impacted &amp;quot;Chromecast Built-in&amp;quot; devices. Certain smart televisions, such as the &#039;&#039;&#039;Caixon EC43S1UA&#039;&#039;&#039;, relied on internal Chromecast modules for their primary &amp;quot;smart&amp;quot; functionality.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Diminished Value:&#039;&#039;&#039; When Google updates the casting protocols or setup requirements to favor the Home app, older integrated hardware often becomes buggy or unresponsive.&lt;br /&gt;
*&#039;&#039;&#039;Loss of Functionality:&#039;&#039;&#039; Owners of these TVs have reported that they can no longer cast content as intended, effectively removing a core advertised feature of the product post-purchase without compensation.&lt;br /&gt;
&lt;br /&gt;
===Discontinuation of the Chromecast Brand (2024)===&lt;br /&gt;
In August 2024, Google announced the end of the Chromecast line, replacing it with the &#039;&#039;&#039;Google TV Streamer&#039;&#039;&#039;. While Google has promised continued software updates for recent Chromecast models, the move marks a shift toward more expensive, &amp;quot;set-top box&amp;quot; style hardware. This raises concerns about &#039;&#039;&#039;planned obsolescence&#039;&#039;&#039;, as older Chromecast &amp;quot;pucks&amp;quot; may eventually lose compatibility with modern apps as Google focuses development on the newer Streamer architecture.&lt;br /&gt;
&lt;br /&gt;
===Audio Casting Limitations===&lt;br /&gt;
Google was involved in a long-standing legal battle with &#039;&#039;&#039;Sonos&#039;&#039;&#039; regarding multi-room audio patents. As a result of this dispute, Google was forced to remove the ability to adjust the volume of a &amp;quot;Speaker Group&amp;quot; (multiple Chromecasts playing at once) using the physical volume buttons on a smartphone, requiring users to open the app and adjust each device individually. This degraded the user experience for thousands of customers who had purchased the devices specifically for synchronized home audio.&lt;br /&gt;
&lt;br /&gt;
[[Category:Google|Chromecast]]&lt;br /&gt;
[[Category:Anti-consumer practices]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Jamboard&amp;diff=54751</id>
		<title>Google Jamboard</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Jamboard&amp;diff=54751"/>
		<updated>2026-05-25T12:48:00Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#seo:&lt;br /&gt;
|description=Google Jamboard was a $4,999 whiteboard remotely disabled in 2024 with no refund for buyers. EDU got Avocor replacements; everyone else got nothing.&lt;br /&gt;
}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|ReleaseYear=2016&lt;br /&gt;
|InProduction=No&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Educational Technology&lt;br /&gt;
|Logo=Google Jamboard logomark.svg&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|Website=https://support.google.com/jamboard/answer/14084927&lt;br /&gt;
|Description=Google killed its $4,999 whiteboard in 2024; no refunds for buyers, factory resets brick the device, exported data arrived as blank PDFs&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;&#039;Google Jamboard&#039;&#039;&#039; was a $4,999 55-inch interactive digital whiteboard announced in October 2016 and shipped to businesses in May 2017.&amp;lt;ref name=&amp;quot;Verge&amp;quot;&amp;gt;{{Cite web |url=https://www.theverge.com/2017/5/23/15680250/google-jamboard-digital-whiteboard-hands-on-video |title=Google made a $5,000 whiteboard — and it&#039;s weirdly fun |first=Jacob |last=Kastrenakes |work=The Verge |date=2017-05-23 |access-date=2025-09-01 |archive-url=https://web.archive.org/web/20250428131124/https://www.theverge.com/2017/5/23/15680250/google-jamboard-digital-whiteboard-hands-on-video |archive-date=2025-04-28 |url-status=live}}&amp;lt;/ref&amp;gt; Beyond the hardware price, Google required a $600 annual management fee to keep [[Cloud (service)|cloud]] features active.&amp;lt;ref name=&amp;quot;TechCrunch-pricing&amp;quot;&amp;gt;{{Cite web |url=https://techcrunch.com/2017/03/09/googles-jamboard-pricing/ |title=Google&#039;s Jamboard will cost $5,000, plus an annual management fee |first=Brian |last=Heater |work=TechCrunch |date=2017-03-09 |access-date=2026-03-26}}&amp;lt;/ref&amp;gt; In September 2023, [[Google]] announced that Jamboard cloud features would end by October 2024, with the app shutting down December 31, 2024 and remaining Jam files deleted from Google&#039;s servers in Q1 2025.&amp;lt;ref name=&amp;quot;Google24&amp;quot;&amp;gt;{{Cite web |title=Google Jamboard is winding down |url=https://support.google.com/jamboard/answer/14084927?hl=en |website=Google Support |access-date=2025-09-01 |archive-url=http://web.archive.org/web/20260222143812/https://support.google.com/jamboard/answer/14084927?hl=en |archive-date=2026-02-22}}&amp;lt;/ref&amp;gt; Buyers received no hardware refund. Factory-reset devices request an activation code that Google can&#039;t provide; users must click &amp;quot;Skip Activation&amp;quot; to access a limited offline whiteboard mode.&amp;lt;ref name=&amp;quot;Google-EOL&amp;quot;&amp;gt;{{Cite web |url=https://support.google.com/a/answer/13342662?hl=en |title=Jamboard device end of life information |website=Google Workspace Admin Help |access-date=2026-03-26}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer-impact summary==&lt;br /&gt;
&lt;br /&gt;
===Freedom===&lt;br /&gt;
The Jamboard Hardware Agreement states that &amp;quot;Google is under no obligation to provide Customer with Hardware, Hardware replacement, Hardware updates, or Hardware support under this Agreement.&amp;quot;&amp;lt;ref name=&amp;quot;JBHA&amp;quot;&amp;gt;{{Cite web |url=https://workspace.google.com/terms/jamboard/ |title=Jamboard Hardware Agreement |website=Google Workspace |access-date=2025-09-01 |archive-url=https://web.archive.org/web/20250615031347/https://workspace.google.com/terms/jamboard/ |archive-date=2025-06-15 |url-status=live}}&amp;lt;/ref&amp;gt; The same agreement prohibits owners from the following actions: &amp;quot;adapt, alter, modify, decompile, translate, disassemble, or reverse engineer the Service and/or the Hardware.&amp;quot;&amp;lt;ref name=&amp;quot;JBHA&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Privacy===&lt;br /&gt;
Jamboard used the same privacy policy as all Google Drive services, which states &amp;quot;we will not use a Private document for marketing or promotional campaigns&amp;quot; and &amp;quot;we will not change a Private document into a Public one.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |url=https://support.google.com/drive/answer/2450387?hl=en |title=Google Drive Terms of Service |date=2020-03-31 |website=Google Drive |access-date=2025-09-01 |archive-url=http://web.archive.org/web/20260128013151/https://support.google.com/drive/answer/2450387?hl=en |archive-date=2026-01-28}}&amp;lt;/ref&amp;gt; After Google deleted all Jam files in Q1 2025, those privacy guarantees became moot; the documents no longer existed in any form.&amp;lt;ref name=&amp;quot;Google-export&amp;quot;&amp;gt;{{Cite web |url=https://support.google.com/jamboard/answer/13864841?hl=en |title=Export your jams |website=Google Jamboard Help |access-date=2026-03-26 |archive-url=http://web.archive.org/web/20251023184211/https://support.google.com/jamboard/answer/13864841?hl=en |archive-date=2025-10-23}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Business model===&lt;br /&gt;
Google received revenue from two streams: the $4,999 hardware sale and recurring Google Workspace subscriptions from educational and business buyers.&amp;lt;ref&amp;gt;{{Cite web |url=https://www.techlearning.com/features/how-to-use-google-jamboard-for-teachers |title=Using Google Jamboard Before It Is Shut Down in 2025 |first=Luke |last=Edwards |date=2024-09-09 |work=Tech Learning |access-date=2025-09-01 |archive-url=http://web.archive.org/web/20250809030944/https://www.techlearning.com/features/how-to-use-google-jamboard-for-teachers |archive-date=2025-08-09}}&amp;lt;/ref&amp;gt; The mandatory $600 annual management fee covered Google Admin console access, firmware updates, and cloud connectivity; without it, the device couldn&#039;t save content or join Google Meet sessions.&amp;lt;ref name=&amp;quot;TechCrunch-pricing&amp;quot; /&amp;gt; Education customers with a Google Workspace for Education subscription paid the $600 management fee once as a perpetual license, with no recurring annual charge.&amp;lt;ref name=&amp;quot;BenQ-edu-license&amp;quot;&amp;gt;{{Cite web |url=https://sites.google.com/benq.com/jamboard-gsuiteforeducation/home |title=Google Jamboard for Education License |website=BenQ / Google |access-date=2026-03-26}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Market control===&lt;br /&gt;
Google Jamboard held a minor share of the collaborative whiteboard market. 6sense estimated Jamboard&#039;s market share at 3.68% of the collaborative whiteboard category.&amp;lt;ref name=&amp;quot;6sense&amp;quot;&amp;gt;{{Cite web |url=https://6sense.com/tech/collaborative-whiteboards/jamboard-market-share |title=Jamboard - Market Share, Competitor Insights in Collaborative Whiteboards |website=6sense |access-date=2026-03-26}}&amp;lt;/ref&amp;gt; Google itself acknowledged that &amp;quot;Jamboard users make up a small portion of our Workspace customer base.&amp;quot;&amp;lt;ref name=&amp;quot;Google-blog&amp;quot;&amp;gt;{{Cite web |url=https://workspace.google.com/blog/product-announcements/next-phase-digital-whiteboarding |title=Announcing the next phase of digital whiteboarding for Google Workspace |first=Dave |last=Citron |website=Google Workspace Blog |date=2023-09-28 |access-date=2026-03-26}}&amp;lt;/ref&amp;gt; Competing hardware included [[Microsoft]]&#039;s Surface Hub and [[Avocor]]&#039;s Series One Board.&amp;lt;ref name=&amp;quot;GD&amp;quot;&amp;gt;{{Cite web |date=2023-09-28 |title=The next phase of digital whiteboarding for Google Workspace |url=https://workspaceupdates.googleblog.com/2023/09/the-next-phase-of-digital-whiteboarding-for-google-workspace.html |website=Google Workspace Updates |archive-url=http://web.archive.org/web/20251220070801/https://workspaceupdates.googleblog.com/2023/09/the-next-phase-of-digital-whiteboarding-for-google-workspace.html |archive-date=2025-12-20}}&amp;lt;/ref&amp;gt; On the software side, FigJam, Lucidspark, and Miro all offered features Jamboard lacked: infinite canvas, templates, and voting.&amp;lt;ref name=&amp;quot;GD&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Hardware specifications==&lt;br /&gt;
The Jamboard ran on an NVIDIA Tegra X1 system-on-chip with a quad-core ARM Cortex-A57 CPU, 4 GB of RAM, and 16 GB of internal storage.&amp;lt;ref name=&amp;quot;LineageOS-GitHub&amp;quot;&amp;gt;{{Cite web |url=https://github.com/LineageOS/android_device_google_baracus |title=LineageOS/android_device_google_baracus: Device configuration for Google Jamboard |website=GitHub |access-date=2026-03-26}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;AndroidAuthority-LineageOS&amp;quot;&amp;gt;{{Cite web |url=https://www.androidauthority.com/jamboard-lineageos-3590035/ |title=Google let Jamboard die, but now LineageOS offers new life |work=Android Authority |date=2025-08-21 |access-date=2026-03-26}}&amp;lt;/ref&amp;gt; The 55-inch 4K display supported up to 16 simultaneous touch points.&amp;lt;ref name=&amp;quot;Wikipedia-Jamboard&amp;quot;&amp;gt;{{Cite web |url=https://en.wikipedia.org/wiki/Jamboard |title=Jamboard |website=Wikipedia |access-date=2026-03-26}}&amp;lt;/ref&amp;gt; The same Tegra X1 chip powers the original Nintendo Switch and the NVIDIA Shield TV; it is a consumer-grade mobile processor, not a specialized enterprise component.&amp;lt;ref name=&amp;quot;AndroidAuthority-LineageOS&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google sold a rolling stand separately.&amp;lt;ref name=&amp;quot;TechCrunch-pricing&amp;quot; /&amp;gt; The hardware ran a custom build of Android, locked to Google&#039;s cloud services with no local-only operating mode.&lt;br /&gt;
&lt;br /&gt;
==Shutdown timeline==&lt;br /&gt;
Google announced the Jamboard shutdown on September 28, 2023, calling it &amp;quot;the next phase of digital whiteboarding for Google Workspace.&amp;quot;&amp;lt;ref name=&amp;quot;GD&amp;quot; /&amp;gt; The shutdown proceeded on a fixed schedule:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;September 28, 2023:&#039;&#039;&#039; Google announces end of Jamboard. Organizations told to export Jam files and evaluate FigJam, Lucidspark, or Miro as replacements.&amp;lt;ref name=&amp;quot;9to5-shutdown&amp;quot;&amp;gt;{{Cite web |date=2023-09-28 |title=Google shutting down Jamboard, offering transition to other whiteboard apps |url=https://9to5google.com/2023/09/28/google-jamboard/ |website=9to5Google |archive-url=http://web.archive.org/web/20260117232434/https://9to5google.com/2023/09/28/google-jamboard/ |archive-date=2026-01-17}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;September 30, 2024:&#039;&#039;&#039; All management and license subscriptions expire. Admin console management ends. Google prorates remaining subscription costs for organizations that had prepaid.&amp;lt;ref name=&amp;quot;Google24&amp;quot; /&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;October 1, 2024:&#039;&#039;&#039; Hardware reaches Auto Update Expiration (AUE). No more security or feature updates. The Jamboard app enters view-only mode; creating or editing Jams is no longer possible.&amp;lt;ref name=&amp;quot;Google24&amp;quot; /&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;December 31, 2024:&#039;&#039;&#039; The Jamboard app shuts down entirely. Hardware enters &amp;quot;unlicensed mode,&amp;quot; losing the ability to save content, join Google Meet, or perform any cloud-connected function.&amp;lt;ref name=&amp;quot;Google24&amp;quot; /&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;Q1 2025:&#039;&#039;&#039; Google runs an automated process to convert remaining Jam files in Google Drive into static PDFs, then deletes all original .jam files from its servers.&amp;lt;ref name=&amp;quot;Google-export&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Google&#039;s stated justification==&lt;br /&gt;
Google framed the shutdown as a response to user feedback. The official announcement stated that the company would &amp;quot;focus our efforts on core content collaboration across Docs, Sheets, and Slides&amp;quot; and rely on third-party partners for whiteboarding.&amp;lt;ref name=&amp;quot;GD&amp;quot; /&amp;gt; Google cited FigJam (by Figma), Lucidspark (by Lucid Software), and Miro as alternatives that offered features Jamboard never developed: infinite canvas sizes, complex templates, and voting mechanisms.&amp;lt;ref name=&amp;quot;GD&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The business rationale was straightforward. Jamboard users were, by Google&#039;s own admission, &amp;quot;a small portion&amp;quot; of the Workspace customer base.&amp;lt;ref name=&amp;quot;Google-blog&amp;quot; /&amp;gt; Rather than invest in catching up with dedicated whiteboard companies, Google integrated Miro, Lucidspark, and FigJam directly into Google Meet, Drive, and Calendar, offloading development costs to third parties while preserving Workspace functionality.&amp;lt;ref name=&amp;quot;GD&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===Remote deactivation and forced obsolescence===&lt;br /&gt;
{{Main|Google Jamboard shutdown}}&lt;br /&gt;
&lt;br /&gt;
On September 28, 2023, Google announced the complete shutdown of Jamboard. Cloud features would end October 1, 2024; the app would shut down December 31, 2024; and all remaining Jam files would be deleted from Google&#039;s servers in Q1 2025.&amp;lt;ref name=&amp;quot;9to5-shutdown&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Google-export&amp;quot; /&amp;gt; This affected organizations that had paid $4,999 per device plus the $600 annual management fee.&amp;lt;ref name=&amp;quot;Slashdot&amp;quot;&amp;gt;{{Cite web |title=$5,000 Google Jamboard Dies In 2024 -- Cloud-Based Apps Will Stop Working, Too |url=https://tech.slashdot.org/story/23/09/29/1951233/5000-google-jamboard-dies-in-2024----cloud-based-apps-will-stop-working-too |website=Slashdot |date=2023-09-29 |author=BeauHD |archive-url=http://web.archive.org/web/20251104131949/https://tech.slashdot.org/story/23/09/29/1951233/5000-google-jamboard-dies-in-2024----cloud-based-apps-will-stop-working-too |archive-date=2025-11-04}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After December 31, 2024, the devices entered &amp;quot;unlicensed mode&amp;quot;: no content saving, no Google Meet, no cloud-connected functions. The 55-inch 4K display still accepted HDMI input, but every Jamboard-specific feature was gone.&amp;lt;ref name=&amp;quot;Google24&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Data loss and forced migration====&lt;br /&gt;
Google permanently deleted all user-created Jams on the server side in Q1 2025. Users who didn&#039;t export in time lost their content. Google offered PDF conversion on what it described as a best-effort basis, warning that &amp;quot;sometimes the contents of a jam file may be corrupted, which prevents conversion to PDF, and in these cases, a blank PDF will be generated.&amp;quot;&amp;lt;ref name=&amp;quot;Google-export&amp;quot; /&amp;gt; Exported PNG files contained only a single frame of multi-page whiteboards.&amp;lt;ref name=&amp;quot;Google-export&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A Change.org petition gathered 499 supporters, arguing that Google Jamboard was &amp;quot;the only slide-based online collaborative whiteboard&amp;quot; and that thousands of teachers relied on the platform for interactive classes.&amp;lt;ref name=&amp;quot;Change&amp;quot;&amp;gt;{{Cite web |title=Petition: Save Jamboard |url=https://www.change.org/p/save-jamboard |website=Change.org |archive-url=http://web.archive.org/web/20251028235721/https://www.change.org/p/save-jamboard |archive-date=2025-10-28}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Lack of compensation for hardware purchasers====&lt;br /&gt;
Google offered zero hardware compensation to non-educational buyers.&amp;lt;ref name=&amp;quot;GD&amp;quot; /&amp;gt; The $4,999 device became an oversized HDMI display with no refund, no trade-in credit, and no alternative software path from Google.&lt;br /&gt;
&lt;br /&gt;
For educational institutions, Google partnered with Avocor to provide a replacement program: one free Avocor Board 65 per Jamboard, one free year of a Google Meet Hardware license (normally $250/year), a free stand or wall mount, and a 3-year warranty.&amp;lt;ref name=&amp;quot;Avocor-replacement&amp;quot;&amp;gt;{{Cite web |url=https://www.avocor.com/products/google-series-one-board-65/jamboard-replacement-program/ |title=Jamboard Replacement Program - Google Meet Series One |website=Avocor |access-date=2026-03-26 |archive-url=http://web.archive.org/web/20240618130002/https://www.avocor.com/products/google-series-one-board-65/jamboard-replacement-program/ |archive-date=2024-06-18 |url-status=dead}}&amp;lt;/ref&amp;gt; After the first free year, EDU buyers would need to pay $250/year for the Google Meet Hardware license to keep full functionality.&amp;lt;ref name=&amp;quot;Avocor-replacement&amp;quot; /&amp;gt; Non-education buyers received nothing.&lt;br /&gt;
&lt;br /&gt;
====Comparison to Google Stadia refunds====&lt;br /&gt;
When Google shut down Stadia in January 2023, it issued automatic refunds for all hardware purchases and game/add-on transactions made through the Google Store; only Stadia Pro subscription fees were excluded.&amp;lt;ref name=&amp;quot;Stadia-refund&amp;quot;&amp;gt;{{Cite web |url=https://support.google.com/stadia/answer/12790109?hl=en |title=Stadia Announcement FAQ |website=Google Stadia Help |access-date=2026-03-26}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Jamboard buyers received no equivalent. Google classified Jamboard as an enterprise product governed by B2B Workspace agreements and predefined Auto Update Expiration dates, removing any consumer-style refund obligation.&amp;lt;ref name=&amp;quot;JBHA&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Hardware lockdown and activation lock====&lt;br /&gt;
Factory-resetting a Jamboard after the shutdown prompts the device to request an activation code. Google&#039;s own Workspace Admin help page confirms: &amp;quot;If you click Next during the factory reset process, it prompts the Jamboard to request an activation code, which can&#039;t be provided. If you get this screen, turn the Jamboard on and off again.&amp;quot;&amp;lt;ref name=&amp;quot;Google-EOL&amp;quot; /&amp;gt; Users who click &amp;quot;Skip Activation&amp;quot; instead can access a limited offline whiteboard mode, but cannot save to Google Drive or use any cloud-connected features.&amp;lt;ref name=&amp;quot;Google-EOL&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====LineageOS community port====&lt;br /&gt;
Developers npjohnson, makinbacon, and Steel01 from the XDA Forums reverse-engineered the Jamboard to install a custom operating system.&amp;lt;ref name=&amp;quot;XDA-LineageOS&amp;quot;&amp;gt;{{Cite web |title=[OFFICIAL] LineageOS 22 for the Google Jamboard [Android TV/Tablet] |url=https://xdaforums.com/t/unofficial-lineageos-22-for-the-google-jamboard-wip.4755529/ |access-date=2026-03-26 |website=XDA Forums |author=npjohnson |date=2025-08-21}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In August 2025, the team released unofficial builds of [[wikipedia:LineageOS|LineageOS]] 22 (based on Android 15) in two variants: an Android TV build that converts the Jamboard into a 55-inch smart TV, and an Android tablet build that restores full 16-point multi-touch functionality.&amp;lt;ref name=&amp;quot;AndroidAuthority-LineageOS&amp;quot; /&amp;gt; Touch input works. [[Digital rights management|DRM]] playback is broken, display brightness control is still in progress, and the stylus eraser function is incompatible with the [[wikipedia:List_of_custom_Android_distributions|custom ROM]].&amp;lt;ref name=&amp;quot;XDA-LineageOS&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Google product discontinuation record==&lt;br /&gt;
The Killed by Google project catalogs 299+ Google products and services that have been discontinued.&amp;lt;ref name=&amp;quot;KilledByGoogle&amp;quot;&amp;gt;{{Cite web |url=https://killedbygoogle.com |title=Google Graveyard - Killed by Google |website=Killed by Google |access-date=2026-03-26}}&amp;lt;/ref&amp;gt; Jamboard appears on the list twice: once for the app (2016 to 2024) and once for the hardware (2017 to 2024).&amp;lt;ref name=&amp;quot;KilledByGoogle&amp;quot; /&amp;gt; Android Police noted that Google&#039;s pattern of killing hardware products makes it harder to recommend buying Google devices when they might not exist in 5 years.&amp;lt;ref name=&amp;quot;AP-google-kills&amp;quot;&amp;gt;{{Cite web |url=https://www.androidpolice.com/google-kills-tech/ |title=It&#039;s getting harder to recommend Google hardware when I know it might not exist in 5 years |first=Ben |last=Khalesi |work=Android Police |date=2026-02-22 |access-date=2026-03-26}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
No class-action lawsuits, state attorney general actions, or FTC complaints have been filed over the Jamboard shutdown as of March 2026. Google&#039;s Jamboard Hardware Agreement and predefined AUE dates appear to have insulated the company from warranty-based claims under the [[Magnuson-Moss Warranty Act]].&amp;lt;ref name=&amp;quot;JBHA&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Planned obsolescence]]&lt;br /&gt;
*[[Right to repair]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
==External links==&lt;br /&gt;
*[https://sites.google.com/eastpennsd.org/epsdtech/elementary/google/google-jamboard Google Jamboard introduction/tutorial (unofficial)]&lt;br /&gt;
&lt;br /&gt;
[[Category:Google|Jamboard]]&lt;br /&gt;
[[Category:Planned obsolescence]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Android&amp;diff=54750</id>
		<title>Android</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Android&amp;diff=54750"/>
		<updated>2026-05-25T12:46:59Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
{{ProductLineCargo&lt;br /&gt;
|ArticleType= Product&lt;br /&gt;
|Category= Software&lt;br /&gt;
|Company= Google&lt;br /&gt;
|InProduction= Yes&lt;br /&gt;
|Logo= Android Logo.svg&lt;br /&gt;
|ReleaseYear= 2008&lt;br /&gt;
|Website= https://android.com/&lt;br /&gt;
|Description= Android is the world&#039;s most widely used mobile operating system, with over 3.5 billion active users. Android devices collect extensive user data, often without clear opt-out options. Google&#039;s Android System SafetyCore was installed silently on all devices in 2025. Many manufacturers lock bootloaders, making it difficult for users to modify their software. Starting in 2026, third-party apps will face restrictions in several regions. Google&#039;s Chromecast protocol limits casting to Google-signed receivers. Google delayed the AOSP 16 QPR1 update without explanation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;{{Wplink|Android (operating_system)|Android}}&#039;&#039;&#039; is an operating system which started in 2003 and was acquired by &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; in 2005,&amp;lt;ref&amp;gt;{{Cite web |last=Elgin |first=Ben |title=Google Buys Android for Its Mobile Arsenal |url=http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm |website=Bloomberg Businessweek |date=17 Aug 2005 |access-date=12 Jul 2025 |url-status=dead |archive-url=https://web.archive.org/web/20110227182929/http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm |archive-date=27 Feb 2011}}&amp;lt;/ref&amp;gt; which made its first official release (Android 1.0) in 2008.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Announcing the Android 1.0 SDK, release 1 |url=https://android-developers.googleblog.com/2008/09/announcing-android-10-sdk-release-1.html |website=Android Developers Blog |date=23 Sep 2008 |access-date=8 Apr 2026 |url-status=live |archive-url=http://web.archive.org/web/20251216120521/https://android-developers.googleblog.com/2008/09/announcing-android-10-sdk-release-1.html |archive-date=16 Dec 2025}}&amp;lt;/ref&amp;gt; It is based on a modified version of the {{Wplink|Linux kernel}} and other open-source software, designed primarily for touchscreen-based mobile devices such as smartphones and tablets, but is also used in smart TVs, cameras, in-car infotainment systems, etc.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Why Android? |url=https://www.android.com/why-android/ |website=Android |date= |access-date=12 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20260221233734/https://www.android.com/why-android/ |archive-date=21 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The original &amp;quot;philosophy and goals&amp;quot; page of Android stated that its aim was &amp;quot;to make sure that there was no central point of failure, where one industry player could restrict or control the innovations of any other&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Philosophy and Goals |url=http://source.android.com/about/philosophy.html |website=Android |date= |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20120111091238/http://source.android.com/about/philosophy.html |archive-date=11 Jan 2012}}&amp;lt;/ref&amp;gt; This founding principle was abandoned with the [[Android Developer Verification]] plan announced in 2025 that is scheduled to come in effect in September 2026.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
&lt;br /&gt;
With over 3.5 billion active users, open-source flexibility, affordability, and extensive device ecosystems continue to shape consumer behavior, regional adoption, and technological advancements.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=G. |first=Nick |title=Android Market Share in 2025: Global Dominance and Key Insights |url=https://techjury.net/industry-analysis/android-market-share |website=techjury |date=4 Sep 2024 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250629102621/https://techjury.net/industry-analysis/android-market-share/ |archive-date=29 Jun 2025}}&amp;lt;/ref&amp;gt; Android&#039;s global reach, affordability, and device diversity make it the preferred OS for billions, particularly in emerging economies. It remains the world&#039;s most widely used mobile operating system, but its dominance has been accompanied by controversies from security vulnerabilities and privacy concerns to accusations of anti-competitive behavior and declining open-source commitments.&lt;br /&gt;
&lt;br /&gt;
===Market control===&lt;br /&gt;
Android remains the world&#039;s dominant mobile operating system (OS) as of 2025, holding a 72.23% global market share compared to iOS with 27.39%.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
*Asia &amp;amp; Africa: Android dominates with 95.16% in India, 86.8% in Indonesia, and 80.88% in Africa due to affordability and device variety.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last1=Qadir |first1=Salam |last2=Shaikh |first2=Sohaib |title=Android vs iOS Statistics 2025: Users, Revenue, and Global Trends |url=https://www.tekrevol.com/blogs/android-vs-ios-statistics/ |website=Tekrevol |date=10 Apr 2025 |access-date=15 May 2025 |url-status=deviated |archive-url=https://web.archive.org/web/20250515022542/https://www.tekrevol.com/blogs/android-vs-ios-statistics/ |archive-date=15 May 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*North America: Android holds 45% market share, trailing iOS (57.68%) in the U.S.A.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |last=Howarth |first=Josh |title=iPhone vs Android User Stats (2025 Data) |url=https://explodingtopics.com/blog/iphone-android-users |website=ExplodingTopics |date=24 Apr 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250709235506/https://explodingtopics.com/blog/iphone-android-users |archive-date=9 Jul 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Europe: Android leads with 65% market share, though iOS is strong in the UK (52.29%).&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;
*Affordability: Android devices range from $100 budget phones to premium flagships, making them accessible in emerging markets.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
*Device Variety: Multiple manufacturers ([[Samsung]], [[Xiaomi]], [[Oppo]]) offer diverse options, unlike Apple&#039;s closed ecosystem.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |last=Frąckiewicz |first=Marcin |title=Smartphone Wars 2025: Inside the Global Market Shake-Up, Trends, and Future Tech Disruptions |url=https://ts2.tech/en/smartphone-wars-2025-inside-the-global-market-shake-up-trends-and-future-tech-disruptions/ |website=Techstock&amp;lt;sup&amp;gt;2&amp;lt;/sup&amp;gt; |date=16 May 2025 |access-date=8 Apr 2025 |url-status=live |archive-url=https://web.archive.org/web/20250720045846/https://ts2.tech/en/smartphone-wars-2025-inside-the-global-market-shake-up-trends-and-future-tech-disruptions/ |archive-date=20 Jul 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this software. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===Apps cannot run writable files===&lt;br /&gt;
Apps targeting Android 10 are not allowed to execute files from their &amp;quot;home&amp;quot; folder, as this is enforced by the system.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Behavior changes: apps targeting API 29+&lt;br /&gt;
|url=https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission |website=Android |date= |access-date=2 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260209004831/https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission |archive-date=9 Feb 2026}}&amp;lt;/ref&amp;gt; While &amp;quot;targeting&amp;quot; any version is an opt-in choice, [[Google Play Store]] policy forbids apps that target old Android versions.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Meet Google Play&#039;s target API level requirement |url=https://developer.android.com/google/play/requirements/target-sdk |website=Android |date= |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260318030349/https://developer.android.com/google/play/requirements/target-sdk |archive-date=18 Mar 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author= |title=Google Play&#039;s Target API Level Policy |url=https://support.google.com/googleplay/android-developer/answer/16561298?hl=en |website=[[Google]] |date= |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260211153736/https://support.google.com/googleplay/android-developer/answer/16561298?hl=en |archive-date=11 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author= |title=Target API level requirements for Google Play apps |url=https://support.google.com/googleplay/android-developer/answer/11926878 |website=[[Google]] |date= |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260318030448/https://support.google.com/googleplay/android-developer/answer/11926878 |archive-date=18 Mar 2026}}&amp;lt;/ref&amp;gt; This negatively impacts apps such as {{Wplink|Termux}},&amp;lt;ref&amp;gt;{{Cite web |author=n0n3m4 |title=No more exec from data folder on targetAPI &amp;gt;= Android Q |url=https://github.com/termux/termux-app/issues/1072 |website=[[GitHub]] |date=18 Mar 2019 |access-date=2 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260315024821/https://github.com/termux/termux-app/issues/1072 |archive-date=15 Mar 2026}}&amp;lt;/ref&amp;gt; which must be &amp;quot;[[Sideloading|sideloaded]]&amp;quot; so that the policy is not applicable, otherwise they must find a way to bypass it (risking legal issues).&amp;lt;ref&amp;gt;{{Cite web |last=Kang &amp;lt;!-- Display name is &amp;quot;iamahuman&amp;quot; as of 8 Apr 2026. -Sojourna --&amp;gt; |first=Jinoh |title=Revisit the Android W^X problem |url=https://github.com/termux/termux-app/issues/2155 |website=[[GitHub]] |date=3 Jul 2021 |access-date=2 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260315024819/https://github.com/termux/termux-app/issues/2155 |archive-date=15 Mar 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Blocking sideloading of unverified Android apps (&#039;&#039;2026—2027&#039;&#039;)===&lt;br /&gt;
{{Main|Google Android restrict app sideloading}}&lt;br /&gt;
&lt;br /&gt;
Google announced in August 2025 that starting September 2026, unmodified Android devices in Brazil, Indonesia, Singapore and Thailand will no longer be allowed to install applications outside of the [[Google Play Store]] unless the developer has verified their identity with Google. The policy is aimed to be enforced world-wide in 2027.&amp;lt;ref&amp;gt;{{Cite web |last=Whitwam |first=Ryan |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/ |website=ArsTechnica |date=26 Aug 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250826032858/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=26 Aug 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |author=DoorStepSamm |title=Google&#039;s plan to end sideloading on Android&lt;br /&gt;
|url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ |website=XDA |date=26 Aug 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260409033222/https://xdaforums.com/t/ongoing-september-2026-googles-plan-to-end-sideloading-on-android.4756353/ |archive-date=9 Apr 2026}}&amp;lt;/ref&amp;gt; Devices without [[Google Mobile Services]] (GMS) or running a third-party {{Wplink|Read-only memory|ROM}} will be unaffected. However it&#039;s hard for users to bypass or spoof [[Google Play Integrity API|Google Play Integrity]] to hide their ROM or [[Jailbreak|root]] status to use utility apps such as most of banking apps.&amp;lt;ref&amp;gt;{{Cite web |author=HippoMan |title=[Discussion] The root-and-mod-hiding/fingerprint-spoofing/keybox-stealing cat-and-mouse game |url=https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |website=XDA |date=3 Apr 2022 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250823095950/https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |archive-date=23 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Data collection===&lt;br /&gt;
{{Main|Android data collection}}&lt;br /&gt;
&lt;br /&gt;
Android mobile devices, even when minimally configured, collect and share extensive user data with Google and provide few options for opting-out, raising privacy concerns. Settings for opting-out of sharing data with Google are generally hard to find, requiring users to search the device&#039;s settings and Google&#039;s settings to locate and toggle the settings on or off. The data shared with Google is sensitive user data including call logs, messages, data recorded from the device&#039;s microphone and camera, and more. This data is used by Google to improve the targeting of personalized advertisements and as training data for [[Google Gemini]].&lt;br /&gt;
&lt;br /&gt;
===Android System SafetyCore silent install===&lt;br /&gt;
{{Main|Android System SafetyCore}}&lt;br /&gt;
&lt;br /&gt;
On 22 January 2025, Google quietly rolled out Android System SafetyCore to all Android devices. The installation of the program neither informed consumers that it was installed, nor did it request consumers to install it onto their devices.&amp;lt;ref&amp;gt;{{Cite web |last=Baran |first=Guru |title=Google’s SafetyCore App Secretly Scans All Your Photos on Android Phones |url=https://cybersecuritynews.com/googles-safetycore-app-secretly-scans/ |website=Cyber Security News |date=27 Feb 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250227210543/https://cybersecuritynews.com/googles-safetycore-app-secretly-scans/ |archive-date=27 Feb 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===OEM Locked Bootloaders===&lt;br /&gt;
{{Main|Motorola}}&lt;br /&gt;
&lt;br /&gt;
In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found. Some OEMs like [[Samsung]] are now completely blocking [[bootloader unlocking]] on their phones regardless of region.&lt;br /&gt;
&lt;br /&gt;
===ADB restrictions===&lt;br /&gt;
Google has been adding more restrictions to what &amp;lt;code&amp;gt;[[wikipedia:Android_Debug_Bridge|adb]]&amp;lt;/code&amp;gt; can access.{{Citation needed|reason=since when?|date=2026-05-18}} For instance, if an app is not [https://developer.android.com/privacy-and-security/risks/android-debuggable debuggable], the user [[Data lock-in|cannot read any files in the app&#039;s data folder]]. Aside from transparency concerns, this makes full backups impossible, unless the app provides a way to export data. Google and many OEMs provide their own (proprietary) full-backup mechanisms, but those typically [[Forced account|require accounts]] and [[Forced cloud|cloud connections]]. Even if the app has &amp;lt;code&amp;gt;[https://developer.android.com/guide/topics/manifest/application-element#allowbackup allowBackup]&amp;lt;/code&amp;gt; enabled, Android 12 forbids backup-restore via ADB unless it&#039;s a device-to-device transfer.&amp;lt;ref&amp;gt;https://developer.android.com/about/versions/12/behavior-changes-12#backup-restore&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Android Cast restricted to Google-signed receivers===&lt;br /&gt;
In Android, streaming over network is referred as &amp;quot;Casting&amp;quot;. In Android 4.4, {{Wplink|Miracast}} support was introduced.&lt;br /&gt;
&lt;br /&gt;
In Android 9, Miracast (an open standard) was fully replaced by the proprietary {{Wplink|Google Cast|Chromecast protocol}} (Google Cast). Google Cast includes signing key verification of both the Cast source and receiver device, meaning that since Android 9 it is no longer possible to cast high quality content to receivers which aren&#039;t signed by Google. This means that unlike AirPlay on Apple devices, there&#039;s no way to stream multi-channel Hi-Fi audio on Android unless the receiver has a valid vendor signature.&amp;lt;ref&amp;gt;{{Cite web |last=Weiske |first=Christian |title=Android/Lineage OS and Screen mirroring (&amp;quot;Cast&amp;quot;) |url=https://p.cweiske.de/669 |website=p.cweiske.de |date=31 Aug 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 |archive-date=31 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Google delaying AOSP 16 QPR1 update without proper explanation===&lt;br /&gt;
&#039;&#039;NOTE: This section needs to be re-written in past tense, the technical verbiage explained or linking to the relevant Wikipedia page using &amp;lt;nowiki&amp;gt;{{Wplink}}&amp;lt;/nowiki&amp;gt;, and how it is applicable from a consumer rights standpoint (otherwise should be deleted). Also remember to check for spelling, punctuation, and grammar.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Google is releasing Android 16 QPR1 update for Pixel devices on September 3, 2025, normally AOSP will get QPR1 update in 24-48 hours after Pixel devices. But until now, there still no QPR1 update for AOSP. Google later told Android Authority said they will release the source code &amp;quot;in the coming weeks.&amp;quot; But they doesn&#039;t explain why they delaying QPR1 update for AOSP 16&amp;lt;ref&amp;gt;{{Cite web |last=Mishaal |first=Rahman |title=Android 16 QPR1’s source code is nowhere to be found, but Google swears it’s coming |url=https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |website=Android Authority |date=10 Sep 2025 |access-date=18 Oct 2025 |url-status=live |archive-url=https://web.archive.org/web/20250911142548/https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |archive-date=11 Sep 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Update : Google is now releasing QPR1 update for AOSP 16 after 2 months delay&amp;lt;ref&amp;gt;{{Cite web |last=Mishaal |first=Rahman |title=The wait is over: Android 16 QPR1&#039;s source code is now available on AOSP |url=https://www.androidauthority.com/android-16-qpr1-source-code-available-3614853/ |website=Android Authority |date=12 Nov 2025 |access-date=12 Nov 2025 |url-status=live |archive-url=https://web.archive.org/web/20251112032612/https://www.androidauthority.com/android-16-qpr1-source-code-available-3614853/ |archive-date=12 Nov 2025}}&amp;lt;/ref&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>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Android_restrict_app_sideloading&amp;diff=54749</id>
		<title>Google Android restrict app sideloading</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Android_restrict_app_sideloading&amp;diff=54749"/>
		<updated>2026-05-25T12:46:18Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OngoingEvent}}&lt;br /&gt;
{{IncidentCargo&lt;br /&gt;
|Company=Google&lt;br /&gt;
|StartDate=2025-08-25&lt;br /&gt;
|EndDate=&lt;br /&gt;
|Status=Active&lt;br /&gt;
|ProductLine=Android&lt;br /&gt;
|Product=&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Type=Privacy, Third-party&lt;br /&gt;
|Description=Google is planning to block Android app installation from sources not vetted by Google in 2026.&lt;br /&gt;
}}&lt;br /&gt;
On 25 August 2025, &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; announced that starting in 2026, the company will block the installation of Android apps from outside the Play Store unless the [[Android Developer Verification|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/20260222032808/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=22 Feb 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/20260222040007/https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |archive-date=22 Feb 2026}}&amp;lt;/ref&amp;gt; This marks a significant change to Android&#039;s long-standing support for sideloading apps and has sparked debate among developers, consumers, and digital rights advocates.&amp;lt;ref name=&amp;quot;:2&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;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
The open-source Android operating system has historically allowed [[sideloading]], the installation of apps from outside the Google Play Store. Users would need to enable &amp;quot;unknown sources&amp;quot; in their device settings to make this possible. This level of openness distinguished Android OS from Apple&#039;s restrictive iOS that does not allow sideloading. Alternative android app stores, such as F-Droid, Amazon&#039;s Appstore, and web downloads from sites like APKMirror, thrived under this model.&amp;lt;ref&amp;gt;{{Cite web |last=Thomas |first=Dallas |date=14 Sep 2024 |title=The Wild West days of sideloading on Android are officially over in this week&#039;s news |url=https://www.androidpolice.com/weekly-android-news-roundup-september-14-2024/ |url-status=live |access-date=25 Aug 2025 |website=Android Police |archive-url=http://web.archive.org/web/20251212191111/https://www.androidpolice.com/weekly-android-news-roundup-september-14-2024/ |archive-date=12 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Over time, Google introduced restrictions to the open-source operating system citing security concerns. In 2023, Google began requiring Play Store developers to verify their identities in order to reduce &amp;quot;impersonation and malware.&amp;quot;&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; Android versions 13 and 15 further limited what sideloaded apps could do, blocking access to sensitive permissions for apps not installed through Google&#039;s channels.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |last=Rahman |first=Mishaal |date=25 Aug 2025 |title=Google wants to make sideloading Android apps safer by verifying developers&#039; identities |url=https://www.androidauthority.com/android-developer-verification-requirements-3590911/ |url-status=live |access-date=26 Aug 2025 |website=Android Authority |archive-url=http://web.archive.org/web/20260219183753/https://www.androidauthority.com/android-developer-verification-requirements-3590911/ |archive-date=19 Feb 2026}}&amp;lt;/ref&amp;gt; These steps appear to have laid the groundwork for Google&#039;s new, broader enforcement.&lt;br /&gt;
&lt;br /&gt;
==Timeline==&lt;br /&gt;
On 25 August 2025, Google announced that &#039;&#039;&#039;apps can only be installed on certified Android devices if their developers have verified their personal identity with Google&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; Developers must register through a new Android Developer Console, pay a one-time $25 fee (except for hobbyists or students, who will have a separate free path), and provide identifying details such as legal name, address, and government-issued ID.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; Apps must also be registered with their signing keys to prove ownership.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The rollout will proceed in stages:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;October 2025:&#039;&#039;&#039; Early access program for select developers.&lt;br /&gt;
*&#039;&#039;&#039;March 2026:&#039;&#039;&#039; Verification opens for all developers worldwide.&lt;br /&gt;
*&#039;&#039;&#039;September 2026:&#039;&#039;&#039; Enforcement begins in Brazil, Indonesia, Singapore, and Thailand.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;2027:&#039;&#039;&#039; Targeted global rollout, eventually covering nearly all certified Android devices.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The new system applies to certified Android devices which are phones and tablets that ship with [[Google Mobile Services]] (e.g., Pixel, Samsung, Xiaomi). Devices running uncertified AOSP builds or custom ROMs (e.g., GrapheneOS, LineageOS) are not subject to this restriction.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; However, uncertified devices often face their own sideloading and app compatibility issues, due to SafetyNet/Play Integrity checks.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Google&#039;s response==&lt;br /&gt;
Google framed this new policy as a necessary security measure to reduce malware, fraud, and impersonation. The company stated that malware is &amp;quot;50× more common outside the Play Store&amp;quot; and that anonymity allows bad actors to evade accountability.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; Suzanne Frey, VP of Product for Android, likened the change to an ID check at the airport: verifying who the developer is without inspecting app content.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google emphasized that it will not review or police apps distributed outside the Play Store for content, only verify developer identities.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; Google&#039;s move gained support from some industry and institutions, including the Developers Alliance, Brazil&#039;s banking federation FEBRABAN, and Indonesia&#039;s Ministry of Communication and Informatics, all of which praised the move as protecting users from fraud.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As backlash mounted, Google took steps to clarify the changes. In late September 2025, an Android Developers Blog Q&amp;amp;A by Android security director Matthew Forsythe reiterated that sideloading is &amp;quot;fundamental to Android&amp;quot; and &amp;quot;absolutely not&amp;quot; going away, stressing the policy&#039;s focus on verifying developer identities rather than limiting user choice.&amp;lt;ref name=&amp;quot;:7&amp;quot;&amp;gt;{{Cite web |date=2025-09-30 |title=Let&#039;s talk security: Answering your top questions about Android developer verification |url=https://android-developers.googleblog.com/2025/09/lets-talk-security-answering-your-top.html |url-status=live |access-date=2025-10-27 |website=Android Developers Blog |archive-url=http://web.archive.org/web/20260119211533/https://android-developers.googleblog.com/2025/09/lets-talk-security-answering-your-top.html |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt; Google assured developers that common workflows remain unaffected; for example, installing test apps via &#039;&#039;&#039;[[wikipedia:Android_Debug_Bridge|ADB]]&#039;&#039;&#039; will not require verification.&amp;lt;ref name=&amp;quot;:7&amp;quot; /&amp;gt; The company also introduced a free &amp;quot;&#039;&#039;&#039;limited distribution&#039;&#039;&#039;&amp;quot; developer account as well as a new Android Developer Console for students, teachers, and hobbyists, allowing them to publish apps without paying a fee or providing government ID.&amp;lt;ref name=&amp;quot;:7&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:8&amp;quot;&amp;gt;{{Cite web |last=Rahman |first=Mishaal |date=2025-10-02 |title=We finally know how Android&#039;s new app verification rules will actually work |url=https://www.androidauthority.com/how-android-app-verification-works-3603559/ |url-status=live |access-date=2025-10-28 |website=Android Authority |archive-url=http://web.archive.org/web/20251228133458/https://www.androidauthority.com/how-android-app-verification-works-3603559/ |archive-date=28 Dec 2025}}&amp;lt;/ref&amp;gt; However, these accounts come with significant app distribution restrictions, namely a strict cap on the number of devices that can install their apps. To enforce this restriction, any user of a hobbyist app must retrieve a unique device identifier, and the developer must whitelist that device in the Android Developer Console before the app can be installed.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; This two-way device registration limits &amp;quot;free tier&amp;quot; apps to a small, known group of people, whereas anyone aiming to reach a broad audience will need to upgrade to a fully verified paid account.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google also detailed how the verification enforcement will work. A new system service called the &#039;&#039;&#039;Android Developer Verifier&#039;&#039;&#039; will check each app at installation to confirm its package name and signing certificate are registered with Google.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; Common apps from verified developers can be installed offline thanks to a cached on-device list, but an active internet connection will be required to verify less common apps that aren&#039;t in the cache.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; To accommodate third-party app stores, Google is developing a &amp;quot;&#039;&#039;&#039;pre-auth token&#039;&#039;&#039;&amp;quot;, a cryptographically signed blob that an alternative app store can pass to the system to pre-verify apps without repeated network calls.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; Enforcement of these rules will debut in &#039;&#039;&#039;Android 16 QPR2&#039;&#039;&#039; (the second quarterly update of Android 16, expected in late 2026), and Google will also update Play Protect on older Android versions to implement similar checks via Google Play Services.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; Notably, Google is carving out exceptions for enterprise scenarios: apps deployed through enterprise mobile management on managed work devices will install without developer verification (the assumption being that an organization&#039;s IT admin is taking responsibility for those apps&#039; safety).&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; However, truly offline use cases may prove tricky. Google has noted that entities with devices kept entirely off the internet will need to &amp;quot;determine for themselves&amp;quot; how to handle verification requests (i.e. such devices must periodically connect online to update the trusted app list).&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer response==&lt;br /&gt;
The announcement sparked backlash in online communities. On [[Reddit]], users accused Google of gradually eroding Android&#039;s openness.&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.reddit.com/r/Android/comments/1n0f5zt/google_will_block_sideloading_of_unverified/ |access-date=26 Aug 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250826174618/https://old.reddit.com/r/Android/comments/1n0f5zt/google_will_block_sideloading_of_unverified/ |archive-date=26 Aug 2025}}&amp;lt;/ref&amp;gt; Many argued that Android is becoming indistinguishable from iOS, with some stating that they may switch to operating systems from Apple or Linux since Android&#039;s openness was its key advantage.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Schenck |first=Stephen |date=27 Aug 2025 |title=With developer verification, I&#039;m struggling to think of Android as a proper smartphone platform |url=https://www.androidauthority.com/android-developer-registration-3591988/ |url-status=live |archive-url=https://web.archive.org/web/20250828113543/https://www.androidauthority.com/android-developer-registration-3591988/ |archive-date=28 Aug 2025 |access-date=28 Aug 2025 |website=Android Authority}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Independent developers raised concerns that hobby projects or sensitive apps (e.g., protest tools, ad-blockers) would be stifled since not all creators are willing to (or can safely) submit government IDs to Google.&amp;lt;ref&amp;gt;{{Cite web |date=25 Aug 2025 |title=Google will allow only apps from verified developers to be installed on Android |url=https://news.ycombinator.com/item?id=45017028 |url-status=live |access-date=26 Aug 2025 |website=Hacker News |archive-url=http://web.archive.org/web/20251219175237/https://news.ycombinator.com/item?id=45017028 |archive-date=19 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite web |date=26 Aug 2025 |title=Google wants to verify all app developers&#039; identities |url=https://discuss.grapheneos.org/d/25235-google-wants-to-verify-all-app-developers-identities |url-status=live |access-date=26 Aug 2025 |website=GrapheneOS Discussion Forum |archive-url=http://web.archive.org/web/20251219144142/https://discuss.grapheneos.org/d/25235-google-wants-to-verify-all-app-developers-identities |archive-date=19 Dec 2025}}&amp;lt;/ref&amp;gt; Open-source communities, including [[GrapheneOS]] developers, argued this would discourage FOSS development and give Google exclusive control over Android&#039;s ecosystem.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Sarang |first= |date=2025-08-26 |title=Finally Over: Google Blocks Sideloading of Android Apps |url=https://www.androidsage.com/2025/08/26/google-blocks-sideloading-of-android-apps/ |url-status=live |archive-url=https://web.archive.org/web/20250827201805/https://www.androidsage.com/2025/08/26/google-blocks-sideloading-of-android-apps/ |archive-date=2025-08-27 |access-date=2025-08-27 |website=Android Sage}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Conversely, some security experts and industry groups welcomed the move, calling it a reasonable compromise that still allows third-party distribution while deterring anonymous malware authors.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; Critics countered that determined attackers could still exploit stolen IDs, and that this introduces a &amp;quot;choke point,&amp;quot; giving Google leverage over all app installs.&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Regulators had not formally responded within the first 24 hours, but commentators noted that the change resembles Apple&#039;s Developer ID system on macOS and that it may be Google&#039;s way of tightening control while remaining compliant with the EU&#039;s {{Wplink|Digital Markets Act}}.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By late September 2025, open-source app developers escalated their opposition. The volunteer-run F-Droid app repository warned that Google&#039;s plan, if implemented, &amp;quot;will end the F-Droid project and other free/open-source app distribution sources as we know them today.&amp;quot;&amp;lt;ref name=&amp;quot;:9&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=2025-09-29 |title=Google&#039;s dev registration plan &#039;will end the F-Droid project&#039; |url=https://www.theregister.com/2025/09/29/googles_dev_registration_plan_will/ |access-date=2025-10-28 |website=The Register |archive-url=http://web.archive.org/web/20260119211449/https://www.theregister.com/2025/09/29/googles_dev_registration_plan_will/ |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt; F-Droid cannot comply with a centralized registration regime; its team builds apps from source code and signs them with its own cryptographic keys so it cannot simply have each apps&#039; original author register and hand over a signing identity without fundamentally changing F-Droid&#039;s model.&amp;lt;ref name=&amp;quot;:10&amp;quot;&amp;gt;{{Cite web |last=Prud&#039;hommeaux |first=Marc |date=2025-09-29 |title=F-Droid and Google&#039;s Developer Registration Decree |url=https://f-droid.org/2025/09/29/google-developer-registration-decree.html |url-status=live |access-date=2025-10-27 |website=F-Droid |archive-url=http://web.archive.org/web/20260119212107/https://f-droid.org/2025/09/29/google-developer-registration-decree.html |archive-date=19 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google offered a limited concession for situations where the same app exists in multiple stores: in rare cases, it will allow duplicate package names if one version has a significantly smaller user base (meaning the developer of the less-installed version might be asked to change their app&#039;s identifier).&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; In practice this would do little to help F-Droid. Many apps on F-Droid share a package name with a more popular Google Play version, so Google&#039;s policy would effectively treat the Play developer as the rightful owner and force the F-Droid variant to disappear or rebrand, an outcome that violates F-Droid&#039;s core philosophy.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The F-Droid team argued that Google is using security as a pretext to consolidate power over software distribution, especially since even the Play Store has repeatedly hosted malware despite all its checks.&amp;lt;ref name=&amp;quot;:9&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:10&amp;quot; /&amp;gt; In an official statement, F-Droid appealed to regulators and competition authorities around the world, citing the EU&#039;s Digital Markets Act, to scrutinize Google&#039;s proposal and protect the ability of alternative app stores and open-source developers to operate freely.&amp;lt;ref name=&amp;quot;:10&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Privacy and free-speech advocates also raised concerns. Requiring every app developer to verify their real-world identity would eliminate anonymity for creators of apps used in sensitive contexts, for example by political dissidents or whistleblowers.&amp;lt;ref&amp;gt;{{Cite web |last=Holwerda |first=Thom |date=2025-10-02 |title=Google details Android developer certification requirement, and it&#039;s as bad as we feared |url=https://www.osnews.com/story/143467/google-details-android-developer-certification-requirement-and-its-as-bad-as-we-feared/ |url-status=live |archive-url=https://web.archive.org/web/20251009112107/https://www.osnews.com/story/143467/google-details-android-developer-certification-requirement-and-its-as-bad-as-we-feared/ |archive-date=2025-10-09 |access-date=2025-10-29 |website=osnews}}&amp;lt;/ref&amp;gt; Google acknowledged that legitimate reasons for developer anonymity exist and stated it won&#039;t publicly disclose developer information, but the company did not promise to withhold that information from governments should they seek it.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt; Google&#039;s stance is that the status quo (allowing anonymous app distribution) poses risks it can no longer accept.&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some former Android team members have also lamented the platform&#039;s direction. Jean-Baptiste Quéru, a founding Android engineer who led the Android Open Source Project, remarked that when he worked on Android, goals included keeping the app ecosystem &amp;quot;as open as the web&amp;quot; and letting users run their own builds, but &amp;quot;12 years later, this seems to have all died&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |last=Holwerda |first=Thom |date=2025-09-29 |title=Google&#039;s Android developer registration requirement will kill F-Droid |url=https://www.osnews.com/story/143450/googles-android-developer-registration-requirement-will-kill-f-droid/ |url-status=live |archive-url=https://web.archive.org/web/20251009111928/https://www.osnews.com/story/143450/googles-android-developer-registration-requirement-will-kill-f-droid/ |archive-date=2025-10-09 |access-date=2025-10-29 |website=osnews}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A website titled https://keepandroidopen.org/ was created to push back against Google&#039;s decision. It was endorsed by F-Droid in a blog post as a way for users to take action. &lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Android]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google&amp;diff=54748</id>
		<title>Google</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google&amp;diff=54748"/>
		<updated>2026-05-25T12:45:56Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&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;
===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, 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 |url=https://source.android.com/docs/core/storage/traditional |title=Traditional storage  &amp;amp;#x7c;  Android Open Source Project }}&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 }}&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 |url=https://techzle.com/remember-android-13-clears-clipboard-1-hour-after-copying |title=Remember: Android 13 clears clipboard 1 hour after copying}}&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;
In 2025, Google announced their [[Android Developer Verification]] program, which if executed will make it impossible to run apps by developers not personally identified and approved by Google.&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;https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ ([http://web.archive.org/web/20210505101632/https://old.reddit.com/r/degoogle/comments/n5card/mike_rose_no_more_robots_publisher_locked_out_of/ Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ ([http://web.archive.org/web/20210805030048/https://old.reddit.com/r/degoogle/comments/oy8qb8/fyi_google_can_lock_you_out_of_your_account_for/ Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ ([http://web.archive.org/web/20230720181226/https://old.reddit.com/r/degoogle/comments/154yht0/dae_noticed_that_google_had_taken_security/ Archived])&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 July 2023 |title=Anonymous puts Taiwan flag, national anthem on 2 UN websites {{!}} Taiwan News {{!}} 2023-07-18 09:56:00 |url=https://www.taiwannews.com.tw/en/news/4946597 |access-date=21 December 2023 |website=Taiwan News}} ([http://web.archive.org/web/20231014070719/https://www.taiwannews.com.tw/en/news/4946597 Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |date=18 October 2023 |title=&#039;Anonymous&#039; hacks Chinese government site to protest Israel–Hamas war {{!}} Taiwan News {{!}} 2023-10-18 19:03:00 |url=https://www.taiwannews.com.tw/en/news/5022840 |access-date=21 December 2023 |website=Taiwan News}} ([http://web.archive.org/web/20240221120716/https://www.taiwannews.com.tw/en/news/5022840 Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |date=8 December 2023 |title=Anonymous posts Taiwan flag on UN site {{!}} Taiwan News {{!}} 2023-12-08 17:26:00 |url=https://www.taiwannews.com.tw/en/news/5055454 |access-date=21 December 2023 |website=Taiwan News}} ([http://web.archive.org/web/20240228035811/https://www.taiwannews.com.tw/en/news/5055454 Archived])&amp;lt;/ref&amp;gt;&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 authorised 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;[https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned DANGER!!!: Chargeback = ACCOUNT PERMANENTLY BANNED. - Virtual curiosities] ([http://web.archive.org/web/20260205120523/https://www.virtualcuriosities.com/articles/3393/danger-chargeback-equals-account-permanently-banned Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ TIFU by accidentally buying two Google Pixels and ended up getting my 15 year old Google Account permanently banned. - Reddit] ([http://web.archive.org/web/20260113140546/https://old.reddit.com/r/tifu/comments/zndbku/tifu_by_accidentally_buying_two_google_pixels_and/ Archived])&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;
&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 |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 |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 |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 3rd 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 3rd party services such as AnyList or Todoist to be managed via Google Assistant. The only list provider available through Google Assistant after this change was 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;https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/&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;https://adguard.com/en/blog/adguard-google-play-removal.html&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L6&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L106&amp;lt;/ref&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;https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/&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 |first=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 |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}&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;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Google| ]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Discord&amp;diff=54710</id>
		<title>Discord</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Discord&amp;diff=54710"/>
		<updated>2026-05-24T22:20:44Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup|reason=References need to be properly formatted. See [[Template:Cite web]].}}&lt;br /&gt;
{{CompanyCargo&lt;br /&gt;
|Founded=2015&lt;br /&gt;
|Industry=VoIP communications, instant messaging, videoconferences, content delivery, and social media&lt;br /&gt;
|Logo=Discord.svg&lt;br /&gt;
|ParentCompany=Discord Inc.&lt;br /&gt;
|Type=Private&lt;br /&gt;
|Website=https://discord.com&lt;br /&gt;
|CompanyAlias=Discord Inc.&lt;br /&gt;
|Description=American technology company that runs a platform for messaging and calling targeted towards gamers.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Discord&#039;&#039;&#039; is a proprietary VoIP and instant-messaging platform developed by Discord Inc. (formerly Hammer &amp;amp; Chisel, Inc.), co-founded by Jason Citron and Stanislav Vishnevskiy.&amp;lt;ref&amp;gt;{{Cite web |last=Gonzalez |first=Guadalupe |date=3 May 2018 |title=There Are 2.6 Billion Online Gamers in the World. This Startup Just May Connect Them All |url=https://www.inc.com/guadalupe-gonzalez/30-under-30-2018-discord.html |url-status=live |archive-url=https://web.archive.org/web/20180503131556/https://www.inc.com/guadalupe-gonzalez/30-under-30-2018-discord.html |archive-date=3 May 2018 |access-date=13 Jul 2025 |website=Inc.}}&amp;lt;/ref&amp;gt; Launched in 2015, the service has grown to over 150 million monthly active users as of 2025. While initially marketed towards PC gamers, Discord has expanded to multiple platforms, serving various communities and use cases, including education.&amp;lt;ref name=&amp;quot;about-company&amp;quot;&amp;gt;{{Cite web |date=15 Apr 2024 |title=About Discord &amp;lt;nowiki&amp;gt;|&amp;lt;/nowiki&amp;gt; Our Mission and Values |url=https://discord.com/company/ |url-status=live |archive-url=https://web.archive.org/web/20250608013037/https://discord.com/company |archive-date=8 Jun 2025 |access-date=13 Jul 2025 |website=Discord}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In April 2025, Humam Sakhnini (formerly King, Activision Blizzard) replaced Jason Citron as CEO.&amp;lt;ref&amp;gt;{{Cite web |title=Discord Appoints Humam Sakhnini as Chief Executive Officer |url=https://discord.com/press-releases/discord-appoints-new-ceo-humam-sakhnini |url-status=live |archive-url=http://web.archive.org/web/20260124072250/https://discord.com/press-releases/discord-appoints-new-ceo-humam-sakhnini |archive-date=24 Jan 2026}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
===Privacy===&lt;br /&gt;
Mentioned within the &#039;&#039;&#039;Discord ToS&#039;&#039;&#039;&amp;lt;ref name=&amp;quot;terms-of-service3&amp;quot;&amp;gt;[https://discord.com/terms/ &amp;quot;Discord&#039;s Terms of Service&amp;quot;]. April 15, 2024. &#039;&#039;Discord&#039;&#039;. Retrieved January 16, 2025. ([https://web.archive.org/web/20260216033955/https://discord.com/terms/ Archived])&amp;lt;/ref&amp;gt; and &#039;&#039;&#039;Privacy Policy&#039;&#039;&#039;:&amp;lt;ref name=&amp;quot;privacy-policy3&amp;quot;&amp;gt;[https://discord.com/privacy/ &amp;quot;Discord Privacy Policy&amp;quot;]. April 15, 2024. ([https://web.archive.org/web/20260216034021/https://discord.com/privacy/ Archived]) &#039;&#039;Discord&#039;&#039;. Retrieved January 16, 2025.&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;community-guidelines2&amp;quot;&amp;gt;[https://discord.com/guidelines/ &amp;quot;Discord Community Guidelines&amp;quot;]. April 15, 2024. &#039;&#039;Discord&#039;&#039;. Retrieved January 16, 2025. ([http://web.archive.org/web/20260216015550/https://discord.com/guidelines Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Collects a variety of user data, such as contact details; user generated messages and posts, including drafts; voice messages; payment information; server participation; device information, such as games being playing; log and event information related to use of Discord services as well as information from [[Web cookie|cookies]] and third party sources&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-29 |title=Privacy Policy: The information we collect |url=https://discord.com/privacy#3 |url-status=live |access-date=2026-02-20 |website=Discord |archive-url=http://web.archive.org/web/20260128220720/https://discord.com/privacy |archive-date=28 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Claims broad rights to user-generated content&lt;br /&gt;
*Stores deleted messages for undefined periods&lt;br /&gt;
*Deleting your account does not delete your messages, must delete messages before account deletion&lt;br /&gt;
*Retains personal information until deemed &amp;quot;no longer needed&amp;quot;&lt;br /&gt;
*Processes user content for &amp;quot;safety features and platform improvement&amp;quot;&lt;br /&gt;
*Shares data with related companies, vendors, and third-party service providers&lt;br /&gt;
*Opt-out behavioral tracking across platform features for personalization&lt;br /&gt;
*Maintains logs of IP addresses and device information for an undetermined amount of time, flags any user who has ever signed in with an EU IP address for inclusion within DSA transparency reports&lt;br /&gt;
*Sends a web request when any UI element is clicked and when typing&lt;br /&gt;
In 2019, Discord started requiring phone verification. The account will be locked until a phone number is added, regardless of account age or recent activity. The account will be automatically locked if the phone number is removed.&amp;lt;ref&amp;gt;{{Cite web |last=opal |date=2019-04-15 |title=guess I&#039;m done with Discord |url=https://wowana.me/blog/guess-im-done-with-discord.xht |url-status=live |archive-url=https://web.archive.org/web/20240331090127/https://wowana.me/blog/guess-im-done-with-discord.xht |archive-date=2024-03-31 |website=wowana.me}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Cadence |date=2020-06-06 |title=Why you shouldn&#039;t trust Discord |url=https://cadence.moe/blog/2020-06-06-why-you-shouldnt-trust-discord |url-status=live |archive-url=https://web.archive.org/web/20260215170749/https://cadence.moe/blog/2020-06-06-why-you-shouldnt-trust-discord |archive-date=2026-02-15 |website=cadence.moe}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Freedom===&lt;br /&gt;
In order to use Discord, users must agree to the &#039;&#039;&#039;Discord ToS&amp;lt;ref name=&amp;quot;terms-of-service3&amp;quot; /&amp;gt;&#039;&#039;&#039; and &#039;&#039;&#039;Privacy Policy&#039;&#039;&#039;, which includes agreeing to:&amp;lt;ref name=&amp;quot;privacy-policy3&amp;quot; /&amp;gt;&lt;br /&gt;
*Granting a perpetual, transferable license to user content&lt;br /&gt;
*Broad terms of service, which allow for unilateral changes&lt;br /&gt;
*Termination of user accounts without prior notice at Discord&#039;s discretion&lt;br /&gt;
*No option to opt out of core data collection while using the service&lt;br /&gt;
*Discord possibly retaining content even after deletion by the user&lt;br /&gt;
Additionally, server owners have limited recourse if their servers are banned, and users are required to use Discord&#039;s payment processing for all monetary transactions.&amp;lt;!-- &amp;quot;Limited recourse&amp;quot; is quite vague. It would be helpful to outline what recourse is possible and why this is insufficient.  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Forced arbitration ===&lt;br /&gt;
Since release&amp;lt;ref&amp;gt;{{Cite web |date=12 Sep 2015 |title=Discord - Terms of Service |url=https://discordapp.com |url-status=unfit |archive-url=https://web.archive.org/web/20170521173532/https://discordapp.com/terms#:~:text=ARBITRATION |archive-date=21 May 2017 |access-date= |website=Discord}}&amp;lt;/ref&amp;gt;, Discord&#039;s [[Terms of Service|terms of service]] have mandated [[Forced arbitration|binding arbitration]] with {{Wplink|class action}} waiver for U.S. users. Users can opt out by sending an &#039;opt-out notice&#039; to arbitration-opt-out@discord.com within 90 days of registering their first account.&#039;&#039;&#039;&amp;lt;ref name=&amp;quot;terms-of-service3&amp;quot; /&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Transparency ===&lt;br /&gt;
Discord&#039;s terms of service are lengthy and complex. In October 2025, the base terms are 29 pages long, with a reading level of 14th grade (equivalent to two years of tertiary education) and an estimated reading time of 42 minutes.&amp;lt;ref&amp;gt;{{Cite web |title=Calculated using readabilitychecker.com based on current discord TOS. discord.com/terms |url=https://readabilitychecker.com/url |access-date=9 Oct 2025 |url-status=live |archive-url=http://web.archive.org/web/20260210185029/https://readabilitychecker.com/url |archive-date=10 Feb 2026}}&amp;lt;/ref&amp;gt;  The 2021 version of Discord&#039;s ToS would take an estimated 275+ hours to read.&amp;lt;ref&amp;gt;{{Cite web |title=EULA of despair |url=https://www.pilotlab.org/eulas-of-despair |access-date=9 Oct 2025 |website=Penn State University Pilot Lab |url-status=live |archive-url=https://web.archive.org/web/20260216034102/https://www.pilotlab.org/eulas-of-despair |archive-date=16 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mentioned within the &#039;&#039;&#039;Discord Privacy Policy&#039;&#039;&#039;&amp;lt;ref name=&amp;quot;privacy-policy3&amp;quot; /&amp;gt; and &#039;&#039;&#039;Community Guidelines&#039;&#039;&#039;:&amp;lt;ref name=&amp;quot;community-guidelines2&amp;quot; /&amp;gt;&lt;br /&gt;
*Unclear processes for handling law enforcement requests&lt;br /&gt;
*Vague about data retention time frames&lt;br /&gt;
*Limited transparency regarding content moderation decisions&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |title=BBB - Discord, Inc. |url=https://www.bbb.org/us/ca/san-francisco/profile/computer-software/discord-inc-1116-918699 |access-date=Aug 2, 2025 |website=Better Business Bureau |url-status=live |archive-url=http://web.archive.org/web/20260210184246/https://www.bbb.org/us/ca/san-francisco/profile/computer-software/discord-inc-1116-918699 |archive-date=10 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |title=Trustpilot - Discord |url=https://www.trustpilot.com/review/discord.com |access-date=Aug 2, 2025 |website=Trustpilot |url-status=live |archive-url=http://web.archive.org/web/20251112025215/https://www.trustpilot.com/review/discord.com |archive-date=12 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
**Offending content not always displayed to the user, including metadata, filenames, timestamps, or the channel where it was posted&lt;br /&gt;
**No limits or restrictions on the age of content (e.g., users can be suspended due to something sent 1500 days ago)&lt;br /&gt;
*Lack of transparency in the server ban appeals process&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
*Limited disclosure of recommendation algorithm factors&lt;br /&gt;
*No clear disclosure of how the content is used for platform improvement&lt;br /&gt;
&lt;br /&gt;
===Bulk message deletion===&lt;br /&gt;
Discord provides no in-app bulk message deletion; instead, you must [https://support.discord.com/hc/en-us/articles/360004027692-Requesting-a-Copy-of-your-Data request your data], then send Discord support a data deletion request via their [https://support.discord.com/hc/en-us/requests/new?ticket_form_id=4750383925911 privacy form]. You must provide the desired message id’s and the channel id’s they were sent in, which makes this process difficult. You will receive your data to the email tied to the account. If you change the email before receiving the data, your data will not be redirected to the new email. Your request will also be canceled if you disable or delete your account before receiving the data.  &lt;br /&gt;
&lt;br /&gt;
Once discord begins message deletion it can take up to 24 hours for all requested messages to be deleted. After 24 hours have passed, you&#039;ll need to request your data package again to confirm all requested messages have been deleted. You can only request your data again 30 days after you previously requested data.  &lt;br /&gt;
&lt;br /&gt;
A third-party website, [https://discorch.org/ Discorch], makes this process significantly easier. Discorch contains more information relevant to this topic, and detailed instructions that should be followed exactly. Discord will likely reply with &amp;quot;This channel is reserved for individuals...&amp;quot;, rejecting your data deletion request. Due to this, Discorch provides a response for you to send back to Discord. Discord will also refuse to delete messages you have access to, so you must leave relevant servers and group DMs before sending a data deletion request, and can only rejoin after the messages have been deleted. If you have deleted your account, you cannot delete your messages.&lt;br /&gt;
&lt;br /&gt;
When requesting your data, you only need your message data. It can take up to 30 days to receive your data, once you have it you can use Discorch. According to Discorch:&amp;lt;blockquote&amp;gt; &#039;&#039;&amp;quot;Discord acts in malicious compliance with the GDPR. You are not allowed to delete your DMs through their support flow, since you can always regain access to a DM, technically speaking, since you are always a member of the DM channel on their backend.&amp;quot;&#039;&#039;&amp;lt;/blockquote&amp;gt;In order to delete DMs in bulk you must use [https://github.com/Darker-Ink/DiscorchDeleter DiscorchDeleter],  which is against Discord&#039;s ToS (as it&#039;s considered self-botting), it&#039;ll automatically delete messages for you. By default the deletion interval tries to comply with Discord&#039;s ratelimits, so an account termination is unlikely, though use at your own risk. You may get rate-limited, in which case you need to increase the deletion interval. DiscorchDeleter requires your data package and will also work outside of DMs if you&#039;d like to avoid discord support or remain in relevant servers and group DMs. &lt;br /&gt;
&lt;br /&gt;
DiscorchDeleter requires [https://chromewebstore.google.com/detail/violentmonkey/jinjaccalgkegednnccohejagnlnfdag ViolentMonkey] and [https://chromewebstore.google.com/detail/vencord-web/cbghhgpcnddeihccjmnadmkaejncjndb Vencord (browser version)]. Discorch provides downloads for all of these, including DiscorchDeleter. ViolentMonkey requires a browser that supports Manifest V2, so consider using [https://brave.com/ Brave] or [https://www.firefox.com/en-US/ Firefox].&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Child safety concerns (&#039;&#039;2023&#039;&#039;)===&lt;br /&gt;
An [[wikipedia:NBC News|NBC News]] investigation in June 2023 uncovered widespread child safety issues on Discord, revealing systemic problems with the platform&#039;s user protection measures.&lt;br /&gt;
&lt;br /&gt;
Investigators identified 35 separate cases where adults were criminally charged with &amp;quot;kidnapping, grooming, or sexual assault&amp;quot; involving contacts initiated through Discord. Additionally, 165 criminal prosecutions involving the sharing of child sexual exploitation material (CSAM) on the platform were documented.&amp;lt;ref&amp;gt;&amp;lt;templatestyles src=&amp;quot;Module:Citation/CS1/styles.css&amp;quot;&amp;gt;&amp;lt;/templatestyles&amp;gt;&amp;lt;cite id=&amp;quot;CITEREFGoggin2023&amp;quot; class=&amp;quot;citation web cs1&amp;quot;&amp;gt;Goggin, Ben (21 Jun 2023). [https://www.nbcnews.com/tech/social-media/discord-child-safety-social-platform-challenges-rcna89769 &amp;quot;Child predators are using Discord, a popular app among teens, for sextortion and abductions&amp;quot;]. &#039;&#039;NBC News&#039;&#039;. [https://web.archive.org/web/20230621152318/https://www.nbcnews.com/tech/social-media/discord-child-safety-social-platform-challenges-rcna89769 Archived] from the original on 21 Jun 2023&amp;lt;span class=&amp;quot;reference-accessdate&amp;quot;&amp;gt;. Retrieved &amp;lt;span class=&amp;quot;nowrap&amp;quot;&amp;gt;13 Jul&amp;lt;/span&amp;gt; 2025&amp;lt;/span&amp;gt;.&amp;lt;/cite&amp;gt;&amp;lt;span title=&amp;quot;ctx_ver=Z39.88-2004&amp;amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;amp;rft.genre=unknown&amp;amp;rft.jtitle=NBC+News&amp;amp;rft.atitle=Child+predators+are+using+Discord%2C+a+popular+app+among+teens%2C+for+sextortion+and+abductions&amp;amp;rft.date=2023-06-21&amp;amp;rft.aulast=Goggin&amp;amp;rft.aufirst=Ben&amp;amp;rft_id=https%3A%2F%2Fwww.nbcnews.com%2Ftech%2Fsocial-media%2Fdiscord-child-safety-social-platform-challenges-rcna89769&amp;amp;rfr_id=info%3Asid%2Fconsumerrights.wiki%3ADiscord&amp;quot; class=&amp;quot;Z3988&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===FTC data collection investigation (&#039;&#039;2024&#039;&#039;)===&lt;br /&gt;
In September 2024, the [[Federal Trade Commission]] (FTC) released a comprehensive report examining Discord&#039;s data collection practices as part of a broader investigation into the data collection practices of social media platforms.&amp;lt;ref&amp;gt;&amp;lt;templatestyles src=&amp;quot;Module:Citation/CS1/styles.css&amp;quot;&amp;gt;&amp;lt;/templatestyles&amp;gt;&amp;lt;cite class=&amp;quot;citation web cs1&amp;quot;&amp;gt;[https://www.ftc.gov/system/files/ftc_gov/pdf/Social-Media-6b-Report-9-11-2024.pdf &amp;quot;A Look Behind the Screens: Examining the Data Practices of Social Media and Video Streaming Services&amp;quot;] &amp;lt;span class=&amp;quot;cs1-format&amp;quot;&amp;gt;(PDF)&amp;lt;/span&amp;gt;. &#039;&#039;Federal Trade Commission&#039;&#039;. 11 Sep 2024. [https://web.archive.org/web/20240919133855/https://www.ftc.gov/system/files/ftc_gov/pdf/Social-Media-6b-Report-9-11-2024.pdf Archived] &amp;lt;span class=&amp;quot;cs1-format&amp;quot;&amp;gt;(PDF)&amp;lt;/span&amp;gt; from the original on 19 Sep 2024&amp;lt;span class=&amp;quot;reference-accessdate&amp;quot;&amp;gt;. Retrieved &amp;lt;span class=&amp;quot;nowrap&amp;quot;&amp;gt;13 Jul&amp;lt;/span&amp;gt; 2025&amp;lt;/span&amp;gt;.&amp;lt;/cite&amp;gt;&amp;lt;span title=&amp;quot;ctx_ver=Z39.88-2004&amp;amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;amp;rft.genre=unknown&amp;amp;rft.jtitle=Federal+Trade+Commission&amp;amp;rft.atitle=A+Look+Behind+the+Screens%3A+Examining+the+Data+Practices+of+Social+Media+and+Video+Streaming+Services&amp;amp;rft.date=2024-09-11&amp;amp;rft_id=https%3A%2F%2Fwww.ftc.gov%2Fsystem%2Ffiles%2Fftc_gov%2Fpdf%2FSocial-Media-6b-Report-9-11-2024.pdf&amp;amp;rfr_id=info%3Asid%2Fconsumerrights.wiki%3ADiscord&amp;quot; class=&amp;quot;Z3988&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The investigation revealed Discord collects extensive user data, including:&lt;br /&gt;
*Message content and metadata&lt;br /&gt;
*Voice-chat participation&lt;br /&gt;
*Server membership and activity&lt;br /&gt;
*Device and location information&lt;br /&gt;
Particular concern was raised about:&lt;br /&gt;
*[https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-312 Collection of data from users under 13]&lt;br /&gt;
*Handling of minors&#039; user information&lt;br /&gt;
*Inadequate age-verification systems&lt;br /&gt;
The FTC identified multiple areas where Discord&#039;s practices put users at risk:&lt;br /&gt;
*Identity theft exposure&lt;br /&gt;
*Potential stalking risks&lt;br /&gt;
*Discrimination concerns&lt;br /&gt;
*Mental health and emotional impact&lt;br /&gt;
&lt;br /&gt;
The FTC concluded that Discord&#039;s data practices posed unacceptable risks to users, particularly minors, and recommended significant reforms to the platform&#039;s privacy protection measures.&amp;lt;ref&amp;gt;&amp;lt;templatestyles src=&amp;quot;Module:Citation/CS1/styles.css&amp;quot;&amp;gt;&amp;lt;/templatestyles&amp;gt;&amp;lt;cite id=&amp;quot;CITEREFTolentino2024&amp;quot; class=&amp;quot;citation web cs1&amp;quot;&amp;gt;Tolentino, Daysia (19 Sep 2024). [https://www.nbcnews.com/tech/security/social-media-companies-engaged-vast-surveillance-ftc-finds-calling-sta-rcna171814 &amp;quot;Social media companies engaged in &#039;vast surveillance,&#039; FTC finds, calling status quo &#039;unacceptable&#039;&amp;lt;span class=&amp;quot;cs1-kern-right&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&amp;quot;]. &#039;&#039;NBC News&#039;&#039;. [https://web.archive.org/web/20240919171049/https://www.nbcnews.com/tech/security/social-media-companies-engaged-vast-surveillance-ftc-finds-calling-sta-rcna171814 Archived] from the original on 19 Sep 2024&amp;lt;span class=&amp;quot;reference-accessdate&amp;quot;&amp;gt;. Retrieved &amp;lt;span class=&amp;quot;nowrap&amp;quot;&amp;gt;13 Jul&amp;lt;/span&amp;gt; 2025&amp;lt;/span&amp;gt;.&amp;lt;/cite&amp;gt;&amp;lt;span title=&amp;quot;ctx_ver=Z39.88-2004&amp;amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;amp;rft.genre=unknown&amp;amp;rft.jtitle=NBC+News&amp;amp;rft.atitle=Social+media+companies+engaged+in+%27vast+surveillance%2C%27+FTC+finds%2C+calling+status+quo+%27unacceptable%27&amp;amp;rft.date=2024-09-19&amp;amp;rft.aulast=Tolentino&amp;amp;rft.aufirst=Daysia&amp;amp;rft_id=https%3A%2F%2Fwww.nbcnews.com%2Ftech%2Fsecurity%2Fsocial-media-companies-engaged-vast-surveillance-ftc-finds-calling-sta-rcna171814&amp;amp;rfr_id=info%3Asid%2Fconsumerrights.wiki%3ADiscord&amp;quot; class=&amp;quot;Z3988&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Reinforcement of forced arbitration (&#039;&#039;September 2025&#039;&#039;)===&lt;br /&gt;
Announced August 29th, 2025, and put into effect September 29th, 2025, Discord updated and re-iterated their [[forced arbitration]] clause but gave users another option to opt-out of forced arbitration until October 29th, 2025, for existing accounts, or 30 days after initial agreement for new accounts.&amp;lt;ref&amp;gt;{{Cite web |date=2025-09-29 |title=Discord&#039;s Terms of Service |url=https://discord.com/terms#16 |url-status=live |archive-url=https://web.archive.org/web/20251007023150/https://discord.com/terms#16 |archive-date=2025-10-07 |access-date=2025-10-07 |website=Discord.com}}&amp;lt;/ref&amp;gt; Users are automatically opted into the forced arbitration clause unless they take specific action to opt out of it within 30 days. Instead, if users chose to delete their accounts, the platform required them to accept the terms in order to access their account, from which they could then delete it, making acceptance of the new terms mandatory.&lt;br /&gt;
[[File:Discord ToS update 2025.png|thumb|200px|alt=An example of Discord forcing users to agree to arbitration if they want to continue using the application.|(2025-09-29) An example of Discord forcing users to agree to arbitration if they want to continue using the application.  The terms of service at the time of this screenshot includes forced arbitration and disallows users from filing a class-action lawsuit.&amp;lt;ref&amp;gt;{{Cite web |last=Discord |date=2025-09-29 |title=Terms of Service {{!}} Discord |url=https://discord.com/terms |url-status=live |access-date=2025-09-29 |website=Discord}} ([http://web.archive.org/web/20260222174800/https://discord.com/terms Archived])&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
===Third-party customer service data breach (&#039;&#039;October 2025&#039;&#039;)===&lt;br /&gt;
{{Main|Discord / 5CA Data Breach}}&lt;br /&gt;
&lt;br /&gt;
In October 2025, Discord issued a press release announcing a &amp;quot;Security Incident Involving Third-Party Customer Service [5CA]&amp;quot;, in which &amp;quot;the unauthorized party [...] gained access to a small number of government‑ID images (e.g., driver’s license, passport) from users who had appealed an age determination,&amp;quot; as well as other personal data provided to support.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |date=2025-10-03 |title=Update on a Security Incident Involving Third-Party Customer Service |url=https://discord.com/press-releases/update-on-security-incident-involving-third-party-customer-service |url-status=live |archive-url=https://web.archive.org/web/20251006163040/https://discord.com/press-releases/update-on-security-incident-involving-third-party-customer-service |archive-date=2025-10-06 |access-date=2025-10-07 |website=Discord}}&amp;lt;/ref&amp;gt; The number of ID images accessed was approximately 70,000, and the third-party in question was later named as 5CA.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; The hackers involved in the breach have revealed that the data was accessed via Zendesk.&amp;lt;ref&amp;gt;{{Cite web |last=Hunt |first=Troy |date=2025-10-04 |title=X |url=https://x.com/troyhunt/status/1974558088847102289}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Any better sources? The tweet referred to by this person is not archived. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Announcement of age verification coming in March (&#039;&#039;February 2026&#039;&#039;)===&lt;br /&gt;
&amp;lt;!-- Above under the incidents &amp;quot;Child safety concerns&amp;quot; (June 2023) and &amp;quot;FTC data collection investigation (Sept. 2024), there is implied criticism of Discord for failing to protect child safety and insufficient age verification. This age verification measure could then be seen as Discord trying to address these criticisms.   In order for this page have a coherent stance on companies responsibility regarding child safety and the use of age verification, it might be necessary to articulate (either here or linked to a separate page) why this widespread age verification is a violation of consumer privacy rights and its ineffectiveness at improving child safety. [A main article has been already created, added the link here]  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Main|Discord&#039;s Mandatory Age Verification}}&lt;br /&gt;
&lt;br /&gt;
In February 2026, Discord issued a press release announcing &amp;quot;enhanced teen safety features rolling out globally&amp;quot;, which begins with a &amp;quot;rollout to new and existing users in early March&amp;quot;, that may require users &amp;quot;to engage in an age-verification process to change certain settings or access sensitive content&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |date=2026-02-09 |title=Discord Launches Teen-by-Default Settings Globally |url=https://discord.com/press-releases/discord-launches-teen-by-default-settings-globally |url-status=live |archive-url=https://web.archive.org/web/20260209142047/https://discord.com/press-releases/discord-launches-teen-by-default-settings-globally |archive-date=2026-02-09 |access-date=2026-02-09 |website=Discord}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On February 9, 2026, a [https://www.change.org/p/prevent-discord-from-implementing-id-verification Change.org petition] was created to prevent Discord from implementing the age verification globally.&lt;br /&gt;
&lt;br /&gt;
===Discord&#039;s connections to Palantir===&lt;br /&gt;
Discord in the UK once utilized&amp;lt;ref&amp;gt;{{Cite web |last=Roth |first=Emma |date=2026-02-23 |title=Discord distances itself from Persona age verification after user backlash |url=https://www.theverge.com/tech/878369/discord-persona-age-verification |url-status=usurped |archive-url=https://web.archive.org/web/20260224163803/https://www.theverge.com/tech/878369/discord-persona-age-verification |archive-date=2026-02-24 |website=The Verge}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Giono |first=Catherina |date=2026-02-24 |title=Discord distances itself from Peter Thiel–backed verification software after its code was found on a Google Cloud endpoint |url=https://fortune.com/2026/02/24/discord-peter-thiel-backed-persona-identity-verification-breach/ |url-status=usurped |archive-url=https://web.archive.org/web/20260226164710/https://fortune.com/2026/02/24/discord-peter-thiel-backed-persona-identity-verification-breach/https://fortune.com/2026/02/24/discord-peter-thiel-backed-persona-identity-verification-breach/ |archive-date=2026-02-26 |website=Fortune}}&amp;lt;/ref&amp;gt; [[Persona]] as a third-party, specialized vendor for age verification, requiring UK-based users to submit facial scans or ID to access restricted content. A since redacted statement on the support.discord.com web-page under the &amp;quot;How to Complete Age Assurance on Discord&amp;quot; article stated&amp;lt;ref&amp;gt;{{Cite web |last=Bubbles |title=How to Complete Age Assurance on Discord |url=https://support.discord.com/hc/en-us/articles/30326565624343-How-to-Complete-Age-Assurance-on-Discord |url-status=usurped |archive-url=https://web.archive.org/web/20260212201755/https://support.discord.com/hc/en-us/articles/30326565624343-How-to-Complete-Age-Assurance-on-Discord |archive-date=2026-02-12 |website=Discord}}&amp;lt;/ref&amp;gt;:{{Quote|&amp;quot;Important: If you&#039;re located in the UK, you may be part of an experiment where your information will be processed by an age-assurance vendor, Persona. The Information you submit will be temporarily stored for up to 7 days, then deleted. For ID document verification, all details are blurred except your photo and date of birth, so only what&#039;s truly needed for age verification is used&amp;quot;.}}&lt;br /&gt;
[[File:Discord age assurance support article changes before &amp;amp; after.png|alt=Screenshots of changes made to the support article on Discord&#039;s support page|thumb|Comparison of changes made between 15 February 2026 to 19 February 2026.]]&lt;br /&gt;
After significant backlash from the online community, Discord has changed their statement under the article (as of February 19th, 2026)&amp;lt;ref&amp;gt;{{Cite web |last=Bubbles |title=How to Complete Age Assurance on Discord |url=https://support.discord.com/hc/en-us/articles/30326565624343-How-to-Complete-Age-Assurance-on-Discord |url-status=live |archive-url=https://web.archive.org/web/20260218072524/https://support.discord.com/hc/en-us/articles/30326565624343-How-to-Complete-Age-Assurance-on-Discord |archive-date=2026-02-18 |website=Discord}}&amp;lt;/ref&amp;gt;: {{Quote|&amp;quot;Note: Some users in regions outside the UK and Australia may see age-assurance prompts when accessing certain features or settings as part of ongoing experiments.&amp;quot;}}&lt;br /&gt;
&lt;br /&gt;
Discord does not further clarify what the &amp;quot;experiments&amp;quot; entail. Furthermore, the more detailed help-center article does not contain any mentions of the vendor Persona. &amp;lt;ref&amp;gt;{{Cite web |last=Bubbles |title=What’s Changing for UK Users Due to the UK Online Safety Act |url=https://support.discord.com/hc/en-us/articles/33362401287959-What-s-Changing-for-UK-Users-Due-to-the-UK-Online-Safety-Act |url-status=live |archive-url=https://web.archive.org/web/20260228040004/https://support.discord.com/hc/en-us/articles/33362401287959-What-s-Changing-for-UK-and-Australian-Users |archive-date=2026-02-28 |website=Discord}}&amp;lt;/ref&amp;gt; &amp;lt;!-- &amp;lt; This page has differences since when it was last archive in 2025. In case anyone&#039;s interested --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Persona is an identity verification tool producer, that has received $200 million dollars&amp;lt;ref&amp;gt;{{Cite web |last=Song |first=Rick |date=2026-01-21 |title=Announcing Persona’s $200M Series D |url=https://withpersona.com/blog/series-d |url-status=live |archive-url=https://web.archive.org/web/20260218172300/https://withpersona.com/blog/series-d |archive-date=2026-02-18 |website=*Persona}}&amp;lt;/ref&amp;gt; from the Founders Fund&amp;lt;ref&amp;gt;{{Cite web |title=Persona |url=https://foundersfund.com/company/persona/ |url-status=live |archive-url=https://web.archive.org/web/20260228040423/https://foundersfund.com/company/persona/ |archive-date=2026-02-28 |access-date=2026-02-28 |website=Founders Fund}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |title=Founders&#039; Fund - Portfolio |url=https://foundersfund.com/portfolio/ |url-status=live |archive-url=https://web.archive.org/web/20260228034728/https://foundersfund.com/portfolio/ |archive-date=2026-02-28 |website=Founders Fund}}&amp;lt;/ref&amp;gt;, a venture capital group headed by Peter Thiel&amp;lt;ref&amp;gt;{{Cite web |title=Peter Thiel |url=https://foundersfund.com/team/peter-thiel/ |url-status=usurped |archive-url=https://web.archive.org/web/20160528193728/http://foundersfund.com/team/peter-thiel/ |archive-date=2016-05-28 |access-date=2026-02-28 |website=Founders Fund}}&amp;lt;/ref&amp;gt;. Peter Thiel is also the co-founder of Palantir Technologies Inc, a global surveillance company.&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Inactive account deletions===&lt;br /&gt;
Discord has a [[Inactive account deletion|deletion policy on inactive accounts]], in which accounts that are not used for 2 years or more may be scheduled for deletion. Before the deletion of an inactive account, users may receive an email or text message warning that their account is scheduled for deletion. 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 that have prolonged internet shutdowns. &amp;lt;ref&amp;gt;{{Cite web |last=Librarian |date=2023-06-14 |title=Inactive Account Deletion |url=https://support.discord.com/hc/en-us/articles/5106714856215-Inactive-Account-Deletion |url-status=live |archive-url=http://web.archive.org/web/20260210025748/https://support.discord.com/hc/en-us/articles/5106714856215-Inactive-Account-Deletion |archive-date=2026-02-10 |website=Discord}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===SDK vulnerability with Arc Raiders integration (&#039;&#039;March 2026&#039;&#039;)===&lt;br /&gt;
In March 2026, Timothy Meadows, a computer engineer discovered a privacy and security vulnerability that involved Discord&#039;s [[wikipedia:Software_development_kit|software developer kit (SDK)]] and integrations with the [[wikipedia:Arc_Raiders|Arc Raiders]] game.&amp;lt;ref&amp;gt;{{Cite web |last=Meadows |first=Timothy |date=3 Mar 2026 |title=Arc Raiders - Discord SDK Data Exposure |url=https://timothymeadows.com/arc-raiders-discord-sdk-data-exposure/ |url-status=live |archive-url=https://archive.is/pktbu |archive-date=2026-03-06 |access-date=8 Mar 2026 |website=timothymeadows.com}}&amp;lt;/ref&amp;gt; This vulnerability affected the users with their Discord account linked with the game, allowing the software to log and store locally Discord private conversations, user credentials and other user information in an unencrypted log file. If the Arc Raiders game crashes, this file could be sent to the game developers. Embark Studios disabled the SDK integration after the incident was announced. &amp;lt;ref&amp;gt;{{Cite web |last=Klotz |first=Aaron |date=Mar 2026 |title=Arc Raiders was accidentally recording Discord conversations into an unencrypted local game file — vulnerability in SDK could log messages and credentials in plaintext |url=https://www.tomshardware.com/video-games/pc-gaming/arc-raiders-was-accidentally-recording-discord-conversations-into-an-unencrypted-local-game-file-vulnerability-in-sdk-could-log-messages-and-credentials-in-plaintext |url-status=live |archive-url=https://archive.is/kWBIf |archive-date=2026-03-07 |access-date=8 Mar 2026 |website=Tom&#039;s Hardware}}&amp;lt;/ref&amp;gt; &amp;lt;ref&amp;gt;{{Cite web |last=Marnell |first=Blair |date=6 Mar 2026 |title=Arc Raiders Was Recording Private Discord DMs |url=https://www.gamespot.com/articles/arc-raiders-was-recording-private-discord-dms/1100-6538629/|url-status=live |archive-url=https://archive.is/2ZQ1M |archive-date=2026-03-08 |access-date=8 Mar 2026 |website=Gamespot}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
Before the incident was known, when an user linked their Discord account, a pop-up claimed that Arc Raiders &amp;quot;cannot read users&#039; messages&amp;quot;. &amp;lt;ref&amp;gt;{{Cite web |last=Makar |first=Connor |date=2026-03-05 |title=Embark Studios rushes to fix Arc Raiders Discord integration bug as &amp;quot;serious privacy and security violations&amp;quot; may have exposed private Discord DMs, friends data, more |url=https://www.eurogamer.net/arc-raiders-discord-messages-security-problem-fix-incoming |url-status=live |website=Eurogamer}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Parker |first=Lewis |date=2026-03-05 |title=Arc Raiders Rushes Out Emergency Fix After Its Discord Accidentally Spied On Players |url=https://kotaku.com/arc-raiders-hotfix-discord-integration-2000676444 |url-status=live |website=Kotaku}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Lowry |first=Brendan |date=2026-03-05 |title=ARC Raiders recorded private Discord DM messages between players in &amp;quot;serious privacy and security violations&amp;quot; — Embark promises that your data is safe |url=https://www.windowscentral.com/gaming/arc-raiders-recorded-private-discord-messages-between-players-in-serious-privacy-and-security-violations |url-status=live |website=Windows Central}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Discord banning users taking action against child predators (&#039;&#039;April 2025—&#039;&#039;)===&lt;br /&gt;
[[File:Discord&#039;s protection of pedophiles.png|thumb|First offense is a 24-hour mute, with it as an active violation that stays on a user&#039;s profile for up to four years, when going after active child predators.]]&lt;br /&gt;
Since April 2025, users have been reported their accounts have been banned after taking action against child sexual predators instead of banning the predator themselves. When an account is banned for this, the reason given is [https://discord.com/safety/hateful-conduct-policy-explainer &amp;quot;hateful conduct policy&amp;quot;] The ban grants a 24-hour mute, making users unable to talk or interact with others. This account flag might stay up to four years.&amp;lt;ref&amp;gt;{{Cite news |last=Lim |first=Alex |date=24 Apr 2025 |title=Why Did Discord Make the Controversial Decision to Shut Down Ro-Cleaner? |url=https://pupuweb.com/why-did-discord-make-the-controversial-decision-to-shut-down-ro-cleaner/ |url-status=live |archive-url=https://web.archive.org/web/20250425034609if_/https://pupuweb.com/why-did-discord-make-the-controversial-decision-to-shut-down-ro-cleaner/ |archive-date=25 Apr 2025 |access-date=25 Apr 2025 |work=Pupuweb}}&amp;lt;/ref&amp;gt;  [https://www.youtube.com/watch?v=XJD9MQLaQ-g No Text To Speech&#039;s video] explains this incident with more details on YouTube.&lt;br /&gt;
&lt;br /&gt;
==Solution to delete an account without agreeing to the updated ToS==&lt;br /&gt;
&lt;br /&gt;
*Visit [https://support.discord.com/hc/en-us/articles/212500837-How-to-Delete-your-Discord-Account How to delete Discord account] and scroll to &amp;quot;Having Trouble Deleting Your Discord Account?&amp;quot; Find the link titled &amp;quot;Reach out to our support team&amp;quot;. Direct link subject to user instance - http://dis.gd/support&lt;br /&gt;
&lt;br /&gt;
*Fill out the &amp;quot;Submit a request&amp;quot; form. (A web search for &amp;quot;Submit a request Discord&amp;quot; may help users find the form. Be sure to answer the question &amp;quot;What can we help you with?&amp;quot; with &amp;quot;Help and Support&amp;quot; from the drop-down.) &#039;&#039;&#039;Please fill out the form using the same email address associated with your Discord account, as this process may need to be restarted if it is not.&#039;&#039;&#039; In the form, under &amp;quot;Type of question,&amp;quot; there is an option for &amp;quot;Account deletion request&amp;quot;. Proceed to fill out and submit the form with any other relevant information. An email will then be sent with further instructions, including how to proceed with account deletion, which involves responding to the email with &amp;quot;I confirm that I would like to delete the account associated with [user email].&amp;quot; &#039;&#039;&#039;The response must be received from the same email as the one associated with the Discord account.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Solution to disable forced updates on Linux==&lt;br /&gt;
If you&#039;re running a .deb installation of Discord, you can disable forced updates by adding &amp;quot;SKIP_HOST_UPDATE&amp;quot;: true to ~/.config/discord/settings.json.&amp;lt;ref&amp;gt;{{Cite web |last=Pardomuan |first=Patar Isac |date=2025-04-26 |title=How I Bypassed Discord’s Forced Update on Linux |url=https://medium.com/@patarisac/how-i-bypassed-discords-forced-update-on-linux-2bbc39b5949c |url-status=live |access-date=2026-02-20 |website=Medium |archive-url=http://web.archive.org/web/20251004041109/https://medium.com/@patarisac/how-i-bypassed-discords-forced-update-on-linux-2bbc39b5949c |archive-date=4 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer friendly alternatives==&lt;br /&gt;
&lt;br /&gt;
*[https://fluxer.app/ Fluxer] [https://github.com/fluxerapp/fluxer Fluxer&#039;s GitHub]&lt;br /&gt;
*[https://zulip.com/ Zulip][https://github.com/zulip/zulip/ Zulip&#039;s GitHub]&lt;br /&gt;
&lt;br /&gt;
*[https://stoat.chat/ Stoat] [https://github.com/stoatchat Stoat&#039;s GitHub]&lt;br /&gt;
&lt;br /&gt;
[[File:Discord Vague Infringement example.png|thumb|An example of how Discord handles its moderation from a user&#039;s perspective.]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;br /&gt;
[[Category:Social media companies]]&lt;br /&gt;
[[Category:Companies using forced arbitration clauses]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=ChatGPT&amp;diff=54709</id>
		<title>ChatGPT</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=ChatGPT&amp;diff=54709"/>
		<updated>2026-05-24T22:19:27Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ProductCargo&lt;br /&gt;
|Company=OpenAI&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|ReleaseYear=2022&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Software, Artificial Intelligence, Generative AI, Large Language Models&lt;br /&gt;
|Website=https://chatgpt.com/&lt;br /&gt;
|Description=ChatGPT data has been mishandled in the past, and is worsening with court-ordered data retention and integrated advertising.&lt;br /&gt;
|Logo=OpenAI logo (symbol).svg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ChatGPT&#039;&#039;&#039; (Chat Generative Pre-trained Transformer) is a generative artificial intelligence application developed and marketed by [[OpenAI]]. It was released on November 30th, 2022.&amp;lt;ref&amp;gt;{{Cite web |date=2022-11-30 |title=Introducing ChatGPT |url=https://openai.com/index/chatgpt/ |url-status=live |archive-url=http://web.archive.org/web/20260219054935/https://openai.com/index/chatgpt/ |archive-date=19 Feb 2026|access-date=2026-01-26 |website=OpenAI}}&amp;lt;/ref&amp;gt; It is a large language model (LLM) specialized in dialog that can perform human-like conversations. Various iterations of ChatGPT include GPT-3, GPT-4, GPT-4o, and previews of OpenAI-o1, OpenAI-o1 mini and GPT-5.&amp;lt;ref&amp;gt;{{Cite web |date=2025-07-09 |title=ChatGPT version history: Evolution timeline |url=https://nexos.ai/blog/chatgpt-version-history/ |url-status=live |archive-url=http://web.archive.org/web/20260217071448/https://nexos.ai/blog/chatgpt-version-history/ |archive-date=17 Feb 2026|access-date=2026-01-26 |website=nexos.ai}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Hayat |first=Usman |date=2025-08-22 |title=ChatGPT Version History List, Changelog &amp;amp; Latest Releases |url=https://wpexperts.io/blog/chatgpt-version-history/ |url-status=live |archive-url=http://web.archive.org/web/20251023153623/https://wpexperts.io/blog/chatgpt-version-history/ |archive-date=23 Oct 2025|access-date=2026-01-26 |website=WPExperts.io}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
===User freedom===&lt;br /&gt;
Users who are not logged in can use ChatGPT, but their access is limited (for example, they can only have one conversation at a time and cannot save chat history).&amp;lt;ref&amp;gt;{{Cite web |title=The ChatGPT home page |url=https://help.openai.com/en/articles/9125172-the-chatgpt-home-page |url-status=live |access-date=2026-02-19 |website=OpenAI Help Center |archive-url=http://web.archive.org/web/20260214024602/https://help.openai.com/en/articles/9125172-the-chatgpt-home-page |archive-date=14 Feb 2026}}&amp;lt;/ref&amp;gt; After GPT-5’s release, manual model selection is not available to all users: OpenAI limits the ChatGPT “model picker” to paid tiers, while other users may be routed automatically (e.g., via “Auto,” which can switch between model variants).&amp;lt;ref&amp;gt;{{Cite web |title=Model Release Notes |url=https://help.openai.com/en/articles/9624314-model-release-notes |website=OpenAI Help Center |access-date=2026-02-19 |archive-url=http://web.archive.org/web/20251230143058/https://help.openai.com/en/articles/9624314-model-release-notes |archive-date=30 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=ChatGPT Enterprise and Edu - Models &amp;amp; Limits |url=https://help.openai.com/en/articles/11165333-chatgpt-enterprise-and-edu-models-limits |website=OpenAI Help Center |access-date=2026-02-19 |archive-url=http://web.archive.org/web/20251211113140/https://help.openai.com/en/articles/11165333-chatgpt-enterprise-and-edu-models-limits |archive-date=11 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
A mobile phone number in a friendly country is required to better track your identity.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
====Data policy====&lt;br /&gt;
From OpenAI&#039;s data usage policy:&amp;lt;ref&amp;gt;{{Cite web |title=Data Usage for Consumer Services FAQ {{!}} OpenAI Help Center |url=https://help.openai.com/en/articles/7039943-data-usage-for-consumer-services-faq |url-status=live |archive-url=http://web.archive.org/web/20260210234712/https://help.openai.com/en/articles/7039943-data-usage-for-consumer-services-faq |archive-date=2026-02-10 |access-date=2026-01-27}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
{{Quote|We share content with a select group of trusted service providers that help us provide our services. We share the minimum amount of content we need in order to accomplish this purpose and our service providers are subject to strict confidentiality and security obligations. We do not use or share user content for marketing or advertising purposes.}}&lt;br /&gt;
The wording does not detail the extent of conversations shared with OpenAI&#039;s trusted service providers.&amp;lt;!-- (still) Placeholder. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Misleading advertising====&lt;br /&gt;
ChatGPT terms of service say it should not be used to make decisions about people.&amp;lt;ref&amp;gt;{{Cite web |title=Terms of Use {{!}} OpenAI |url=https://openai.com/policies/terms-of-use/ |url-status=live |archive-url=http://web.archive.org/web/20260123055141/https://openai.com/policies/terms-of-use/ |archive-date=2026-01-23 |access-date=2026-01-27}}&amp;lt;/ref&amp;gt; However, their advertising claims it is &amp;quot;PhD level&amp;quot; and makes other claims that seem to imply it is reliable. Many people use ChatGPT as if its output were meaningful, reliable, or a substitute for interaction with a person, with some cases involving &amp;quot;relationships&amp;quot; with the AI. [[ChatGPT-4o]] was one of their models known for inducing a lot of vulnerable users into AI psychosis.&lt;br /&gt;
&lt;br /&gt;
===Billing and moderation===&lt;br /&gt;
Credits (money) expire automatically with no notification, and the credit balance interface makes this process confusing. You must maintain a positive account balance, and you are auto-billed a fixed amount if it goes negative. The interface of users from the United States that have no subscription (Free tier) or are in the Go subscription tier shows integrated ads that appear inside the chats.&lt;br /&gt;
Accounts can be banned and credits confiscated for typing the wrong things in chat, with no recourse.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
===Market control===&lt;br /&gt;
Global market share data shows ChatGPT is the most used chatbot in the world (79.98% as of February 2026)&amp;lt;ref&amp;gt;{{Cite web |publisher=StatCounter |date=Feb 2026 |title=AI Chatbot Market Share Worldwide |url=https://gs.statcounter.com/ai-chatbot-market-share |url-status=live |archive-url=https://archive.is/stjr5 |archive-date=2026-03-09 |access-date=9 Mar 2026 |website=statcounter.com}}&amp;lt;/ref&amp;gt;. However, adoption has been declined since 2025 due to recent incidents, controversial decisions and comparable competitors, such as [[Google Gemini]] and [[Claude]]. &amp;lt;ref&amp;gt;{{Cite web |last=Nolan |first=Beatrice |date=5 Feb 2026 |title=ChatGPT’s market share is slipping as Google and rivals close the gap, app-tracker data shows |url=https://finance.yahoo.com/news/chatgpt-market-share-slipping-google-155419736.html |url-status=live |access-date=9 Mar 2026 |website=Yahoo Finance}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===Security breach (&#039;&#039;2023&#039;&#039;)===&lt;br /&gt;
On March 20, 2023 a bug allowed some users to see other users&#039; conversation titles. Sam Altman, OpenAI&#039;s CEO, stated users couldn&#039;t view other users&#039; conversation content. After the bug was fixed, users reported they were unable to view their conversation history. Later reports showed this issue was much bigger than it was thought at first, with OpenAI reporting there were leaks of the users&#039; name, last name, e-mail address, payment address, and partial credit card information.&amp;lt;ref&amp;gt;{{Cite web |last=Simo |first=Fidgi |date=20 March 2023 |title=March 20 ChatGPT outage: Here’s what happened |url=https://openai.com/index/march-20-chatgpt-outage/ |url-status=live |archive-url=http://web.archive.org/web/20260210072430/https://openai.com/index/march-20-chatgpt-outage/ |archive-date=10 Feb 2026|access-date=26 Jan 2026 |website=OpenAI}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===ChatGPT-4o (&#039;&#039;2024—2026&#039;&#039;)===&lt;br /&gt;
{{Main|ChatGPT-4o}}&lt;br /&gt;
&lt;br /&gt;
On May 13, 2024, OpenAI announced and released the model ChatGPT-4o.&amp;lt;ref&amp;gt;{{Cite web |author=OpenAI |date=13 May 2024 |title=Hello, GPT-4o |url=https://openai.com/es-ES/index/hello-gpt-4o/ |url-status=live |archive-url=http://web.archive.org/web/20251216045649/https://openai.com/es-ES/index/hello-gpt-4o/ |archive-date=16 Dec 2025|access-date=2026-02-17 |website=OpenAI}}&amp;lt;/ref&amp;gt; The model was temporarily retired from the public in April 2025 due to an update that caused the model to have excessive sycophancy. &amp;lt;ref&amp;gt;{{Cite web |last=Franzen |first=Carl |date=30 Apr 2025 |title=OpenAI rolls back ChatGPT&#039;s sycophancy and explains what went wrong |url=https://venturebeat.com/ai/openai-rolls-back-chatgpts-sycophancy-and-explains-what-went-wrong |url-status=live |archive-url=http://web.archive.org/web/20250815154215/https://venturebeat.com/ai/openai-rolls-back-chatgpts-sycophancy-and-explains-what-went-wrong/ |archive-date=15 Aug 2025|access-date=15 Feb 2026 |website=VentureBeat}}&amp;lt;/ref&amp;gt;It also had several controversies because of users developing [[wikipedia:Chatbot_psychosis|AI psychosis]], with some severe cases ending with users committing suicide. &amp;lt;ref&amp;gt;{{Cite web |last=Hill |first=Kashmir |date=13 Jun 2025 |url=https://www.nytimes.com/2025/06/13/technology/chatgpt-ai-chatbots-conspiracies.html|title=They Asked an A.I. Chatbot Questions. The Answers Sent Them Spiraling. |url-status=live |archive-url=http://web.archive.org/web/20260117185232/https://www.nytimes.com/2025/06/13/technology/chatgpt-ai-chatbots-conspiracies.html |archive-date=17 Jan 2026|access-date=2025-02-15 |website=The New York Times}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
With the launch of GPT-5 in August 2025, OpenAI removed legacy models from non-API users, such as GPT-4o. This decision caused an outrage, with users complaining about the removal of the models along with the complaints about GPT-5. OpenAI&#039;s response was to end paywalling these older models, making them available only for Plus users. &lt;br /&gt;
In 2026, OpenAI announced they will be removing definitely GPT-4o and other models, such as GPT-5 and GPT-4.1. On February 13, 2026, 4o and other legacy models were removed for non-API users, causing again controversies in social media. These legacy models will be removed for API-users on April 2026. {{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
===Users&#039; data retention by court mandate (&#039;&#039;May 2025—October 2025&#039;&#039;)===&lt;br /&gt;
On May 13, 2025, New York Times filed a lawsuit against OpenAI and Microsoft for copyright infringement. A court in New York mandated OpenAI to preserve users&#039; conversation logs, including data from deleted conversations and temporary conversations. This affected Free, Plus, Pro and Team subscription tiers and also non Zero-Data-Retention API users. Edu, Enterprise tiers and Zero-Data-Retention API users were exempt from this.&amp;lt;ref&amp;gt;{{Cite web |last=Bradbury |first=Danny |date=6 Jun 2025 |title=OpenAI forced to preserve ChatGPT chats |url=https://www.malwarebytes.com/blog/news/2025/06/openai-forced-to-preserve-chatgpt-chats |url-status=live |archive-url=http://web.archive.org/web/20251114012548/https://www.malwarebytes.com/blog/news/2025/06/openai-forced-to-preserve-chatgpt-chats |archive-date=14 Nov 2025|access-date=26 Jan 2026 |website=Malwarebytes}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=R |first=Sudha |date=15 Jul 2025 |title=ChatGPT To Retain Conversations Indefinitely |url=https://medium.com/aimonks/court-orders-openai-to-retain-chatgpt-conversations-indefinitely-what-you-need-to-know-1530f24501a6 |url-status=live |archive-url= |archive-date= |access-date=26 Jan 2026 |website=Medium}}&amp;lt;/ref&amp;gt; &amp;lt;!-- &amp;lt; The medium article, archive.today is stuck loading. https://archive.is/wip/Zyy1e. I don&#039;t feel like resetting my IA password atm. Just a note to future citers. -raster --&amp;gt; On September 26, 2025, the preservation order was revoked. However, some deleted and temporary chats will still be monitored for being flagged.&amp;lt;ref&amp;gt;{{Cite web |last=Belanger |first=Ashley |date=10 Oct 2025 |title=OpenAI will stop saving most ChatGPT users’ deleted chats |url=https://arstechnica.com/tech-policy/2025/10/openai-no-longer-forced-to-save-deleted-chats-but-some-users-still-affected/ |url-status=live |archive-url=http://web.archive.org/web/20260101145932/https://arstechnica.com/tech-policy/2025/10/openai-no-longer-forced-to-save-deleted-chats-but-some-users-still-affected/ |archive-date=1 Jan 2026|access-date=26 Jan 2026 |website=Ars Technica}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GPT-5 release (&#039;&#039;August 2025&#039;&#039;)===&lt;br /&gt;
On August 7, 2025, OpenAI released their newest model, GPT-5. The next day, several users complained in social media about the performance of the model, claiming it was underwhelming and was &amp;quot;dumber&amp;quot; than the previous model. Users also realised OpenAI&#039;s platform was most of the time setting the lowest-performance GPT-5 models and discovered they can make the platform to set the better-performance models by adding &amp;quot;think harder&amp;quot; in prompts. Sam Altman claimed that a &amp;quot;malfunction&amp;quot; of the autoswitcher was the reason behind GPT-5 performance.&lt;br /&gt;
&amp;lt;ref&amp;gt;{{Cite web |last=Edwards |first=Benj |date=11 Aug 2025 |title=The GPT-5 rollout has been a big mess |url=https://arstechnica.com/information-technology/2025/08/the-gpt-5-rollout-has-been-a-big-mess/ |url-status=live |archive-url=http://web.archive.org/web/20260109001515/https://arstechnica.com/information-technology/2025/08/the-gpt-5-rollout-has-been-a-big-mess/ |archive-date=9 Jan 2026|access-date=5 Feb 2026 |website=Ars Technica}}&amp;lt;/ref&amp;gt; &amp;lt;ref&amp;gt;{{Cite web |last=Franzen |first=Carl |date=8 Aug 2025 |title=OpenAI returns old models to ChatGPT as Sam Altman admits ‘bumpy’ GPT-5 rollout |url=https://venturebeat.com/business/openai-returns-old-models-to-chatgpt-as-sam-altman-admits-bumpy-gpt-5-rollout |url-status=live |archive-url=https://archive.is/hunUK |archive-date=2026-02-05 |access-date=5 Feb 2026 |website=VentureBeat}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===Age verification (&#039;&#039;2026&#039;&#039;)===&lt;br /&gt;
With a justification to &amp;quot;help teens have an age-appropriate experience on ChatGPT&amp;quot;, the platform will be implementing globally an [[age verification]] system to detect if a user is over 18 to allow them to access to mature content. OpenAI will scan and analyze the user&#039;s account, their conversations and their behavior - including the times of a day they use ChatGPT - to estimate their age. If this system detects a user as underage, it will use third-party tools provided by [[Persona]] to estimate their age, asking the user to upload a selfie or their government ID. If the user refuses to send a selfie or their ID, the platform will limit ChatGPT&#039;s generated content.&amp;lt;ref&amp;gt;{{Cite web |date=21 Jan 2026 |title=Age prediction in ChatGPT |url=https://help.openai.com/en/articles/12652064-age-prediction-in-chatgpt |url-status=live |archive-url=http://web.archive.org/web/20260119032400/https://help.openai.com/en/articles/12652064-age-prediction-in-chatgpt |archive-date=19 Jan 2026|access-date=26 Jan 2026 |website=OpenAI}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Integrated ads (&#039;&#039;February 2026&#039;&#039;)===&lt;br /&gt;
On January 16, 2026, OpenAI announced that they will be implementing ads for &amp;quot;testing purposes&amp;quot;. &amp;lt;ref&amp;gt;{{Cite web |last=Simo |first=Fidgi |date=16 Jan 2026 |title=Our approach to advertising and expanding access to ChatGPT |url=https://openai.com/index/our-approach-to-advertising-and-expanding-access/ |url-status=live |archive-url=http://web.archive.org/web/20260118192220/https://openai.com/index/our-approach-to-advertising-and-expanding-access/ |archive-date=18 Jan 2026|access-date=25 Jan 2026 |website=OpenAI}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Cirello |first=Rafaelle F |last2=Backholer |first2=Kathryn |date=23 Jan 2026 |title=OpenAI will put ads in ChatGPT. This opens a new door for dangerous influence |url=https://theconversation.com/openai-will-put-ads-in-chatgpt-this-opens-a-new-door-for-dangerous-influence-273806 |url-status=live |archive-url=http://web.archive.org/web/20260125175609/https://theconversation.com/openai-will-put-ads-in-chatgpt-this-opens-a-new-door-for-dangerous-influence-273806 |archive-date=25 Jan 2026|access-date=26 Jan 2026}}&amp;lt;/ref&amp;gt; On February 9, 2026, ads rolled out, affecting users over 18 from the US who are in Free and Go subscription tiers. Pro, Business and Enterprise tiers are exempt from this. These ads are [[Personalized ads|personalized ads]] that appear at the bottom of ChatGPT&#039;s messages, showing the sponsored site name next to a &amp;quot;Sponsored&amp;quot; text, and below it, links to the sponsored site. OpenAI stated the ads that appear are based on current conversations, ads that user has engaged with, and past chats and ChatGPT&#039;s memories. OpenAI also claims the data provided to show ads &amp;quot;it&#039;s not shared with advertisers&amp;quot;. It is possible to opt-out for getting personalized ads and delete ads data. &amp;lt;!-- (If you&#039;re from the US and have access to ads in ChatGPT please check if personalized ads is active by default and if something from here is wrong. If so, please add that info on this entry) --&amp;gt;  &amp;lt;ref&amp;gt;https://x.com/OpenAI/status/2020936703763153010 - Archived: https://megalodon.jp/2026-0304-0444-55/https://x.com:443/OpenAI/status/2020936703763153010&amp;lt;/ref&amp;gt; The announcement and release of this patch has raised several concerns about privacy &amp;lt;ref&amp;gt;{{Cite web |last=Werthmuller |first=Digby |date=1 Mar 2026 |title=Privacy fears as OpenAI trials ads in its ChatGPT chatbot in the US |url=https://www.abc.net.au/news/2026-03-02/open-ai-testing-ads-in-chatgpt-in-us-plans-to-rollout-globally/106377798 |url-status=live |archive-url=https://archive.is/OEdhY |archive-date=2026-03-02 |access-date=3 Mar 2026 |website=ABC.net}}&amp;lt;/ref&amp;gt;, data usage, ad experience potentially becoming worse &amp;lt;ref&amp;gt;{{Cite web |last=Serazio |first=Michael |date=3 Mar 2026 |title=AI Is Going to Revolutionize Advertising in the Worst Imaginable Way |url=https://newrepublic.com/article/207106/chatgpt-ads-open-ai-revolutionize-advertising-worst-imaginable-way |url-status=live |archive-url=https://archive.is/w2bJw |archive-date=2026-03-03 |access-date=3 Mar 2026 |website=The New Republic}}&amp;lt;/ref&amp;gt;, and the AI usage to manipulate users. After the ad release in the US, users have experienced that ads can appear on a new conversation by just sending the first prompt, something that was considered as aggresive advertising. &amp;lt;ref&amp;gt;{{Cite web |last=Adegbola |first=Anu |date=19 Feb 2026 |title=ChatGPT ads spotted and they are quite aggressive |url=https://searchengineland.com/chatgpt-ads-spotted-and-they-are-quite-aggressive-469651 |url-status=live |archive-url=https://archive.is/V5bRc |archive-date=2026-03-03 |access-date=3 Mar 2026 |website=Search Engine Land}}&amp;lt;/ref&amp;gt; &amp;lt;ref&amp;gt;{{Cite web |last=Kasanmascheff |first=Markus|date=21 Feb 2026 |title=ChatGPT Ads Now Hit on Your Very First Message |url=https://winbuzzer.com/2026/02/21/chatgpt-ads-now-appearing-first-prompt-free-users-openai-xcxwbn/ |url-status=live |archive-url=https://archive.is/K1l8s |archive-date=2026-03-03 |access-date=3 Mar 2026 |website=WinBuzzer}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[OpenAI]]&lt;br /&gt;
*[[Artificial intelligence]]&lt;br /&gt;
*[[Claude]]&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>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Artificial_intelligence/training&amp;diff=54708</id>
		<title>Artificial intelligence/training</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Artificial_intelligence/training&amp;diff=54708"/>
		<updated>2026-05-24T22:17:54Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
&#039;&#039;&#039;AI training&#039;&#039;&#039; is a process by which data is fed into an [[Artificial intelligence|AI]] model, in order to adjust its weights. This makes the output of the model closely match that of its input.&lt;br /&gt;
&lt;br /&gt;
==How it works==&lt;br /&gt;
There are several ways to implement AI, and even more ways to train them, the most well-known being [[wikipedia:Backpropagation|backpropagation]]. With respect to the data-set, LLMs must be trained on massive amounts of data, which is a task that&#039;s only feasible via automation. This is in contrast to curated data-sets, in which both the data and the training is done in a more carefully controlled environment. Automated training on massive data-sets is typically done using internet web-sites as sources. The process of scraping is similar to how web-[[wikipedia:Search_engine|search-engines]] index and [[wikipedia:Cache_(computing)|cache]] pages.&lt;br /&gt;
&lt;br /&gt;
==Why it is a problem==&lt;br /&gt;
&lt;br /&gt;
===Intellectual property laundering===&lt;br /&gt;
Most, if not all, of the data used for training is copied indiscriminately, without even checking licenses or any copyright terms.{{Citation needed}} This is very controversial. Some people argue that it is &amp;quot;fair use&amp;quot; because AI systems learn in ways similar to animal and human brains, others claim it&#039;s more like [[wikt:parroting|a parrot learning phrases]], others claim that it&#039;s &amp;quot;transformative&amp;quot; so it&#039;s still fair-use, others say it&#039;s akin to [[wikipedia:Tracing_(art)|tracing images]] (this applies mostly to image models, though the analogy can work for text models).{{Citation needed|reason=too many opinions}}&lt;br /&gt;
&lt;br /&gt;
Ultimately, it depends a lot on the technical details of how each model works, so none of those arguments are universal.&lt;br /&gt;
&lt;br /&gt;
Some people request that, at the very least, the sources of the training data must be publicly disclosed, for the sake of [[wikipedia:Transparency_(behavior)|transparency]] and [[wikipedia:Attribution_(copyright)|attribution]].&amp;lt;ref&amp;gt;{{Cite web |last=Tunney |first=Justine |date=2024-08-23 |title=AI Training Shouldn&#039;t Erase Authorship |url=https://justine.lol/history/ |access-date=2026-04-26}}&amp;lt;/ref&amp;gt; Others propose that authors should be [[wikipedia:Financial_compensation|compensated]] in some way, and that AI should be regulated.&amp;lt;ref&amp;gt;{{Cite web |last=Hartzell |first=Jimmy |date=2024-06-30 |title=Large Language Models Should Have to Obey Copyright |url=https://www.thecodedmessage.com/posts/llm-copyright/ |access-date=2026-05-18 |website=The Coded Message}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Energy use===&lt;br /&gt;
While [[Self-hosting|self-hosted]] models can be trained with a single consumer-grade [[wikipedia:Graphics_processing_unit|GPU]], data-centers with hundreds or thousands of GPUs (known for being more power-hungry than CPUs) are used to train corporate-grade (or &amp;quot;enterprise&amp;quot;) models. This can worsen [[wikipedia:Climate_change|climate change]].&lt;br /&gt;
&lt;br /&gt;
===Bandwidth abuse===&lt;br /&gt;
Massive data needs massive bandwidth. Scraping web-pages across the entire internet requires sending millions of requests to all known servers. Some AI companies go as far as to &#039;&#039;repeatedly&#039;&#039; send requests for the same content (or several revisions of the same content) as frequent bursts in short intervals, which is indistinguishable from [[wikipedia:Denial-of-service_attack|distributed denial-of-service (DDoS) attacks]].&lt;br /&gt;
&lt;br /&gt;
===Chip shortage===&lt;br /&gt;
Many AI companies have pre-ordered massive amounts of computer components. So much that it doesn&#039;t even fit in their current data-centers. This is done in anticipation for &#039;&#039;more&#039;&#039; data-centers being built.{{Citation needed}} This has caused such components to become scarce, and prices to spike. The most notable being the [[RAM shortage|increase in RAM prices]].&lt;br /&gt;
&lt;br /&gt;
==Examples==&lt;br /&gt;
While &amp;quot;mainstream&amp;quot; companies such as [[OpenAI]], [[Anthropic]], and [[Meta]] appear to correctly follow industry-standard practice for web crawlers, others ignore them (such as [[wikipedia:Alibaba_Group|Alibaba]]&amp;lt;ref&amp;gt;{{Cite news |last=Venerandi |first=Niccolò |title=FOSS infrastructure is under attack by AI companies |url=https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies |access-date=2026-02-23 |work=LibreNews |archive-url=http://web.archive.org/web/20260217195639/https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/ |archive-date=17 Feb 2026}}&amp;lt;/ref&amp;gt;), causing DDoS attacks which damage access to freely-accessible websites. This is particularly an issue for websites that are large or contain many dynamic links.&lt;br /&gt;
&lt;br /&gt;
Ethical website scrapers, known as &amp;quot;spiders&amp;quot; that crawl the web, follow a certain set of minimum guidelines. Specifically, they follow &amp;lt;code&amp;gt;[[wikipedia:robots.txt|robots.txt]]&amp;lt;/code&amp;gt;, a text file found at the root of a domain that indicates:&lt;br /&gt;
&lt;br /&gt;
*Paths bots are allowed to index&lt;br /&gt;
*Paths bots should not index&lt;br /&gt;
*How long the bot should wait in between requests to the server, to reduce load&lt;br /&gt;
*The [[wikipedia:Sitemaps|sitemap]] of the website&#039;s content&lt;br /&gt;
&lt;br /&gt;
These rules are typically configured for all bots, with minor adjustments made to individual bots as needed. Additionally, specific web pages may use the [[wikipedia:noindex|robots meta tag]] to control use of their output.&lt;br /&gt;
&lt;br /&gt;
While it is good practice for a bot to respect &amp;lt;code&amp;gt;robots.txt&amp;lt;/code&amp;gt;, there is no requirement for it, and there is no punishment for not following a website&#039;s wishes. It is additionally standard practice, but in no way enforced, that bots use a [[wikipedia:User-Agent header|User-Agent header]] to uniquely identify itself. This allows a website operator to observe a bot&#039;s traffic patterns, potentially blocking the bot outright if its scraping is not desirable. The header also typically contains a URL or email address that can be used to contact the operator in case of anomalies observed in its traffic.&lt;br /&gt;
&lt;br /&gt;
Unethical [[Artificial_intelligence|AI]] scraper bots do not follow &amp;lt;code&amp;gt;robots.txt&amp;lt;/code&amp;gt; - in fact, they may not even request this file at all. They typically completely ignore it, instead opting to start from an entry point such as the root home page (&amp;lt;code&amp;gt;/&amp;lt;/code&amp;gt;), working its way through an exponentially growing list of links as it finds them, with little to no delay between requests. The bots use false User-Agent header strings that would correspond to real web browsers on desktop or mobile operating systems - blocking them would also block legitimate users, or at least legitimate users on VPNs.&lt;br /&gt;
&lt;br /&gt;
Some AI services opt to use separate User-Agent strings, potentially also ignoring &amp;lt;code&amp;gt;robots.txt&amp;lt;/code&amp;gt;, when a request is made through user command rather than as part of model training. For example, ChatGPT identifies itself as &amp;lt;code&amp;gt;ChatGPT-User&amp;lt;/code&amp;gt; rather than its standard &amp;lt;code&amp;gt;OpenAI&amp;lt;/code&amp;gt; when it uses the &amp;quot;search the web&amp;quot; command - even if searching the web was an automatic decision. In a less favorable example, Perplexity AI in this same situation falsely identifies as a standard [[Google_Chrome|Chrome]] web browser running on [[Microsoft_Windows|Windows]]. AI companies defend this under the belief that they are not a &amp;quot;spider&amp;quot;, but rather a &amp;quot;user agent&amp;quot; (like a web browser), when called upon by a user&#039;s request.&amp;lt;ref name=&amp;quot;perplexity-aws&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Less legitimate bots use a wide distribution of IP addresses, further reducing options for the website to protect itself. This is in a clear attempt to bypass IP-based request throttling and rate limiting the website may implement. They are also known to ignore HTTP response status codes that indicate a server error ([[wikipedia:HTTP status code#5xx server errors|5xx]]), or warnings that the client needs to slow down ([[wikipedia:HTTP status code#429|429 Too Many Requests]]) or has been entirely blocked ([[wikipedia:HTTP status code#403|403 Forbidden]]).&lt;br /&gt;
&lt;br /&gt;
===Effect on users===&lt;br /&gt;
To protect against unethical crawlers, due to concerns of both intellectual property and service disruption, websites adopt practices that affect the experience of real users:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Bot check walls&#039;&#039;&#039;: The user may be required to pass a security check &amp;quot;wall&amp;quot;. While usually automatic for the user, this can affect legitimate bots. When a website protection service such as [[Cloudflare]] is not confident as to whether the visitor is legitimate, it may present a [[CAPTCHA]] to be manually filled out. An example is &amp;quot;Google Sorry&amp;quot;, a CAPTCHA wall frequently seen when using Google Search via a VPN. An example that&#039;s popular in the FOSS community is {{Wplink|Anubis (software)|Anubis}}.&lt;br /&gt;
*&#039;&#039;&#039;Login walls&#039;&#039;&#039;: Should bots be found to pass CAPTCHA walls, the website may advance to requiring logging in to view content. A major recent example of this is [[YouTube]]&#039;s &amp;quot;Sign in to confirm you&#039;re not a bot&amp;quot; messages.&lt;br /&gt;
*&#039;&#039;&#039;JavaScript requirement&#039;&#039;&#039;: Most websites do not need [[JavaScript]] to deliver their content. However, as many scrapers expect content to be found directly in the HTML, it is often an easy workaround to use JavaScript to &amp;quot;insert&amp;quot; the content after the page has loaded. This may reduce the responsiveness of the website, increasing points of failure, and preventing security-conscious users who disable JavaScript from viewing the website.&lt;br /&gt;
*&#039;&#039;&#039;IP address blocking&#039;&#039;&#039;: Blocking IP addresses, especially by blocking entire providers via their {{Wplink|Autonomous system (Internet)|autonomous system number}}, always comes with some risk of blocking legitimate users. Particularly, this may restrict access to users making use of a VPN.&lt;br /&gt;
*&#039;&#039;&#039;Heuristic blocking&#039;&#039;&#039;: Patterns in request headers may give away that the request is being made by an unethical bot, despite attempts to act as a legitimate visitor. Heuristics are imperfect and may block legitimate users, especially those that may use less common browsers.&lt;br /&gt;
&lt;br /&gt;
In rare situations, a website operator may redirect detected bot traffic, such as to download speed test files hosted by ISPs containing multiple gigabytes of random garbage data. This may have the effect of disrupting the bot, but its effectiveness is unknown.&lt;br /&gt;
&lt;br /&gt;
The need to respond to unethical scraping also further consolidates the web into the control of a few large {{Wplink|Web application firewall|web application firewall}} (WAF) services, most notably [[Cloudflare]], as website owners find themselves otherwise unable to protect their service from being disrupted by such traffic.&lt;br /&gt;
&lt;br /&gt;
===Case studies===&lt;br /&gt;
====Diaspora====&lt;br /&gt;
On 27 December 2024, the open-source social network project Diaspora noted that 70% of traffic across its infrastructure was in service of AI scrapers.&amp;lt;ref name=&amp;quot;geraspora&amp;quot;&amp;gt;{{Cite web |last=Schubert |first=Dennis |date=27 Dec 2024 |title=In the last 60 days, the diaspora* web assets received 11.3 million requests ... |url=https://pod.geraspora.de/posts/17342163 |via=Diaspora* |url-status=live |archive-url=http://web.archive.org/web/20251203054837/https://pod.geraspora.de/posts/17342163 |archive-date=3 Dec 2025}}&amp;lt;/ref&amp;gt; Particularly, the project noted that bots had followed links to crawl every individual edit in their [[#MediaWiki|MediaWiki]] instance, causing an exponential increase in the number of unique requests being made.&lt;br /&gt;
&lt;br /&gt;
====LVFS====&lt;br /&gt;
The [https://fwupd.org/ Linux Vendor Firmware Service] (LVFS) provides a free central store of firmware updates, such as for UEFI motherboards and SSD controllers. This feature is integrated with many Linux distributions through the &amp;lt;code&amp;gt;fwupd&amp;lt;/code&amp;gt; daemon. For situations where internet access is not permitted, the service allows users to make a local mirror of the entire 100+ GB store.&lt;br /&gt;
&lt;br /&gt;
On 9 January 2025, the project announced that it would introduce a login wall around its mirror feature, citing unnecessary use of its bandwidth.&amp;lt;ref&amp;gt;{{Cite web |last=Hughes |first=Richard |date=9 Jan 2025 |title=Authentication soon required to mirror the entire LVFS |url=https://lore.kernel.org/lvfs-announce/zDlhotSvKqnMDfkCKaE_u4-8uvWsgkuj18ifLBwrLN9vWWrIJjrYQ-QfhpY3xuwIXuZgzOVajW99ymoWmijTdngeFRVjM0BxhPZquUzbDfM=@hughsie.com/T/ |website=Linux Vendor Firmware Service (LVFS) mailing list |url-status=live |archive-url=http://web.archive.org/web/20250901012238/https://lore.kernel.org/lvfs-announce/zDlhotSvKqnMDfkCKaE_u4-8uvWsgkuj18ifLBwrLN9vWWrIJjrYQ-QfhpY3xuwIXuZgzOVajW99ymoWmijTdngeFRVjM0BxhPZquUzbDfM=@hughsie.com/T/ |archive-date=1 Sep 2025}}&amp;lt;/ref&amp;gt; Up to 1,000 files may be downloaded per day without logging in. The author later mentioned on Mastodon that the problem appears to be caused by AI scraping.&amp;lt;ref&amp;gt;{{Cite web |last=Hughes |first=Richard |date=22 Jan 2025 |title=Commentary citing &#039;Authentication soon required to mirror the entire LVFS&#039; |url=https://mastodon.social/@hughsie/113871373001227969 |via=Mastodon |url-status=live |archive-url=http://web.archive.org/web/20251019021656/https://mastodon.social/@hughsie/113871373001227969 |archive-date=19 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====LWN.net====&lt;br /&gt;
On 21 January 2025, Jonathan Corbet, maintainer of the Linux news website [[wikipedia:LWN.net|LWN.net]], made the following [https://social.kernel.org/notice/AqJkUigsjad3gQc664 post] to social.kernel.org:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Should you be wondering why @LWN #LWN is occasionally sluggish... since the new year, the DDOS onslaughts from AI-scraper bots has picked up considerably. Only a small fraction of our traffic is serving actual human readers at this point. At times, some bot decides to hit us from hundreds of IP addresses at once, clogging the works. They don&#039;t identify themselves as bots, and robots.txt is the only thing they *don&#039;t* read off the site.&lt;br /&gt;
&lt;br /&gt;
This is beyond unsustainable. We are going to have to put time into deploying some sort of active defenses just to keep the site online. I think I&#039;d even rather be writing about accounting systems than dealing with this cr*p. And it&#039;s not just us, of course; this behavior is going to wreck the net even more than it&#039;s already wrecked.&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
He later commented:&amp;lt;ref&amp;gt;{{Cite web |last=Knop |first=Dirk |date=22 Jan 2025 |title=AI bots paralyze Linux news site and others |url=https://www.heise.de/en/news/AI-bots-paralyze-Linux-news-site-and-others-10252162.html |website=Heise |language=en, de |url-status=live |archive-url=http://web.archive.org/web/20251018112153/https://www.heise.de/en/news/AI-bots-paralyze-Linux-news-site-and-others-10252162.html |archive-date=18 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
We do indeed see a kind of pattern. Every IP stays below the threshold for our fuses, but the overload is overwhelming. Any form of active defense will probably have to figure out to block entire subnets instead of individual addresses, and even that might not be enough.&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====MediaWiki, Wikipedia, and the Wikimedia Foundation====&lt;br /&gt;
[[wikipedia:MediaWiki|MediaWiki]] is of particular interest to LLM training due to the vast amount of factual, plain-text content wikis tend to hold. While [[wikipedia:Wikipedia|Wikipedia]] and the [[wikipedia:Wikimedia Foundation|Wikimedia Foundation]] host the most well-known wikis, numerous smaller wikis exist thanks to the work of many independent editors. The strength of wiki architecture is its ability for every edit to be audited by anyone, at any time - you can still view [https://en.wikipedia.org/w/index.php?oldid=1 the first edit to Wikipedia] from 2002. This makes wikis a hybrid of a static website and a dynamic web app, which becomes problematic when poorly-designed bots attempt to scrape them.&amp;lt;ref name=&amp;quot;geraspora&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- COI alert: I, [[User:kirb]], am an admin for The Apple Wiki. Hopefully this is neutral enough?&lt;br /&gt;
--&amp;gt;The Apple Wiki, which documents internal details of Apple&#039;s hardware and software, holds more than 50,000 articles. On 2 August 2024, with a repeat occurrence on 5 January 2025, the service was disrupted by scraping efforts.&amp;lt;ref&amp;gt;{{Cite web |title=Bot traffic abuse |url=https://theapplewiki.com/wiki/The_Apple_Wiki:Community_portal#Bot_traffic_abuse |website=The Apple Wiki |url-status=live |archive-url=http://web.archive.org/web/20260130154004/https://theapplewiki.com/wiki/The_Apple_Wiki:Community_portal |archive-date=30 Jan 2026}}&amp;lt;/ref&amp;gt; The wiki contains a considerable amount of information that is scraped by legitimate security research tools, making it difficult for the website to block non-legitimate requests. Efforts to block unethical scraping and protect the wiki have disrupted these legitimate tools. The large article count, combined with more than 280,000 total edits over the wiki&#039;s lifetime, create an untenable situation where it is simply not possible to scrape the website without causing significant service disruption.&lt;br /&gt;
&lt;br /&gt;
On 1 April 2025, the Wikimedia Foundation indicated that its infrastructure has been under increasing pressure from content scraping bots since January 2024, with the particularly critical metric that &amp;quot;65% of our most expensive traffic comes from bots&amp;quot;, despite estimating 35% of all traffic as coming from bots. The bots create traffic patterns that are significantly unlike human traffic patterns, effectively bypassing Wikimedia&#039;s caching infrastructure and placing significant load on the core servers. A blog post provides an example where bot traffic caused the [[wikipedia:Wikimedia Commons|Wikimedia Commons]] service to become unstable during a human traffic spike. The Foundation is considering introduction of a Responsible Use of Infrastructure policy to ensure the continued stability of their services.&amp;lt;ref&amp;gt;{{Cite web |last=Mueller |first=Birgit |last2=Danis |first2=Chris |last3=Lavagetto |first3=Giuseppe |date=1 Apr 2025 |title=How crawlers impact the operations of the Wikimedia projects |url=https://diff.wikimedia.org/2025/04/01/how-crawlers-impact-the-operations-of-the-wikimedia-projects/ |website=Wikimedia Foundation |url-status=live |archive-url=http://web.archive.org/web/20260207164851/https://diff.wikimedia.org/2025/04/01/how-crawlers-impact-the-operations-of-the-wikimedia-projects/ |archive-date=7 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Perplexity AI and news outlets====&lt;br /&gt;
[[Perplexity AI]], founded in August 2022, is a large language model that aims to be viewed as a general search engine. It encourages users to consume news through its summaries of stories.&lt;br /&gt;
&lt;br /&gt;
On 15 June 2024, an investigation by Apple blog MacStories found that Perplexity does not follow its own documented policies when accessing content the user requests from the web. In their testing, the scraper pretended to be Chrome 111 running on Windows 10, connecting from an IP address not found in Perplexity&#039;s publicly-listed IP address ranges.&amp;lt;ref&amp;gt;{{Cite web |last=Knight |first=Robb |date=15 Jun 2024 |title=Perplexity AI Is Lying about Their User Agent |url=https://rknight.me/blog/perplexity-ai-is-lying-about-its-user-agent/ |url-status=live |archive-url=http://web.archive.org/web/20260123072701/https://rknight.me/blog/perplexity-ai-is-lying-about-its-user-agent/ |archive-date=23 Jan 2026}}&amp;lt;/ref&amp;gt; MacStories&#039; findings were confirmed by a WIRED investigation.&amp;lt;ref&amp;gt;{{Cite web |last=Mehrotra |first=Dhruv |last2=Marchman |first2=Tim |date=19 Jun 2024 |title=Perplexity Is a Bullshit Machine |url=https://www.wired.com/story/perplexity-is-a-bullshit-machine/ |website=WIRED |url-status=live |archive-url=http://web.archive.org/web/20260201173126/https://www.wired.com/story/perplexity-is-a-bullshit-machine/ |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt; Perplexity responded by removing its list of IP addresses.&lt;br /&gt;
&lt;br /&gt;
On 27 June 2024, [[Amazon]] announced an investigation into Perplexity AI, suggesting the behavior may be considered abusive under Amazon Web Services terms of service:&amp;lt;ref name=&amp;quot;perplexity-aws&amp;quot;&amp;gt;{{Cite web |last=Mehrotra |first=Dhruv |date=27 Jun 2024 |title=Amazon Is Investigating Perplexity Over Claims of Scraping Abuse |url=https://www.wired.com/story/aws-perplexity-bot-scraping-investigation/ |website=WIRED |url-status=live |archive-url=https://web.archive.org/web/20260202160655/https://www.wired.com/story/aws-perplexity-bot-scraping-investigation/ |archive-date=2 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
&amp;quot;AWS&#039;s terms of service prohibit abusive and illegal activities and our customers are responsible for complying with those terms,&amp;quot; [AWS spokesperson Patrick] Neighorn said in a statement. &amp;quot;We routinely receive reports of alleged abuse from a variety of sources and engage our customers to understand those reports.&amp;quot;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Read the Docs====&lt;br /&gt;
In an early example, on 25 July 2024, open source documentation website Read the Docs detailed cases of abusive bots downloading large amounts of content from the service. Particularly, the significant range of IP addresses used in an aggressive manner rendered existing rate limiting ineffective. Taking action to block traffic identified by Cloudflare as &amp;quot;AI crawlers&amp;quot; reduced bandwidth requirements by 75%, at a cost saving of $1,500 USD/month.&amp;lt;ref&amp;gt;{{Cite web |last=Holscher |first=Eric |date=25 Jul 2024 |title=AI crawlers need to be more respectful |url=https://about.readthedocs.com/blog/2024/07/ai-crawlers-abuse/ |website=Read the Docs |url-status=live |archive-url=http://web.archive.org/web/20251028100640/https://about.readthedocs.com/blog/2024/07/ai-crawlers-abuse/ |archive-date=28 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====SourceHut and Fedora Linux====&lt;br /&gt;
On 15 March 2025, an infrastructure manager for the [[wikipedia:Fedora Linux|Fedora Linux]] open source project discussed an assumed large language model crawling attack against the Prague.io Git source code hosting service. The project made the decision to block the entire country of Brazil for some time, while also blocking access to certain repositories whose traffic was creating significant CPU usage.&amp;lt;ref&amp;gt;{{Cite web |last=Fenzi |first=Kevin |date=15 Mar 2025 |title=Mid March infra bits 2025 |url=https://www.scrye.com/blogs/nirik/posts/2025/03/15/mid-march-infra-bits-2025/ |url-status=live |archive-url=https://web.archive.org/web/20260215235430/https://www.scrye.com/blogs/nirik/posts/2025/03/15/mid-march-infra-bits-2025/ |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Fenzi |first=Kevin |date=29 Mar 2025 |title=Late March infra bits 2025 |url=https://www.scrye.com/blogs/nirik/posts/2025/03/29/late-march-infra-bits-2025/ |url-status=live |archive-url=http://web.archive.org/web/20251018081550/https://www.scrye.com/blogs/nirik/posts/2025/03/29/late-march-infra-bits-2025/ |archive-date=18 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On 17 March 2025, the Git source code host SourceHut announced that the service was being disrupted by large language model crawlers. Mitigations deployed to reduce disruption involved requiring login for some areas of the service, and blocking IP ranges of cloud providers, affecting legitimate use of the website by its users.&amp;lt;ref&amp;gt;{{Cite web |date=17 Mar 2025 |title=LLM crawlers continue to DDoS SourceHut |url=https://status.sr.ht/issues/2025-03-17-git.sr.ht-llms/ |website=sr.ht status |url-status=live |archive-url=http://web.archive.org/web/20251220125852/https://status.sr.ht/issues/2025-03-17-git.sr.ht-llms/ |archive-date=20 Dec 2025}}&amp;lt;/ref&amp;gt; In response to the event, SourceHut founder Drew DeVault wrote a blog post entitled &amp;quot;[https://drewdevault.com/2025/03/17/2025-03-17-Stop-externalizing-your-costs-on-me.html Please stop externalizing your costs directly into my face]&amp;quot;, discussing his frustrations with having ongoing and ever-adapting attacks that must be addressed in a timely fashion to reduce disruption to legitimate SourceHut users. DeVault estimates that between &amp;quot;20-100%&amp;quot; of his time is now spent addressing such attacks.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Artificial intelligence|*Training]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Generative_artificial_intelligence&amp;diff=54707</id>
		<title>Generative artificial intelligence</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Generative_artificial_intelligence&amp;diff=54707"/>
		<updated>2026-05-24T22:17:10Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&amp;lt;!-- ADMIN COMMENT: This article is fine as a collection of consumer-facing GenAI issues and incidents, however we need to avoid straying into territory relating to workers rights, the ethics of web-scraping for training data, or other similar concerns. This wiki is to be strictly focussed on consumer affairs! If a company changes the terms of a contract to force users into letting their private data be used for AI training, that is relevant. If a company has laid off 500 workers to replace them with a chatbot, the treatment of those workers is not relevant to this wiki (although consumer-facing issues caused by the use of the chatbot might be!).--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Main|Artificial intelligence}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Generative AI&#039;&#039;&#039;, also referred to as GenAI or simply &amp;quot;AI&amp;quot; in colloquial English, is a program or service with the purpose of &amp;quot;generating&amp;quot; pieces of media (text, code, videos, images, et cetera) with a text prompt as an input (e.g. &amp;quot;How long do I heat popcorn for in the microwave?&amp;quot; or &amp;quot;bowl of buttery popcorn, realistic, artstation, pretty&amp;quot;) utilizing a captioned dataset, and various/random outputs relating to the prompt. GenAI, over its short existence and rising prevalence in online communities, has garnered large amounts of concern across the various fields it has been applied to. &amp;lt;!-- I used to help operate a Kialo discussion covering Generative AI, that discussion may be beneficial for reference as a way to further flesh this page out. Just please take note that most claims are a few years old and may not be accurate, so please fact-check any statements from there before mentioning anything anti-consumer here&lt;br /&gt;
&lt;br /&gt;
https://www.kialo.com/is-ai-art-theft-60905 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==General controversies surrounding Generative AI==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+General controversies surroundng GenAI&lt;br /&gt;
!Controversy&lt;br /&gt;
!Brief Description&lt;br /&gt;
!Related Article(s)/Section(s)&lt;br /&gt;
|-&lt;br /&gt;
|Training data collected without consent&lt;br /&gt;
|Various platforms have scraped data ranging within the petabytes concerning content created by users and potentially owned by companies, without first obtaining an adequate license to use this data. This has gone so far as to not even request consent or even notifying users in advance that their content was used to train AI-powered tools.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Replacing skilled workers with AI&lt;br /&gt;
|Due to its generalized nature, jobs across fields from digital art to writing and programming have had experienced staff replaced by lesser-paid (and often lesser-experienced) employees who would be tasked to use generative tools to do their work. This usage can lead to problems with product quality for consumers, such as representatives replaced with chatbots, or products being sold by companies use poorly-generated content that may harm the consumer.&amp;lt;ref&amp;gt;{{Cite web |last=Grady |first=Constance |date=29 Apr 2024 |title=The AI grift that can literally poison you |url=https://www.vox.com/24141648/ai-ebook-grift-mushroom-foraging-mycological-society |url-status=live |access-date=31 Mar 2025 |website=Vox |archive-url=http://web.archive.org/web/20260107155933/https://www.vox.com/24141648/ai-ebook-grift-mushroom-foraging-mycological-society |archive-date=7 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Reference included more to represent what is intended --&amp;gt;&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Major media platforms with controversies relating to Generative AI==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Major media platforms with controversies relating to GenAI&lt;br /&gt;
!Platform&lt;br /&gt;
!Controversy&amp;lt;!-- The table is ordered by severity when it comes to the infringement of consumer rights, because I felt like racketeering from Microsoft didn&#039;t deserve to be buried under proprietary scraping allegations. --&amp;gt;&lt;br /&gt;
!Specifics&lt;br /&gt;
!Related Article(s)/Section(s)&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;GitHub&#039;&#039;&#039;&lt;br /&gt;
|Scraping all users&#039; public code repositories without prior notice nor consent for a large language model (&#039;&#039;&#039;GitHub CoPilot&#039;&#039;&#039;), then locking the ability to opt-out behind a subscription service&lt;br /&gt;
|Labeled on the FAQ for GitHub CoPilot,&amp;lt;ref&amp;gt;{{Cite web |last=CoPilot |title=FAQ |url=https://copilot.github.trust.page/faq?s=v2qe7voltpwtv2usl4ikhs#ip-and-open-source |access-date=Mar 30, 2025 |website=github |archive-url=http://web.archive.org/web/20260202024510/https://copilot.github.trust.page/faq?s=v2qe7voltpwtv2usl4ikhs |archive-date=2 Feb 2026}}&amp;lt;/ref&amp;gt; users who pay for either a &#039;&#039;Pro&#039;&#039; or &#039;&#039;Enterprise&#039;&#039; tier plan do not have their repositories (&#039;&#039;repos&#039;&#039;) scanned for the purposes of training CoPilot. There are theories that private repos may not be used for training purposes,{{Citation needed}} but these have not been verified{{CitationNeeded}}.&lt;br /&gt;
|[[GitHub]]&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;DeviantArt&#039;&#039;&#039;&lt;br /&gt;
|Training on all user-published content without prior notice nor consent for a proprietary image-generation model (&#039;&#039;&#039;DreamUp&#039;&#039;&#039;)&amp;lt;!-- Considering the over 2 year long history that continues to have new drama stir from this, we should look into eventually making a dedicated article focused on DreamUp --&amp;gt;&lt;br /&gt;
|While more speculative, it is reasonable for users to assume&amp;lt;ref&amp;gt;{{Cite web |title=What I think about DeviantArt&#039;s AI Choices |url=https://www.reddit.com/r/AI_Generator_Guide/comments/167sbit/what_i_think_about_deviantarts_ai_choices/ |url-status=dead |access-date=31 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20230917145828/https://old.reddit.com/r/AI_Generator_Guide/comments/167sbit/what_i_think_about_deviantarts_ai_choices/ |archive-date=17 Sep 2023}}&amp;lt;/ref&amp;gt; that when [[DeviantArt]] initially automatically opted all users into allowing their work to be training data for generative AI,&amp;lt;ref&amp;gt;{{Cite web |date=11 Nov 2022 |title=deviantart&#039;s AI art program (and how to opt out) |url=https://www.deviantart.com/izzy-paw/journal/deviantart-s-AI-art-program-and-how-to-opt-out-936581886 |url-status=live |access-date=31 Mar 2025 |website=Deviant Art |archive-url=http://web.archive.org/web/20251021011313/https://www.deviantart.com/izzy-paw/journal/deviantart-s-AI-art-program-and-how-to-opt-out-936581886 |archive-date=21 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Erdine |first=Önder |date=16 Nov 2022 |title=DeviantArt DreamUp is the latest contender for the AI art crown |url=https://en.digitalreport.com.tr/deviantart-dreamup-how-to-use-ai-opt-out/ |url-status=dead |access-date=31 Mar 2025 |website=Digital Report |archive-url=http://web.archive.org/web/20251018122736/https://en.digitalreport.com.tr/deviantart-dreamup-how-to-use-ai-opt-out/ |archive-date=18 Oct 2025}}&amp;lt;/ref&amp;gt; that all content uploaded to DeviantArt was used as training data for their DreamUp tool. However, according to statements from DeviantArt CEO Moti Levy,&amp;lt;ref&amp;gt;{{Cite web |last=Robertston |first=Adi |date=15 Nov 2022 |title=How DeviantArt is navigating the AI art minefield |url=https://www.theverge.com/2022/11/15/23449036/deviantart-ai-art-dreamup-training-data-controversy |url-status=live |access-date=31 Mar 2025 |website=The Verge |archive-url=http://web.archive.org/web/20251214011702/https://www.theverge.com/2022/11/15/23449036/deviantart-ai-art-dreamup-training-data-controversy |archive-date=14 Dec 2025}}&amp;lt;/ref&amp;gt; DeviantArt did not plan or intend to train their tool based on user-generated works, and that any user-generated works that were used in their model were introduced by StabilityAI&amp;lt;ref&amp;gt;{{Cite web |last=Team (DeviantArt Staff) |date=11 Nov 2022 |title=Create AI-Generated Art Fairly with DreamUp |url=https://www.deviantart.com/team/journal/Create-your-own-AI-generated-art-with-DreamUp-933537821 |access-date=25 Jan 2025 |website=DeviantArt |archive-url=http://web.archive.org/web/20250828110415/https://www.deviantart.com/team/journal/Create-your-own-AI-generated-art-with-DreamUp-933537821 |archive-date=28 Aug 2025}}&amp;lt;/ref&amp;gt;. Regardless, the introduction of DreamUp to the art sharing platform has stirred controversy on the platform&amp;lt;ref&amp;gt;{{Cite web |last=Edwards |first=Benj |date=11 Nov 2022 |title=DeviantArt upsets artists with its new AI art generator, DreamUp [Updated] |url=https://arstechnica.com/information-technology/2022/11/deviantart-upsets-artists-with-its-new-ai-art-generator-dreamup/ |url-status=live |access-date=31 Mar 2025 |website=www.arstechnica.com |archive-url=http://web.archive.org/web/20260108104735/https://arstechnica.com/information-technology/2022/11/deviantart-upsets-artists-with-its-new-ai-art-generator-dreamup/ |archive-date=8 Jan 2026}}&amp;lt;/ref&amp;gt; and fractured it into two distinct groups;&amp;lt;ref&amp;gt;{{Cite web |last=Duchess Celestia |date=13 Nov 2022 |title=DeviantART Just Betrayed Its Whole Community. (DreamUp AI Controversy) {{!}}{{!}} SPEEDPAINT + COMMENTARY |url=https://www.youtube.com/watch?v=IGj_3OhMrAU |url-status=live |access-date=31 Mar 2025 |website=[[YouTube]]}} ([https://preservetube.com/watch?v=IGj_3OhMrAU Archived])&amp;lt;/ref&amp;gt; those for generative AI (typically those who hold newer accounts) and those against the usage of such algorithms on an art forum (typically users who have existed on the platform for far longer.) Since the introduction of DreamUp, the platform has been cluttered with AI generated images, and staff have historically, frequently, and intentionally featured multiple users who exclusively upload GenAI content&amp;lt;ref&amp;gt;{{Cite web |date=22 Jul 2024 |title=DeviantArt Seller: StygianAI |url=https://www.deviantart.com/team/art/DeviantArt-Seller-StygianAI-1077776294 |access-date=31 Mar 2025 |website=Deviant Art |archive-url=http://web.archive.org/web/20260210073110/https://www.deviantart.com/team/art/DeviantArt-Seller-StygianAI-1077776294 |archive-date=10 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=9 Oct 2024 |title=Create on DeviantArt: VeilAI |url=https://www.deviantart.com/team/art/Create-on-DeviantArt-VeilAI-1108146133 |url-status=live |access-date=31 Mar 2025 |website=Deviant Art |archive-url=http://web.archive.org/web/20251114234046/https://www.deviantart.com/team/art/Create-on-DeviantArt-VeilAI-1108146133 |archive-date=14 Nov 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=15 Jul 2024 |title=DeviantArt Seller: ExeFelix |url=https://www.deviantart.com/team/art/DeviantArt-Seller-ExeFelix-1075192370 |url-status=live |access-date=31 Mar 2025 |website=Deviant Art |archive-url=http://web.archive.org/web/20251019011625/https://www.deviantart.com/team/art/DeviantArt-Seller-ExeFelix-1075192370 |archive-date=19 Oct 2025}}&amp;lt;/ref&amp;gt; or post content that uses generative content as a base.&amp;lt;ref&amp;gt;{{Cite web |date=9 Oct 2024 |title=Create on DeviantArt: AKoukis |url=https://www.deviantart.com/team/art/Create-on-DeviantArt-AKoukis-1108151629 |url-status=live |access-date=31 Mar 2025 |website=Deviant Art |archive-url=http://web.archive.org/web/20250708132009/https://www.deviantart.com/team/art/Create-on-DeviantArt-AKoukis-1108151629 |archive-date=8 Jul 2025}}&amp;lt;/ref&amp;gt; The majority of featured creators on the site are ones who excessively or exclusively upload AI generated content.&amp;lt;!-- I was scrolling through their gallery and most featured artist posts were about AI creators, I stopped my search when I reached posts that released before the generative AI controversies on the platform occurred, which had a rough stopping point of around Q4 2022.&lt;br /&gt;
https://www.deviantart.com/team/gallery --&amp;gt;&amp;lt;!-- Due to my close familiarity with the situation, yes, I developed this section a lot more than initially planned. --&amp;gt;&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Twitter/X&#039;&#039;&#039;&lt;br /&gt;
|Training on all active users&#039; data without prior notice nor explicit consent for a proprietary large language and image generation model (&#039;&#039;&#039;Grok&#039;&#039;&#039;); leaking over 370,000 private chats with Grok over Google search results without prior notice nor user consent&lt;br /&gt;
|Sometime in mid 2024, [[X Corp]]&#039;s platform of the same moniker quietly changed its Terms of Service to allow all user-generated content submitted through it to be used to &amp;quot;Train artificial intelligence models, whether generative or another type&amp;quot;, specifically with a permanent license for said content granted to the corporation and without any form of monetary compensation.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |date=2026-01-05 |title=X Terms of Service |url=https://x.com/en/tos#:~:text=You%20agree%20that%20this%20license%20includes%20the%20right%20for%20us%20to%20%28i%29%20analyze%20text%20and%20other%20information%20you%20provide%20and%20to%20otherwise%20provide%2C%20promote%2C%20and%20improve%20the%20Services%2C%20including%2C%20for%20example%2C%20for%20use%20with%20and%20training%20of%20our%20machine%20learning%20and%20artificial%20intelligence%20models%2C%20whether%20generative%20or%20another%20type%3B%20and%20%28ii%29%20to%20make%20Content%20submitted%20to%20or%20through%20the%20Services%20available%20to%20other%20companies%2C%20organizations%20or%20individuals%2C%20including%2C%20for%20example%2C%20for%20improving%20the%20Services%20and%20the%20syndication%2C%20broadcast%2C%20distribution%2C%20repost%2C%20promotion%20or%20publication%20of%20such%20Content%20on%20other%20media%20and%20services%2C%20subject%20to%20our%20terms%20and%20conditions%20for%20such%20Content%20use%2E%20Such%20additional%20uses%20by%20us%2C%20or%20other%20companies%2C%20organizations%20or%20individuals%2C%20is%20made%20with%20no%20compensation%20paid%20to%20you%20with%20respect%20to%20the%20Content%20that%20you%20submit%2C%20post%2C%20transmit%20or%20otherwise%20make%20available%20through%20the%20Services%20as%20the%20use%20of%20the%20Services%20by%20you%20is%20hereby%20agreed%20as%20being%20sufficient%20compensation%20for%20the%20Content%20and%20grant%20of%20rights%20herein%2E |access-date=2026-01-05 |website=X |archive-url=http://web.archive.org/web/20260220081214/https://x.com/en/tos |archive-date=20 Feb 2026}}&amp;lt;/ref&amp;gt; Though there remains an option to opt-out in the platform&#039;s privacy settings, users were opted-in by default.&amp;lt;ref&amp;gt;{{Cite web |last=Cohen |first=Jason |date=2025-08-08 |title=Your Posts On X Are Being Used To Train Grok AI. Here&#039;s How To Stop It |url=https://www.pcmag.com/how-to/your-tweets-x-posts-train-elon-musk-grok-ai-how-to-stop-it-opt-out |url-status=live |archive-url=https://web.archive.org/web/20251103053227/https://www.pcmag.com/how-to/your-tweets-x-posts-train-elon-musk-grok-ai-how-to-stop-it-opt-out |archive-date=2025-11-03 |access-date=2026-01-05 |website=PC Magazine}}&amp;lt;/ref&amp;gt; The following is speculative, as X Corp and sister corporation xAI have been almost entirely silent about the specifics of their methodology, but it&#039;s reasonable to assume that all users&#039; available Content (as defined in the platform&#039;s Terms of Service)&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; was scraped and introduced to xAI (and possibly other third-parties&#039;) datasets when the change was established. In addition, users&#039; private conversations with the chatbot, which are shared through saved links, were/are accessible to search engines like Google and showed up for the first time in publicly accessible search results in August 2025.&amp;lt;ref&amp;gt;{{Cite web |last=Martin |first=Iain |date=2025-08-20 |title=Elon Musk’s xAI Published Hundreds Of Thousands Of Grok Chatbot Conversations |url=https://www.forbes.com/sites/iainmartin/2025/08/20/elon-musks-xai-published-hundreds-of-thousands-of-grok-chatbot-conversations/ |url-status=live |archive-url=https://web.archive.org/web/20250820105050/https://www.forbes.com/sites/iainmartin/2025/08/20/elon-musks-xai-published-hundreds-of-thousands-of-grok-chatbot-conversations/ |archive-date=2025-08-20 |access-date=2026-01-05 |website=Forbes}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|[[X Corp]]&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Stack Overflow&#039;&#039;&#039;&lt;br /&gt;
|Training on all active users&#039; content without prior notice nor explicit consent for a large language model service (&#039;&#039;&#039;Overflow AI&#039;&#039;&#039;)&lt;br /&gt;
|In late July of 2023, Overflow AI was made available by Stack Overflow, a Q&amp;amp;A forum for programmers. The information used to train the LLMs provided by the service was taken from questions and answers left by the StackOverflow community.&amp;lt;ref&amp;gt;{{Cite news |last=StackOverflow |date=Jul 27, 2023 |title=Announcing OverflowAI |url=https://stackoverflow.blog/2023/07/27/announcing-overflowai/ |access-date=Mar 30, 2025 |work=StackOverflow blog |archive-url=http://web.archive.org/web/20251221210340/https://stackoverflow.blog/2023/07/27/announcing-overflowai/ |archive-date=21 Dec 2025}}&amp;lt;/ref&amp;gt; This action subverts one of the website&#039;s existing policies, wherein its users are disallowed from AI generating responses to answer forum posts.&amp;lt;ref&amp;gt;{{Cite web |last=StackOverflow |title=Generative AI Policy |url=https://stackoverflow.com/help/gen-ai-policy |access-date=Mar 30, 2025 |website=StackOverflow help center |archive-url=http://web.archive.org/web/20250926063840/https://stackoverflow.com/help/gen-ai-policy |archive-date=26 Sep 2025}}&amp;lt;/ref&amp;gt; The only way users might have the capability to opt-out currently would be to manually delete all posts and topics before deleting their account. The effectiveness of this method remains questionable, however, considering that StackOverflow&#039;s &amp;quot;Get Out&amp;quot; clause&amp;lt;ref&amp;gt;{{Cite web |last=StackOverflow |title=How do I delete all my contributions? |url=https://stackoverflow.com/help/delete-content |access-date=Mar 30, 2025 |website=StackOverflow help center |archive-url=http://web.archive.org/web/20260131203918/https://stackoverflow.com/help/delete-content |archive-date=31 Jan 2026}}&amp;lt;/ref&amp;gt; may allow the service to retrieve content that was previously deleted.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Reddit&#039;&#039;&#039;&lt;br /&gt;
|Training on all users&#039; content without prior notice nor explicit consent for a large language model (&#039;&#039;&#039;Reddit Answers&#039;&#039;&#039;)&lt;br /&gt;
|In late 2024, [[Reddit]] announced the release of &#039;Reddit Answers,&#039; a large language model (LLM) that was publicly stated&amp;lt;ref&amp;gt;{{Cite web |title=Reddit Answers (Currently in Beta) |url=https://support.reddithelp.com/hc/en-us/articles/32026729424916-Reddit-Answers-Currently-in-Beta |url-status=live |access-date=31 Mar 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20260129070028/https://support.reddithelp.com/hc/en-us/articles/32026729424916-Reddit-Answers-Currently-in-Beta |archive-date=29 Jan 2026}}&amp;lt;/ref&amp;gt; to use content created by users to train the tool, without requiring prior consent or prior public notice. Reddit&#039;s Terms of Service explicitly allows the platform to scrape user-generated content for the purpose of training &amp;quot;AI and machine learning models&amp;quot;,&amp;lt;ref&amp;gt;{{Cite web |first= |date=May 29, 2025 |title=User Agreement |url=https://redditinc.com/policies/user-agreement |url-status=live |archive-url=https://web.archive.org/web/20260101023854/https://redditinc.com/policies/user-agreement |archive-date=2026-01-01 |access-date=2026-01-05 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt; though this is likely limited to Reddit&#039;s proprietary dataset; it has legally discouraged third-party services from scraping the platform as per the Reddit Public Content Policy.&amp;lt;ref&amp;gt;{{Cite web |date= |title=Public Content Policy |url=https://support.reddithelp.com/hc/en-us/articles/26410290525844-Public-Content-Policy |url-status=live |archive-url=https://web.archive.org/web/20251230012504/https://support.reddithelp.com/hc/en-us/articles/26410290525844-Public-Content-Policy |archive-date=30 Dec 2025 |access-date=2026-01-05 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|[[Reddit]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Other controversies involving generative AI==&lt;br /&gt;
&lt;br /&gt;
===LAION-5b training database===&lt;br /&gt;
Many users have had their content scraped by LAION to power their training database. Currently, there is no way to opt-out or request a removal of one&#039;s content from it or any successor database, as the service which previously allowed individuals to request the removal of their data is defunct.&amp;lt;ref&amp;gt;[https://haveibeentrained.com/ Have I Been Trained?] ([http://web.archive.org/web/20260128021446/https://haveibeentrained.com/ Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Copyright]]&lt;br /&gt;
[[Category:Artificial intelligence|*]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Claude&amp;diff=54706</id>
		<title>Claude</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Claude&amp;diff=54706"/>
		<updated>2026-05-24T22:16:26Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Anthropic&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|ReleaseYear=2023&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Software, Artificial Intelligence, Generative AI, Large Language Models&lt;br /&gt;
|Website=https://claude.ai/&lt;br /&gt;
|Description=American language model developed by Anthropic that will ask for identity verification for new accounts or accessing advanced features. Identity verifications are provided by Persona.&lt;br /&gt;
|Logo=Claude AI logo.svg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Claude&#039;&#039;&#039; is a generative artificial intelligence, a large language model (LLM) developed and released by [[Anthropic]]. It was created with the objective of being a safe AI for the public. Claude family includes Haiku, a fast and cheaper model, Sonnet, a more complex model capable of completing more complex tasks, and Opus, their most advanced model.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
===Business model===&lt;br /&gt;
Free tier users have a limited access to only one version of the LLM. The LLM token limit ends after generating some messages, but the platform doesn&#039;t specify how much tokens or credits are left. Some experimental or advanced features of Claude can be very limited for free users or is just paywalled.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
===Third-party usage===&lt;br /&gt;
Anthropic provides two ways of accessing their LLMs: subscriptions and direct API usage. API pricing is simple: you pay for what you use. By paying for a subscription you can get up to 13.5x worth of API usage — a &amp;quot;Max&amp;quot; subscription costs $200 per month but allows users to use up to $3,000 worth of actual API costs [[https://she-llac.com/claude-limits source]]. However paying for a subscription means user is locked into Anthropic&#039;s tools only — either their web app or desktop app (Claude Code). Several talented engineers managed to hijack the behavior of Anthropic&#039;s tools and hence use limits of their subscriptions in third-party tools. Anthropic responded by changing their policies and banning any suspicions of account subscriptions being used outside of their first-party applications.&amp;lt;ref&amp;gt;{{Cite web |last=Zolkos |first=Rob |title=Rob Zolkos on X |url=https://x.com/robzolkos/status/2024125323755884919 |website=[[X]] |date=18 Feb 2026 |access-date=22 Apr 2026 |url-status=live |archive-url=https://megalodon.jp/2026-0423-0816-27/https://x.com:443/robzolkos/status/2024125323755884919 |archive-date=23 Apr 2026}}&amp;lt;/ref&amp;gt; Several users on [[X]] complained about being banned even without ever taking part in such activities, namely those who have used multiple accounts with named subscription on the same computer.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
====DMCA====&lt;br /&gt;
Anthropic&#039;s most popular product, Claude Code, is closed-source, meaning the actual code used to make the application is not public. Additionally the distributed version of said application is obfuscated. Obfuscation is a common process used in order to make reading code more difficult, essentially impossible without the use of reverse-engineering tools. In 2025 Anthropic accidentally published &amp;quot;source maps&amp;quot; of the application, aiding in mapping the obfuscated code to its original form. Some developers posted said information online, to which Anthropic responded with [[DMCA]] claims.&amp;lt;ref&amp;gt;{{Cite web |last=Wiggers |first=Kyle |title=Anthropic sent a takedown notice to a dev trying to reverse-engineer its coding tool |url=https://techcrunch.com/2025/04/25/anthropic-sent-a-takedown-notice-to-a-dev-trying-to-reverse-engineer-its-coding-tool/ |website=TechCrunch |date=25 Apr 2025 |access-date=22 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250425220915/https://techcrunch.com/2025/04/25/anthropic-sent-a-takedown-notice-to-a-dev-trying-to-reverse-engineer-its-coding-tool/ |archive-date=25 Apr 2025}}&amp;lt;/ref&amp;gt; [[GitHub]], a platform for sharing code, keeps a [https://github.com/github/dmca track of DMCA claims] and makes them public.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Code search results |url=https://github.com/search?q=repo%3Agithub%2Fdmca%20anthropic&amp;amp;type=code |url-access=registration |website=[[GitHub]]&lt;br /&gt;
|date=&lt;br /&gt;
|access-date=&lt;br /&gt;
|url-status=live&lt;br /&gt;
|archive-url=&lt;br /&gt;
|archive-date=&lt;br /&gt;
}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Requires account and I&#039;m not making one for this. If someone else does have one, please fill out what you can. -Sojourna --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Privacy====&lt;br /&gt;
In order to use the LLM, a person must sign in with an e-mail address or to log in with a [[Google]] account, as well as obligatorily verify a smartphone number.&amp;lt;ref&amp;gt;{{Cite web |author=&lt;br /&gt;
|title=Verifying your phone number {{!}} Claude Help Center |url=https://support.claude.com/en/articles/8287232-verifying-your-phone-number |website=Claude |date=24 Mar 2026 |access-date=24 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260408203422/https://support.claude.com/en/articles/8287232-verifying-your-phone-number |archive-date=8 Apr 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Anthropic may use input and output data from their services to train their AI models. Users are able to opt-out if they want to. However, Anthropic may still collect inputs and outputs that belong to conversations that have been flagged for safety review or content that has been reported by the user.&amp;lt;ref&amp;gt;{{Cite web |author= |title=Privacy Policy |url=https://www.anthropic.com/legal/privacy |website=[[Anthropic]] |date=20 Mar 2023 |access-date=27 Jan 2026 |url-status=live |archive-url=http://web.archive.org/web/20260211053754/https://www.anthropic.com/legal/privacy |archive-date=11 Feb 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer-protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===ID verification for newer accounts and access of advanced features (&#039;&#039;April 2026&#039;&#039;)===&lt;br /&gt;
In April 2026, Anthropic announced they would implement identity verification that are done by the third-party provider [[Persona]] &amp;quot;for a few use cases&amp;quot; to access to advanced features and to verify new accounts created. The reason given was to &amp;quot;prevent abuse, enforce our usage policies and comply with legal obligations&amp;quot; (at a moment there&#039;s no currently known legislation in the US or any country that enforces AI companies to ask for identity verification). The purpose for the ID verification is &amp;quot;to confirm who you are and not for any other purposes&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |author=Pirat_Nation |title=Pirat_Nation on X |url=https://x.com/Pirat_Nation/status/2044960285510053929 |website=[[X]] |date=16 Apr 2026 |access-date=22 Apr 2026 |url-status=live |archive-url=https://megalodon.jp/2026-0423-0855-24/https://x.com:443/Pirat_Nation/status/2044960285510053929 |archive-date=23 Apr 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Tests for removing Claude Code features from Pro subscription tier (&#039;&#039;April 2026&#039;&#039;)===&lt;br /&gt;
In April 2026, users reported on social media that the Claude pricing page shows that Claude Code is not supported in the Pro subscription tier. After the reports from users, Anthropic replied that this was caused by a modification done for testing purposes, affecting 2% of the users visiting the site.&amp;lt;ref&amp;gt;{{Cite web |last=Axon |first=Samuel |title=Anthropic tested removing Claude Code from the Pro plan |url=https://arstechnica.com/ai/2026/04/anthropic-tested-removing-claude-code-from-the-pro-plan/ |website=Ars Technica |date=22 Apr 2026 |access-date=22 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260422235948/https://arstechnica.com/ai/2026/04/anthropic-tested-removing-claude-code-from-the-pro-plan/ |archive-date=22 Apr 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[OpenAI]]&lt;br /&gt;
*[[Artificial intelligence]]&lt;br /&gt;
*[[ChatGPT]]&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>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=ChatGPT&amp;diff=54705</id>
		<title>ChatGPT</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=ChatGPT&amp;diff=54705"/>
		<updated>2026-05-24T22:15:53Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ProductCargo&lt;br /&gt;
|Company=OpenAI&lt;br /&gt;
|ProductLine=&lt;br /&gt;
|ReleaseYear=2022&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Software, Artificial Intelligence, Generative AI, Large Language Models&lt;br /&gt;
|Website=https://chatgpt.com/&lt;br /&gt;
|Description=ChatGPT data has been mishandled in the past, and is worsening with court-ordered data retention and integrated advertising.&lt;br /&gt;
|Logo=OpenAI logo (symbol).svg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ChatGPT&#039;&#039;&#039; (Chat Generative Pre-trained Transformer) is a generative artificial intelligence application developed and marketed by [[OpenAI]]. It was released on November 30th, 2022.&amp;lt;ref&amp;gt;{{Cite web |date=2022-11-30 |title=Introducing ChatGPT |url=https://openai.com/index/chatgpt/ |url-status=live |archive-url=http://web.archive.org/web/20260219054935/https://openai.com/index/chatgpt/ |archive-date=19 Feb 2026|access-date=2026-01-26 |website=OpenAI}}&amp;lt;/ref&amp;gt; It is a large language model (LLM) specialized in dialog that can perform human-like conversations. Various iterations of ChatGPT include GPT-3, GPT-4, GPT-4o, and previews of OpenAI-o1, OpenAI-o1 mini and GPT-5.&amp;lt;ref&amp;gt;{{Cite web |date=2025-07-09 |title=ChatGPT version history: Evolution timeline |url=https://nexos.ai/blog/chatgpt-version-history/ |url-status=live |archive-url=http://web.archive.org/web/20260217071448/https://nexos.ai/blog/chatgpt-version-history/ |archive-date=17 Feb 2026|access-date=2026-01-26 |website=nexos.ai}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Hayat |first=Usman |date=2025-08-22 |title=ChatGPT Version History List, Changelog &amp;amp; Latest Releases |url=https://wpexperts.io/blog/chatgpt-version-history/ |url-status=live |archive-url=http://web.archive.org/web/20251023153623/https://wpexperts.io/blog/chatgpt-version-history/ |archive-date=23 Oct 2025|access-date=2026-01-26 |website=WPExperts.io}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
===User freedom===&lt;br /&gt;
Users who are not logged in can use ChatGPT, but their access is limited (for example, they can only have one conversation at a time and cannot save chat history).&amp;lt;ref&amp;gt;{{Cite web |title=The ChatGPT home page |url=https://help.openai.com/en/articles/9125172-the-chatgpt-home-page |url-status=live |access-date=2026-02-19 |website=OpenAI Help Center |archive-url=http://web.archive.org/web/20260214024602/https://help.openai.com/en/articles/9125172-the-chatgpt-home-page |archive-date=14 Feb 2026}}&amp;lt;/ref&amp;gt; After GPT-5’s release, manual model selection is not available to all users: OpenAI limits the ChatGPT “model picker” to paid tiers, while other users may be routed automatically (e.g., via “Auto,” which can switch between model variants).&amp;lt;ref&amp;gt;{{Cite web |title=Model Release Notes |url=https://help.openai.com/en/articles/9624314-model-release-notes |website=OpenAI Help Center |access-date=2026-02-19 |archive-url=http://web.archive.org/web/20251230143058/https://help.openai.com/en/articles/9624314-model-release-notes |archive-date=30 Dec 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=ChatGPT Enterprise and Edu - Models &amp;amp; Limits |url=https://help.openai.com/en/articles/11165333-chatgpt-enterprise-and-edu-models-limits |website=OpenAI Help Center |access-date=2026-02-19 |archive-url=http://web.archive.org/web/20251211113140/https://help.openai.com/en/articles/11165333-chatgpt-enterprise-and-edu-models-limits |archive-date=11 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
A mobile phone number in a friendly country is required to better track your identity.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
====Data policy====&lt;br /&gt;
From OpenAI&#039;s data usage policy:&amp;lt;ref&amp;gt;{{Cite web |title=Data Usage for Consumer Services FAQ {{!}} OpenAI Help Center |url=https://help.openai.com/en/articles/7039943-data-usage-for-consumer-services-faq |url-status=live |archive-url=http://web.archive.org/web/20260210234712/https://help.openai.com/en/articles/7039943-data-usage-for-consumer-services-faq |archive-date=2026-02-10 |access-date=2026-01-27}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
{{Quote|We share content with a select group of trusted service providers that help us provide our services. We share the minimum amount of content we need in order to accomplish this purpose and our service providers are subject to strict confidentiality and security obligations. We do not use or share user content for marketing or advertising purposes.}}&lt;br /&gt;
The wording does not detail the extent of conversations shared with OpenAI&#039;s trusted service providers.&amp;lt;!-- (still) Placeholder. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Misleading advertising====&lt;br /&gt;
ChatGPT terms of service say it should not be used to make decisions about people.&amp;lt;ref&amp;gt;{{Cite web |title=Terms of Use {{!}} OpenAI |url=https://openai.com/policies/terms-of-use/ |url-status=live |archive-url=http://web.archive.org/web/20260123055141/https://openai.com/policies/terms-of-use/ |archive-date=2026-01-23 |access-date=2026-01-27}}&amp;lt;/ref&amp;gt; However, their advertising claims it is &amp;quot;PhD level&amp;quot; and makes other claims that seem to imply it is reliable. Many people use ChatGPT as if its output were meaningful, reliable, or a substitute for interaction with a person, with some cases involving &amp;quot;relationships&amp;quot; with the AI. [[ChatGPT-4o]] was one of their models known for inducing a lot of vulnerable users into AI psychosis.&lt;br /&gt;
&lt;br /&gt;
===Billing and moderation===&lt;br /&gt;
Credits (money) expire automatically with no notification, and the credit balance interface makes this process confusing. You must maintain a positive account balance, and you are auto-billed a fixed amount if it goes negative. The interface of users from the United States that have no subscription (Free tier) or are in the Go subscription tier shows integrated ads that appear inside the chats.&lt;br /&gt;
Accounts can be banned and credits confiscated for typing the wrong things in chat, with no recourse.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
===Market control===&lt;br /&gt;
Global market share data shows ChatGPT is the most used chatbot in the world (79.98% as of February 2026)&amp;lt;ref&amp;gt;{{Cite web |publisher=StatCounter |date=Feb 2026 |title=AI Chatbot Market Share Worldwide |url=https://gs.statcounter.com/ai-chatbot-market-share |url-status=live |archive-url=https://archive.is/stjr5 |archive-date=2026-03-09 |access-date=9 Mar 2026 |website=statcounter.com}}&amp;lt;/ref&amp;gt;. However, adoption has been declined since 2025 due to recent incidents, controversial decisions and comparable competitors, such as [[Google Gemini]] and [[Claude]]. &amp;lt;ref&amp;gt;{{Cite web |last=Nolan |first=Beatrice |date=5 Feb 2026 |title=ChatGPT’s market share is slipping as Google and rivals close the gap, app-tracker data shows |url=https://finance.yahoo.com/news/chatgpt-market-share-slipping-google-155419736.html |url-status=live |access-date=9 Mar 2026 |website=Yahoo Finance}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===Security breach (&#039;&#039;2023&#039;&#039;)===&lt;br /&gt;
On March 20, 2023 a bug allowed some users to see other users&#039; conversation titles. Sam Altman, OpenAI&#039;s CEO, stated users couldn&#039;t view other users&#039; conversation content. After the bug was fixed, users reported they were unable to view their conversation history. Later reports showed this issue was much bigger than it was thought at first, with OpenAI reporting there were leaks of the users&#039; name, last name, e-mail address, payment address, and partial credit card information.&amp;lt;ref&amp;gt;{{Cite web |last=Simo |first=Fidgi |date=20 March 2023 |title=March 20 ChatGPT outage: Here’s what happened |url=https://openai.com/index/march-20-chatgpt-outage/ |url-status=live |archive-url=http://web.archive.org/web/20260210072430/https://openai.com/index/march-20-chatgpt-outage/ |archive-date=10 Feb 2026|access-date=26 Jan 2026 |website=OpenAI}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===ChatGPT-4o (&#039;&#039;2024—2026&#039;&#039;)===&lt;br /&gt;
{{Main|ChatGPT-4o}}&lt;br /&gt;
&lt;br /&gt;
On May 13, 2024, OpenAI announced and released the model ChatGPT-4o.&amp;lt;ref&amp;gt;{{Cite web |author=OpenAI |date=13 May 2024 |title=Hello, GPT-4o |url=https://openai.com/es-ES/index/hello-gpt-4o/ |url-status=live |archive-url=http://web.archive.org/web/20251216045649/https://openai.com/es-ES/index/hello-gpt-4o/ |archive-date=16 Dec 2025|access-date=2026-02-17 |website=OpenAI}}&amp;lt;/ref&amp;gt; The model was temporarily retired from the public in April 2025 due to an update that caused the model to have excessive sycophancy. &amp;lt;ref&amp;gt;{{Cite web |last=Franzen |first=Carl |date=30 Apr 2025 |title=OpenAI rolls back ChatGPT&#039;s sycophancy and explains what went wrong |url=https://venturebeat.com/ai/openai-rolls-back-chatgpts-sycophancy-and-explains-what-went-wrong |url-status=live |archive-url=http://web.archive.org/web/20250815154215/https://venturebeat.com/ai/openai-rolls-back-chatgpts-sycophancy-and-explains-what-went-wrong/ |archive-date=15 Aug 2025|access-date=15 Feb 2026 |website=VentureBeat}}&amp;lt;/ref&amp;gt;It also had several controversies because of users developing [[wikipedia:Chatbot_psychosis|AI psychosis]], with some severe cases ending with users committing suicide. &amp;lt;ref&amp;gt;{{Cite web |last=Hill |first=Kashmir |date=13 Jun 2025 |url=https://www.nytimes.com/2025/06/13/technology/chatgpt-ai-chatbots-conspiracies.html|title=They Asked an A.I. Chatbot Questions. The Answers Sent Them Spiraling. |url-status=live |archive-url=http://web.archive.org/web/20260117185232/https://www.nytimes.com/2025/06/13/technology/chatgpt-ai-chatbots-conspiracies.html |archive-date=17 Jan 2026|access-date=2025-02-15 |website=The New York Times}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
With the launch of GPT-5 in August 2025, OpenAI removed legacy models from non-API users, such as GPT-4o. This decision caused an outrage, with users complaining about the removal of the models along with the complaints about GPT-5. OpenAI&#039;s response was to end paywalling these older models, making them available only for Plus users. &lt;br /&gt;
In 2026, OpenAI announced they will be removing definitely GPT-4o and other models, such as GPT-5 and GPT-4.1. On February 13, 2026, 4o and other legacy models were removed for non-API users, causing again controversies in social media. These legacy models will be removed for API-users on April 2026. {{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
===Users&#039; data retention by court mandate (&#039;&#039;May 2025—October 2025&#039;&#039;)===&lt;br /&gt;
On May 13, 2025, New York Times filed a lawsuit against OpenAI and Microsoft for copyright infringement. A court in New York mandated OpenAI to preserve users&#039; conversation logs, including data from deleted conversations and temporary conversations. This affected Free, Plus, Pro and Team subscription tiers and also non Zero-Data-Retention API users. Edu, Enterprise tiers and Zero-Data-Retention API users were exempt from this.&amp;lt;ref&amp;gt;{{Cite web |last=Bradbury |first=Danny |date=6 Jun 2025 |title=OpenAI forced to preserve ChatGPT chats |url=https://www.malwarebytes.com/blog/news/2025/06/openai-forced-to-preserve-chatgpt-chats |url-status=live |archive-url=http://web.archive.org/web/20251114012548/https://www.malwarebytes.com/blog/news/2025/06/openai-forced-to-preserve-chatgpt-chats |archive-date=14 Nov 2025|access-date=26 Jan 2026 |website=Malwarebytes}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=R |first=Sudha |date=15 Jul 2025 |title=ChatGPT To Retain Conversations Indefinitely |url=https://medium.com/aimonks/court-orders-openai-to-retain-chatgpt-conversations-indefinitely-what-you-need-to-know-1530f24501a6 |url-status=live |archive-url= |archive-date= |access-date=26 Jan 2026 |website=Medium}}&amp;lt;/ref&amp;gt; &amp;lt;!-- &amp;lt; The medium article, archive.today is stuck loading. https://archive.is/wip/Zyy1e. I don&#039;t feel like resetting my IA password atm. Just a note to future citers. -raster --&amp;gt; On September 26, 2025, the preservation order was revoked. However, some deleted and temporary chats will still be monitored for being flagged.&amp;lt;ref&amp;gt;{{Cite web |last=Belanger |first=Ashley |date=10 Oct 2025 |title=OpenAI will stop saving most ChatGPT users’ deleted chats |url=https://arstechnica.com/tech-policy/2025/10/openai-no-longer-forced-to-save-deleted-chats-but-some-users-still-affected/ |url-status=live |archive-url=http://web.archive.org/web/20260101145932/https://arstechnica.com/tech-policy/2025/10/openai-no-longer-forced-to-save-deleted-chats-but-some-users-still-affected/ |archive-date=1 Jan 2026|access-date=26 Jan 2026 |website=Ars Technica}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GPT-5 release (&#039;&#039;August 2025&#039;&#039;)===&lt;br /&gt;
On August 7, 2025, OpenAI released their newest model, GPT-5. The next day, several users complained in social media about the performance of the model, claiming it was underwhelming and was &amp;quot;dumber&amp;quot; than the previous model. Users also realised OpenAI&#039;s platform was most of the time setting the lowest-performance GPT-5 models and discovered they can make the platform to set the better-performance models by adding &amp;quot;think harder&amp;quot; in prompts. Sam Altman claimed that a &amp;quot;malfunction&amp;quot; of the autoswitcher was the reason behind GPT-5 performance.&lt;br /&gt;
&amp;lt;ref&amp;gt;{{Cite web |last=Edwards |first=Benj |date=11 Aug 2025 |title=The GPT-5 rollout has been a big mess |url=https://arstechnica.com/information-technology/2025/08/the-gpt-5-rollout-has-been-a-big-mess/ |url-status=live |archive-url=http://web.archive.org/web/20260109001515/https://arstechnica.com/information-technology/2025/08/the-gpt-5-rollout-has-been-a-big-mess/ |archive-date=9 Jan 2026|access-date=5 Feb 2026 |website=Ars Technica}}&amp;lt;/ref&amp;gt; &amp;lt;ref&amp;gt;{{Cite web |last=Franzen |first=Carl |date=8 Aug 2025 |title=OpenAI returns old models to ChatGPT as Sam Altman admits ‘bumpy’ GPT-5 rollout |url=https://venturebeat.com/business/openai-returns-old-models-to-chatgpt-as-sam-altman-admits-bumpy-gpt-5-rollout |url-status=live |archive-url=https://archive.is/hunUK |archive-date=2026-02-05 |access-date=5 Feb 2026 |website=VentureBeat}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===Age verification (&#039;&#039;2026&#039;&#039;)===&lt;br /&gt;
With a justification to &amp;quot;help teens have an age-appropriate experience on ChatGPT&amp;quot;, the platform will be implementing globally an [[age verification]] system to detect if a user is over 18 to allow them to access to mature content. OpenAI will scan and analyze the user&#039;s account, their conversations and their behavior - including the times of a day they use ChatGPT - to estimate their age. If this system detects a user as underage, it will use third-party tools provided by [[Persona]] to estimate their age, asking the user to upload a selfie or their government ID. If the user refuses to send a selfie or their ID, the platform will limit ChatGPT&#039;s generated content.&amp;lt;ref&amp;gt;{{Cite web |date=21 Jan 2026 |title=Age prediction in ChatGPT |url=https://help.openai.com/en/articles/12652064-age-prediction-in-chatgpt |url-status=live |archive-url=http://web.archive.org/web/20260119032400/https://help.openai.com/en/articles/12652064-age-prediction-in-chatgpt |archive-date=19 Jan 2026|access-date=26 Jan 2026 |website=OpenAI}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Integrated ads (&#039;&#039;February 2026&#039;&#039;)===&lt;br /&gt;
On January 16, 2026, OpenAI announced that they will be implementing ads for &amp;quot;testing purposes&amp;quot;. &amp;lt;ref&amp;gt;{{Cite web |last=Simo |first=Fidgi |date=16 Jan 2026 |title=Our approach to advertising and expanding access to ChatGPT |url=https://openai.com/index/our-approach-to-advertising-and-expanding-access/ |url-status=live |archive-url=http://web.archive.org/web/20260118192220/https://openai.com/index/our-approach-to-advertising-and-expanding-access/ |archive-date=18 Jan 2026|access-date=25 Jan 2026 |website=OpenAI}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Cirello |first=Rafaelle F |last2=Backholer |first2=Kathryn |date=23 Jan 2026 |title=OpenAI will put ads in ChatGPT. This opens a new door for dangerous influence |url=https://theconversation.com/openai-will-put-ads-in-chatgpt-this-opens-a-new-door-for-dangerous-influence-273806 |url-status=live |archive-url=http://web.archive.org/web/20260125175609/https://theconversation.com/openai-will-put-ads-in-chatgpt-this-opens-a-new-door-for-dangerous-influence-273806 |archive-date=25 Jan 2026|access-date=26 Jan 2026}}&amp;lt;/ref&amp;gt; On February 9, 2026, ads rolled out, affecting users over 18 from the US who are in Free and Go subscription tiers. Pro, Business and Enterprise tiers are exempt from this. These ads are [[Personalized ads|personalized ads]] that appear at the bottom of ChatGPT&#039;s messages, showing the sponsored site name next to a &amp;quot;Sponsored&amp;quot; text, and below it, links to the sponsored site. OpenAI stated the ads that appear are based on current conversations, ads that user has engaged with, and past chats and ChatGPT&#039;s memories. OpenAI also claims the data provided to show ads &amp;quot;it&#039;s not shared with advertisers&amp;quot;. It is possible to opt-out for getting personalized ads and delete ads data. &amp;lt;!-- (If you&#039;re from the US and have access to ads in ChatGPT please check if personalized ads is active by default and if something from here is wrong. If so, please add that info on this entry) --&amp;gt;  &amp;lt;ref&amp;gt;https://x.com/OpenAI/status/2020936703763153010 - Archived: https://megalodon.jp/2026-0304-0444-55/https://x.com:443/OpenAI/status/2020936703763153010&amp;lt;/ref&amp;gt; The announcement and release of this patch has raised several concerns about privacy &amp;lt;ref&amp;gt;{{Cite web |last=Werthmuller |first=Digby |date=1 Mar 2026 |title=Privacy fears as OpenAI trials ads in its ChatGPT chatbot in the US |url=https://www.abc.net.au/news/2026-03-02/open-ai-testing-ads-in-chatgpt-in-us-plans-to-rollout-globally/106377798 |url-status=live |archive-url=https://archive.is/OEdhY |archive-date=2026-03-02 |access-date=3 Mar 2026 |website=ABC.net}}&amp;lt;/ref&amp;gt;, data usage, ad experience potentially becoming worse &amp;lt;ref&amp;gt;{{Cite web |last=Serazio |first=Michael |date=3 Mar 2026 |title=AI Is Going to Revolutionize Advertising in the Worst Imaginable Way |url=https://newrepublic.com/article/207106/chatgpt-ads-open-ai-revolutionize-advertising-worst-imaginable-way |url-status=live |archive-url=https://archive.is/w2bJw |archive-date=2026-03-03 |access-date=3 Mar 2026 |website=The New Republic}}&amp;lt;/ref&amp;gt;, and the AI usage to manipulate users. After the ad release in the US, users have experienced that ads can appear on a new conversation by just sending the first prompt, something that was considered as aggresive advertising. &amp;lt;ref&amp;gt;{{Cite web |last=Adegbola |first=Anu |date=19 Feb 2026 |title=ChatGPT ads spotted and they are quite aggressive |url=https://searchengineland.com/chatgpt-ads-spotted-and-they-are-quite-aggressive-469651 |url-status=live |archive-url=https://archive.is/V5bRc |archive-date=2026-03-03 |access-date=3 Mar 2026 |website=Search Engine Land}}&amp;lt;/ref&amp;gt; &amp;lt;ref&amp;gt;{{Cite web |last=Kasanmascheff |first=Markus|date=21 Feb 2026 |title=ChatGPT Ads Now Hit on Your Very First Message |url=https://winbuzzer.com/2026/02/21/chatgpt-ads-now-appearing-first-prompt-free-users-openai-xcxwbn/ |url-status=live |archive-url=https://archive.is/K1l8s |archive-date=2026-03-03 |access-date=3 Mar 2026 |website=WinBuzzer}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[OpenAI]]&lt;br /&gt;
*[[Artificial intelligence]]&lt;br /&gt;
*[[Claude]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:OpenAI]]&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Category:Microsoft_Office&amp;diff=54704</id>
		<title>Category:Microsoft Office</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Category:Microsoft_Office&amp;diff=54704"/>
		<updated>2026-05-24T22:13:11Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[Category:Microsoft|Office]]&lt;br /&gt;
[[Category:Products]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Bing&amp;diff=54703</id>
		<title>Bing</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Bing&amp;diff=54703"/>
		<updated>2026-05-24T22:11:55Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}{{ProductCargo|ArticleType=Product|Logo=Bing Fluent Logo.png|Category=Search Engine|Company=Microsoft|Description=Privacy-focused search engine|InProduction=Yes|ReleaseYear=3 June 2009|Website=https://bing.com/}}&lt;br /&gt;
&#039;&#039;&#039;Microsoft Bing&#039;&#039;&#039; (also known simply as &#039;&#039;&#039;Bing&#039;&#039;&#039;) is a search engine owned and operated by Microsoft, and developed by Microsoft AI.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
===Privacy===&lt;br /&gt;
In 2022, France imposed a €60 million fine on Microsoft for privacy law violations using Bing [[Web cookie|cookies]] that prevented users from rejecting those cookies.&amp;lt;ref&amp;gt;{{Cite web |date=December 24, 2022 |title=France fines Microsoft 60 million euros over Bing cookies |url=https://borncity.com/win/2022/12/24/france-fines-microsoft-60-million-euros-over-bing-cookies/ |url-status=live |archive-url=https://web.archive.org/web/20221224151305/https://borncity.com/win/2022/12/24/france-fines-microsoft-60-million-euros-over-bing-cookies/ |archive-date=December 24, 2022 |access-date=December 24, 2022 |website=Born&#039;s Tech and Windows World}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=December 22, 2022 |title=France fines Microsoft €60m for imposing advertising cookies |url=https://www.rfi.fr/en/france/20221222-france-fines-microsoft-%E2%82%AC60m-for-imposing-advertising-cookies |url-status=live |archive-url=https://web.archive.org/web/20221224151303/https://www.rfi.fr/en/france/20221222-france-fines-microsoft-%E2%82%AC60m-for-imposing-advertising-cookies |archive-date=December 24, 2022 |access-date=December 24, 2022 |website=RFI}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Xiao |first=Menghan |date=December 23, 2022 |title=Microsoft fined $64 million by France over cookies used in Bing searches |url=https://www.scmagazine.com/analysis/compliance/microsoft-fined-64-million-by-france-over-cookies-used-in-bing-searches |url-status=live |archive-url=https://web.archive.org/web/20221224151305/https://www.scmagazine.com/analysis/compliance/microsoft-fined-64-million-by-france-over-cookies-used-in-bing-searches |archive-date=December 24, 2022 |access-date=December 24, 2022 |website=SC Media}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Censorship in China===&lt;br /&gt;
Microsoft has been criticized for censoring Bing search results to queries made in simplified Chinese characters which are used in mainland China. This is done to comply with the censorship requirements of the government in China.&amp;lt;ref&amp;gt;{{cite news |last=Kristof |first=Nicholas |date=November 20, 2009 |title=Boycott Microsoft Bing |url=http://kristof.blogs.nytimes.com/2009/11/20/boycott-microsoft-bing/ |url-status=dead |archive-url=https://web.archive.org/web/20091123194315/http://kristof.blogs.nytimes.com/2009/11/20/boycott-microsoft-bing/ |archive-date=November 23, 2009 |access-date=March 31, 2010 |work=The New York Times}}&amp;lt;/ref&amp;gt; Microsoft has not indicated a willingness to stop censoring search results in simplified Chinese characters in the wake of Google&#039;s decision to do so.&amp;lt;ref&amp;gt;{{cite web |date=March 23, 2010 |title=Activists applaud Google&#039;s censorship move, China grumbles |url=http://www.itpro.co.uk/621706/activists-applaud-googles-censorship-move-china-grumbles |url-status=live |archive-url=https://web.archive.org/web/20111028071727/http://www.itpro.co.uk/621706/activists-applaud-googles-censorship-move-china-grumbles |archive-date=October 28, 2011 |access-date=January 30, 2012 |publisher=IT PRO}}&amp;lt;/ref&amp;gt; All simplified Chinese searches in Bing are censored regardless of the user&#039;s country.&amp;lt;ref&amp;gt;{{cite news |date=November 20, 2009 |title=Boycott Microsoft Bing |url=http://kristof.blogs.nytimes.com/2009/11/20/boycott-microsoft-bing/ |url-status=dead |archive-url=https://web.archive.org/web/20091123194315/http://kristof.blogs.nytimes.com/2009/11/20/boycott-microsoft-bing/ |archive-date=November 23, 2009 |access-date=March 23, 2010 |work=The New York Times}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite news |date=February 12, 2014 |title=Bing&#039;s Chinese enigma |url=https://www.economist.com/blogs/analects/2014/02/internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20180107064213/https://www.economist.com/blogs/analects/2014/02/internet-censorship |archive-date=January 7, 2018 |access-date=January 6, 2018 |newspaper=The Economist}}&amp;lt;/ref&amp;gt; The English-language search results of Bing in China has been skewed to show more content from state-run media like Xinhua News Agency and &#039;&#039;China Daily&#039;&#039;.&amp;lt;ref&amp;gt;{{cite news |last1=Liu |first1=Charles |date=May 17, 2016 |title=Bing Goes Full-on Censorship in English Search Results Within China |url=https://thenanfang.com/search-engine-bing-com-featuring-skewed-results-china/ |url-status=dead |archive-url=https://web.archive.org/web/20180107175119/https://thenanfang.com/search-engine-bing-com-featuring-skewed-results-china/ |archive-date=January 7, 2018 |access-date=January 7, 2018 |publisher=The Nanfang |df=mdy-all}}&amp;lt;/ref&amp;gt; On 23 January 2019, Bing was blocked in China.&amp;lt;ref&amp;gt;{{cite web |date=24 January 2019 |title=China blocks Microsoft&#039;s Bing search engine |url=https://www.theguardian.com/world/2019/jan/24/china-blocks-microsofts-bing-search-engine |url-status=live |archive-url=https://web.archive.org/web/20191208042303/https://www.theguardian.com/world/2019/jan/24/china-blocks-microsofts-bing-search-engine |archive-date=December 8, 2019 |access-date=January 24, 2019 |website=[[TheGuardian.com]] |agency=Reuters}}&amp;lt;/ref&amp;gt; According to a source quoted by &#039;&#039;The Financial Times&#039;&#039;, the order was from the Chinese government to block Bing for &amp;quot;illegal content&amp;quot;.&amp;lt;ref&amp;gt;{{Cite web |last=Yang |first=Yuan |date=2019-01-24 |title=China blocks Bing access in curb on last foreign search engine |url=https://www.ft.com/content/714ac466-1f64-11e9-b126-46fc3ad87c65 |url-access=subscription |url-status=live |archive-url=https://ghostarchive.org/archive/20221211191251/https://www.ft.com/content/714ac466-1f64-11e9-b126-46fc3ad87c65 |archive-date=December 11, 2022 |access-date=December 17, 2021 |work=The Financial Times}}&amp;lt;/ref&amp;gt; On 24 January, Bing was accessible again in China.&amp;lt;ref&amp;gt;{{cite news |last1=Lanxon |first1=Nate |date=January 24, 2019 |title=Microsoft&#039;s Bing accessible again in China after hours of outages |url=https://www.seattletimes.com/business/microsofts-bing-accessible-again-in-china-after-hours-of-outages/ |url-status=live |archive-url=https://web.archive.org/web/20190125130828/https://www.seattletimes.com/business/microsofts-bing-accessible-again-in-china-after-hours-of-outages/ |archive-date=January 25, 2019 |access-date=25 January 2019 |publisher=Bloomberg News}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Around 4 June 2021, the anniversary of the 1989 Tiananmen Square protests and massacre, Bing blocked image and video search results for the English term &amp;quot;Tank Man&amp;quot; in the US, UK, France, Germany, Singapore, Switzerland, and other countries. Microsoft responded that &amp;quot;This is due to an accidental human error&amp;quot;.&amp;lt;ref&amp;gt;{{cite web |date=4 June 2021 |title=Bing Censors Image Search for &#039;Tank Man&#039; Even in US |url=https://www.vice.com/en/article/bing-censors-tank-man/ |url-status=live |archive-url=https://web.archive.org/web/20210605072041/https://www.vice.com/amp/en/article/qj8v9m/bing-censors-tank-man |archive-date=June 5, 2021 |access-date=June 5, 2021 |work=Vice}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web |date=5 June 2021 |title=Microsoft says error led to no matching Bing images for Tiananmen &#039;tank man&#039; |url=https://www.reuters.com/technology/microsoft-bing-raises-concerns-over-lack-image-results-tiananmen-tank-man-2021-06-04/ |url-status=live |archive-url=https://web.archive.org/web/20210705124052/https://www.reuters.com/technology/microsoft-bing-raises-concerns-over-lack-image-results-tiananmen-tank-man-2021-06-04/ |archive-date=July 5, 2021 |access-date=June 5, 2021 |publisher=Reuters}}&amp;lt;/ref&amp;gt; According to an investigation by &#039;&#039;Bloomberg Businessweek&#039;&#039;, the full explanation was that Microsoft accidentally applied its Chinese blacklist globally.&amp;lt;ref&amp;gt;{{cite news |last1=Gallagher |first1=Ryan |date=March 7, 2024 |title=How Microsoft&#039;s Bing Helps Maintain Beijing&#039;s Great Firewall |url=https://www.bloomberg.com/news/features/2024-03-07/microsoft-s-bing-helps-maintain-china-s-great-firewall |url-status=live |archive-url=https://web.archive.org/web/20240324014927/https://www.bloomberg.com/news/features/2024-03-07/microsoft-s-bing-helps-maintain-china-s-great-firewall |archive-date=March 24, 2024 |access-date=March 23, 2024 |work=Bloomberg Businessweek |publisher=Bloomberg L.P.}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In December 2021, it was required by a &amp;quot;relevant government agency&amp;quot; to suspend its auto-suggest function in China for 30 days.&amp;lt;ref&amp;gt;{{cite web |date=2021-12-17 |title=Microsoft&#039;s Bing suspends auto suggest function in China at government&#039;s behest |url=https://www.reuters.com/technology/microsoft-bing-says-suspended-auto-suggest-function-china-government-behest-2021-12-17/ |url-status=live |archive-url=https://web.archive.org/web/20211217062628/https://www.reuters.com/technology/microsoft-bing-says-suspended-auto-suggest-function-china-government-behest-2021-12-17/ |archive-date=December 17, 2021 |access-date=December 17, 2021 |work=Reuters}}&amp;lt;/ref&amp;gt; The search engine became partially unavailable in mainland China from 16 December until its resumption on 18 December 2021.&amp;lt;ref&amp;gt;{{Cite web |last=Lin |first=Liza |date=2021-12-17 |title=Microsoft&#039;s Bing Halts Autofill Feature in China, Citing Local Laws |url=https://www.wsj.com/articles/microsofts-bing-halts-autofill-feature-in-china-citing-local-laws-11639743295 |archiveurl=https://archive.today/20211217122907/https://www.wsj.com/articles/microsofts-bing-halts-autofill-feature-in-china-citing-local-laws-11639743295 |archivedate=December 17, 2021 |access-date=December 17, 2021 |work=The Wall Street Journal}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2021-12-18 |title=微软 Bing（必应）已可正常访问 |url=https://m.ithome.com/html/593213.htm |archiveurl=https://archive.today/20211219143355/https://m.ithome.com/html/593213.htm |archivedate=December 19, 2021 |access-date=December 19, 2021 |work=IT Home |language=zh}}&amp;lt;/ref&amp;gt; According to the company, a government agency in March 2022 required that it suspend auto-suggest function in China for seven days; Bing did not specify the reason.&amp;lt;ref&amp;gt;{{cite news |date=21 March 2022 |title=China requires Microsoft&#039;s Bing to suspend auto-suggest feature |url=https://www.reuters.com/technology/china-requires-microsofts-bing-suspend-auto-suggest-feature-2022-03-21/ |url-status=live |archive-url=https://web.archive.org/web/20220322044210/https://www.reuters.com/technology/china-requires-microsofts-bing-suspend-auto-suggest-feature-2022-03-21/ |archive-date=March 22, 2022 |access-date=March 22, 2022 |work=Reuters |language=en}}&amp;lt;/ref&amp;gt; In May 2022, a report released by the [[Citizen Lab]] of the University of Toronto found that Bing&#039;s autosuggestion system censored the names of Chinese Communist Party leaders, dissidents, and other persons considered politically sensitive in China in both Chinese and English, not only in China but also in the United States and Canada.&amp;lt;ref&amp;gt;{{Cite journal |last1=Knockel |first1=Jeffrey |last2=Ruan |first2=Lotus |date=2022-05-19 |title=Bada Bing, Bada Boom: Microsoft Bing&#039;s Chinese Political Censorship of Autosuggestions in North America |url=https://citizenlab.ca/2022/05/bada-bing-bada-boom-microsoft-bings-chinese-political-censorship-autosuggestions-north-america/ |url-status=live |journal=Citizen Lab |archive-url=https://web.archive.org/web/20220519143154/https://citizenlab.ca/2022/05/bada-bing-bada-boom-microsoft-bings-chinese-political-censorship-autosuggestions-north-america/ |archive-date=May 19, 2022 |access-date=May 19, 2022}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite news |last=Tilley |first=Aaron |date=2022-05-19 |title=Microsoft Is Censoring Searches in U.S. for Politically Sensitive Chinese Names, Researchers Say |url=https://www.wsj.com/articles/microsoft-said-to-censor-searches-in-u-s-for-politically-sensitive-chinese-names-11652965201 |url-status=live |archive-url=https://web.archive.org/web/20220520030332/https://www.wsj.com/articles/microsoft-said-to-censor-searches-in-u-s-for-politically-sensitive-chinese-names-11652965201 |archive-date=May 20, 2022 |access-date=2022-05-20 |work=[[The Wall Street Journal]] |language=en-US |issn=0099-9660}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In April 2023, Citizen Lab reported that Bing was more censorious in China than native Chinese search engines.&amp;lt;ref&amp;gt;{{Cite news |last=Myers |first=Steven Lee |date=2023-04-26 |title=China&#039;s Search Engines Have More Than 66,000 Rules Controlling Content, Report Says |url=https://www.nytimes.com/2023/04/26/business/china-censored-search-engine.html |url-status=live |archive-url=https://web.archive.org/web/20230429155352/https://www.nytimes.com/2023/04/26/business/china-censored-search-engine.html |archive-date=April 29, 2023 |access-date=2023-04-29 |work=[[The New York Times]] |language=en-US |issn=0362-4331}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Chiu |first=Joanna |date=2024-06-27 |title=Microsoft Bing&#039;s censorship in China is even &amp;quot;more extreme&amp;quot; than Chinese companies&#039; |url=https://restofworld.org/2024/microsoft-bing-chinese-censorship/ |access-date=2024-06-27 |website=Rest of World |language=en-US}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Child pornography===&lt;br /&gt;
A study released in 2019 of Bing Image search showed that it both freely offered up images that had been tagged as illegal [[child pornography]] in national databases, as well as automatically suggesting via its auto-completion feature queries related to child pornography. This easy accessibility was considered particularly surprising since Microsoft pioneered [[PhotoDNA]], the main technology used for tracking images reported as originating from child pornography.&amp;lt;ref&amp;gt;{{Cite web |last=Constine |first=Josh |date=January 10, 2019 |title=Microsoft Bing not only shows child sexual abuse, it suggests it |url=https://techcrunch.com/2019/01/10/unsafe-search/ |url-status=live |archive-url=https://web.archive.org/web/20230220184238/https://techcrunch.com/2019/01/10/unsafe-search/ |archive-date=February 20, 2023 |access-date=February 20, 2023}}&amp;lt;/ref&amp;gt; Additionally, some arrested child pornographers reported using Bing as their main search engine for new content.&amp;lt;ref&amp;gt;{{Cite news |last1=Keller |first1=Michael H. |last2=Dance |first2=Gabriel J. X. |date=November 9, 2019 |title=Child Abusers Run Rampant as Tech Companies Look the Other Way |url=https://www.nytimes.com/interactive/2019/11/09/us/internet-child-sex-abuse.html |url-status=live |archive-url=https://web.archive.org/web/20191202200034/https://www.nytimes.com/interactive/2019/11/09/us/internet-child-sex-abuse.html |archive-date=December 2, 2019 |access-date=December 2, 2019 |newspaper=The New York Times}}&amp;lt;/ref&amp;gt; Microsoft vowed to fix the problem and assign additional staff to combat the issue after the report was released.&lt;br /&gt;
&lt;br /&gt;
===Malware===&lt;br /&gt;
In 2024, [[malware]] was found in the official Bing Wallpaper app that tries to change the users&#039; browser settings in order to  set the default web browser to Microsoft Edge. It has also been found stealing Edge, Chrome, and Firefox cookies.&amp;lt;ref&amp;gt;{{cite web |last=Maruccia |first=Alfonso |date=November 21, 2024 |title=The official &amp;quot;Bing Wallpaper app&amp;quot; does some nasty, malware-like things to Windows |url=https://www.techspot.com/news/105673-official-bing-wallpaper-app-does-nasty-malware-like.html |access-date=July 4, 2025 |publisher=Techspot |archive-url=http://web.archive.org/web/20251230112244/https://www.techspot.com/news/105673-official-bing-wallpaper-app-does-nasty-malware-like.html |archive-date=30 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[DuckDuckGo]]&lt;br /&gt;
*[[Brave browser|Brave]]&lt;br /&gt;
*[[Google]]&lt;br /&gt;
*[[Google Search]]&lt;br /&gt;
*[[Yandex]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
[[Category:Microsoft|Bing]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Microsoft_Authenticator&amp;diff=54702</id>
		<title>Microsoft Authenticator</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Microsoft_Authenticator&amp;diff=54702"/>
		<updated>2026-05-24T22:11:17Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Microsoft&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Logo=Microsoft Authenticator.png&lt;br /&gt;
|Category=Security, Software&lt;br /&gt;
|Website=https://www.microsoft.com/en-us/security/mobile-authenticator-app, https://support.microsoft.com/en-us/account-billing/about-microsoft-authenticator-9783c865-0308-42fb-a519-8cf666fe0acc&lt;br /&gt;
|Description=A free app that secures Microsoft accounts with single sign-on (SSO) and provides multi-factor authentication (MFA) to various other online services.&lt;br /&gt;
}}&#039;&#039;&#039;Microsoft Authenticator&#039;&#039;&#039; is a free mobile app that secures the user&#039;s Microsoft account with single sign-on (SSO) and provides multi-factor authenication (MFA) for other online services. &lt;br /&gt;
&lt;br /&gt;
One of its key functions is generating secure, ephemeral, random six-digit tokens to enable two-factor authentication (2FA) for arbitrary online services.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
&lt;br /&gt;
===User Freedom===&lt;br /&gt;
&lt;br /&gt;
====Inability to export codes====&lt;br /&gt;
Like [[Authy]], Microsoft Authenticator does not allow the user to export their MFA codes to another service.&lt;br /&gt;
[[File:Proton Microsoft Authenticator.png|thumb|325x325px]]&lt;br /&gt;
&lt;br /&gt;
====Cross-Platform Migration Friction====&lt;br /&gt;
A major pain point for users is that Microsoft Authenticator &#039;&#039;&#039;does not support direct cross-platform restore&#039;&#039;&#039;. This means that if a user with many accounts synced on an iPhone purchases an Android device, they have effectively two options to continue using Microsoft Authenticator for MFA:&lt;br /&gt;
&lt;br /&gt;
#Retain possession of the old iPhone for daily MFA needs, or&lt;br /&gt;
#Manually reconfigure every service that depends on Microsoft Authenticator for MFA on the new Android device.&lt;br /&gt;
&lt;br /&gt;
For personal power users, manual reconfiguration may be inconvenient but feasible. However, for work accounts, this process is often impractical as it may require administrative privileges beyond the user’s own.&lt;br /&gt;
&lt;br /&gt;
Microsoft’s official documentation acknowledges this limitation, stating:&amp;lt;blockquote&amp;gt;&amp;quot;&#039;&#039;&#039;Important&#039;&#039;&#039;: You can only backup and restore on the same device type: accounts backed up using an iOS device cannot be restored on an Android device.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |date=2025-10-07 |title=Back up your accounts in Microsoft Authenticator |url=https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |url-status=live |archive-url=https://web.archive.org/web/20260131003513/https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |archive-date=2026-01-31 |access-date=2025-10-07 |website=[[Microsoft]]}}&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Removal of password manager (June 2025)===&lt;br /&gt;
In June 2025, Microsoft Authenticator users were no longer be able to save new passwords in the app. Then in July 2025, autofill was removed and no longer available. And finally in August 2025, saved passwords were deleted in the Authenticator app.&amp;lt;ref&amp;gt;{{Cite web |last=Lakshmanan |first=Ravie |date=2025-07-01 |title=Microsoft Removes Password Management from Authenticator App Starting August 2025 |url=https://thehackernews.com/2025/07/microsoft-removes-password-management.html |url-status=live |archive-url=https://web.archive.org/web/20251216031451/https://thehackernews.com/2025/07/microsoft-removes-password-management.html |archive-date=2025-12-16 |access-date=2026-03-12 |website=[[The Hacker News]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Watkins |first=Jessica |date=2025-06-13 |title=Microsoft Deleting Saved Passwords From Auth App |url=https://flamingltd.com/microsoft-deleting-saved-passwords-from-auth-app/ |url-status=live |archive-url=https://web.archive.org/web/20251205183620/https://flamingltd.com/microsoft-deleting-saved-passwords-from-auth-app/ |archive-date=2025-12-05 |access-date=2026-03-12 |website=[[Flaming]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Brinkmann |first=Martin |date=2025-05-05 |title=Microsoft removes Authenticator App feature to promote Microsoft Edge |url=https://www.ghacks.net/2025/05/05/microsoft-removes-authenticator-app-feature-to-promote-microsoft-edge/ |url-status=live |archive-url=https://web.archive.org/web/20251210071101/https://www.ghacks.net/2025/05/05/microsoft-removes-authenticator-app-feature-to-promote-microsoft-edge/ |archive-date=2025-12-10 |access-date=2026-03-12 |website=[[ghacks.net]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Authy]]&lt;br /&gt;
*[[Proton Authenticator]]&lt;br /&gt;
*[[Google Authenticator]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Microsoft|Authenticator]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Microsoft_account&amp;diff=54701</id>
		<title>Microsoft account</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Microsoft_account&amp;diff=54701"/>
		<updated>2026-05-24T22:10:56Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}{{ProductCargo&lt;br /&gt;
|Company=Microsoft&lt;br /&gt;
|ReleaseYear=2019&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|Logo=Microsoft logo.svg&lt;br /&gt;
|Website=https://account.microsoft.com/account&lt;br /&gt;
|Description=Represents you.  Controls access to Microsoft products and services.  Allows Microsoft to track and control what you do.&lt;br /&gt;
}}&lt;br /&gt;
{{See also|Account}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Microsoft accounts&#039;&#039;&#039; are the central feature of modern Microsoft services. Though there have been a variety of Microsoft account types dating to the 1990s, the latest incarnation was pioneered in 2019 to centralize their [[Microsoft Office 365|productivity]], [[Microsoft Windows 11|operating system]], [[Microsoft Edge|web-browser]], and [[Xbox|gaming]] branches under a single unified account.&lt;br /&gt;
&lt;br /&gt;
Nearly from the onset, users and technical experts have expressed concern over the institution of Microsoft accounts, primarily out of concern for user privacy, though also for further limiting the ownership rights of individual consumers. Most Microsoft services, including Windows 11, Xbox, and Office 365, require a Microsoft account to function under normal circumstances. &lt;br /&gt;
==Consumer-impact summary==&lt;br /&gt;
&lt;br /&gt;
*Potential loss of data&lt;br /&gt;
*Potential loss of control/access to your Windows computer&lt;br /&gt;
*User privacy&lt;br /&gt;
*User freedom&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
{{Ph-C-Inc}}&lt;br /&gt;
This is a list of all consumer-protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
===Example incident one (&#039;&#039;date&#039;&#039;)===&lt;br /&gt;
{{See also|Microsoft&#039;s anticompetitive practices}}&lt;br /&gt;
Mysteriously banned the developer of LibreOffice from his Hotmail Account; Automated systems handled the appeal process and refused to restore access to his account, potentially harming LibreOffice&#039;s development.&amp;lt;ref&amp;gt;{{Cite news |last=Simms |first=Daniel |date=Jul 30, 2025 |title=Microsoft suddenly bans LibreOffice developer&#039;s email account, blocks appeal |url=https://www.techspot.com/news/108878-microsoft-suddenly-bans-libreoffice-developer-email-account-blocks.html |access-date=Aug 4, 2025 |work=TechSpot |archive-url=http://web.archive.org/web/20251126035944/https://www.techspot.com/news/108878-microsoft-suddenly-bans-libreoffice-developer-email-account-blocks.html |archive-date=26 Nov 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite news |last=Beri |first=Devesh |date=Aug 1, 2025 |title=Microsoft Bans Profile Belonging to Developer Behind Free Microsoft Office Alternative |url=https://tech.yahoo.com/business/articles/microsoft-bans-profile-belonging-developer-204536148.html |access-date=Aug 4, 2025 |work=ExtremeTech |archive-url=http://web.archive.org/web/20251001015153/https://tech.yahoo.com/business/articles/microsoft-bans-profile-belonging-developer-204536148.html |archive-date=1 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite news |last=Kumar |first=Rohit |date=Aug 3, 2025 |title=LibreOffice Developer Says Microsoft Blocked His Email Account Without Warning |url=https://www.alltechnerd.com/libreoffice-developer-says-microsoft-blocked-his-email-account-without-warning/ |access-date=Aug 4, 2025 |work=All Tech Nerd |archive-url=http://web.archive.org/web/20251001015153/https://www.alltechnerd.com/libreoffice-developer-says-microsoft-blocked-his-email-account-without-warning/ |archive-date=1 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Forced account]]&lt;br /&gt;
*[[Inactive account deletion]]&lt;br /&gt;
*[[Microsoft Authenticator]]&lt;br /&gt;
*[[Microsoft ends use of bypassnro.cmd for Windows 11|Microsoft ends use of &amp;lt;code&amp;gt;bypassnro.cmd&amp;lt;/code&amp;gt; for Windows 11]]&lt;br /&gt;
*[[Microsoft Office 365]]&lt;br /&gt;
*[[Microsoft Windows 11]]&lt;br /&gt;
*[[Minecraft account migration]]&lt;br /&gt;
*[[OneDrive]]&lt;br /&gt;
*[[Xbox]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Microsoft|Account]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Microsoft_Edge&amp;diff=54700</id>
		<title>Microsoft Edge</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Microsoft_Edge&amp;diff=54700"/>
		<updated>2026-05-24T22:09:12Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Cleanup}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Logo=Microsoft_Edge_logo.svg&lt;br /&gt;
|Category=Web browser&lt;br /&gt;
|Company=Microsoft&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ReleaseYear=2020-01-15&lt;br /&gt;
|Website=https://www.microsoft.com/en-us/edge&lt;br /&gt;
|Description=Microsoft Edge is a Chromium-based web browser developed by Microsoft in 2015 as a successor to Internet Explorer.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Microsoft Edge&#039;&#039;&#039; is a proprietary web browser developed by [[Microsoft]], first released in 2015 as the successor to Internet Explorer. Based on the [[Chromium]] engine since 2020, Edge is marketed as a fast and secure browser with integration across Microsoft services.&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-30 |title=What&#039;s the difference between the new Microsoft Edge and Microsoft Edge Legacy? |url=https://support.microsoft.com/en-us/microsoft-edge/what-s-the-difference-between-the-new-microsoft-edge-and-microsoft-edge-legacy-a01258e5-8c05-7bbb-bed2-c65bec0eb126 |url-status=live |website=Microsoft Support |archive-url=http://web.archive.org/web/20251122093923/https://support.microsoft.com/en-us/microsoft-edge/what-s-the-difference-between-the-new-microsoft-edge-and-microsoft-edge-legacy-a01258e5-8c05-7bbb-bed2-c65bec0eb126 |archive-date=22 Nov 2025}}&amp;lt;/ref&amp;gt; However, its deep embedding into Windows and Microsoft’s promotional tactics have drawn ongoing criticism.&amp;lt;sup&amp;gt;[&#039;&#039;[[Consumer Rights Wiki:Verifiability|citation needed]]&#039;&#039;]&amp;lt;/sup&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
===User freedom===&lt;br /&gt;
Microsoft discourages people from switching to a different web browser. Edge is set as the default browser in Windows, and is sometimes automatically re-installed when Windows updates occur.&amp;lt;ref&amp;gt;&lt;br /&gt;
{{Cite web&lt;br /&gt;
| last=Huculak&lt;br /&gt;
| first=Mauro&lt;br /&gt;
| title=How to prevent new Microsoft Edge from installing automatically on Windows 10&lt;br /&gt;
| url=https://www.windowscentral.com/how-prevent-microsoft-edge-chromium-installing-automatically-windows-10&lt;br /&gt;
| website=windowscentral.com&lt;br /&gt;
| access-date=2025-01-29&lt;br /&gt;
| date=2020-06-05&lt;br /&gt;
| archive-url=http://web.archive.org/web/20250917184020/https://www.windowscentral.com/how-prevent-microsoft-edge-chromium-installing-automatically-windows-10&lt;br /&gt;
| archive-date=2025-09-17&lt;br /&gt;
| url-status=live&lt;br /&gt;
}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;&lt;br /&gt;
{{Cite web |date=2025-01-06 |title=Edge Reïnstalls Itself? |url=https://www.elevenforum.com/t/edge-reinstalls-itself.32137/ |url-status=live |archive-url=https://web.archive.org/web/20260405195715/https://www.elevenforum.com/t/edge-reinstalls-itself.32137/ |archive-date=5 Apr 2026 |access-date=2026-02-24 |website=Windows ElevenForum}}&lt;br /&gt;
&amp;lt;/ref&amp;gt;&lt;br /&gt;
When attempting to install Google Chrome, for example, Edge displays text telling people &amp;quot;There&#039;s no need to download a new web browser&amp;quot;, among other things.&lt;br /&gt;
&amp;lt;ref&amp;gt;&lt;br /&gt;
{{Cite web&lt;br /&gt;
|last=Sen&lt;br /&gt;
|first=Sayan&lt;br /&gt;
|date=2021-12-02&lt;br /&gt;
|title=Microsoft says its own Edge browser is more trustworthy than &amp;quot;so 2008&amp;quot; Google Chrome |url=https://www.neowin.net/news/microsoft-says-its-own-edge-browser-is-more-trustworthy-than-so-2008-google-chrome/&lt;br /&gt;
|url-status=live&lt;br /&gt;
|archive-url=https://web.archive.org/web/20211202081952/https://www.neowin.net/news/microsoft-says-its-own-edge-browser-is-more-trustworthy-than-so-2008-google-chrome/&lt;br /&gt;
|archive-date=2021-12-02&lt;br /&gt;
|access-date=2025-08-22&lt;br /&gt;
|website=Neowin}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
Microsoft also hosts a page on their website with the URL &amp;quot;https://www.microsoft.com/en-us/edge/uninstall-edge&amp;quot;, suggesting this is a guide to uninstall the browser. However, the page is actually titled &amp;quot;Are you sure you want to uninstall Microsoft Edge?&amp;quot; and attempts to convince the reader that Edge is worth using, misleading readers.&amp;lt;!-- TODO: Update citation 5&#039;s archive link from archive.today. An archive.org capture failed, need to find different archival service that works.--&amp;gt;&lt;br /&gt;
&amp;lt;ref&amp;gt;&lt;br /&gt;
{{Cite web |date=2025-02-11 |title=Uninstall Microsoft Edge |url=http://archive.today/01vwF |url-status=live |archive-url=https://archive.org/details/screenshot-20260405-210358085-1 |archive-date=5 Apr 2026 |website=Microsoft.com}}&lt;br /&gt;
&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;&lt;br /&gt;
{{Cite web&lt;br /&gt;
| url=https://www.techradar.com/computing/edge/sorry-youre-not-getting-microsoft-edge-off-of-your-pc-at-least-according-to-its-new-uninstall-document&lt;br /&gt;
| last=Williams&lt;br /&gt;
| first=Isaiah&lt;br /&gt;
| website=TechRadar&lt;br /&gt;
| title=Sorry, you&#039;re not getting Microsoft Edge off of your PC, at least according to its new &#039;uninstall&#039; document&lt;br /&gt;
| date=2025-02-07&lt;br /&gt;
| access-date=2026-02-24&lt;br /&gt;
| archive-url=https://web.archive.org/web/20251208104305/https://www.techradar.com/computing/edge/sorry-youre-not-getting-microsoft-edge-off-of-your-pc-at-least-according-to-its-new-uninstall-document&lt;br /&gt;
| archive-date=2025-12-08&lt;br /&gt;
| url-status=live&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/ref&amp;gt;&lt;br /&gt;
All of these methods try to keep Edge installed on a person&#039;s computer and try to maximize the chances that person uses Edge.&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
Privacy advocates have raised concerns about Edge&#039;s telemetry and data collection, including browsing history and search queries sent to Microsoft by default.{{Citation needed}} While the company claims this improves performance and security, critics view it as excessive surveillance.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
===Business model===&lt;br /&gt;
Edge follows a freemium-adjacent model, integrating Microsoft services such as Bing and Shopping tools directly into the browser.{{Citation needed}} Critics argue these features prioritize monetization and ecosystem lock-in over user experience.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
====Market control====&lt;br /&gt;
By bundling Edge with Windows and tightly integrating it into the operating system, Microsoft has been accused of leveraging its OS dominance to entrench its browser market share.{{Citation needed}} This has attracted regulatory scrutiny and anti-trust complaints.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer-protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===Forced Installation via Windows Updates===&lt;br /&gt;
Microsoft has been criticized for pushing Edge installations through Windows updates, even when users had previously removed or replaced the browser. The browser gets reinstalled after an update due to the browser update programs being listed as system services, which get reactivated after updating.&amp;lt;ref&amp;gt;https://learn.microsoft.com/en-my/answers/questions/5727874/how-do-i-prevent-edge-from-reinstalling-itself ([https://web.archive.org/web/20260503110346/https://learn.microsoft.com/en-my/answers/questions/5727874/how-do-i-prevent-edge-from-reinstalling-itself archive])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Chromium]]&lt;br /&gt;
*[[Firefox]]&lt;br /&gt;
*[[Microsoft]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Microsoft|Edge]]&lt;br /&gt;
[[Category:Web browsers]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Visual_Studio_Code&amp;diff=54699</id>
		<title>Visual Studio Code</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Visual_Studio_Code&amp;diff=54699"/>
		<updated>2026-05-24T22:08:06Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Microsoft&lt;br /&gt;
|ReleaseYear=2015&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Software&lt;br /&gt;
|Website=https://code.visualstudio.com&lt;br /&gt;
|Logo=Visual Studio Code logo.svg}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[wikipedia:Visual Studio Code|Visual Studio Code]]&#039;&#039;&#039; is a cross platform text and code editor developed by [[Microsoft]] for [[Windows]], Linux, macOS and web browsers.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
&lt;br /&gt;
===Freedom===&lt;br /&gt;
The source code is available on GitHub under the MIT License. However, the binaries published by Microsoft are licensed under the proprietary &amp;quot;Microsoft Software License&amp;quot; and ships with closed-source modifications, similar to how [[Google]] ships [[Chromium]], their open source browser and [[Chrome]], their flagship, proprietary browser built on top of Chromium but with various closed source modifications.&lt;br /&gt;
&lt;br /&gt;
Alternative, fully open source forks exist, such as [https://vscodium.com/ VS Codium].&lt;br /&gt;
&lt;br /&gt;
===Market Control===&lt;br /&gt;
Visual Studio Code (Also known as VS Code) is widely used upon, with over 50 million developers using it as of May 15th, 2025.&amp;lt;ref&amp;gt;https://developer.microsoft.com/blog/celebrating-50-million-developers-the-journey-of-visual-studio-and-visual-studio-code ([http://web.archive.org/web/20251221194419/https://developer.microsoft.com/blog/celebrating-50-million-developers-the-journey-of-visual-studio-and-visual-studio-code Archived])&amp;lt;/ref&amp;gt; Due to the software being open source, users may switch to other forks such as [https://vscodium.com/ VS Codium] if they are not happy with Visual Studio Code&#039;s features.&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===Telemetry enabled by default===&lt;br /&gt;
Microsoft&#039;s proprietary build sends telemetry data by default&amp;lt;ref&amp;gt;{{Cite web |title=Telemetry |url=https://code.visualstudio.com/docs/configure/telemetry |url-status=live |archive-url=https://web.archive.org/web/20251219092557/https://code.visualstudio.com/docs/configure/telemetry |archive-date=19 Dec 2025 |website=VS Code Documentation}}&amp;lt;/ref&amp;gt; which goes under [https://www.microsoft.com/en-us/privacy/privacystatement Microsoft&#039;s Privacy Statement]. It has to be disabled manually by setting &amp;lt;code&amp;gt;telemetry.telemetryLevel&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;off&amp;lt;/code&amp;gt; in the user settings.&lt;br /&gt;
&lt;br /&gt;
===Blocking extensions for third-party forks===&lt;br /&gt;
In April 2025, Microsoft pushed an update to the &amp;quot;C/C++&amp;quot; extension for Visual Studio Code (an extension that adds functionality such as better syntax highlighting) that introduced functionality that would intentionally disable the extension if it detected that it was running inside of a third-party fork of the editor,&amp;lt;ref&amp;gt;{{Cite news |last=Claburn |first=Thomas |date=2025-04-24 |title=Devs sound alarm after Microsoft subtracts C/C++ extension from VS Code forks |url=https://www.theregister.com/2025/04/24/microsoft_vs_code_subtracts_cc_extension/ |url-status=live |archive-url=http://web.archive.org/web/20260218105824/https://www.theregister.com/2025/04/24/microsoft_vs_code_subtracts_cc_extension/ |archive-date=18 Feb 2026|work=The Register}}&amp;lt;/ref&amp;gt; displaying an error message that says:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span lang=&amp;quot;en&amp;quot; dir=&amp;quot;ltr&amp;quot;&amp;gt;&amp;quot;The C/C++ extension may be used only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services to develop and test your applications.&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=VSCodium issues |url=https://github.com/VSCodium/vscodium/issues/2300 |archive-url=https://web.archive.org/web/20250405162831/https://github.com/VSCodium/vscodium/issues/2300 |archive-date=5 Apr 2025 |website=&amp;quot;Microsoft C/C++ Extension appears to no longer support unofficial forks of VS Code&amp;quot;}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |title=Cursor issues |url=https://github.com/cursor/cursor/issues/2976 |archive-url=https://web.archive.org/web/20250625115317/https://github.com/cursor/cursor/issues/2976 |archive-date=25 Jun 2025 |website=&amp;quot;Has the VSCode C/C++ Extension been blocked?&amp;quot;}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Microsoft]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=OneDrive&amp;diff=54698</id>
		<title>OneDrive</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=OneDrive&amp;diff=54698"/>
		<updated>2026-05-24T22:07:36Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ProductCargo&lt;br /&gt;
|Logo=OneDrive.svg&lt;br /&gt;
|Company=Microsoft&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Service&lt;br /&gt;
|Category=Cloud storage&lt;br /&gt;
|ReleaseYear=2007 (as SkyDrive)|Website=https://onedrive.live.com/}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;OneDrive&#039;&#039;&#039; is a cloud storage service created by [[Microsoft]] in 2007 as SkyDrive and rebranded in 2014.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===Automatic syncing===&lt;br /&gt;
Previously, Microsoft prompted users to back up their devices through reminders and asked for their permission to back folders up to OneDrive. Currently, OneDrive alters the Windows File Explorer to default to OneDrive&#039;s folders, and to replace the standard shortcuts to folders for Documents, Images, Downloads, etc. with shortcuts to OneDrive&#039;s folders.&amp;lt;ref&amp;gt;{{Cite web |last=Pippig |first=Laura |date=25 Jun 2024 |title=Windows 11 starts forcing OneDrive backups without asking permission |url=https://www.pcworld.com/article/2376883/attention-microsoft-activates-this-feature-in-windows-11-without-asking-you.html |url-status=live |access-date=27 Aug 2025 |website=PCWorld |archive-url=http://web.archive.org/web/20260201192828/https://www.pcworld.com/article/2376883/attention-microsoft-activates-this-feature-in-windows-11-without-asking-you.html |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt; This causes user files to back up to OneDrive by default, even when the folders are disabled for syncing,&amp;lt;ref&amp;gt;{{Cite web |title=OneDrive&#039;s Forcable Takeover of Folders Is Intolerable |url=https://www.reddit.com/r/onedrive/comments/1e5riab/onedrives_forcable_takeover_of_folders_is/ |url-status=live |archive-url=https://web.archive.org/web/20260407171938/https://old.reddit.com/r/onedrive/comments/1e5riab/onedrives_forcable_takeover_of_folders_is/ |archive-date=7 Apr 2026 |access-date=27 Aug 2025 |website=Reddit}}&amp;lt;/ref&amp;gt; usually without their knowledge or consent. &lt;br /&gt;
&lt;br /&gt;
Once users have reached the maximum space OneDrive allows, they are prompted to pay for additional space, and in some cases are prevented from downloading attachments through Outlook and other Microsoft products.&amp;lt;ref&amp;gt;{{Cite web |date=3 Mar 2025 |title=OneDrive sync&#039;d EVERYTHING without permission? |url=https://learn.microsoft.com/en-us/answers/questions/3887116/onedrive-syncd-everything-without-permission |url-status=live |archive-url=https://web.archive.org/web/20260407172107/https://learn.microsoft.com/en-us/answers/questions/3887116/onedrive-syncd-everything-without-permission |archive-date=7 Apr 2026 |access-date=27 Aug 2025 |website=Microsoft Q&amp;amp;A}}&amp;lt;/ref&amp;gt; Without the standard shortcuts to local folders in place, users are often unaware that they have alternative options. When users attempt to disable OneDrive, the service removes the user&#039;s files from the cloud.&amp;lt;ref&amp;gt;{{Cite web |date=19 Mar 2024 |title=RANT: OneDrive enabled without consent |url=https://learn.microsoft.com/en-us/answers/questions/4043083/rant-onedrive-enabled-without-consent |url-status=live |archive-url=https://web.archive.org/web/20260407172111/https://learn.microsoft.com/en-us/answers/questions/4043083/rant-onedrive-enabled-without-consent |archive-date=7 Apr 2026 |access-date=27 Aug 2025 |website=Microsoft Q&amp;amp;A}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=9 Feb 2023 |title=Onedrive is horrible, invasive and impossible |url=https://learn.microsoft.com/en-us/answers/questions/5213385/onedrive-is-horrible-invasive-and-impossible |url-status=live |access-date=27 Aug 2025 |website=Microsoft Q&amp;amp;A |archive-url=http://web.archive.org/web/20251023052231/https://learn.microsoft.com/en-us/answers/questions/5213385/onedrive-is-horrible-invasive-and-impossible |archive-date=23 Oct 2025}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |first= |title=Onedrive Syncs files without permission and can&#039;t be removed without deletion of the files in the local machine. |url=https://www.reddit.com/r/onedrive/comments/zx79j6/onedrive_syncs_files_without_permission_and_cant/ |url-status=live |access-date=27 Aug 2025 |website=Reddit |archive-url=http://web.archive.org/web/20221228141331/https://old.reddit.com/r/onedrive/comments/zx79j6/onedrive_syncs_files_without_permission_and_cant/ |archive-date=28 Dec 2022}}&amp;lt;/ref&amp;gt; If users have not made a local backup beforehand, their files are permanently lost.&lt;br /&gt;
==See also==&lt;br /&gt;
*[[iCloud]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
[[Category:Microsoft]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Microsoft_Authenticator&amp;diff=54697</id>
		<title>Microsoft Authenticator</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Microsoft_Authenticator&amp;diff=54697"/>
		<updated>2026-05-24T22:04:28Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Microsoft&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Logo=Microsoft Authenticator.png&lt;br /&gt;
|Category=Security, Software&lt;br /&gt;
|Website=https://www.microsoft.com/en-us/security/mobile-authenticator-app, https://support.microsoft.com/en-us/account-billing/about-microsoft-authenticator-9783c865-0308-42fb-a519-8cf666fe0acc&lt;br /&gt;
|Description=A free app that secures Microsoft accounts with single sign-on (SSO) and provides multi-factor authentication (MFA) to various other online services.&lt;br /&gt;
}}&#039;&#039;&#039;Microsoft Authenticator&#039;&#039;&#039; is a free mobile app that secures the user&#039;s Microsoft account with single sign-on (SSO) and provides multi-factor authenication (MFA) for other online services. &lt;br /&gt;
&lt;br /&gt;
One of its key functions is generating secure, ephemeral, random six-digit tokens to enable two-factor authentication (2FA) for arbitrary online services.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
&lt;br /&gt;
===User Freedom===&lt;br /&gt;
&lt;br /&gt;
====Inability to export codes====&lt;br /&gt;
Like [[Authy]], Microsoft Authenticator does not allow the user to export their MFA codes to another service.&lt;br /&gt;
[[File:Proton Microsoft Authenticator.png|thumb|325x325px]]&lt;br /&gt;
&lt;br /&gt;
====Cross-Platform Migration Friction====&lt;br /&gt;
A major pain point for users is that Microsoft Authenticator &#039;&#039;&#039;does not support direct cross-platform restore&#039;&#039;&#039;. This means that if a user with many accounts synced on an iPhone purchases an Android device, they have effectively two options to continue using Microsoft Authenticator for MFA:&lt;br /&gt;
&lt;br /&gt;
#Retain possession of the old iPhone for daily MFA needs, or&lt;br /&gt;
#Manually reconfigure every service that depends on Microsoft Authenticator for MFA on the new Android device.&lt;br /&gt;
&lt;br /&gt;
For personal power users, manual reconfiguration may be inconvenient but feasible. However, for work accounts, this process is often impractical as it may require administrative privileges beyond the user’s own.&lt;br /&gt;
&lt;br /&gt;
Microsoft’s official documentation acknowledges this limitation, stating:&amp;lt;blockquote&amp;gt;&amp;quot;&#039;&#039;&#039;Important&#039;&#039;&#039;: You can only backup and restore on the same device type: accounts backed up using an iOS device cannot be restored on an Android device.&amp;quot;&amp;lt;ref&amp;gt;{{Cite web |date=2025-10-07 |title=Back up your accounts in Microsoft Authenticator |url=https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |url-status=live |archive-url=https://web.archive.org/web/20260131003513/https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |archive-date=2026-01-31 |access-date=2025-10-07 |website=[[Microsoft]]}}&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
==Incidents==&lt;br /&gt;
===Removal of password manager (June 2025)===&lt;br /&gt;
In June 2025, Microsoft Authenticator users were no longer be able to save new passwords in the app. Then in July 2025, autofill was removed and no longer available. And finally in August 2025, saved passwords were deleted in the Authenticator app.&amp;lt;ref&amp;gt;{{Cite web |last=Lakshmanan |first=Ravie |date=2025-07-01 |title=Microsoft Removes Password Management from Authenticator App Starting August 2025 |url=https://thehackernews.com/2025/07/microsoft-removes-password-management.html |url-status=live |archive-url=https://web.archive.org/web/20251216031451/https://thehackernews.com/2025/07/microsoft-removes-password-management.html |archive-date=2025-12-16 |access-date=2026-03-12 |website=[[The Hacker News]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Watkins |first=Jessica |date=2025-06-13 |title=Microsoft Deleting Saved Passwords From Auth App |url=https://flamingltd.com/microsoft-deleting-saved-passwords-from-auth-app/ |url-status=live |archive-url=https://web.archive.org/web/20251205183620/https://flamingltd.com/microsoft-deleting-saved-passwords-from-auth-app/ |archive-date=2025-12-05 |access-date=2026-03-12 |website=[[Flaming]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Brinkmann |first=Martin |date=2025-05-05 |title=Microsoft removes Authenticator App feature to promote Microsoft Edge |url=https://www.ghacks.net/2025/05/05/microsoft-removes-authenticator-app-feature-to-promote-microsoft-edge/ |url-status=live |archive-url=https://web.archive.org/web/20251210071101/https://www.ghacks.net/2025/05/05/microsoft-removes-authenticator-app-feature-to-promote-microsoft-edge/ |archive-date=2025-12-10 |access-date=2026-03-12 |website=[[ghacks.net]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Authy]]&lt;br /&gt;
*[[Proton Authenticator]]&lt;br /&gt;
*[[Google Authenticator]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Microsoft]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Microsoft&amp;diff=54696</id>
		<title>Microsoft</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Microsoft&amp;diff=54696"/>
		<updated>2026-05-24T22:04:08Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: cat sort&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete|Issue 1=Article needs to be broken up into sub-articles in order to make it more legible, organized, and navigable. use of main headings should also be improved|Issue 2=Elaboration needed on section(s) describing recent and ongoing anti-competitive lawsuits.|Issue 3=Elaboration needed on Bing and search engine under anti-competitive incidents.}}&lt;br /&gt;
{{CompanyCargo&lt;br /&gt;
| Founded       = 1975&lt;br /&gt;
| Industry      = Information Technology, AI&lt;br /&gt;
| Logo          = Microsoft_logo.svg&lt;br /&gt;
| ParentCompany = &lt;br /&gt;
| Type          = Public&lt;br /&gt;
| Website       = https://www.microsoft.com/&lt;br /&gt;
| Description   = Microsoft is one of the &amp;quot;Big Five&amp;quot; tech giants who has had issues ranging from antitrust issues to monopolies&lt;br /&gt;
|CompanyAlias = Microsoft Corporation&lt;br /&gt;
}}&lt;br /&gt;
[[Wikipedia:Microsoft|&#039;&#039;&#039;&#039;&#039;Microsoft Corporation&#039;&#039;&#039;&#039;&#039;]] was founded in 1975 by &#039;&#039;Bill Gates&#039;&#039; and &#039;&#039;Paul Allen&#039;&#039; in Albuquerque, New Mexico. It is one of the &amp;quot;Big Five&amp;quot; tech giants, well known for licensing &#039;&#039;Q-DOS&#039;&#039; from &#039;&#039;Seattle Computer Product&#039;&#039;s as &#039;&#039;MS-DOS&#039;&#039; prior to purchasing it in 1980, as well as being known for &#039;&#039;Windows&#039;&#039;, the graphical extension to &#039;&#039;MS-DO&#039;&#039;S. They have developed the &#039;&#039;Microsoft&#039;&#039; &#039;&#039;Office Suite: Access,&#039;&#039; &#039;&#039;Excel, PowerPoint, Publisher,&#039;&#039; and &#039;&#039;Word&#039;&#039;; the &#039;&#039;Xbox&#039;&#039; under &#039;&#039;the Microsoft&#039;&#039; &#039;&#039;Gaming&#039;&#039; division; the &#039;&#039;Surface&#039;&#039; line of laptop devices; and the cloud platform &#039;&#039;Azure&#039;&#039;.&amp;lt;ref&amp;gt;{{Cite web |last=Zachary |first=Gregg Pascal |last2=Hall |first2=Mark |last3=Montevirgen |first3=Karl |title=Microsoft-Corporation |url=https://www.britannica.com/money/Microsoft-Corporation |url-status=live |website=britannica.com |archive-url=http://web.archive.org/web/20260113144228/https://www.britannica.com/money/Microsoft-Corporation |archive-date=13 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Miller |first=Michael |date=August 12, 2021 |title=The Rise of DOS: How Microsoft Got the IBM PC OS Contract |url=https://www.pcmag.com/news/the-rise-of-dos-how-microsoft-got-the-ibm-pc-os-contract |url-status=live |website=PCmag |archive-url=http://web.archive.org/web/20251218215243/https://www.pcmag.com/news/the-rise-of-dos-how-microsoft-got-the-ibm-pc-os-contract |archive-date=18 Dec 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Through acquisitions, Microsoft owns numerous other tech-related businesses.&amp;lt;ref&amp;gt;{{Cite web |title=List of mergers and acquisitions by Microsoft |url=https://en.wikipedia.org/wiki/List_of_mergers_and_acquisitions_by_Microsoft |website=Wikipedia |archive-url=http://web.archive.org/web/20260102005731/https://en.wikipedia.org/wiki/List_of_mergers_and_acquisitions_by_Microsoft |archive-date=2 Jan 2026}}&amp;lt;/ref&amp;gt;. Their most notable acquisitions include Skype, [[LinkedIn]], Github and [[Activision Blizzard]].&lt;br /&gt;
&lt;br /&gt;
They also invest heavily in artificial intelligence enterprises like &#039;&#039;[[OpenAI]]&#039;&#039; (best known for creating &#039;&#039;ChatGPT&#039;&#039;).&amp;lt;ref&amp;gt;{{Cite news |last=Vincent |first=James |date=July 22, 2019 |title=Microsoft invests $1 billion in OpenAI to pursue holy grail of artificial intelligence |url=https://www.theverge.com/2019/7/22/20703578/microsoft-openai-investment-partnership-1-billion-azure-artificial-general-intelligence-agi |work=The Verge |archive-url=http://web.archive.org/web/20251112210115/https://www.theverge.com/2019/7/22/20703578/microsoft-openai-investment-partnership-1-billion-azure-artificial-general-intelligence-agi |archive-date=12 Nov 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
Microsoft has engaged in significant anti-consumer and anti-competitive practices, often leading to lawsuits in relating to allegations of monopolistic behavior. Such lawsuits have featured Microsoft&#039;s practices of bundling Internet Explorer (and later, the Edge browser) with the Windows operating system, signing exclusive deals with original equipment manufacturers (OEM) to stifle competition, using [[wikipedia:Embrace,_extend,_and_extinguish|&amp;quot;embrace, extend, extinguish&amp;quot;]] tactics to eliminate competitors, and other incidents. Microsoft was also featured within the [[wikipedia:2010s_global_surveillance_disclosures|Snowden leaks]] as being engaged in mass surveillance through the PRISM program&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |date=July 11, 2011 |title=Snowden Reveals Microsoft PRISM Cooperation: Helped NSA Decrypt Emails, Chats, Skype Conversations |url=https://www.ibtimes.com/snowden-reveals-microsoft-prism-cooperation-helped-nsa-decrypt-emails-chats-skype-conversations |url-status=live |archive-url=https://web.archive.org/web/20250701125316/https://www.ibtimes.com/snowden-reveals-microsoft-prism-cooperation-helped-nsa-decrypt-emails-chats-skype-conversations |archive-date=2025-07-01 |access-date=2025-08-18 |website=International Business Times}}&amp;lt;/ref&amp;gt; and has been reported on for removing content from Bing to appease the Chinese government&amp;lt;ref&amp;gt;{{Cite web |last=Nicholas |first=Kristof |date=2009-11-20 |title=Boycott Microsoft Bing |url=http://kristof.blogs.nytimes.com/2009/11/20/boycott-microsoft-bing/ |url-status=dead |archive-url=https://web.archive.org/web/20091123194315/http://kristof.blogs.nytimes.com/2009/11/20/boycott-microsoft-bing/ |archive-date=2009-11-23 |access-date=2025-08-18 |website=The New York Times}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
Microsoft also has a rich and plentiful history of data breaches. Many services that Microsoft offers have been forcibly accessed into by malicious and white hat hackers.&amp;lt;ref&amp;gt;{{Cite web |last=Heiligenstein |first=Michael |date=2024-02-20 |title=Microsoft Data Breaches: Full Timeline Through 2024 |url=https://firewalltimes.com/microsoft-data-breach-timeline/ |url-status=live |archive-url=https://web.archive.org/web/20250502010658/https://firewalltimes.com/microsoft-data-breach-timeline/ |archive-date=2025-05-02 |access-date=2025-08-17 |website=Firewall Times}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Anti-competitive lawsuits==&lt;br /&gt;
&lt;br /&gt;
===US Department of Justice, U.S. v. Microsoft Corp. (1998-2001)===&lt;br /&gt;
In a major antitrust case brought by the &#039;&#039;US Department of Justice&#039;&#039;, &#039;&#039;U.S. v.&#039;&#039; Microsoft Corp&#039;&#039;&#039;&#039;&#039;.&#039;&#039;&#039;,&#039;&#039; 253 F.3d 34 (D.C. Cir. 2001)&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{Cite web |date=2001-06-28 |title=U.S. v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001) |url=https://law.justia.com/cases/federal/appellate-courts/F3/253/34/576095/ |url-status=live |archive-url=https://web.archive.org/web/20110413112825/https://law.justia.com/cases/federal/appellate-courts/F3/253/34/576095/ |archive-date=2011-04-13 |access-date=2025-08-19 |website=JUSTIA U.S. Law}}&amp;lt;/ref&amp;gt;, Microsoft argued that there was no barrier to entry in the market they operated in. A central issue at that time was whether Microsoft could bundle the web browser &#039;&#039;Internet Explorer&#039;&#039; with the Microsoft Windows operating system. The District Court stated the following in the court case:&amp;lt;blockquote&amp;gt;&amp;quot;The District Court condemned a number of provisions in Microsoft&#039;s agreements licensing Windows to OEMs, because it found that Microsoft&#039;s imposition of those provisions (like many of Microsoft&#039;s other actions at issue in this case) serves to reduce usage share of &#039;&#039;Netscape&#039;&#039;&amp;lt;nowiki/&amp;gt;&#039;s browser and, hence, protect Microsoft&#039;s operating system monopoly.&amp;quot;&amp;lt;/blockquote&amp;gt;The court specifically identified three main license restrictions for [[Original Equipment Manufacturers]] (OEMs) that were considered problematic:&lt;br /&gt;
&lt;br /&gt;
#The prohibition upon the removal of desktop icons, folders, and Start menu entries&lt;br /&gt;
#The prohibition of modifying the initial boot sequence&lt;br /&gt;
#The prohibition of otherwise altering the appearance of the Windows desktop&lt;br /&gt;
&lt;br /&gt;
The case was eventually settled&amp;lt;ref&amp;gt;[https://www.justice.gov/atr/case-document/file/503541/dl &amp;quot;Final judgment of US v. Microsoft&amp;quot;] - justice.gov - accessed 2025-01-29 ([http://web.archive.org/web/20250713154704/https://www.justice.gov/atr/case-document/file/503541/dl Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://law.justia.com/cases/federal/appellate-courts/F3/373/1199/474311/ &amp;quot;Commonwealth of Massachusetts, Ex Rel., Appellant, v. Microsoft Corporation&amp;quot;] - law.justia.com - accessed 2025-01-29 ([http://web.archive.org/web/20250813044241/https://law.justia.com/cases/federal/appellate-courts/F3/373/1199/474311/ Archived])&amp;lt;/ref&amp;gt; and did not result in a company breakup.&amp;lt;ref&amp;gt;[https://www.seattletimes.com/business/microsoft/long-antitrust-saga-ends-for-microsoft/ &amp;quot;Long antitrust saga ends for Microsoft&amp;quot;] - seattletimes.com - accessed 2025-01-29 ([http://web.archive.org/web/20251201140124/https://www.seattletimes.com/business/microsoft/long-antitrust-saga-ends-for-microsoft/ Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Section III.H of the Consent Decree&amp;lt;ref&amp;gt;[https://www.justice.gov/atr/microsoft-consent-decree-compliance-advisory-august-1-2003-us-v-microsoft &amp;quot;Microsoft Consent Decree Compliance Advisory - August 1, 2003 : U.S. V. Microsoft&amp;quot;] - justice.gov - accessed 2025-01-29 ([http://web.archive.org/web/20260211182935/https://www.justice.gov/atr/microsoft-consent-decree-compliance-advisory-august-1-2003-us-v-microsoft Archived])&amp;lt;/ref&amp;gt; required &#039;&#039;Microsoft&#039;&#039; to &amp;quot;allow end users and OEMs to enable or remove access to all middleware products­, including web browsers, e-mail clients, and media players ­through a readily accessible, centralized mechanism.&amp;quot; End users and Original Equipment Manufacturers should be able &amp;quot;to specify a non-Microsoft middleware product as the default middleware product to be launched in place of the corresponding Microsoft middleware product.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
In the case &#039;&#039;United States v.&#039;&#039; Microsoft Corp&#039;&#039;&#039;&#039;&#039;.&#039;&#039;&#039;,&#039;&#039; 87 F. Supp. 2d 30 (D.D.C. 2000),&amp;lt;ref&amp;gt;[https://law.justia.com/cases/federal/district-courts/FSupp2/87/30/2307082/ &amp;quot;United States v. Microsoft Corp., 87 F. Supp. 2d 30 (D.D.C. 2000)&amp;quot;] - law.justia.com - accessed 2025-01-29 ([http://web.archive.org/web/20250812193258/https://law.justia.com/cases/federal/district-courts/FSupp2/87/30/2307082/ Archived])&amp;lt;/ref&amp;gt; Microsoft&#039;s conduct in totality was described as a &amp;quot;deliberate assault upon entrepreneurial efforts that, could well have enabled the introduction of competition into the market for [[Intel]]-compatible PC operating systems&amp;quot;. Furthermore, &amp;quot;Microsoft&#039;s anti-competitive actions trammeled the competitive process through which the computer software industry generally stimulates innovation and conduces to the optimum benefit of consumers.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
====Summary of anti-competitive practices alleged in this lawsuit====&lt;br /&gt;
:*Slowing development of rival products like IBM and Apple through contractual or technical barriers.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |date=2002-01-25 |title=Competitive Processes, Anticompetitive Practices And Consumer Harm In The Software Industry: An Analysis Of The Inadequacies Of The Microsoft-Department Of Justice Proposed Final Judgment |url=https://www.justice.gov/atr/competitive-processes-anticompetitive-practices-and-consumer-harm-software-industry-analysis |url-status=live |archive-url=https://web.archive.org/web/20171115104834/https://www.justice.gov/atr/competitive-processes-anticompetitive-practices-and-consumer-harm-software-industry-analysis |archive-date=2017-11-15 |access-date=2025-08-23 |website=justice.gov |publisher=U.S. Department Of Justice}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
:*Overcharging consumers by $20–30 billion total for Windows licenses in the 1990s by hiding costs in PC bundles.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
:*Degrading interoperability of competing software (e.g., Java, Netscape) with Windows. &amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
:*Blocking rivals&#039; distribution channels by signing exclusive deals with PC manufacturers and ISPs. &amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Microsoft Corp. v Commission of the European Communities (2004-2007)===&lt;br /&gt;
The EU began an investigation of Microsoft in 1998 following a complaint by Sun Microsystems for not disclosing some interfaces to Windows NT. In August 2001, the EU expanded the investigation to look at how streaming media technology has been integrated into Windows.&amp;lt;ref&amp;gt;{{cite news |last=McCullagh |first=Declan |date=2002-07-01 |title=EU looks to wrap up Microsoft probe |url=http://www.news.com/2100-1001_3-941090.html |url-status=dead |archive-url=https://web.archive.org/web/20260222223326/https://www.cnet.com/news/ |archive-date=22 Feb 2026|access-date=2025-08-23 |work=CNET}}&amp;lt;/ref&amp;gt; Microsoft was found guilty of illegally abusing its dominant position in the operating system market&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{Cite web |date=2007-09-17 |title=EUR-Lex - 62004TJ0201 - Judgment of the Court of First Instance (Grand Chamber) of 17 September 2007. Microsoft Corp. v Commission of the European Communities. |url=https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:62004TJ0201 |url-status=live |archive-url=https://web.archive.org/web/20150725161632/https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:62004TJ0201 |archive-date=2015-07-25 |access-date=2025-08-21 |website=EUR-Lex}}&amp;lt;/ref&amp;gt; in order to dominate the entertainment market and push out competitors. It did this by bundling Windows Media Player with the Windows operating system, despite them being two distinct products, allowing &amp;quot;that media player automatically to achieve a level of market penetration corresponding to that of the dominant undertaking’s client PC operating system, without having to compete on the merits with competing products&amp;quot;.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The case was settled and Microsoft was fined €497 million ($613 million) - the largest fine issued by the EU for abuse of a dominant position at the time&amp;lt;ref&amp;gt;{{Cite web |date=2004-03-25 |title=Microsoft hit by record EU fine - CNN |url=http://www.cnn.com/2004/BUSINESS/03/24/microsoft.eu/ |url-status=dead |archive-url=https://web.archive.org/web/20060413082435/http://www.cnn.com/2004/BUSINESS/03/24/microsoft.eu/ |archive-date=2006-04-13 |website=CNN}}&amp;lt;/ref&amp;gt; - as well as having to provide a version of its Windows operating system without a bundled media player&amp;lt;ref name=&amp;quot;:7&amp;quot;&amp;gt;{{Cite web |date=2004-03-25 |title=Microsoft hit by record EU fine |url=http://www.cnn.com/2004/BUSINESS/03/24/microsoft.eu/ |url-status=dead |archive-url=https://web.archive.org/web/20060413082435/http://www.cnn.com/2004/BUSINESS/03/24/microsoft.eu/ |archive-date=2006-04-13 |access-date=2025-08-21 |website=CNN}}&amp;lt;/ref&amp;gt; (called Windows XP Home Edition N&amp;lt;ref name=&amp;quot;WinXPSRedmondMag2&amp;quot;&amp;gt;{{cite news |last=Bekker |first=Scot |date=2005-03-28 |title=European Windows Called &#039;Windows XP Home Edition N&#039; |url=http://www.redmondmag.com/news/article.asp?EditorialsID=6625 |url-status=dead |archive-url=https://web.archive.org/web/20050407081820/http://redmondmag.com/news/article.asp?EditorialsID=6625 |archive-date=2005-04-07 |access-date=2025-08-23 |publisher=Redmondmag.com}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;WinXPSBBC&amp;quot;&amp;gt;{{cite news |date=2005-03-28 |title=Microsoft and EU reach agreement |url=http://news.bbc.co.uk/2/hi/business/4388349.stm |url-status=live |archive-url=https://web.archive.org/web/20051222031525/http://news.bbc.co.uk/2/hi/business/4388349.stm |archive-date=2005-12-22 |access-date=2025-08-23 |publisher=BBC}}&amp;lt;/ref&amp;gt;). However, this ruling could be seen as insufficient to reduce Microsoft&#039;s monopolistic control as the company priced it the same as its bundled counterpart and the ruling didn&#039;t prevent them from selling Windows XP Home Edition. Consumer interest was low, and major Original Equipment Manufacturers did not pre-install Windows XP N on their computers&amp;lt;ref name=&amp;quot;WinXPlite&amp;quot;&amp;gt;{{cite news |last=Wearden |first=Graeme |date=2005-06-28 |title=Windows XP-lite &#039;not value for money&#039; |url=http://management.silicon.com/government/0,39024677,39131434,00.htm |url-status=dead |archive-url=https://web.archive.org/web/20051102014905/http://management.silicon.com/government/0%2C39024677%2C39131434%2C00.htm |archive-date=2005-11-02 |access-date=2025-08-23 |website=Silicon.com}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
See also: [[wikipedia:Microsoft_Corp._v_European_Commission|&#039;&#039;Microsoft Corp. v European Commission&#039;&#039; (Wikipedia)]]&lt;br /&gt;
&lt;br /&gt;
===JJH Enterprises Limited (trading as ValueLicensing) v Microsoft Corporation and Others (2021-ongoing)===&lt;br /&gt;
Valuelicensing, a UK reseller of software licenses, sued&amp;lt;ref&amp;gt;{{Cite web |date=2022-11-22 |title=JJH Enterprises Limited (trading as ValueLicensing) v Microsoft Corporation and Others |url=https://www.catribunal.org.uk/cases/15705722-t-jjh-enterprises-limited-trading-valuelicensing |url-status=live |archive-url=https://web.archive.org/web/20250219014502/https://www.catribunal.org.uk/cases/15705722-t-jjh-enterprises-limited-trading-valuelicensing |archive-date=2025-02-19 |access-date=2025-08-23 |website=Competition Appeal Tribunal}}&amp;lt;/ref&amp;gt; Microsoft for &amp;quot;suppressing the availability of preowned perpetual licences&amp;quot; and restricting customers from reselling old licenses in exchange for more favourable terms on newer, subscription-based models&amp;lt;ref&amp;gt;{{Cite news |last=Speed |first=Richard |date=2022-07-08 |title=Judge rejects another Microsoft appeal against surplus license reseller suit |url=https://www.theregister.com/2022/07/08/microsoft_valuelicensing/ |url-status=live |archive-url=https://web.archive.org/web/20220708112410/https://www.theregister.com/2022/07/08/microsoft_valuelicensing/ |archive-date=2022-07-08 |access-date=2025-08-23 |work=The Register}}&amp;lt;/ref&amp;gt;, claiming £270 million in damages&amp;lt;ref&amp;gt;{{Cite news |last=Speed |first=Richard |date=2021-04-08 |title=UK reseller sues Microsoft for £270m in damages claiming prohibitive contracts choke off surplus Office licence supplies |url=https://www.theregister.com/2021/04/08/valuelicensing_microsoft_lawsuit/ |url-status=live |archive-url=https://web.archive.org/web/20210408123252/https://www.theregister.com/2021/04/08/valuelicensing_microsoft_lawsuit/ |archive-date=2021-04-08 |access-date=2025-08-23 |work=The Register}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Ongoing UK lawsuit for overcharging users of non Azure cloud services===&lt;br /&gt;
UK lawsuit alleges &#039;&#039;Windows Servers&#039;&#039; users were overcharged when using non &#039;&#039;Azure &#039;&#039;cloud services.&amp;lt;ref&amp;gt;{{Cite web |last=Gerken |first=Tom |date=2024-12-03 |title=Microsoft faces £1bn class action case in UK over software prices |url=https://www.bbc.com/news/articles/c20wjnxr5ldo |url-status=live |archive-url=https://web.archive.org/web/20241203111042/https://www.bbc.com/news/articles/c20wjnxr5ldo |archive-date=2024-12-03 |access-date=2025-08-21 |website=BBC}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Facing EU and UK lawsuits, Microsoft settled with some cloud vendors but retained practices criticized as unfair.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Browne |first=Ryan |date=December 3, 2024 |title=Microsoft faces £1 billion lawsuit in UK for allegedly overcharging rival cloud firms’ customers |url=https://www.cnbc.com/2024/12/03/microsoft-overcharging-rival-cloud-firms-customers-uk-lawsuit-says.html |url-status=live |website=cnbc.com |archive-url=http://web.archive.org/web/20260104142642/https://www.cnbc.com/2024/12/03/microsoft-overcharging-rival-cloud-firms-customers-uk-lawsuit-says.html |archive-date=4 Jan 2026}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Antitrust investigation by U.S.===&lt;br /&gt;
Making it costly or technically difficult for customers to migrate data from Azure to other platforms.&amp;lt;ref&amp;gt;{{Cite web |last=Godoy |first=Jody |date=November 28, 2024 |title=Microsoft faces wide-ranging US antitrust probe |url=https://www.reuters.com/technology/microsoft-faces-wide-ranging-us-antitrust-probe-2024-11-27/ |website=reuters.com |archive-url=http://web.archive.org/web/20250721011825/https://www.reuters.com/technology/microsoft-faces-wide-ranging-us-antitrust-probe-2024-11-27/ |archive-date=21 Jul 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Anti-competitive incidents&amp;lt;!-- Please try to keep this table organized in chronological order! - JamesTDG --&amp;gt;==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
!Incident&lt;br /&gt;
!Date Started - Date Ended (if applicable)&lt;br /&gt;
!Incident summary&lt;br /&gt;
!Related Product&lt;br /&gt;
!Related article (if applicable)&lt;br /&gt;
|-&lt;br /&gt;
|Taking down Minecraft competitors&lt;br /&gt;
|2019 - Present&lt;br /&gt;
|Microsoft has submitted various takedowns on games that compete against [[Minecraft]],&amp;lt;ref&amp;gt;{{Cite web |last=Maxwell |first=Andy |date=September 1, 2019 |title=Microsoft Puts Blocks On In-Browser Minecraft Clone |url=https://torrentfreak.com/microsoft-puts-blocks-on-in-browser-minecraft-clone-190831/ |access-date=Feb 10, 2026 |website=Torrent Freak |archive-url=http://web.archive.org/web/20260215012038/https://torrentfreak.com/microsoft-puts-blocks-on-in-browser-minecraft-clone-190831/ |archive-date=15 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Mazeriio |date=Feb 10, 2026 |title=Tweet from Mazeriio |url=https://nitter.us.catsarch.com/Mazeriio/status/2021128578742513930 |url-status=live |archive-url=https://web.archive.org/web/20260321121352/https://nitter.us.catsarch.com/Mazeriio/status/2021128578742513930 |archive-date=21 Mar 2026 |access-date=Feb 10, 2026 |website=X formerly [[Twitter]]}}&amp;lt;/ref&amp;gt; which unfairly thins out competition against the game.&lt;br /&gt;
|[[Minecraft]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Prompts to stop users from installing competing browsers&lt;br /&gt;
|2021 - Present&lt;br /&gt;
|Users attempting to install other web browsers, such as &#039;&#039;[[Google Chrome|Chrome]], [[Brave browser|Brave]], or [[Opera web browser|Opera]],&#039;&#039; will face a pop-up on their screen telling users to instead use [[Microsoft Edge|Edge]].&amp;lt;ref&amp;gt;{{Cite web |last=Warren |first=Tom |date=2021-12-02 |title=Microsoft’s new Windows prompts try to stop people downloading Chrome |url=https://www.theverge.com/2021/12/2/22813733/microsoft-windows-edge-download-chrome-prompts |url-status=live |archive-url=https://web.archive.org/web/20211202114904/https://www.theverge.com/2021/12/2/22813733/microsoft-windows-edge-download-chrome-prompts |archive-date=2021-12-02 |access-date=2025-08-22 |website=The Verge}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Sen |first=Sayan |date=2021-12-02 |title=Microsoft says its own Edge browser is more trustworthy than &amp;quot;so 2008&amp;quot; Google Chrome |url=https://www.neowin.net/news/microsoft-says-its-own-edge-browser-is-more-trustworthy-than-so-2008-google-chrome/ |url-status=live |archive-url=https://web.archive.org/web/20211202081952/https://www.neowin.net/news/microsoft-says-its-own-edge-browser-is-more-trustworthy-than-so-2008-google-chrome/ |archive-date=2021-12-02 |access-date=2025-08-22 |website=Neowin}}&amp;lt;/ref&amp;gt; It has been reported to occur on devices running either &#039;&#039;[[Windows|Windows 10]]&#039;&#039; or &#039;&#039;[[Windows|Windows 11]],&amp;lt;ref&amp;gt;{{Cite web |last=Hollister |first=Sean |date=2023-10-25 |title=Microsoft now thirstily injects a poll when you download Google Chrome |url=https://www.theverge.com/23930960/microsoft-edge-google-chrome-poll-why-try-another-browser |archive-url=https://web.archive.org/web/20231025001842/https://www.theverge.com/23930960/microsoft-edge-google-chrome-poll-why-try-another-browser |archive-date=2023-10-25 |access-date=2025-08-22 |website=The Verge}}&amp;lt;/ref&amp;gt;&#039;&#039; which harms the market share of [[Google Chrome|Chrome]], despite [[Microsoft Edge|Edge]] being based on &#039;&#039;[[Chromium]]&#039;&#039;.&lt;br /&gt;
|[[Microsoft Edge]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Bing search attempting to harm competing search engines&lt;br /&gt;
|2023 - Present&lt;br /&gt;
|When doing a web search for an alternative web browser through &#039;&#039;[[Microsoft Bing|Bing]]&#039;&#039;, &#039;&#039;[[Microsoft]]&#039;&#039;&amp;lt;nowiki/&amp;gt;&#039;s in-house developed search engine that is also used as the default for &#039;&#039;[[Microsoft Edge|Edge]]&#039;&#039;, the search engine&#039;s AI will attempt to bury the search results for the web browser from the user.&amp;lt;ref&amp;gt;{{Cite news |last=Hollister |first=Sean |date=Jun 6, 2023 |title=Microsoft has no shame: Bing spit on my ‘Chrome’ search with a fake AI answer |url=https://www.theverge.com/2023/6/6/23736289/microsoft-bing-chrome-search-fake-ai-chatbot |access-date=Jun 21, 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111203332/https://www.theverge.com/2023/6/6/23736289/microsoft-bing-chrome-search-fake-ai-chatbot |archive-date=11 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Purged text, include ONLY when a verifiable, trustworthy source reports on this.&lt;br /&gt;
&lt;br /&gt;
Beyond this, users specifically using both Edge and its default search engine will continue to see notices at the top of the search, attempting to keep the user on the browser. --&amp;gt;&lt;br /&gt;
|[[Bing]], [[Microsoft Edge]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Bing disguising itself as another search engine&lt;br /&gt;
|2025 - Present&lt;br /&gt;
|Currently, when a user does a web search for &amp;quot;[[Google]]&amp;quot;, the search engine will disguise itself as a generic search engine that would appear to look like Google in the eyes of the average user.&amp;lt;ref&amp;gt;{{Cite news |last=Warren |first=Tom |date=Jan 6, 2025 |title=Microsoft is using Bing to trick people into thinking they’re on Google |url=https://www.theverge.com/2025/1/6/24337117/microsoft-bing-search-results-google-design-trick |access-date=Jun 21, 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111203330/https://www.theverge.com/2025/1/6/24337117/microsoft-bing-search-results-google-design-trick |archive-date=11 Jan 2026}}&amp;lt;/ref&amp;gt;&amp;lt;!--I want to see more elaboration here - JamesTDG--&amp;gt;&lt;br /&gt;
|[[Bing]]&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Anti-consumer incidents==&lt;br /&gt;
&lt;br /&gt;
===Failure to handle quality assurance&amp;lt;!-- The main article will cover mostly the QA failures of Windows 11 causing fatal problems for hardware, but things such as the RROD on the 360, and other incident-worthy flaws will likely be moved under this main article. --&amp;gt;===&lt;br /&gt;
{{Main|Microsoft&#039;s quality assurance failures}}&lt;br /&gt;
Microsoft has had an extensive history when it comes to failing to maintain the quality of its products.&amp;lt;!-- Will handle writing later, out of time... --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Windows 3.1 AARD code===&lt;br /&gt;
[[File:Windows 3.10.068 setup AARD code.png|alt=Windows 3.1 beta setup with a gray square in the middle in red text coloring that says &amp;quot;Non-fatal error detected: error #4D53 (Please contact Windows 3.1 beta support.). Press ENTER to continue&amp;quot;|thumb|Windows 3.1 AARD code]]&lt;br /&gt;
Users attempting to install a beta release of Windows 3.1 on a machine running [[wikipedia:DR-DOS|DR-DOS]] would receive an error message stating &amp;quot;&#039;&#039;&#039;Non-fatal error detected: error #4D53 (Please contact Windows 3.1 beta support)&#039;&#039;&#039;&amp;quot;. The error code was discovered by Geoff Chappell on April 17 1992.&amp;lt;ref&amp;gt;{{Cite web |last=Chappell |first=Geoff |date=8 May 1999 |title=AARD code |url=https://www.geoffchappell.com/notes/windows/archive/aard/index.htm?tx=57 |url-status=live |archive-url=https://web.archive.org/web/20240112155815/https://www.geoffchappell.com/notes/windows/archive/aard/index.htm?tx=57 |archive-date=12 Jan 2024 |access-date=16 Aug 2025 |website=Geoff Chappell, Software Analyst}}&amp;lt;/ref&amp;gt; DR DOS was capable of running Windows 3.1 as it is compatible with MS-DOS, but the AARD code in the installer used undocumented structures to detect if the machine was running DR DOS in order to display this message. The rationale was to pressure the user into buying MS-DOS: &amp;quot;What the [user] is supposed to do is feel uncomfortable, and when he has bugs, suspect that the problem is DR-DOS and then go out to buy MS-DOS,&amp;quot; wrote Brad Silverberg, the senior vice president of Microsoft at the time,  in a 1992 email.&amp;lt;ref&amp;gt;{{Cite news |date=2002-01-02 |title=Microsoft emails focus on DR-DOS threat |url=https://www.cnet.com/news/microsoft-emails-focus-on-dr-dos-threat/ |url-status=dead |archive-url=https://web.archive.org/web/20160310065721/https://www.cnet.com/news/microsoft-emails-focus-on-dr-dos-threat/ |archive-date=2016-03-10 |access-date=2025-08-30 |work=CNET}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
===Inactive account deletions===&lt;br /&gt;
Microsoft has a [[Inactive account deletion|deletion policy on inactive accounts]] in which accounts that are not used for 2 years or more may be scheduled to be deleted. Any account that has been locked for more than two years will also be considered &amp;quot;inactive&amp;quot; and will be closed. Before the deletion of the inactive account, users may get an email or text message warning that their account is scheduled to be deleted. 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.&amp;lt;ref&amp;gt;https://support.microsoft.com/en-us/topic/microsoft-account-activity-policy-7c0a9fa7-0982-b7c6-fd72-df852b63699f ([http://web.archive.org/web/20260125105026/https://support.microsoft.com/en-us/topic/microsoft-account-activity-policy-7c0a9fa7-0982-b7c6-fd72-df852b63699f Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Exceptions====&lt;br /&gt;
&lt;br /&gt;
The following are the exceptions to the inactive account deletion policy as provided by Microsoft:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Purchases&#039;&#039;&#039;: If you have used your Microsoft account to purchase, or to redeem or access a purchase of, a current Microsoft product or service, your Microsoft account will remain active and Microsoft will not close your account due to inactivity. Note, this does not apply to gift cards, certifications or subscription-based purchases or services.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Subscriptions&#039;&#039;&#039;: Your Microsoft account will continue to remain active for so long as you have an active Microsoft subscription associated with your Microsoft account. Following the expiration or termination of the subscription, you must sign in to your Microsoft account at least once in a two-year period to keep your account active.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Publishing to the Microsoft Store&#039;&#039;&#039;: If you have used your Microsoft account to publish applications or games (including game DLCs) to the Microsoft Store or to register for a Microsoft Partner Center account, your Microsoft account will remain active and Microsoft will not close your account due to inactivity.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Certifications&#039;&#039;&#039;: If you earn a certification from Microsoft using your Microsoft account, your Microsoft account will remain active and Microsoft will not close your account due to inactivity.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Account Balance&#039;&#039;&#039;: Your Microsoft account will continue to remain active for so long as you have an unspent balance in your Microsoft account (e.g. from a Microsoft gift card or a credit from Microsoft). If you live in a jurisdiction where gift cards are considered “unclaimed property,” Microsoft will, pursuant to local law, escheat the unspent balance associated with your Microsoft gift card.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Accounts Payable&#039;&#039;&#039;: Your Microsoft account will continue to remain active for so long as there is an amount owed to you by Microsoft associated with your Microsoft account (e.g. amounts due to you from Microsoft Payment Central).&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Family Accounts&#039;&#039;&#039;:  If you have an inactive Microsoft account that has granted consent for an active Microsoft account belonging to a minor, Microsoft will not close your Microsoft account due to your inactivity. Your inactive Microsoft account will be kept open by Microsoft until the minor’s account (i) is deemed inactive and closed by Microsoft, (ii) is closed by you, or (iii) transitions into a standard Microsoft account when the minor reaches the requisite age of majority in their region.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Legal Requirements or as otherwise provided by Microsoft&#039;&#039;&#039;: Notwithstanding the foregoing, Microsoft reserves the right to maintain your account status as active, or not to close an inactive account, as required by applicable law or regulation, or as otherwise provided by Microsoft to you.&lt;br /&gt;
&lt;br /&gt;
===Edge===&lt;br /&gt;
{{Main|Microsoft Edge}}&lt;br /&gt;
&#039;&#039;Microsoft Edge&#039;&#039;(&#039;&#039;Edge&#039;&#039;) is a &#039;&#039;[[Chromium]]&#039;&#039;-based &amp;lt;ref&amp;gt;{{Cite web |last=Tung |first=Liam |date=2020-06-03 |title=Windows 10: Microsoft begins automatically pushing Chromium Edge to users |url=https://www.zdnet.com/article/windows-10-microsoft-begins-automatically-pushing-chromium-edge-to-users/ |url-status=live |archive-url=https://web.archive.org/web/20200603160238/https://www.zdnet.com/article/windows-10-microsoft-begins-automatically-pushing-chromium-edge-to-users/ |archive-date=2020-06-03 |access-date=2025-08-21 |website=ZDNET}}&amp;lt;/ref&amp;gt; web browser that comes preinstalled with Windows 10 and later. It is the successor to &#039;&#039;IE&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
====Resetting primary browser (2017-present)====&lt;br /&gt;
Windows has frequently been resetting the default browser to &#039;&#039;Edge&#039;&#039; without consent.{{Citation needed|reason=old link dead}} While there are methods to disable this,&amp;lt;ref&amp;gt;[https://www.reddit.com/r/techsupport/comments/15zbjar/default_browser_keeps_changing_to_microsoft_edge/ &amp;quot;Default browser keeps changing to Microsoft Edge after every PC restart. Win 11, tried everything&amp;quot;] - reddit.com - accessed 2025-01-29 ([http://web.archive.org/web/20230911115100/https://old.reddit.com/r/techsupport/comments/15zbjar/default_browser_keeps_changing_to_microsoft_edge/ Archived])&amp;lt;/ref&amp;gt; it is tedious to achieve, especially for users who are not tech-savvy.&lt;br /&gt;
&lt;br /&gt;
====Inability to delete (2018-present)====&lt;br /&gt;
During major updates for &#039;&#039;Windows&#039;&#039;, users have been reporting their installations of &#039;&#039;Edge&#039;&#039; being reinstalled to their devices without their consent.&amp;lt;ref&amp;gt;&lt;br /&gt;
{{Cite web&lt;br /&gt;
| last=Huculak&lt;br /&gt;
| first=Mauro&lt;br /&gt;
| title=How to prevent new Microsoft Edge from installing automatically on Windows 10&lt;br /&gt;
| url=https://www.windowscentral.com/how-prevent-microsoft-edge-chromium-installing-automatically-windows-10&lt;br /&gt;
| website=windowscentral.com&lt;br /&gt;
| access-date=2025-01-29&lt;br /&gt;
| date=2020-06-05&lt;br /&gt;
| archive-url=http://web.archive.org/web/20250917184020/https://www.windowscentral.com/how-prevent-microsoft-edge-chromium-installing-automatically-windows-10&lt;br /&gt;
| archive-date=2025-09-17&lt;br /&gt;
| url-status=live&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Importing content from other browsers (2020-?)====&lt;br /&gt;
Users have reported on frequent occasions that Edge has imported user data from browsers such as &#039;&#039;Chrome&#039;&#039; and &#039;&#039;Firefox&#039;&#039; without first requesting consent from the user.&amp;lt;ref&amp;gt;{{Cite web |last=Komando |first=Kim |date=2020-07-01 |title=Microsoft caught importing data before you give the OK |url=https://www.komando.com/news/microsoft-edge-caught-importing-data/ |url-status=dead |archive-url=https://web.archive.org/web/20241213192319/https://www.komando.com/news/microsoft-edge-caught-importing-data/ |archive-date=2024-12-13 |access-date=2025-08-22 |website=KIMKOMANDO}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Could we get another source added here? --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Pressuring users into using Edge (2020-?)====&lt;br /&gt;
In 2020, users for [[Windows|Windows 10]] faced repeated harassment from Edge to use this browser instead of the user&#039;s chosen default browser.&amp;lt;ref&amp;gt;{{Cite web |last=Hollister |first=Sean |date=2020-07-02 |title=Microsoft just sank to a new low by shoving Edge down our throats |url=https://www.theverge.com/21310611/microsoft-edge-browser-forced-update-chromium-editorial |url-status=live |archive-url=https://web.archive.org/web/20200702205823/https://www.theverge.com/21310611/microsoft-edge-browser-forced-update-chromium-editorial |archive-date=2020-07-02 |access-date=2025-08-22 |website=The Verge}}&amp;lt;/ref&amp;gt; Some examples included the browser opening on startup, the browser being forced into full screen, being incapable of closing the browser until the user acknowledges the pop-up, and the browser pinning itself to the taskbar.&amp;lt;ref&amp;gt;{{Cite web |date=2026-01-01 |title=Every trick Microsoft pulled to make you browse Edge instead of Chrome |url=https://www.theverge.com/23935029/microsoft-edge-forced-windows-10-google-chrome-fight |url-status=live |website=The Verge}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Removal of &#039;&#039;365&#039;&#039; features to push &#039;&#039;Copilot (2025)&#039;&#039;====&lt;br /&gt;
Eliminated key search features in &#039;&#039;365&#039;&#039;&amp;lt;ref&amp;gt;{{Cite web |last=Laplante |first=Martin |date=2025-10-09 |title=Microsoft Search’s Disappearing Act |url=https://www.pointfire.com/blogs/microsoft-searchs-disappearing-act |url-status=live |website=pointfire}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Endicott |first=Sean |date=2025-01-22 |title=I&#039;m aghast, stunned, and flabbergasted that Microsoft just removed the thesaurus from Word |url=https://www.windowscentral.com/software-apps/im-aghast-stunned-and-flabbergasted-that-microsoft-just-removed-the-thesaurus-from-word |url-status=live |website=Windows Central}}&amp;lt;/ref&amp;gt;, forcing users to pay $30/month for &#039;&#039;Copilot&#039;&#039; access, sparking backlash from businesses and educators.{{Citation needed}} The FTC and DOJ are reportedly investigating, with Elon Musk alleging antitrust violations in its &#039;&#039;OpenAI&#039;&#039; partnership.&amp;lt;ref&amp;gt;{{Cite web |last=Scarcella |first=Mike |date=2024-11-15 |title=Musk expands lawsuit against OpenAI, adding Microsoft and antitrust claims |url=https://www.reuters.com/technology/musk-expands-lawsuit-against-openai-adding-microsoft-antitrust-claims-2024-11-15/ |url-status=live |website=Reuters}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Increasing the difficulty to switch default browsers (2021 - Present)====&lt;br /&gt;
After an update in 2021, computers running &#039;&#039;[[Windows 11]]&#039;&#039; had the systems that handled modifying the web browser defaults.&amp;lt;ref name=&amp;quot;:03&amp;quot;&amp;gt;{{Cite news |last=Warren |first=Tom |date=Aug 18, 2021 |title=Microsoft is making it harder to switch default browsers in Windows 11 |url=https://www.theverge.com/22630319/microsoft-windows-11-default-browser-changes |access-date=Jun 21, 2025 |work=The Verge |archive-url=http://web.archive.org/web/20251209162923/https://www.theverge.com/22630319/microsoft-windows-11-default-browser-changes |archive-date=9 Dec 2025}}&amp;lt;/ref&amp;gt; Rather than allow the user to simply switch the default web browser, file types typically accessed via web browsers, such as HTM, HTML, SVG, and more have to be individually modified to have the default opening application changed. This has angered companies maintaining competing web browsers&amp;lt;ref name=&amp;quot;:03&amp;quot; /&amp;gt;&amp;lt;!--If we can get the notes feature added, this should be a useful note to include:&lt;br /&gt;
&lt;br /&gt;
“We have been increasingly worried about the trend on Windows,” says Selena Deckelmann, senior vice president of Firefox, in a statement to The Verge. “Since Windows 10, users have had to take additional and unnecessary steps to set and retain their default browser settings. These barriers are confusing at best and seem designed to undermine a user’s choice for a non-Microsoft browser.”--&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Lockheimer |first=Hiroshi |date=Aug 18, 2021 |title=Tweet from Hiroshi Lockheimer |url=https://nitter.us.catsarch.com/lockheimer/status/1428047760620621831 |url-status=live |archive-url=https://megalodon.jp/2026-0321-2130-35/https://nitter.us.catsarch.com:443/lockheimer/status/1428047760620621831 |archive-date=21 Mar 2026 |access-date=Jun 21, 2025 |website=X, formerly [[Twitter]]}}&amp;lt;/ref&amp;gt; and consumers alike over this change. Even if users modify all of these default settings, other features on the device, such as the taskbar&#039;s weather widget, which if opened, will create a new tab specifically in &#039;&#039;[[Microsoft Edge|Edge]]&#039;&#039;.&amp;lt;ref name=&amp;quot;:03&amp;quot; /&amp;gt;&amp;lt;!--Another note to add under [39]&lt;br /&gt;
&lt;br /&gt;
Windows 11 continues this trend, with search still forcing users into Edge, and now a new dedicated widgets area that also ignores the default browser setting. “It appears that Windows 11 widgets will ignore a user’s default browser choice and open Microsoft Edge for the content instead,” says a Brave spokesperson in a statement to The Verge. “Brave puts users first and we condemn this Windows 11 approach, because the choice of a default browser has many implications for individuals and their privacy. Users should be free to choose.”--&amp;gt;Microsoft attempts to justify this by stating:&amp;lt;ref name=&amp;quot;:03&amp;quot; /&amp;gt;&amp;lt;blockquote&amp;gt;“With Windows 11, we are implementing customer feedback to customize and control defaults at a more granular level, eliminating app categories and elevating all apps to the forefront of the defaults experience,” “As evidenced by this change, we’re constantly listening and learning, and welcome customer feedback that helps shape Windows. Windows 11 will continue to evolve over time; if we learn from user experience that there are ways to make improvements, we will do so.”&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Minecraft===&lt;br /&gt;
{{Main|Minecraft account migration}}&lt;br /&gt;
Following Microsoft&#039;s acquisition of Minecraft, they have started forcing account migration to users who already had a Mojang account to a Microsoft account. The company gave users a grace period for account migration, after which users would have to purchase Minecraft again if the Mojang account was not migrated.&amp;lt;ref&amp;gt;https://help.minecraft.net/hc/en-us/articles/19633473939981-I-Missed-My-Chance-to-Migrate-What-Happens-to-My-Account ([http://web.archive.org/web/20250716045613/https://help.minecraft.net/hc/en-us/articles/19633473939981-I-Missed-my-Chance-to-Migrate-What-Happens-to-my-Account Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Office 365 Suite===&lt;br /&gt;
{{Main|Microsoft Office 365}}&lt;br /&gt;
The Office 365 program has been facing a number of issues in recent years, with allegations of forced upsell and forced implementation of OneDrive. &lt;br /&gt;
&lt;br /&gt;
===Microsoft Windows===&lt;br /&gt;
&#039;&#039;Main article: [[Microsoft Windows]]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
====Telemetry====&lt;br /&gt;
Windows 10 and 11 are configured to send telemetry by default&amp;lt;ref&amp;gt;{{Cite web |last=Bott |first=Ed |date=2026-03-03 |title=I&#039;ve been studying Windows telemetry for a decade - here&#039;s the only setting I turn off |url=https://www.zdnet.com/article/microsoft-spying-windows-telemetry/ |url-status=live |website=zdnet}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Bingham |first=Brock |date=2026-03-23 |title=How to disable Windows telemetry |url=https://www.pdq.com/blog/how-to-disable-windows-telemetry/ |url-status=live |website=PDQ}}&amp;lt;/ref&amp;gt;, and users may only switch it to a reduced mode, without actually being able to easily disable it&amp;lt;ref name=&amp;quot;:8&amp;quot;&amp;gt;{{Cite web |date=2022-05-04 |title=Deaktivierung der Telemetriekomponente in Windows 10 21H2 |url=https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Cyber-Sicherheit/SiSyPHus/E20172000_BSI_Win10_AFUNKT_TELE_DEAKTIVIEREN_v1_0.pdf?__blob=publicationFile&amp;amp;v=6 |url-status=live |access-date=2026-04-06 |website=https://www.bsi.bund.de}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2021-08-11 |title=Enable or Disable Send Required and Optional Diagnostic Data for Windows 11 |url=https://www.elevenforum.com/t/enable-or-disable-send-required-and-optional-diagnostic-data-for-windows-11.2621/ |url-status=live |access-date=2026-04-06 |website=https://www.elevenforum.com}}&amp;lt;/ref&amp;gt;. Only certain editions like the Enterprise version have options to switch it off&amp;lt;ref&amp;gt;{{Cite web |last=Ruparelia |first=Arjun |date=2022-01-01 |title=How to Disable Telemetry on Windows 10 and 11 |url=https://www.makeuseof.com/windows-10-11-disable-telemetry/ |url-status=live |website=Make Use Of}}&amp;lt;/ref&amp;gt;, but a study conducted by the German ministry of information security in 2018 suggests that even this does not stop telemetry data collection completely&amp;lt;ref name=&amp;quot;:8&amp;quot; /&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Telemetry covers a wide variety of system information as well as a multitude of user interactions. Microsoft can configure remotely which and how much data and is collected from a particular system&amp;lt;sup&amp;gt;[&#039;&#039;[[Consumer Rights Wiki:Verifiability|citation needed]]&#039;&#039;]&amp;lt;/sup&amp;gt;. This can go up to a level where all key presses are transmitted in real time{{Citation needed}}. This makes telemetry very intransparent and difficult to monitor since the kind of data being collected could change at any moment without notice.&amp;lt;sup&amp;gt;[&#039;&#039;[[Consumer Rights Wiki:Verifiability|citation needed]]&#039;&#039;]&amp;lt;/sup&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Windows 10====&lt;br /&gt;
The release of Windows 10 in 2015 marked a decade of taking away user choice through forced updates, resetting user preferences, and [[Forced app download|forced software installation.]]&amp;lt;ref&amp;gt;{{Cite web |last=Hruska |first=Joel |date=30 Jul 2015 |title=Windows 10&#039;s default privacy settings and controls leave much to be desired |url=https://www.extremetech.com/extreme/211208-windows-10s-default-privacy-settings-and-controls-leave-much-to-be-desired |website=ExtremeTech |archive-url=http://web.archive.org/web/20260222104027/https://www.extremetech.com/extreme/211208-windows-10s-default-privacy-settings-and-controls-leave-much-to-be-desired |archive-date=22 Feb 2026}}&amp;lt;/ref&amp;gt; Updates would be automatically scheduled when the computer is inactive, &amp;lt;ref&amp;gt;[https://www.crn.com/news/applications-os/300077576/did-microsoft-just-backtrack-on-forced-updates-for-windows-10 &amp;quot;Did Microsoft Just Backtrack On Forced Updates For Windows 10?&amp;quot;] - crn.com - accessed 2025-01-29 ([http://web.archive.org/web/20251126094745/https://www.crn.com/news/applications-os/300077576/did-microsoft-just-backtrack-on-forced-updates-for-windows-10 Archived])&amp;lt;/ref&amp;gt; leading to some systems being rendered unusable because of bugged updates that cannot be avoided.&amp;lt;ref&amp;gt;[https://www.tomsguide.com/news/windows-10-update-is-bricking-pcs-uninstall-this-right-now &amp;quot;Windows 10 update is &#039;breaking&#039; PCs — what to do now&amp;quot;] - tomsguide.com - accessed 2025-01-29 ([http://web.archive.org/web/20260212180250/https://www.tomsguide.com/news/windows-10-update-is-bricking-pcs-uninstall-this-right-now Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://answers.microsoft.com/en-us/windows/forum/all/windows-update-bricked-my-bios-thought-to-be/a1f0ebc7-d20d-459f-9956-72a3f98ca432 &amp;quot;Windows update bricked my bios ?? Thought to be impossible ?&amp;quot;] - answers.microsoft.com - accessed 2025-01-29 ([http://web.archive.org/web/20250708171954/https://answers.microsoft.com/en-us/windows/forum/all/windows-update-bricked-my-bios-thought-to-be/a1f0ebc7-d20d-459f-9956-72a3f98ca432 Archived])&amp;lt;/ref&amp;gt; Some updates would force changes on preferences set by the user for various applications and settings.&amp;lt;ref&amp;gt;[https://www.reddit.com/r/Windows10/comments/n1hoz0/windows_please_stop_changing_my_settings_with/ &amp;quot;Windows: PLEASE STOP CHANGING MY SETTINGS WITH UPDATES&amp;quot;] - reddit.com - accessed 2025-01-29 ([http://web.archive.org/web/20210429235550/https://old.reddit.com/r/Windows10/comments/n1hoz0/windows_please_stop_changing_my_settings_with/ Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://answers.microsoft.com/en-us/windows/forum/all/windows-10-updated-and-reset-all-of-my-settings/529ffb03-edd4-4be2-9412-50e3271fa8fe &amp;quot;Windows 10 updated and reset all of my settings and preferences.&amp;quot;] - answers.microsoft.com - 2025-01-29 ([http://web.archive.org/web/20250708171948/https://answers.microsoft.com/en-us/windows/forum/all/windows-10-updated-and-reset-all-of-my-settings/529ffb03-edd4-4be2-9412-50e3271fa8fe Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://www.minitool.com/news/windows-settings-are-reset-after-reboot.html &amp;quot;Windows Settings Are Reset After Reboot? Best Fixes Here!&amp;quot;] - minitool.com - accessed 2025-01-29 ([http://web.archive.org/web/20260219115001/https://www.minitool.com/news/windows-settings-are-reset-after-reboot.html Archived])&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Additionally, Microsoft Windows installs software, such as Candy Crush, on computers that the user did not ask for.&amp;lt;ref&amp;gt;{{Cite web |last=Moscaritolo |first=Angela |date=2015-05-15 |title=Windows 10 Will Come With Candy Crush Saga Pre-Installed |url=https://www.pcmag.com/news/windows-10-will-come-with-candy-crush-saga-pre-installed |url-status=live |website=PCMag}}&amp;lt;/ref&amp;gt; This may also force users to agree to licensing terms, for instance when interacting with forcibly installed software to remove it.{{Citation needed}}   &lt;br /&gt;
&lt;br /&gt;
When &#039;&#039;Windows&#039;&#039; &#039;&#039;10&#039;&#039; is installed from the ISO that can be downloaded from Microsoft, the EULA explicitly mentions forced arbitration.&amp;lt;ref&amp;gt;{{Cite web |title=Microsoft Software License Terms |url=https://www.microsoft.com/content/dam/microsoft/usetm/documents/windows/10/oem-pre-installed/UseTerms_OEM_Windows_10_English.pdf |url-status=live |archive-url=https://web.archive.org/web/20250729194240/https://www.microsoft.com/content/dam/microsoft/usetm/documents/windows/10/oem-pre-installed/UseTerms_OEM_Windows_10_English.pdf |archive-date=2025-07-29 |access-date=2025-08-11 |page=6 |quote=&amp;quot;If we can’t [informally resolve a dispute], you and we agree to binding individual arbitration before the American Arbitration Association (“AAA”) under the Federal Arbitration Act (“FAA”), and not to sue in court in front of a judge or jury.&amp;quot;}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Windows 11====&lt;br /&gt;
{{Main|Microsoft Windows 11}}&lt;br /&gt;
&lt;br /&gt;
=====TPM 2.0 chip requirements=====&lt;br /&gt;
{{see also|Trusted computing}}&lt;br /&gt;
Microsoft updated their system requirements to include &#039;&#039;Trusted Platform Module 2.0&#039;&#039; (TPM) support as a mandatory requirement for upgrading to &#039;&#039;[[Windows 11]]&#039;&#039;. This would require either a TPM-compatible CPU, or a separate TPM-dedicated chip to be installed on the motherboard, however some users were able to circumvent this requirement by editing the registry.&amp;lt;ref&amp;gt;[https://www.starwindsoftware.com/blog/bypass-tpm-and-install-windows-11-on-unsupported-hardware/ &amp;quot;Bypass TPM and Install Windows 11 on Unsupported Hardware&amp;quot;] - starwindsoftware.com - accessed 2025-01-29 ([http://web.archive.org/web/20250930121420/https://www.starwindsoftware.com/blog/bypass-tpm-and-install-windows-11-on-unsupported-hardware/ Archived])&amp;lt;/ref&amp;gt; This change resulted in many customers selling or discarding their otherwise functional computers and hardware that did not meet the new system requirements.&amp;lt;ref&amp;gt;[https://securityonline.info/windows-11s-tpm-2-0-free-software-foundation-fights-forced-upgrades-and-e-waste/ &amp;quot;Windows 11’s TPM 2.0: Free Software Foundation Fights Forced Upgrades and E-Waste&amp;quot;] - securityonline.info - accessed 2025-01-29 ([http://web.archive.org/web/20250708171949/https://securityonline.info/windows-11s-tpm-2-0-free-software-foundation-fights-forced-upgrades-and-e-waste/ Archived])&amp;lt;/ref&amp;gt; Microsoft has been frequently reminding users of &#039;&#039;[[Windows|Windows 10]]&#039;&#039; to upgrade their hardware to be compatible with &#039;&#039;[[Windows 11]]&#039;&#039;,&amp;lt;ref&amp;gt;[https://www.pcmag.com/news/microsoft-revives-pop-ups-in-windows-10-to-push-windows-11-upgrades &amp;quot;Microsoft Revives Pop-Ups in Windows 10 to Push Windows 11 Upgrades&amp;quot;] - pcmag.com - accessed 2025-01-29 ([http://web.archive.org/web/20260215005212/https://www.pcmag.com/news/microsoft-revives-pop-ups-in-windows-10-to-push-windows-11-upgrades Archived])&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://www.techradar.com/computing/windows/microsoft-embarrasses-itself-with-windows-10-pop-up-that-hogs-the-desktop-urging-an-upgrade-to-windows-11-then-promptly-crashes &amp;quot;Microsoft embarrasses itself with Windows 10 pop-up that hogs the desktop urging an upgrade to Windows 11 – then promptly crashes&amp;quot;] - techradar.com - accessed 2025-01-29 ([http://web.archive.org/web/20251224021647/https://www.techradar.com/computing/windows/microsoft-embarrasses-itself-with-windows-10-pop-up-that-hogs-the-desktop-urging-an-upgrade-to-windows-11-then-promptly-crashes Archived])&amp;lt;/ref&amp;gt; which has caused many users frequent agitation.&amp;lt;ref&amp;gt;[https://www.reddit.com/r/microsoft/comments/19dvs9k/any_way_to_disable_the_upgrade_to_windows_11_ads/ &amp;quot;Any way to disable the &amp;quot;upgrade to Windows 11&amp;quot; ads?&amp;quot;] - reddit.com - accessed 2025-01-29 ([http://web.archive.org/web/20251016073816/https://old.reddit.com/r/microsoft/comments/19dvs9k/any_way_to_disable_the_upgrade_to_windows_11_ads/ Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some advocacy groups, such as the [https://endof10.org End of Windows 10 campaign] , have encouraged users with older PCs to switch to Linux instead.&lt;br /&gt;
&lt;br /&gt;
=====Recall=====&lt;br /&gt;
{{Main|Microsoft Copilot&#039;s recall feature}}&lt;br /&gt;
In 2024, Microsoft unveiled &#039;&#039;Recall&#039;&#039; for &#039;&#039;Copilot+ PCs&#039;&#039;, marketed as a way for users to search through what they have done on their computer by recording their screen. This sparked controversy,&amp;lt;ref&amp;gt;[https://www.techradar.com/computing/windows/microsofts-controversial-recall-feature-for-windows-11-could-already-be-in-legal-hot-water &amp;quot;Microsoft’s controversial Recall feature for Windows 11 could already be in legal hot water&amp;quot;] - techradar.com - accessed 2025-01-29 ([http://web.archive.org/web/20251002141424/https://www.techradar.com/computing/windows/microsofts-controversial-recall-feature-for-windows-11-could-already-be-in-legal-hot-water Archived])&amp;lt;/ref&amp;gt; especially among security experts&amp;lt;ref&amp;gt;[https://www.techtarget.com/searchenterpriseai/feature/Privacy-and-security-risks-surrounding-Microsoft-Recall &amp;quot;Privacy and security risks surrounding Microsoft Recall&amp;quot;] - techtarget.com - accessed 2025-01-29 ([http://web.archive.org/web/20251209084156/https://www.techtarget.com/searchenterpriseai/feature/Privacy-and-security-risks-surrounding-Microsoft-Recall Archived])&amp;lt;/ref&amp;gt; who worried about the security of screenshots,&amp;lt;ref&amp;gt;[https://news.sky.com/story/microsoft-ai-feature-investigated-by-uk-watchdog-over-screenshots-13141171 &amp;quot;Microsoft AI feature investigated by UK watchdog over screenshots&amp;quot;] - news.sky.com - accessed 2025-01-29 ([http://web.archive.org/web/20260203142620/https://news.sky.com/story/microsoft-ai-feature-investigated-by-uk-watchdog-over-screenshots-13141171 Archived])&amp;lt;/ref&amp;gt; since it could easily document private information like social-security numbers, bank-account information, and passwords, as well as user browsing behavior. A &#039;&#039;Python&#039;&#039; script was developed, called &amp;quot;&#039;&#039;TotalRecall&#039;&#039;&amp;quot;, that collects the screenshots and descriptions of these recordings,&amp;lt;ref&amp;gt;[https://github.com/xaitax/TotalRecall &amp;quot;TotalRecall - a &#039;privacy nightmare&#039;?&amp;quot;] - github.com - accessed 2025-01-29 ([http://web.archive.org/web/20260204070642/https://github.com/xaitax/TotalRecall Archived])&amp;lt;/ref&amp;gt; proving the danger of &#039;&#039;Recall&#039;&#039;. This feature was delayed after backlash from users.&amp;lt;ref&amp;gt;[https://www.malwarebytes.com/blog/news/2024/06/microsoft-recall-delayed-after-privacy-and-security-concerns &amp;quot;Microsoft Recall delayed after privacy and security concerns&amp;quot;] - malwarebytes.com - accessed 2025-01-29 ([http://web.archive.org/web/20251229124341/https://www.malwarebytes.com/blog/news/2024/06/microsoft-recall-delayed-after-privacy-and-security-concerns Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In 2025, Microsoft re-released &#039;&#039;Recall&#039;&#039;,&amp;lt;ref&amp;gt;{{Cite news |last=Davenport |first=Corbin |date=Apr 25, 2025 |title=Windows Recall Is Finally Rolling Out After Controversal Reveal |url=https://www.howtogeek.com/windows-recall-is-finally-rolling-out-after-controversal-release/ |access-date=Jun 20, 2025 |work=How to Geek |archive-url=http://web.archive.org/web/20260218203614/https://www.howtogeek.com/windows-recall-is-finally-rolling-out-after-controversal-release/ |archive-date=18 Feb 2026}}&amp;lt;/ref&amp;gt; with claims that the tool has resolved the security flaws and it coming disabled by default.&amp;lt;ref&amp;gt;{{Cite news |last=LeClair |first=Dave |date=Apr 11, 2025 |title=Microsoft Recall is rolling out following major controversy — what you need to know |url=https://www.tomsguide.com/computing/microsoft-recall-is-coming-for-real-this-time |access-date=Jun 20, 2025 |work=Tom&#039;s Guide |archive-url=http://web.archive.org/web/20251119223853/https://www.tomsguide.com/computing/microsoft-recall-is-coming-for-real-this-time |archive-date=19 Nov 2025}}&amp;lt;/ref&amp;gt; However, despite integrating better security, having this feature enabled continues to pose privacy risks for consumers, as it is only a matter of when a vulnerability is discovered for the problems both consumers and businesses initially had with the tool to resurface,&amp;lt;ref&amp;gt;{{Cite news |last=Lewis |first=Nick |date=May 5, 2025 |title=Turn Off Windows&#039; Recall to Protect Your Privacy |url=https://www.howtogeek.com/how-to-disable-recall/ |access-date=Jun 20, 2025 |work=How to Geek |archive-url=http://web.archive.org/web/20260216130638/https://www.howtogeek.com/how-to-disable-recall/ |archive-date=16 Feb 2026}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Piltch |first=Avram |date=2025-08-01 |title=Tested: Microsoft Recall can still capture credit cards and passwords, a treasure trove for crooks |url=https://www.theregister.com/2025/08/01/microsoft_recall_captures_credit_card_info/ |access-date=2025-08-05 |website=The Register |archive-url=http://web.archive.org/web/20260201105110/https://www.theregister.com/2025/08/01/microsoft_recall_captures_credit_card_info/ |archive-date=1 Feb 2026}}&amp;lt;/ref&amp;gt; especially since it is difficult for users to inspect the screenshots that are taken by the tool.&lt;br /&gt;
&lt;br /&gt;
=====Family Safety=====&lt;br /&gt;
{{Main|Microsoft&#039;s anticompetitive practices}}&lt;br /&gt;
A feature seen within &#039;&#039;[[Windows 11]]&#039;&#039;&amp;lt;nowiki/&amp;gt;&#039;s parental controls is Family Safety. A key problem shown from this feature is that it can questionably ban certain applications from properly running on the device, with no notice to the administrator in charge of the device. In &#039;&#039;&#039;June 2025&#039;&#039;&#039;, this feature banned the string &amp;quot;Chrome&amp;quot;,&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |last=u/Witty-Discount-2906 |date=Jun 3, 2025 |title=Chrome won’t open (Windows 11) |url=https://www.reddit.com/r/chrome/comments/1l2c552/comment/mvt1w2a/ |url-status=live |archive-url=https://web.archive.org/web/20260321124027/https://old.reddit.com/r/chrome/comments/1l2c552/chrome_wont_open_windows_11/mvt1w2a/ |archive-date=21 Mar 2026 |access-date=Jun 20, 2025 |website=[[Reddit]]}}&amp;lt;/ref&amp;gt; which blocked the web browser [[Google Chrome|&#039;&#039;Chrome&#039;&#039;]] from functioning.&amp;lt;ref&amp;gt;{{Cite news |last=Warren |first=Tom |date=Jun 20, 2025 |title=Microsoft is blocking Google Chrome through its family safety feature |url=https://www.theverge.com/news/690179/microsoft-block-google-chrome-family-safety-feature |access-date=Jun 20, 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260203193533/https://www.theverge.com/news/690179/microsoft-block-google-chrome-family-safety-feature |archive-date=3 Feb 2026}}&amp;lt;/ref&amp;gt; Schools in particular use this feature on devices given out for students to complete classwork remotely, and as [[Google Chrome|&#039;&#039;Chrome&#039;&#039;]] holds the majority market share of web browser usage, (65-70%)&amp;lt;ref&amp;gt;{{Cite web |date=May 1, 2025 |title=Browser Market Share Worldwide |url=https://gs.statcounter.com/browser-market-share/ |access-date=Jun 20, 2025 |website=Statcounter |archive-url=http://web.archive.org/web/20260122220040/https://gs.statcounter.com/browser-market-share |archive-date=22 Jan 2026}}&amp;lt;/ref&amp;gt; there has been mass reports of students being unable to complete their classwork strictly due to this flaw.&amp;lt;ref name=&amp;quot;:04&amp;quot;&amp;gt;{{Cite news |last=Priestley |first=Peter |date=Jun 4, 2025 |title=Microsoft Family Safety Blocking Chrome Browser |url=https://answers.microsoft.com/en-us/windows/forum/windows_11-wintop_famsafety/microsoft-family-safety-blocking-chrome-browser/40023ef5-177b-4eed-a857-80ed15afa3a5 |url-status=live |archive-url=https://web.archive.org/web/20260305010351/https://learn.microsoft.com/en-us/answers/questions/3862286/microsoft-family-safety-blocking-chrome-browser |archive-date=5 Mar 2026 |access-date=Jun 20, 2025 |work=Microsoft Answers}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, Microsoft has neglected to inform users on rolling out a fix in the future,&amp;lt;ref&amp;gt;{{Cite web |date=Jun 3, 2025 |title=[User Feedback - Stable] M137 Windows - Increase in feedback about crashing |url=https://issues.chromium.org/issues/422222571 |access-date=Jun 20, 2025 |website=Chromium issues |archive-url=http://web.archive.org/web/20251215065440/https://issues.chromium.org/issues/422222571 |archive-date=15 Dec 2025}}&amp;lt;/ref&amp;gt; and the only solutions available to users is to either rename the executable on the affected device&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt; or disable &amp;quot;Block inappropriate browsing&amp;quot; inside the &#039;&#039;Family Safety&#039;&#039; settings.&amp;lt;ref name=&amp;quot;:04&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Removal of WordPad=====&lt;br /&gt;
Starting with Windows 11, version 24H2, [[wikipedia:WordPad|WordPad]], a word processor included with every version of Windows since [[wikipedia:Windows_95|Windows 95]] was removed and would not be included with future clean installations. Microsoft recommended users to use [[wikipedia:Microsoft_Word|Microsoft Word]] for rich text documents like .doc and .rtf, and [[wikipedia:Windows_Notepad|Windows Notepad]] for plain text documents like .txt. Microsoft Word is included with Microsoft 365 for $69.99 a year, or with Office 2024 with a one-time purchase of $149.99.&amp;lt;ref&amp;gt;{{Cite web |date=Oct 4, 2024 |title=RIP: Windows 11 Update Officially Removes WordPad |url=https://www.pcmag.com/news/rip-windows-11-update-officially-removes-wordpad |access-date=2025-09-03 |website=PC Mag |archive-url=http://web.archive.org/web/20251002140136/https://www.pcmag.com/news/rip-windows-11-update-officially-removes-wordpad |archive-date=2 Oct 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Microsoft account increasingly required=====&lt;br /&gt;
{{See also|Microsoft ends use of &amp;quot;bypassnro.cmd&amp;quot; for Windows 11}}&lt;br /&gt;
Increasingly difficult to use a local account rather than a Microsoft account for installation and use of Windows.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Tone, and needs sources  May be deleted, see discuss tab for details --&amp;gt;&lt;br /&gt;
[[File:MSInstall.png|thumb|An image of a Windows 10 installation, to illustrate the effort required to make an account unattached to a Microsoft account.]]&lt;br /&gt;
Numerous [[dark patterns]] have been implemented in the form of vague language and a confusing user interface, which hides the option to create a local-user without a Microsoft account under sub-menus and small text. This implementation, first launched under Windows 10 in 2015, continues into the [[Windows 11]] installation process. In March 2025, Microsoft announced that the creation of a Microsoft account would be [[Forced account|mandatory]] when downloading Windows 11, claiming that the decision would tighten security and streamline the user experience (see [[Deceptive language frequently used against consumers]]).&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-28 |title=Windows 11 Enforces Mandatory Microsoft Account for Setup: What You Need to Know |url=https://windowsforum.com/threads/windows-11-enforces-mandatory-microsoft-account-for-setup-what-you-need-to-know.358519/ |url-status=live |access-date=2025-10-05 |website=Windows Forum |archive-url=http://web.archive.org/web/20260222014631/https://windowsforum.com/threads/windows-11-enforces-mandatory-microsoft-account-for-setup-what-you-need-to-know.358519/ |archive-date=22 Feb 2026}}&amp;lt;/ref&amp;gt;  On occasion, Microsoft accounts have been unilaterally disabled by Microsoft.  The default experience with a Microsoft account and trusted computing is that if something goes wrong with the computer, you are likely to lose all your data.  Experienced users know to backup credentials to minimize this risk, however Microsoft sets most users up for failure.&lt;br /&gt;
&lt;br /&gt;
=====Discontinued support for Windows Mixed Reality (WMR)=====&lt;br /&gt;
{{Main|Windows Mixed Reality (WMR) discontinuation}}&lt;br /&gt;
Beginning with [[Windows 11]] version &#039;&#039;24H2&#039;&#039;, Microsoft no longer supports Windows Mixed Reality, and all support for the platform will end November 1, 2027. This affects device models from manufacturers including &#039;&#039;[[Samsung]]&#039;&#039;, &#039;&#039;[[HP Inc.|HP]]&#039;&#039;, &#039;&#039;[[Lenovo]]&#039;&#039;, &#039;&#039;[[Acer]]&#039;&#039;, &#039;&#039;Dell&#039;&#039;, and Microsoft - including their own flagship device, Microsoft &#039;&#039;HoloLens&#039;&#039;. Users who wish to continue using these devices must either use Windows 10 or block the &#039;&#039;24H2&#039;&#039; update from being installed.&amp;lt;ref&amp;gt; https://answers.microsoft.com/en-us/windows/forum/all/hp-reverb-g2-windows-11-24h2-not-working-need-help/dd90e232-1f28-4655-aafa-685285017d59 ([http://web.archive.org/web/20250708171951/https://answers.microsoft.com/en-us/windows/forum/all/hp-reverb-g2-windows-11-24h2-not-working-need-help/dd90e232-1f28-4655-aafa-685285017d59 Archived])&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Xbox===&lt;br /&gt;
{{Main|xbox}}&lt;br /&gt;
&lt;br /&gt;
====Xbox 360 Defect - The &amp;quot;Red Ring of Death&amp;quot;====&lt;br /&gt;
{{Main|Bumpgate}}&lt;br /&gt;
In 2005, Microsoft released the &#039;&#039;Xbox 360&#039;&#039;. Not long after, consumers began reporting an issue with their consoles of three red flashing lights on the ring around the power button. This was coined by consumers as the &amp;quot;&#039;&#039;Red Ring of Death&#039;&#039;&amp;quot;, and by 2007, &#039;&#039;Xbox&#039;&#039;&amp;lt;nowiki/&amp;gt;&#039;s hardware engineers eventually discovered that the reason for it was a defect in the &#039;&#039;Xbox 360&#039;&#039;&amp;lt;nowiki/&amp;gt;&#039;s GPU.&amp;lt;ref&amp;gt;{{Cite web |date=December 13, 2021 |title=Power On: The Story of Xbox {{!}} Chapter 5: The Red Ring of Death |url=https://www.youtube.com/watch?v=z2d6IMBS8oY |url-status=live |archive-url=https://preservetube.com/watch?v=z2d6IMBS8oY |archive-date=2024-01-29 |access-date=June 4, 2025 |website=YouTube}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For several months of this incident&#039;s prevalence in 2006, consumers had to pay to get their consoles fixed by Microsoft if the console was outside of its one year warranty. However, by September 2007, they chose to extend the warranty to three years from the date of original purchase, and they refunded anyone who had previously paid to get this issue fixed&amp;lt;ref&amp;gt;{{Cite web |last=Moore |first=Peter |date=2007 |title=Open Letter from Peter Moore |url=http://xbox.com/en-ca/support/petermooreletter.htm |url-status=dead |archive-url=https://web.archive.org/web/20071023004948/http://xbox.com/en-ca/support/petermooreletter.htm |archive-date=23 Oct 2007 |access-date=4 Jun 2025 |website=Xbox}}&amp;lt;/ref&amp;gt;. Some current and former employees&#039; comments in the &#039;&#039;Xbox&#039;&#039; documentary, &#039;&#039;Power On: The Story of Xbox&#039;&#039; reveal that Microsoft may have done this to rescue the &#039;&#039;Xbox&#039;&#039; brand.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; Nonetheless, this was beneficial to consumers who had made an investment in and enjoyed games from Microsoft&#039;s console.&lt;br /&gt;
&lt;br /&gt;
====Xbox====&lt;br /&gt;
*&#039;&#039;&#039;Online activation&#039;&#039;&#039;&lt;br /&gt;
:Requiring internet connectivity to set up Xbox consoles or install physical game discs, even for single-player modes.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |date=April 12, 2021 |title=DRM or Die. How Anti-Consumer Practices Became the New Norm and the Consumers Are to Blame |url=https://cgicoffee.com/blog/2021/04/drm-or-die-anti-consumer-practices |website= |archive-url=http://web.archive.org/web/20250814164227/https://cgicoffee.com/blog/2021/04/drm-or-die-anti-consumer-practices |archive-date=14 Aug 2025}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Elaborate. Show why this matters and how it goes against a common sense alternative --&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;DRM&#039;&#039;&#039;&lt;br /&gt;
:Xbox Series X/S games demand online verification for disc-based installations, rendering offline play difficult.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&amp;lt;!-- Elaborate --&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;Xbox storage monopolization&#039;&#039;&#039;&lt;br /&gt;
:Xbox Series X/S uses a proprietary [https://www.seagate.com/content/dam/seagate/en/content-fragments/products/datasheets/xbox-expansion-card-series-4tb/xbox-expansion-card-series-4tb-DS2081-4-2504US-en_US.pdf Storage Expansion Card] that costs more when compared to industry standard storage.&amp;lt;ref&amp;gt;{{Cite web |last=Haske |first=Steve |date=2025-09-10 |title=Your standard SSD might work as an Xbox storage expansion |url=https://arstechnica.com/gaming/2021/09/your-standard-ssd-might-work-as-an-xbox-storage-expansion/ |url-status=live |website=Ars Technica}}&amp;lt;/ref&amp;gt;&amp;lt;!-- this section seems to reference a lot of support forums/reddit. not exactly the most professional but it&#039;s better than nothing considering this is user reporting --&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;Encrypted Storage&#039;&#039;&#039;&lt;br /&gt;
:Xbox Series X/S consoles have a removable solid-state drive (SSD), yet they contain an encrypted partition with a key that is married to the motherboard. This key changes after each system update, making it difficult to replace the drive&amp;lt;ref&amp;gt;{{Cite web |date=Jul 13, 2023 |title=New Xbox SSD interface is horribly anti repair|url=https://www.youtube.com/watch?v=Bbmzp-rqwfU |access-date=2025-09-03 |website=YouTube |archive-url=https://preservetube.com/watch?v=Bbmzp-rqwfU |archive-date=23 Feb 2026}}&amp;lt;/ref&amp;gt;. Xbox One consoles allowed users to easily replace the hard disk drive (HDD) as needed since the hard drives did not contain such encryption&amp;lt;ref&amp;gt;{{Cite web |date=May 20, 2024 |title=Xbox One Hard Drive Replacement|url=https://www.ifixit.com/Guide/Xbox+One+Hard+Drive+Replacement/36771 |access-date=2025-09-03 |website=iFixit |archive-url=http://web.archive.org/web/20251218160941/https://www.ifixit.com/Guide/Xbox+One+Hard+Drive+Replacement/36771 |archive-date=18 Dec 2025}}&amp;lt;/ref&amp;gt;. Though technically possible to replace HDDs on the Xbox 360, replacement drives have to be modified to report original drive information (like serial number) and in some cases cannot utilize all the storage available on a drive&amp;lt;ref&amp;gt;{{Cite web |title=Security Sector Information |url=https://fatxplorer.eaton-works.com/security-sector-information/ |url-status=live |archive-url=https://web.archive.org/web/20260321125530/https://fatxplorer.eaton-works.com/security-sector-information/ |archive-date=21 Mar 2026 |access-date=2026-03-01 |website=FATXplorer}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=Nov 28, 2024 |title=Xbox 360 HDD Replacement|url=https://www.ifixit.com/Guide/Xbox+360+HDD+Replacement/3430 |access-date=2025-09-03 |website=iFixit |archive-url=http://web.archive.org/web/20260130220622/https://www.ifixit.com/Guide/Xbox+360+HDD+Replacement/3430 |archive-date=30 Jan 2026}}&amp;lt;/ref&amp;gt;. For the original Xbox, the hard drive was married to the motherboard, but if the console was modified with custom firmware, users could easily replace the drive&amp;lt;ref&amp;gt;{{Cite web |first=Ryan |title=How To Upgrade The HDD (Hard Drive) In A Softmodded Xbox! |url=https://www.youtube.com/watch?v=rv-gOJ1i2eI |url-status=live |website=YouTube - Archades Games}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
*&#039;&#039;&#039;Ending Third-Party Wireless Controller Support&#039;&#039;&#039;&lt;br /&gt;
:Support for third-party wireless controllers was ended in October 2023. Users were given a two week warning before their devices could no longer be used wirelessly unless the manufacturer paid a licensing fee.&lt;br /&gt;
&lt;br /&gt;
====Removal of games====&lt;br /&gt;
In early September 2016, Microsoft shut down &#039;&#039;Xbox Live Indie Games&#039;&#039;,&amp;lt;ref&amp;gt;[https://www.polygon.com/2015/9/9/9297959/xbox-live-indie-games-shutting-down &amp;quot;After seven years, Xbox Live Indie Games is closing down for good&amp;quot;] - polygon.com - accessed 2025-01-29 ([http://web.archive.org/web/20250820204939/https://www.polygon.com/2015/9/9/9297959/xbox-live-indie-games-shutting-down/ Archived])&amp;lt;/ref&amp;gt; and in late July 2024, Microsoft shut down its storefront for &#039;&#039;[[Xbox|Xbox 360]]&#039;&#039; games.&amp;lt;ref&amp;gt;[https://news.xbox.com/en-us/2023/08/17/xbox-360-store-will-close-july-2024/ &amp;quot;The Xbox 360 Store Will Close July 2024, But You Can Keep Playing Your Favorite Games&amp;quot;] - news.xbox.com - accessed 2025-01-29 ([http://web.archive.org/web/20260221231632/https://news.xbox.com/en-us/2023/08/17/xbox-360-store-will-close-july-2024/ Archived])&amp;lt;/ref&amp;gt; These shutdowns have made it impossible to obtain new copies of, or in some cases, play, hundreds of games within the legacy &#039;&#039;[[Xbox]]&#039;&#039; library.&lt;br /&gt;
&lt;br /&gt;
===Other===&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;&#039;Collaboration with surveillance&#039;&#039;&#039;====&lt;br /&gt;
Working with the NSA and FBI to bypass encryption (PRISM program) and access user data (Skype, Outlook).&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;&#039;Recurring billing traps&#039;&#039;&#039;====&lt;br /&gt;
Defaulting users into subscription auto-renewals while making cancellation processes opaque.&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-18 |title=Why is MS Software So Predatory? |url=https://learn.microsoft.com/en-us/answers/questions/3869973/why-is-ms-software-so-predatory?forum=windows-all&amp;amp;referrer=answers |url-status=live |access-date=2025-08-18 |website=learn.microsoft.com |archive-url=http://web.archive.org/web/20250812172730/https://learn.microsoft.com/en-us/answers/questions/3869973/why-is-ms-software-so-predatory?forum=windows-all&amp;amp;referrer=answers |archive-date=12 Aug 2025}}&amp;lt;/ref&amp;gt;{{Citation needed|reason=better source than just support forum}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
[[Microsoft Office 365]], an article on Microsoft&#039;s Office 365 subscription service which includes how to avoid the $30 price increase at the start.&lt;br /&gt;
&lt;br /&gt;
Cross-platform limitations and consumer impact of [[Microsoft Authenticator]] multi-factor authentication.&lt;br /&gt;
&lt;br /&gt;
*[[Visual Studio Code]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Microsoft| ]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google_Chromecast&amp;diff=54695</id>
		<title>Google Chromecast</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google_Chromecast&amp;diff=54695"/>
		<updated>2026-05-24T22:03:15Z</updated>

		<summary type="html">&lt;p&gt;Tracerneo: -cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{SloppyAI}}&lt;br /&gt;
&lt;br /&gt;
{{ProductLineCargo&lt;br /&gt;
|Logo=Collection of Chromecast devices.jpg&lt;br /&gt;
|Company=Google|ReleaseYear=2013|InProduction=No|Description=Google Chromecast is a line of digital media players developed by Google. The devices, designed as small dongles, allow users with a mobile device or personal computer to play online content}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Google Chromecast&#039;&#039;&#039; is a line of digital media players developed by Google. The devices, designed as small dongles, allow users with a mobile device or personal computer to play online content on a high-definition television or home audio system through mobile and web apps that support the Google Cast technology.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
===User freedom===&lt;br /&gt;
Originally marketed as a simple, &amp;quot;plug-and-play&amp;quot; solution for streaming, Chromecast has increasingly moved toward a closed ecosystem. Early models allowed for basic setup via a PC or simple browser interface. However, Google transitioned to a mandatory requirement for the &#039;&#039;&#039;Google Home app&#039;&#039;&#039; on a compatible smartphone or tablet for setup and management. This shift forces users into the Google mobile ecosystem and creates a barrier for those without modern smartphones or those who wish to maintain a &amp;quot;decoupled&amp;quot; home theater setup.&lt;br /&gt;
&lt;br /&gt;
===User privacy===&lt;br /&gt;
As a hardware extension of the Google ecosystem, Chromecast acts as a significant data collection node. It tracks usage patterns, including which apps are used, the duration of viewing sessions, and the domains from which content is cast. Because it is managed via the Google Home app, this data is tied directly to a user&#039;s primary Google account, enabling detailed cross-device profiling for advertising purposes.&lt;br /&gt;
&lt;br /&gt;
===Business model===&lt;br /&gt;
The Chromecast business model transitioned from selling low-cost hardware to high-volume users to a service-based model. By integrating &#039;&#039;&#039;Google TV&#039;&#039;&#039; into later models, Google transformed the device from a passive receiver into an active content recommendation engine. This allows Google to capture revenue through featured placements, app subscriptions, and targeted advertising on the home screen.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===Mandatory Google Home App Requirement===&lt;br /&gt;
Initially, Chromecast devices could be set up using a laptop or a simple web interface. Google eventually deprecated these methods, making the &#039;&#039;&#039;Google Home app&#039;&#039;&#039; the exclusive way to set up and manage the hardware. This has significant implications for consumer rights:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Accessibility:&#039;&#039;&#039; Customers who do not own a smartphone or have older devices that cannot run the latest Google Home app are unable to use a product they purchased.&lt;br /&gt;
*&#039;&#039;&#039;Forced Ecosystem:&#039;&#039;&#039; Users are forced to agree to the Google Home Terms of Service and Privacy Policy simply to use the basic functions of their television hardware.&lt;br /&gt;
&lt;br /&gt;
===Feature Removal from Integrated TVs (e.g., Caixon EC43S1UA)===&lt;br /&gt;
The shift to app-only control has negatively impacted &amp;quot;Chromecast Built-in&amp;quot; devices. Certain smart televisions, such as the &#039;&#039;&#039;Caixon EC43S1UA&#039;&#039;&#039;, relied on internal Chromecast modules for their primary &amp;quot;smart&amp;quot; functionality.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Diminished Value:&#039;&#039;&#039; When Google updates the casting protocols or setup requirements to favor the Home app, older integrated hardware often becomes buggy or unresponsive.&lt;br /&gt;
*&#039;&#039;&#039;Loss of Functionality:&#039;&#039;&#039; Owners of these TVs have reported that they can no longer cast content as intended, effectively removing a core advertised feature of the product post-purchase without compensation.&lt;br /&gt;
&lt;br /&gt;
===Discontinuation of the Chromecast Brand (2024)===&lt;br /&gt;
In August 2024, Google announced the end of the Chromecast line, replacing it with the &#039;&#039;&#039;Google TV Streamer&#039;&#039;&#039;. While Google has promised continued software updates for recent Chromecast models, the move marks a shift toward more expensive, &amp;quot;set-top box&amp;quot; style hardware. This raises concerns about &#039;&#039;&#039;planned obsolescence&#039;&#039;&#039;, as older Chromecast &amp;quot;pucks&amp;quot; may eventually lose compatibility with modern apps as Google focuses development on the newer Streamer architecture.&lt;br /&gt;
&lt;br /&gt;
===Audio Casting Limitations===&lt;br /&gt;
Google was involved in a long-standing legal battle with &#039;&#039;&#039;Sonos&#039;&#039;&#039; regarding multi-room audio patents. As a result of this dispute, Google was forced to remove the ability to adjust the volume of a &amp;quot;Speaker Group&amp;quot; (multiple Chromecasts playing at once) using the physical volume buttons on a smartphone, requiring users to open the app and adjust each device individually. This degraded the user experience for thousands of customers who had purchased the devices specifically for synchronized home audio.&lt;br /&gt;
&lt;br /&gt;
[[Category:Google]]&lt;br /&gt;
[[Category:Anti-consumer practices]]&lt;/div&gt;</summary>
		<author><name>Tracerneo</name></author>
	</entry>
</feed>