<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://mirror.consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tpat90</id>
	<title>Consumer Rights Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://mirror.consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tpat90"/>
	<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/w/Special:Contributions/Tpat90"/>
	<updated>2026-05-19T21:41:41Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=User:Tpat90&amp;diff=7205</id>
		<title>User:Tpat90</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=User:Tpat90&amp;diff=7205"/>
		<updated>2025-01-31T14:56:51Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Mmmyes&lt;br /&gt;
&lt;br /&gt;
Much read&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Likes tea, hates humans, does way to much volunteering&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Contribution Scores&lt;br /&gt;
!Score&lt;br /&gt;
!Unique Pages Editted&lt;br /&gt;
!Changes&lt;br /&gt;
|-&lt;br /&gt;
|{{#cscore:tpat90|score}}&lt;br /&gt;
|{{#cscore:tpat90|pages}}&lt;br /&gt;
|{{#cscore:tpat90|changes}}&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Wiki_Content_Policies&amp;diff=6941</id>
		<title>Wiki Content Policies</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Wiki_Content_Policies&amp;diff=6941"/>
		<updated>2025-01-30T14:59:00Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Changed redirect target from Consumer Action Taskforce:Wiki Content Policies to Consumer Action Taskforce:Wiki content policies&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Consumer Action Taskforce:Wiki content policies]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Tools_for_Writing_Articles&amp;diff=6940</id>
		<title>Tools for Writing Articles</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Tools_for_Writing_Articles&amp;diff=6940"/>
		<updated>2025-01-30T14:58:24Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Changed redirect target from Consumer Action Taskforce:Tools for Writing Articles to Consumer Action Taskforce:Tools for writing articles&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Consumer Action Taskforce:Tools for writing articles]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Moderator_Guidelines&amp;diff=6938</id>
		<title>Moderator Guidelines</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Moderator_Guidelines&amp;diff=6938"/>
		<updated>2025-01-30T14:57:57Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Changed redirect target from Consumer Action Taskforce:Moderator Guidelines to Consumer Action Taskforce:Moderator guidelines&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Consumer Action Taskforce:Moderator guidelines]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Living_Persons_Policy&amp;diff=6937</id>
		<title>Living Persons Policy</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Living_Persons_Policy&amp;diff=6937"/>
		<updated>2025-01-30T14:57:35Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Changed redirect target from Consumer Action Taskforce:Living Persons Policy to Consumer Action Taskforce:Living persons policy&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Consumer Action Taskforce:Living persons policy]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Roku&amp;diff=6935</id>
		<title>Roku</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Roku&amp;diff=6935"/>
		<updated>2025-01-30T14:54:39Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{InfoboxProductLine&lt;br /&gt;
| Title = Roku, Inc.&lt;br /&gt;
| Release Year = 2002&lt;br /&gt;
| Product Type = Hardware&lt;br /&gt;
| In Production = Yes&lt;br /&gt;
| Official Website = https://roku.com/&lt;br /&gt;
| Logo = Roku.png&lt;br /&gt;
}}&#039;&#039;&#039;Roku, Inc.&#039;&#039;&#039; is an American technology company, founded in October of 2002, known for their &amp;quot;Roku&amp;quot; line of products which consist of Smart TVs &amp;amp; streaming players. It is also the creator and maintainer of &amp;quot;Roku OS.&amp;quot; Roku OS is a smart TV operating system allowing users to access apps such as streaming services, which was released in 2004.&lt;br /&gt;
&lt;br /&gt;
==Consumer-protection summary==&lt;br /&gt;
&lt;br /&gt;
====Privacy&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;https://docs.roku.com/published/userprivacypolicy/en/us&amp;lt;/ref&amp;gt;====&lt;br /&gt;
&lt;br /&gt;
*Roku collects personal information such as the user&#039;s device information, usage data, viewing activity, and location data.&lt;br /&gt;
*This data is used for purposes such as providing and improving services, personalizing content, and targeted advertisements.&lt;br /&gt;
*Roku retains personal data for as long as deemed necessary.&lt;br /&gt;
*On many of their devices and services such as Roku OS, &amp;quot;Do not sell my personal information&amp;quot; is opt-out rather than opt-in.&lt;br /&gt;
&lt;br /&gt;
====Transparency====&lt;br /&gt;
&lt;br /&gt;
*The &amp;quot;Do not sell my personal information&amp;quot; setting on Roku OS is hidden behind many menus.&lt;br /&gt;
*Roku states the added forced arbitration clause was a decision made separate of the data breach (More on this below). This has obviously led to skepticism on the companies&#039; overall truthfulness.&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;https://www.bleepingcomputer.com/news/security/over-15-000-hacked-roku-accounts-sold-for-50-each-to-buy-hardware/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer-protection incidents==&lt;br /&gt;
&lt;br /&gt;
===Post-Purchase EULA Modification (Mar. 2024)===&lt;br /&gt;
[[File:Roku Forced Arbitration.jpg|thumb|510x510px|The screen in which consumers agreed to force arbitration. There is no &amp;quot;disagree.&amp;quot;&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;https://www.techhive.com/article/2258136/rokus-forced-arbitration-update-leaves-users-fuming.html&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
In early March 2024, Roku Inc. [[Post-purchase EULA modification|modified]] its [[End-user license agreement]] (EULA), after the company disclosed a data breach that affected 15,000 accounts.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; In April 2024, Roku disclosed another incident that affected 576,000 additional accounts.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This new EULA was enforced onto pre-existing users in the form of a message on their Smart TV/streaming player, which only allowed the user to accept the new terms, and did not offer an option to decline. The only option Roku Inc. offered to opt-out of the new EULA was for the user to mail the company their contact information and email used to register the Roku account (if applicable), along with the product model, software, or service &amp;quot;at issue.&amp;quot; In this new EULA, Roku included a [[forced arbitration]] agreement to not allow users to sue, or to take part in lawsuits against Roku Inc.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; Roku claimed a week later that the new EULA was not in relation to the aforementioned data breach.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;HDMI-customized ad insertion&amp;quot; patent (Oct. 2023)===&lt;br /&gt;
In early October 2023, Roku filed a patent ([https://patents.google.com/patent/US20230388589A1/en US20230388589A1]) for a program to insert ads on top of the display output of any non-Roku device displayed on a Roku TV. This program would be able to detect when the consumer has paused a video feed and display an advertisement, personalized by data collected through Roku services.&amp;lt;ref&amp;gt;https://patents.google.com/patent/US20230388589A1/en&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As of January 2025, this patent has not been implemented into any Roku devices. However, a similar feature which also detects content from connected devices, called &amp;quot;More Ways to Watch,&amp;quot; has previously been implemented.&amp;lt;ref&amp;gt;https://support.roku.com/article/115005739288&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://www.cnet.com/tech/home-entertainment/roku-tvs-now-track-what-you-watch-to-suggest-streams-target-ads/&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:Electronics companies]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=6934</id>
		<title>Disney wrongful-death lawsuit</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=6934"/>
		<updated>2025-01-30T14:54:12Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Legal Lockout]]&lt;br /&gt;
===The EPCOT death lawsuit and Disney&#039;s arbitration clause===&lt;br /&gt;
In a wrongful-death lawsuit,&amp;lt;ref&amp;gt;[[:File:AUGUST 2ND RESPONSE.pdf|&amp;quot;AUGUST 2ND RESPONSE.pdf&amp;quot;]] - wiki.rossmanngroup.com - accessed 2025-01-29 &amp;lt;/ref&amp;gt; Jeffrey Piccolo sued Walt Disney Parks &amp;amp; Resorts (WDPR) and Great Irish Pubs Florida, Inc. after his wife, Dr. Kanokporn Tangsuan, died from a severe allergic reaction at Raglan Road Irish Pub in Disney Springs on October 5, 2023. The lawsuit accused the restaurant and Disney of negligence in accommodating her food allergy, which contributed to her death.&amp;lt;ref name=&amp;quot;nprdwd&amp;quot;&amp;gt;[https://www.npr.org/2024/08/14/nx-s1-5074830/disney-wrongful-death-lawsuit-disney &amp;quot;Disney backtracks on request to toss wrongful death suit over Disney+ agreement&amp;quot;] - npr.org - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
Dr. Tangsuan, a family-medicine specialist at NYU Langone Hospital, had severe allergies to dairy and nuts. She and her family chose to dine at Raglan Road, specifically because Disney had advertised that they accommodate guests with food allergies throughout their properties. Despite Dr. Tangsuan repeatedly informing her server about her allergies and receiving multiple assurances that their ordered dishes would be allergen-free, Dr. Tangsuan suffered a severe allergic reaction approximately 45 minutes after eating. Although she self-administered an EpiPen, she later died at the hospital. The medical examiner confirmed her death was due to anaphylaxis from elevated levels of dairy and nuts in her system.&amp;lt;ref name=&amp;quot;nytdwd&amp;quot;&amp;gt;[https://www.nytimes.com/2024/08/14/nyregion/disney-wrongful-death-lawsuit-arbitration.html &amp;quot;Can a Disney+ Subscription Keep a Widower From Suing Disney in Court?&amp;quot;] - nytimes.com - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The EULA roofie attempt==&lt;br /&gt;
In May 2024, Disney attempted to have the case dismissed from court and sent to [[Forced Arbitration|arbitration]], citing two separate [[End-user license agreement|user agreements]]:&lt;br /&gt;
&lt;br /&gt;
#The Disney+ user agreement Piccolo accepted in 2019 when signing up for a free trial to Disney&#039;s streaming service on his PlayStation&lt;br /&gt;
#Terms accepted when purchasing (ultimately unused) Epcot tickets through the My Disney Experience app in September 2023&lt;br /&gt;
&lt;br /&gt;
This represented a classic example of a [[EULA roofie]], where Disney attempted to use terms buried within a streaming-service agreement to deny a consumer&#039;s right to sue over an unrelated wrongful-death case at a restaurant. Disney argued that because Piccolo had clicked &amp;quot;Agree &amp;amp; Continue&amp;quot; when signing up for the Disney+ streaming service, he was bound by an arbitration clause for any legal claims against the company or its affiliates. This, they argued, included the food served by a restaurant on their premises that killed his wife, even if the issue was unrelated to the streaming service.&lt;br /&gt;
&lt;br /&gt;
Disney said that the reason for trying to send the case to arbitration was because the restaurant &amp;quot;is neither owned nor operated by Disney&amp;quot; and that they were defending themselves against inclusion in the lawsuit.&amp;lt;ref&amp;gt;[https://edition.cnn.com/2024/08/14/business/disney-plus-wrongful-death-lawsuit/index.html &amp;quot;Disney wants wrongful death suit thrown out because widower bought an Epcot ticket and had Disney+&amp;quot;] - edition.cnn.com - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Legal arguments===&lt;br /&gt;
Piccolo&#039;s attorneys filed a 123-page response calling Disney&#039;s argument &amp;quot;preposterous&amp;quot; and &amp;quot;fatally flawed&amp;quot; for several reasons:&lt;br /&gt;
&lt;br /&gt;
*Mr. Piccolo brought the lawsuit as Personal Representative of his wife&#039;s estate, not as him the individual&lt;br /&gt;
*The estate itself never agreed to any arbitration terms&lt;br /&gt;
*The estate did not exist at the time Mr. Piccolo accepted the Disney+ terms, as Dr. Tangsuan was still alive&lt;br /&gt;
*The Disney+ Subscriber Agreement was specifically limited to disputes concerning the streaming service&lt;br /&gt;
*Disney had already waived any right to arbitration by participating in the litigation before raising the issue&lt;br /&gt;
&lt;br /&gt;
The attorneys argued that &amp;quot;the notion that terms agreed to by a consumer when creating a Disney+ free trial account would forever bar that consumer&#039;s right to a jury trial in any dispute with any Disney affiliate or subsidiary, is so outrageously unreasonable and unfair as to shock the judicial conscience.&amp;quot;&amp;lt;ref name=&amp;quot;nytdwd&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Procedural timeline==&lt;br /&gt;
Disney had initially participated in discovery and filed an answer to the complaint without raising arbitration as a defense. Only later did the company attempt to use the [[End-user license agreement]] (EULA) to avoid litigation. As noted in its second response, in August: &amp;quot;WDPR has waived its alleged right to seek arbitration by filing its Answer without raising arbitration as an affirmative defense and by serving two separate Requests for Copies under Rule 1.351(e).&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 3&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Key legal issues around consumer rights==&lt;br /&gt;
===Meeting of minds===&lt;br /&gt;
The response highlighted fundamental contract-law principles that challenge the validity of using broad EULAs to bind consumers. As stated in the filing, Disney&#039;s attempt violated basic principles of contract formation including &amp;quot;meeting of the minds (mutual understanding between parties)&amp;quot; and &amp;quot;good-faith dealing&amp;quot;.&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 11&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Unconscionability===&lt;br /&gt;
The response detailed both procedural and substantive unconscionability in Disney&#039;s EULA:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Procedural unconscionability:&#039;&#039;&#039;&lt;br /&gt;
**&amp;quot;There was no showing that Mr. Piccolo was given any explanation of the arbitration clauses in The Disney+ Subscriber Agreement.&amp;quot;&lt;br /&gt;
**&amp;quot;The so-called binding arbitration provision was merely contained in a link. With respect to the Disney Terms of Use, the link was not even referenced or hyperlinked on the Disney+ registration page. It was buried within another document that was hyperlinked.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 27-28&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Substantive unconscionability:&#039;&#039;&#039;&lt;br /&gt;
**The arbitration provisions &amp;quot;could present a problem for more than just their own client&amp;quot;&lt;br /&gt;
**&amp;quot;In effect, WDPR is explicitly seeking to bar its 150 million Disney+ subscribers from ever prosecuting a wrongful death case against it in front of a jury even if the case facts have nothing to with Disney+&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 30&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The Florida Supreme Court has acknowledged there is some overlap in the analysis of whether a valid written agreement to arbitrate exists and whether an arbitrable issue exists, noting: &#039;It is something of a chicken and egg situation as to which comes first.&#039; This highlights the fundamental problem with modern EULAs - consumers cannot meaningfully assess what rights they&#039;re giving up when agreeing to terms that may be interpreted to cover any future dispute with any related corporate entity.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 19&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Resolution==&lt;br /&gt;
Following significant public backlash and media attention highlighting how this could affect Disney+&#039;s 150 million subscribers, Disney withdrew its motion to compel arbitration in August 2024. Josh D&#039;Amaro, chairman of Disney Experiences, stated: &amp;quot;At Disney, we strive to put humanity above all other considerations… With such unique circumstances as the ones in this case, we believe this situation warrants a sensitive approach to expedite a resolution for the family who have experienced such a painful loss.&amp;quot;&amp;lt;ref name=&amp;quot;nprdwd&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Significance==&lt;br /&gt;
&lt;br /&gt;
The response specifically addressed how Disney&#039;s EULA-roofie attempt represents the type of modern consumer exploitation that traditional consumer protection laws fail to address: the potential dangers of overly broad arbitration clauses in consumer agreements and their use to deny access to courts even in serious cases like wrongful death. It demonstrates how companies may attempt to use unrelated consumer agreements to strip away fundamental legal rights, making it a notable example of the EULA-roofie phenomenon. The case also showed how public attention and backlash can sometimes force companies to reconsider such tactics. This case demonstrated how companies use complex legal documents and digital agreements to manufacture consent for terms that a reasonable consumer would never knowingly accept, as a customer might be less likely to sign up for a free trial of a streaming service if he knew it would absolve the company from accountability for killing his wife. &lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Lawsuits]]&lt;br /&gt;
[[Category:EULA roofieing]]&lt;br /&gt;
[[Category:Disney]]&lt;br /&gt;
[[Category:Articles based on videos]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=6923</id>
		<title>Disney wrongful-death lawsuit</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=6923"/>
		<updated>2025-01-30T14:41:21Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Legal Lockout]]&lt;br /&gt;
===The EPCOT death lawsuit and Disney&#039;s arbitration clause===&lt;br /&gt;
In a wrongful-death lawsuit,&amp;lt;ref&amp;gt;[[:File:AUGUST 2ND RESPONSE.pdf|&amp;quot;AUGUST 2ND RESPONSE.pdf&amp;quot;]] - wiki.rossmanngroup.com - accessed 2025-01-29 &amp;lt;/ref&amp;gt; Jeffrey Piccolo sued Walt Disney Parks &amp;amp; Resorts (WDPR) and Great Irish Pubs Florida, Inc. after his wife, Dr. Kanokporn Tangsuan, died from a severe allergic reaction at Raglan Road Irish Pub in Disney Springs on October 5, 2023. The lawsuit accused the restaurant and Disney of negligence in accommodating her food allergy, which contributed to her death.&amp;lt;ref name=&amp;quot;nprdwd&amp;quot;&amp;gt;[https://www.npr.org/2024/08/14/nx-s1-5074830/disney-wrongful-death-lawsuit-disney &amp;quot;Disney backtracks on request to toss wrongful death suit over Disney+ agreement&amp;quot;] - npr.org - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
Dr. Tangsuan, a family-medicine specialist at NYU Langone Hospital, had severe allergies to dairy and nuts. She and her family chose to dine at Raglan Road, specifically because Disney had advertised that they accommodate guests with food allergies throughout their properties. Despite Dr. Tangsuan repeatedly informing her server about her allergies and receiving multiple assurances that their ordered dishes would be allergen-free, Dr. Tangsuan suffered a severe allergic reaction approximately 45 minutes after eating. Although she self-administered an EpiPen, she later died at the hospital. The medical examiner confirmed her death was due to anaphylaxis from elevated levels of dairy and nuts in her system.&amp;lt;ref name=&amp;quot;nytdwd&amp;quot;&amp;gt;[https://www.nytimes.com/2024/08/14/nyregion/disney-wrongful-death-lawsuit-arbitration.html &amp;quot;Can a Disney+ Subscription Keep a Widower From Suing Disney in Court?&amp;quot;] - nytimes.com - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The EULA roofie attempt==&lt;br /&gt;
In May 2024, Disney attempted to have the case dismissed from court and sent to [[Forced Arbitration|arbitration]], citing two separate [[End-user license agreement|user agreements]]:&lt;br /&gt;
&lt;br /&gt;
#The Disney+ user agreement Piccolo accepted in 2019 when signing up for a free trial to Disney&#039;s streaming service on his PlayStation&lt;br /&gt;
#Terms accepted when purchasing (ultimately unused) Epcot tickets through the My Disney Experience app in September 2023&lt;br /&gt;
&lt;br /&gt;
This represented a classic example of a [[EULA roofie]], where Disney attempted to use terms buried within a streaming-service agreement to deny a consumer&#039;s right to sue over an unrelated wrongful-death case at a restaurant. Disney argued that because Piccolo had clicked &amp;quot;Agree &amp;amp; Continue&amp;quot; when signing up for the Disney+ streaming service, he was bound by an arbitration clause for any legal claims against the company or its affiliates. This, they argued, included the food served by a restaurant on their premises that killed his wife, even if the issue was unrelated to the streaming service.&lt;br /&gt;
&lt;br /&gt;
Disney said that the reason for trying to send the case to arbitration was because the restaurant &amp;quot;is neither owned nor operated by Disney&amp;quot; and that they were defending themselves against inclusion in the lawsuit.&amp;lt;ref&amp;gt;[https://edition.cnn.com/2024/08/14/business/disney-plus-wrongful-death-lawsuit/index.html &amp;quot;Disney wants wrongful death suit thrown out because widower bought an Epcot ticket and had Disney+&amp;quot;] - edition.cnn.com - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Legal arguments===&lt;br /&gt;
Piccolo&#039;s attorneys filed a 123-page response calling Disney&#039;s argument &amp;quot;preposterous&amp;quot; and &amp;quot;fatally flawed&amp;quot; for several reasons:&lt;br /&gt;
&lt;br /&gt;
*Mr. Piccolo brought the lawsuit as Personal Representative of his wife&#039;s estate, not as him the individual&lt;br /&gt;
*The estate itself never agreed to any arbitration terms&lt;br /&gt;
*The estate did not exist at the time Mr. Piccolo accepted the Disney+ terms, as Dr. Tangsuan was still alive&lt;br /&gt;
*The Disney+ Subscriber Agreement was specifically limited to disputes concerning the streaming service&lt;br /&gt;
*Disney had already waived any right to arbitration by participating in the litigation before raising the issue&lt;br /&gt;
&lt;br /&gt;
The attorneys argued that &amp;quot;the notion that terms agreed to by a consumer when creating a Disney+ free trial account would forever bar that consumer&#039;s right to a jury trial in any dispute with any Disney affiliate or subsidiary, is so outrageously unreasonable and unfair as to shock the judicial conscience.&amp;quot;&amp;lt;ref name=&amp;quot;nytdwd&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Procedural timeline==&lt;br /&gt;
Disney had initially participated in discovery and filed an answer to the complaint without raising arbitration as a defense. Only later did the company attempt to use the [[End-User License Agreement|End-user license agreement]] (EULA) to avoid litigation. As noted in its second response, in August: &amp;quot;WDPR has waived its alleged right to seek arbitration by filing its Answer without raising arbitration as an affirmative defense and by serving two separate Requests for Copies under Rule 1.351(e).&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 3&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Key legal issues around consumer rights==&lt;br /&gt;
===Meeting of minds===&lt;br /&gt;
The response highlighted fundamental contract-law principles that challenge the validity of using broad EULAs to bind consumers. As stated in the filing, Disney&#039;s attempt violated basic principles of contract formation including &amp;quot;meeting of the minds (mutual understanding between parties)&amp;quot; and &amp;quot;good-faith dealing&amp;quot;.&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 11&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Unconscionability===&lt;br /&gt;
The response detailed both procedural and substantive unconscionability in Disney&#039;s EULA:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Procedural unconscionability:&#039;&#039;&#039;&lt;br /&gt;
**&amp;quot;There was no showing that Mr. Piccolo was given any explanation of the arbitration clauses in The Disney+ Subscriber Agreement.&amp;quot;&lt;br /&gt;
**&amp;quot;The so-called binding arbitration provision was merely contained in a link. With respect to the Disney Terms of Use, the link was not even referenced or hyperlinked on the Disney+ registration page. It was buried within another document that was hyperlinked.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 27-28&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Substantive unconscionability:&#039;&#039;&#039;&lt;br /&gt;
**The arbitration provisions &amp;quot;could present a problem for more than just their own client&amp;quot;&lt;br /&gt;
**&amp;quot;In effect, WDPR is explicitly seeking to bar its 150 million Disney+ subscribers from ever prosecuting a wrongful death case against it in front of a jury even if the case facts have nothing to with Disney+&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 30&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The Florida Supreme Court has acknowledged there is some overlap in the analysis of whether a valid written agreement to arbitrate exists and whether an arbitrable issue exists, noting: &#039;It is something of a chicken and egg situation as to which comes first.&#039; This highlights the fundamental problem with modern EULAs - consumers cannot meaningfully assess what rights they&#039;re giving up when agreeing to terms that may be interpreted to cover any future dispute with any related corporate entity.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 19&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Resolution==&lt;br /&gt;
Following significant public backlash and media attention highlighting how this could affect Disney+&#039;s 150 million subscribers, Disney withdrew its motion to compel arbitration in August 2024. Josh D&#039;Amaro, chairman of Disney Experiences, stated: &amp;quot;At Disney, we strive to put humanity above all other considerations… With such unique circumstances as the ones in this case, we believe this situation warrants a sensitive approach to expedite a resolution for the family who have experienced such a painful loss.&amp;quot;&amp;lt;ref name=&amp;quot;nprdwd&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Significance==&lt;br /&gt;
&lt;br /&gt;
The response specifically addressed how Disney&#039;s EULA-roofie attempt represents the type of modern consumer exploitation that traditional consumer protection laws fail to address: the potential dangers of overly broad arbitration clauses in consumer agreements and their use to deny access to courts even in serious cases like wrongful death. It demonstrates how companies may attempt to use unrelated consumer agreements to strip away fundamental legal rights, making it a notable example of the EULA-roofie phenomenon. The case also showed how public attention and backlash can sometimes force companies to reconsider such tactics. This case demonstrated how companies use complex legal documents and digital agreements to manufacture consent for terms that a reasonable consumer would never knowingly accept, as a customer might be less likely to sign up for a free trial of a streaming service if he knew it would absolve the company from accountability for killing his wife. &lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Lawsuits]]&lt;br /&gt;
[[Category:EULA roofieing]]&lt;br /&gt;
[[Category:Disney]]&lt;br /&gt;
[[Category:Articles based on videos]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Article_Types&amp;diff=6920</id>
		<title>Article Types</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Article_Types&amp;diff=6920"/>
		<updated>2025-01-30T14:38:12Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Changed redirect target from Consumer Action Taskforce:Article Types to Consumer Action Taskforce:Article types&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Consumer Action Taskforce:Article types]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Roku&amp;diff=6919</id>
		<title>Roku</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Roku&amp;diff=6919"/>
		<updated>2025-01-30T14:36:51Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{InfoboxProductLine&lt;br /&gt;
| Title = Roku, Inc.&lt;br /&gt;
| Release Year = 2002&lt;br /&gt;
| Product Type = Hardware&lt;br /&gt;
| In Production = Yes&lt;br /&gt;
| Official Website = https://roku.com/&lt;br /&gt;
| Logo = Roku.png&lt;br /&gt;
}}&#039;&#039;&#039;Roku, Inc.&#039;&#039;&#039; is an American technology company, founded in October of 2002, known for their &amp;quot;Roku&amp;quot; line of products which consist of Smart TVs &amp;amp; streaming players. It is also the creator and maintainer of &amp;quot;Roku OS.&amp;quot; Roku OS is a smart TV operating system allowing users to access apps such as streaming services, which was released in 2004.&lt;br /&gt;
&lt;br /&gt;
==Consumer-protection summary==&lt;br /&gt;
&lt;br /&gt;
====Privacy&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;https://docs.roku.com/published/userprivacypolicy/en/us&amp;lt;/ref&amp;gt;====&lt;br /&gt;
&lt;br /&gt;
*Roku collects personal information such as the user&#039;s device information, usage data, viewing activity, and location data.&lt;br /&gt;
*This data is used for purposes such as providing and improving services, personalizing content, and targeted advertisements.&lt;br /&gt;
*Roku retains personal data for as long as deemed necessary.&lt;br /&gt;
*On many of their devices and services such as Roku OS, &amp;quot;Do not sell my personal information&amp;quot; is opt-out rather than opt-in.&lt;br /&gt;
&lt;br /&gt;
====Transparency====&lt;br /&gt;
&lt;br /&gt;
*The &amp;quot;Do not sell my personal information&amp;quot; setting on Roku OS is hidden behind many menus.&lt;br /&gt;
*Roku states the added forced arbitration clause was a decision made separate of the data breach (More on this below). This has obviously led to skepticism on the companies&#039; overall truthfulness.&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;https://www.bleepingcomputer.com/news/security/over-15-000-hacked-roku-accounts-sold-for-50-each-to-buy-hardware/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer-protection incidents==&lt;br /&gt;
&lt;br /&gt;
===Post-Purchase EULA Modification (Mar. 2024)===&lt;br /&gt;
[[File:Roku Forced Arbitration.jpg|thumb|510x510px|The screen in which consumers agreed to force arbitration. There is no &amp;quot;disagree.&amp;quot;&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;https://www.techhive.com/article/2258136/rokus-forced-arbitration-update-leaves-users-fuming.html&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
In early March 2024, Roku Inc. [[Post-purchase EULA modification|modified]] its [[End-User License Agreement|End-user license agreement]] (EULA), after the company disclosed a data breach that affected 15,000 accounts.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt; In April 2024, Roku disclosed another incident that affected 576,000 additional accounts.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This new EULA was enforced onto pre-existing users in the form of a message on their Smart TV/streaming player, which only allowed the user to accept the new terms, and did not offer an option to decline. The only option Roku Inc. offered to opt-out of the new EULA was for the user to mail the company their contact information and email used to register the Roku account (if applicable), along with the product model, software, or service &amp;quot;at issue.&amp;quot; In this new EULA, Roku included a [[forced arbitration]] agreement to not allow users to sue, or to take part in lawsuits against Roku Inc.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; Roku claimed a week later that the new EULA was not in relation to the aforementioned data breach.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;HDMI-customized ad insertion&amp;quot; patent (Oct. 2023)===&lt;br /&gt;
In early October 2023, Roku filed a patent ([https://patents.google.com/patent/US20230388589A1/en US20230388589A1]) for a program to insert ads on top of the display output of any non-Roku device displayed on a Roku TV. This program would be able to detect when the consumer has paused a video feed and display an advertisement, personalized by data collected through Roku services.&amp;lt;ref&amp;gt;https://patents.google.com/patent/US20230388589A1/en&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As of January 2025, this patent has not been implemented into any Roku devices. However, a similar feature which also detects content from connected devices, called &amp;quot;More Ways to Watch,&amp;quot; has previously been implemented.&amp;lt;ref&amp;gt;https://support.roku.com/article/115005739288&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://www.cnet.com/tech/home-entertainment/roku-tvs-now-track-what-you-watch-to-suggest-streams-target-ads/&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:Electronics companies]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=6918</id>
		<title>Disney wrongful-death lawsuit</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=6918"/>
		<updated>2025-01-30T14:36:23Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Legal Lockout]]&lt;br /&gt;
===The EPCOT death lawsuit and Disney&#039;s arbitration clause===&lt;br /&gt;
In a wrongful-death lawsuit,&amp;lt;ref&amp;gt;[[:File:AUGUST 2ND RESPONSE.pdf|&amp;quot;AUGUST 2ND RESPONSE.pdf&amp;quot;]] - wiki.rossmanngroup.com - accessed 2025-01-29 &amp;lt;/ref&amp;gt; Jeffrey Piccolo sued Walt Disney Parks &amp;amp; Resorts (WDPR) and Great Irish Pubs Florida, Inc. after his wife, Dr. Kanokporn Tangsuan, died from a severe allergic reaction at Raglan Road Irish Pub in Disney Springs on October 5, 2023. The lawsuit accused the restaurant and Disney of negligence in accommodating her food allergy, which contributed to her death.&amp;lt;ref name=&amp;quot;nprdwd&amp;quot;&amp;gt;[https://www.npr.org/2024/08/14/nx-s1-5074830/disney-wrongful-death-lawsuit-disney &amp;quot;Disney backtracks on request to toss wrongful death suit over Disney+ agreement&amp;quot;] - npr.org - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
Dr. Tangsuan, a family-medicine specialist at NYU Langone Hospital, had severe allergies to dairy and nuts. She and her family chose to dine at Raglan Road, specifically because Disney had advertised that they accommodate guests with food allergies throughout their properties. Despite Dr. Tangsuan repeatedly informing her server about her allergies and receiving multiple assurances that their ordered dishes would be allergen-free, Dr. Tangsuan suffered a severe allergic reaction approximately 45 minutes after eating. Although she self-administered an EpiPen, she later died at the hospital. The medical examiner confirmed her death was due to anaphylaxis from elevated levels of dairy and nuts in her system.&amp;lt;ref name=&amp;quot;nytdwd&amp;quot;&amp;gt;[https://www.nytimes.com/2024/08/14/nyregion/disney-wrongful-death-lawsuit-arbitration.html &amp;quot;Can a Disney+ Subscription Keep a Widower From Suing Disney in Court?&amp;quot;] - nytimes.com - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The EULA roofie attempt==&lt;br /&gt;
In May 2024, Disney attempted to have the case dismissed from court and sent to [[Forced Arbitration|arbitration]], citing two separate [[EULA|user agreements]]:&lt;br /&gt;
&lt;br /&gt;
#The Disney+ user agreement Piccolo accepted in 2019 when signing up for a free trial to Disney&#039;s streaming service on his PlayStation&lt;br /&gt;
#Terms accepted when purchasing (ultimately unused) Epcot tickets through the My Disney Experience app in September 2023&lt;br /&gt;
&lt;br /&gt;
This represented a classic example of a [[EULA roofie]], where Disney attempted to use terms buried within a streaming-service agreement to deny a consumer&#039;s right to sue over an unrelated wrongful-death case at a restaurant. Disney argued that because Piccolo had clicked &amp;quot;Agree &amp;amp; Continue&amp;quot; when signing up for the Disney+ streaming service, he was bound by an arbitration clause for any legal claims against the company or its affiliates. This, they argued, included the food served by a restaurant on their premises that killed his wife, even if the issue was unrelated to the streaming service.&lt;br /&gt;
&lt;br /&gt;
Disney said that the reason for trying to send the case to arbitration was because the restaurant &amp;quot;is neither owned nor operated by Disney&amp;quot; and that they were defending themselves against inclusion in the lawsuit.&amp;lt;ref&amp;gt;[https://edition.cnn.com/2024/08/14/business/disney-plus-wrongful-death-lawsuit/index.html &amp;quot;Disney wants wrongful death suit thrown out because widower bought an Epcot ticket and had Disney+&amp;quot;] - edition.cnn.com - accessed 2025-01-29&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Legal arguments===&lt;br /&gt;
Piccolo&#039;s attorneys filed a 123-page response calling Disney&#039;s argument &amp;quot;preposterous&amp;quot; and &amp;quot;fatally flawed&amp;quot; for several reasons:&lt;br /&gt;
&lt;br /&gt;
*Mr. Piccolo brought the lawsuit as Personal Representative of his wife&#039;s estate, not as him the individual&lt;br /&gt;
*The estate itself never agreed to any arbitration terms&lt;br /&gt;
*The estate did not exist at the time Mr. Piccolo accepted the Disney+ terms, as Dr. Tangsuan was still alive&lt;br /&gt;
*The Disney+ Subscriber Agreement was specifically limited to disputes concerning the streaming service&lt;br /&gt;
*Disney had already waived any right to arbitration by participating in the litigation before raising the issue&lt;br /&gt;
&lt;br /&gt;
The attorneys argued that &amp;quot;the notion that terms agreed to by a consumer when creating a Disney+ free trial account would forever bar that consumer&#039;s right to a jury trial in any dispute with any Disney affiliate or subsidiary, is so outrageously unreasonable and unfair as to shock the judicial conscience.&amp;quot;&amp;lt;ref name=&amp;quot;nytdwd&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Procedural timeline==&lt;br /&gt;
Disney had initially participated in discovery and filed an answer to the complaint without raising arbitration as a defense. Only later did the company attempt to use the [[End-User License Agreement|End-user license agreement]] (EULA) to avoid litigation. As noted in its second response, in August: &amp;quot;WDPR has waived its alleged right to seek arbitration by filing its Answer without raising arbitration as an affirmative defense and by serving two separate Requests for Copies under Rule 1.351(e).&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 3&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Key legal issues around consumer rights==&lt;br /&gt;
===Meeting of minds===&lt;br /&gt;
The response highlighted fundamental contract-law principles that challenge the validity of using broad EULAs to bind consumers. As stated in the filing, Disney&#039;s attempt violated basic principles of contract formation including &amp;quot;meeting of the minds (mutual understanding between parties)&amp;quot; and &amp;quot;good-faith dealing&amp;quot;.&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 11&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Unconscionability===&lt;br /&gt;
The response detailed both procedural and substantive unconscionability in Disney&#039;s EULA:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Procedural unconscionability:&#039;&#039;&#039;&lt;br /&gt;
**&amp;quot;There was no showing that Mr. Piccolo was given any explanation of the arbitration clauses in The Disney+ Subscriber Agreement.&amp;quot;&lt;br /&gt;
**&amp;quot;The so-called binding arbitration provision was merely contained in a link. With respect to the Disney Terms of Use, the link was not even referenced or hyperlinked on the Disney+ registration page. It was buried within another document that was hyperlinked.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 27-28&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Substantive unconscionability:&#039;&#039;&#039;&lt;br /&gt;
**The arbitration provisions &amp;quot;could present a problem for more than just their own client&amp;quot;&lt;br /&gt;
**&amp;quot;In effect, WDPR is explicitly seeking to bar its 150 million Disney+ subscribers from ever prosecuting a wrongful death case against it in front of a jury even if the case facts have nothing to with Disney+&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 30&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The Florida Supreme Court has acknowledged there is some overlap in the analysis of whether a valid written agreement to arbitrate exists and whether an arbitrable issue exists, noting: &#039;It is something of a chicken and egg situation as to which comes first.&#039; This highlights the fundamental problem with modern EULAs - consumers cannot meaningfully assess what rights they&#039;re giving up when agreeing to terms that may be interpreted to cover any future dispute with any related corporate entity.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 19&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Resolution==&lt;br /&gt;
Following significant public backlash and media attention highlighting how this could affect Disney+&#039;s 150 million subscribers, Disney withdrew its motion to compel arbitration in August 2024. Josh D&#039;Amaro, chairman of Disney Experiences, stated: &amp;quot;At Disney, we strive to put humanity above all other considerations… With such unique circumstances as the ones in this case, we believe this situation warrants a sensitive approach to expedite a resolution for the family who have experienced such a painful loss.&amp;quot;&amp;lt;ref name=&amp;quot;nprdwd&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Significance==&lt;br /&gt;
&lt;br /&gt;
The response specifically addressed how Disney&#039;s EULA-roofie attempt represents the type of modern consumer exploitation that traditional consumer protection laws fail to address: the potential dangers of overly broad arbitration clauses in consumer agreements and their use to deny access to courts even in serious cases like wrongful death. It demonstrates how companies may attempt to use unrelated consumer agreements to strip away fundamental legal rights, making it a notable example of the EULA-roofie phenomenon. The case also showed how public attention and backlash can sometimes force companies to reconsider such tactics. This case demonstrated how companies use complex legal documents and digital agreements to manufacture consent for terms that a reasonable consumer would never knowingly accept, as a customer might be less likely to sign up for a free trial of a streaming service if he knew it would absolve the company from accountability for killing his wife. &lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Lawsuits]]&lt;br /&gt;
[[Category:EULA roofieing]]&lt;br /&gt;
[[Category:Disney]]&lt;br /&gt;
[[Category:Articles based on videos]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Valve_removes_arbitration_requirement_from_Steam_Subscriber_Agreement&amp;diff=6917</id>
		<title>Valve removes arbitration requirement from Steam Subscriber Agreement</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Valve_removes_arbitration_requirement_from_Steam_Subscriber_Agreement&amp;diff=6917"/>
		<updated>2025-01-30T14:35:58Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In September 2024, [[Valve]] removed both the individual [[Forced Arbitration|binding arbitration]] requirements and class-action waiver from the [https://store.steampowered.com/subscriber_agreement Steam Subscriber Agreement], which is, essentially, [[Steam]]&#039;s [[End-user license agreement]]. This was done because of a pending [https://storage.courtlistener.com/recap/gov.uscourts.wawd.337957/gov.uscourts.wawd.337957.1.0.pdf class-action lawsuit] wherein &amp;quot;the named Plaintiffs won binding decisions from arbitrators rendering Valve&#039;s arbitration provision unenforceable for both lack of notice and because it impermissibly seeks to bar public injunctive relief.&amp;quot;[1]&lt;br /&gt;
&lt;br /&gt;
== Implications ==&lt;br /&gt;
This restores consumer rights to both court litigation and class-action lawsuits, rather than being bound to forced arbitration, for resolving disputes with Steam.&lt;br /&gt;
&lt;br /&gt;
== Sources/Links ==&lt;br /&gt;
&lt;br /&gt;
* Link to the Steam news article: https://store.steampowered.com/news/app/593110/view/4696781406111167991. [https://web.archive.org/web/20240927180120/https://store.steampowered.com/oldnews/ Archived] from the original on 27 September, 2024. Retrieved 17 January, 2025.&lt;br /&gt;
* Link to the Steam Subscriber Agreement: https://store.steampowered.com/subscriber_agreement. [https://web.archive.org/web/20240928014938/https://store.steampowered.com/subscriber_agreement/ Archived] from the original on 28 September, 2024. Retrieved 17 January, 2025.&lt;br /&gt;
* Louis Rossmann&#039;s video on the news: https://www.youtube.com/watch?v=1f81qXxggo8&lt;br /&gt;
* NACA&#039;s arbitration definition: [https://www.consumeradvocates.org/for-consumers/arbitration/ https://www.consumeradvocates.org/for-consumers/arbitration/.] . [https://web.archive.org/web/20250101160116/https://www.consumeradvocates.org/for-consumers/arbitration/ Archived] from the original on 1 January, 2025. Retrieved 17 January, 2025.&lt;br /&gt;
* [1] &amp;quot;Steam doesn’t want to pay arbitration fees, tells gamers to sue instead&amp;quot;: https://arstechnica.com/tech-policy/2024/09/steam-doesnt-want-to-pay-arbitration-fees-tells-gamers-to-sue-instead/. [https://web.archive.org/web/20241217090450/https://arstechnica.com/tech-policy/2024/09/steam-doesnt-want-to-pay-arbitration-fees-tells-gamers-to-sue-instead/ Archived] from the original on 17 December, 2024. Retrieved 17 January, 2025.&lt;br /&gt;
&lt;br /&gt;
[[Category:Valve Corporation]]&lt;br /&gt;
[[Category:Articles based on videos]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=List_of_devices_requiring_account_for_initial_setup&amp;diff=6915</id>
		<title>List of devices requiring account for initial setup</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=List_of_devices_requiring_account_for_initial_setup&amp;diff=6915"/>
		<updated>2025-01-30T14:35:41Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You&#039;ve just bought your shiny new gadget. As you&#039;ve just unboxed it, you want to set it up. Unfortunately, you can&#039;t do anything with it as is. You have to pair it with some shady app on your smartphone and accept a lengthy [[End-user license agreement]] (EULA) just to test it. Then you have to create a new account that links your e-mail and other personal data to the device.&lt;br /&gt;
&lt;br /&gt;
Often this information is hidden deep inside a manual, and there are no mentions on the product page or box. Sometimes it&#039;s not even disclosed in the manual. You have to watch some random unboxing videos on YouTube, to get to know that you need to create an account to use the device. &lt;br /&gt;
&lt;br /&gt;
==Why not?==&lt;br /&gt;
&#039;&#039;&#039;Why would I want to avoid such devices?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Sometimes when you buy such a device, you can receive an open-box unit which is paired to an account of the previous owner. Unlinking it is often impossible without an access to paired account, as even the manufacturer&#039;s support refuses to do it, citing &amp;quot;security reasons&amp;quot;.&amp;lt;ref&amp;gt;https://ipcamtalk.com/threads/ezviz-c8c-camera-blocked-by-previous-owner.63418/#post-666651&amp;lt;/ref&amp;gt;&lt;br /&gt;
*You have to accept a lengthy EULA, often hiding [[EULA roofie|undesirable clauses]], such as [[forced arbitration]].&lt;br /&gt;
&lt;br /&gt;
==The list==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
!Manufacturer&lt;br /&gt;
!Model&lt;br /&gt;
!Notes&lt;br /&gt;
!Source&lt;br /&gt;
|-&lt;br /&gt;
|EZVIZ&lt;br /&gt;
|H6c, Probably all cameras&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref&amp;gt;https://mfs.ezvizlife.com/H6c_QSG_EN(EU)(V1.0.0).pdf?ver=52475 page 4&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|DJI&lt;br /&gt;
|Osmo Pocket 3&lt;br /&gt;
|Android app needs to be sideloaded, circumventing Google&#039;s Play Store security checks.&lt;br /&gt;
|&amp;lt;ref&amp;gt;https://support.dji.com/help/content?customId=en-us03400009024&amp;amp;spaceId=34&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|DJI&lt;br /&gt;
|RS 3 Mini&lt;br /&gt;
|Allows &amp;quot;5 trial uses&amp;quot; without activation.&lt;br /&gt;
|&amp;lt;ref&amp;gt;https://support.dji.com/help/content?customId=en-us03400007193&amp;amp;spaceId=34&amp;amp;re=US&amp;amp;lang=en &amp;quot;Activating the Gimbal&amp;quot; section&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|DJI&lt;br /&gt;
|RS 3 Pro&lt;br /&gt;
|Allows &amp;quot;5 trial uses&amp;quot; without activation.&lt;br /&gt;
|&amp;lt;ref&amp;gt;https://support.dji.com/help/content?customId=03400006898&amp;amp;spaceId=34&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|TP-Link&lt;br /&gt;
|Kasa Smart Wi-Fi Power Strip, 6-Outlet&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref&amp;gt;https://web.archive.org/web/20240629160455/https://static.tp-link.com/upload/manual/2021/202111/20211101/1910013111_HS300(US)_UG_V2.0.1.pdf&amp;quot;Set Up Your Smart Power Strip&amp;quot; section&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Canon&lt;br /&gt;
|EOS Webcam Utility software&lt;br /&gt;
|&lt;br /&gt;
|&amp;lt;ref&amp;gt;[[Requirement for Canon EOS Webcam Utility subscription to enable webcam features on cameras#User Frustrations]] Better source needed&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Sony&lt;br /&gt;
|WH-XB910N&lt;br /&gt;
|App is needed to be to change the switch for ambient sound / noise cancellation to including turning it off. Account is needed for the app&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
Some device groups have an unified idea about account requirements, even through different manufacturers.&lt;br /&gt;
&lt;br /&gt;
===IP cameras===&lt;br /&gt;
A lot of modern IP cameras do not have a traditional RTSP/HTTP video stream access, but need to be paired with an app. The smartphone app is the only means to view the camera stream. There&#039;s no sustainable way to record the stream locally. You are forced to use manufacturer&#039;s cloud storage subscription solution. &lt;br /&gt;
&lt;br /&gt;
Sometimes volunteers have provided a way to circumvent this restriction, providing an alternative firmware that an advanced user can flash.&amp;lt;ref&amp;gt;https://github.com/roleoroleo/yi-hack-Allwinner-v2&amp;lt;/ref&amp;gt; This is not an ideal solution, as the support is sometimes janky, and manufacturer can always block this in newer model revisions.&lt;br /&gt;
&lt;br /&gt;
===DJI===&lt;br /&gt;
All DJI devices appear to need account for setup. The Android app needs to be sideloaded, circumventing Google&#039;s Play Store security checks.&amp;lt;ref&amp;gt;https://drones.stackexchange.com/questions/2209/how-come-the-dji-fly-app-is-not-in-google-play-store&amp;lt;/ref&amp;gt; It was previously available on Play Store, but has been pulled off in 2021. DJI officially says it&#039;s due to changing &amp;quot;compatibility strategy&amp;quot;.&amp;lt;ref&amp;gt;https://web.archive.org/web/20211213081844/https://twitter.com/DJISupport/status/1470305900132913152&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Overview]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Hidden_EULA_language&amp;diff=6914</id>
		<title>Hidden EULA language</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Hidden_EULA_language&amp;diff=6914"/>
		<updated>2025-01-30T14:35:05Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;quot;EULA roofie&amp;quot; describes the practice of hiding contentious terms within an [[End-user license agreement]] (EULA). The term applies to situations where such terms, if made clear upfront, might cause a customer to second-guess their purchase. The term was coined by consumer rights advocate [[wikipedia:Louis_Rossmann|Louis Rossmann]]&amp;lt;sup&amp;gt;[source?]&amp;lt;/sup&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
This term highlights the unethical business practice of &amp;quot;manufacturing consent&amp;quot; for terms which a reasonable and informed customer might reject. It also emphasizes the erosion of informed consent through shaming and conformity.&lt;br /&gt;
&lt;br /&gt;
By hiding contentious or unconscionable terms in dense legal documents, manufacturers exploit:&lt;br /&gt;
&lt;br /&gt;
#the consumer&#039;s lack of proficiency in understanding legal documents, and&lt;br /&gt;
#the impracticality of reading long documents in order to meet one&#039;s basic human needs.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;EULA roofie&amp;quot; applies to individuals and corporations that utilize these practices to secure and manufacture consent under these false pretenses.&lt;br /&gt;
&lt;br /&gt;
According to Rossmann, just as drugging someone (&amp;quot;roofying&amp;quot;) to secure agreement is indefensible, so too is the act of concealing ethically or morally questionable terms in the fine print of a contract. The term &amp;quot;EULA roofie&amp;quot; attempts to draw a greater degree of societal scorn, scrutiny, and condemnation towards these actions, as they are seen at best as a minor legal nuisance rather than a disregard for informed consent and human rights.&lt;br /&gt;
&lt;br /&gt;
==Core Concept==&lt;br /&gt;
The term &amp;quot;EULA roofie&amp;quot; describes three key deceptive practices:&lt;br /&gt;
&lt;br /&gt;
#Burying unattractive terms deep within an End User License Agreement (while avoiding mention of them in marketing materials and customer-facing interfaces).&lt;br /&gt;
#Making the full terms impractical or impossible for the customer to meaningfully review.&lt;br /&gt;
#Pointing to the End User License Agreement as a justification for unpopular practices.&lt;br /&gt;
&lt;br /&gt;
==Notable Examples==&lt;br /&gt;
&lt;br /&gt;
===Sony PlayStation Store===&lt;br /&gt;
Sony prominently displays &#039;&#039;&amp;quot;PURCHASE&amp;quot;&#039;&#039; buttons for digital content but buries a redefinition of the word &amp;quot;purchase&amp;quot; in Section 10.1 of their Terms of Service:&amp;lt;ref&amp;gt;PLAYSTATION&amp;lt;sup&amp;gt;TM&amp;lt;/sup&amp;gt; NETWORK TERMS OF SERVICE AND USER AGREEMENT, December 30th, 2023: https://web.archive.org/web/20231230163548/https://www.playstation.com/en-us/legal/psn-terms-of-service/&amp;lt;/ref&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;quot;Use of the terms &#039;own,&#039; &#039;ownership&#039;, &#039;purchase,&#039; &#039;sale,&#039; &#039;sold,&#039; &#039;sell,&#039; &#039;rent&#039; or &#039;buy&#039;… does not mean or imply any transfer of ownership…&amp;quot;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This became an issue in 2023 when Sony and Discovery removed previously &amp;quot;purchased&amp;quot; content from users&#039; libraries, citing terms hidden in their service agreement.&amp;lt;ref&amp;gt;Playstation Video Content: Legal Update Notice https://web.archive.org/web/20231203150040/https://www.playstation.com/en-us/legal/psvideocontent/&amp;lt;/ref&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
Placing disclaimers such as &amp;quot;We may take away and remove television and movies you bought &amp;amp; paid for at any time, because purchase doesn&#039;t mean purchase anymore&amp;quot; next to the &amp;quot;Add to cart&amp;quot; button would understandably negatively affect sales. Therefore, Sony buries this information on page 21 of their Terms of Service.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Valve Steam Store&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Valve does something identical to Sony in the it says you are &amp;quot;PURCHASING&amp;quot; a game but redefined what the word &amp;quot;purchase&amp;quot; means in Section 1 of their terms of service. [3]&lt;br /&gt;
&lt;br /&gt;
# 1. LIMITED LICENSE; RESTRICTIONS AND OWNERSHIP - this Agreement does not give you any right to obtain reissues or replacements of the Game at any time and ZeniMax [valve]  is not obliged to supply software updates, upgrades, or expansions for the Game, or even to operate or continue to support the Game for an indefinite period.&lt;br /&gt;
# Valve may change, modify, suspend, or discontinue any aspect of the Game at any time and Valve may also impose limits on certain features or restrict your access to parts or all of the Game without notice or liability.&lt;br /&gt;
&lt;br /&gt;
This is essentially saying your &#039;ownership&#039; amounts to nothing, as they say in the EULA they can discontinue the game you purchased at at any time they wish. You are merely leasing a game when you &#039;purchase&#039; a game from steam. There will be a lot of blow back on this because most people think they own their steam games but there is no argument to be made when it says right their in their EULA that you in face only own it for only they amount of time Valve decides to support it. At any time, and for no reason other than they want to, the game you purchased will no longer be playable. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In this same EULA they clearly state they can modify the terms and conditions at any time and you are responsible for keeping up with the new terms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[3] footnote - https://store.steampowered.com/eula/1716740_eula_0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Smart Appliance Data Collection &amp;amp; Third-Party Data Sharing===&lt;br /&gt;
[[File:LG ThinQ app terms of service part 1.webp|alt=LG ThinQ app terms of service from July 2024, for use of an LG smart washing machine|thumb|LG ThinQ app terms of service from July 2024, for use of an LG smart washing machine]]&lt;br /&gt;
[[File:LG ThinQ app TOS.webp|alt=LG ThinQ app terms of service from July 2024, for use of an LG smart washing machine: part 2 of 3.|thumb|LG ThinQ app terms of service from July 2024, for use of an LG smart washing machine: part 2 of 3.]]&lt;br /&gt;
[[File:LG ThinQ app terms of service from July 2024, for use of an LG smart washing machine- part 3 of 3..webp|thumb]]&lt;br /&gt;
&lt;br /&gt;
LG Electronics (among others) require users to accept extensive terms of service and privacy policies to use the &amp;quot;smart&amp;quot; features on home appliances, such as washing machines.   &lt;br /&gt;
&lt;br /&gt;
While the &amp;quot;smart&amp;quot; features may have time-saving benefits, the time required to actually read and decipher these documents (often 3+ hours, especially for non-tech-savvy users) negates any time-saving benefits of the smart features themselves. This makes meaningful informed consent impractical.  &lt;br /&gt;
&lt;br /&gt;
A consumer has to read the complete Privacy Policy (see attached images below) to learn that LG collects their personal data and shares it with their advertising partners. Futhermore, this Privacy Policy is only shown to the customer once they have bought the LG product. &lt;br /&gt;
&lt;br /&gt;
==Consumer Impact==&lt;br /&gt;
The practice undermines informed consent in digital transactions by:&lt;br /&gt;
&lt;br /&gt;
*Using lengthy documents (often 50+ pages) to hide terms that deprive the consumer of their privacy and their rights.&lt;br /&gt;
*Employing complex legal language to obscure the real meaning of agreements.&lt;br /&gt;
*Placing important information deep within documents where it is unlikely to be found.&lt;br /&gt;
*Presenting one meaning of terms (like &amp;quot;purchase&amp;quot;) in the user interface while legally defining them differently in hidden terms.&lt;br /&gt;
&lt;br /&gt;
==Legal Context==&lt;br /&gt;
While EULAs and Terms of Service are legally binding documents, the &amp;quot;EULA roofie&amp;quot; concept challenges their legitimacy by highlighting how they may violate principles of contract law such as:&lt;br /&gt;
&lt;br /&gt;
*Meeting of the minds (mutual understanding between parties).&lt;br /&gt;
*Good-faith dealing.&lt;br /&gt;
*Reasonable notice of terms.&lt;br /&gt;
*Unconscionability (terms so unfair they shock the conscience).&lt;br /&gt;
&lt;br /&gt;
==Consumer Protection Response==&lt;br /&gt;
The concept has been used in advocacy for:&lt;br /&gt;
&lt;br /&gt;
*Plain-language requirements in consumer agreements.&lt;br /&gt;
*Prominent disclosure of significant terms.&lt;br /&gt;
*Reform of digital ownership rights.&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
&lt;br /&gt;
*[https://tosdr.org/en/ TOSDR] &amp;amp;emdash; Helps consumers to understand and review terms of service policies&lt;br /&gt;
*[https://tosback.org/ TOSBack] &amp;amp;emdash; Helps consumers to understand and review terms of service policies&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Anti-Consumer_Practices]]&lt;br /&gt;
[[Category:Common terms]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=User:Tpat90/Sandbox%F0%9F%AB%96&amp;diff=6899</id>
		<title>User:Tpat90/Sandbox🫖</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=User:Tpat90/Sandbox%F0%9F%AB%96&amp;diff=6899"/>
		<updated>2025-01-30T14:13:27Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Created page with &amp;quot;This is a test to break kostas assumption that 🫖 and other utf 16 characters would be of problem.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a test to break kostas assumption that 🫖 and other utf 16 characters would be of problem.&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Sandbox&amp;diff=6894</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Sandbox&amp;diff=6894"/>
		<updated>2025-01-30T14:11:31Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Let&amp;#039;s see how it reacts to 🫖&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a place to experiment. It&#039;s the best place to test out modifications to template code without affecting the rest of the wiki, but it can be used for any form of experimentation. &lt;br /&gt;
&lt;br /&gt;
Some other wikis have their sandboxes in the wiki&#039;s namespace (CAT in our case). Also, some wikis reset this page periodically, but that can probably be done manually for now.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
🫖🫖🫖&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Shortage_of_medical_ventilators_during_COVID-19_pandemic&amp;diff=6891</id>
		<title>Shortage of medical ventilators during COVID-19 pandemic</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Shortage_of_medical_ventilators_during_COVID-19_pandemic&amp;diff=6891"/>
		<updated>2025-01-30T14:07:25Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&lt;br /&gt;
During the COVID crisis, manufacturers like General Electric, Dräger, Steris,  locked down the supply of spare parts, software and repair manuals behind expensive certifications for technicians, and threaten &lt;br /&gt;
&lt;br /&gt;
https://www.businessinsider.com/ventilator-manufacturers-dont-let-hospitals-fix-coronavirus-right-to-repair-2020-5?op=1&lt;br /&gt;
&lt;br /&gt;
https://www.vice.com/en/article/a-medical-device-maker-threatens-ifixit-over-ventilator-repair-project/&lt;br /&gt;
&lt;br /&gt;
https://pirg.org/media-center/new-senate-right-to-repair-bill-to-reduce-barriers-to-fixing-medical-equipment-including-ventilators/&lt;br /&gt;
&lt;br /&gt;
https://www.extremetech.com/extreme/312560-deadly-drm-right-to-repair-a-life-or-death-problem-during-the-coronavirus-pandemic&lt;br /&gt;
&lt;br /&gt;
https://www.vice.com/en/article/ventilator-companies-finally-make-the-life-saving-devices-easier-to-repair/&lt;br /&gt;
&lt;br /&gt;
https://scholarship.shu.edu/cgi/viewcontent.cgi?article=1816&amp;amp;context=shlr&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Shortage_of_medical_ventilators_during_COVID-19_pandemic&amp;diff=6890</id>
		<title>Shortage of medical ventilators during COVID-19 pandemic</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Shortage_of_medical_ventilators_during_COVID-19_pandemic&amp;diff=6890"/>
		<updated>2025-01-30T14:07:00Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: stubbed&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{stub}}&lt;br /&gt;
&lt;br /&gt;
During the COVID crisis, manufacturers like General Electric, Dräger, Steris,  locked down the supply of spare parts, software and repair manuals behind expensive certifications for technicians, and threaten &lt;br /&gt;
&lt;br /&gt;
https://www.businessinsider.com/ventilator-manufacturers-dont-let-hospitals-fix-coronavirus-right-to-repair-2020-5?op=1&lt;br /&gt;
&lt;br /&gt;
https://www.vice.com/en/article/a-medical-device-maker-threatens-ifixit-over-ventilator-repair-project/&lt;br /&gt;
&lt;br /&gt;
https://pirg.org/media-center/new-senate-right-to-repair-bill-to-reduce-barriers-to-fixing-medical-equipment-including-ventilators/&lt;br /&gt;
&lt;br /&gt;
https://www.extremetech.com/extreme/312560-deadly-drm-right-to-repair-a-life-or-death-problem-during-the-coronavirus-pandemic&lt;br /&gt;
&lt;br /&gt;
https://www.vice.com/en/article/ventilator-companies-finally-make-the-life-saving-devices-easier-to-repair/&lt;br /&gt;
&lt;br /&gt;
https://scholarship.shu.edu/cgi/viewcontent.cgi?article=1816&amp;amp;context=shlr&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=John_Deere&amp;diff=6849</id>
		<title>John Deere</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=John_Deere&amp;diff=6849"/>
		<updated>2025-01-30T12:10:24Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&#039;&#039;&#039;[[wikipedia:John Deere|John Deere]]&#039;&#039;&#039; is a leading manufacturer of agricultural and heavy machinery. Founded in 1837, they are primarily known for their heavy-duty agriculture machines, such as tractors and combines. They have recently faced criticism for their business practices, especially in the realm of equipment repair. These practices have raised concerns among farmers, independent repair technicians, and consumer-advocacy groups.&amp;lt;ref name=&amp;quot;jdflrtrt&amp;quot;&amp;gt;https://www.npr.org/2025/01/15/nx-s1-5260895/john-deere-ftc-lawsuit-right-to-repair-tractors&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{InfoboxCompany&lt;br /&gt;
| Name = John Deere&lt;br /&gt;
| Type = Public&lt;br /&gt;
| Founded = 1837&lt;br /&gt;
| Industry = Agricultural machinery, Heavy equipment&lt;br /&gt;
| Official Website = https://deere.com/&lt;br /&gt;
| Logo = John Deere logo.png&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Consumer-protection profile==&lt;br /&gt;
[[File:John deere doc.png|thumb|524x524px|Front Page of the FTC&#039;s Suit Against John Deere&amp;lt;ref name=&amp;quot;DCRCCN325&amp;quot;&amp;gt;https://www.ftc.gov/system/files/ftc_gov/pdf/DeereCoREDACTEDComplaintCaseNo325-cv-50017.pdf&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
====Repairability====&lt;br /&gt;
&lt;br /&gt;
*John Deere limits access to essential repair software and diagnostic tools.&amp;lt;ref name=&amp;quot;dith3&amp;quot;&amp;gt;https://pirg.org/resources/deere-in-the-headlights-3/&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Restrictive policies prevent farmers from performing repairs or using independent repair shops, forcing them to rely on authorized dealerships.&amp;lt;ref name=&amp;quot;jdflrtrt&amp;quot; /&amp;gt;&lt;br /&gt;
*Farmers have reported being unable to fix minor mechanical issues without John Deere&#039;s proprietary tools.&amp;lt;ref name=&amp;quot;fssdcp&amp;quot;&amp;gt;https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-states-sue-deere-company-protect-farmers-unfair-corporate-tactics-high-repair-costs&amp;lt;/ref&amp;gt;&lt;br /&gt;
*John Deere has allegedly unlawfully inflated repair costs by controlling the repair-service market.&lt;br /&gt;
&lt;br /&gt;
====Monopoly on repairs====&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; John Deere&#039;s control over the repair market has been likened to monopolistic behavior.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; By restricting and controlling access to repair resources and parts, the company has effectively eliminated competition in the repair market.&amp;lt;ref&amp;gt;https://www.courthousenews.com/ftc-accuses-john-deere-of-unlawful-equipment-repair-practices/&amp;lt;/ref&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Digital rights and ownership====&lt;br /&gt;
&lt;br /&gt;
*John Deere uses software locks and [[digital rights management]] (DRM) systems that control user autonomy.&amp;lt;ref&amp;gt;https://pirg.org/edfund/resources/john-deere-repair-software/&amp;lt;/ref&amp;gt;&lt;br /&gt;
*These measures prevent farmers and independent repair technicians from completing repairs without access to the proprietary software.&amp;lt;ref name=&amp;quot;dith3&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Opposition to right-to-repair legislation====&lt;br /&gt;
&lt;br /&gt;
*John Deere has actively lobbied against [[Right to repair|right-to-repair]] legislation in multiple states, and on the federal level. &amp;lt;ref&amp;gt;[https://pirg.org/resources/john-deere-and-right-to-repair-over-the-years/?utm_source=chatgpt.com https://pirg.org/resources/john-deere-and-right-to-repair-over-the-years/]&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;[https://wisconsinwatch.org/2024/04/midwest-farmers-right-to-repair-agriculture-john-deere-illinois/?utm_source=chatgpt.com https://wisconsinwatch.org/2024/04/midwest-farmers-right-to-repair-agriculture-john-deere-illinois/]&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Despite signing a memorandum of understanding with the American Farm Bureau Federation in 2023, the company has been accused of undermining the spirit of the agreement.&amp;lt;ref&amp;gt;[https://investigatemidwest.org/2024/11/12/is-john-deeres-day-of-reckoning-soon-at-hand/#:~:text=In%20a%20nutshell%3A%20Deere%20embeds%20authorization%20codes%20in,dealers%20have%20access%20to%20all%20the%20verification%20codes. https://investigatemidwest.org/2024/11/12/is-john-deeres-day-of-reckoning-soon-at-hand/#:~:text=In%20a%20nutshell%3A%20Deere%20embeds%20authorization%20codes%20in,dealers%20have%20access%20to%20all%20the%20verification%20codes.]&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=7-RgOUT3zeo&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Consumer-protection incidents==&lt;br /&gt;
&lt;br /&gt;
====FTC Lawsuit (January 2025)====&lt;br /&gt;
On January 15, 2025, the [[Federal Trade Commission]] (FTC) filed a lawsuit against John Deere, alleging anticompetitive practices in the repair market.&amp;lt;ref name=&amp;quot;fssdcp&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;DCRCCN325&amp;quot; /&amp;gt; The lawsuit claims that:&lt;br /&gt;
&lt;br /&gt;
*John Deere unlawfully inflated repair costs by monopolizing the repair-service market.&lt;br /&gt;
*The company&#039;s restrictive policies violated consumer-protection laws and limited farmers&#039; ability to maintain their equipment.&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
&lt;br /&gt;
* [[John Deere dealerships are lobbying against right to repair]]&lt;br /&gt;
* [[John Deere employee responds to Right to Repair]]&lt;br /&gt;
* [[John Deere fails to uphold right to repair agreement]]&lt;br /&gt;
* [[John Deere security flaws exposed sensitive customer information]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Agricultural machinery manufacturers]]&lt;br /&gt;
[[Category:Tractor manufacturers]]&lt;br /&gt;
[[Category:Garden tool manufacturers]]&lt;br /&gt;
[[Category:Construction equipment manufacturers]]&lt;br /&gt;
[[Category:Engine manufacturers]]&lt;br /&gt;
[[Category:Defense companies]]&lt;br /&gt;
[[Category:Automotive transmission makers]]&lt;br /&gt;
[[Category:Electrical generation engine manufacturers]]&lt;br /&gt;
[[Category:Tool manufacturing companies of the United States]]&lt;br /&gt;
[[Category:John Deere]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=6673</id>
		<title>Newag</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=6673"/>
		<updated>2025-01-29T19:46:40Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Newag S.A.&#039;&#039;&#039; (pronounced &#039;&#039;&amp;quot;nevag&amp;quot;&#039;&#039;) is a Polish company based in Nowy Sącz that specializes in the production, maintenance, and modernization of railway rolling stock.&amp;lt;ref&amp;gt;https://www.newag.pl/en/company/history/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Backdoor incident==&lt;br /&gt;
In 2022, when maintenance was done on trains manufactured by &#039;&#039;&#039;Newag&#039;&#039;&#039;, malicious code and backdoors were discovered which were found to make the trains break down after third-party repairs, prevent them from entering a competitors workshop and also stop working after a set amount of time standing still.&amp;lt;ref&amp;gt;[https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/?utm_source=chatgpt.com https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/]&amp;lt;/ref&amp;gt; The investigation against &#039;&#039;&#039;Newag&#039;&#039;&#039; is still on-going.&lt;br /&gt;
&lt;br /&gt;
==Sources==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=6672</id>
		<title>Newag</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=6672"/>
		<updated>2025-01-29T19:45:47Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{stub}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Newag S.A.&#039;&#039;&#039; (pronounced &#039;&#039;&amp;quot;nevag&amp;quot;&#039;&#039;) is a Polish company based in Nowy Sącz that specializes in the production, maintenance, and modernization of railway rolling stock.&amp;lt;ref&amp;gt;https://www.newag.pl/en/company/history/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Backdoor incident==&lt;br /&gt;
In 2022, when maintenance was done on trains manufactured by &#039;&#039;&#039;Newag&#039;&#039;&#039;, malicious code and backdoors were discovered which were found to make the trains break down after third-party repairs, prevent them from entering a competitors workshop and also stop working after a set amount of time standing still.&amp;lt;ref&amp;gt;[https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/?utm_source=chatgpt.com https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/]&amp;lt;/ref&amp;gt; The investigation against &#039;&#039;&#039;Newag&#039;&#039;&#039; is still on-going.&lt;br /&gt;
&lt;br /&gt;
==Sources==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=User_talk:Louis&amp;diff=6229</id>
		<title>User talk:Louis</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=User_talk:Louis&amp;diff=6229"/>
		<updated>2025-01-28T13:07:46Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: /* can&amp;#039;t fully agree to user page, seems like a biased opinion */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi, If you are Louis Rossmann please fix [[Template:Cite web]]. Great Wiki. Thanks. [[User:Jack Franks|Jack Franks]] ([[User talk:Jack Franks|talk]]) 19:32, 19 January 2025 (UTC)&lt;br /&gt;
&lt;br /&gt;
== can&#039;t fully agree to user page, seems like a biased opinion ==&lt;br /&gt;
&lt;br /&gt;
The user page doesn&#039;t disagrees with the mission statement. There isn&#039;t any reference attached to it and I never heard Louis say he is a cool person. Please add references! [[User:Tpat90|Tpat90]] ([[User talk:Tpat90|talk]]) 13:07, 28 January 2025 (UTC)&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=LG_refrigerator_warranty_scandal&amp;diff=6015</id>
		<title>LG refrigerator warranty scandal</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=LG_refrigerator_warranty_scandal&amp;diff=6015"/>
		<updated>2025-01-27T19:34:33Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==&#039;&#039;&#039;LG Linear Compressor Refrigerator Failures &amp;amp; Arbitration&#039;&#039;&#039;==&lt;br /&gt;
Here we&#039;ll go over a systematic pattern of early refrigerator failures &amp;amp; attempts by LG Electronics to prevent consumer lawsuits regarding their lack of warranty coverage for failed fridges through contested arbitration practices.&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
LG Electronics faced widespread consumer complaints due to systematic failures of their linear compressor refrigerators, with many reports of units failing within 2-5 years in spite of being advertised with a 10-year warranty &amp;amp; 20-year lifespan.&amp;lt;ref&amp;gt;[https://www.nbcbayarea.com/investigations/consumer/lg-refrigerators-failures-update/3465620/ NBC Bay Area, &amp;quot;Fridge failures: LG says angry owners can&#039;t sue, company points to cardboard box&amp;quot;, February 27, 2024]&amp;lt;/ref&amp;gt; The company&#039;s response to these failures has focused on attempting to force consumers into private arbitration rather than addressing the underlying product flaws, where LG cites arbitration notices that most consumers never had the opportunity to see.&lt;br /&gt;
&lt;br /&gt;
==The Linear Compressor Issue==&lt;br /&gt;
===Pattern of Failures===&lt;br /&gt;
Many documented cases show LG&#039;s linear compressor refrigerators failing well before their advertised lifespan:&lt;br /&gt;
&lt;br /&gt;
*Reports of compressors failing within 24 months of purchase&amp;lt;ref&amp;gt;NBC Bay Area interview with Sunil Kardile, February 27, 2024: &amp;quot;The compressor dies like every year&amp;quot;&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Multiple customers requiring 4-5 compressor replacements within a few years&lt;br /&gt;
*Consistent pattern of failures happening shortly after the standard warranty period&lt;br /&gt;
&lt;br /&gt;
===Cost to Consumers===&lt;br /&gt;
While LG&#039;s warranty covers the compressor part itself, consumers report large financial impact:&lt;br /&gt;
&lt;br /&gt;
*Labor costs averaging $1,000 per repair despite part coverage&amp;lt;ref&amp;gt;[https://www.reddit.com/r/technology/comments/1b3d8yr/comment/ksrtouv/?utm_source=share&amp;amp;utm_medium=web3x&amp;amp;utm_name=web3xcss&amp;amp;utm_term=1&amp;amp;utm_content=share_button Reddit discussion r/technology, January 2024: &amp;quot;I&#039;ve had two LG fridge compressors go bad. They cover the part but not the labor and I&#039;ve spent more than $1000 installing new compressors into them&amp;quot;]&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Extended periods without functioning refrigeration while awaiting repairs&amp;lt;ref&amp;gt;NBC Bay Area interview with Frank Rodriguez, February 27, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Some consumers forced to purchase replacement units after multiple failed repairs&lt;br /&gt;
&lt;br /&gt;
==Arbitration Controversy==&lt;br /&gt;
In 2024, LG attempted to prevent a class action lawsuit by citing arbitration notices that appeared in three locations:&lt;br /&gt;
&lt;br /&gt;
#On the product box&lt;br /&gt;
#Inside the refrigerator&lt;br /&gt;
#In the owner&#039;s manual&lt;br /&gt;
&lt;br /&gt;
===Legal Issues with Notice===&lt;br /&gt;
Several issues make LG&#039;s arbitration notice strategy legally questionable:&lt;br /&gt;
&lt;br /&gt;
*Delivery people routinely remove refrigerators from boxes before bringing them into homes so that they can fit through the door, preventing customers from seeing box notices&amp;lt;ref&amp;gt;NBC Bay Area investigation found that &amp;quot;nobody they talked to saw the box. The delivery guys typically took the box off before even bringing it inside.&amp;quot;&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Internal notices and manual contents are only accessible &#039;&#039;&#039;&#039;&#039;after&#039;&#039;&#039;&#039;&#039; purchase completion&amp;lt;ref&amp;gt;Attorney Azar Mouzari statement to NBC Bay Area: &amp;quot;Consumers don&#039;t have access to an owner&#039;s manual until after they&#039;ve made the purchase.&amp;quot;&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Legal precedent from similar cases (such as Samsung&#039;s smartphone box arbitration notices) suggests post-purchase notices may not be enforceable&amp;lt;ref&amp;gt;Professor Anna Han, Santa Clara University School of Law, NBC Bay Area interview, February 27, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Professor Anna Han of Santa Clara University School of Law notes that proper notice requires both sides to &amp;quot;knowingly agree not to sue,&amp;quot; questioning whether notices unseen until after purchase can constitute valid agreement.&lt;br /&gt;
&lt;br /&gt;
==Consumer Response==&lt;br /&gt;
The issue gained widespread attention in early 2024 when attorney Azar Mouzari reported receiving &amp;quot;thousands of calls within a span of two weeks&amp;quot; from affected consumers after media coverage of the situation.&amp;lt;ref&amp;gt;Attorney Azar Mouzari to NBC Bay Area: &amp;quot;We received thousands of calls within a span of two weeks ... thousands&amp;quot;&amp;lt;/ref&amp;gt; Consumer complaints centered on several key issues:&lt;br /&gt;
&lt;br /&gt;
*Systematic failure of compressors&lt;br /&gt;
*High repair cost despite warranty coverage&lt;br /&gt;
*Difficult to obtain warranty service&lt;br /&gt;
*Unable to receive refunds or replacements for units that keep failing&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Organizations]]&lt;br /&gt;
[[Category:Products]]&lt;br /&gt;
[[Category:Anti-Consumer Practices]]&lt;br /&gt;
[[Category:Lawsuits]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Talk:LG_refrigerator_warranty_scandal&amp;diff=6013</id>
		<title>Talk:LG refrigerator warranty scandal</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Talk:LG_refrigerator_warranty_scandal&amp;diff=6013"/>
		<updated>2025-01-27T19:32:14Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: /* Sources / Refs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Sources / Refs ==&lt;br /&gt;
&lt;br /&gt;
List of the sources:&lt;br /&gt;
&lt;br /&gt;
* https://www.nbcbayarea.com/investigations/consumer/lg-refrigerators-failures-update/3465620/&lt;br /&gt;
* https://www.reddit.com/r/technology/comments/1b3d8yr/comment/ksrtouv/?utm_source=share&amp;amp;utm_medium=web3x&amp;amp;utm_name=web3xcss&amp;amp;utm_term=1&amp;amp;utm_content=share_button&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
[[User:Tpat90|Tpat90]] ([[User talk:Tpat90|talk]]) 19:29, 27 January 2025 (UTC)&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Talk:LG_refrigerator_warranty_scandal&amp;diff=6011</id>
		<title>Talk:LG refrigerator warranty scandal</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Talk:LG_refrigerator_warranty_scandal&amp;diff=6011"/>
		<updated>2025-01-27T19:29:01Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: /* Sources / Refs */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Sources / Refs ==&lt;br /&gt;
&lt;br /&gt;
List of the sources:&lt;br /&gt;
&lt;br /&gt;
* https://www.nbcbayarea.com/investigations/consumer/lg-refrigerators-failures-update/3465620/&lt;br /&gt;
&lt;br /&gt;
[[User:Tpat90|Tpat90]] ([[User talk:Tpat90|talk]]) 19:29, 27 January 2025 (UTC)&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Seattle_Avionics&amp;diff=5417</id>
		<title>Seattle Avionics</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Seattle_Avionics&amp;diff=5417"/>
		<updated>2025-01-25T16:43:07Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[https://www.seattleavionics.com/ &#039;&#039;&#039;Seattle Avionics&#039;&#039;&#039;] is a company that specializes in providing software for general aviation aircraft. FlyQ EFB was an [https://en.wikipedia.org/wiki/Electronic_flight_bag electronic flight bag] application available for iPad and iPhone which was primarily geared towards non-commercial (Part 91, general aviation) aircraft use. General Aviation pilots mostly favored other competing electronic flight bags, all of which required yearly subscriptions. &lt;br /&gt;
&lt;br /&gt;
==FlyQ EFB change to terms of service==&lt;br /&gt;
Seattle Avionics offered lifetime subscriptions annually during Black Friday for many of its subscription-based products, including FlyQ EFB. Eventually, Seattle Avionics would stop offering deals for lifetime subscriptions. Around September 2020, Seattle Avionics was acquired by AFV Partners.&amp;lt;ref&amp;gt;https://www.aopa.org/news-and-media/all-news/2020/september/24/seattle-avionics-acquired-by-technology-investor&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On July 19, 2024, Seattle Avionics sent an email to FlyQ EFB lifetime subscribers. This email began with announcing bug fixes, new features, and even a new version. Below this section was a section detailing a &amp;quot;change&amp;quot; to the lifetime program:&amp;lt;blockquote&amp;gt;In order to continue investing at this pace, starting today, we’re making the following changes to our Lifetime program:&lt;br /&gt;
&lt;br /&gt;
1. All Lifetime customers can use the new FlyQ+ EFB 7.0 and later releases for 30 days.&lt;br /&gt;
&lt;br /&gt;
2. During that period, Lifetime customers can upgrade to an annual subscription with a one-time 25% discount to continue to enjoy FlyQ+ EFB 7.0 and all other future releases.&lt;br /&gt;
&lt;br /&gt;
3. In 30 days, Lifetime customers who do not move to a new annual subscription can download a forthcoming new FlyQ EFB Legacy 6.9.1 and use it for a year, after which it will be sunset. As the version number implies, FlyQ EFB Legacy is the same as FlyQ EFB 6.9.1 released in May 2024 and does not include the features or fixes in FlyQ+ EFB 7.0.&lt;br /&gt;
&lt;br /&gt;
Once again, thank you so much for your support over the years. We’re excited to aggressively move FlyQ+ into the future with both defect fixes and industry-leading new features while retaining FlyQ’s famous ease of use! We look forward to you joining us on this exciting journey.&amp;lt;ref group=&amp;quot;Full Email Communications&amp;quot;&amp;gt;[[:File:FlyQ 1 19Jul2024.PNG]]&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;Pilots voiced dissatisfaction toward these policy changes on various general aviation forums including on Reddit,&amp;lt;ref&amp;gt;https://www.reddit.com/r/flying/comments/1e7e6bu/flyq_efb_revokes_lifetime_subscription/?ref=share&amp;amp;ref_source=link&amp;lt;/ref&amp;gt; Pilots of America,&amp;lt;ref&amp;gt;https://www.pilotsofamerica.com/community/threads/seattle-avionics.148039/&amp;lt;/ref&amp;gt; and Mooney Space.&amp;lt;ref&amp;gt;https://mooneyspace.com/topic/49042-i-guess-i-have-13-months-to-live-just-kidding/&amp;lt;/ref&amp;gt; AVWeb further wrote an article outlining this email.&amp;lt;ref&amp;gt;https://www.avweb.com/aviation-news/seattle-avionics-ends-lifetime-subscription-memberships-for-flyq-efb/&amp;lt;/ref&amp;gt; The timing was directly before [https://www.eaa.org/airventure EAA Airventure] 2024, the world&#039;s largest event for general aviation where Seattle Avionics had their own booth. Shortly after, on July 31, Seattle Avionics sent a second email updating lifetime subscribers.&amp;lt;blockquote&amp;gt;We announced and released our new app FlyQ+ EFB 7.0 on Friday July 19, 2024. We also announced that we&#039;ll be releasing the FlyQ Legacy app for FlyQ Lifetime subscribers soon. Since that time, we received numerous emails from FlyQ Lifetime users, spoke to many people at EAA AirVenture Oshkosh, and reviewed posts on social media. Based on the feedback we received, we are making the following updates:&lt;br /&gt;
&lt;br /&gt;
*Lifetime users can continue to use FlyQ without any additional charge by downloading the FlyQ Legacy app, which we are releasing in the coming weeks. FlyQ Legacy will be version 6.9.2 to reflect that it’s based on FlyQ EFB 6.9.1 but also includes stability fixes added in FlyQ+ EFB 7.0.0 as well as fixes being added to forthcoming FlyQ+ EFB 7.0.2.&lt;br /&gt;
&lt;br /&gt;
*FlyQ Legacy will load your existing flight plans and aircraft / pilot profiles as well as continue to receive monthly ChartData updates.&lt;br /&gt;
&lt;br /&gt;
*We have no plans to update FlyQ Legacy after this release.&lt;br /&gt;
&lt;br /&gt;
*You can trial and use the new FlyQ+ EFB 7.0 app and later versions for 90 days without charge.&lt;br /&gt;
&lt;br /&gt;
*FlyQ Legacy and FlyQ+ EFB can both be loaded on the same iPad or iPhone so you can compare both apps and determine if FlyQ+ has the value you seek. If you decide to subscribe to FlyQ+, we are offering a 25% discount from current standard prices as acknowledgement of your Lifetime purchase. After your discount, a VFR subscription is $74.99 and an IFR+VFR subscription is $149.99. You’ll receive an email with purchase information shortly.&lt;br /&gt;
&lt;br /&gt;
*Seattle Avionics also sold Lifetime ChartData subscriptions for Aspen, Dynon, AFS, GRT, and Honeywell products. There are no changes to these subscriptions.&lt;br /&gt;
&lt;br /&gt;
Our goal is to increase the velocity of the development of FlyQ+ with more frequent releases that deliver high value and offer the best product to meet your flying requirements. Please continue to provide your feedback and help guide our road map. We will release more features over the next 90 days in FlyQ+ for you to evaluate and we look forward to your feedback.&amp;lt;ref group=&amp;quot;Full Email Communications&amp;quot;&amp;gt;[[:File:FlyQ 2 31Jul2024.PNG]]&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;While this did affirm that other Seattle Avionics products that also had lifetime subscriptions were not affected, the policy effectively did not change their revocation of the FlyQ EFB lifetime subscription. On October 2, Seattle Avionics sent a final update:&amp;lt;blockquote&amp;gt;In our effort to communicate critical changes to FlyQ, we’ve sent multiple emails describing the new FlyQ Lifetime subscription model. This change allows us to substantially accelerate investment in the product, both improving the app stability and adding multiple new features. The proof has been a half dozen releases already this calendar year.&lt;br /&gt;
&lt;br /&gt;
Of course, I&#039;d be remiss if I didn’t note how the policy change was handled, and we sincerely apologize for the angst, confusion, and mistrust this has caused. Clearly, we’re better at writing software than policy statements. To that point, we’ve come up with a revised plan that we believe better portrays our commitment to the FlyQ community and allows us to continue the increased investment in FlyQ.&lt;br /&gt;
&lt;br /&gt;
(+) All FlyQ customers, lifetime and annual subscribers alike, will be able to use FlyQ+. No one will be asked to download a new app.&lt;br /&gt;
&lt;br /&gt;
(+) All FlyQ customers, lifetime and annual subscribers alike, will continue to get new ChartData updates and subsequent releases of FlyQ+ as they are released.&lt;br /&gt;
&lt;br /&gt;
(+) The only difference will be that new features, beyond what was in FlyQ EFB 6.9.1, will only be enabled for annual subscribers. To be clear, this means that all users will continue to receive bug fixes and new releases as iOS updates are produced but only annual subscribers will benefit from the new features added in FlyQ+ 7.0 and later.&amp;lt;ref group=&amp;quot;Full Email Communications&amp;quot;&amp;gt;[[:File:FlyQ 3 02Oct2024.PNG]]&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;This update gave lifetime customers continued access to the app and miscellaneous fixes, as the company was still active and actively developing the app, but would exclude lifetime subscribers from any additional features now included in the equivalent subscriptions today.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&amp;lt;references group=&amp;quot;Full Email Communications&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Software companies]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Seattle_Avionics&amp;diff=5415</id>
		<title>Seattle Avionics</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Seattle_Avionics&amp;diff=5415"/>
		<updated>2025-01-25T16:40:53Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[https://www.seattleavionics.com/ &#039;&#039;&#039;Seattle Avionics&#039;&#039;&#039;] is a company that specializes in providing software for general aviation aircraft. FlyQ EFB was an [electronic flight bag](https://en.wikipedia.org/wiki/Electronic_flight_bag) application available for iPad and iPhone which was primarily geared towards non-commercial (Part 91, general aviation) aircraft use. General Aviation pilots mostly favored other competing electronic flight bags, all of which required yearly subscriptions. &lt;br /&gt;
&lt;br /&gt;
==FlyQ EFB change to terms of service==&lt;br /&gt;
Seattle Avionics offered lifetime subscriptions annually during Black Friday for many of its subscription-based products, including FlyQ EFB. Eventually, Seattle Avionics would stop offering deals for lifetime subscriptions. Around September 2020, Seattle Avionics was acquired by AFV Partners.&amp;lt;ref&amp;gt;https://www.aopa.org/news-and-media/all-news/2020/september/24/seattle-avionics-acquired-by-technology-investor&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On July 19, 2024, Seattle Avionics sent an email to FlyQ EFB lifetime subscribers. This email began with announcing bug fixes, new features, and even a new version. Below this section was a section detailing a &amp;quot;change&amp;quot; to the lifetime program:&amp;lt;blockquote&amp;gt;In order to continue investing at this pace, starting today, we’re making the following changes to our Lifetime program:&lt;br /&gt;
&lt;br /&gt;
1. All Lifetime customers can use the new FlyQ+ EFB 7.0 and later releases for 30 days.&lt;br /&gt;
&lt;br /&gt;
2. During that period, Lifetime customers can upgrade to an annual subscription with a one-time 25% discount to continue to enjoy FlyQ+ EFB 7.0 and all other future releases.&lt;br /&gt;
&lt;br /&gt;
3. In 30 days, Lifetime customers who do not move to a new annual subscription can download a forthcoming new FlyQ EFB Legacy 6.9.1 and use it for a year, after which it will be sunset. As the version number implies, FlyQ EFB Legacy is the same as FlyQ EFB 6.9.1 released in May 2024 and does not include the features or fixes in FlyQ+ EFB 7.0.&lt;br /&gt;
&lt;br /&gt;
Once again, thank you so much for your support over the years. We’re excited to aggressively move FlyQ+ into the future with both defect fixes and industry-leading new features while retaining FlyQ’s famous ease of use! We look forward to you joining us on this exciting journey.&amp;lt;ref group=&amp;quot;Full Email Communications&amp;quot;&amp;gt;[[:File:FlyQ 1 19Jul2024.PNG]]&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;Pilots voiced dissatisfaction toward these policy changes on various general aviation forums including on Reddit,&amp;lt;ref&amp;gt;https://www.reddit.com/r/flying/comments/1e7e6bu/flyq_efb_revokes_lifetime_subscription/?ref=share&amp;amp;ref_source=link&amp;lt;/ref&amp;gt; Pilots of America,&amp;lt;ref&amp;gt;https://www.pilotsofamerica.com/community/threads/seattle-avionics.148039/&amp;lt;/ref&amp;gt; and Mooney Space.&amp;lt;ref&amp;gt;https://mooneyspace.com/topic/49042-i-guess-i-have-13-months-to-live-just-kidding/&amp;lt;/ref&amp;gt; AVWeb further wrote an article outlining this email.&amp;lt;ref&amp;gt;https://www.avweb.com/aviation-news/seattle-avionics-ends-lifetime-subscription-memberships-for-flyq-efb/&amp;lt;/ref&amp;gt; The timing was directly before [https://www.eaa.org/airventure EAA Airventure] 2024, the world&#039;s largest event for general aviation where Seattle Avionics had their own booth. Shortly after, on July 31, Seattle Avionics sent a second email updating lifetime subscribers.&amp;lt;blockquote&amp;gt;We announced and released our new app FlyQ+ EFB 7.0 on Friday July 19, 2024. We also announced that we&#039;ll be releasing the FlyQ Legacy app for FlyQ Lifetime subscribers soon. Since that time, we received numerous emails from FlyQ Lifetime users, spoke to many people at EAA AirVenture Oshkosh, and reviewed posts on social media. Based on the feedback we received, we are making the following updates:&lt;br /&gt;
&lt;br /&gt;
*Lifetime users can continue to use FlyQ without any additional charge by downloading the FlyQ Legacy app, which we are releasing in the coming weeks. FlyQ Legacy will be version 6.9.2 to reflect that it’s based on FlyQ EFB 6.9.1 but also includes stability fixes added in FlyQ+ EFB 7.0.0 as well as fixes being added to forthcoming FlyQ+ EFB 7.0.2.&lt;br /&gt;
&lt;br /&gt;
*FlyQ Legacy will load your existing flight plans and aircraft / pilot profiles as well as continue to receive monthly ChartData updates.&lt;br /&gt;
&lt;br /&gt;
*We have no plans to update FlyQ Legacy after this release.&lt;br /&gt;
&lt;br /&gt;
*You can trial and use the new FlyQ+ EFB 7.0 app and later versions for 90 days without charge.&lt;br /&gt;
&lt;br /&gt;
*FlyQ Legacy and FlyQ+ EFB can both be loaded on the same iPad or iPhone so you can compare both apps and determine if FlyQ+ has the value you seek. If you decide to subscribe to FlyQ+, we are offering a 25% discount from current standard prices as acknowledgement of your Lifetime purchase. After your discount, a VFR subscription is $74.99 and an IFR+VFR subscription is $149.99. You’ll receive an email with purchase information shortly.&lt;br /&gt;
&lt;br /&gt;
*Seattle Avionics also sold Lifetime ChartData subscriptions for Aspen, Dynon, AFS, GRT, and Honeywell products. There are no changes to these subscriptions.&lt;br /&gt;
&lt;br /&gt;
Our goal is to increase the velocity of the development of FlyQ+ with more frequent releases that deliver high value and offer the best product to meet your flying requirements. Please continue to provide your feedback and help guide our road map. We will release more features over the next 90 days in FlyQ+ for you to evaluate and we look forward to your feedback.&amp;lt;ref group=&amp;quot;Full Email Communications&amp;quot;&amp;gt;[[:File:FlyQ 2 31Jul2024.PNG]]&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;While this did affirm that other Seattle Avionics products that also had lifetime subscriptions were not affected, the policy effectively did not change their revocation of the FlyQ EFB lifetime subscription. On October 2, Seattle Avionics sent a final update:&amp;lt;blockquote&amp;gt;In our effort to communicate critical changes to FlyQ, we’ve sent multiple emails describing the new FlyQ Lifetime subscription model. This change allows us to substantially accelerate investment in the product, both improving the app stability and adding multiple new features. The proof has been a half dozen releases already this calendar year.&lt;br /&gt;
&lt;br /&gt;
Of course, I&#039;d be remiss if I didn’t note how the policy change was handled, and we sincerely apologize for the angst, confusion, and mistrust this has caused. Clearly, we’re better at writing software than policy statements. To that point, we’ve come up with a revised plan that we believe better portrays our commitment to the FlyQ community and allows us to continue the increased investment in FlyQ.&lt;br /&gt;
&lt;br /&gt;
(+) All FlyQ customers, lifetime and annual subscribers alike, will be able to use FlyQ+. No one will be asked to download a new app.&lt;br /&gt;
&lt;br /&gt;
(+) All FlyQ customers, lifetime and annual subscribers alike, will continue to get new ChartData updates and subsequent releases of FlyQ+ as they are released.&lt;br /&gt;
&lt;br /&gt;
(+) The only difference will be that new features, beyond what was in FlyQ EFB 6.9.1, will only be enabled for annual subscribers. To be clear, this means that all users will continue to receive bug fixes and new releases as iOS updates are produced but only annual subscribers will benefit from the new features added in FlyQ+ 7.0 and later.&amp;lt;ref group=&amp;quot;Full Email Communications&amp;quot;&amp;gt;[[:File:FlyQ 3 02Oct2024.PNG]]&amp;lt;/ref&amp;gt;&amp;lt;/blockquote&amp;gt;This update gave lifetime customers continued access to the app and miscellaneous fixes, as the company was still active and actively developing the app, but would exclude lifetime subscribers from any additional features now included in the equivalent subscriptions today.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&amp;lt;references group=&amp;quot;Full Email Communications&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Software companies]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=RepairShopr_data_privacy&amp;diff=5412</id>
		<title>RepairShopr data privacy</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=RepairShopr_data_privacy&amp;diff=5412"/>
		<updated>2025-01-25T16:33:38Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=RepairShopr changing terms of service=&lt;br /&gt;
&lt;br /&gt;
[[RepairShopr]], a [[Software as a service|software-as-a-service]] (SaaS) platform used primarily for [[customer-relationship management]] (CRM) and ticketing in repair shops, has as of December 2024 been the subject of scrutiny, because of changes in its [[terms of service]]. While the platform was previously praised for its utility and robust features, concerns have arisen about data-usage policies and subscription practices after its acquisition by [[Synchro]], leading to dissatisfaction among long-term users.&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;https://www.youtube.com/watch?v=bu_rjYHZj9I&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
Initially developed by Troy Anderson, RepairShopr gained popularity as an affordable and effective CRM solution for repair businesses. Its features included [[QuickBooks]] integration, shipping automation, and caller-ID syncing with ticket statuses. Users valued its simplicity and responsiveness to feedback. Following its sale to Synchro, however, the platform has faced criticism for declining functionality, increased pricing, and controversial updates to its terms of service.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;https://www.youtube.com/watch?v=ASJE0501nOA&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Key issues==&lt;br /&gt;
&lt;br /&gt;
===AI tools and data usage===&lt;br /&gt;
The most contentious issue involves RepairShopr’s updated terms of service, which grant the platform the right to use &amp;quot;user content&amp;quot; and &amp;quot;usage information&amp;quot; to train AI tools. While Synchro claims no current AI features are operational, the terms allow for future implementation. Critics argue this represents a violation of privacy, as user content includes communications with customers, which are considered sensitive business data.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;https://www.repairshopr.com/repairshopr-user-access-and-license-agreement. [https://web.archive.org/web/20250106203556/https://www.repairshopr.com/repairshopr-user-access-and-license-agreement Archived] from the original on January 6, 2025. Retrieved January 17, 2025.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Opt-out policies===&lt;br /&gt;
Users must opt out of data collection for AI training by directly contacting the company. Previously collected data, however, remain usable under the terms, creating further concerns about consent and [[retroactive policy enforcement]]. This policy is outlined under the &#039;&#039;&#039;&amp;quot;Intellectual Property; Reservation of Rights&amp;quot;&#039;&#039;&#039; section of the RepairShopr User Access and License Agreement, specifically the sixth point:&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;blockquote&amp;gt;&amp;quot;If you wish to opt out of any future collection and aggregation by Servably of your User Content or Usage Information in an anonymous form in order to train Servably’s AI Tools, please contact us as set forth below. For clarity, such opt-out will apply only on a go-forward basis and will not obligate Servably to cease using any previously anonymized and aggregated User Content or other Usage Information as otherwise permitted in this Agreement.&amp;quot;&amp;lt;/blockquote&amp;gt;Furthermore, the opt-out process must be initiated by the business owner, which limits the ability of individual employees or customers of the business to safeguard data. Per Louis Rossmann’s account, the changes to the terms were not disclosed until after they had already taken effect, leaving a window of time where data could have been collected without the user’s knowledge or consent.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Increased costs and decline in functionality===&lt;br /&gt;
Since the acquisition, RepairShopr’s subscription fees have increased by 40%, with users reporting degraded service quality. Core functionalities, such as email communication with customers, have experienced extended downtimes, undermining its role as a CRM tool.&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Transparency and communication===&lt;br /&gt;
Users were notified of changes to the terms of service by email late in December 2024, with the new policies already having been in effect for weeks. Many users criticized the lack of proactive communication, claiming the updates were poorly communicated and buried under non-critical updates.&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Broader implications==&lt;br /&gt;
This case reflects broader trends in SaaS:&lt;br /&gt;
*&#039;&#039;&#039;Erosion of ownership rights:&#039;&#039;&#039; Platforms increasingly transition to subscription-based models, asserting greater control over user data and functionality.&lt;br /&gt;
*&#039;&#039;&#039;AI training and data ethics:&#039;&#039;&#039; Policies allowing AI training on user-generated data raise ethical and legal concerns about privacy and informed consent.&lt;br /&gt;
*&#039;&#039;&#039;Consumer trust:&#039;&#039;&#039; Poor communication and retroactive application of terms erode trust in service providers.&lt;br /&gt;
*&#039;&#039;&#039;Transparency in terms of service:&#039;&#039;&#039; SaaS providers should clearly communicate terms changes, ensuring users explicitly consent to updates.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Retroactive policy enforcement]]&lt;br /&gt;
*[[Consumer rights in SaaS platforms]]&lt;br /&gt;
*[[AI training and data-privacy ethics]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Term Spiking]]&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:RepairShopr]]&lt;br /&gt;
[[Category:Servably]]&lt;br /&gt;
[[Category:Consumer rights]]&lt;br /&gt;
[[Category:Subscription-based services]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Adobe_sued_by_FTC_over_hidden_fees_in_subscription_plans&amp;diff=4019</id>
		<title>Adobe sued by FTC over hidden fees in subscription plans</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Adobe_sued_by_FTC_over_hidden_fees_in_subscription_plans&amp;diff=4019"/>
		<updated>2025-01-21T19:14:53Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Reverted edit by 2001:67C:6EC:203:192:42:116:191 (talk) to last revision by Keith&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The U.S. Federal Trade Commission (FTC) has filed a lawsuit against Adobe Inc. and two of its executives, alleging deceptive subscription practices that violate federal consumer protection laws. The case, filed in the U.S. District Court for the Northern District of California, accuses Adobe of concealing critical terms of its subscription plans and creating obstacles to cancellation.&lt;br /&gt;
&lt;br /&gt;
== Key Allegations ==&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Hidden Early Termination Fees (ETFs):&#039;&#039;&#039;&lt;br /&gt;
#* Adobe allegedly pre-selected its &amp;quot;Annual, Paid Monthly&amp;quot; (APM) subscription plan as the default option for users signing up for services like Creative Cloud.&lt;br /&gt;
#* While marketed as a monthly payment plan, the APM plan locks users into a year-long contract. If canceled within the first year, users are charged an ETF amounting to 50% of the remaining annual payments. [https://natlawreview.com/article/ftc-sues-adobe-and-execs-illegal-hidden-fees]&lt;br /&gt;
#* The FTC claims the ETF was buried in fine print or hidden behind hyperlinks that most consumers would not notice during the sign-up process. [https://www.ftc.gov/news-events/news/press-releases/2024/06/ftc-takes-action-against-adobe-executives-hiding-fees-preventing-consumers-easily-cancelling]&lt;br /&gt;
# &#039;&#039;&#039;Complex Cancellation Process:&#039;&#039;&#039;&lt;br /&gt;
#* Adobe&#039;s cancellation process reportedly requires navigating through multiple pages, re-entering passwords, providing feedback, and reviewing warnings about fees.&lt;br /&gt;
#* Consumers attempting to cancel online or via customer service often faced dropped calls, multiple transfers, and continued charges even after cancellation attempts. [https://www.ftc.gov/business-guidance/blog/2024/06/ftc-says-adobe-hid-key-terms-annual-paid-monthly-subscription-plan-set-roadblocks-deter-customer]&lt;br /&gt;
# &#039;&#039;&#039;Violation of Consumer Protection Laws:&#039;&#039;&#039;&lt;br /&gt;
#* The FTC alleges that Adobe&#039;s practices violate the Restore Online Shoppers&#039; Confidence Act (ROSCA) and the FTC Act by:&lt;br /&gt;
#** Failing to clearly disclose material terms upfront.&lt;br /&gt;
#** Charging consumers without obtaining express informed consent.&lt;br /&gt;
#** Not providing simple mechanisms for stopping recurring charges. [https://www.gtlaw-financialservicesobserver.com/2024/07/ftc-targets-adobe-for-hidden-fees-and-deceptive-subscription-practices/]&lt;br /&gt;
&lt;br /&gt;
== FTC&#039;s Legal Action ==&lt;br /&gt;
The FTC is seeking:&lt;br /&gt;
&lt;br /&gt;
* A permanent injunction to stop Adobe from continuing these practices.&lt;br /&gt;
* Civil penalties and monetary relief for affected consumers. [https://www.mondaq.com/unitedstates/advertising-marketing-branding/1496334/ftc-takes-action-against-adobe-for-unfair-subscription-practices]&lt;br /&gt;
&lt;br /&gt;
The lawsuit also names two Adobe executives—Maninder Sawhney and David Wadhwani—highlighting their roles in implementing these subscription practices. This reflects a growing trend in holding corporate officers personally accountable for deceptive business practices.&lt;br /&gt;
&lt;br /&gt;
== Adobe&#039;s Response ==&lt;br /&gt;
Adobe has denied the allegations, stating that its subscription services are transparent and designed to provide flexibility to users. The company plans to contest the lawsuit in court. [https://www.archpaper.com/2024/07/the-ftc-is-suing-software-giant-adobe-over-hidden-fees-and-an-overly-complicated-cancellation-process/]&lt;br /&gt;
&lt;br /&gt;
== Current Status ==&lt;br /&gt;
As of January 2025, the case remains pending in federal court. The FTC continues to push for stronger enforcement against hidden fees and deceptive subscription practices across industries.&lt;br /&gt;
&lt;br /&gt;
== TL;DR ==&lt;br /&gt;
The FTC has sued Adobe for allegedly deceiving consumers with hidden early termination fees in its &amp;quot;Annual, Paid Monthly&amp;quot; subscription plans and making cancellations unnecessarily difficult. The lawsuit accuses Adobe of violating federal consumer protection laws and seeks penalties and injunctive relief. Adobe denies wrongdoing, and the case is ongoing as of January 2025.&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Lenovo_X1_Carbon&amp;diff=3924</id>
		<title>Lenovo X1 Carbon</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Lenovo_X1_Carbon&amp;diff=3924"/>
		<updated>2025-01-21T13:25:02Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
&lt;br /&gt;
This article outlines the various anti-consumer measures used in the Lenovo X1 Carbon series of laptops. Some concepts may overlap with [[Lenovo]]&#039;s general practices, a Chinese-American multinational technology company.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Vendor Lockout (BIOS Whitelist) ===&lt;br /&gt;
Most models of the Lenovo X1 Carbon will fail to post if the user changes their WWAN broadband card to a WWAN card that is not on the Lenovo Vendor Whitelist&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;[https://wiki.archlinux.org/title/ThinkPad_mobile_Internet &amp;quot;ThinkPad mobile Internet&amp;quot;] - wiki.archlinux.org&amp;lt;/ref&amp;gt;. If a user intends to use a WWAN card manufactured by another company, which are typically cheaper than the Lenovo factory-installed WWAN cards, the computer will not boot until the user removes the card. Evasion of these whitelists has been outlined in the ArchLinux wiki&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;, but success is very limited. &lt;br /&gt;
&lt;br /&gt;
The intent behind this vendor-lockout is ambiguous, and not well-documented officially by Lenovo. &lt;br /&gt;
&lt;br /&gt;
==== Resulting cost for the consumer ====&lt;br /&gt;
&lt;br /&gt;
Lenovo currently charges $298 USD to install a Quectel RM520N-GL 5G Sub6 from the factory&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;. &lt;br /&gt;
[[File:Lenovo store screenshot.png|thumb|right| Pricing options for WWAN card (Lenovo X1 Carbon gen2) &amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt; [[:File:Lenovo store screenshot.png|Screenshot or pricing options for WWAN card of Lenovo Laptop]]&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
Some used options of similar modems can, at the time of writing, be purchased for $150 USD&amp;lt;ref&amp;gt;[https://www.ebay.com/itm/296886818084 &amp;quot;Quectel RM520N-GL&amp;quot;] - ebay.com - 17 Jan 2025 - Archived Page: https://archive.is/IkmZV&amp;lt;/ref&amp;gt;. 4G modems can be purchased for even less&amp;lt;ref&amp;gt;[https://www.ebay.com/itm/196914042141 &amp;quot;NEW Dell V8KN6 Sierra Wireless AirPrime EM7455 DW5811e LTE 4G WWAN Card&amp;quot;] - ebay.com - 17 Jan 2025 - Archived Page: https://archive.is/uSubr&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Product lines]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Volkswagen_car-location_data-exposure_incident&amp;diff=3923</id>
		<title>Volkswagen car-location data-exposure incident</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Volkswagen_car-location_data-exposure_incident&amp;diff=3923"/>
		<updated>2025-01-21T13:23:22Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Under_Development&lt;br /&gt;
|date=January 2025&lt;br /&gt;
|stage=early&lt;br /&gt;
|priority=high&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
In 2024, Volkswagen experienced a data security incident involving customer vehicle information stored on Amazon Web Services (AWS). The incident occurred when Volkswagen&#039;s implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances due to a misconfiguration&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;[https://cybersecuritynews.com/volkswagen-data-breach/]&amp;quot;Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked&amp;quot; written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/tVDzM Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.&amp;lt;/ref&amp;gt;.&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
This incident occurred within a broader context of automotive data security concerns. Modern vehicles increasingly collect and transmit various types of data, including location information, driving patterns, and user identification&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;[https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/05/cars-consumer-data-unlawful-collection-use]&amp;quot;Cars &amp;amp; Consumer Data: On Unlawful Collection &amp;amp; Use&amp;quot; written in collaboration by the Office of Technology and the Division of Privacy and Identity Protection in the Bureau of Consumer Protection. [https://web.archive.org/web/20240514181955/https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/05/cars-consumer-data-unlawful-collection-use Archived] from the original on May 14, 2024. Retrieved January 15, 2025.&amp;lt;/ref&amp;gt;. The automotive industry has previously faced scrutiny regarding data collection practices, with documented instances of manufacturers collecting and sharing vehicle data with third parties.&lt;br /&gt;
&lt;br /&gt;
== The Incident ==&lt;br /&gt;
[[File:Volkswagen.png|alt=Pie Chart showing the total cars affected including the severity of each(whether its location was exposed down to a radius of 10cm or 10km) and breakdown by brand|thumb|Pie Chart showing the total cars affected and breakdown by brand]]&lt;br /&gt;
The core issue stemmed from a misconfiguration in Volkswagen&#039;s AWS storage implementation, which left customer data publicly accessible without proper authentication or access restrictions&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;. This exposed sensitive information about vehicle locations, EV battery statistics and sensitive customer information.  The incident not only breached customer trust, but Volkswagen&#039;s own Terms of Service. &lt;br /&gt;
&lt;br /&gt;
== Industry Context ==&lt;br /&gt;
&lt;br /&gt;
The incident highlighted ongoing discussions about automotive data security and privacy. Similar concerns were raised during the [[2020 Massachusetts Right to Repair ballot initiative]], where major automotive manufacturers including General Motors, Ford, Nissan, Toyota, and Honda invested approximately $25 million in campaign advertising discussing data security implications.&lt;br /&gt;
&lt;br /&gt;
== Regulatory Response ==&lt;br /&gt;
&lt;br /&gt;
The National Highway Traffic Safety Administration (NHTSA) has previously expressed concerns about automotive data security. Following the 2020 Massachusetts Right to Repair initiative, NHTSA official Carrie Gules issued a letter addressing potential security vulnerabilities in vehicle data systems{{Citation needed|date=January 2024|reason=Letter reference needed}}.&amp;lt;!-- I couldn&#039;t find any specific letter that was referenced here, although there have been some sources saying that the NHTSA has taken part in Massachusetts Right to Repair regulations. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Broader Implications ==&lt;br /&gt;
&lt;br /&gt;
This incident demonstrates the broader challenges facing the automotive industry regarding data security and privacy. It has been documented that automotive manufacturers regularly collect various types of vehicle data&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;, including:&lt;br /&gt;
* Location information&lt;br /&gt;
* Driving patterns&lt;br /&gt;
* Vehicle operation metrics&lt;br /&gt;
* User behavior data&lt;br /&gt;
&lt;br /&gt;
Some manufacturers have established partnerships with data aggregators and insurance companies for data-sharing purposes. For example, General Motors has been documented to share driving data with LexisNexis and insurance companies, including information about:&lt;br /&gt;
&lt;br /&gt;
* Vehicle location data&lt;br /&gt;
* Turning radius information&lt;br /&gt;
* Stop times&lt;br /&gt;
* Drive times&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [[Data Privacy]]&lt;br /&gt;
* [[Right to Repair movement]]&lt;br /&gt;
* [[CARIAD]]&lt;br /&gt;
* [[Volkswagen Group]]&lt;br /&gt;
* [[2020 Massachusetts Right to Repair ballot initiative]]&lt;br /&gt;
* [[General Motors Data Theft]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&#039;&#039;Note: This article represents an ongoing situation and may be updated as more information becomes available.&#039;&#039;&lt;br /&gt;
&amp;lt;!-- commenting out to granular categories for the moment --&amp;gt;&lt;br /&gt;
[[Category:Data breaches]]&lt;br /&gt;
&amp;lt;!-- [[Category:Volkswagen Group]] --&amp;gt;&lt;br /&gt;
[[Category:AWS security incidents]]&lt;br /&gt;
&amp;lt;!-- [[Category:2024 in automotive industry]] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
* [https://www.spiegel.de/netzwelt/web/volkswagen-konzern-datenleck-wir-wissen-wo-dein-auto-steht-a-e12d33d0-97bc-493c-96d1-aa5892861027 For the link to the news source which was tipped off by a German hacktivist group]. [https://web.archive.org/web/20241227094207/https://www.spiegel.de/netzwelt/web/volkswagen-konzern-datenleck-wir-wissen-wo-dein-auto-steht-a-e12d33d0-97bc-493c-96d1-aa5892861027 Archived] from the original on December 27, 2024. Retrieved January 15, 2025.&lt;br /&gt;
* [https://www.youtube.com/watch?v=Agcp37iiWLc&amp;amp;t=188s Youtube video with mentioned credits for more information].&lt;br /&gt;
[[Category:Automotive privacy]]&lt;br /&gt;
[[Category:Right to repair]]&lt;br /&gt;
[[Category:CARIAD]]&lt;br /&gt;
[[Category:Incidents]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Volkswagen_car-location_data-exposure_incident&amp;diff=3922</id>
		<title>Volkswagen car-location data-exposure incident</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Volkswagen_car-location_data-exposure_incident&amp;diff=3922"/>
		<updated>2025-01-21T13:22:40Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Under_Development&lt;br /&gt;
|date=January 2025&lt;br /&gt;
|stage=early&lt;br /&gt;
|priority=high&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
In 2024, Volkswagen experienced a data security incident involving customer vehicle information stored on Amazon Web Services (AWS). The incident occurred when Volkswagen&#039;s implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances due to a misconfiguration&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;[https://cybersecuritynews.com/volkswagen-data-breach/]&amp;quot;Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked&amp;quot; written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/tVDzM Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.&amp;lt;/ref&amp;gt;.&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
This incident occurred within a broader context of automotive data security concerns. Modern vehicles increasingly collect and transmit various types of data, including location information, driving patterns, and user identification&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;[https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/05/cars-consumer-data-unlawful-collection-use]&amp;quot;Cars &amp;amp; Consumer Data: On Unlawful Collection &amp;amp; Use&amp;quot; written in collaboration by the Office of Technology and the Division of Privacy and Identity Protection in the Bureau of Consumer Protection. [https://web.archive.org/web/20240514181955/https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/05/cars-consumer-data-unlawful-collection-use Archived] from the original on May 14, 2024. Retrieved January 15, 2025.&amp;lt;/ref&amp;gt;. The automotive industry has previously faced scrutiny regarding data collection practices, with documented instances of manufacturers collecting and sharing vehicle data with third parties.&lt;br /&gt;
&lt;br /&gt;
== The Incident ==&lt;br /&gt;
[[File:Volkswagen.png|alt=Pie Chart showing the total cars affected including the severity of each(whether its location was exposed down to a radius of 10cm or 10km) and breakdown by brand|thumb|Pie Chart showing the total cars affected and breakdown by brand]]&lt;br /&gt;
The core issue stemmed from a misconfiguration in Volkswagen&#039;s AWS storage implementation, which left customer data publicly accessible without proper authentication or access restrictions&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;. This exposed sensitive information about vehicle locations, EV battery statistics and sensitive customer information.  The incident not only breached customer trust, but Volkswagen&#039;s own Terms of Service. &lt;br /&gt;
&lt;br /&gt;
== Industry Context ==&lt;br /&gt;
&lt;br /&gt;
The incident highlighted ongoing discussions about automotive data security and privacy. Similar concerns were raised during the [[2020 Massachusetts Right to Repair ballot initiative]], where major automotive manufacturers including General Motors, Ford, Nissan, Toyota, and Honda invested approximately $25 million in campaign advertising discussing data security implications.&lt;br /&gt;
&lt;br /&gt;
== Regulatory Response ==&lt;br /&gt;
&lt;br /&gt;
The National Highway Traffic Safety Administration (NHTSA) has previously expressed concerns about automotive data security. Following the 2020 Massachusetts Right to Repair initiative, NHTSA official Carrie Gules issued a letter addressing potential security vulnerabilities in vehicle data systems{{Citation needed|date=January 2024|reason=Letter reference needed}}.&amp;lt;!-- I couldn&#039;t find any specific letter that was referenced here, although there have been some sources saying that the NHTSA has taken part in Massachusetts Right to Repair regulations. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Broader Implications ==&lt;br /&gt;
&lt;br /&gt;
This incident demonstrates the broader challenges facing the automotive industry regarding data security and privacy. It has been documented that automotive manufacturers regularly collect various types of vehicle data&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt;, including:&lt;br /&gt;
* Location information&lt;br /&gt;
* Driving patterns&lt;br /&gt;
* Vehicle operation metrics&lt;br /&gt;
* User behavior data&lt;br /&gt;
&lt;br /&gt;
Some manufacturers have established partnerships with data aggregators and insurance companies for data-sharing purposes. For example, General Motors has been documented to share driving data with LexisNexis and insurance companies, including information about:&lt;br /&gt;
&lt;br /&gt;
* Vehicle location data&lt;br /&gt;
* Turning radius information&lt;br /&gt;
* Stop times&lt;br /&gt;
* Drive times&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [[Data Privacy]]&lt;br /&gt;
* [[Right to Repair movement]]&lt;br /&gt;
* [[CARIAD]]&lt;br /&gt;
* [[Volkswagen Group]]&lt;br /&gt;
* [[2020 Massachusetts Right to Repair ballot initiative]]&lt;br /&gt;
* [[General Motors Data Theft]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&#039;&#039;Note: This article represents an ongoing situation and may be updated as more information becomes available.&#039;&#039;&lt;br /&gt;
&amp;lt;!-- commenting out to granular categories for the moment --&amp;gt;&lt;br /&gt;
[[Category:Data breaches]]&lt;br /&gt;
&amp;lt;!-- [[Category:Volkswagen Group]] --&amp;gt;&lt;br /&gt;
[[Category:AWS security incidents]]&lt;br /&gt;
&amp;lt;!-- [[Category:2024 in automotive industry]] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
3. [https://www.spiegel.de/netzwelt/web/volkswagen-konzern-datenleck-wir-wissen-wo-dein-auto-steht-a-e12d33d0-97bc-493c-96d1-aa5892861027 For the link to the news source which was tipped off by a German hacktivist group]. [https://web.archive.org/web/20241227094207/https://www.spiegel.de/netzwelt/web/volkswagen-konzern-datenleck-wir-wissen-wo-dein-auto-steht-a-e12d33d0-97bc-493c-96d1-aa5892861027 Archived] from the original on December 27, 2024. Retrieved January 15, 2025.&lt;br /&gt;
&lt;br /&gt;
4. [https://www.youtube.com/watch?v=Agcp37iiWLc&amp;amp;t=188s Youtube video with mentioned credits for more information].&lt;br /&gt;
[[Category:Automotive privacy]]&lt;br /&gt;
[[Category:Right to repair]]&lt;br /&gt;
[[Category:CARIAD]]&lt;br /&gt;
[[Category:Incidents]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Tom_Evans_Audio_copyright_strike&amp;diff=3921</id>
		<title>Tom Evans Audio copyright strike</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Tom_Evans_Audio_copyright_strike&amp;diff=3921"/>
		<updated>2025-01-21T13:20:22Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Upload ===&lt;br /&gt;
&lt;br /&gt;
In November 2024, YouTube creator [https://www.youtube.com/@MendItMark Mend It Mark] uploaded a video in which he repaired a [https://audiodesign.co.uk/styled-23/styled-27/index.html MasterGroove SR Mk3] pre-amp made by Tom Evans Audio. In the video, he took the pre-amp apart and to help diagnose the issue, he reverse engineered the device and created some schematic diagrams.&amp;lt;ref&amp;gt;https://archive.org/details/the-gbp-25-000-pre-amp-that-went-wrong-tom-evans-mastergroove-sr-mk-iii-rjbp-fsfzi-i&amp;lt;/ref&amp;gt; He also made his viewers aware of the fact that the price of this pre-amp is £25,000 (about 30,000 USD) and that many of the electrical components in the pre-amp had the part numbers scraped off.&lt;br /&gt;
&lt;br /&gt;
=== After Upload ===&lt;br /&gt;
&lt;br /&gt;
After the video was published, Tom Evans Audio issued a copyright strike against the video which resulted in the video being taken down. Mend It Mark was not informed on what the copyright infringement was.&amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=qYpPNCzQCVQ&amp;lt;/ref&amp;gt; This decision was met with criticism from creators on YouTube since it questions whether or not showing a circuit design in a video could be considered copyright infringement.&amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=gJYIhLQJtTs&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=93QlQN_1yUA&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=15AiQv-EiGM&amp;lt;/ref&amp;gt; In December 2024, Louis Rossmann re-uploaded Mend It Mark&#039;s original video to his channel with his own introduction.&amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=6hVe_spuJQI&amp;lt;/ref&amp;gt; As of January 2025, the video is still up on his channel.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Companies]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=EVGA&amp;diff=3920</id>
		<title>EVGA</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=EVGA&amp;diff=3920"/>
		<updated>2025-01-21T13:07:03Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}{{InfoboxCompany&lt;br /&gt;
| Company = EVGA Corporation&lt;br /&gt;
| Name = EVGA&lt;br /&gt;
| Type = Private&lt;br /&gt;
| Founded = April 13, 1999&lt;br /&gt;
| Industry = Computer Hardware&lt;br /&gt;
| Official Website = https://evga.com&lt;br /&gt;
| Logo = EVGA_Logo.svg.png&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
* [[wikipedia:EVGA_Corporation|&#039;&#039;&#039;EVGA Corporation&#039;&#039;&#039;]] is an American computer hardware company that produces motherboards, gaming laptops, power supplies, all-in-one liquid coolers, computer cases, and gaming mice.&lt;br /&gt;
* Founded on April 13, 1999, it is headquartered in Brea, California.&lt;br /&gt;
&lt;br /&gt;
== Controversies ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
!Controversy&lt;br /&gt;
!Year&lt;br /&gt;
!Background Info&lt;br /&gt;
!Aftermath&lt;br /&gt;
!Related Article&lt;br /&gt;
!Related Video(s)&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== General References: ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Companies]]&lt;br /&gt;
[[Category:EVGA]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Sony%27s_WF-1000XM4_earbuds&amp;diff=3918</id>
		<title>Sony&#039;s WF-1000XM4 earbuds</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Sony%27s_WF-1000XM4_earbuds&amp;diff=3918"/>
		<updated>2025-01-21T12:55:14Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
&lt;br /&gt;
The video titled &amp;quot;Why you should never buy Sony earphones until they fix battery defects!&amp;quot; discusses significant battery issues in Sony&#039;s WF-1000XM4 earbuds, particularly after firmware updates. Users have reported severe uneven battery drain, with the affected earbud becoming excessively hot during charging. The common factor appears to be the 1.4.2 firmware update.&lt;br /&gt;
&lt;br /&gt;
[https://www.reddit.com/r/SonyHeadphones/comments/x7mx2n/wf1000xm4_severe_battery_issues/?utm_source=chatgpt.com&amp;amp;rdt=65095 Reddit] [https://archive.is/V0cUP Archived]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Key Points:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Battery Drain Issues:&#039;&#039;&#039; Many users have experienced rapid battery depletion in one earbud, leading to significantly reduced usage time.&lt;br /&gt;
* &#039;&#039;&#039;Overheating During Charging:&#039;&#039;&#039; Some users have reported that the affected earbud becomes unusually hot while charging, indicating potential battery damage.&lt;br /&gt;
* &#039;&#039;&#039;Firmware Update Concerns:&#039;&#039;&#039; The 1.4.2 firmware update is commonly associated with these battery issues. Users have noted that downgrading to earlier firmware versions may alleviate the problem, but this is not a guaranteed solution.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Recommendations:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Contact Sony Support:&#039;&#039;&#039; If you experience these issues, reach out to Sony&#039;s customer service for assistance. They may offer warranty replacements or repairs.&lt;br /&gt;
* &#039;&#039;&#039;Monitor Firmware Updates:&#039;&#039;&#039; Be cautious with firmware updates. Before updating, check user forums and official communications for any reported issues related to the new firmware.&lt;br /&gt;
* &#039;&#039;&#039;Community Feedback:&#039;&#039;&#039; Engage with online communities, such as Reddit&#039;s r/SonyHeadphones, to share experiences and solutions with other users facing similar problems.&lt;br /&gt;
&lt;br /&gt;
[[Category:Sony]]&lt;br /&gt;
[[Category:Products]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=3915</id>
		<title>Disney wrongful-death lawsuit</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Disney_wrongful-death_lawsuit&amp;diff=3915"/>
		<updated>2025-01-21T12:44:41Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Legal Lockout]]&lt;br /&gt;
=== The EPCOT Death Lawsuit and Disney&#039;s Arbitration Clause ===&lt;br /&gt;
In a wrongful death lawsuit&amp;lt;ref&amp;gt;[[:File:AUGUST 2ND RESPONSE.pdf]]&amp;lt;/ref&amp;gt;, Jeffrey Piccolo sued Walt Disney Parks &amp;amp; Resorts (WDPR) &amp;amp; Great Irish Pubs Florida, Inc. after his wife, Dr. Kanokporn Tangsuan, died from a severe allergic reaction at Raglan Road Irish Pub in Disney Springs on October 5, 2023. The lawsuit accused the restaurant and Disney with negligence in accommodating her food allergy which contributed to her death.&amp;lt;ref name=nprdwd&amp;gt;https://www.npr.org/2024/08/14/nx-s1-5074830/disney-wrongful-death-lawsuit-disney&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
Dr. Tangsuan, a family medicine specialist at NYU Langone Hospital, had severe allergies to dairy &amp;amp; nuts. She &amp;amp; her family chose to dine at Raglan Road, &#039;&#039;specifically because Disney had advertised that they accommodate guests with food allergies throughout their properties.&#039;&#039; Despite Dr. Tangsuan repeatedly informing her server about her allergies &amp;amp; receiving multiple assurances that their ordered dishes would be allergen-free, Dr. Tangsuan suffered a severe allergic reaction approximately 45 minutes after eating. Although she self-administered an EpiPen, she later died at the hospital. The medical examiner confirmed her death was due to anaphylaxis from elevated levels of dairy and nuts in her system.&amp;lt;ref name=nytdwd&amp;gt;https://www.nytimes.com/2024/08/14/nyregion/disney-wrongful-death-lawsuit-arbitration.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The EULA Roofie Attempt==&lt;br /&gt;
In May 2024, Disney attempted to have the case dismissed from court and sent to [[Forced Arbitration|arbitration]], citing two separate user agreements:&lt;br /&gt;
&lt;br /&gt;
# The Disney+ user agreement Piccolo accepted in 2019 when signing up for a free trial to Disney&#039;s streaming service on his PlayStation&lt;br /&gt;
# Terms accepted when purchasing (ultimately unused) Epcot tickets through the My Disney Experience app in September 2023&lt;br /&gt;
&lt;br /&gt;
This represented a classic example of a [[EULA roofie]], where Disney attempted to use terms buried within a streaming service agreement to deny a consumer&#039;s right to sue over an unrelated wrongful death case at a restaurant. Disney argued that because Piccolo had clicked &amp;quot;Agree &amp;amp; Continue&amp;quot; when signing up for the Disney+ streaming service, he was bound by an arbitration clause for any legal claims against the company or its affiliates when the food served by a restaurant on their premises killed his wife; regardless of whether the issue was related to the streaming service.&lt;br /&gt;
&lt;br /&gt;
Disney said that the reason for trying to send the case to arbitration was because the restaurant &amp;quot;is neither owned nor operated by Disney&amp;quot; and that they were defending themselves against inclusion in the lawsuit.&amp;lt;ref&amp;gt;https://edition.cnn.com/2024/08/14/business/disney-plus-wrongful-death-lawsuit/index.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Legal Arguments===&lt;br /&gt;
Piccolo&#039;s attorneys filed a 123-page response calling Disney&#039;s argument &amp;quot;preposterous&amp;quot; &amp;amp; &amp;quot;fatally flawed&amp;quot; for several reasons:&lt;br /&gt;
&lt;br /&gt;
* Mr. Piccolo brought the lawsuit as Personal Representative of his wife&#039;s estate, not as him the individual&lt;br /&gt;
* The estate itself never agreed to any arbitration terms&lt;br /&gt;
* The estate did not exist at the time Mr. Piccolo accepted the Disney+ terms, as Dr. Tangsuan was still alive&lt;br /&gt;
* The Disney+ Subscriber Agreement was &#039;&#039;specifically limited to disputes concerning the streaming service&#039;&#039;&lt;br /&gt;
* Disney had already waived any right to arbitration by participating in the litigation before raising the issue&lt;br /&gt;
&lt;br /&gt;
The attorneys argued that &amp;quot;the notion that terms agreed to by a consumer when creating a Disney+ free trial account would forever bar that consumer&#039;s right to a jury trial in any dispute with any Disney affiliate or subsidiary, is so outrageously unreasonable and unfair as to shock the judicial conscience.&amp;quot;&amp;lt;ref name=nytdwd /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Procedural Timeline==&lt;br /&gt;
A concerning aspect of Disney&#039;s attempt was that they first participated in discovery and filed an Answer to the complaint without raising arbitration as a defense; only later trying to use the EULA to avoid litigation. As noted in the August 2nd Response: &amp;quot;WDPR has waived its alleged right to seek arbitration by filing its Answer without raising arbitration as an affirmative defense and by serving two separate Requests for Copies under Rule 1.351(e).&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 3&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Key Legal Issues Around Consumer Rights==&lt;br /&gt;
===Meeting of Minds===&lt;br /&gt;
The Response highlighted fundamental contract law principles that challenge the validity of using broad EULAs to bind consumers. As stated in the filing, Disney&#039;s attempt violated basic principles of contract formation including &amp;quot;meeting of the minds (mutual understanding between parties)&amp;quot; and &amp;quot;good-faith dealing.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 11&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Unconscionability===&lt;br /&gt;
The Response detailed both procedural &amp;amp; substantive unconscionability in Disney&#039;s EULA:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Procedural Unconscionability:&#039;&#039;&#039;&lt;br /&gt;
** &amp;quot;There was no showing that Mr. Piccolo was given any explanation of the arbitration clauses in The Disney+ Subscriber Agreement.&amp;quot;&lt;br /&gt;
** &amp;quot;The so-called binding arbitration provision was merely contained in a link. With respect to the Disney Terms of Use, the link was not even referenced or hyperlinked on the Disney+ registration page. It was buried within another document that was hyperlinked.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 27-28&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Substantive Unconscionability:&#039;&#039;&#039;&lt;br /&gt;
** The arbitration provisions &amp;quot;could present a problem for more than just their own client&amp;quot;&lt;br /&gt;
** &amp;quot;In effect, WDPR is explicitly seeking to bar its 150 million Disney+ subscribers from ever prosecuting a wrongful death case against it in front of a jury even if the case facts have nothing to with Disney+&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 30&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The Florida Supreme Court has acknowledged there is some overlap in the analysis of whether a valid written agreement to arbitrate exists and whether an arbitrable issue exists, noting: &#039;It is something of a chicken and egg situation as to which comes first.&#039; This highlights the fundamental problem with modern EULAs - consumers cannot meaningfully assess what rights they&#039;re giving up when agreeing to terms that may be interpreted to cover any future dispute with any related corporate entity.&amp;quot;&amp;lt;ref&amp;gt;Plaintiff&#039;s Response in Opposition to Disney&#039;s Motion to Compel Arbitration, p. 19&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Resolution==&lt;br /&gt;
Following significant public backlash &amp;amp; media attention highlighting how this could affect Disney+&#039;s 150 million subscribers, Disney withdrew its motion to compel arbitration in August 2024. Josh D&#039;Amaro, chairman of Disney Experiences, stated: &amp;quot;At Disney, we strive to put humanity above all other considerations... With such unique circumstances as the ones in this case, we believe this situation warrants a sensitive approach to expedite a resolution for the family who have experienced such a painful loss.&amp;quot;&amp;lt;ref name=nprdwd /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Significance==&lt;br /&gt;
&lt;br /&gt;
The Response specifically addressed how Disney&#039;s [[EULA roofie]] attempt represents the type of modern consumer exploitation that traditional consumer protection laws fail to address: the potential dangers of overly broad arbitration clauses in consumer agreements and their use to deny access to courts even in serious cases like wrongful death. It demonstrates how companies may attempt to use unrelated consumer agreements to strip away fundamental legal rights, making it a notable example of the [[EULA roofie]] phenomenon. The case also showed how public attention and backlash can sometimes force companies to reconsider such tactics. This case demonstrates how companies use complex legal documents &amp;amp; digital agreements to manufacture consent for terms that a reasonable consumer would never knowingly accept, as a customer might be less likely to sign up for a free trial of a streaming service if he knew it would absolve the company from accountability for killing his wife. &lt;br /&gt;
== References ==&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Lawsuits]]&lt;br /&gt;
[[Category:EULA roofieing]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Blu-Ray_Ultra-HD_DRM&amp;diff=3911</id>
		<title>Blu-Ray Ultra-HD DRM</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Blu-Ray_Ultra-HD_DRM&amp;diff=3911"/>
		<updated>2025-01-21T12:30:12Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
&lt;br /&gt;
Ultra HD Blu-ray uses internet connected AACCS DRM requiring wifi every time a disk is played, if AACS servers shut down disks are permanently unplayable .&lt;br /&gt;
&lt;br /&gt;
[[Category:Digital rights management]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Xiaomi_Phone_unlock_requirements_and_procedure&amp;diff=3908</id>
		<title>Xiaomi Phone unlock requirements and procedure</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Xiaomi_Phone_unlock_requirements_and_procedure&amp;diff=3908"/>
		<updated>2025-01-21T12:24:36Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
&lt;br /&gt;
The following are some of the requirements/procedures needed to unlock a Xiaomi phone, as stated in their [https://new.c.mi.com/global/post/101245 FAQ]&lt;br /&gt;
&lt;br /&gt;
* Xiaomi requires users to create and link a Xiaomi account to their phone (and accept the [https://static.account.xiaomi.com/html/agreement/user/global/en_US.html EULA] for creating an account), and keep it linked for at least a week&lt;br /&gt;
** Stated directly in the  EULA is the following&amp;lt;blockquote&amp;gt;6. Modification of this Agreement Xiaomi may need to revise this Agreement and various rules from time to time in accordance with the promulgation of laws and regulations, the development of the Internet, and the adjustment of the company&#039;s operating conditions and business strategies. We will notify you of the new agreement in an appropriate manner, and you may view the latest version of the terms of the agreement on the relevant service page. **Once the revised agreement and rules are announced, they will take effect immediately and become an integral part of this Agreement. If you do not agree to the modified terms, you shall immediately discontinue your use of our services.** Your continued access or use of our services shall be deemed as your acceptance of the modified agreement.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
* Xiaomi requires users to attempt an unlock and wait a week before attempting again &amp;lt;blockquote&amp;gt;Click on Unlock » Unlock anyway. On your first attempt, Mi Unlock will flash the message _Couldn’t unlock. Please unlock 168 hours later._ Follow the timer / waiting period to unlock successfully.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
* Xiaomi requires users to be using an Intel based PC to unlock their phone (However, other CPU vendors work fine with the unlock tool on Linux)&lt;br /&gt;
* Unlocking your phone will void your phone&#039;s warranty&lt;br /&gt;
* You can only unlock one phone every 30 days and 4 phones every year&lt;br /&gt;
&lt;br /&gt;
[[Category:Xiaomi]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Sony_x900h_television&amp;diff=3906</id>
		<title>Sony x900h television</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Sony_x900h_television&amp;diff=3906"/>
		<updated>2025-01-21T12:22:54Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: incomplete, some ref work done&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
&lt;br /&gt;
Sony never fixed the blur issue in their X900H TV. It was advertised as supporting 4K120.&amp;lt;ref&amp;gt;https://web.archive.org/web/20210111215436/https://www.sony.ca/en/electronics/televisions/xbr-x900h-series/specifications&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://www.avsforum.com/threads/owners-thread-for-the-sony-x900h-no-price-talk.3125278/page-1819&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://videocardz.com/newz/sony-fixes-4k120hz-blurriness-on-x900h-xh90-tvs-by-applying-a-sharpening-filter&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Sony]]&lt;br /&gt;
[[Category:Products]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=3901</id>
		<title>Newag</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=3901"/>
		<updated>2025-01-21T12:15:43Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Under Development|date=15 January 2025|stage=Writing|priority=Medium to Low}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Newag S.A.&#039;&#039;&#039; (pronounced &#039;&#039;&amp;quot;nevag&amp;quot;&#039;&#039;) is a Polish company based in Nowy Sącz that specializes in the production, maintenance, and modernization of railway rolling stock.&amp;lt;ref&amp;gt;https://www.newag.pl/en/company/history/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Backdoor Incident ==&lt;br /&gt;
In 2022, when maintenance was done on trains manufactured by &#039;&#039;&#039;Newag&#039;&#039;&#039;, malicious code and backdoors were discovered which were found to make the trains break down after third-party repairs, prevent them from entering a competitors workshop and also stop working after a set amount of time standing still.&amp;lt;ref&amp;gt;https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/?utm_source=chatgpt.com&amp;lt;/ref&amp;gt; The investigation against &#039;&#039;&#039;Newag&#039;&#039;&#039; is still on-going.&lt;br /&gt;
&lt;br /&gt;
== Sources ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=John_Deere&amp;diff=1878</id>
		<title>John Deere</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=John_Deere&amp;diff=1878"/>
		<updated>2025-01-17T20:27:18Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&#039;&#039;&#039;[https://www.deere.com John Deere]&#039;&#039;&#039; is a leading manufacturer of Agricultural, and Heavy Machinery. Founded in 1837, they are primarily known for their heavy-duty agriculture machines, such as tractors and combines. They have recently faced criticism for their business practices, especially in the realm of equipment repair. These practices have raised concerns among farmers, independent repair technicians, and consumer advocacy groups.&amp;lt;ref name=&amp;quot;jdflrtrt&amp;quot;&amp;gt;https://www.npr.org/2025/01/15/nx-s1-5260895/john-deere-ftc-lawsuit-right-to-repair-tractors&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Consumer Protection Profile ==&lt;br /&gt;
[[File:John deere doc.png|thumb|524x524px|Front Page of the FTC&#039;s Suit Against John Deere&amp;lt;ref name=&amp;quot;DCRCCN325&amp;quot;&amp;gt;https://www.ftc.gov/system/files/ftc_gov/pdf/DeereCoREDACTEDComplaintCaseNo325-cv-50017.pdf&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
==== Repairability ====&lt;br /&gt;
&lt;br /&gt;
* John Deere limits access to essential repair software and diagnostic tools.&amp;lt;ref name=&amp;quot;dith3&amp;quot;&amp;gt;https://pirg.org/resources/deere-in-the-headlights-3/&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Restrictive policies prevent farmers from performing repairs or utilizing independent repair shops, forcing them to rely on authorized dealerships.&amp;lt;ref name=&amp;quot;jdflrtrt&amp;quot; /&amp;gt;&lt;br /&gt;
* Farmers have reported being unable to fix minor mechanical issues without John Deere&#039;s proprietary tools.&amp;lt;ref name=&amp;quot;fssdcp&amp;quot;&amp;gt;https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-states-sue-deere-company-protect-farmers-unfair-corporate-tactics-high-repair-costs&amp;lt;/ref&amp;gt;&lt;br /&gt;
* John Deere has allegedly unlawfully inflated repair costs by controlling the repair service market.&lt;br /&gt;
&lt;br /&gt;
==== Monopoly On Repairs ====&lt;br /&gt;
&lt;br /&gt;
* John Deere&#039;s control over the repair market has been likened to monopolistic behavior.&lt;br /&gt;
* By restricting, and controlling access to repair resources, and parts, the company has effectively eliminated competition in the repair market.&lt;br /&gt;
&lt;br /&gt;
==== Digital Rights and Ownership ====&lt;br /&gt;
&lt;br /&gt;
* John Deere uses software locks, and digital rights management (DRM) systems that control user autonomy.&amp;lt;ref&amp;gt;https://pirg.org/edfund/resources/john-deere-repair-software/&amp;lt;/ref&amp;gt;&lt;br /&gt;
* These measures prevent Farmers, and Independent repair technicians from completing repairs without access to the proprietary software.&amp;lt;ref name=&amp;quot;dith3&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Right to Repair Legislation Opposition ====&lt;br /&gt;
&lt;br /&gt;
* John Deer has actively lobbied against right-to-repair legislation in multiple states, and on the Federal level. &amp;lt;ref&amp;gt;https://pirg.org/resources/john-deere-and-right-to-repair-over-the-years/?utm_source=chatgpt.com&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://wisconsinwatch.org/2024/04/midwest-farmers-right-to-repair-agriculture-john-deere-illinois/?utm_source=chatgpt.com&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Despite signing a memorandum of understanding with the American Farm Bureau Federation in 2023, the company has been accused of undermining the spirit of the agreement.&amp;lt;ref&amp;gt;[https://investigatemidwest.org/2024/11/12/is-john-deeres-day-of-reckoning-soon-at-hand/#:~:text=In%20a%20nutshell%3A%20Deere%20embeds%20authorization%20codes%20in,dealers%20have%20access%20to%20all%20the%20verification%20codes. https://investigatemidwest.org/2024/11/12/is-john-deeres-day-of-reckoning-soon-at-hand/#:~:text=In%20a%20nutshell%3A%20Deere%20embeds%20authorization%20codes%20in,dealers%20have%20access%20to%20all%20the%20verification%20codes.]&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://www.youtube.com/watch?v=7-RgOUT3zeo&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Consumer Protection Incidents ==&lt;br /&gt;
&lt;br /&gt;
==== FTC Lawsuit (January 2025) ====&lt;br /&gt;
On January 15, 2025, the Federal Trade Commission (FTC) filed a lawsuit against John Deere, alleging anticompetitive practices in the repair market.&amp;lt;ref name=&amp;quot;fssdcp&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;DCRCCN325&amp;quot; /&amp;gt; The lawsuit claims that:&lt;br /&gt;
&lt;br /&gt;
* John Deere unlawfully inflated repair costs by monopolizing the repair service market.&lt;br /&gt;
* The company&#039;s restrictive policies violated consumer protection laws, and limited farmers&#039; ability to maintain their equipment.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Adobe_ToS_update_gives_the_company_rights_over_consumers%27_works&amp;diff=1021</id>
		<title>Adobe ToS update gives the company rights over consumers&#039; works</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Adobe_ToS_update_gives_the_company_rights_over_consumers%27_works&amp;diff=1021"/>
		<updated>2025-01-15T20:58:09Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Adobe, a computer software company that creates programs for content creation, editing, and publishing, has sparked controversy with their updated Terms of Service (ToS) which declares that by accepting, the user will grant Adobe a &amp;quot;non-exclusive, worldwide, royalty-free license&amp;quot;[https://www.adobe.com/legal/terms.html#:~:text=Content%2C%20you%20grant%20us-,a%20non%2Dexclusive%2C%20worldwide%2C%20royalty%2Dfree%20license,-to%20do%20the%20following] to their content to &#039;&#039;&#039;reproduce&#039;&#039;&#039;, &#039;&#039;&#039;distribute&#039;&#039;&#039;, &#039;&#039;&#039;create derivative works&#039;&#039;&#039;, &#039;&#039;&#039;publicly display&#039;&#039;&#039;, &#039;&#039;&#039;publicly preform&#039;&#039;&#039;, and &#039;&#039;&#039;sublicense [https://www.adobe.com/legal/terms.html#:~:text=reproduce%C2%A0%C2%A0%E2%80%A8%0A(for,your%20Cloud%20Content).]&#039;&#039;&#039; the user&#039;s content.  &lt;br /&gt;
&lt;br /&gt;
This sparks controversy because it can potentially violate a Non-Disclosure Agreement (NDA), and users can not access their content without first agreeing to the updated ToS, leaving many users without access to their unfinished projects. Furthermore, Adobe claims they do not use your content to train generative AI, but does admit they may use your content for machine learning and that you always have the option to opt-out despite there not being an &amp;quot;opt-out&amp;quot; button on the updated ToS screen shown below.  &lt;br /&gt;
&lt;br /&gt;
[[File:Adobe tos.jpg|thumb|Adobe&#039;s updated Terms of Service, which does not include an &amp;quot;opt-out&amp;quot; nor a &amp;quot;decline&amp;quot; option.]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Articles under development]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Adobe_ToS_update_gives_the_company_rights_over_consumers%27_works&amp;diff=1020</id>
		<title>Adobe ToS update gives the company rights over consumers&#039; works</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Adobe_ToS_update_gives_the_company_rights_over_consumers%27_works&amp;diff=1020"/>
		<updated>2025-01-15T20:57:46Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Adobe, a computer software company that creates programs for content creation, editing, and publishing, has sparked controversy with their updated Terms of Service (ToS) which declares that by accepting, the user will grant Adobe a &amp;quot;non-exclusive, worldwide, royalty-free license&amp;quot;[https://www.adobe.com/legal/terms.html#:~:text=Content%2C%20you%20grant%20us-,a%20non%2Dexclusive%2C%20worldwide%2C%20royalty%2Dfree%20license,-to%20do%20the%20following] to their content to &#039;&#039;&#039;reproduce&#039;&#039;&#039;, &#039;&#039;&#039;distribute&#039;&#039;&#039;, &#039;&#039;&#039;create derivative works&#039;&#039;&#039;, &#039;&#039;&#039;publicly display&#039;&#039;&#039;, &#039;&#039;&#039;publicly preform&#039;&#039;&#039;, and &#039;&#039;&#039;sublicense [https://www.adobe.com/legal/terms.html#:~:text=reproduce%C2%A0%C2%A0%E2%80%A8%0A(for,your%20Cloud%20Content).]&#039;&#039;&#039; the user&#039;s content.  &lt;br /&gt;
&lt;br /&gt;
This sparks controversy because it can potentially violate a Non-Disclosure Agreement (NDA), and users can not access their content without first agreeing to the updated ToS, leaving many users without access to their unfinished projects. Furthermore, Adobe claims they do not use your content to train generative AI, but does admit they may use your content for machine learning and that you always have the option to opt-out despite there not being an &amp;quot;opt-out&amp;quot; button on the updated ToS screen shown below.  &lt;br /&gt;
&lt;br /&gt;
[[File:Adobe tos.jpg|thumb|Adobe&#039;s updated Terms of Service, which does not include an &amp;quot;opt-out&amp;quot; nor a &amp;quot;decline&amp;quot; option.]]&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Articles under development]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=1002</id>
		<title>Newag</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=1002"/>
		<updated>2025-01-15T20:17:56Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Under Development|date=15 January 2025|stage=Writing|priority=Medium to Low}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Newag S.A.&#039;&#039;&#039; (pronounced &#039;&#039;&amp;quot;nevag&amp;quot;&#039;&#039;) is a Polish company, based in Nowy Sącz, specializing in the production, maintenance, and modernization of railway rolling stock.&amp;lt;ref&amp;gt;https://www.newag.pl/en/company/history/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Backdoor Incident ==&lt;br /&gt;
In 2022 maintenance was done on trains manufactured by &#039;&#039;&#039;Newag&#039;&#039;&#039; which uncovered malicious software code and backdoors.&amp;lt;ref&amp;gt;https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/?utm_source=chatgpt.com&amp;lt;/ref&amp;gt; The investigation against &#039;&#039;&#039;Newag&#039;&#039;&#039; is still on-going.&lt;br /&gt;
== Sources ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Amazon_PhotosPlus_discontinuation&amp;diff=973</id>
		<title>Amazon PhotosPlus discontinuation</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Amazon_PhotosPlus_discontinuation&amp;diff=973"/>
		<updated>2025-01-15T19:15:06Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Amazon PhotosPlus was a Subscription based service that offered users the ability to display their chosen photos on their devices as the &amp;quot;primary content&amp;quot;.  Additionally, It provided 25GB of Amazon Photos storage, and costed 2$ per month. Announced&amp;lt;ref&amp;gt;https://www.pocket-lint.com/what-is-amazon-photosplus/&amp;lt;/ref&amp;gt; in October 2023, Amazon sent an email informing its users that they were discontinuing&amp;lt;ref&amp;gt;https://www.threads.net/@wheelsee/post/C-58LrqSbYW?xmt=AQGzdSySswLxRPEtQdHvzY0PMn5k0eXCG2lzMqmc0irZoIQ&amp;lt;/ref&amp;gt; the service, cancelling it on September 12, 2024.  &lt;br /&gt;
&lt;br /&gt;
The Amazon Echo Show 8 was a Digital Frame, launched at 149.99$. For 10$ more, you could get the Amazon Echo Show 8 Photos Edition, which came with 6 months of PhotosPlus and the ability to display your photos as the &amp;quot;primary&amp;quot; content. Amazon spokesperson Courtney Ramirez&amp;lt;ref&amp;gt;https://www.theverge.com/2023/9/22/23885332/amazon-echo-show-8-photos-edition-digital-frame-price-fee&amp;lt;/ref&amp;gt; confirmed that “Occasionally, Alexa will provide content suggestions based on a customer’s interest. However, photos will remain the primary content.”  &lt;br /&gt;
&lt;br /&gt;
After the cancellation of the PhotosPlus Service, the Amazon Echo Show 8 Photos Edition is identical&amp;lt;ref&amp;gt;https://www.howtogeek.com/amazon-cancels-photosplus-subscription/&amp;lt;/ref&amp;gt; to the Amazon Echo Show 8, and user who wish to display their photos have to do so with advertisements and promotional content.  &lt;br /&gt;
== Sources ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Incidents]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Amazon_PhotosPlus_discontinuation&amp;diff=972</id>
		<title>Amazon PhotosPlus discontinuation</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Amazon_PhotosPlus_discontinuation&amp;diff=972"/>
		<updated>2025-01-15T19:14:47Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: References corrected&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Amazon PhotosPlus was a Subscription based service that offered users the ability to display their chosen photos on their devices as the &amp;quot;primary content&amp;quot;.  Additionally, It provided 25GB of Amazon Photos storage, and costed 2$ per month. Announced&amp;lt;ref&amp;gt;https://www.pocket-lint.com/what-is-amazon-photosplus/&amp;lt;/ref&amp;gt; in October 2023, Amazon sent an email informing its users that they were discontinuing&amp;lt;ref&amp;gt;https://www.threads.net/@wheelsee/post/C-58LrqSbYW?xmt=AQGzdSySswLxRPEtQdHvzY0PMn5k0eXCG2lzMqmc0irZoIQ&amp;lt;/ref&amp;gt; the service, cancelling it on September 12, 2024.  &lt;br /&gt;
&lt;br /&gt;
The Amazon Echo Show 8 was a Digital Frame, launched at 149.99$. For 10$ more, you could get the Amazon Echo Show 8 Photos Edition, which came with 6 months of PhotosPlus and the ability to display your photos as the &amp;quot;primary&amp;quot; content. Amazon spokesperson Courtney Ramirez&amp;lt;ref&amp;gt;https://www.theverge.com/2023/9/22/23885332/amazon-echo-show-8-photos-edition-digital-frame-price-fee&amp;lt;/ref&amp;gt; confirmed that “Occasionally, Alexa will provide content suggestions based on a customer’s interest. However, photos will remain the primary content.”  &lt;br /&gt;
&lt;br /&gt;
After the cancellation of the PhotosPlus Service, the Amazon Echo Show 8 Photos Edition is identical&amp;lt;ref&amp;gt;https://www.howtogeek.com/amazon-cancels-photosplus-subscription/&amp;lt;/ref&amp;gt; to the Amazon Echo Show 8, and user who wish to display their photos have to do so with advertisements and promotional content.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Sources ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
Sources: &lt;br /&gt;
&lt;br /&gt;
https://www.pocket-lint.com/what-is-amazon-photosplus/&lt;br /&gt;
&lt;br /&gt;
https://www.threads.net/@wheelsee/post/C-58LrqSbYW?xmt=AQGzdSySswLxRPEtQdHvzY0PMn5k0eXCG2lzMqmc0irZoIQ&lt;br /&gt;
&lt;br /&gt;
https://www.theverge.com/2023/9/22/23885332/amazon-echo-show-8-photos-edition-digital-frame-price-fee&lt;br /&gt;
&lt;br /&gt;
https://www.howtogeek.com/amazon-cancels-photosplus-subscription/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Incidents]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=933</id>
		<title>Newag</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=933"/>
		<updated>2025-01-15T14:17:26Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Under Development|date=15 January 2025|stage=Writing|priority=Medium to Low}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Newag S.A.&#039;&#039;&#039; (pronounced &#039;&#039;&amp;quot;nevag&amp;quot;&#039;&#039;) is a Polish company, based in Nowy Sącz, specializing in the production, maintenance, and modernization of railway rolling stock.&amp;lt;ref&amp;gt;https://www.newag.pl/en/company/history/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Backdoor Incident ==&lt;br /&gt;
In 2022 maintenance was done on trains manufactured by &#039;&#039;&#039;Newag&#039;&#039;&#039; which uncovered malicious software code and backdoors.&amp;lt;ref&amp;gt;https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/?utm_source=chatgpt.com&amp;lt;/ref&amp;gt; The investigation against &#039;&#039;&#039;Newag&#039;&#039;&#039; is still on-going.&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=932</id>
		<title>Newag</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Newag&amp;diff=932"/>
		<updated>2025-01-15T14:16:10Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: Created page with &amp;quot;&amp;#039;&amp;#039;&amp;#039;Newag S.A.&amp;#039;&amp;#039;&amp;#039; (pronounced &amp;#039;&amp;#039;&amp;quot;nevag&amp;quot;&amp;#039;&amp;#039;) is a Polish company, based in Nowy Sącz, specializing in the production, maintenance, and modernization of railway rolling stock.&amp;lt;ref&amp;gt;https://www.newag.pl/en/company/history/&amp;lt;/ref&amp;gt;  == Backdoor Incident == In 2022 maintenance was done on trains manufactured by &amp;#039;&amp;#039;&amp;#039;Newag&amp;#039;&amp;#039;&amp;#039; which uncovered malicious software code and backdoors.&amp;lt;ref&amp;gt;https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-com...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Newag S.A.&#039;&#039;&#039; (pronounced &#039;&#039;&amp;quot;nevag&amp;quot;&#039;&#039;) is a Polish company, based in Nowy Sącz, specializing in the production, maintenance, and modernization of railway rolling stock.&amp;lt;ref&amp;gt;https://www.newag.pl/en/company/history/&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Backdoor Incident ==&lt;br /&gt;
In 2022 maintenance was done on trains manufactured by &#039;&#039;&#039;Newag&#039;&#039;&#039; which uncovered malicious software code and backdoors.&amp;lt;ref&amp;gt;https://arstechnica.com/tech-policy/2023/12/manufacturer-deliberately-bricked-trains-repaired-by-competitors-hackers-find/?utm_source=chatgpt.com&amp;lt;/ref&amp;gt; The investigation against &#039;&#039;&#039;Newag&#039;&#039;&#039; is still on-going.&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Ancestry.com&amp;diff=883</id>
		<title>Ancestry.com</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Ancestry.com&amp;diff=883"/>
		<updated>2025-01-15T12:10:46Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Genealogy company based in the US.&lt;br /&gt;
&lt;br /&gt;
== Cancellation policy ==&lt;br /&gt;
May charge a cancellation fee for &amp;quot;Subscriptions Longer than a Month, Billed Monthly&amp;quot; if you do not cancel within the first 14 days: &amp;lt;ref&amp;gt;https://www.ancestry.com/c/legal/renewal-cancellation-terms&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Where offered, some subscriptions longer than a month may be eligible for monthly billing. Even though you will be billed monthly, you are committing to the entire length of your subscription (e.g. 6 months or 12 months).&lt;br /&gt;
 &lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
(1) cancel immediately for a full refund of the first month’s fee and immediate loss of access, or (2) cancel effective at the end of the first month, subject to a cancellation fee. If you change from this type of subscription to a different type of subscription before the end of your subscription term, you will receive a prorated refund for the remainder of the current paid month, and you may be charged a cancellation fee. For subscriptions purchased on www.ancestry.com, cancellation fees are the lesser of (i) $25 USD for 6-month subscriptions or $50 USD for 12-month subscriptions (plus any applicable taxes) or (ii) the remaining cost of your subscription&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
[https://web.archive.org/web/20240824032751/https://www.ancestry.com/offers/subscribe Ancestry&#039;s older price pages] showed an offer which was following these cancellation terms along with a citation showing the commitment, however since then this has been removed from the page.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:anti-consumer]]&lt;br /&gt;
[[Category:Companies]]&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
	<entry>
		<id>https://mirror.consumerrights.wiki/index.php?title=Ford&amp;diff=600</id>
		<title>Ford</title>
		<link rel="alternate" type="text/html" href="https://mirror.consumerrights.wiki/index.php?title=Ford&amp;diff=600"/>
		<updated>2025-01-15T00:08:40Z</updated>

		<summary type="html">&lt;p&gt;Tpat90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
----&lt;br /&gt;
Henry Ford made the first patent Ford automobile, the quadricycle in 1896. He then actually incorporated the Ford motor company in 1903. They&#039;re now a company known pretty well for anti-consumer behaviour, and automotive-typical practices like marked up parts sharing that probably started in the late 1990&#039;s.&lt;br /&gt;
&lt;br /&gt;
=== Anti-Consumer Practices ===&lt;br /&gt;
Ford have been known recently for being the maker of America&#039;s most recalled vehicles. CEO Jim Farley recently said &amp;quot;no more recalls&amp;quot;, and at least in Europe, that&#039;s been enforced by selling engines that break themselves and sometimes catch fire doing it, with the only recall being to fix the fire part. Ford have filed dangerous patents and have managed to find a way in the 2020&#039;s to make a software update go so wrong it bricks a vehicle.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ford also have made some, luckily not realised patents for systems like one that feeds ads to distract the driver of their automobiles, and another patent for a system to annoy the owner of, restrict access to and then repossess or destroy vehicles where the owner &amp;quot;has defected&amp;quot; on finance payments.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Samcrac&#039;s 2024 video mini-series on his Aston Martin shows the pettiness and stupidity of either Ford or Aston Martin, but certainly Ford&#039;s design of needing a VIN-and-vehicle-specific &amp;quot;Car Configuration File&amp;quot; they (and now Aston Martin as its own corporate entity) only have control of to turn a Volvo C30&#039;s ECU into one for an exotic Aston Martin, is a bit ridiculous, and the fact Aston Martin wouldn&#039;t simply give Samcrac the simple file without attaching $15,000 in overpriced and completely unneeded repairs, is even worse.&lt;br /&gt;
&lt;br /&gt;
==== Footnote from the author ====&lt;br /&gt;
I live in the EU. Why does this company not understand we do not want more dropshipped Volkswagen ID4&#039;s carrying the nameplates of once actually good cars? There are two of those now (The &amp;quot;Capri&amp;quot; and &amp;quot;Explorer&amp;quot;), and something else that&#039;s very similar (the &amp;quot;Mustang&amp;quot; Mach-E). We don&#039;t want more shoddily designed compact SUV&#039;s made by another manufacturer, and it&#039;s proven competing with yourself is stupid and in the end, you won&#039;t win doing that.&lt;/div&gt;</summary>
		<author><name>Tpat90</name></author>
	</entry>
</feed>