Consumer Rights Wiki - User contributions [en]

Markiza and Joy ad-skipping disabling

2026-05-16T21:39:12Z

Louis: Remove red links per anti-slop rule

{{#seo:
|description=Slovak broadcasters Markíza and Joj disabled ad-skipping on IPTV archive services in mid-2025, triggering an antitrust investigation by the PMÚ.
}}

{{IncidentCargo
|Company=TV Markíza,TV Joj
|StartDate=2025-05-21
|EndDate=
|Status=Active
|ProductLine=
|Product=
|ArticleType=Service
|Type=Anti-competitive practice
|Description=Slovak broadcasters Markíza and Joj disabled ad-skipping in IPTV archive and catch-up services, removing a feature subscribers paid for
}}

'''TV Markíza''' & '''TV Joj''', Slovakia's two largest commercial broadcasters, disabled ad-skipping & fast-forwarding during commercial breaks in IPTV archive & catch-up services in mid-2025, removing a feature that had been included in paid subscriptions.<ref name="broadband-pmu">{{Cite web |url=https://www.broadbandtvnews.com/2025/10/02/pmu-launches-probe-into-markiza-joj-over-ad-skipping-restrictions/ |title=PMÚ launches probe into Markíza & JOJ over ad-skipping restrictions |publisher=Broadband TV News |date=October 2, 2025 |access-date=May 15, 2026}}</ref> The restrictions began with Markíza on May 21, 2025, followed by Joj in July 2025.<ref name="omediach">{{Cite web |url=https://www.omediach.com/tv/29076-protimonopolny-urad-zacal-konat-proti-joj-a-markize-pre-obmedzenie-moznosti-pretacania-reklam |title=Protimonopolný úrad začal konať proti JOJ a Markíze pre obmedzenie možnosti pretáčania reklám |publisher=Omediach.com |date=September 30, 2025 |access-date=May 15, 2026}}</ref> 4ka rolled out the blocks on June 23 & July 15, 2025,<ref name="4ka-faq">{{Cite web |url=https://www.4ka.sk/pretacanie-reklam/ |title=Pretáčanie reklám |publisher=4ka |date=2025 |access-date=May 15, 2026}}</ref> & Orange Slovensko implemented the Markíza block on June 18, 2025 & announced the Joj block would take effect on July 16, 2025.<ref name="mediaklik">{{Cite web |url=https://www.mediaklik.sk/televizia/clanok/756261-dalsi-velky-operator-blokuje-pretacanie-reklam-na-markize-reklamy-v-archive-uz-nepreskocite-ani-po-3-minutach/ |title=Ďalší veľký operátor blokuje pretáčanie reklám na Markíze: Reklamy v archíve už nepreskočíte ani po 3 minútach |author=Vanessa Teluchová |publisher=Mediaklik |date=June 18, 2025 |access-date=May 15, 2026}}</ref><ref name="zive-orange">{{Cite web |url=https://zive.aktuality.sk/clanok/dwnx1rF/zakaz-pretacania-reklam-pri-joj-kedy-s-nim-zacne-velky-operator-bude-iny-nez-pri-markize/ |title=Zákaz pretáčania reklám pri JOJ: Kedy s ním začne veľký operátor. Bude iný než pri Markíze |author=Filip Maxa |publisher=Živé.sk |date=July 15, 2025 |access-date=May 15, 2026}}</ref> Slovakia's Antimonopoly Office (PMÚ) expanded an ongoing administrative proceeding against TV Markíza in late July 2025 & opened a separate proceeding against TV Joj in August 2025, then publicly announced both investigations on September 30, 2025, alleging abuse of dominant market position & imposing potential fines of up to 10 percent of their global turnover.<ref name="antitrust">{{Cite web |url=https://antitrust-intelligence.com/slovak-pmu-investigates-tv-markiza-and-tv-joj-for-potential-market-abuse/ |title=Slovak PMÚ Investigates TV Markíza and TV JOJ for Potential Market Abuse |publisher=Antitrust Intelligence |date=October 2025 |access-date=May 15, 2026}}</ref>

== Background ==

Slovakia's commercial television market is dominated by two broadcasters: TV Markíza & TV Joj.<ref name="omediach" /> IPTV archive & catch-up services allow subscribers to view programs after their original broadcast, typically with the ability to pause, rewind, & fast-forward through content.<ref name="4ka-faq" /> Before May 2025, fast-forwarding through commercial breaks was a standard function of these services.<ref name="4ka-faq" />

== Ad-skipping restrictions ==

TV Markíza implemented a technical solution to disable ad-skipping on May 21, 2025, compelling telecommunications operators to deploy the restriction across their networks.<ref name="omediach" /> Orange Slovensko rolled out the block for Markíza channels on June 18, 2025,<ref name="mediaklik" /> & 4ka followed on June 23, 2025.<ref name="4ka-faq" /> 4ka stated it had resisted the broadcaster mandate for more than a year before implementing the restrictions.<ref name="4ka-faq" /> The affected Markíza channels included Markíza, Doma, Dajto, Krimi, & Klasik.<ref name="4ka-faq" />

TV Joj mandated the restriction in July 2025.<ref name="omediach" /> 4ka deployed the block for Joj channels on July 15, 2025,<ref name="4ka-faq" /> & Orange Slovensko announced it would implement the restriction on July 16, 2025.<ref name="zive-orange" /> The affected Joj channels included JOJ, JOJ Plus, & WAU.<ref name="4ka-faq" />

The restrictions prevent subscribers from skipping advertising blocks in archive programming. When a subscriber opens an affected program, the system allows 60 seconds of free navigation before locking forward skip for the remainder of the program. During the marked segment, the fast-forward & skip functions are disabled.<ref name="imafex">{{Cite web |url=https://www.imafex.sk/reklamy-na-markize-uz-nepretocite |title=Reklamy na TV staniciach Markíza a JOJ už nepretočíte |publisher=IMAFEX |date=2025 |access-date=May 15, 2026}}</ref>

4ka introduced a paid add-on called "Bez reklám" (No Ads) priced at €4 per month, which enables subscribers to skip advertising blocks on JOJ channels (JOJ, JOJ Plus, and WAU).<ref name="4ka-faq" />

=== Markíza's response ===

Markíza CEO Peter Gažík stated in May 2025, as reported by omediach.com:
<blockquote>''Z našej strany ide o dlho pripravovanú reakciu na súčasné trendy. Sme komerčná televízia, ktorá hlavne vďaka príjmom z reklamy dokáže produkovať kvalitné vlastné programy, filmy či seriály, obľúbené u našich divákov a diváčok. Zavedením tejto funkcionality dosiahneme odstránenie rozdielu medzi sledovaním televízie a reklám v reálnom čase a pri sledovaní s časovým posunom, ako aj porovnateľné nastavenie, ktoré je aplikované pri iných online platformách.''</blockquote><ref name="omediach" />

== PMÚ investigation ==

In late July 2025, the PMÚ expanded an ongoing administrative proceeding against TV Markíza to include the ad-skipping restrictions.<ref name="omediach" /> In August 2025, the PMÚ opened a separate administrative proceeding against TV Joj.<ref name="omediach" /> On September 30, 2025, the PMÚ publicly announced investigations into both broadcasters.<ref name="broadband-pmu" /><ref name="zive">{{Cite web |url=https://zive.aktuality.sk/clanok/3fJlcym/markiza-a-joj-maju-problem-stat-ich-preveruje-pre-obmedzene-pretacanie-reklam/ |title=Markíza a JOJ majú problém: Štát ich preveruje pre obmedzené pretáčanie reklám |author=Filip Maxa |publisher=Živé.sk |date=September 30, 2025 |access-date=May 15, 2026}}</ref>

The proceedings allege abuse of a dominant market position under Slovak Act No. 187/2021 Coll. on the Protection of Competition.<ref name="slovak-act">{{Cite web |url=https://www.antimon.gov.sk/zakon-o-ochrane-hospodarskej-sutaze/ |title=Zákon o ochrane hospodárskej súťaže |publisher=Protimonopolný úrad Slovenskej republiky |date=2021 |access-date=May 15, 2026}}</ref> If the PMÚ finds a violation, the broadcasters face fines of up to 10 percent of their global turnover.<ref name="antitrust" />

The Telecommunications Union of the Slovak Republic (TUSR), an industry association representing operators, formally welcomed the PMÚ investigation in October 2025.<ref name="techbyte">{{Cite web |url=https://www.techbyte.sk/2025/10/markiza-jojka-klepli-prstoch-zakaz-pretacania-reklam/ |title=Markíze aj JOJ-ke klepli po prstoch: Majú ZRUŠIŤ obmedzenie |publisher=TechByte.sk |date=October 7, 2025 |access-date=May 15, 2026}}</ref>

== Consumer response ==

Subscribers reacted to the restrictions with complaints about what TechByte.sk described as a feeling of "double paying"; paying for IPTV service while being forced to watch advertisements they previously could skip.<ref name="techbyte" />

== Related incidents ==

In June 2022, FTV Prima, a Czech commercial broadcaster, imposed similar ad-skipping restrictions on its IPTV archive service.<ref name="broadband-prima">{{Cite web |url=https://www.broadbandtvnews.com/2022/05/27/czech-prima-to-stop-ad-skipping/ |title=Czech Prima to stop ad-skipping |publisher=Broadband TV News |date=May 27, 2022 |access-date=May 15, 2026}}</ref>
== References ==

{{reflist}}

[[Category:TV Markíza]]
[[Category:TV Joj]]
[[Category:Anti-competitive practice]]
[[Category:Slovakia]]

Markiza and Joy ad-skipping disabling

2026-05-16T21:36:25Z

Louis: Initial publication via architect pipeline

{{#seo:
|description=Slovak broadcasters Markíza and Joj disabled ad-skipping on IPTV archive services in mid-2025, triggering an antitrust investigation by the PMÚ.
}}

{{IncidentCargo
|Company=TV Markíza,TV Joj
|StartDate=2025-05-21
|EndDate=
|Status=Active
|ProductLine=
|Product=
|ArticleType=Service
|Type=Anti-competitive practice
|Description=Slovak broadcasters Markíza and Joj disabled ad-skipping in IPTV archive and catch-up services, removing a feature subscribers paid for
}}

'''TV Markíza''' & '''TV Joj''', Slovakia's two largest commercial broadcasters, disabled ad-skipping & fast-forwarding during commercial breaks in IPTV archive & catch-up services in mid-2025, removing a feature that had been included in paid subscriptions.<ref name="broadband-pmu">{{Cite web |url=https://www.broadbandtvnews.com/2025/10/02/pmu-launches-probe-into-markiza-joj-over-ad-skipping-restrictions/ |title=PMÚ launches probe into Markíza & JOJ over ad-skipping restrictions |publisher=Broadband TV News |date=October 2, 2025 |access-date=May 15, 2026}}</ref> The restrictions began with Markíza on May 21, 2025, followed by Joj in July 2025.<ref name="omediach">{{Cite web |url=https://www.omediach.com/tv/29076-protimonopolny-urad-zacal-konat-proti-joj-a-markize-pre-obmedzenie-moznosti-pretacania-reklam |title=Protimonopolný úrad začal konať proti JOJ a Markíze pre obmedzenie možnosti pretáčania reklám |publisher=Omediach.com |date=September 30, 2025 |access-date=May 15, 2026}}</ref> 4ka rolled out the blocks on June 23 & July 15, 2025,<ref name="4ka-faq">{{Cite web |url=https://www.4ka.sk/pretacanie-reklam/ |title=Pretáčanie reklám |publisher=4ka |date=2025 |access-date=May 15, 2026}}</ref> & Orange Slovensko implemented the Markíza block on June 18, 2025 & announced the Joj block would take effect on July 16, 2025.<ref name="mediaklik">{{Cite web |url=https://www.mediaklik.sk/televizia/clanok/756261-dalsi-velky-operator-blokuje-pretacanie-reklam-na-markize-reklamy-v-archive-uz-nepreskocite-ani-po-3-minutach/ |title=Ďalší veľký operátor blokuje pretáčanie reklám na Markíze: Reklamy v archíve už nepreskočíte ani po 3 minútach |author=Vanessa Teluchová |publisher=Mediaklik |date=June 18, 2025 |access-date=May 15, 2026}}</ref><ref name="zive-orange">{{Cite web |url=https://zive.aktuality.sk/clanok/dwnx1rF/zakaz-pretacania-reklam-pri-joj-kedy-s-nim-zacne-velky-operator-bude-iny-nez-pri-markize/ |title=Zákaz pretáčania reklám pri JOJ: Kedy s ním začne veľký operátor. Bude iný než pri Markíze |author=Filip Maxa |publisher=Živé.sk |date=July 15, 2025 |access-date=May 15, 2026}}</ref> Slovakia's Antimonopoly Office (PMÚ) expanded an ongoing administrative proceeding against TV Markíza in late July 2025 & opened a separate proceeding against TV Joj in August 2025, then publicly announced both investigations on September 30, 2025, alleging abuse of dominant market position & imposing potential fines of up to 10 percent of their global turnover.<ref name="antitrust">{{Cite web |url=https://antitrust-intelligence.com/slovak-pmu-investigates-tv-markiza-and-tv-joj-for-potential-market-abuse/ |title=Slovak PMÚ Investigates TV Markíza and TV JOJ for Potential Market Abuse |publisher=Antitrust Intelligence |date=October 2025 |access-date=May 15, 2026}}</ref>

== Background ==

Slovakia's commercial television market is dominated by two broadcasters: [[TV Markíza]] & [[TV Joj]].<ref name="omediach" /> IPTV archive & catch-up services allow subscribers to view programs after their original broadcast, typically with the ability to pause, rewind, & fast-forward through content.<ref name="4ka-faq" /> Before May 2025, fast-forwarding through commercial breaks was a standard function of these services.<ref name="4ka-faq" />

== Ad-skipping restrictions ==

TV Markíza implemented a technical solution to disable ad-skipping on May 21, 2025, compelling telecommunications operators to deploy the restriction across their networks.<ref name="omediach" /> Orange Slovensko rolled out the block for Markíza channels on June 18, 2025,<ref name="mediaklik" /> & 4ka followed on June 23, 2025.<ref name="4ka-faq" /> 4ka stated it had resisted the broadcaster mandate for more than a year before implementing the restrictions.<ref name="4ka-faq" /> The affected Markíza channels included Markíza, Doma, Dajto, Krimi, & Klasik.<ref name="4ka-faq" />

TV Joj mandated the restriction in July 2025.<ref name="omediach" /> 4ka deployed the block for Joj channels on July 15, 2025,<ref name="4ka-faq" /> & Orange Slovensko announced it would implement the restriction on July 16, 2025.<ref name="zive-orange" /> The affected Joj channels included JOJ, JOJ Plus, & WAU.<ref name="4ka-faq" />

The restrictions prevent subscribers from skipping advertising blocks in archive programming. When a subscriber opens an affected program, the system allows 60 seconds of free navigation before locking forward skip for the remainder of the program. During the marked segment, the fast-forward & skip functions are disabled.<ref name="imafex">{{Cite web |url=https://www.imafex.sk/reklamy-na-markize-uz-nepretocite |title=Reklamy na TV staniciach Markíza a JOJ už nepretočíte |publisher=IMAFEX |date=2025 |access-date=May 15, 2026}}</ref>

4ka introduced a paid add-on called "Bez reklám" (No Ads) priced at €4 per month, which enables subscribers to skip advertising blocks on JOJ channels (JOJ, JOJ Plus, and WAU).<ref name="4ka-faq" />

=== Markíza's response ===

Markíza CEO Peter Gažík stated in May 2025, as reported by omediach.com:
<blockquote>''Z našej strany ide o dlho pripravovanú reakciu na súčasné trendy. Sme komerčná televízia, ktorá hlavne vďaka príjmom z reklamy dokáže produkovať kvalitné vlastné programy, filmy či seriály, obľúbené u našich divákov a diváčok. Zavedením tejto funkcionality dosiahneme odstránenie rozdielu medzi sledovaním televízie a reklám v reálnom čase a pri sledovaní s časovým posunom, ako aj porovnateľné nastavenie, ktoré je aplikované pri iných online platformách.''</blockquote><ref name="omediach" />

== PMÚ investigation ==

In late July 2025, the PMÚ expanded an ongoing administrative proceeding against TV Markíza to include the ad-skipping restrictions.<ref name="omediach" /> In August 2025, the PMÚ opened a separate administrative proceeding against TV Joj.<ref name="omediach" /> On September 30, 2025, the PMÚ publicly announced investigations into both broadcasters.<ref name="broadband-pmu" /><ref name="zive">{{Cite web |url=https://zive.aktuality.sk/clanok/3fJlcym/markiza-a-joj-maju-problem-stat-ich-preveruje-pre-obmedzene-pretacanie-reklam/ |title=Markíza a JOJ majú problém: Štát ich preveruje pre obmedzené pretáčanie reklám |author=Filip Maxa |publisher=Živé.sk |date=September 30, 2025 |access-date=May 15, 2026}}</ref>

The proceedings allege abuse of a dominant market position under Slovak Act No. 187/2021 Coll. on the Protection of Competition.<ref name="slovak-act">{{Cite web |url=https://www.antimon.gov.sk/zakon-o-ochrane-hospodarskej-sutaze/ |title=Zákon o ochrane hospodárskej súťaže |publisher=Protimonopolný úrad Slovenskej republiky |date=2021 |access-date=May 15, 2026}}</ref> If the PMÚ finds a violation, the broadcasters face fines of up to 10 percent of their global turnover.<ref name="antitrust" />

The Telecommunications Union of the Slovak Republic (TUSR), an industry association representing operators, formally welcomed the PMÚ investigation in October 2025.<ref name="techbyte">{{Cite web |url=https://www.techbyte.sk/2025/10/markiza-jojka-klepli-prstoch-zakaz-pretacania-reklam/ |title=Markíze aj JOJ-ke klepli po prstoch: Majú ZRUŠIŤ obmedzenie |publisher=TechByte.sk |date=October 7, 2025 |access-date=May 15, 2026}}</ref>

== Consumer response ==

Subscribers reacted to the restrictions with complaints about what TechByte.sk described as a feeling of "double paying"; paying for IPTV service while being forced to watch advertisements they previously could skip.<ref name="techbyte" />

== Related incidents ==

In June 2022, FTV Prima, a Czech commercial broadcaster, imposed similar ad-skipping restrictions on its IPTV archive service.<ref name="broadband-prima">{{Cite web |url=https://www.broadbandtvnews.com/2022/05/27/czech-prima-to-stop-ad-skipping/ |title=Czech Prima to stop ad-skipping |publisher=Broadband TV News |date=May 27, 2022 |access-date=May 15, 2026}}</ref>
== See also ==

* [[TV Markíza]]
* [[TV Joj]]
* [[Protimonopolný úrad Slovenskej republiky|PMÚ]]
* [[FTV Prima]]

== References ==

{{reflist}}

[[Category:TV Markíza]]
[[Category:TV Joj]]
[[Category:Anti-competitive practice]]
[[Category:Slovakia]]

Enequi Core Industry subscription lockout

2026-05-14T16:46:49Z

Louis: new incident article on enequi mandatory smart saver subscription lockout for quipower core hardware

{{#seo:
|description=Enequi AB requires a 69 SEK/month Smart Saver subscription for Core hardware to function; unsubscribed devices lose most features
}}

{{IncidentCargo
|Company=Enequi
|StartDate=2025
|EndDate=
|Status=Active
|ProductLine=QuiPower
|Product=ENEQUI QuiPower Core Industry,ENEQUI QuiPower Core
|ArticleType=Product
|Type=Planned Obsolescence,Subscription Lockout
|Description=ENEQUI Core hardware requires 69 SEK/month Smart Saver subscription to function; unsubscribed devices lose most features
}}

'''Enequi Core Industry subscription lockout''' refers to the practice by Swedish energy management company [[Enequi|Enequi AB]] of requiring owners of ENEQUI QuiPower Core hardware, including the commercial Core Industry unit, to maintain an active Smart Saver subscription at 69 Swedish kronor per month to retain intelligent energy steering, peak shaving, and tariff optimization. Without the subscription, Enequi states that the hardware loses "most of the features," limiting the device to basic pass-through despite retail prices starting at 15,990 SEK.<ref name="enequi-faq"/><ref name="enequi-smart-saver-en"/><ref name="amss-core-industry"/>

== Background ==

Enequi AB was founded in 2017 and is headquartered in Sollentuna, Sweden.<ref name="prospeo"/> The company's primary product is the QuiPower platform for intelligent energy storage, solar energy storage, and electric vehicle charging.<ref name="smart-city-sweden"/>

The commercial variant, ENEQUI QuiPower Core Industry (article number 300470), is sold through B2B channels and electrical wholesalers including Ahlsell and Senergia at a retail price of 15,990 SEK, discounted from 21,399 SEK.<ref name="amss-core-industry"/> The standard residential ENEQUI Core was priced at 5,995 SEK as of February 2026.<ref name="elinstallatoren"/>

== Subscription announcement ==

In 2025, Enequi introduced a mandatory Smart Saver subscription priced at 69 SEK per month including VAT.<ref name="enequi-smart-saver-en"/><ref name="enequi-smart-saver-se"/> The subscription is managed through the QuiPower app.<ref name="enequi-faq"/> Enequi's FAQ explicitly states:

<blockquote>''Yes, an active Smart Saver subscription is required for your ENEQUI Core to work. The service costs 69 SEK/month.''</blockquote><ref name="enequi-faq"/>

A September 2025 company statement clarified the consequences of non-payment:

<blockquote>''We want to highlight that without the subscription, you will lose most of the features and thus your savings will be limited.''</blockquote><ref name="enequi-smart-saver-en"/>

During 2025, Enequi also offered an alternative tier called QuiPower Plus at 125 SEK per month, which included Frequency Containment Reserve support services.<ref name="senergia-support-monthly"/>

== Consumer impact ==

The mandatory subscription means that hardware purchased for thousands of Swedish kronor loses its primary energy optimization functions if the owner stops paying 69 SEK per month. The device retains physical connectivity to inverters and batteries but can no longer perform intelligent steering, peak shaving, or tariff management.<ref name="enequi-faq"/>

A Swedish Enequi customer reported to Louis Rossmann via email that they received an offer to upgrade their Core Industry unit to a "Core Premium" tier priced at 1,195 SEK or 1,495 SEK upfront, with a warning that portal.enequi.com would be shut down for non-upgraded units and that the update would be irreversible.<ref name="rossmann-email"/> As of May 2026, this claim is supported only by the email report.

== Consumer response ==

Enequi's Trustpilot profile shows exactly one review, with an aggregate score of 3.2 out of 5 stars.<ref name="trustpilot"/>

== Legal context ==

EU Directive 2019/770 on digital content and digital services required Member States to apply its measures from January 1, 2022. The directive defines "goods with digital elements" as tangible items that incorporate digital content or a digital service in such a way that the absence of that digital content would prevent the goods from performing their functions.<ref name="legislation-gov-uk"/><ref name="cooley-directive"/> It requires traders to supply updates necessary to maintain conformity and grants consumers termination rights if modifications negatively impact functionality.<ref name="legislation-gov-uk"/><ref name="hogan-lovells"/>

Sweden transposed the directive into national law through Konsumentköplagen (SFS 2022:260), which took effect on May 1, 2022.<ref name="lagen-nu"/><ref name="lexly-konsumentkop"/> The law extends the reverse burden of proof from 6 months to 2 years and states that digital content is considered an integral part of a hardware purchase unless otherwise agreed.<ref name="lexly-konsumentkop"/> Swedish legal summaries note that if a modification impairs functionality, the consumer has the right to terminate the contract within 30 days.<ref name="lexly-konsumentkop"/>

Konsumentköplagen applies to B2C transactions and grants consumers the right to terminate a contract within 30 days if a post-sale modification impairs the functionality of a good with digital elements.<ref name="lagen-nu"/><ref name="lexly-konsumentkop"/>

== Industry pattern ==

Tesla's Powerwall ecosystem requires an authorized installer using the proprietary Tesla One app to clear Arc Fault lockouts after five alerts within 24 hours; until the lockout is cleared, the hardware does not operate.<ref name="tesla-arc-fault"/>

== See also ==

* [[Enequi]]
* [[Right to Repair]]
* [[Planned Obsolescence]]
* [[Enphase Energy]]
* [[Tesla]]

== References ==

{{reflist}}

<ref name="enequi-faq">{{Cite web |url=https://www.enequi.com/en/faq/ |title=FAQ |website=Enequi |access-date=2026-05-14}}</ref>
<ref name="enequi-smart-saver-en">{{Cite web |url=https://www.enequi.com/en/enequi-smart-saver/ |title=ENEQUI Smart Saver |website=Enequi |access-date=2026-05-14}}</ref>
<ref name="enequi-smart-saver-se">{{Cite web |url=https://www.enequi.com/enequi-smart-saver-prenumeration/ |title=ENEQUI Smart Saver Prenumeration |website=Enequi |access-date=2026-05-14}}</ref>
<ref name="senergia-support-monthly">{{Cite web |url=https://support.senergia.se/sv-SE/support/solutions/articles/101000541002-hur-debiterar-enequi-f%C3%B6r-manadskostnaden- |title=Hur debiterar Enequi för månadskostnaden? |website=Senergia Support |access-date=2026-05-14}}</ref>
<ref name="amss-core-industry">{{Cite web |url=https://www.amss.se/sv/inverters/enequi-quipower-core-industry.html |title=Enequi EMS Core Industry |website=AMSS |access-date=2026-05-14}}</ref>
<ref name="elinstallatoren">{{Cite web |url=https://www.elinstallatoren.se/5-rad-om-att-styra-batteriet-10-kwh-kan-spara-15-000-kronor/ |title=5 råd om att styra batteriet – 10 kWh kan spara 15 000 kronor |website=Elinstallatören |access-date=2026-05-14}}</ref>
<ref name="prospeo">{{Cite web |url=https://prospeo.io/c/enequi |title=Enequi AB |website=Prospeo |access-date=2026-05-14}}</ref>
<ref name="polar-structure">{{Cite web |url=https://polarstructure.se/our-portfolio/enequi/ |title=Enequi |website=Polar Structure |access-date=2026-05-14}}</ref>
<ref name="smart-city-sweden">{{Cite web |url=https://smartcitysweden.com/companies/2120/enequi/ |title=Enequi |website=Smart City Sweden |access-date=2026-05-14}}</ref>
<ref name="rossmann-email">Customer report to Louis Rossmann (email, name withheld at recipient's request).</ref>
<ref name="trustpilot">{{Cite web |url=https://se.trustpilot.com/review/enequi.com |title=Enequi Reviews |website=Trustpilot |access-date=2026-05-14}}</ref>
<ref name="legislation-gov-uk">{{Cite web |url=https://www.legislation.gov.uk/eudr/2019/770/body/data.xht?view=snippet&wrap=true |title=Directive (EU) 2019/770 on certain aspects concerning contracts for the supply of digital content and digital services |website=legislation.gov.uk |access-date=2026-05-14}}</ref>
<ref name="cooley-directive">{{Cite web |url=https://products.cooley.com/2022/06/23/productwise-bitesize-digital-content-and-digital-services-directive-2019-770/ |title=Productwise Bitesize: Digital Content and Digital Services Directive 2019/770 |website=Cooley |date=2022-06-23 |access-date=2026-05-14}}</ref>
<ref name="hogan-lovells">{{Cite web |url=https://www.hoganlovells.com/en/publications/directive-for-the-supply-of-digital-content-and-digital-services-to-consumers-spain-update |title=Directive for the supply of digital content and digital services to consumers |website=Hogan Lovells |access-date=2026-05-14}}</ref>
<ref name="lagen-nu">{{Cite web |url=https://lagen.nu/2022:260 |title=Konsumentköplagen (2022:260) |website=lagen.nu |access-date=2026-05-14}}</ref>
<ref name="lexly-konsumentkop">{{Cite web |url=https://lexly.se/om-oss/aktuellt/sa-paverkar-den-nya-konsumentkoplagen-dig-som-konsument |title=Så påverkar den nya konsumentköplagen dig som konsument |website=Lexly |access-date=2026-05-14}}</ref>
<ref name="tesla-arc-fault">{{Cite web |url=https://energylibrary.tesla.com/docs/Public/EnergyStorage/Powerwall/3/DeviceSetupGuide/en-us/GUID-73A45665-0B05-4235-A6A5-9020A46E4B61.html |title=Arc Fault Errors |website=Tesla |access-date=2026-05-14}}</ref>


[[Category:Enequi]]
[[Category:Subscription Lockout]]
[[Category:Planned Obsolescence]]
[[Category:2025 incidents]]

Enequi

2026-05-14T16:45:30Z

Louis: new article on swedish energy company requiring mandatory smart saver subscription for quipower core hardware

{{#seo:
|description=Swedish energy company requiring mandatory Smart Saver subscription for QuiPower Core hardware; unsubscribed devices lose most features
}}




{{CompanyCargo
|Founded=2017
|Industry=Energy management,Renewable energy
|Logo=
|ParentCompany=
|CompanyAlias=
|Type=Private
|Website=https://www.enequi.com/
|Description=Requires mandatory Smart Saver subscription for Core hardware to function; unsubscribed devices lose most energy optimization features
}}

'''Enequi AB''' is a Swedish energy company that requires owners of ENEQUI QuiPower Core hardware to pay a mandatory Smart Saver subscription of 69 Swedish kronor per month. Without the subscription, Enequi states that the hardware loses "most of the features."<ref name="enequi-faq"/><ref name="enequi-smart-saver-en"/> The company was founded in 2017 and is headquartered in Sollentuna, Sweden. It provides energy storage systems for private and commercial properties, with solutions for electrical installation, metering, and industrial automation.<ref name="prospeo"/><ref name="polar-structure"/>

== Consumer-impact summary ==

* Enequi requires a mandatory Smart Saver subscription at 69 SEK per month for all ENEQUI Core hardware, including the residential Core and commercial Core Industry units. Without the subscription, the device loses most optimization features.<ref name="enequi-faq"/><ref name="enequi-smart-saver-en"/>
* Konsumentköplagen 2022:260 grants consumers the right to terminate a contract within 30 days if a post-sale modification impairs the functionality of a good with digital elements. The statute applies to B2C transactions.<ref name="lagen-nu"/><ref name="lexly-konsumentkop"/>

== Background ==

Enequi AB was founded in 2017 and is headquartered at Kung Hans väg 3, 192 68 Sollentuna, Sweden. Enequi employs between 11 and 20 people and reported estimated annual revenue of approximately $1,283,325.<ref name="prospeo"/> Enequi is backed by investor Polar Structure<ref name="polar-structure"/> and provides energy storage systems for private and commercial properties, with solutions for electrical installation, metering, and industrial automation.<ref name="polar-structure"/>

== Incidents ==

=== Enequi Core Industry subscription lockout ===
{{Main|Enequi Core Industry subscription lockout}}
Enequi requires mandatory ongoing payment of 69 SEK per month for Core hardware to function as advertised.<ref name="enequi-faq"/> Hardware purchased for up to 21,399 SEK loses most optimization features if the owner unsubscribes.<ref name="amss-core-industry"/><ref name="enequi-faq"/><ref name="enequi-smart-saver-en"/>


== Products ==

* [[ENEQUI QuiPower Core]]. Residential energy management hardware that connects to batteries, solar inverters, and EV chargers via RS485, CAN, Modbus TCP, Ethernet, USB, and Wi-Fi.
* [[ENEQUI QuiPower Core Industry]]. Commercial-grade variant (article number 300470) sold through B2B wholesalers for industrial and agricultural energy management.
* [[ENEQUI QuiPower Core 2nd Generation]]. Residential successor with a built-in network switch, HAN port for smart meter reading, and dual Wi-Fi antennas.
* [[ENEQUI QuiPower Node]]. Hardware for intelligent load and lighting control, operating stand-alone or networked for backup during power outages.

== See also ==

* [[Right to Repair]]
* [[Planned Obsolescence]]
* [[Enphase Energy]]
* [[Tesla]]

== References ==

{{reflist}}

<ref name="enequi-faq">{{Cite web |url=https://www.enequi.com/en/faq/ |title=FAQ |website=Enequi |access-date=2026-05-14}}</ref>
<ref name="senergia-core-industry">{{Cite web |url=https://b2b.senergia.se/enequi-quipower-core-industry |title=ENEQUI QuiPower Core Industry |website=Senergia |access-date=2026-05-14}}</ref>
<ref name="amss-core-industry">{{Cite web |url=https://www.amss.se/sv/inverters/enequi-quipower-core-industry.html |title=Enequi EMS Core Industry |website=AMSS |access-date=2026-05-14}}</ref>
<ref name="prospeo">{{Cite web |url=https://prospeo.io/c/enequi |title=Enequi AB |website=Prospeo |access-date=2026-05-14}}</ref>
<ref name="polar-structure">{{Cite web |url=https://polarstructure.se/our-portfolio/enequi/ |title=Enequi |website=Polar Structure |access-date=2026-05-14}}</ref>
<ref name="lagen-nu">{{Cite web |url=https://lagen.nu/2022:260 |title=Konsumentköplagen (2022:260) |website=lagen.nu |access-date=2026-05-14}}</ref>
<ref name="lexly-konsumentkop">{{Cite web |url=https://lexly.se/om-oss/aktuellt/sa-paverkar-den-nya-konsumentkoplagen-dig-som-konsument |title=Så påverkar den nya konsumentköplagen dig som konsument |website=Lexly |access-date=2026-05-14}}</ref>
<ref name="enequi-smart-saver-en">{{Cite web |url=https://www.enequi.com/en/enequi-smart-saver/ |title=ENEQUI Smart Saver |website=Enequi |access-date=2026-05-14}}</ref>

[[Category:Enequi]]
[[Category:Right to Repair]]
[[Category:Planned Obsolescence]]

Maxon

2026-05-14T12:13:31Z

Louis: Update: Remove Autograph section to focus on highest-severity incidents only

{{#seo:description=Maxon eliminates perpetual licenses for acquired products including ZBrush, Red Giant, and Forger, forcing subscriptions and locking users out of proprietary files.}}

{{CompanyCargo
|Founded=1985
|Industry=Software,3D Modeling,Animation,Visual Effects
|Logo=
|ParentCompany=Nemetschek Group
|CompanyAlias=Maxon Computer GmbH
|Type=Subsidiary
|Website=https://maxon.net/
|Description=Eliminates perpetual licenses for acquired products and forces subscriptions; discontinued Forger app, locking users out of proprietary files.
}}

'''Maxon''' discontinued the iPad sculpting app [[Forger]] in September 2025, leaving subscribers unable to export proprietary files when subscriptions lapsed.<ref name="forger-cgchannel">{{Cite web |url=https://www.cgchannel.com/2025/07/maxon-discontinues-forger/ |title=Maxon discontinues Forger |date=2025-07 |website=CG Channel |access-date=2026-05-13}}</ref><ref name="forger-manual">{{Cite web |url=https://learn.forger.app/ios-manual/licensing/ |title=Licensing - Forger Manual |website=Maxon |access-date=2026-05-13}}</ref> The company has also eliminated perpetual licenses for [[ZBrush]] and [[Red Giant]], moving both to subscription-only models.<ref name="zbrush2024-cgchannel">{{Cite web |url=https://www.cgchannel.com/2023/11/maxon-releases-zbrush-2024/ |title=Maxon releases ZBrush 2024 |date=2023-11-16 |website=CG Channel |access-date=2026-05-13}}</ref><ref name="redgiant-cgchannel">{{Cite web |url=https://www.cgchannel.com/2021/09/maxon-ends-perpetual-licences-of-red-giant-products/ |title=Maxon ends perpetual licences of Red Giant products |date=2021-09-17 |website=CG Channel |access-date=2026-05-13}}</ref>

== Consumer-impact summary ==

* Maxon acquired Forger in 2021 and discontinued it on September 10, 2025. The app was removed from the App Store, and existing subscribers who let their subscriptions lapse lost the ability to save or export proprietary files.<ref name="forger-manual" /> ZBrush for iPad, the replacement Maxon recommended, did not natively support Forger's file format.<ref name="forger-faq">{{Cite web |url=https://www.maxon.net/en/forger-eos-faq |title=Forger End of Sale (EoS) FAQ |website=Maxon |access-date=2026-05-13}}</ref> ZBrush for iPad cost $9.99 per month or $89.99 per year, roughly six times Forger's previous price of $1.99 per month or $14.99 per year.<ref name="forger-cgchannel" />
* Maxon acquired Pixologic, the developer of ZBrush, in December 2021.<ref name="zbrush-faq" /> In November 2023, Maxon released ZBrush 2024 exclusively via subscription at $39 per month or $359 per year, eliminating perpetual licenses that Pixologic had previously sold with free feature upgrades.<ref name="zbrush2024-cgchannel" />
* In September 2021, Maxon discontinued perpetual licenses for [[Red Giant]] plugin suites without advance announcement, leaving only subscription options for new versions of Trapcode Suite, VFX Suite, and Magic Bullet Suite.<ref name="redgiant-cgchannel">{{Cite web |url=https://www.cgchannel.com/2021/09/maxon-ends-perpetual-licences-of-red-giant-products/ |title=Maxon ends perpetual licences of Red Giant products |date=2021-09-17 |website=CG Channel |access-date=2026-05-13}}</ref>
== Incidents ==

=== Maxon Forger discontinuation and subscription file lockout ===
{{Main|Maxon Forger discontinuation and subscription file lockout}}

Maxon acquired Forger, an iPad sculpting app originally released in 2011, in March 2021.<ref name="forger-acquisition-cgchannel">{{Cite web |url=https://www.cgchannel.com/2021/03/maxon-acquires-forger/ |title=Maxon acquires forger |date=2021-03 |website=CG Channel |access-date=2026-05-13}}</ref> On September 10, 2025, Maxon placed Forger into what it termed "limited maintenance mode." The app was removed from the App Store, and no new updates or bug fixes were released.<ref name="forger-maxon">{{Cite web |url=https://www.maxon.net/en/article/forger-entering-limited-maintenance-mode |title=Forger Entering Limited Maintenance Mode |website=Maxon |access-date=2026-05-13}}</ref> Existing subscribers could continue using the app until the end of their current subscription term, but could not renew after September 10, 2025.<ref name="forger-maxon" />

The free version of Forger imposed a three-document save limit and disabled all exporting, including sending files to Cinema 4D. According to Maxon's own documentation, files saved while a subscription was active could be opened in the free version, but could not be saved or exported.<ref name="forger-manual" /> Forger's native file format was not supported in ZBrush for iPad, the replacement Maxon recommended. Users who did not export their work in .goz or .obj format before their subscription expired would be unable to open their Forger files in ZBrush for iPad or export them to other formats.<ref name="forger-faq" />

ZBrush for iPad cost $9.99 per month or $89.99 per year as of July 2025, compared to Forger's previous price of $1.99 per month or $14.99 per year.<ref name="forger-cgchannel" />

=== ZBrush perpetual license elimination ===

Maxon finalized its acquisition of Pixologic, the developer of ZBrush, on December 29, 2021.<ref name="zbrush-faq">{{Cite web |url=https://www.maxon.net/en/zbrush-acquisition-faq |title=ZBrush Acquisition FAQ |website=Maxon |access-date=2026-05-13}}</ref> At that time, Maxon altered the end-user license agreement for new perpetual license purchases. Customers who bought perpetual licenses after December 29, 2021, would receive only bug fixes, not free feature upgrades. Customers who purchased perpetual licenses between December 30, 2020 and December 29, 2021 were grandfathered with a one-year update window.<ref name="zbrush-faq" />

In November 2023, Maxon released ZBrush 2024. The release was available exclusively via subscription. Perpetual licenses were no longer offered for the new version, and holders of existing perpetual licenses could not upgrade to ZBrush 2024.<ref name="zbrush2024-cgchannel" /> Subscription pricing was set at $39 per month or $359 per year.<ref name="zbrush2024-cgchannel" /> New features introduced in ZBrush 2024, including the Repeat to Similar system and Cinema 4D noise integrations, were available only to subscribers.<ref name="zbrush2024-cgchannel" />

=== Red Giant perpetual license discontinuation ===

Maxon merged with Red Giant, a developer of visual effects and color grading plugins. The merger added Trapcode Suite, VFX Suite, Magic Bullet Suite, Universe, and PluralEyes to Maxon's product portfolio.<ref name="redgiant-cgchannel" />

In September 2021, Maxon discontinued perpetual licenses for Trapcode Suite, VFX Suite, and Magic Bullet Suite without advance announcement. CG Channel reported that the change was only apparent when perpetual license purchase options vanished from the Maxon online store. When contacted, Maxon confirmed that it had "decided to not offer a perpetual version of the individual suites."<ref name="redgiant-cgchannel" /> Perpetual licenses of the previous versions remained available for $999, but the latest versions were accessible only via Red Giant Complete subscriptions at $79 per month or $599 per year, or via Maxon One subscriptions at $149 per month or $1,199 per year.<ref name="redgiant-cgchannel" />

== Products ==

* [[Cinema 4D]]
* ZBrush
* Red Giant plugin suites (Trapcode Suite, VFX Suite, Magic Bullet Suite, Universe, PluralEyes)
* [[Redshift]] renderer
* Forger (discontinued September 2025)
* [[Maxon One]] subscription bundle

== See also ==

* [[Subscription software licensing]]
* [[Digital rights management]]

== References ==

{{reflist}}



[[Category:Maxon]]
[[Category:Software Companies]]
[[Category:Subscription Licensing]]

Maxon

2026-05-14T12:11:26Z

Louis: New article: Maxon Company page covering subscription licensing controversies and product discontinuations (via pipeline)

{{#seo:description=Maxon eliminates perpetual licenses for acquired products including ZBrush, Red Giant, and Forger, forcing subscriptions and locking users out of legacy files.}}

{{CompanyCargo
|Founded=1985
|Industry=Software,3D Modeling,Animation,Visual Effects
|Logo=
|ParentCompany=Nemetschek Group
|CompanyAlias=Maxon Computer GmbH
|Type=Subsidiary
|Website=https://maxon.net/
|Description=Eliminates perpetual licenses for acquired products and forces subscriptions; discontinued Forger app, locking users out of proprietary files.
}}

'''Maxon''' discontinued the iPad sculpting app [[Forger]] in September 2025, leaving subscribers unable to export proprietary files when subscriptions lapsed.<ref name="forger-cgchannel">{{Cite web |url=https://www.cgchannel.com/2025/07/maxon-discontinues-forger/ |title=Maxon discontinues Forger |date=2025-07 |website=CG Channel |access-date=2026-05-13}}</ref><ref name="forger-manual">{{Cite web |url=https://learn.forger.app/ios-manual/licensing/ |title=Licensing - Forger Manual |website=Maxon |access-date=2026-05-13}}</ref> The company has also eliminated perpetual licenses for [[ZBrush]] and [[Red Giant]], moving both to subscription-only models.<ref name="zbrush2024-cgchannel">{{Cite web |url=https://www.cgchannel.com/2023/11/maxon-releases-zbrush-2024/ |title=Maxon releases ZBrush 2024 |date=2023-11-16 |website=CG Channel |access-date=2026-05-13}}</ref><ref name="redgiant-cgchannel">{{Cite web |url=https://www.cgchannel.com/2021/09/maxon-ends-perpetual-licences-of-red-giant-products/ |title=Maxon ends perpetual licences of Red Giant products |date=2021-09-17 |website=CG Channel |access-date=2026-05-13}}</ref>

== Consumer-impact summary ==

* Maxon acquired Forger in 2021 and discontinued it on September 10, 2025. The app was removed from the App Store, and existing subscribers who let their subscriptions lapse lost the ability to save or export proprietary files.<ref name="forger-manual" /> ZBrush for iPad, the replacement Maxon recommended, did not natively support Forger's file format.<ref name="forger-faq">{{Cite web |url=https://www.maxon.net/en/forger-eos-faq |title=Forger End of Sale (EoS) FAQ |website=Maxon |access-date=2026-05-13}}</ref> ZBrush for iPad cost $9.99 per month or $89.99 per year, roughly six times Forger's previous price of $1.99 per month or $14.99 per year.<ref name="forger-cgchannel" />
* Maxon acquired Pixologic, the developer of ZBrush, in December 2021.<ref name="zbrush-faq" /> In November 2023, Maxon released ZBrush 2024 exclusively via subscription at $39 per month or $359 per year, eliminating perpetual licenses that Pixologic had previously sold with free feature upgrades.<ref name="zbrush2024-cgchannel" />
* In September 2021, Maxon discontinued perpetual licenses for [[Red Giant]] plugin suites without advance announcement, leaving only subscription options for new versions of Trapcode Suite, VFX Suite, and Magic Bullet Suite.<ref name="redgiant-cgchannel">{{Cite web |url=https://www.cgchannel.com/2021/09/maxon-ends-perpetual-licences-of-red-giant-products/ |title=Maxon ends perpetual licences of Red Giant products |date=2021-09-17 |website=CG Channel |access-date=2026-05-13}}</ref>
* In June 2025, Maxon acquired the team behind Autograph, a motion graphics application, as developer Left Angle shut down. The company's website and related channels went offline.<ref name="autograph-maxon">{{Cite web |url=https://www.maxon.net/en/article/autograph-acquisition |title=Maxon Welcomes Autograph Team Following Left Angle Transition |date=2025-06-05 |website=Maxon |access-date=2026-05-13}}</ref><ref name="autograph-80lv">{{Cite web |url=https://80.lv/articles/maxon-welcomes-autograph-team-following-left-angle-s-closure |title=Autograph Team Joins Maxon As Left Angle Shuts Down |date=2025-06-06 |website=80.lv |access-date=2026-05-13}}</ref> User reports indicated that license validation servers also became inaccessible, preventing some license holders from opening the software.<ref name="autograph-reddit">{{Cite web |url=https://www.reddit.com/r/MotionDesign/comments/1l4ofkf/maxon_acquires_leftangle_company_behind_the/ |title=Maxon acquires LeftAngle, company behind the Autograph software. Locks out customers. |website=Reddit |date=2025-06-05 |access-date=2026-05-13}}</ref>

== Incidents ==

=== Maxon Forger discontinuation and subscription file lockout ===
{{Main|Maxon Forger discontinuation and subscription file lockout}}

Maxon acquired Forger, an iPad sculpting app originally released in 2011, in March 2021.<ref name="forger-acquisition-cgchannel">{{Cite web |url=https://www.cgchannel.com/2021/03/maxon-acquires-forger/ |title=Maxon acquires forger |date=2021-03 |website=CG Channel |access-date=2026-05-13}}</ref> On September 10, 2025, Maxon placed Forger into what it termed "limited maintenance mode." The app was removed from the App Store, and no new updates or bug fixes were released.<ref name="forger-maxon">{{Cite web |url=https://www.maxon.net/en/article/forger-entering-limited-maintenance-mode |title=Forger Entering Limited Maintenance Mode |website=Maxon |access-date=2026-05-13}}</ref> Existing subscribers could continue using the app until the end of their current subscription term, but could not renew after September 10, 2025.<ref name="forger-maxon" />

The free version of Forger imposed a three-document save limit and disabled all exporting, including sending files to Cinema 4D. According to Maxon's own documentation, files saved while a subscription was active could be opened in the free version, but could not be saved or exported.<ref name="forger-manual" /> Forger's native file format was not supported in ZBrush for iPad, the replacement Maxon recommended. Users who did not export their work in .goz or .obj format before their subscription expired would be unable to open their Forger files in ZBrush for iPad or export them to other formats.<ref name="forger-faq" />

ZBrush for iPad cost $9.99 per month or $89.99 per year as of July 2025, compared to Forger's previous price of $1.99 per month or $14.99 per year.<ref name="forger-cgchannel" />

=== ZBrush perpetual license elimination ===

Maxon finalized its acquisition of Pixologic, the developer of ZBrush, on December 29, 2021.<ref name="zbrush-faq">{{Cite web |url=https://www.maxon.net/en/zbrush-acquisition-faq |title=ZBrush Acquisition FAQ |website=Maxon |access-date=2026-05-13}}</ref> At that time, Maxon altered the end-user license agreement for new perpetual license purchases. Customers who bought perpetual licenses after December 29, 2021, would receive only bug fixes, not free feature upgrades. Customers who purchased perpetual licenses between December 30, 2020 and December 29, 2021 were grandfathered with a one-year update window.<ref name="zbrush-faq" />

In November 2023, Maxon released ZBrush 2024. The release was available exclusively via subscription. Perpetual licenses were no longer offered for the new version, and holders of existing perpetual licenses could not upgrade to ZBrush 2024.<ref name="zbrush2024-cgchannel" /> Subscription pricing was set at $39 per month or $359 per year.<ref name="zbrush2024-cgchannel" /> New features introduced in ZBrush 2024, including the Repeat to Similar system and Cinema 4D noise integrations, were available only to subscribers.<ref name="zbrush2024-cgchannel" />

=== Red Giant perpetual license discontinuation ===

Maxon merged with Red Giant, a developer of visual effects and color grading plugins. The merger added Trapcode Suite, VFX Suite, Magic Bullet Suite, Universe, and PluralEyes to Maxon's product portfolio.<ref name="redgiant-cgchannel" />

In September 2021, Maxon discontinued perpetual licenses for Trapcode Suite, VFX Suite, and Magic Bullet Suite without advance announcement. CG Channel reported that the change was only apparent when perpetual license purchase options vanished from the Maxon online store. When contacted, Maxon confirmed that it had "decided to not offer a perpetual version of the individual suites."<ref name="redgiant-cgchannel" /> Perpetual licenses of the previous versions remained available for $999, but the latest versions were accessible only via Red Giant Complete subscriptions at $79 per month or $599 per year, or via Maxon One subscriptions at $149 per month or $1,199 per year.<ref name="redgiant-cgchannel" />

=== Autograph acquisition and server shutdown ===

In June 2025, the team behind Autograph, a motion graphics application developed by Left Angle, joined Maxon.<ref name="autograph-maxon" /> Concurrent with the acquisition, Left Angle wound down its business operations. A message from Left Angle posted on Maxon's website stated that "our website and all related channels will go offline."<ref name="autograph-maxon" /> Industry coverage from 80.lv noted that the acquisition details for the Autograph software itself remained unclear.<ref name="autograph-80lv" />

A Reddit post in r/MotionDesign reported that users were unable to access Autograph after the acquisition because Left Angle's license validation servers had gone down during the business closure.<ref name="autograph-reddit" /> Alexandre and Francois, co-founders of Left Angle, posted a response in the same thread:

<blockquote>''Let us say that it has been killing us that your service was interrupted when our license servers went down during the closing of our business. Let us also say that Maxon did not shut down our license server and discontinue the software -- they stepped into a difficult situation to help preserve a future for us.''</blockquote><ref name="autograph-reddit" />

== Products ==

* [[Cinema 4D]]
* ZBrush
* Red Giant plugin suites (Trapcode Suite, VFX Suite, Magic Bullet Suite, Universe, PluralEyes)
* [[Redshift]] renderer
* Forger (discontinued September 2025)
* Autograph
* [[Maxon One]] subscription bundle

== See also ==

* [[Subscription software licensing]]
* [[Digital rights management]]

== References ==

{{reflist}}



[[Category:Maxon]]
[[Category:Software Companies]]
[[Category:Subscription Licensing]]

Maxon Forger discontinuation and subscription file lockout

2026-05-13T23:22:43Z

Louis: New article: Maxon Forger discontinuation and subscription file lockout (via pipeline)

{{#seo:description=Maxon discontinued Forger and stopped subscription renewals, leaving subscribers unable to export or save project files stored in a native format unsupported by any other application.}}

{{IncidentCargo
|Company=Maxon
|StartDate=2025-07-04
|EndDate=2025-09-10
|Status=Resolved
|ProductLine=
|Product=Forger
|ArticleType=Product
|Type=Planned Obsolescence,Data Access Restriction
|Description=Maxon discontinued its iPad sculpting app Forger and stopped subscription renewals, causing subscribers who lost export and save access to project files stored in a native format unsupported by any other application
}}

'''Maxon Forger''' was a 3D sculpting application for iPad that [[Maxon]] discontinued on September 10, 2025.<ref name="maxon-maintenance">{{Cite web |url=https://www.maxon.net/en/article/forger-entering-limited-maintenance-mode |title=Forger Entering Limited Maintenance Mode |date=July 4, 2025 |publisher=Maxon |access-date=May 13, 2026}}</ref> When the app was removed from the [[Apple App Store]], existing subscribers could not renew their subscriptions.<ref name="maxon-maintenance" /> Upon lapse, the application reverted to a restricted free tier that allowed users to open existing project files but blocked both saving changes and exporting geometry to standard formats.<ref name="forger-licensing">{{Cite web |url=https://learn.forger.app/ios-manual/licensing/ |title=Forger for iOS Reference Manual: Licensing |publisher=Maxon |access-date=May 13, 2026}}</ref> Because Forger stored projects in a native file format that no other application supports, users who had not exported their work before their subscription ended could not migrate their data to another program.<ref name="maxon-faq">{{Cite web |url=https://www.maxon.net/en/forger-eos-faq |title=Forger End of Sale (EoS) FAQ |publisher=Maxon |access-date=May 13, 2026}}</ref><ref name="digitalproduction">{{Cite web |url=https://digitalproduction.com/2025/07/08/maxon-sunsets-forger-ipad-sculptors-get-the-maintenance-axe/ |title=Maxon Sunsets Forger: iPad Sculptors Get the (Maintenance) Axe |author=Bela Beier |date=July 8, 2025 |publisher=Digital Production |access-date=May 13, 2026}}</ref>

== Background ==

Forger was created by VFX TD Javier Edo and first released in 2011 as one of the earliest dedicated 3D sculpting apps for iPad.<ref name="cgchannel-discontinues">{{Cite web |url=https://www.cgchannel.com/2025/07/maxon-discontinues-forger/ |title=Maxon discontinues Forger |author=Jim Thacker |date=July 6, 2025 |publisher=CG Channel |access-date=May 13, 2026}}</ref> Maxon acquired the application in March 2021.<ref name="cgchannel-acquires">{{Cite web |url=https://www.cgchannel.com/2021/03/maxon-acquires-forger/ |title=Maxon acquires Forger |publisher=CG Channel |date=March 2021 |access-date=May 13, 2026}}</ref> After the acquisition, Maxon added a freemium option with subscription tiers.<ref name="slatepad">{{Cite web |url=https://slatepad.org/forger-ipad-discontinued-zbrush/ |title=Forger for iPad Is Being Discontinued, Pushing Sculptors Toward ZBrush |author=Riley Hill |date=July 12, 2025 |publisher=SlatePad |access-date=May 13, 2026}}</ref>

The free tier imposed two restrictions that became consequential after discontinuation. Users could save no more than three scenes; starting a fourth required deleting an existing file or subscribing.<ref name="forger-licensing" /> Exporting any scene also required an active subscription, including exports to [[Cinema 4D|Cinema 4D]].<ref name="forger-licensing" /> The standalone subscription cost $1.99 per month or $14.99 per year.<ref name="cgchannel-discontinues" /> Forger was also included in Maxon One bundles.<ref name="forger-licensing" />

Maxon's own reference manual described the subscription-lapse behavior explicitly:

<blockquote>''Files that were saved while a subscription was active can be opened and edited, but cannot be saved in Free mode.''</blockquote><ref name="forger-licensing" />

This meant that when a subscription expired, a user could still view existing projects and make temporary edits, but could not save modifications or export the geometry to standard interoperable formats.<ref name="forger-licensing" />

== Discontinuation and file access restrictions ==

On July 4, 2025, Maxon announced that Forger would enter "Limited Maintenance Mode" on September 10, 2025.<ref name="maxon-maintenance" /> From that date forward, the app would no longer be available for purchase or download on the App Store and subscription renewals would no longer be possible.<ref name="maxon-maintenance" /> The company stated there would no longer be any updates, bug fixes, or changes to the software.<ref name="maxon-faq" /> Existing subscribers could continue using the app until the end of their then-current billing period, and technical support would remain available until September 10, 2025 or the end of the subscription term, whichever came first.<ref name="maxon-faq" />

The cutoff prevented any subscriber from maintaining an active subscription past their existing billing period.<ref name="maxon-maintenance" /> Maxon's announcement explicitly stated that "Subscription licenses of Forger can be renewed only until September 10th, 2025."<ref name="maxon-maintenance" /> RevenueCat, a subscription-management platform, confirmed that when a developer removes an auto-renewable subscription from sale in App Store Connect, "existing subscribers won't be able to renew this subscription" and the entitlement expires at the end of the current paid period.<ref name="revenuecat">{{Cite web |url=https://community.revenuecat.com/general-questions-7/is-it-safe-to-delete-subscriptions-in-app-store-connect-5817 |title=Is it safe to delete subscriptions in App Store Connect? |publisher=RevenueCat Community |date=January 30, 2025 |access-date=May 13, 2026}}</ref>

Once a subscriber's Forger entitlement lapsed, the app reverted to the free tier. The user retained visual access to locally stored project files but lost the ability to export them.<ref name="forger-licensing" /> Because the native Forger file format is unsupported in ZBrush, Cinema 4D, or any third-party application, a user who had not exported their work before the subscription ended had no migration path.<ref name="maxon-faq" /><ref name="digitalproduction" />

=== Maxon's response ===

Maxon directed Forger users to ZBrush for iPad as the replacement.<ref name="maxon-faq" /> ZBrush for iPad launched on September 10, 2024, exactly one year before the Forger cutoff.<ref name="cgchannel-zbrush">{{Cite web |url=https://www.cgchannel.com/2024/09/maxon-releases-zbrush-for-ipad/ |title=Maxon releases ZBrush for iPad |publisher=CG Channel |date=September 2024 |access-date=May 13, 2026}}</ref> ZBrush for iPad costs $9.99 per month or $89.99 per year, compared to Forger's $14.99 annual subscription.<ref name="cgchannel-discontinues" /> Maxon merged the Forger development team into the ZBrush for iPad team and stated that the consolidation would allow the company to:
<blockquote>''leverage Forger's history on iPad and ZBrush's sculpting capabilities to introduce more features and innovations.''</blockquote><ref name="maxon-faq" />

Maxon offered no migration path for Forger format files. The company's FAQ stated that Forger format files are "not specifically supported in ZBrush" and advised users to export OBJ or GoZ files.<ref name="maxon-faq" /> Press coverage noted that layers, mesh data, and certain effects might not transfer cleanly, particularly for complex projects.<ref name="digitalproduction" />

A Reddit user on r/ZBrush reported in September 2024 that the app "crashes every few minutes, it doesn't even get a chance to auto save."<ref name="reddit-crash">{{Cite web |url=https://www.reddit.com/r/ZBrush/comments/1fjdy5g/ipadpro_6th_gen_crashing_constantly/ |title=iPadPro 6th gen crashing constantly |publisher=Reddit r/ZBrush |date=September 2024 |access-date=May 13, 2026}}</ref> Maxon's April 15, 2026 release notes for ZBrush 2026.2.0 acknowledged that crashes on document export, welding points, and ZModeler preset deletion had been ongoing issues that the update addressed.<ref name="zbrush-release">{{Cite web |url=https://support.maxon.net/hc/en-us/articles/15780513877788-ZBrush-2026-2-0-Release-Notes-April-15-2026 |title=ZBrush 2026.2.0 Release Notes (April 15, 2026) |publisher=Maxon |date=April 15, 2026 |access-date=May 13, 2026}}</ref>

== Consumer response ==

On October 8, 2023, a Reddit user in r/sculpting articulated the same frustration that would later affect subscribers after the 2025 discontinuation, asking for alternatives after discovering that Forger would not allow export without payment.<ref name="reddit-sculpting">{{Cite web |url=https://www.reddit.com/r/sculpting/comments/173a8wp/3d_app_for_free/ |title=3D app for free? |publisher=Reddit r/sculpting |date=October 8, 2023 |access-date=May 13, 2026}}</ref>

Industry press coverage highlighted the forced migration and price increase. Digital Production's article on July 8, 2025, stated that "Maxon has now nailed the Forger coffin shut" and warned that "Forger's native file format is not supported anywhere else, not even in Cinema 4D."<ref name="digitalproduction" /> SlatePad framed the transition as a push toward ZBrush.<ref name="slatepad">{{Cite web |url=https://slatepad.org/forger-ipad-discontinued-zbrush/ |title=Forger for iPad Is Being Discontinued, Pushing Sculptors Toward ZBrush |author=Riley Hill |date=July 12, 2025 |publisher=SlatePad |access-date=May 13, 2026}}</ref>

== References ==
{{reflist}}

[[Category:Maxon]]
[[Category:Forger]]
[[Category:Software Discontinuation]]
[[Category:Subscription Trap]]
[[Category:Data Access Restriction]]
[[Category:Planned Obsolescence]]
[[Category:Right to Repair]]

Bambu Lab Authorization Control System

2026-05-11T18:20:05Z

Louis:

{{IncidentCargo
|Company=Bambu Lab
|StartDate=2025-01-16
|Status=Active
|Type=Post-purchase terms change
|Description=January 2025 firmware change restricted third-party slicers; April 2026 private cease-and-desist against AGPL fork maintainer Pawel Jarczak.
}}

On January 16, 2025, the 3D-printer manufacturer '''[[Bambu Lab]]''' announced that future firmwares for its 3D printers would introduce an authorization & authentication mechanism for printer connection & control, [[Deceptive language frequently used against consumers|in the name of security]].<ref name="firmware-update-introducing-new-authorization-control-system-2">{{Cite web |last=Bambu Kidd |date=2025-01-16 |title=Firmware Update Introducing New Authorization Control System |url=https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/ |url-status=live |archive-url=https://ghostarchive.org/archive/qwL63 |archive-date=2026-03-07 |website=[[Bambu Lab]] Blog}}</ref> The change restricted the use of third-party accessories & slicers such as Panda Touch & OrcaSlicer, & it gated print initiation, motion control, fan & hotend control, AMS configuration, calibrations, remote video, & firmware upgrade behind a Bambu-issued authentication path.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> Bambu Lab also publishes its own slicer, [https://github.com/bambulab/BambuStudio Bambu Studio], under the [[GNU Affero General Public License|AGPL-3.0]],<ref name="bambustudio-license">{{Cite web |title=BambuStudio LICENSE (AGPL-3.0 verbatim) |url=https://github.com/bambulab/BambuStudio/blob/master/LICENSE |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref> while its [[Terms of Service|Terms of Use]] § 3.4 forbid users to modify, copy, reverse engineer, or create derivatives of "the Product."<ref name=":2">{{Cite web |date=2024-04-24 |title=Terms of Use |url=https://bambulab.com/en-us/policies/terms |url-status=live |archive-url=https://ghostarchive.org/archive/vPu9I |archive-date=2026-03-09 |access-date=2025-05-01 |website=[[Bambu Lab]]}}</ref> In April 2026, Bambu Lab sent a private cease-and-desist demand to a Polish community fork maintainer, Pawel Jarczak, who had restored direct printer control on top of that AGPL source; on May 7, 2026, Bambu Lab published a blog post recharacterizing the dispute as "impersonation" through "falsified identity metadata" rather than as a question about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref><ref name="jarczak-readme">{{Cite web |last=Jarczak |first=Pawel |title=OrcaSlicer-bambulab — This is the end…. |url=https://github.com/jarczakpawel/OrcaSlicer-bambulab |url-status=live |archive-url=https://web.archive.org/web/20260430001537/https://github.com/jarczakpawel/OrcaSlicer-bambulab |archive-date=2026-04-30 |access-date=2026-05-04 |website=[[GitHub]]}}</ref>

==Controversy regarding firmware updates==
[[File:Bambu tos screenshot.png|alt=bambu terms stating print jobs may not function properly if update is not performed to new firmware which is highly limiting. |thumb|Bambu terms regarding printer functionality & potential for disrupted print jobs if users do not update to a new firmware that radically restricts the autonomy of the owner of the printer]]

===Potential for remote disabling of printers===
A concern raised by the community revolves around the wording in Bambu Lab's [[Terms of Service]] (ToS) and firmware update announcements. Critics and users argue that the phrasing leaves open the possibility for the manufacturer to [[Remote disabling|remotely disable]] printers that are not updated to the latest firmware. Specifically, Bambu Lab's ToS warns that printers may block new print jobs if updates are not applied,<ref name=":2" /> which some users interpret as a potential pathway for forced obsolescence.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> While defenders of Bambu Lab point out that offline modes such as SD-card printing and [[wikipedia:Local_area_network|LAN]]-only setups would remain functional, others point out that the ToS do not explicitly limit this restriction to [[Cloud (service)|cloud]]-based printing. This ambiguity has led to speculation that Bambu Lab could enforce broader limitations, effectively rendering printers inoperable for users who choose not to update.<ref name="theverge-bambu-2025">{{Cite web |last=Hollister |first=Sean |date=2025-01-22 |title=Here's what Bambu will — and won't — promise after its controversial 3D printer update |url=https://www.theverge.com/2025/1/21/24349031/bambu-3d-printer-update-authentication-filament-subscription-lock-answers |url-status=live |access-date=2025-05-01 |website=The Verge |archive-url=http://web.archive.org/web/20251122143504/https://www.theverge.com/2025/1/21/24349031/bambu-3d-printer-update-authentication-filament-subscription-lock-answers |archive-date=2025-11-22}}</ref>

====Editing of initial announcement====
Bambu users were concerned they would not be able to use their printer if they did not install this update, due to the wording of the blog and the ToS.<ref>[[:File:Bambu tos screenshot.png]]</ref> This caused confusion since users report that Bambu's blog post dated January 16, 2025<ref name="firmware-update-introducing-new-authorization-control-system-2" /> includes the FAQ entry:
<blockquote>''What happens if I never upgrade to this firmware?''

''You may continue using an older firmware version that does not include the new security updates; however, this means the printers may miss out on important security fixes or bug patches included in newer versions. We highly encourage updating to the latest firmware version for the best experience and enhanced security.''</blockquote>However, '''this was not present on the day of the announcement.''' A snapshot of their webpage from archive.is demonstrates this section did not exist on the day of the announcement, when community members voiced their concerns.<ref name="firmware-update-introducing-new-authorization-control-system-2" /><ref>[[:File:2024-01-16-Firmware Update Introducing New Authorization Control System.pdf]]</ref> Bambu's response to community feedback<ref>{{Cite web |last=@Spaghetti Monster |date=2025-01-20 |title=Updates and Third-Party Integration with Bambu Connect |url=https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |url-status=live |archive-url=https://ghostarchive.org/archive/cIejw |archive-date=2026-03-30 |access-date=2025-05-01 |website=Bambu Lab Blog}}</ref> references ''"social media posts spreading baseless allegations and untrue claims about Bambu Lab",'' including ''"Firmware updates will block your printer's ability to print.",'' without mentioning the context for those allegations. The context for those allegations was the lack of inclusion of the ''"What happens if I never upgrade to this firmware?"'' in Bambu's initial announcement alongside their stated terms of service.

After the edit, the announcement header reads '''Updated: January 17, 2025''' and notes that additional details and FAQs (including the "What happens if I never upgrade to this firmware?" entry) were added.

The earliest archive.is snapshot of the announcement, dated January 16, 2025 17:31 UTC,<ref name="firmware-update-introducing-new-authorization-control-system-22">{{Cite web |last=@BambuKidd |date=2025-01-16 |title=Firmware Update Introducing New Authorization Control System |url=https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/ |url-status=live |archive-url=https://ghostarchive.org/archive/qwL63 |archive-date=2026-03-07 |access-date=2025-05-01 |website=[[Bambu Lab]] Blog}}</ref> contains two passages about staying on the old firmware. Under "Important Information for End Users":
<blockquote>''2. Old Firmware Option: Users who decide to use an older firmware version can still use the previous or new versions of Bambu Studio and Bambu Handy without restrictions.''</blockquote>
Under "Information for OrcaSlicer users":
<blockquote>''1. You can continue using your X Series 3D printer with the older firmware version (which does not include Authorization Features). 2. If you choose to upgrade to the firmware version with Authorization Features, you must download and install Bambu Connect (a printer control software).''</blockquote>
The FAQ section was added after the initial blog post publication and is noted as an update in the announcement header.

===Debate over "bricking" terminology===
The debate has also extended to the definition of "bricking". Some community members assert that if a printer is unable to accept new print jobs without an update, it effectively becomes non-functional and qualifies as being "bricked." Others counter that as long as certain offline functionalities remain (such as SD-card printing) the term does not accurately apply.<ref name="theverge-bambu-2025" />

===Privacy policy issues===
Bambu Lab's privacy policy describes that when a user submits a print job through Bambu cloud, Bambu may forward configuration information, printing settings, model picture, plate thumbnails and G-code files (referred to in the policy as "Printing Files"), and when the print history reprinting feature is enabled, may store started times, finished times, and filament consumption.<ref name=":6">{{Cite web |date=2025-03-25 |title=Privacy Policy |url=https://bambulab.com/en-us/policies/privacy |url-status=live |archive-url=https://ghostarchive.org/archive/0XOv5 |archive-date=2026-03-10 |access-date=2025-05-01 |website=[[Bambu Lab]]}}</ref> The privacy policy webpage is not present in the Wayback Machine.<ref name=":6" />

===Community strategies to deal with risks===
Users have discussed strategies to avoid possible disruptions, including:
*Operating printers exclusively in offline modes.
*Using LAN connections or VPN setups: this requires an access key from the printer (previously, you could use your cloud credentials over LAN).
*Exploring alternative firmware or third-party scripts to restore full functionality.<ref name="theverge-bambu-2025" />

==Bambu Lab's justification and rebuttal==
Bambu Lab has stated that the authorization system is in place in order to protect against "remote hacks," "printer exposure," and "abnormal traffic or attacks." The cited security incidents have specific context:

*The "remote hacks" cited as an example in the article followed a reported security vulnerability in a 3D printer product; according to Bitdefender's reporting, the researcher infected machines to display a harmless message in order to publicize the unpatched flaw.<ref>{{Cite web |last=Cluley |first=Graham |date=2024-03-01 |title=Someone is hacking 3D printers to warn owners of a security flaw |url=https://www.bitdefender.com/en-au/blog/hotforsecurity/someone-is-hacking-3d-printers-to-warn-owners-of-a-security-flaw?ref=blog.bambulab.com |url-status=live |archive-url=https://web.archive.org/web/20260216002646/https://www.bitdefender.com/en-au/blog/hotforsecurity/someone-is-hacking-3d-printers-to-warn-owners-of-a-security-flaw?ref=blog.bambulab.com |archive-date=2026-02-16 |access-date=2025-05-01 |website=[[Bitdefender]]}}</ref>
*In the article cited about printer exposure, the hack was carried out largely because of user misconfiguration.<ref>{{Cite web |last=Ms. Smith |date=2018-09-05 |title=Over 3,700 exposed 3D printers open to remote attackers |url=https://www.csoonline.com/article/566223/over-3700-exposed-3d-printers-open-to-remote-attackers.html?ref=blog.bambulab.com |url-status=live |archive-url=https://web.archive.org/web/20260216002556/https://www.csoonline.com/article/566223/over-3700-exposed-3d-printers-open-to-remote-attackers.html?ref=blog.bambulab.com |archive-date=2026-02-16 |access-date=2025-05-01 |website=[[CSO]]}}</ref>
*The "abnormal traffic" can be mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.<ref>{{Cite web |title=Summary of Security Incident Responses and Abnormal Cloud Traffic |url=https://wiki.bambulab.com/en/security-incidents-cloud-traffic?ref=blog.bambulab.com |url-status=live |archive-url= |archive-date= |access-date=2025-05-01 |website=[[Bambu Lab]] Wiki}}</ref>
*"Other malicious devices in the LAN" can be partially mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.<ref>{{Cite web |last=@SpaghettiMonster |date=2022-11-25 |title=Answering network security concerns for our printers |url=https://blog.bambulab.com/answering-network-security-concerns/ |url-status=live |archive-url=https://ghostarchive.org/archive/CE0Ii |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Blog}}</ref>

==Issues with LAN mode requiring authorization==
[[File:Bambu Connect App - Lan Device Discovery without Bambu Login.png|thumb|Bambu Connect App - Lan Device Discovery without Bambu Login]]
Bambu Lab printers have the ability to be controlled over both cloud and LAN. This allowed users to integrate their printers into private networks and maintain full control without having to rely on the manufacturer's server while also allowing cloud access. The new authorization system mandates that even LAN-based operations must go through an authentication process using Bambu Connect to retain full control.<ref name="bambu-connect">{{Cite web |last=@Nil.lin |title=Bambu Connect (beta) |url=https://wiki.bambulab.com/en/software/bambu-connect |url-status=live |archive-url=https://ghostarchive.org/archive/CVCtK |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Wiki}}</ref> Full local access is still possible and unchanged for those not using the cloud.

This change has drawn criticism for many reasons:
*'''Privacy concerns''': Requiring authentication for LAN mode raises concerns about data being unnecessarily exposed to Bambu Lab's servers, even for local-only operations, though previously, the printer was also connected and could be controlled by the cloud even when sending prints locally.
**Confidentiality required by US Law: this is in conflict with users that have to comply with internal U.S. government classified information handling regulations.
*'''Loss of offline independence while also using cloud''': Before, users could have hybrid offline setups. The requirement for authentication removes this option unless users revert to older firmware versions; Bambu Lab initially indicated rollback would not be permitted, though The Verge later reported that users could still downgrade and use LAN access keys while signed into the cloud.
*'''Increased complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control while retaining cloud functionality.<ref name=":4">{{Cite web |last=@edlboston |date=2023-01 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Yes, I know about the LAN mode. But as has been stated by many people, things like the camera will not work, nor will the Handy app. There is no technical reason that these are bound to the cloud. This is the problem and why I titled this FULL Non-Cloud Network.}}</ref>

*LAN-Only mode in Orca Slicer is implemented by passing API Calls to the installed proprietary Bambu Network Plug-In (unlike BTT and other solutions that did indeed communicate with printer directly via MQTT protocol).
*Plug-In provides controls for Printers "Critical Operations" (as classified by the Firmware Announcement article) and displays these controls within the window of Orca Slicer.
*Using intermediary Plug-In does not manifest as "direct access through network plugin". It is still a Proxy communication, even if user experience is presented as direct communication (same slicer window).
*Bambu Connect moves the Network Plug-In functionality outside of the window of Orca Slicer thus appearing as separate window and presents the appearance of "indirect" communication channel to the printer.
*While the user experience is different, the flow remains unchanged Orca Slicer slices model -> Orca Slicer Calls API of Bambu Proprietary Software -> Bambu Proprietary Software controls the printer.

Additionally, Bambu Connect software (downloaded and installed in January 2025, before the backlash response) supports adding LAN-Only printers without requiring Bambu Account authentication, the same behavior as the Network Plugin used in Orca Slicer.

===Precedents and comparisons===
Critics have likened this potential functionality to similar cases in other industries where manufacturers remotely restrict product features. A documented example is [[HP]]'s printer firmware updates that [[HP Instant Ink|rendered third-party ink cartridges unusable]], which became the subject of a class-action settlement.<ref name=":5">{{Cite web |last=Harding |first=Scharon |date=2025-03-19 |title=HP avoids monetary damages over bricked printers in class-action settlement |url=https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |url-status=live |archive-url=http://web.archive.org/web/20250319231817/https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |archive-date=2025-03-19 |website=Ars Technica}}</ref>

===X1E firmware 01.01.02.00 LAN-mode connection failure===
Newly received X1E printers with firmware 01.01.02.00 will not connect to the Bambu Studio using the Lan only method password. Bambu Studio identifies the un-logged printer but will not allow a connection to the printer. Only after connection / account pairing is done over the Bambu Handy app by giving internet access to the PC and Printer then using the cloud service connection will Lan only communication and login work.<ref>{{Cite web |last= |date=2024-09 |title=Connect X1E to stand-alone computer |url=https://forum.bambulab.com/t/connect-x1e-to-stand-alone-computer/101474 |url-status=live |archive-url=https://web.archive.org/web/20260223033045/https://forum.bambulab.com/t/connect-x1e-to-stand-alone-computer/101474 |archive-date=2026-02-23 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum}}</ref>

==Implementation timeline and requirements==

The authorization system will be rolled out in phases, starting with the X1 series printers. A beta firmware (version 01.08.03.00) was released on January 17, 2025, with the full release scheduled for late January 2025.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> The P & A series printers will get similar updates at an unspecified future date.

To use printers with the new authorization system, users must update multiple pieces of software:<ref name="firmware-update-introducing-new-authorization-control-system-2" />
*Bambu Studio must be updated to version 01.10.02.64 or higher
*Bambu Handy mobile app must be updated to version 2.17.0 or higher
*The new Bambu Connect application must be installed for using third-party slicers

These software updates are mandatory for users who update their firmware. Failing to update all components simultaneously will result in certain printer controls becoming unusable. Users who choose to maintain third-party software compatibility can continue using older firmware versions, or downgrade the firmware for new printers that ship with the authorization system pre-installed.<ref name="firmware-update-introducing-new-authorization-control-system-2" />

Bambu Lab states these coordinated updates are necessary because the new authorization system changes how the printer validates and accepts commands. The older versions of Bambu Studio and Bambu Handy lack the authentication mechanisms required to interact with printers running the new firmware. The Bambu Connect application was created specifically to provide a controlled interface for third-party software, replacing the previous direct access through network plugins.<ref name="firmware-update-introducing-new-authorization-control-system-2" />

==Impact on third-party integration and user choice==

===Changes to third-party access===
The new authorization system replaces direct network API access with a more limited URL-based interface through Bambu Connect. Third-party software can only interact with the printer by sending specific URL commands to Bambu Connect.<ref name="bambu-connect" /> The interface requires three parameters:

*<code>path</code>: The absolute file system path to the 3MF file (e.g., /tmp/cube.gcode.3mf)
*<code>name</code>: The name of the file (e.g., Cube)
*<code>version</code>: A fixed value of 1.0.0 for compatibility

A complete command must be formatted as:

bambu-connect://import-file?path=%2Ftmp%2Fcube.gcode.3mf&name=Cube&version=1.0.0

This interface only allows basic file transfer and print initiation. All other printer-control functions previously available to third-party software are now exclusive to Bambu's own applications. The path and name parameters must be URL-encoded using encodeURIComponent or equivalent functions<ref name="bambu-connect" />.

===Reduced home-automation capabilities===
While basic status monitoring remains available (e.g., print-progress updates in Home Assistant), the new firmware removes the ability for home-automation systems to control printer functions. Users can no longer:
*Start or stop prints remotely using Home Assistant, BTT Panda Touch,<ref name=":0">{{Cite web |last=@BIGTREETECH |date=2025-01-17 |title=BIGTREETECH's post |url=https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |url-status=live |archive-url=http://web.archive.org/web/20251004104021/https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |archive-date=2025-10-04 |website=[[Facebook]]}}</ref> or other third-party accessories or software interfaces
*Control printer temperatures or cooling
*Automate printer behaviors based on sensor data or events
*Access camera feeds through third-party applications<ref name="bambulab-forum-135400/9">{{Cite web |last=@hho |date=2025-01-16 |title=This new auth system will make me sell my printers |url=https://forum.bambulab.com/t/this-new-auth-system-will-make-me-sell-my-printers/135400/9 |url-status=live |archive-url=https://ghostarchive.org/archive/ro1KZ |archive-date=2026-03-30 |access-date=2025-05-01 |website=Bambu Lab Community Forum}}</ref>

===Permanent nature of the update===
Once a printer is updated to the new firmware, users can still revert to previous versions.<ref name="theverge-bambu-2025" /> The option still exists to disable the cloud service.

The manufacturer states this change is required for security, but community members note that many of the security vulnerabilities being addressed stem from Bambu's own cloud-centric design choices rather than inherent risks of local network control<ref name="bambulab-forum-134549/12">{{Cite web |date=2025-01-14 |title=Bambu Studio 1.10.2 Public Beta |url=https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/12 |url-status=live |archive-url=https://ghostarchive.org/archive/u4vpc |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum}}</ref>. The update forces users into using Bambu Connect middleware if they want to retain limited cloud functionality.

For users that would want to use a third-party slicer while using their cloud service, Bambu would require those users to download and install Bambu Connect in order to send gcode wirelessly over LAN or over the cloud. While Bambu claims that they were in contact with SoftFever, the developer of OrcaSlicer, as of January 2025, SoftFever did not have any keys for Bambu Connect and the new firmware was only available as opt-in beta at the time.<ref name=":1">{{Cite web |last=@fever_soft |date=2025-01-18 |title=This is definitely a bummer. I was negotiating for an authorization key to allow OrcaSlicer to communicate with their device like BambuStudio does, but today I was told they won't support this. Only their slicer can send prints directly; others must use their Bambu Connect application |url=https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |url-status=live |access-date=2025-05-01 |website=[[X]] |archive-url=http://web.archive.org/web/20251004104021/https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |archive-date=2025-10-04}}</ref>

==Impact on functionality==
While some functionality remains unauthenticated like in previous firmware versions (sending status information from the printer over the network, starting a print job using SD cards), the most important features now require authentication through a new closed-source client called Bambu Connect<ref name="bambu-connect" />. These restricted features include:

*Initializing prints via LAN or cloud mode
*Remote video access to monitor prints
*Controlling motion system, temperature, fans
*AMS settings and calibrations
*Home automation integration beyond basic status monitoring

Previously, third-party software such as OrcaSlicer<ref name="orca-slicer-issue8063">{{Cite web |date=2025-01-16 |title=FW 1.08.03.00 from Bambu WILL BREAK ORCASLICER for X, P and A series #8063 |url=https://github.com/SoftFever/OrcaSlicer/issues/8063 |url-status=live |archive-url=http://web.archive.org/web/20250708192842/https://github.com/SoftFever/OrcaSlicer/issues/8063 |archive-date=2025-07-08 |access-date=2025-05-01 |website=[[GitHub]]}}</ref> could interact with Bambu Lab printers via the open-source Bambu Studio and proprietary network plug-ins. While Bambu Connect provides a limited URL-based API to initiate prints, most functionality previously openly available is now restricted to Bambu's ecosystem<ref name="bambulab-forum-135400/9" />.

Previously, third-party accessories such as Panda Touch would allow users to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D-pad by default for printer control whereas Panda Touch is a full-color touch screen that had a small battery so that way users could reposition and detach their Panda Touch off their printers if needed. Users would be able to queue up jobs, jog printer motors, and connect to multiple printers at once in order to monitor print jobs. According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch not to update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch. <ref name=":0" />

==Communication with Panda Touch developers==

As of late January 2025, no formal communication between Big Tree Tech (BTT), the manufacturer and developer of Panda Touch, and Bambu Labs had been reported. BTT stated in a Facebook announcement that they had contacted Bambu Lab and would publish updates if Bambu responded.<ref name=":0" />

==Communication with OrcaSlicer developers==

Before the official announcement of the new authorization and authentication, Bambu Lab engaged with the OrcaSlicer development team regarding the changes.

===Pre-announcement contact===
Reports from OrcaSlicer demonstrate that Bambu Lab provided limited advance notice of the changes that would render their software incompatible with Bambu printers running the new firmware. The communication emphasized:
*The introduction of Bambu Connect as the only supported method for interacting with third-party slicers.
*The discontinuation of the network plugin API that OrcaSlicer and other tools relied on for printer control<ref name="orca-slicer-issue8063" />.
*An invitation for OrcaSlicer developers to adapt their software to integrate with the Bambu Connect URL scheme.

The communication lacked the detailed technical documentation that would be necessary for developers to be able to work with the new requirements.

===How the community viewed these actions===
Primary criticisms of Bambu were:
*'''Lack of transparency''': SoftFever reported that the limited warning given to OrcaSlicer developers preceded community engagement with existing customers.<ref name="orca-slicer-issue8063" /> Point to the contrary: the new firmware is in beta and Bambu Connect middleware contains temporary compromises to allow third-party slicers to work as before.
*'''Lack of follow-through:''' As of January 2025, SoftFever, OrcaSlicer's lead developer, did not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Some community members questioned whether Bambu Lab's outreach to OrcaSlicer was a substantive collaboration effort.<ref name=":1" />
*'''Disregard for open-source collaboration''': OrcaSlicer is open-source software developed under the AGPL-3.0 license.<ref name="softfever-orcaslicer-license" /> The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect removes customer choice in how the printer is operated.
*'''Token support for third-party tools''': While Bambu Connect provides a workaround for third-party slicer use, it restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools<ref name="bambu-connect" />.
*'''Power imbalance''': As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users.

==Community-driven workarounds and technical alternatives==

Community members have published workarounds for the firmware restrictions.

===Custom firmware development===
Discussions within the community highlight interest in developing custom firmware as an alternative to Bambu's official updates. One prominent project mentioned in forums is the development of custom firmware for the X1-series printers, such as the "X1Plus Custom Firmware"<ref name="bambulab-forum-134549/12" />. This firmware aims to:
*Restore direct network control and third-party slicer compatibility.
*Re-enable previously available features such as motion-system adjustments, temperature control, and AMS settings without requiring proprietary software.
*Provide users with greater flexibility in integrating printers with home-automation systems and workflows.

However, custom firmware development faces several challenges, including:
*Limited documentation and proprietary hardware components, which complicate reverse-engineering efforts.
*The potential voiding of warranties and risks of bricking devices.
*Legal concerns regarding intellectual property and bypassing manufacturer-imposed restrictions.

==Backup of current third party access enabled firmware and network plugins==
A GitHub repository, [https://github.com/Tzeny/bambulabs_plugins_firmware Tzeny/bambulabs_plugins_firmware], contains a backup of the latest firmware released by Bambu Labs for their printers and of the network plugin used by slicers such as Orca Slicer to communicate with the printer.<ref name="tzeny-bambulabs-plugins-firmware">{{Cite web |last=Tzeny |title=bambulabs_plugins_firmware |url=https://github.com/Tzeny/bambulabs_plugins_firmware |website=GitHub |access-date=2026-05-10 |url-status=live}}</ref>

==LAN mode and blocked internet access==
In January 2025, user Tzeny15 on Reddit authored a five step guide to blocking internet access for the Bambu P1S as a precaution in case the manufacturer attempts to limit functionality for printers without the newest firmware.<ref> {{Cite web |last=@Tzeny15 |title=LAN mode with live view, remote monitoring+control and blocked internet access - a five step guide |url=https://www.reddit.com/r/BambuLab/comments/1i4vp5i/lan_mode_with_live_view_remote_monitoringcontrol/ |url-status=live |access-date=2025-05-01 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250310115818/https://old.reddit.com/r/BambuLab/comments/1i4vp5i/lan_mode_with_live_view_remote_monitoringcontrol/ |archive-date=2025-03-10}}</ref>

[[Bambu Lab LAN mode guide]]

==Reverse engineering Bambu Connect==
{{:Reverse Engineering Bambu Connect}}

''[[Reverse Engineering Bambu Connect|Read more about reverse engineering Bambu Connect here.]]''

==Community tools and scripts==
In addition to firmware alternatives, some users have come up with custom scripts and software tools to interface with Bambu Lab printers indirectly. These tools often rely on:
*Reverse-engineering the URL-based commands required by Bambu Connect to enable partial functionality with third-party slicers like OrcaSlicer.
*Creating local server emulations to replicate the network API previously available before the update.

While these tools provide temporary solutions, they do not fully replace the open access that existed before the firmware update.

===Re-engineering printer-control electronics===
ChazLayyd's Bambu Lab Klipper Conversion project is currently in an incomplete stage<ref>{{Cite web |last=@ChazLayyd |title=Running Klipper on a Bambu Lab machine by replacing it's internal electronics with readily available open-source hardware. |url=https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion |url-status=live |access-date=2025-05-01 |website=GitHub |archive-url=http://web.archive.org/web/20251116182420/https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion |archive-date=2025-11-16}}</ref><ref>{{Cite web |title=ChazLayyd's Discord Community |url=https://discord.com/invite/W6B5mBejuC |url-access=registration |url-status=live |archive-url=https://web.archive.org/web/20260223033213/https://discord.com/invite/W6B5mBejuC |archive-date=2026-02-23 |website=[[Discord]]}}</ref>. While the project was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that run Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.

===Advocacy for open-ecosystem support===
Community members have also organized to advocate for open-source support and rollback options. Suggestions include:
*Allowing an opt-out option for existing users who prefer local network control without cloud dependency.
*Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.<ref name="orca-slicer-issue8063" />

===X1Plus and other alternative firmware===
X1Plus is an open-source custom firmware version for Bambu Labs printers (more details on the GitHub page). It instructs the printer's auto-update mechanism that the device is on a future version (numbered 99 or higher) so the official firmware does not overwrite the modification.

*Installation tutorials are available for users who have not yet updated. Installing third-party firmware will void the warranty. Users are advised to consult the GitHub documentation before installation.
*[https://github.com/X1Plus/X1Plus X1Plus on GitHub]
*The Bambu Labs website offers consumers the ability to request a rootable firmware to be sent to their printers. As of January 26, 2025, the feature (in the EU at least) is broken such that you cannot finalize the process of requesting such a firmware.<ref name="bambu-third-party-firmware-plan">{{Cite web |title=Third Party Firmware Plan |url=https://bambulab.com/en-eu/third-party-firmware/plan |website=Bambu Lab |access-date=2025-01-26 |url-status=live}}</ref>
**The result of accepting the terms of the page titled "Third Party Firmware Plan Guideline" and clicking "Next" takes you to a page titled "Important Notice and Risk Warning" which, when accepting the terms leaves you with an "I got it" button that takes you back to the previous page.

==Cease and desist against the OrcaSlicer-bambulab re-enablement project==

In April 2026, Bambu Lab sent a cease-and-desist communication to the developer of a third-party OrcaSlicer fork that had restored direct printer control after the Authorization Control System rollout. The project was wiped from public view the same day the threat was delivered, and the developer published a summary of Bambu Lab's allegations but not the letter itself, citing Bambu Lab's refusal to authorize publication.<ref name="jarczak-readme" /> The full public-record account includes a parallel May 7, 2026 Bambu Lab blog post & three same-day public Reddit replies from the maintainer.

===What OrcaSlicer is===
OrcaSlicer is a free, open-source slicer: a program that converts a 3D model file into the layer-by-layer instructions (G-code) a 3D printer needs to produce the physical object. It is maintained by the developer SoftFever and draws from Bambu Lab's Bambu Studio, which is itself a fork of Prusa Research's PrusaSlicer.<ref name="softfever-orcaslicer">{{Cite web |last=SoftFever |title=OrcaSlicer |url=https://github.com/SoftFever/OrcaSlicer |url-status=live |access-date=2026-05-04 |website=[[GitHub]]}}</ref> Bambu Studio in turn descends from Slic3r, the upstream project Prusa Research forked.<ref name="slic3r-repo">{{Cite web |title=Slic3r |url=https://github.com/slic3r/Slic3r |website=GitHub |access-date=2026-05-10 |url-status=live}}</ref><ref name="prusaslicer-license">{{Cite web |title=PrusaSlicer LICENSE (AGPL-3.0) |url=https://github.com/prusa3d/PrusaSlicer/blob/master/LICENSE |website=GitHub |publisher=Prusa Research |access-date=2026-05-10 |url-status=live}}</ref> OrcaSlicer is widely used by owners of Bambu Lab printers as an alternative to Bambu Studio, & it ships under the AGPL-3.0 license.<ref name="softfever-orcaslicer" /><ref name="softfever-orcaslicer-license">{{Cite web |title=OrcaSlicer LICENSE.txt (AGPL-3.0) |url=https://github.com/SoftFever/OrcaSlicer/blob/main/LICENSE.txt |website=GitHub |publisher=SoftFever |access-date=2026-05-10 |url-status=live}}</ref><ref name="xda-jarczak">{{Cite web |last=Batt |first=Simon |date=2026-04-23 |title=A developer restored OrcaSlicer's features that Bambu Lab killed — then the legal threats arrived |url=https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |url-status=live |archive-url=https://web.archive.org/web/20260427233833/https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |archive-date=2026-04-27 |access-date=2026-05-04 |website=XDA Developers}}</ref>

===Restrictions introduced by the Authorization Control System===
The Authorization Control System announced on January 16, 2025 gated print initiation, motion control, fan & hotend temperature control, AMS configuration, calibrations, remote video, & firmware upgrade behind a Bambu-issued authentication path. Owners who installed the new firmware could no longer send print jobs from third-party slicers directly over the local network; they had to route those jobs through a new closed-source middleware, Bambu Connect.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> SoftFever was not given API keys for Bambu Connect & stated publicly that direct print sending from OrcaSlicer would not be supported going forward.<ref name=":1" />

=== OrcaSlicer-bambulab fork===
On April 23, 2026, the developer Pawel Jarczak (GitHub user <code>jarczakpawel</code>) made a public fork named OrcaSlicer-bambulab at <code>github.com/jarczakpawel/OrcaSlicer-bambulab</code>. The fork restored the ability to send print jobs from OrcaSlicer directly to Bambu Lab printers without routing through Bambu Connect.<ref name="xda-jarczak" /> According to Jarczak's own description, the fork worked by reaching the printer through a Linux-side workflow Bambu Lab had not yet disabled, & was built on publicly available Bambu Studio source code combined with the developer's own integration layer; it did not redistribute Bambu Lab's proprietary networking plugin binaries.<ref name="jarczak-readme" /><ref name="3druck-jarczak">{{Cite web |date=2026-04-30 |title=Developer ends OrcaSlicer fork after Bambu Lab threatens legal action |url=https://3druck.com/en/programs/developer-terminates-orcaslicer-fork-after-bambu-lab-threatens-to-sue-32156744/ |url-status=live |access-date=2026-05-04 |website=3Druck.com}}</ref> Jarczak also maintained a sibling fork at <code>github.com/jarczakpawel/BambuStudio-BMCU</code> that added support for a third-party multi-color unit (BMCU); that repository remained live as of May 9, 2026.<ref name="jarczak-bmcu">{{Cite web |last=Jarczak |first=Pawel |title=BambuStudio-BMCU |url=https://github.com/jarczakpawel/BambuStudio-BMCU |website=GitHub |access-date=2026-05-10 |url-status=live}}</ref>

===cease and desist===
Bambu Lab contacted Jarczak directly & demanded removal of the fork. According to Jarczak's own first-person account in his public archive README, Bambu Lab "referred to legal materials and stated that a cease and desist letter had been prepared," & alleged that the implementation:
<blockquote>''impersonated Bambu Studio, bypassed their authorization controls, violated their Terms of Use, involved "reverse engineering", and could allow modified forks to send arbitrary commands to printers.''</blockquote><ref name="jarczak-readme" /> Jarczak rejected the reverse-engineering characterization, stating that his work was based on publicly available Bambu Studio source code, which Bambu Lab releases under the AGPL-3.0 license.<ref name="jarczak-readme" /><ref name="3druck-jarczak" /> Jarczak disputed the broader characterization and asked for specifics: the exact files or commits at issue, & the exact legal or contractual basis. He reports receiving "further broad accusations" instead of that specificity.<ref name="jarczak-readme" /> Bambu Lab refused consent for publication of the correspondence itself, & Jarczak elected to honor that refusal while retaining the letter.<ref name="jarczak-readme" /> The repository was wiped the same day the threat was delivered.<ref name="jarczak-readme" /><ref name="xda-jarczak" /> Jarczak removed the contents voluntarily & stated this was a practical decision, not an admission that the legal or technical allegations were correct; in his own words from the public archive notice:
<blockquote>''I removed the repository voluntarily. That removal should not be interpreted as an admission that all legal or technical allegations made against the project were correct.''</blockquote><ref name="jarczak-readme" />
XDA Developers reported that Bambu Lab had not responded to its request for comment as of publication.<ref name="xda-jarczak" /> 3Druck independently confirmed the same set of allegations, citing Jarczak's GitHub statement.<ref name="3druck-jarczak" /> Tom's Hardware also covered the takedown on April 29, 2026.<ref name="tomshardware-jarczak">{{Cite web |title=Developer re-enables 3D printer features that Bambu Lab disabled, firm promptly threatens legal action — OrcaSlicer-BambuLab project now shuttered |url=https://www.tomshardware.com/3d-printing/developer-re-enables-3d-printer-features-that-bambu-lab-disabled-firm-promptly-threatens-legal-action-orcaslicer-bambulab-project-now-shuttered |website=Tom's Hardware |date=2026-04-29 |access-date=2026-05-10 |url-status=live}}</ref> The trade outlet Manufactur3D added context on May 1, 2026, including that the dispute had become a flashpoint in the wider 3D-printing community.<ref name="manufactur3d-controversy">{{Cite web |title=Bambu Lab OrcaSlicer Controversy Ignites After Legal Threats |url=https://manufactur3dmag.com/bambu-lab-orcaslicer-controversy-escalates/ |website=Manufactur3D |date=2026-05-01 |access-date=2026-05-10 |url-status=live}}</ref>

The publicly documented allegations track Bambu Lab's [[Terms of Service]] & an "authorization bypass" framing.<ref name=":2" /><ref name="jarczak-readme" /> Because the letter itself was not made public, no primary source confirms which specific statute, if any, Bambu Lab invoked; neither Jarczak's account nor the secondary reporting names a specific statute, including the [[DMCA Section 1201|DMCA §1201]] anti-circumvention provision, as part of Bambu Lab's claim. The upstream OrcaSlicer maintainer SoftFever was not named in the cease-and-desist, has issued no public statement on the fork or the letter, & the upstream repository remains active.<ref name="softfever-orcaslicer" />

===Public timeline===
The timeline below is built strictly from public sources. Private direct-message correspondence between Pawel Jarczak & Bambu Lab is not republished; every claim is anchored to Jarczak's public archive README, Bambu Lab's public blog, Bambu Lab's public Reddit post, three public Reddit replies under the parent thread, or independent press coverage.

*'''January 16, 2025.''' Bambu Lab announced "Firmware Update: Introducing the New Authorization Control System," describing the firmware-gated authorization model.<ref name="firmware-update-introducing-new-authorization-control-system-2" />
*'''Spring 2026.''' Pawel Jarczak published <code>OrcaSlicer-bambulab</code> & a sibling repository <code>BambuStudio-BMCU</code> on GitHub.<ref name="jarczak-readme" /><ref name="jarczak-bmcu" />
*'''Late April 2026.''' Bambu Lab contacted Jarczak privately on Reddit & demanded removal of the OrcaSlicer fork. Per Jarczak's public README, Bambu Lab's allegations were impersonation of Bambu Studio, bypass of authorization controls, ToS violation, reverse engineering, & the potential for modified forks to send arbitrary commands to printers.<ref name="jarczak-readme" />
*'''Around April 23, 2026.''' Jarczak removed the <code>OrcaSlicer-bambulab</code> repository voluntarily & replaced its contents with a public archive notice; <code>jarczakpawel/BambuStudio-BMCU</code> remained live as of May 9, 2026.<ref name="jarczak-readme" /><ref name="jarczak-bmcu" />
*'''May 7, 2026.''' Bambu Lab published "Setting the record straight on Cloud Access and Community" on its blog & posted a parallel announcement on r/BambuLab the same day.<ref name="bambu-blog-record-straight" /><ref name="bambu-reddit-record-straight">{{Cite web |last=BambuLab |title=Setting the record straight on Cloud Access and Community |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/setting_the_record_straight_on_cloud_access_and/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref>
*'''May 7, 2026 (same day).''' A Reddit user posting as <code>Low-Anything6975</code> replied publicly under three top-level comments on the r/BambuLab thread. The first reply pinpointed the file path & code line in Bambu's own AGPL source where the User-Agent string is generated.<ref name="pawel-reddit-okg9iih">{{Cite web |last=Low-Anything6975 |title=Reply on User-Agent attribution in Bambu Studio AGPL source code |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/comment/okg9iih/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The second reply addressed the cloud Terms of Service & AGPL rights to use, modify & redistribute.<ref name="pawel-reddit-okguwzs">{{Cite web |last=Low-Anything6975 |title=Reply on cloud Terms of Service and AGPL rights to use, modify and redistribute |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/comment/okguwzs/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The third reply articulated the plugin-severability symmetry argument.<ref name="pawel-reddit-okiacag">{{Cite web |last=Low-Anything6975 |title=Reply on plugin severability symmetry between AGPL forks and Bambu Lab cloud |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/comment/okiacag/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref>
*'''May 9, 2026.''' Jarczak's public archive README was last updated; <code>BambuStudio-BMCU</code> remained live.<ref name="jarczak-readme" /><ref name="jarczak-bmcu" />
*'''May 9, 2026.''' Right-to-repair advocate Louis Rossmann publicly pledged $10,000 toward Jarczak's legal defense if Bambu Lab proceeded with the threatened lawsuit in a YouTube video titled "I'll put up $10,000 to teach bambu labs a lesson."<ref name="rossmann-youtube-pledge">{{Cite web |last=Rossmann |first=Louis |title=I'll put up $10,000 to teach bambu labs a lesson |url=https://www.youtube.com/watch?v=qLLVn6XT7v0 |website=YouTube |date=2026-05-09 |access-date=2026-05-10 |url-status=live}}</ref>
*'''May 10, 2026.''' Tom's Hardware reported Rossmann's pledge & accompanying public statement directed at Bambu Lab.<ref name="tomshardware-rossmann-pledge">{{Cite web |title=Louis Rossmann tells 3D printer maker Bambu Lab to 'Go (Bleep) yourself' over its threatened lawsuit against enthusiast — Right to Repair advocate offers to pay the legal fees for a threatened OrcaSlicer developer |url=https://www.tomshardware.com/3d-printing/louis-rossmann-tells-3d-printer-maker-bambu-lab-to-go-bleep-yourself-over-its-lawsuit-against-enthusiast-right-to-repair-advocate-offers-to-pay-the-legal-fees-for-a-threatened-orcaslicer-developer |website=Tom's Hardware |date=2026-05-10 |access-date=2026-05-10 |url-status=live}}</ref>

===Bambu Lab's public response===
Bambu Lab's May 7, 2026 blog post conceded that AGPL forks of Bambu Studio are permitted, recast the dispute as one about cloud access & "impersonation" rather than open source, & declined any responsibility under AGPL for the cloud back-end. Bambu Lab characterized the AGPL question:
<blockquote>''Bambu Studio is an open-source project under the AGPL-3.0 license. Anyone can take its code, modify it, and distribute it. This is not a matter of our "permission" - it is simply how the license and open source work.''</blockquote><ref name="bambu-blog-record-straight" />
The same post bifurcated AGPL code from cloud infrastructure:
<blockquote>''Our cloud is a private service. Access to it is governed by a user agreement, not the AGPL license.''</blockquote><ref name="bambu-blog-record-straight" />
Bambu Lab's only concrete technical allegation against the OrcaSlicer-bambulab fork in the post was that the modification "worked by injecting falsified identity metadata into network communication." The post identified the metadata as the HTTP User-Agent string the fork emitted to Bambu Cloud:
<blockquote>''When this particular OrcaSlicer fork communicates with our cloud services, it quietly introduces itself as official Bambu Studio - with a hardcoded version number and all... that's precisely the point where code modification crosses into impersonation.''</blockquote><ref name="bambu-blog-record-straight" />
Bambu Lab restated the bifurcation in summary form:
<blockquote>''Modifying and distributing AGPL code - absolutely. But impersonating official clients in communication with our cloud infrastructure is not allowed.''</blockquote><ref name="bambu-blog-record-straight" />
The trade outlet 3Druck published an analysis of the post on May 7, 2026, headlined that the dispute was about cloud access rather than open-source customization.<ref name="3druck-bambu-cloud-not-opensource">{{Cite web |title=Dispute over OrcaSlicer fork: Bambu Lab is about cloud access, not open-source customization |url=https://3druck.com/en/programs/dispute-over-orcaslicer-fork-bambu-lab-is-about-cloud-access-not-open-source-customization-16157098/ |website=3Druck.com |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref>

===Consumer-rights significance===
Bambu Lab printer owners had paid for hardware that, at the time of purchase, allowed third-party slicers to send print jobs directly over their own local network. The January 2025 firmware update removed that capability for owners who installed the update.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> When an independent developer rebuilt the lost capability on top of source code Bambu Lab itself publishes, Bambu Lab contacted him privately on Reddit and stated that a cease and desist letter had been prepared.<ref name="jarczak-readme" /> The developer took the project down and stated he had "no interest in maintaining a prolonged dispute."<ref name="jarczak-readme" />

==Open-source licensing dispute==

The cease-and-desist against Pawel Jarczak's OrcaSlicer-bambulab fork made the underlying open-source-licensing conflict concrete: a manufacturer that publishes a slicer under the AGPL-3.0 license, while imposing a Terms of Use that forbids the modification & redistribution that license grants, is on a collision course with the license it chose. The legal arguments in this section are drawn from the AGPL text Bambu Lab applied to Bambu Studio, the Terms of Use Bambu Lab publishes on its corporate website, the Bambu Lab blog post of May 7, 2026, three public Reddit replies under the parent thread, the BambuStudio source code on GitHub, the FSF's published interpretive guidance, & U.S. & EU primary law. None of the theories below has been adjudicated against Bambu Lab; each is a question raised by Bambu Lab's own conduct & documents.

===Bambu Studio AGPL-3.0 licensing===
Bambu Lab elected to release Bambu Studio under the [[GNU Affero General Public License|GNU Affero General Public License version 3]] (AGPL-3.0). The LICENSE file in the upstream Bambu Studio repository is the verbatim AGPL-3.0 text.<ref name="bambustudio-license" /><ref name="agpl3-license">{{Cite web |title=GNU Affero General Public License Version 3 |url=https://www.gnu.org/licenses/agpl-3.0.html |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> The AGPL is a copyleft license: anyone who receives the code can use, modify & redistribute it, on the condition that they pass the same rights to everyone they distribute to, & that they make their modifications available as source code.<ref name="agpl3-license" /> The final paragraph of Section 10 (titled "Automatic Licensing of Downstream Recipients") begins:
<blockquote>''You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.''</blockquote><ref name="agpl3-section10">{{Cite web |title=GNU Affero General Public License Version 3, Section 10 (Automatic Licensing of Downstream Recipients) |url=https://www.gnu.org/licenses/agpl-3.0.html#section10 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> The paragraph continues with examples of prohibited restrictions, including imposing license fees or royalties for exercise of the granted rights & initiating patent litigation against users of the program.<ref name="agpl3-section10" />
Section 7, paragraph 4, lists the only kinds of additional terms a licensor may attach to AGPL-licensed code & states that downstream recipients may strip out anything outside that list:
<blockquote>''All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.''</blockquote><ref name="agpl3-section7">{{Cite web |title=GNU Affero General Public License Version 3, Section 7 (Additional Terms) |url=https://www.gnu.org/licenses/agpl-3.0.html#section7 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref>
Bambu Lab's May 7, 2026 blog post acknowledges the licensing posture.<ref name="bambu-blog-record-straight" />

===Terms of Use conflict with AGPL===
Bambu Lab's Terms of Use § 3.4, preserving a typo in the source text:
<blockquote>''Except as otherwise expressly permitted, you shall not, nor allow any other person to misappropriate, intrude or make other inappropriate use of the Product, including, but not limited to modify, discoder, copy, reverse engineer, publish, publicly disseminate, decompile, export codes, disassemble or create derivatives of the Product in any way.''</blockquote><ref name=":2" />
Two further clauses in § 3.5 reinforce the same prohibitions. § 3.5(2) states:
<blockquote>''(2) provide to third parties, or allow third parties to use the whole or part of the Software without obtaining Bambu Lab's written consent (including but not limited to apps, services, code, and source code)''</blockquote><ref name=":2" />
§ 3.5(5) states:
<blockquote>''(5) attempt to destroy, bypass, change, invalidate or escape from the Product and/or any digital rights management system that is part of the organic composition of the Product''</blockquote><ref name=":2" />
Bambu Lab's Terms define "Product" to include Bambu Lab devices & the software contained therein.<ref name=":2" /> Bambu Lab's own May 7, 2026 blog post confirms that Bambu Studio is "the software" in question.<ref name="bambu-blog-record-straight" />

The collision is straightforward: AGPL § 7 ¶ 4 & § 10 forbid the licensor from imposing additional restrictions on AGPL-granted rights, & TOS § 3.4 / § 3.5 forbid the modification, copying, reverse engineering, decompilation, & redistribution that AGPL-3.0 explicitly grants. Either the TOS clauses do not apply to the AGPL-licensed Bambu Studio (in which case Bambu Lab should say so on the TOS page) or they do (in which case § 10 makes them unenforceable as further restrictions, & § 7 ¶ 4 lets downstream recipients strip them). On the public record, both documents exist unqualified on Bambu Lab's servers; the FSF's published GPL FAQ classifies a network of dynamically linked components & function calls as "a single combined program" for license-obligation purposes,<ref name="fsf-gpl-faq-plugins">{{Cite web |title=Frequently Asked Questions about the GNU Licenses (GPLPlugins anchor) |url=https://www.gnu.org/licenses/gpl-faq.html#GPLPlugins |website=GNU Project |publisher=Free Software Foundation |access-date=2026-05-10 |url-status=live}}</ref> & nothing in Bambu Lab's blog post resolves the contradiction between the AGPL grant & the TOS prohibitions on AGPL-covered conduct.

The same Reddit user addressed this directly on May 7, 2026:
<blockquote>''Cloud ToS also cannot erase AGPL rights to use, modify and redistribute that code.''</blockquote><ref name="pawel-reddit-okguwzs" />

===Plugin severability contradiction===
Bambu Lab's May 7, 2026 blog post asserts two positions that cannot both be right. The first treats the proprietary networking plugin as severable from the AGPL-licensed Bambu Studio code so that Bambu Lab owes no AGPL obligations on the plugin's network conduct or on Bambu Cloud:
<blockquote>''Our cloud is a private service. Access to it is governed by a user agreement, not the AGPL license.''</blockquote><ref name="bambu-blog-record-straight" />
The second treats the same plugin's network conduct as the AGPL fork's responsibility for impersonation-liability purposes:
<blockquote>''When this particular OrcaSlicer fork communicates with our cloud services, it quietly introduces itself as official Bambu Studio - with a hardcoded version number and all... that's precisely the point where code modification crosses into impersonation.''</blockquote><ref name="bambu-blog-record-straight" />
Severability is symmetrical. Either the proprietary plugin is severable from the AGPL Bambu Studio code (in which case the AGPL fork is the wrong defendant for plugin-mediated network conduct, since the user voluntarily installs the plugin), or the plugin is part of a "Combined Work" with the AGPL Bambu Studio code (in which case Bambu Lab carries AGPL obligations on the combined work).<ref name="fsf-gpl-faq-plugins" /><ref name="fsf-gpl-faq-aggregation">{{Cite web |title=Frequently Asked Questions about the GNU Licenses (MereAggregation anchor) |url=https://www.gnu.org/licenses/gpl-faq.html#MereAggregation |website=GNU Project |publisher=Free Software Foundation |access-date=2026-05-10 |url-status=live}}</ref> The third reply from the same Reddit user on May 7, 2026 stated the symmetry plainly:
<blockquote>''It is more like someone opened a gym on a public square and then tried to forbid people from using the public square.''</blockquote><ref name="pawel-reddit-okgsid2">{{Cite web |last=Low-Anything6975 |title=Reply analogizing Bambu's cloud restrictions to fencing off a public square |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/comment/okgsid2/ |website=Reddit |date=2026-05-07 |access-date=2026-05-11 |url-status=live}}</ref>

===User-Agent identity metadata===
The "falsified identity metadata" Bambu Lab calls "impersonation" is the HTTP User-Agent string the fork emits when contacting Bambu Cloud. That string is generated by Bambu Lab's own AGPL-licensed source code. The User-Agent setter is in <code>src/slic3r/Utils/Http.cpp</code>, & assembles its value from constants defined in <code>version.inc</code>. The relevant line in <code>Http.cpp</code> reads:
<blockquote>''::curl_easy_setopt(curl, CURLOPT_USERAGENT, SLIC3R_APP_NAME "/" SLIC3R_VERSION);''</blockquote><ref name="bambustudio-http-cpp">{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-11 |url-status=live}}</ref>
The constants in <code>version.inc</code> set the application name & version directly:
<blockquote>''set(SLIC3R_APP_NAME "BambuStudio")''

''set(SLIC3R_VERSION "02.06.01.55")''</blockquote><ref name="bambustudio-version-inc">{{Cite web |title=version.inc (SLIC3R_APP_NAME and SLIC3R_VERSION constants) |url=https://github.com/bambulab/BambuStudio/blob/master/version.inc |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>
Both files are governed by the BambuStudio LICENSE, which is AGPL-3.0.<ref name="bambustudio-license" /> A clean compile of unmodified upstream Bambu Studio emits a <code>User-Agent: BambuStudio/02.06.01.55</code> header on every HTTP request by default, because that is the value Bambu Lab itself wrote into its own published source. The same Reddit user made this point:
<blockquote>''User-Agent is not authentication. It is just self-declared client metadata. Any program can set any User-Agent. And the most important part: this comes directly from your own AGPL code.''</blockquote><ref name="pawel-reddit-okg9iih" />
Whichever branch of the severability dilemma Bambu Lab takes in the previous subsection, the impersonation framing relies on Bambu Lab's own AGPL-licensed code generating the very header Bambu Lab calls falsified.

===Other AGPL theories raised by the public record===
Three additional AGPL theories follow from the same facts. Each has weaker public-record support than the TOS-versus-AGPL collision & the User-Agent question above; each is identified here so the catalogue is complete, with the evidentiary gaps that any enforcement organization would need to close before relying on the theory.

[[GNU Affero General Public License|AGPL § 13]] (network copyleft) requires that a licensor running a modified version of an AGPL program as a network service offer all users interacting with it remotely an opportunity to receive the Corresponding Source.<ref name="agpl3-section13">{{Cite web |title=GNU Affero General Public License Version 3, Section 13 (Remote Network Interaction) |url=https://www.gnu.org/licenses/agpl-3.0.html#section13 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> Bambu Lab's May 7, 2026 blog post denies any § 13 obligation by treating Bambu Cloud as a separate private service.<ref name="bambu-blog-record-straight" /> The public record does not establish that Bambu Cloud's server-side software derives from AGPL components inherited from upstream Slic3r or PrusaSlicer; until that link is documented, § 13 attachment to Bambu Cloud is an open question, not an established violation.

AGPL § 1 defines "Corresponding Source" for a work in object code form as:
<blockquote>''all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.''</blockquote><ref name="agpl3-section1">{{Cite web |title=GNU Affero General Public License Version 3, Section 1 (Definitions) |url=https://www.gnu.org/licenses/agpl-3.0.html |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> The Bambu Studio AGPL source contains a runtime plugin loader declared in <code>src/slic3r/Utils/NetworkAgent.hpp</code> & implemented in <code>src/slic3r/Utils/NetworkAgent.cpp</code>; the loader brings in the proprietary <code>bambu_networking</code> plugin via standard dynamic-linking calls, & the function-pointer interface lives in the AGPL header <code>src/slic3r/Utils/bambu_networking.hpp</code>.<ref name="bambustudio-networkagent-hpp">{{Cite web |title=NetworkAgent.hpp (plugin loader header) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/NetworkAgent.hpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref><ref name="bambustudio-networkagent-cpp">{{Cite web |title=NetworkAgent.cpp (proprietary plugin loader) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/NetworkAgent.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref><ref name="bambustudio-bambu-networking-hpp">{{Cite web |title=bambu_networking.hpp (function-pointer interface) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/bambu_networking.hpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref> The FSF's GPL FAQ states that dynamically linked plug-ins that make function calls & share data structures with a host program "form a single combined program."<ref name="fsf-gpl-faq-plugins" /> Whether the AGPL source alone produces a binary functionally equivalent to Bambu Lab's official release requires a clean-compile demonstration that has not been publicly performed; the architectural facts are public, the practical effect is not yet documented.

AGPL § 6 (User-Product anti-Tivoization, parallel to GPLv3 § 6) requires that a licensor convey "Installation Information" sufficient to install & execute modified versions of the covered work on a User Product.<ref name="agpl3-section6">{{Cite web |title=GNU Affero General Public License Version 3, Section 6 (Conveying Non-Source Forms) |url=https://www.gnu.org/licenses/agpl-3.0.html#section6 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> Per Bambu Lab's open-source software disclosure page, the X1-series printer firmware is built on the Rockchip RV1126 SDK with Linux kernel & U-Boot components under GPLv2 (which has no anti-Tivoization clause), & the P1 / A1 series firmware uses an ESP32 SDK from Espressif Systems with no disclosed GPL components.<ref name="bambu-opensource-disclosure">{{Cite web |title=Open Source Software |url=https://wiki.bambulab.com/en/knowledge-sharing/open-source-software |website=Bambu Lab Wiki |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref> On those facts, AGPL § 6 / GPLv3 § 6 anti-Tivoization does not currently anchor a complaint against Bambu Lab printer firmware. The theory would reactivate only if a future firmware audit surfaced GPLv3 or AGPLv3 components.

===U.S. and EU consequences===
In the United States, the doctrine of copyright misuse bars enforcement of copyrights that are being misused. The Fourth Circuit recognized the defense in [https://www.courtlistener.com/opinion/546900/lasercomb-america-inc-v-job-reynolds/ Lasercomb America, Inc. v. Reynolds], 911 F.2d 970 (4th Cir. 1990), with the court holding:
<blockquote>''Since copyright and patent law serve parallel public interests, a "misuse" defense should apply to infringement actions brought to vindicate either right.''</blockquote><ref name="lasercomb-1990">{{Cite web |title=Lasercomb America, Inc. v. Reynolds, 911 F.2d 970 (4th Cir. 1990) |url=https://www.courtlistener.com/opinion/546900/lasercomb-america-inc-v-job-reynolds/ |website=CourtListener |access-date=2026-05-10 |url-status=live}}</ref>
The Ninth Circuit confirmed the doctrine in [https://www.courtlistener.com/opinion/744681/practice-management-information-corp-v-american-medical-assn/ Practice Management Information Corp. v. AMA], 121 F.3d 516 (9th Cir. 1997), holding that the AMA had used its copyright:
<blockquote>''in a manner violative of the public policy embodied in the grant of a copyright.''</blockquote><ref name="practice-management-1997">{{Cite web |title=Practice Management Information Corp. v. American Medical Ass'n., 121 F.3d 516 (9th Cir. 1997) |url=https://www.courtlistener.com/opinion/744681/practice-management-information-corp-v-american-medical-assn/ |website=CourtListener |access-date=2026-05-10 |url-status=live}}</ref> The Ninth Circuit quoted Lasercomb at 977 for that formulation & adopted copyright misuse as a defense to copyright infringement.<ref name="practice-management-1997" />
A defendant accused of copyright infringement on Bambu Studio code can raise the TOS-versus-AGPL conflict as a misuse defense.

In the European Union, [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009L0024 Software Directive 2009/24/EC, Article 8] provides:
<blockquote>''The provisions of this Directive shall be without prejudice to any other legal provisions such as those concerning patent rights, trade-marks, unfair competition, trade secrets, protection of semi-conductor products or the law of contract. Any contractual provisions contrary to Article 6 or to the exceptions provided for in Article 5(2) and (3) shall be null and void.''</blockquote><ref name="eu-software-directive-2009-24-ec">{{Cite web |title=Directive 2009/24/EC of the European Parliament and of the Council of 23 April 2009 on the legal protection of computer programs |url=https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009L0024 |website=EUR-Lex |publisher=European Union |date=2009-04-23 |access-date=2026-05-10 |url-status=live}}</ref>
The Court of Justice of the European Union confirmed in [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 SAS Institute Inc. v. World Programming Ltd], Case C-406/10 (Grand Chamber, May 2, 2012), that a software licensee's right to observe, study & test the program cannot be overridden by contract.<ref name="cjeu-c-406-10">{{Cite web |title=Case C-406/10, SAS Institute Inc. v World Programming Ltd, Judgment of the Court (Grand Chamber), 2 May 2012 |url=https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 |website=EUR-Lex |publisher=European Union |date=2012-05-02 |access-date=2026-05-10 |url-status=live}}</ref> Polish law transposes the Software Directive in the [https://eli.gov.pl/eli/DU/1994/83 Polish Copyright Act of February 4, 1994], with art. 75 protecting lawful-user observation, study & testing rights, & art. 76 declaring contract provisions that conflict with art. 75 sections 2 and 3 void.<ref name="polish-copyright-act-1994">{{Cite web |title=Ustawa z dnia 4 lutego 1994 r. o prawie autorskim i prawach pokrewnych |url=https://eli.gov.pl/eli/DU/1994/83 |website=Elektroniczny Dziennik Urzędowy |publisher=Government of Poland |date=1994-02-04 |access-date=2026-05-10 |url-status=live}}</ref> Whether art. 76 reaches a non-EU choice-of-law clause attempting to bypass these mandatory rules is a separate question that requires Polish-counsel briefing; the doctrinal point is that the rules are mandatory within Polish jurisdiction.

===Open-source licensing context: SFC v. Vizio===
The closest live U.S. analog to a manufacturer publishing copyleft client software with a proprietary cloud back-end is [[Software Freedom Conservancy v. Vizio]]. The case is proceeding in Orange County Superior Court, California; the [[Software Freedom Conservancy]] filed it in October 2021, on behalf of a consumer-purchaser theory of breach-of-contract enforcement of GPLv2 & LGPLv2.1 components in Vizio's smart TVs.<ref name="sfc-vizio-case-page">{{Cite web |title=Software Freedom Conservancy v. Vizio Inc. |url=https://sfconservancy.org/copyleft-compliance/vizio.html |website=Software Freedom Conservancy |access-date=2026-05-10 |url-status=live}}</ref>

On December 4, 2025, the trial court issued a tentative ruling granting SFC's motion on a direct-contract theory: the court found that a direct contract was formed, with Vizio under a duty to provide complete and corresponding source code, when SFC's systems administrator, Paul Visscher, requested source code for a Vizio TV that SFC had purchased.<ref name="sfc-vizio-tentative-2025">{{Cite web |title=Tentative Vizio Ruling in Favor of SFC |url=https://sfconservancy.org/news/2025/dec/04/tentative-vizio-ruling-in-favor-of-sfc/ |website=Software Freedom Conservancy |date=2025-12-04 |access-date=2026-05-10 |url-status=live}}</ref> On December 23, 2025, Judge Leal granted Vizio's motion for summary adjudication on a peripheral installation-keys point, ruling that GPLv2 does not impose a duty on a licensee to provide information permitting reinstallation of modified software such that the device continues to function properly. SFC's December 24, 2025 commentary on the ruling characterized the issue as orthogonal to its core copyleft-enforcement theory, noting:
<blockquote>''SFC has never held the position, nor do we today hold the position, that any version of the GPL (even including GPLv3!) require "that the device continues to function properly" after a user installs their modified version of the copyleft components.''</blockquote><ref name="sfc-vizio-msa-2025">{{Cite web |title=Vizio MSA Irrelevant Ruling |url=https://sfconservancy.org/news/2025/dec/24/vizio-msa-irrelevant-ruling/ |website=Software Freedom Conservancy |date=2025-12-24 |access-date=2026-05-10 |url-status=live}}</ref> On January 26, 2026, SFC reported that the trial had been postponed because of an older case taking docket priority.<ref name="sfc-vizio-trial-delay-2026">{{Cite web |title=Some Unfortunate Delays in our Struggle for Copyleft Justice |url=https://sfconservancy.org/blog/2026/jan/26/delay-in-start-of-vizio-trial/ |website=Software Freedom Conservancy |date=2026-01-26 |access-date=2026-05-10 |url-status=live}}</ref> The trial is now scheduled for August 10 to August 19, 2026.<ref name="sfc-vizio-case-page" /><ref name="sfc-vizio-trial-delay-2026" /> Industry counsel commentary tracked these rulings as a significant endorsement of consumer-purchaser standing to enforce GPL terms as a contract.<ref name="dlapiper-vizio-jan-2026">{{Cite web |title=SFC v. Vizio ruling on General Public License compliance: Key takeaways |url=https://www.dlapiper.com/en/insights/publications/2026/01/sfc-v-vizio-ruling-on-general-public-license-compliance-key-takeaways |website=DLA Piper |date=2026-01-05 |access-date=2026-05-10 |url-status=live}}</ref><ref name="bakerbotts-vizio-may-2026">{{Cite web |title=When Consumers Enforce Open Source: The SFC v. Vizio Case |url=https://www.bakerbotts.com/thought-leadership/publications/2026/may/when-consumers-enforce-open-source |website=Baker Botts |date=2026-05-01 |access-date=2026-05-10 |url-status=live}}</ref>

A separate doctrinal anchor for the AGPL § 7 ¶ 4 further-restrictions argument is Bradley M. Kuhn's expert report in <code>Neo4j, Inc. v. PureThink, LLC and John Mark Suhy</code>, 5:18-cv-07182 (N.D. Cal.). Kuhn served as third-party expert for the defendants & analyzed AGPL § 7's right to remove "Commons Clause"-style restrictions.<ref name="sfc-kuhn-neo4j-2023">{{Cite web |title=SFC's Policy Fellow Files Expert Report in Neo4j v. PureThink |url=https://sfconservancy.org/news/2023/feb/09/kuhn-neo4j-purethink-expert-report/ |website=Software Freedom Conservancy |date=2023-02-09 |access-date=2026-05-10 |url-status=live}}</ref> The FSF filed an amicus brief in Neo4j v. Suhy on March 3, 2025, in the Ninth Circuit (Case No. 24-5538), arguing that AGPL § 7's prohibition on further restrictions invalidates Commons Clause-style contractual overlays.<ref name="fsf-amicus-neo4j-2025">{{Cite web |title=FSF submits amicus brief in Neo4j v. Suhy |url=https://www.fsf.org/news/fsf-submits-amicus-brief-in-neo4j-v-suhy |website=Free Software Foundation |date=2025-03-03 |access-date=2026-05-10 |url-status=live}}</ref> As of publication, no appellate court has yet ruled on the AGPL § 7 ¶ 4 question.

===German GPL enforcement (Welte-line cases)===
European GPL-as-contract enforcement has run through a line of German trial-court rulings tied to programmer Harald Welte, the maintainer of <code>netfilter</code>/<code>iptables</code>. In September 2006 the Frankfurt District Court (Landgericht Frankfurt) ruled against D-Link Germany GmbH, finding that the company had distributed a Linux-based network-attached-storage device incompliant with the GNU General Public License and ordering D-Link to reimburse expenses incurred in connection with the test purchase, re-engineering and legal representation.<ref name="gpl-violations-dlink-2006">{{Cite web |last=Welte |first=Harald |title=gpl-violations.org project prevails in court case on GPL violation by D-Link |url=https://web.archive.org/web/20151120221400/http://gpl-violations.org/news/20060922-dlink-judgement_frankfurt/ |website=gpl-violations.org |date=2006-09-22 |access-date=2026-05-11 |url-status=live}}</ref> In June 2013 the Hamburg Regional Court (Landgericht Hamburg) ruled against Fantec GmbH, holding that a vendor distributing a media player containing <code>iptables</code> code under GPLv2 is itself responsible for verifying GPL compliance and cannot rely on a supplier's assurance.<ref name="gpl-violations-fantec-2013">{{Cite web |last=Welte |first=Harald |title=Regional court Hamburg judgement against FANTEC |url=https://web.archive.org/web/20151120221400/http://gpl-violations.org/news/20130626-fantec_judgement/ |website=gpl-violations.org |date=2013-06-26 |access-date=2026-05-11 |url-status=live}}</ref> Both cases concern GPLv2 rather than AGPLv3, but the contract-enforceability principle they apply translates by analogy: German trial courts have treated copyleft terms as enforceable obligations on a vendor that distributes copyleft binaries. Bambu Lab does not currently distribute Bambu Studio binaries through Germany under any contractual notice that overrides AGPL § 10; the Welte cases are cited as comparable precedent rather than as authority controlling the Bambu Lab matter.

===John Deere AGPL: no filed litigation, SFC v. Vizio is the operative analog===
A widely circulated assumption in repair-advocacy discussion is that there is a "John Deere AGPL precedent" that supports community enforcement against a manufacturer who publishes copyleft code & locks down the product. There is no such case in litigation form. The Software Freedom Conservancy described its John Deere compliance work in a March 16, 2023 blog post stating that Deere had failed to provide complete corresponding source for more than two years after SFC's first request; the post does not announce a filed complaint, & no SFC litigation against John Deere has been publicly docketed since.<ref name="sfc-john-deere-2023">{{Cite web |title=John Deere's GPL Violations |url=https://sfconservancy.org/blog/2023/mar/16/john-deere-gpl-violations/ |website=Software Freedom Conservancy |date=2023-03-16 |access-date=2026-05-10 |url-status=live}}</ref> The right-to-repair litigation involving John Deere has run on different statutes: [[DMCA Section 1201|DMCA § 1201]] exemption petitions, FTC enforcement, & the 2023 American Farm Bureau memorandum of understanding. Those are repair-policy fights, not AGPL enforcement actions. The actual analog for the Bambu Lab pattern, copyleft client software paired with a proprietary cloud back-end on consumer hardware, is SFC v. Vizio.

===Who can enforce AGPL against Bambu Lab===
Pawel Jarczak personally cannot bring an AGPL enforcement action against Bambu Lab on his own. The right to sue for AGPL violations belongs to the original authors whose code Bambu Lab built on top of: the [https://github.com/slic3r/Slic3r Slic3r contributors],<ref name="slic3r-repo" /> Prusa Research & the [https://github.com/prusa3d/PrusaSlicer/blob/master/LICENSE PrusaSlicer contributors],<ref name="prusaslicer-license" /> & the [https://github.com/SoftFever/OrcaSlicer/blob/main/LICENSE.txt SoftFever / OrcaSlicer maintainers].<ref name="softfever-orcaslicer-license" /> Jarczak's role in any formal complaint is reporter & witness, not plaintiff.

The institutional capacity for AGPL enforcement on these facts sits with several organizations:

*'''[[Software Freedom Conservancy]] (SFC).''' SFC operates the only U.S.-based copyleft enforcement program currently litigating consumer-purchaser claims against a hardware manufacturer (the Vizio matter). Its [https://sfconservancy.org/copyleft-compliance/ copyleft-compliance program] handles strategic enforcement; Bradley M. Kuhn's AGPL § 7 expert report from <code>Neo4j v. PureThink</code> remains the strongest published doctrinal anchor for the Bambu Lab TOS-versus-AGPL argument.<ref name="sfc-copyleft-compliance">{{Cite web |title=Copyleft Compliance Projects |url=https://sfconservancy.org/copyleft-compliance/ |website=Software Freedom Conservancy |access-date=2026-05-10 |url-status=live}}</ref><ref name="sfc-kuhn-neo4j-2023" />
*'''Free Software Foundation (FSF).''' FSF drafted the AGPL & operates the [https://www.fsf.org/licensing/ Licensing & Compliance Lab]. FSF will not be the lead enforcement vehicle here because FSF does not hold copyright in BambuStudio; it can supply doctrinal authority, amicus filings, & public statements. FSF filed an amicus brief in <code>Neo4j v. Suhy</code> on March 3, 2025.<ref name="fsf-licensing">{{Cite web |title=Licensing & Compliance Lab |url=https://www.fsf.org/licensing/ |website=Free Software Foundation |access-date=2026-05-10 |url-status=live}}</ref><ref name="fsf-amicus-neo4j-2025" />
*'''Free Software Foundation Europe (FSFE).''' FSFE convenes the [https://fsfe.org/activities/ln/ln.en.html European Legal Network] of free-software lawyers & is geographically appropriate to a Polish maintainer.<ref name="fsfe-legal-network">{{Cite web |title=Legal Network |url=https://fsfe.org/activities/ln/ln.en.html |website=Free Software Foundation Europe |access-date=2026-05-10 |url-status=live}}</ref>
*'''Electronic Frontier Foundation (EFF).''' Not for AGPL enforcement, but for the maintainer's defensive posture. The [https://www.eff.org/issues/coders Coders' Rights Project] works on the legal issues developers face under DMCA, CFAA, & similar computer-crime laws & provides public guidance for reverse engineering & vulnerability disclosure.<ref name="eff-coders-rights">{{Cite web |title=Coders' Rights Project |url=https://www.eff.org/issues/coders |website=Electronic Frontier Foundation |access-date=2026-05-10 |url-status=live}}</ref>
*'''iFixit & The Repair Association.''' Press reach & [[right to repair]] coalition framing. Neither litigates AGPL; both have established media reach & legislative relationships & have publicly tracked the Bambu Lab takedown in their channels.

===Consequences for FOSS forks of corporate-sponsored AGPL projects===
Louis Rossmann publicly pledged $10,000 toward Jarczak's legal defense if Bambu Lab proceeded with a lawsuit in a May 9, 2026 YouTube video,<ref name="rossmann-youtube-pledge" /> & directed an explicit public statement at the company's leadership; Tom's Hardware reported the pledge on May 10, 2026.<ref name="tomshardware-rossmann-pledge" /> The 3D-printing trade press (3Druck, XDA, Tom's Hardware, Manufactur3D) covered the dispute as the immediate flashpoint. Enforcement organizations including the Free Software Foundation, Software Freedom Conservancy, FSFE, and Electronic Frontier Foundation have jurisdiction to bring AGPL claims, but no enforcement action involving Bambu Lab had been announced as of publication. The same question reaches every IoT-device vendor who ships AGPL or GPLv3 components with companion mobile apps & cloud back-ends, & every consumer-electronics company publishing open-source slicers, control panels, or firmware while routing user functionality through proprietary remote services.

==Impact on professional users and privacy concerns==

===Impact on professional users and print farms===
The restrictions imposed by the new authorization system create operational challenges for professional users who kept their printers signed into the cloud:

*Print farms can no longer use custom automation systems to manage multiple printers
*Workflows built around third-party software have to be completely redesigned
*The requirement to manually export and import files through Bambu Connect creates additional labor
*Integration with existing business systems and workflows becomes more difficult or impossible
*Print-farm operators report that the new workflow disrupts their fleet-management workflows<ref name="bambulab-forum-135400/9" />
Print-farm operators can avoid these restrictions by operating their printers in LAN-only mode rather than signing them into Bambu Cloud.

===Privacy and data-collection concerns===

The shift toward mandatory use of Bambu Studio and Bambu Connect raises several privacy and data collection concerns:

*All printer operations must now pass through Bambu's cloud infrastructure when using cloud mode
*User print data, including file names and print settings, becomes visible to Bambu when cloud is used
*Operational data is processed through Bambu's servers while on a different network. The camera feed, on the other hand, is always peer-to-peer.
*Users have limited visibility into how their data is collected, stored, and used in the cloud
*The system creates dependence on Bambu's cloud services availability for basic printer functionality<ref name=":4" />

While Bambu Lab maintains that cloud processing is necessary for security and functionality, community members argue this represents unnecessary data collection that could be handled locally.<ref name="bambulab-forum-134549/12" /> Users who do not require cloud-based features can disable cloud connectivity and operate the printer through LAN mode.

Users who do not want their print data routed through Bambu's cloud infrastructure can operate their printers in LAN-only mode.

==Customer reactions==

Customer reactions on community forums and Reddit were negative.<ref>{{Cite web |last=@hho |date=2025-01-15 |title=Bambu Studio 1.10.2 Public Beta |url=https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/4 |url-status=live |archive-url=https://ghostarchive.org/archive/ahrz6 |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Improvements Introduce authorization and authentication protection mechanism: Bambu Studio now supports signing and encrypting control commands sent to printers when the printer supports authorization and authentication protection. The printer will determine whether the commands can be executed. Hmmm. This reads suspiciously vague. It could mean that Bambu printers get an onboard permission handling, so that you can "lock down" your printer and set what commands can be run. But it could also mean that Bambu printers in (or of?) the future will only run Gcode encrypted and signed by Bambu Studio…}}</ref><ref>{{Cite web |last=@iranintoavan |title=Firmware Update Introducing New Authorization Control System |url=https://old.reddit.com/r/BambuLab/comments/1i2psvz/firmware_update_introducing_new_authorization/ |url-status=live |archive-url=http://web.archive.org/web/20250403012526/https://old.reddit.com/r/BambuLab/comments/1i2psvz/firmware_update_introducing_new_authorization/ |archive-date=2025-04-03 |access-date=2025-05-01 |website=Old [[Reddit]]}}</ref> Bambu Lab has historically pushed cloud-based printer interaction while offering limited LAN mode functionality<ref name=":4" />. Many customers argue that the security issues this locked-down firmware claims to address are actually consequences of the company's cloud-based design choices rather than inherent risks of local network control.<ref name="bambulab-forum-134549/12" /> After the announcement, Bambu Lab's Trustpilot page recorded a wave of one-star reviews citing the firmware restrictions as the reason for the rating.<ref>{{Cite web |title=Bambu Lab |url=https://www.trustpilot.com/review/bambulab.com?sort=recency |archive-url=https://web.archive.org/web/20250119162028/https://www.trustpilot.com/review/bambulab.com?sort=recency |archive-date=2025-01-19 |website=[[Trustpilot]]}}</ref>

As of publication, '''no changes have been announced for owners who never sign their printers into the Bambu cloud service'''. Past firmware updates allowed pairing the slicer via IP address and access key and performing offline firmware updates without ever signing the printer into the cloud, keeping local functionality unchanged.<ref name="firmware-update-introducing-new-authorization-control-system-2" />

==Comparisons to similar practices by other companies==

Bambu Lab's new authorization & authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as [[HP]] & [[Epson]], who have faced backlash & litigation over [[digital rights management]] (DRM) practices in 2D printers. The Federal Trade Commission's May 2021 report ''Nixing the Fix'' described firmware-mediated cartridge restrictions as one of the recurring repair-policy issues the agency examined, & noted that the Magnuson-Moss Warranty Act prohibits a printer manufacturer from conditioning its warranty on the purchaser's use of the manufacturer's branded ink.<ref name="ftc-nixing-the-fix">{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |author=Federal Trade Commission |url=https://www.ftc.gov/system/files/documents/reports/nixing-fix-ftc-report-congress-repair-restrictions/nixing_the_fix_report_final_5521_630pm-508_002.pdf |website=Federal Trade Commission |date=2021-05-06 |access-date=2026-05-10 |url-status=live}}</ref> HP settled an "Ink Cartridge Monopoly" class action for $1.5 million in 2018, with settlement payments to class members distributed in late 2019,<ref name="hp-2019-class-action">{{Cite web |last=Spicer |first=Christina |title=HP Ink Cartridge Monopoly Class Action Lawsuit Settles for $1.5M |url=https://topclassactions.com/lawsuit-settlements/lawsuit-news/hp-ink-cartridge-monopoly-class-action-lawsuit-settles-1-5m/ |website=Top Class Actions |date=2019-11-26 |access-date=2026-05-10 |url-status=live}}</ref> & in September 2022 reached a Euroconsumers settlement covering Dynamic Security firmware practices in the EU.<ref name="hp-euroconsumers-2022">{{Cite web |title=HP and Euroconsumers settle on Dynamic Security |author=Euroconsumers |url=https://www.euroconsumers.org/hp-and-euroconsumers-settle-on-dynamic-security/ |website=Euroconsumers |date=2022-09-07 |access-date=2026-05-10 |url-status=live}}</ref> A March 19, 2025 Ars Technica account of the U.S. HP class-action settlement reported that owners of 21 specific HP printer models can opt out of Dynamic Security firmware updates as part of the resolution.<ref name=":5" /> Epson faced its own consumer class action over allegations that firmware updates rendered third-party cartridges unusable.<ref name="epson-mondigo-class-action">{{Cite web |last=Cohen |first=Steven |title=Epson Class Action Alleges Printer Ink Defect |url=https://topclassactions.com/lawsuit-settlements/consumer-products/electronics/epson-class-action-alleges-printer-ink-defect/ |website=Top Class Actions |date=2020-05-19 |access-date=2026-05-10 |url-status=live}}</ref> These comparisons address:
*'''Forced updates''': Firmware updates have rendered third-party ink cartridges incompatible, forcing users to purchase proprietary consumables.
*'''Restricted features''': Scanner / printer combos that will not scan if the ink is empty.
*'''Consumer backlash''': Users criticized these updates as anti-consumer, with some pursuing {{Wplink|class action}} lawsuits for deceptive practices.<ref name=":5" />

A parallel from the 3D-printing industry is the 3D-printer manufacturer [[MakerBot]], whose 2012 shift from open-source, DIY-focused machines to closed-source, proprietary machines drove customers to less-expensive open-source competitors, as documented by Hackaday's 2016 obituary of the company.<ref>{{Cite web |last=Benchoff |first=Brian |date=2016-04-28 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=2025-12-08 |access-date=2025-05-01 |website=[[Hackaday]]}}</ref> MakerBot was also accused of asserting ownership over publicly available, open-source designs uploaded to its 3D print repository, Thingiverse.<ref>{{Cite web |last=Biggs |first=John |date=2014-05-28 |title=MakerBot Responds To Critics Who Claim It Is Stealing Community IP |url=https://techcrunch.com/2014/05/28/makerbot-responds-to-critics-who-claim-it-is-stealing-community-ip/ |url-status=live |archive-url=http://web.archive.org/web/20251111041317/https://techcrunch.com/2014/05/28/makerbot-responds-to-critics-who-claim-it-is-stealing-community-ip/ |archive-date=2025-11-11 |access-date=2025-05-01 |website=[[TechCrunch]]}}</ref>

==TOS restricting development of third party devices and accessories==

Archived discussion threads from January 2024 confirm that the § 3.1 clause has been part of the Bambu Lab Terms of Use at least since then.<ref>{{Cite web |last=@X1Plus |title=X1plus community Bambu Lab firmware - A win for everyone? |url=https://www.reddit.com/r/3Dprinting/comments/18zaay0/x1plus_community_bambu_lab_firmware_a_win_for/kggqg4n/ |url-status=live |archive-url=https://web.archive.org/web/20260222212657/https://old.reddit.com/r/3Dprinting/comments/18zaay0/x1plus_community_bambu_lab_firmware_a_win_for/kggqg4n/ |archive-date=2026-02-22 |access-date=2025-05-01 |website=[[Reddit]]}}</ref> Community reaction was split: some readers argued the clause is intended to restrict third-party development, while others characterized it as standard boilerplate in vendor terms.<ref>{{Cite web |last=@mflexx |title=Not updated. And this part is shared by pretty much every company that has ever existed on this planet. That's just blatant karma farming at this point. |url=https://www.reddit.com/r/BambuLab/comments/1ibhhg7/updated_tos_shots_fired/m9i78kj/ |url-status=live |archive-url=https://web.archive.org/web/20260222212738/https://old.reddit.com/r/BambuLab/comments/1ibhhg7/updated_tos_shots_fired/m9i78kj/ |archive-date=2026-02-22 |access-date=2025-05-01 |website=[[Reddit]]}}</ref>

Bambu Lab's Terms of Use § 3.1 states:
<blockquote>''3.1 You may not use Bambu Lab technology or Bambu Lab intellectual property to develop software or design, develop, manufacture, sell, or licence third-party devices/accessories associated with Bambu Lab Product without Bambu Lab's prior consent.''</blockquote><ref name=":2" />

==See also==

*[[Forced account]]
*[[Right to repair]]
*[[Terms of Service]]
*[[Software Freedom Conservancy v. Vizio]]
*[[GNU Affero General Public License]]
*[[Software Freedom Conservancy]]

==References==
{{reflist}}

[[Category:Bambu Lab]]
[[Category:Feature Ransom]]
[[Category:3D printers]]
[[Category:Open source]]

Bambu Lab Authorization Control System

2026-05-11T05:49:51Z

Louis: expanded the agpl-vs-tos legal analysis with primary text from §§ 1, 6, 7, 10, 13 and bambu's own tos §§ 3.1, 3.4, 3.5; added the may 2026 cease-and-desist timeline from pawel jarczak's public sources (3 reddit replies, github readme, xda + tom's + 3druck + manufactur3d coverage); added sfc v. vizio context with the dec 4 tentative ruling, dec 23 msa ruling, august 2026 trial; added rossmann's may 9 youtube pledge and tom's hardware coverage; deleted a fabricated sfc blockquote, a spurious de...

{{IncidentCargo
|Company=Bambu Lab
|StartDate=2025-01-16
|Status=Active
|Type=Post-purchase terms change
|Description=January 2025 firmware change restricted third-party slicers; April 2026 private cease-and-desist against AGPL fork maintainer Pawel Jarczak.
}}

On January 16, 2025, the 3D-printer manufacturer '''[[Bambu Lab]]''' announced that future firmwares for its 3D printers would introduce an authorization & authentication mechanism for printer connection & control, [[Deceptive language frequently used against consumers|in the name of security]].<ref name="firmware-update-introducing-new-authorization-control-system-2">{{Cite web |last=Bambu Kidd |date=2025-01-16 |title=Firmware Update Introducing New Authorization Control System |url=https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/ |url-status=live |archive-url=https://ghostarchive.org/archive/qwL63 |archive-date=2026-03-07 |website=[[Bambu Lab]] Blog}}</ref> The change restricted the use of third-party accessories & slicers such as Panda Touch & OrcaSlicer, & it gated print initiation, motion control, fan & hotend control, AMS configuration, calibrations, remote video, & firmware upgrade behind a Bambu-issued authentication path.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> Bambu Lab also publishes its own slicer, [https://github.com/bambulab/BambuStudio Bambu Studio], under the [[GNU Affero General Public License|AGPL-3.0]],<ref name="bambustudio-license">{{Cite web |title=BambuStudio LICENSE (AGPL-3.0 verbatim) |url=https://github.com/bambulab/BambuStudio/blob/master/LICENSE |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref> while its [[Terms of Service|Terms of Use]] § 3.4 forbid users to modify, copy, reverse engineer, or create derivatives of "the Product."<ref name=":2">{{Cite web |date=2024-04-24 |title=Terms of Use |url=https://bambulab.com/en-us/policies/terms |url-status=live |archive-url=https://ghostarchive.org/archive/vPu9I |archive-date=2026-03-09 |access-date=2025-05-01 |website=[[Bambu Lab]]}}</ref> In April 2026, Bambu Lab sent a private cease-and-desist demand to a Polish community fork maintainer, Pawel Jarczak, who had restored direct printer control on top of that AGPL source; on May 7, 2026, Bambu Lab published a blog post recharacterizing the dispute as "impersonation" through "falsified identity metadata" rather than as a question about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref><ref name="jarczak-readme">{{Cite web |last=Jarczak |first=Pawel |title=OrcaSlicer-bambulab — This is the end…. |url=https://github.com/jarczakpawel/OrcaSlicer-bambulab |url-status=live |archive-url=https://web.archive.org/web/20260430001537/https://github.com/jarczakpawel/OrcaSlicer-bambulab |archive-date=2026-04-30 |access-date=2026-05-04 |website=[[GitHub]]}}</ref>

==Controversy regarding firmware updates==
[[File:Bambu tos screenshot.png|alt=bambu terms stating print jobs may not function properly if update is not performed to new firmware which is highly limiting. |thumb|Bambu terms regarding printer functionality & potential for disrupted print jobs if users do not update to a new firmware that radically restricts the autonomy of the owner of the printer]]

===Potential for remote disabling of printers===
A concern raised by the community revolves around the wording in Bambu Lab's [[Terms of Service]] (ToS) and firmware update announcements. Critics and users argue that the phrasing leaves open the possibility for the manufacturer to [[Remote disabling|remotely disable]] printers that are not updated to the latest firmware. Specifically, Bambu Lab's ToS warns that printers may block new print jobs if updates are not applied,<ref name=":2" /> which some users interpret as a potential pathway for forced obsolescence.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> While defenders of Bambu Lab point out that offline modes such as SD-card printing and [[wikipedia:Local_area_network|LAN]]-only setups would remain functional, others point out that the ToS do not explicitly limit this restriction to [[Cloud (service)|cloud]]-based printing. This ambiguity has led to speculation that Bambu Lab could enforce broader limitations, effectively rendering printers inoperable for users who choose not to update.<ref name="theverge-bambu-2025">{{Cite web |last=Hollister |first=Sean |date=2025-01-22 |title=Here's what Bambu will — and won't — promise after its controversial 3D printer update |url=https://www.theverge.com/2025/1/21/24349031/bambu-3d-printer-update-authentication-filament-subscription-lock-answers |url-status=live |access-date=2025-05-01 |website=The Verge |archive-url=http://web.archive.org/web/20251122143504/https://www.theverge.com/2025/1/21/24349031/bambu-3d-printer-update-authentication-filament-subscription-lock-answers |archive-date=2025-11-22}}</ref>

====Editing of initial announcement====
Bambu users were concerned they would not be able to use their printer if they did not install this update, due to the wording of the blog and the ToS.<ref>[[:File:Bambu tos screenshot.png]]</ref> This caused confusion since users report that Bambu's blog post dated January 16, 2025<ref name="firmware-update-introducing-new-authorization-control-system-2" /> includes the FAQ entry:
<blockquote>''What happens if I never upgrade to this firmware?''

''You may continue using an older firmware version that does not include the new security updates; however, this means the printers may miss out on important security fixes or bug patches included in newer versions. We highly encourage updating to the latest firmware version for the best experience and enhanced security.''</blockquote>However, '''this was not present on the day of the announcement.''' A snapshot of their webpage from archive.is demonstrates this section did not exist on the day of the announcement, when community members voiced their concerns.<ref name="firmware-update-introducing-new-authorization-control-system-2" /><ref>[[:File:2024-01-16-Firmware Update Introducing New Authorization Control System.pdf]]</ref> Bambu's response to community feedback<ref>{{Cite web |last=@Spaghetti Monster |date=2025-01-20 |title=Updates and Third-Party Integration with Bambu Connect |url=https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |url-status=live |archive-url=https://ghostarchive.org/archive/cIejw |archive-date=2026-03-30 |access-date=2025-05-01 |website=Bambu Lab Blog}}</ref> references ''"social media posts spreading baseless allegations and untrue claims about Bambu Lab",'' including ''"Firmware updates will block your printer's ability to print.",'' without mentioning the context for those allegations. The context for those allegations was the lack of inclusion of the ''"What happens if I never upgrade to this firmware?"'' in Bambu's initial announcement alongside their stated terms of service.

After the edit, the announcement header reads '''Updated: January 17, 2025''' and notes that additional details and FAQs (including the "What happens if I never upgrade to this firmware?" entry) were added.

The earliest archive.is snapshot of the announcement, dated January 16, 2025 17:31 UTC,<ref name="firmware-update-introducing-new-authorization-control-system-22">{{Cite web |last=@BambuKidd |date=2025-01-16 |title=Firmware Update Introducing New Authorization Control System |url=https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/ |url-status=live |archive-url=https://ghostarchive.org/archive/qwL63 |archive-date=2026-03-07 |access-date=2025-05-01 |website=[[Bambu Lab]] Blog}}</ref> contains two passages about staying on the old firmware. Under "Important Information for End Users":
<blockquote>''2. Old Firmware Option: Users who decide to use an older firmware version can still use the previous or new versions of Bambu Studio and Bambu Handy without restrictions.''</blockquote>
Under "Information for OrcaSlicer users":
<blockquote>''1. You can continue using your X Series 3D printer with the older firmware version (which does not include Authorization Features). 2. If you choose to upgrade to the firmware version with Authorization Features, you must download and install Bambu Connect (a printer control software).''</blockquote>
The FAQ section was added after the initial blog post publication and is noted as an update in the announcement header.

===Debate over "bricking" terminology===
The debate has also extended to the definition of "bricking". Some community members assert that if a printer is unable to accept new print jobs without an update, it effectively becomes non-functional and qualifies as being "bricked." Others counter that as long as certain offline functionalities remain (such as SD-card printing) the term does not accurately apply.<ref name="theverge-bambu-2025" />

===Privacy policy issues===
Bambu Lab's privacy policy describes that when a user submits a print job through Bambu cloud, Bambu may forward configuration information, printing settings, model picture, plate thumbnails and G-code files (referred to in the policy as "Printing Files"), and when the print history reprinting feature is enabled, may store started times, finished times, and filament consumption.<ref name=":6">{{Cite web |date=2025-03-25 |title=Privacy Policy |url=https://bambulab.com/en-us/policies/privacy |url-status=live |archive-url=https://ghostarchive.org/archive/0XOv5 |archive-date=2026-03-10 |access-date=2025-05-01 |website=[[Bambu Lab]]}}</ref> The privacy policy webpage is not present in the Wayback Machine.<ref name=":6" />

===Community strategies to deal with risks===
Users have discussed strategies to avoid possible disruptions, including:
*Operating printers exclusively in offline modes.
*Using LAN connections or VPN setups: this requires an access key from the printer (previously, you could use your cloud credentials over LAN).
*Exploring alternative firmware or third-party scripts to restore full functionality.<ref name="theverge-bambu-2025" />

==Bambu Lab's justification and rebuttal==
Bambu Lab has stated that the authorization system is in place in order to protect against "remote hacks," "printer exposure," and "abnormal traffic or attacks." The cited security incidents have specific context:

*The "remote hacks" cited as an example in the article followed a reported security vulnerability in a 3D printer product; according to Bitdefender's reporting, the researcher infected machines to display a harmless message in order to publicize the unpatched flaw.<ref>{{Cite web |last=Cluley |first=Graham |date=2024-03-01 |title=Someone is hacking 3D printers to warn owners of a security flaw |url=https://www.bitdefender.com/en-au/blog/hotforsecurity/someone-is-hacking-3d-printers-to-warn-owners-of-a-security-flaw?ref=blog.bambulab.com |url-status=live |archive-url=https://web.archive.org/web/20260216002646/https://www.bitdefender.com/en-au/blog/hotforsecurity/someone-is-hacking-3d-printers-to-warn-owners-of-a-security-flaw?ref=blog.bambulab.com |archive-date=2026-02-16 |access-date=2025-05-01 |website=[[Bitdefender]]}}</ref>
*In the article cited about printer exposure, the hack was carried out largely because of user misconfiguration.<ref>{{Cite web |last=Ms. Smith |date=2018-09-05 |title=Over 3,700 exposed 3D printers open to remote attackers |url=https://www.csoonline.com/article/566223/over-3700-exposed-3d-printers-open-to-remote-attackers.html?ref=blog.bambulab.com |url-status=live |archive-url=https://web.archive.org/web/20260216002556/https://www.csoonline.com/article/566223/over-3700-exposed-3d-printers-open-to-remote-attackers.html?ref=blog.bambulab.com |archive-date=2026-02-16 |access-date=2025-05-01 |website=[[CSO]]}}</ref>
*The "abnormal traffic" can be mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.<ref>{{Cite web |title=Summary of Security Incident Responses and Abnormal Cloud Traffic |url=https://wiki.bambulab.com/en/security-incidents-cloud-traffic?ref=blog.bambulab.com |url-status=live |archive-url= |archive-date= |access-date=2025-05-01 |website=[[Bambu Lab]] Wiki}}</ref>
*"Other malicious devices in the LAN" can be partially mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.<ref>{{Cite web |last=@SpaghettiMonster |date=2022-11-25 |title=Answering network security concerns for our printers |url=https://blog.bambulab.com/answering-network-security-concerns/ |url-status=live |archive-url=https://ghostarchive.org/archive/CE0Ii |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Blog}}</ref>

==Issues with LAN mode requiring authorization==
[[File:Bambu Connect App - Lan Device Discovery without Bambu Login.png|thumb|Bambu Connect App - Lan Device Discovery without Bambu Login]]
Bambu Lab printers have the ability to be controlled over both cloud and LAN. This allowed users to integrate their printers into private networks and maintain full control without having to rely on the manufacturer's server while also allowing cloud access. The new authorization system mandates that even LAN-based operations must go through an authentication process using Bambu Connect to retain full control.<ref name="bambu-connect">{{Cite web |last=@Nil.lin |title=Bambu Connect (beta) |url=https://wiki.bambulab.com/en/software/bambu-connect |url-status=live |archive-url=https://ghostarchive.org/archive/CVCtK |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Wiki}}</ref> Full local access is still possible and unchanged for those not using the cloud.

This change has drawn criticism for many reasons:
*'''Privacy concerns''': Requiring authentication for LAN mode raises concerns about data being unnecessarily exposed to Bambu Lab's servers, even for local-only operations, though previously, the printer was also connected and could be controlled by the cloud even when sending prints locally.
**Confidentiality required by US Law: this is in conflict with users that have to comply with internal U.S. government classified information handling regulations.
*'''Loss of offline independence while also using cloud''': Before, users could have hybrid offline setups. The requirement for authentication removes this option unless users revert to older firmware versions; Bambu Lab initially indicated rollback would not be permitted, though The Verge later reported that users could still downgrade and use LAN access keys while signed into the cloud.
*'''Increased complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control while retaining cloud functionality.<ref name=":4">{{Cite web |last=@edlboston |date=2023-01 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Yes, I know about the LAN mode. But as has been stated by many people, things like the camera will not work, nor will the Handy app. There is no technical reason that these are bound to the cloud. This is the problem and why I titled this FULL Non-Cloud Network.}}</ref>

*LAN-Only mode in Orca Slicer is implemented by passing API Calls to the installed proprietary Bambu Network Plug-In (unlike BTT and other solutions that did indeed communicate with printer directly via MQTT protocol).
*Plug-In provides controls for Printers "Critical Operations" (as classified by the Firmware Announcement article) and displays these controls within the window of Orca Slicer.
*Using intermediary Plug-In does not manifest as "direct access through network plugin". It is still a Proxy communication, even if user experience is presented as direct communication (same slicer window).
*Bambu Connect moves the Network Plug-In functionality outside of the window of Orca Slicer thus appearing as separate window and presents the appearance of "indirect" communication channel to the printer.
*While the user experience is different, the flow remains unchanged Orca Slicer slices model -> Orca Slicer Calls API of Bambu Proprietary Software -> Bambu Proprietary Software controls the printer.

Additionally, Bambu Connect software (downloaded and installed in January 2025, before the backlash response) supports adding LAN-Only printers without requiring Bambu Account authentication, the same behavior as the Network Plugin used in Orca Slicer.

===Precedents and comparisons===
Critics have likened this potential functionality to similar cases in other industries where manufacturers remotely restrict product features. A documented example is [[HP]]'s printer firmware updates that [[HP Instant Ink|rendered third-party ink cartridges unusable]], which became the subject of a class-action settlement.<ref name=":5">{{Cite web |last=Harding |first=Scharon |date=2025-03-19 |title=HP avoids monetary damages over bricked printers in class-action settlement |url=https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |url-status=live |archive-url=http://web.archive.org/web/20250319231817/https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |archive-date=2025-03-19 |website=Ars Technica}}</ref>

===X1E firmware 01.01.02.00 LAN-mode connection failure===
Newly received X1E printers with firmware 01.01.02.00 will not connect to the Bambu Studio using the Lan only method password. Bambu Studio identifies the un-logged printer but will not allow a connection to the printer. Only after connection / account pairing is done over the Bambu Handy app by giving internet access to the PC and Printer then using the cloud service connection will Lan only communication and login work.<ref>{{Cite web |last= |date=2024-09 |title=Connect X1E to stand-alone computer |url=https://forum.bambulab.com/t/connect-x1e-to-stand-alone-computer/101474 |url-status=live |archive-url=https://web.archive.org/web/20260223033045/https://forum.bambulab.com/t/connect-x1e-to-stand-alone-computer/101474 |archive-date=2026-02-23 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum}}</ref>

==Implementation timeline and requirements==

The authorization system will be rolled out in phases, starting with the X1 series printers. A beta firmware (version 01.08.03.00) was released on January 17, 2025, with the full release scheduled for late January 2025.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> The P & A series printers will get similar updates at an unspecified future date.

To use printers with the new authorization system, users must update multiple pieces of software:<ref name="firmware-update-introducing-new-authorization-control-system-2" />
*Bambu Studio must be updated to version 01.10.02.64 or higher
*Bambu Handy mobile app must be updated to version 2.17.0 or higher
*The new Bambu Connect application must be installed for using third-party slicers

These software updates are mandatory for users who update their firmware. Failing to update all components simultaneously will result in certain printer controls becoming unusable. Users who choose to maintain third-party software compatibility can continue using older firmware versions, or downgrade the firmware for new printers that ship with the authorization system pre-installed.

Bambu Lab states these coordinated updates are necessary because the new authorization system changes how the printer validates and accepts commands. The older versions of Bambu Studio and Bambu Handy lack the authentication mechanisms required to interact with printers running the new firmware. The Bambu Connect application was created specifically to provide a controlled interface for third-party software, replacing the previous direct access through network plugins.<ref name="firmware-update-introducing-new-authorization-control-system-2" />

==Impact on third-party integration and user choice==

===Changes to third-party access===
The new authorization system replaces direct network API access with a more limited URL-based interface through Bambu Connect. Third-party software can only interact with the printer by sending specific URL commands to Bambu Connect.<ref name="bambu-connect" /> The interface requires three parameters:

*<code>path</code>: The absolute file system path to the 3MF file (e.g., /tmp/cube.gcode.3mf)
*<code>name</code>: The name of the file (e.g., Cube)
*<code>version</code>: A fixed value of 1.0.0 for compatibility

A complete command must be formatted as:

bambu-connect://import-file?path=%2Ftmp%2Fcube.gcode.3mf&name=Cube&version=1.0.0

This interface only allows basic file transfer and print initiation. All other printer-control functions previously available to third-party software are now exclusive to Bambu's own applications. The path and name parameters must be URL-encoded using encodeURIComponent or equivalent functions<ref name="bambu-connect" />.

===Reduced home-automation capabilities===
While basic status monitoring remains available (e.g., print-progress updates in Home Assistant), the new firmware removes the ability for home-automation systems to control printer functions. Users can no longer:
*Start or stop prints remotely using Home Assistant, BTT Panda Touch,<ref name=":0">{{Cite web |last=@BIGTREETECH |date=2025-01-17 |title=BIGTREETECH's post |url=https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |url-status=live |archive-url=http://web.archive.org/web/20251004104021/https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |archive-date=2025-10-04 |website=[[Facebook]]}}</ref> or other third-party accessories or software interfaces
*Control printer temperatures or cooling
*Automate printer behaviors based on sensor data or events
*Access camera feeds through third-party applications<ref name="bambulab-forum-135400/9">{{Cite web |last=@hho |date=2025-01-16 |title=This new auth system will make me sell my printers |url=https://forum.bambulab.com/t/this-new-auth-system-will-make-me-sell-my-printers/135400/9 |url-status=live |archive-url=https://ghostarchive.org/archive/ro1KZ |archive-date=2026-03-30 |access-date=2025-05-01 |website=Bambu Lab Community Forum}}</ref>

===Permanent nature of the update===
Once a printer is updated to the new firmware, users can still revert to previous versions.<ref name="theverge-bambu-2025" /> The option still exists to disable the cloud service.

The manufacturer states this change is required for security, but community members note that many of the security vulnerabilities being addressed stem from Bambu's own cloud-centric design choices rather than inherent risks of local network control<ref name="bambulab-forum-134549/12">{{Cite web |date=2025-01-14 |title=Bambu Studio 1.10.2 Public Beta |url=https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/12 |url-status=live |archive-url=https://ghostarchive.org/archive/u4vpc |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum}}</ref>. The update forces users into using Bambu Connect middleware if they want to retain limited cloud functionality.

For users that would want to use a third-party slicer while using their cloud service, Bambu would require those users to download and install Bambu Connect in order to send gcode wirelessly over LAN or over the cloud. While Bambu claims that they were in contact with SoftFever, the developer of OrcaSlicer, as of January 2025, SoftFever did not have any keys for Bambu Connect and the new firmware was only available as opt-in beta at the time.<ref name=":1">{{Cite web |last=@fever_soft |date=2025-01-18 |title=This is definitely a bummer. I was negotiating for an authorization key to allow OrcaSlicer to communicate with their device like BambuStudio does, but today I was told they won't support this. Only their slicer can send prints directly; others must use their Bambu Connect application |url=https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |url-status=live |access-date=2025-05-01 |website=[[X]] |archive-url=http://web.archive.org/web/20251004104021/https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |archive-date=2025-10-04}}</ref>

==Impact on functionality==
While some functionality remains unauthenticated like in previous firmware versions (sending status information from the printer over the network, starting a print job using SD cards), the most important features now require authentication through a new closed-source client called Bambu Connect<ref name="bambu-connect" />. These restricted features include:

*Initializing prints via LAN or cloud mode
*Remote video access to monitor prints
*Controlling motion system, temperature, fans
*AMS settings and calibrations
*Home automation integration beyond basic status monitoring

Previously, third-party software such as OrcaSlicer<ref name="orca-slicer-issue8063">{{Cite web |date=2025-01-16 |title=FW 1.08.03.00 from Bambu WILL BREAK ORCASLICER for X, P and A series #8063 |url=https://github.com/SoftFever/OrcaSlicer/issues/8063 |url-status=live |archive-url=http://web.archive.org/web/20250708192842/https://github.com/SoftFever/OrcaSlicer/issues/8063 |archive-date=2025-07-08 |access-date=2025-05-01 |website=[[GitHub]]}}</ref> could interact with Bambu Lab printers via the open-source Bambu Studio and proprietary network plug-ins. While Bambu Connect provides a limited URL-based API to initiate prints, most functionality previously openly available is now restricted to Bambu's ecosystem<ref name="bambulab-forum-135400/9" />.

Previously, third-party accessories such as Panda Touch would allow users to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D-pad by default for printer control whereas Panda Touch is a full-color touch screen that had a small battery so that way users could reposition and detach their Panda Touch off their printers if needed. Users would be able to queue up jobs, jog printer motors, and connect to multiple printers at once in order to monitor print jobs. According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch not to update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch. <ref name=":0" />

==Communication with Panda Touch developers==

As of late January 2025, no formal communication between Big Tree Tech (BTT), the manufacturer and developer of Panda Touch, and Bambu Labs had been reported. BTT stated in a Facebook announcement that they had contacted Bambu Lab and would publish updates if Bambu responded.<ref name=":0" />

==Communication with OrcaSlicer developers==

Before the official announcement of the new authorization and authentication, Bambu Lab engaged with the OrcaSlicer development team regarding the changes. This communication has sparked discussion within the 3D-printing community, particularly regarding its timing, tone, and implications.

===Pre-announcement contact===
Reports from OrcaSlicer demonstrate that Bambu Lab provided limited advance notice of the changes that would render their software incompatible with Bambu printers running the new firmware. The communication emphasized:
*The introduction of Bambu Connect as the only supported method for interacting with third-party slicers.
*The discontinuation of the network plugin API that OrcaSlicer and other tools relied on for printer control<ref name="orca-slicer-issue8063" />.
*An invitation for OrcaSlicer developers to adapt their software to integrate with the Bambu Connect URL scheme.

The communication lacked the detailed technical documentation that would be necessary for developers to be able to work with the new requirements.

===How the community viewed these actions===
Primary criticisms of Bambu were:
*'''Lack of transparency''': SoftFever reported that the limited warning given to OrcaSlicer developers preceded community engagement with existing customers.<ref name="orca-slicer-issue8063" /> Point to the contrary: the new firmware is in beta and Bambu Connect middleware contains temporary compromises to allow third-party slicers to work as before.
*'''Lack of follow-through:''' As of January 2025, SoftFever, OrcaSlicer's lead developer, did not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Some community members questioned whether Bambu Lab's outreach to OrcaSlicer was a substantive collaboration effort.<ref name=":1" />
*'''Disregard for open-source collaboration''': OrcaSlicer is open-source software developed under the AGPL-3.0 license.<ref name="softfever-orcaslicer-license" /> The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect removes customer choice in how the printer is operated.
*'''Token support for third-party tools''': While Bambu Connect provides a workaround for third-party slicer use, it restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools<ref name="bambu-connect" />.
*'''Power imbalance''': As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users.

==Community-driven workarounds and technical alternatives==

Community members have published workarounds for the firmware restrictions.

===Custom firmware development===
Discussions within the community highlight interest in developing custom firmware as an alternative to Bambu's official updates. One prominent project mentioned in forums is the development of custom firmware for the X1-series printers, such as the "X1Plus Custom Firmware"<ref name="bambulab-forum-134549/12" />. This firmware aims to:
*Restore direct network control and third-party slicer compatibility.
*Re-enable previously available features such as motion-system adjustments, temperature control, and AMS settings without requiring proprietary software.
*Provide users with greater flexibility in integrating printers with home-automation systems and workflows.

However, custom firmware development faces several challenges, including:
*Limited documentation and proprietary hardware components, which complicate reverse-engineering efforts.
*The potential voiding of warranties and risks of bricking devices.
*Legal concerns regarding intellectual property and bypassing manufacturer-imposed restrictions.

==Backup of current third party access enabled firmware and network plugins==
A GitHub repository, [https://github.com/Tzeny/bambulabs_plugins_firmware Tzeny/bambulabs_plugins_firmware], contains a backup of the latest firmware released by Bambu Labs for their printers and of the network plugin used by slicers such as Orca Slicer to communicate with the printer.<ref name="tzeny-bambulabs-plugins-firmware">{{Cite web |last=Tzeny |title=bambulabs_plugins_firmware |url=https://github.com/Tzeny/bambulabs_plugins_firmware |website=GitHub |access-date=2026-05-10 |url-status=live}}</ref>

==LAN mode and blocked internet access==
In January 2025, user Tzeny15 on Reddit authored a five step guide to blocking internet access for the Bambu P1S as a precaution in case the manufacturer attempts to limit functionality for printers without the newest firmware.<ref> {{Cite web |last=@Tzeny15 |title=LAN mode with live view, remote monitoring+control and blocked internet access - a five step guide |url=https://www.reddit.com/r/BambuLab/comments/1i4vp5i/lan_mode_with_live_view_remote_monitoringcontrol/ |url-status=live |access-date=2025-05-01 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250310115818/https://old.reddit.com/r/BambuLab/comments/1i4vp5i/lan_mode_with_live_view_remote_monitoringcontrol/ |archive-date=2025-03-10}}</ref>

[[Bambu Lab LAN mode guide]]

==Reverse engineering Bambu Connect==
{{:Reverse Engineering Bambu Connect}}

''[[Reverse Engineering Bambu Connect|Read more about reverse engineering Bambu Connect here.]]''

==Community tools and scripts==
In addition to firmware alternatives, some users have come up with custom scripts and software tools to interface with Bambu Lab printers indirectly. These tools often rely on:
*Reverse-engineering the URL-based commands required by Bambu Connect to enable partial functionality with third-party slicers like OrcaSlicer.
*Creating local server emulations to replicate the network API previously available before the update.

While these tools provide temporary solutions, they do not fully replace the open access that existed before the firmware update.

===Re-engineering printer-control electronics===
ChazLayyd's Bambu Lab Klipper Conversion project is currently in an incomplete stage<ref>{{Cite web |last=@ChazLayyd |title=Running Klipper on a Bambu Lab machine by replacing it's internal electronics with readily available open-source hardware. |url=https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion |url-status=live |access-date=2025-05-01 |website=GitHub |archive-url=http://web.archive.org/web/20251116182420/https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion |archive-date=2025-11-16}}</ref><ref>{{Cite web |title=ChazLayyd's Discord Community |url=https://discord.com/invite/W6B5mBejuC |url-access=registration |url-status=live |archive-url=https://web.archive.org/web/20260223033213/https://discord.com/invite/W6B5mBejuC |archive-date=2026-02-23 |website=[[Discord]]}}</ref>. While the project was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that run Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.

===Advocacy for open-ecosystem support===
Community members have also organized to advocate for open-source support and rollback options. Suggestions include:
*Allowing an opt-out option for existing users who prefer local network control without cloud dependency.
*Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.<ref name="orca-slicer-issue8063" />

===X1Plus and other alternative firmware===
X1Plus is an open-source custom firmware version for Bambu Labs printers (more details on the GitHub page). It instructs the printer's auto-update mechanism that the device is on a future version (numbered 99 or higher) so the official firmware does not overwrite the modification.

*Installation tutorials are available for users who have not yet updated. Installing third-party firmware will void the warranty. Users are advised to consult the GitHub documentation before installation.
*[https://github.com/X1Plus/X1Plus X1Plus on GitHub]
*The Bambu Labs website offers consumers the ability to request a rootable firmware to be sent to their printers. As of January 26, 2025, the feature (in the EU at least) is broken such that you cannot finalize the process of requesting such a firmware.<ref name="bambu-third-party-firmware-plan">{{Cite web |title=Third Party Firmware Plan |url=https://bambulab.com/en-eu/third-party-firmware/plan |website=Bambu Lab |access-date=2025-01-26 |url-status=live}}</ref>
**The result of accepting the terms of the page titled "Third Party Firmware Plan Guideline" and clicking "Next" takes you to a page titled "Important Notice and Risk Warning" which, when accepting the terms leaves you with an "I got it" button that takes you back to the previous page.

==Cease and desist against the OrcaSlicer-bambulab re-enablement project==

In April 2026, Bambu Lab sent a cease-and-desist communication to the developer of a third-party OrcaSlicer fork that had restored direct printer control after the Authorization Control System rollout. The project was wiped from public view the same day the threat was delivered, and the developer published a summary of Bambu Lab's allegations but not the letter itself, citing Bambu Lab's refusal to authorize publication.<ref name="jarczak-readme" /> The full public-record account includes a parallel May 7, 2026 Bambu Lab blog post & three same-day public Reddit replies from the maintainer.

===What OrcaSlicer is===
OrcaSlicer is a free, open-source slicer: a program that converts a 3D model file into the layer-by-layer instructions (G-code) a 3D printer needs to produce the physical object. It is maintained by the developer SoftFever and draws from Bambu Lab's Bambu Studio, which is itself a fork of Prusa Research's PrusaSlicer.<ref name="softfever-orcaslicer">{{Cite web |last=SoftFever |title=OrcaSlicer |url=https://github.com/SoftFever/OrcaSlicer |url-status=live |access-date=2026-05-04 |website=[[GitHub]]}}</ref> Bambu Studio in turn descends from Slic3r, the upstream project Prusa Research forked.<ref name="slic3r-repo">{{Cite web |title=Slic3r |url=https://github.com/slic3r/Slic3r |website=GitHub |access-date=2026-05-10 |url-status=live}}</ref><ref name="prusaslicer-license">{{Cite web |title=PrusaSlicer LICENSE (AGPL-3.0) |url=https://github.com/prusa3d/PrusaSlicer/blob/master/LICENSE |website=GitHub |publisher=Prusa Research |access-date=2026-05-10 |url-status=live}}</ref> OrcaSlicer is widely used by owners of Bambu Lab printers as an alternative to Bambu Studio, & it ships under the AGPL-3.0 license.<ref name="softfever-orcaslicer" /><ref name="softfever-orcaslicer-license">{{Cite web |title=OrcaSlicer LICENSE.txt (AGPL-3.0) |url=https://github.com/SoftFever/OrcaSlicer/blob/main/LICENSE.txt |website=GitHub |publisher=SoftFever |access-date=2026-05-10 |url-status=live}}</ref><ref name="xda-jarczak">{{Cite web |last=Batt |first=Simon |date=2026-04-23 |title=A developer restored OrcaSlicer's features that Bambu Lab killed — then the legal threats arrived |url=https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |url-status=live |archive-url=https://web.archive.org/web/20260427233833/https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |archive-date=2026-04-27 |access-date=2026-05-04 |website=XDA Developers}}</ref>

===Restrictions introduced by the Authorization Control System===
The Authorization Control System announced on January 16, 2025 gated print initiation, motion control, fan & hotend temperature control, AMS configuration, calibrations, remote video, & firmware upgrade behind a Bambu-issued authentication path. Owners who installed the new firmware could no longer send print jobs from third-party slicers directly over the local network; they had to route those jobs through a new closed-source middleware, Bambu Connect.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> SoftFever was not given API keys for Bambu Connect & stated publicly that direct print sending from OrcaSlicer would not be supported going forward.<ref name=":1" />

===The OrcaSlicer-bambulab fork===
On April 23, 2026, the developer Pawel Jarczak (GitHub user <code>jarczakpawel</code>) made a public fork named OrcaSlicer-bambulab at <code>github.com/jarczakpawel/OrcaSlicer-bambulab</code>. The fork restored the ability to send print jobs from OrcaSlicer directly to Bambu Lab printers without routing through Bambu Connect.<ref name="xda-jarczak" /> According to Jarczak's own description, the fork worked by reaching the printer through a Linux-side workflow Bambu Lab had not yet disabled, & was built on publicly available Bambu Studio source code combined with the developer's own integration layer; it did not redistribute Bambu Lab's proprietary networking plugin binaries.<ref name="jarczak-readme" /><ref name="3druck-jarczak">{{Cite web |date=2026-04-30 |title=Developer ends OrcaSlicer fork after Bambu Lab threatens legal action |url=https://3druck.com/en/programs/developer-terminates-orcaslicer-fork-after-bambu-lab-threatens-to-sue-32156744/ |url-status=live |access-date=2026-05-04 |website=3Druck.com}}</ref> Jarczak also maintained a sibling fork at <code>github.com/jarczakpawel/BambuStudio-BMCU</code> that added support for a third-party multi-color unit (BMCU); that repository remained live as of May 9, 2026.<ref name="jarczak-bmcu">{{Cite web |last=Jarczak |first=Pawel |title=BambuStudio-BMCU |url=https://github.com/jarczakpawel/BambuStudio-BMCU |website=GitHub |access-date=2026-05-10 |url-status=live}}</ref>

===The cease and desist===
Bambu Lab contacted Jarczak directly & demanded removal of the fork. According to Jarczak's own first-person account in his public archive README, Bambu Lab "referred to legal materials and stated that a cease and desist letter had been prepared," & alleged that the implementation:
<blockquote>''impersonated Bambu Studio, bypassed their authorization controls, violated their Terms of Use, involved "reverse engineering", and could allow modified forks to send arbitrary commands to printers.''</blockquote><ref name="jarczak-readme" /> Jarczak rejected the reverse-engineering characterization, stating that his work was based on publicly available Bambu Studio source code, which Bambu Lab releases under the AGPL-3.0 license.<ref name="jarczak-readme" /><ref name="3druck-jarczak" /> Jarczak disputed the broader characterization and asked for specifics: the exact files or commits at issue, & the exact legal or contractual basis. He reports receiving "further broad accusations" instead of that specificity.<ref name="jarczak-readme" /> Bambu Lab refused consent for publication of the correspondence itself, & Jarczak elected to honor that refusal while retaining the letter.<ref name="jarczak-readme" /> The repository was wiped the same day the threat was delivered.<ref name="jarczak-readme" /><ref name="xda-jarczak" /> Jarczak removed the contents voluntarily & stated this was a practical decision, not an admission that the legal or technical allegations were correct; in his own words from the public archive notice:
<blockquote>''I removed the repository voluntarily. That removal should not be interpreted as an admission that all legal or technical allegations made against the project were correct.''</blockquote><ref name="jarczak-readme" />
XDA Developers reported that Bambu Lab had not responded to its request for comment as of publication.<ref name="xda-jarczak" /> 3Druck independently confirmed the same set of allegations, citing Jarczak's GitHub statement.<ref name="3druck-jarczak" /> Tom's Hardware also covered the takedown on April 29, 2026.<ref name="tomshardware-jarczak">{{Cite web |title=Developer re-enables 3D printer features that Bambu Lab disabled, firm promptly threatens legal action — OrcaSlicer-BambuLab project now shuttered |url=https://www.tomshardware.com/3d-printing/developer-re-enables-3d-printer-features-that-bambu-lab-disabled-firm-promptly-threatens-legal-action-orcaslicer-bambulab-project-now-shuttered |website=Tom's Hardware |date=2026-04-29 |access-date=2026-05-10 |url-status=live}}</ref> The trade outlet Manufactur3D added context on May 1, 2026, including that the dispute had become a flashpoint in the wider 3D-printing community.<ref name="manufactur3d-controversy">{{Cite web |title=Bambu Lab OrcaSlicer Controversy Ignites After Legal Threats |url=https://manufactur3dmag.com/bambu-lab-orcaslicer-controversy-escalates/ |website=Manufactur3D |date=2026-05-01 |access-date=2026-05-10 |url-status=live}}</ref>

The publicly documented allegations track Bambu Lab's [[Terms of Service]] & an "authorization bypass" framing.<ref name=":2" /><ref name="jarczak-readme" /> Because the letter itself was not made public, no primary source confirms which specific statute, if any, Bambu Lab invoked; neither Jarczak's account nor the secondary reporting names a specific statute, including the [[DMCA Section 1201|DMCA §1201]] anti-circumvention provision, as part of Bambu Lab's claim. The upstream OrcaSlicer maintainer SoftFever was not named in the cease-and-desist, has issued no public statement on the fork or the letter, & the upstream repository remains active.<ref name="softfever-orcaslicer" />

===Public timeline===
The timeline below is built strictly from public sources. Private direct-message correspondence between Pawel Jarczak & Bambu Lab is not republished; every claim is anchored to Jarczak's public archive README, Bambu Lab's public blog, Bambu Lab's public Reddit post, three public Reddit replies under the parent thread, or independent press coverage.

*'''January 16, 2025.''' Bambu Lab announced "Firmware Update: Introducing the New Authorization Control System," describing the firmware-gated authorization model.<ref name="firmware-update-introducing-new-authorization-control-system-2" />
*'''Spring 2026.''' Pawel Jarczak published <code>OrcaSlicer-bambulab</code> & a sibling repository <code>BambuStudio-BMCU</code> on GitHub.<ref name="jarczak-readme" /><ref name="jarczak-bmcu" />
*'''Late April 2026.''' Bambu Lab contacted Jarczak privately on Reddit & demanded removal of the OrcaSlicer fork. Per Jarczak's public README, Bambu Lab's allegations were impersonation of Bambu Studio, bypass of authorization controls, ToS violation, reverse engineering, & the potential for modified forks to send arbitrary commands to printers.<ref name="jarczak-readme" />
*'''Around April 23, 2026.''' Jarczak removed the <code>OrcaSlicer-bambulab</code> repository voluntarily & replaced its contents with a public archive notice; <code>jarczakpawel/BambuStudio-BMCU</code> remained live as of May 9, 2026.<ref name="jarczak-readme" /><ref name="jarczak-bmcu" />
*'''May 7, 2026.''' Bambu Lab published "Setting the record straight on Cloud Access and Community" on its blog & posted a parallel announcement on r/BambuLab the same day.<ref name="bambu-blog-record-straight" /><ref name="bambu-reddit-record-straight">{{Cite web |last=BambuLab |title=Setting the record straight on Cloud Access and Community |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/setting_the_record_straight_on_cloud_access_and/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref>
*'''May 7, 2026 (same day).''' A Reddit user posting as <code>Low-Anything6975</code> replied publicly under three top-level comments on the r/BambuLab thread. The first reply pinpointed the file path & code line in Bambu's own AGPL source where the User-Agent string is generated.<ref name="pawel-reddit-okg9iih">{{Cite web |last=Low-Anything6975 |title=Reply on User-Agent attribution in Bambu Studio AGPL source code |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/comment/okg9iih/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The second reply addressed the cloud Terms of Service & AGPL rights to use, modify & redistribute.<ref name="pawel-reddit-okguwzs">{{Cite web |last=Low-Anything6975 |title=Reply on cloud Terms of Service and AGPL rights to use, modify and redistribute |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/comment/okguwzs/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The third reply articulated the plugin-severability symmetry argument.<ref name="pawel-reddit-okiacag">{{Cite web |last=Low-Anything6975 |title=Reply on plugin severability symmetry between AGPL forks and Bambu Lab cloud |url=https://www.reddit.com/r/BambuLab/comments/1t66ru1/comment/okiacag/ |website=Reddit |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref>
*'''May 9, 2026.''' Jarczak's public archive README was last updated; <code>BambuStudio-BMCU</code> remained live.<ref name="jarczak-readme" /><ref name="jarczak-bmcu" />
*'''May 9, 2026.''' Right-to-repair advocate Louis Rossmann publicly pledged $10,000 toward Jarczak's legal defense if Bambu Lab proceeded with the threatened lawsuit in a YouTube video titled "I'll put up $10,000 to teach bambu labs a lesson."<ref name="rossmann-youtube-pledge">{{Cite web |last=Rossmann |first=Louis |title=I'll put up $10,000 to teach bambu labs a lesson |url=https://www.youtube.com/watch?v=qLLVn6XT7v0 |website=YouTube |date=2026-05-09 |access-date=2026-05-10 |url-status=live}}</ref>
*'''May 10, 2026.''' Tom's Hardware reported Rossmann's pledge & accompanying public statement directed at Bambu Lab.<ref name="tomshardware-rossmann-pledge">{{Cite web |title=Louis Rossmann tells 3D printer maker Bambu Lab to 'Go (Bleep) yourself' over its threatened lawsuit against enthusiast — Right to Repair advocate offers to pay the legal fees for a threatened OrcaSlicer developer |url=https://www.tomshardware.com/3d-printing/louis-rossmann-tells-3d-printer-maker-bambu-lab-to-go-bleep-yourself-over-its-lawsuit-against-enthusiast-right-to-repair-advocate-offers-to-pay-the-legal-fees-for-a-threatened-orcaslicer-developer |website=Tom's Hardware |date=2026-05-10 |access-date=2026-05-10 |url-status=live}}</ref>

===Bambu Lab's public response===
Bambu Lab's May 7, 2026 blog post conceded that AGPL forks of Bambu Studio are permitted, recast the dispute as one about cloud access & "impersonation" rather than open source, & declined any responsibility under AGPL for the cloud back-end. Bambu Lab characterized the AGPL question:
<blockquote>''Bambu Studio is an open-source project under the AGPL-3.0 license. Anyone can take its code, modify it, and distribute it. This is not a matter of our 'permission' - it is simply how the license and open source work.''</blockquote><ref name="bambu-blog-record-straight" />
The same post bifurcated AGPL code from cloud infrastructure:
<blockquote>''Our cloud is a private service. Access to it is governed by a user agreement, not the AGPL license.''</blockquote><ref name="bambu-blog-record-straight" />
Bambu Lab's only concrete technical allegation against the OrcaSlicer-bambulab fork in the post was that the modification "worked by injecting falsified identity metadata into network communication." The post identified the metadata as the HTTP User-Agent string the fork emitted to Bambu Cloud:
<blockquote>''When this particular OrcaSlicer fork communicates with our cloud services, it quietly introduces itself as official Bambu Studio - with a hardcoded version number and all... that's precisely the point where code modification crosses into impersonation.''</blockquote><ref name="bambu-blog-record-straight" />
Bambu Lab restated the bifurcation in summary form:
<blockquote>''Modifying and distributing AGPL code - absolutely. But impersonating official clients in communication with our cloud infrastructure is not allowed.''</blockquote><ref name="bambu-blog-record-straight" />
The trade outlet 3Druck published an analysis of the post on May 7, 2026, headlined that the dispute was about cloud access rather than open-source customization.<ref name="3druck-bambu-cloud-not-opensource">{{Cite web |title=Dispute over OrcaSlicer fork: Bambu Lab is about cloud access, not open-source customization |url=https://3druck.com/en/programs/dispute-over-orcaslicer-fork-bambu-lab-is-about-cloud-access-not-open-source-customization-16157098/ |website=3Druck.com |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref>

===Consumer-rights significance===
Bambu Lab printer owners had paid for hardware that, at the time of purchase, allowed third-party slicers to send print jobs directly over their own local network. The January 2025 firmware update removed that capability for owners who installed the update.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> When an independent developer rebuilt the lost capability on top of source code Bambu Lab itself publishes, the company's response was a private legal threat rather than a technical or contractual remedy that the affected owners could read or contest.<ref name="jarczak-readme" /> The developer took the project down & stated he had "no interest in maintaining a prolonged dispute."<ref name="jarczak-readme" />

==Open-source licensing dispute==

The cease-and-desist against Pawel Jarczak's OrcaSlicer-bambulab fork made the underlying open-source-licensing conflict concrete: a manufacturer that publishes a slicer under the AGPL-3.0 license, while imposing a Terms of Use that forbids the modification & redistribution that license grants, is on a collision course with the license it chose. The legal arguments in this section are drawn from the AGPL text Bambu Lab applied to Bambu Studio, the Terms of Use Bambu Lab publishes on its corporate website, the Bambu Lab blog post of May 7, 2026, three public Reddit replies under the parent thread, the BambuStudio source code on GitHub, the FSF's published interpretive guidance, & U.S. & EU primary law. None of the theories below has been adjudicated against Bambu Lab; each is a question raised by Bambu Lab's own conduct & documents.

===Bambu Studio AGPL-3.0 licensing===
Bambu Lab elected to release Bambu Studio under the [[GNU Affero General Public License|GNU Affero General Public License version 3]] (AGPL-3.0). The LICENSE file in the upstream Bambu Studio repository is the verbatim AGPL-3.0 text.<ref name="bambustudio-license" /><ref name="agpl3-license">{{Cite web |title=GNU Affero General Public License Version 3 |url=https://www.gnu.org/licenses/agpl-3.0.html |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> The AGPL is a copyleft license: anyone who receives the code can use, modify & redistribute it, on the condition that they pass the same rights to everyone they distribute to, & that they make their modifications available as source code.<ref name="agpl3-license" /> The final paragraph of Section 10 (titled "Automatic Licensing of Downstream Recipients") begins:
<blockquote>''You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.''</blockquote><ref name="agpl3-section10">{{Cite web |title=GNU Affero General Public License Version 3, Section 10 (Automatic Licensing of Downstream Recipients) |url=https://www.gnu.org/licenses/agpl-3.0.html#section10 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> The paragraph continues with examples of prohibited restrictions, including imposing license fees or royalties for exercise of the granted rights & initiating patent litigation against users of the program.<ref name="agpl3-section10" />
Section 7, paragraph 4, lists the only kinds of additional terms a licensor may attach to AGPL-licensed code & states that downstream recipients may strip out anything outside that list:
<blockquote>''All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.''</blockquote><ref name="agpl3-section7">{{Cite web |title=GNU Affero General Public License Version 3, Section 7 (Additional Terms) |url=https://www.gnu.org/licenses/agpl-3.0.html#section7 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref>
Bambu Lab's May 7, 2026 blog post acknowledges the licensing posture.<ref name="bambu-blog-record-straight" />

===Terms of Use conflict with AGPL===
Bambu Lab's Terms of Use § 3.4, preserving a typo in the source text:
<blockquote>''Except as otherwise expressly permitted, you shall not, nor allow any other person to misappropriate, intrude or make other inappropriate use of the Product, including, but not limited to modify, discoder, copy, reverse engineer, publish, publicly disseminate, decompile, export codes, disassemble or create derivatives of the Product in any way.''</blockquote><ref name=":2" />
Two further clauses in § 3.5 reinforce the same prohibitions. § 3.5(2) states:
<blockquote>''(2) provide to third parties, or allow third parties to use the whole or part of the Software without obtaining Bambu Lab's written consent (including but not limited to apps, services, code, and source code)''</blockquote><ref name=":2" />
§ 3.5(5) states:
<blockquote>''(5) attempt to destroy, bypass, change, invalidate or escape from the Product and/or any digital rights management system that is part of the organic composition of the Product''</blockquote><ref name=":2" />
Bambu Lab's Terms define "Product" to include Bambu Lab devices & the software contained therein.<ref name=":2" /> Bambu Lab's own May 7, 2026 blog post confirms that Bambu Studio is "the software" in question.<ref name="bambu-blog-record-straight" />

The collision is straightforward: AGPL § 7 ¶ 4 & § 10 forbid the licensor from imposing additional restrictions on AGPL-granted rights, & TOS § 3.4 / § 3.5 forbid the modification, copying, reverse engineering, decompilation, & redistribution that AGPL-3.0 explicitly grants. Either the TOS clauses do not apply to the AGPL-licensed Bambu Studio (in which case Bambu Lab should say so on the TOS page) or they do (in which case § 10 makes them unenforceable as further restrictions, & § 7 ¶ 4 lets downstream recipients strip them). On the public record, both documents exist unqualified on Bambu Lab's servers; the FSF's published GPL FAQ classifies a network of dynamically linked components & function calls as "a single combined program" for license-obligation purposes,<ref name="fsf-gpl-faq-plugins">{{Cite web |title=Frequently Asked Questions about the GNU Licenses (GPLPlugins anchor) |url=https://www.gnu.org/licenses/gpl-faq.html#GPLPlugins |website=GNU Project |publisher=Free Software Foundation |access-date=2026-05-10 |url-status=live}}</ref> & nothing in Bambu Lab's blog post resolves the contradiction between the AGPL grant & the TOS prohibitions on AGPL-covered conduct.

The same Reddit user addressed this directly on May 7, 2026:
<blockquote>''Cloud ToS also cannot erase AGPL rights to use, modify and redistribute that code.''</blockquote><ref name="pawel-reddit-okguwzs" />

===Plugin severability contradiction===
Bambu Lab's May 7, 2026 blog post asserts two positions that cannot both be right. The first treats the proprietary networking plugin as severable from the AGPL-licensed Bambu Studio code so that Bambu Lab owes no AGPL obligations on the plugin's network conduct or on Bambu Cloud:
<blockquote>''Our cloud is a private service. Access to it is governed by a user agreement, not the AGPL license.''</blockquote><ref name="bambu-blog-record-straight" />
The second treats the same plugin's network conduct as the AGPL fork's responsibility for impersonation-liability purposes:
<blockquote>''When this particular OrcaSlicer fork communicates with our cloud services, it quietly introduces itself as official Bambu Studio - with a hardcoded version number and all... that's precisely the point where code modification crosses into impersonation.''</blockquote><ref name="bambu-blog-record-straight" />
Severability is symmetrical. Either the proprietary plugin is severable from the AGPL Bambu Studio code (in which case the AGPL fork is the wrong defendant for plugin-mediated network conduct, since the user voluntarily installs the plugin), or the plugin is part of a "Combined Work" with the AGPL Bambu Studio code (in which case Bambu Lab carries AGPL obligations on the combined work).<ref name="fsf-gpl-faq-plugins" /><ref name="fsf-gpl-faq-aggregation">{{Cite web |title=Frequently Asked Questions about the GNU Licenses (MereAggregation anchor) |url=https://www.gnu.org/licenses/gpl-faq.html#MereAggregation |website=GNU Project |publisher=Free Software Foundation |access-date=2026-05-10 |url-status=live}}</ref> The third reply from the same Reddit user on May 7, 2026 stated the symmetry plainly:
<blockquote>''It is more like someone opened a gym on a public square and then tried to forbid people from using the public square.''</blockquote><ref name="pawel-reddit-okiacag" />

===User-Agent identity metadata===
The "falsified identity metadata" Bambu Lab calls "impersonation" is the HTTP User-Agent string the fork emits when contacting Bambu Cloud. That string is generated by Bambu Lab's own AGPL-licensed source code. The User-Agent setter is in <code>src/slic3r/Utils/Http.cpp</code>, & assembles its value from constants defined in <code>version.inc</code>. The relevant line in <code>Http.cpp</code> reads:
<blockquote>''::curl_easy_setopt (curl, CURLOPT_USERAGENT, SLIC3R_APP_NAME " / " SLIC3R_VERSION);''</blockquote><ref name="bambustudio-http-cpp">{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>
The constants in <code>version.inc</code> set the application name & version directly:
<blockquote>''set(SLIC3R_APP_NAME "BambuStudio")''

''set(SLIC3R_VERSION "02.06.01.55")''</blockquote><ref name="bambustudio-version-inc">{{Cite web |title=version.inc (SLIC3R_APP_NAME and SLIC3R_VERSION constants) |url=https://github.com/bambulab/BambuStudio/blob/master/version.inc |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>
Both files are governed by the BambuStudio LICENSE, which is AGPL-3.0.<ref name="bambustudio-license" /> A clean compile of unmodified upstream Bambu Studio emits a <code>User-Agent: BambuStudio / 02.06.01.55</code> header on every HTTP request by default, because that is the value Bambu Lab itself wrote into its own published source. The same Reddit user made this point:
<blockquote>''User-Agent is not authentication. It is just self-declared client metadata. Any program can set any User-Agent. And the most important part: this comes directly from your own AGPL code.''</blockquote><ref name="pawel-reddit-okg9iih" />
Whichever branch of the severability dilemma Bambu Lab takes in the previous subsection, the impersonation framing relies on Bambu Lab's own AGPL-licensed code generating the very header Bambu Lab calls falsified.

===Other AGPL theories raised by the public record===
Three additional AGPL theories follow from the same facts. Each has weaker public-record support than the TOS-versus-AGPL collision & the User-Agent question above; each is identified here so the catalogue is complete, with the evidentiary gaps that any enforcement organization would need to close before relying on the theory.

[[GNU Affero General Public License|AGPL § 13]] (network copyleft) requires that a licensor running a modified version of an AGPL program as a network service offer all users interacting with it remotely an opportunity to receive the Corresponding Source.<ref name="agpl3-section13">{{Cite web |title=GNU Affero General Public License Version 3, Section 13 (Remote Network Interaction) |url=https://www.gnu.org/licenses/agpl-3.0.html#section13 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> Bambu Lab's May 7, 2026 blog post denies any § 13 obligation by treating Bambu Cloud as a separate private service.<ref name="bambu-blog-record-straight" /> The public record does not establish that Bambu Cloud's server-side software derives from AGPL components inherited from upstream Slic3r or PrusaSlicer; until that link is documented, § 13 attachment to Bambu Cloud is an open question, not an established violation.

AGPL § 1 defines "Corresponding Source" as "all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work."<ref name="agpl3-section1">{{Cite web |title=GNU Affero General Public License Version 3, Section 1 (Definitions) |url=https://www.gnu.org/licenses/agpl-3.0.html |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> The Bambu Studio AGPL source contains a runtime plugin loader declared in <code>src/slic3r/Utils/NetworkAgent.hpp</code> & implemented in <code>src/slic3r/Utils/NetworkAgent.cpp</code>; the loader brings in the proprietary <code>bambu_networking</code> plugin via standard dynamic-linking calls, & the function-pointer interface lives in the AGPL header <code>src/slic3r/Utils/bambu_networking.hpp</code>.<ref name="bambustudio-networkagent-hpp">{{Cite web |title=NetworkAgent.hpp (plugin loader header) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/NetworkAgent.hpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref><ref name="bambustudio-networkagent-cpp">{{Cite web |title=NetworkAgent.cpp (proprietary plugin loader) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/NetworkAgent.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref><ref name="bambustudio-bambu-networking-hpp">{{Cite web |title=bambu_networking.hpp (function-pointer interface) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/bambu_networking.hpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref> The FSF's GPL FAQ states that dynamically linked plug-ins that make function calls & share data structures with a host program "form a single combined program."<ref name="fsf-gpl-faq-plugins" /> Whether the AGPL source alone produces a binary functionally equivalent to Bambu Lab's official release requires a clean-compile demonstration that has not been publicly performed; the architectural facts are public, the practical effect is not yet documented.

AGPL § 6 (User-Product anti-Tivoization, parallel to GPLv3 § 6) requires that a licensor convey "Installation Information" sufficient to install & execute modified versions of the covered work on a User Product.<ref name="agpl3-section6">{{Cite web |title=GNU Affero General Public License Version 3, Section 6 (Conveying Non-Source Forms) |url=https://www.gnu.org/licenses/agpl-3.0.html#section6 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref> Per Bambu Lab's open-source software disclosure page, the X1-series printer firmware is built on the Rockchip RV1126 SDK with Linux kernel & U-Boot components under GPLv2 (which has no anti-Tivoization clause), & the P1 / A1 series firmware uses an ESP32 SDK from Espressif Systems with no disclosed GPL components.<ref name="bambu-opensource-disclosure">{{Cite web |title=Open Source Software |url=https://wiki.bambulab.com/en/knowledge-sharing/open-source-software |website=Bambu Lab Wiki |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref> On those facts, AGPL § 6 / GPLv3 § 6 anti-Tivoization does not currently anchor a complaint against Bambu Lab printer firmware. The theory would reactivate only if a future firmware audit surfaced GPLv3 or AGPLv3 components.

===U.S. and EU consequences===
In the United States, the doctrine of copyright misuse bars enforcement of copyrights that are being misused. The Fourth Circuit recognized the defense in [https://www.courtlistener.com/opinion/546900/lasercomb-america-inc-v-job-reynolds/ Lasercomb America, Inc. v. Reynolds], 911 F.2d 970 (4th Cir. 1990), with the court holding:
<blockquote>''Since copyright and patent law serve parallel public interests, a "misuse" defense should apply to infringement actions brought to vindicate either right.''</blockquote><ref name="lasercomb-1990">{{Cite web |title=Lasercomb America, Inc. v. Reynolds, 911 F.2d 970 (4th Cir. 1990) |url=https://www.courtlistener.com/opinion/546900/lasercomb-america-inc-v-job-reynolds/ |website=CourtListener |access-date=2026-05-10 |url-status=live}}</ref>
The Ninth Circuit confirmed the doctrine in [https://www.courtlistener.com/opinion/744681/practice-management-information-corp-v-american-medical-assn/ Practice Management Information Corp. v. AMA], 121 F.3d 516 (9th Cir. 1997), holding that the AMA had used its copyright:
<blockquote>''in a manner violative of the public policy embodied in the grant of a copyright.''</blockquote><ref name="practice-management-1997">{{Cite web |title=Practice Management Information Corp. v. American Medical Ass'n., 121 F.3d 516 (9th Cir. 1997) |url=https://www.courtlistener.com/opinion/744681/practice-management-information-corp-v-american-medical-assn/ |website=CourtListener |access-date=2026-05-10 |url-status=live}}</ref> The Ninth Circuit quoted Lasercomb at 977 for that formulation & adopted copyright misuse as a defense to copyright infringement.<ref name="practice-management-1997" />
A defendant accused of copyright infringement on Bambu Studio code can raise the TOS-versus-AGPL conflict as a misuse defense.

In the European Union, [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009L0024 Software Directive 2009/24/EC, Article 8] provides:
<blockquote>''The provisions of this Directive shall be without prejudice to any other legal provisions such as those concerning patent rights, trade-marks, unfair competition, trade secrets, protection of semi-conductor products or the law of contract. Any contractual provisions contrary to Article 6 or to the exceptions provided for in Article 5(2) and (3) shall be null and void.''</blockquote><ref name="eu-software-directive-2009-24-ec">{{Cite web |title=Directive 2009/24/EC of the European Parliament and of the Council of 23 April 2009 on the legal protection of computer programs |url=https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009L0024 |website=EUR-Lex |publisher=European Union |date=2009-04-23 |access-date=2026-05-10 |url-status=live}}</ref>
The Court of Justice of the European Union confirmed in [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 SAS Institute Inc. v. World Programming Ltd], Case C-406/10 (Grand Chamber, May 2, 2012), that a software licensee's right to observe, study & test the program cannot be overridden by contract.<ref name="cjeu-c-406-10">{{Cite web |title=Case C-406/10, SAS Institute Inc. v World Programming Ltd, Judgment of the Court (Grand Chamber), 2 May 2012 |url=https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 |website=EUR-Lex |publisher=European Union |date=2012-05-02 |access-date=2026-05-10 |url-status=live}}</ref> Polish law transposes the Software Directive in the [https://eli.gov.pl/eli/DU/1994/83 Polish Copyright Act of February 4, 1994], with art. 75 protecting lawful-user observation, study & testing rights, & art. 76 declaring contract provisions that conflict with art. 75 sections 2 and 3 void.<ref name="polish-copyright-act-1994">{{Cite web |title=Ustawa z dnia 4 lutego 1994 r. o prawie autorskim i prawach pokrewnych |url=https://eli.gov.pl/eli/DU/1994/83 |website=Elektroniczny Dziennik Urzędowy |publisher=Government of Poland |date=1994-02-04 |access-date=2026-05-10 |url-status=live}}</ref> Whether art. 76 reaches a non-EU choice-of-law clause attempting to bypass these mandatory rules is a separate question that requires Polish-counsel briefing; the doctrinal point is that the rules are mandatory within Polish jurisdiction.

===Open-source licensing context: SFC v. Vizio===
The closest live U.S. analog to a manufacturer publishing copyleft client software with a proprietary cloud back-end is [[Software Freedom Conservancy v. Vizio]]. The case is proceeding in Orange County Superior Court, California; the [[Software Freedom Conservancy]] filed it in October 2021, on behalf of a consumer-purchaser theory of breach-of-contract enforcement of GPLv2 & LGPLv2.1 components in Vizio's smart TVs.<ref name="sfc-vizio-case-page">{{Cite web |title=Software Freedom Conservancy v. Vizio Inc. |url=https://sfconservancy.org/copyleft-compliance/vizio.html |website=Software Freedom Conservancy |access-date=2026-05-10 |url-status=live}}</ref>

On December 4, 2025, the trial court issued a tentative ruling granting SFC's motion on a direct-contract theory: the court found that a direct contract was formed, with Vizio under a duty to provide complete and corresponding source code, when SFC's systems administrator, Paul Visscher, requested source code for a Vizio TV that SFC had purchased.<ref name="sfc-vizio-tentative-2025">{{Cite web |title=Tentative Vizio Ruling in Favor of SFC |url=https://sfconservancy.org/news/2025/dec/04/tentative-vizio-ruling-in-favor-of-sfc/ |website=Software Freedom Conservancy |date=2025-12-04 |access-date=2026-05-10 |url-status=live}}</ref> On December 23, 2025, Judge Leal granted Vizio's motion for summary adjudication on a peripheral installation-keys point, ruling that GPLv2 does not impose a duty on a licensee to provide information permitting reinstallation of modified software such that the device continues to function properly. SFC's December 24, 2025 commentary on the ruling characterized the issue as orthogonal to its core copyleft-enforcement theory, noting:
<blockquote>''SFC has never held the position, nor do we today hold the position, that any version of the GPL (even including GPLv3!) require "that the device continues to function properly" after a user installs their modified version of the copyleft components.''</blockquote><ref name="sfc-vizio-msa-2025">{{Cite web |title=Vizio MSA Irrelevant Ruling |url=https://sfconservancy.org/news/2025/dec/24/vizio-msa-irrelevant-ruling/ |website=Software Freedom Conservancy |date=2025-12-24 |access-date=2026-05-10 |url-status=live}}</ref> On January 26, 2026, SFC reported that the trial had been postponed because of an older case taking docket priority.<ref name="sfc-vizio-trial-delay-2026">{{Cite web |title=Some Unfortunate Delays in our Struggle for Copyleft Justice |url=https://sfconservancy.org/blog/2026/jan/26/delay-in-start-of-vizio-trial/ |website=Software Freedom Conservancy |date=2026-01-26 |access-date=2026-05-10 |url-status=live}}</ref> The trial is now scheduled for August 10 to August 19, 2026.<ref name="sfc-vizio-case-page" /><ref name="sfc-vizio-trial-delay-2026" /> Industry counsel commentary tracked these rulings as a significant endorsement of consumer-purchaser standing to enforce GPL terms as a contract.<ref name="dlapiper-vizio-jan-2026">{{Cite web |title=SFC v. Vizio ruling on General Public License compliance: Key takeaways |url=https://www.dlapiper.com/en/insights/publications/2026/01/sfc-v-vizio-ruling-on-general-public-license-compliance-key-takeaways |website=DLA Piper |date=2026-01-05 |access-date=2026-05-10 |url-status=live}}</ref><ref name="bakerbotts-vizio-may-2026">{{Cite web |title=When Consumers Enforce Open Source: The SFC v. Vizio Case |url=https://www.bakerbotts.com/thought-leadership/publications/2026/may/when-consumers-enforce-open-source |website=Baker Botts |date=2026-05-01 |access-date=2026-05-10 |url-status=live}}</ref>

A separate doctrinal anchor for the AGPL § 7 ¶ 4 further-restrictions argument is Bradley M. Kuhn's expert report in <code>Neo4j, Inc. v. PureThink, LLC and John Mark Suhy</code>, 5:18-cv-07182 (N.D. Cal.). Kuhn served as third-party expert for the defendants & analyzed AGPL § 7's right to remove "Commons Clause"-style restrictions.<ref name="sfc-kuhn-neo4j-2023">{{Cite web |title=SFC's Policy Fellow Files Expert Report in Neo4j v. PureThink |url=https://sfconservancy.org/news/2023/feb/09/kuhn-neo4j-purethink-expert-report/ |website=Software Freedom Conservancy |date=2023-02-09 |access-date=2026-05-10 |url-status=live}}</ref> The FSF filed an amicus brief in Neo4j v. Suhy on March 3, 2025, in the Ninth Circuit (Case No. 24-5538), arguing that AGPL § 7's prohibition on further restrictions invalidates Commons Clause-style contractual overlays.<ref name="fsf-amicus-neo4j-2025">{{Cite web |title=FSF submits amicus brief in Neo4j v. Suhy |url=https://www.fsf.org/news/fsf-submits-amicus-brief-in-neo4j-v-suhy |website=Free Software Foundation |date=2025-03-03 |access-date=2026-05-10 |url-status=live}}</ref> As of publication, no appellate court has yet ruled on the AGPL § 7 ¶ 4 question.

===German GPL enforcement (Welte-line cases)===
European GPL-as-contract enforcement has run through a line of German trial-court rulings tied to programmer Harald Welte, the maintainer of <code>netfilter</code>/<code>iptables</code>. German trial courts have repeatedly ruled in Welte-line GPL cases against Sitecom (LG München 2004), D-Link (LG Frankfurt 2006), Skype (LG München, 7 O 5245/07, 2007), and Fantec (LG Hamburg, 308 O 10/13, 2013), holding variously that GPL distribution terms function as enforceable conditions on the license grant, that linking to GPL text on a website is insufficient for a hardware product, and that a manufacturer cannot blindly rely on a supplier's GPL-compliance assurance.<ref name="sfc-copyleft-compliance" /> These cases concern GPLv2 rather than AGPLv3, but the contract-enforceability principle they apply translates by analogy: a German trial court has been willing to treat copyleft terms as enforceable obligations on a vendor that distributes copyleft binaries. Bambu Lab does not currently distribute Bambu Studio binaries through Germany under any contractual notice that overrides AGPL § 10; the Welte cases are cited as comparable precedent rather than as authority controlling the Bambu Lab matter.

===John Deere AGPL: no filed litigation, SFC v. Vizio is the operative analog===
A widely circulated assumption in repair-advocacy discussion is that there is a "John Deere AGPL precedent" that supports community enforcement against a manufacturer who publishes copyleft code & locks down the product. There is no such case in litigation form. The Software Freedom Conservancy described its John Deere compliance work in a March 16, 2023 blog post stating that Deere had failed to provide complete corresponding source for more than two years after SFC's first request; the post does not announce a filed complaint, & no SFC litigation against John Deere has been publicly docketed since.<ref name="sfc-john-deere-2023">{{Cite web |title=John Deere's GPL Violations |url=https://sfconservancy.org/blog/2023/mar/16/john-deere-gpl-violations/ |website=Software Freedom Conservancy |date=2023-03-16 |access-date=2026-05-10 |url-status=live}}</ref> The right-to-repair litigation involving John Deere has run on different statutes: [[DMCA Section 1201|DMCA § 1201]] exemption petitions, FTC enforcement, & the 2023 American Farm Bureau memorandum of understanding. Those are repair-policy fights, not AGPL enforcement actions. The actual analog for the Bambu Lab pattern, copyleft client software paired with a proprietary cloud back-end on consumer hardware, is SFC v. Vizio.

===Who can enforce AGPL against Bambu Lab===
Pawel Jarczak personally cannot bring an AGPL enforcement action against Bambu Lab on his own. The right to sue for AGPL violations belongs to the original authors whose code Bambu Lab built on top of: the [https://github.com/slic3r/Slic3r Slic3r contributors],<ref name="slic3r-repo" /> Prusa Research & the [https://github.com/prusa3d/PrusaSlicer/blob/master/LICENSE PrusaSlicer contributors],<ref name="prusaslicer-license" /> & the [https://github.com/SoftFever/OrcaSlicer/blob/main/LICENSE.txt SoftFever / OrcaSlicer maintainers].<ref name="softfever-orcaslicer-license" /> Jarczak's role in any formal complaint is reporter & witness, not plaintiff.

The institutional capacity for AGPL enforcement on these facts sits with several organizations:

*'''[[Software Freedom Conservancy]] (SFC).''' SFC operates the only U.S.-based copyleft enforcement program currently litigating consumer-purchaser claims against a hardware manufacturer (the Vizio matter). Its [https://sfconservancy.org/copyleft-compliance/ copyleft-compliance program] handles strategic enforcement; Bradley M. Kuhn's AGPL § 7 expert report from <code>Neo4j v. PureThink</code> remains the strongest published doctrinal anchor for the Bambu Lab TOS-versus-AGPL argument.<ref name="sfc-copyleft-compliance">{{Cite web |title=Copyleft Compliance Projects |url=https://sfconservancy.org/copyleft-compliance/ |website=Software Freedom Conservancy |access-date=2026-05-10 |url-status=live}}</ref><ref name="sfc-kuhn-neo4j-2023" />
*'''Free Software Foundation (FSF).''' FSF drafted the AGPL & operates the [https://www.fsf.org/licensing/ Licensing & Compliance Lab]. FSF will not be the lead enforcement vehicle here because FSF does not hold copyright in BambuStudio; it can supply doctrinal authority, amicus filings, & public statements. FSF filed an amicus brief in <code>Neo4j v. Suhy</code> on March 3, 2025.<ref name="fsf-licensing">{{Cite web |title=Licensing & Compliance Lab |url=https://www.fsf.org/licensing/ |website=Free Software Foundation |access-date=2026-05-10 |url-status=live}}</ref><ref name="fsf-amicus-neo4j-2025" />
*'''Free Software Foundation Europe (FSFE).''' FSFE convenes the [https://fsfe.org/activities/ln/ln.en.html European Legal Network] of free-software lawyers & is geographically appropriate to a Polish maintainer.<ref name="fsfe-legal-network">{{Cite web |title=Legal Network |url=https://fsfe.org/activities/ln/ln.en.html |website=Free Software Foundation Europe |access-date=2026-05-10 |url-status=live}}</ref>
*'''Electronic Frontier Foundation (EFF).''' Not for AGPL enforcement, but for the maintainer's defensive posture. The [https://www.eff.org/issues/coders Coders' Rights Project] works on the legal issues developers face under DMCA, CFAA, & similar computer-crime laws & provides public guidance for reverse engineering & vulnerability disclosure.<ref name="eff-coders-rights">{{Cite web |title=Coders' Rights Project |url=https://www.eff.org/issues/coders |website=Electronic Frontier Foundation |access-date=2026-05-10 |url-status=live}}</ref>
*'''iFixit & The Repair Association.''' Press reach & [[right to repair]] coalition framing. Neither litigates AGPL; both have established media reach & legislative relationships & have publicly tracked the Bambu Lab takedown in their channels.

===Consequences for FOSS forks of corporate-sponsored AGPL projects===
Louis Rossmann publicly pledged $10,000 toward Jarczak's legal defense if Bambu Lab proceeded with a lawsuit in a May 9, 2026 YouTube video,<ref name="rossmann-youtube-pledge" /> & directed an explicit public statement at the company's leadership; Tom's Hardware reported the pledge on May 10, 2026.<ref name="tomshardware-rossmann-pledge" /> The 3D-printing trade press (3Druck, XDA, Tom's Hardware, Manufactur3D) covered the dispute as the immediate flashpoint. Enforcement organizations including the Free Software Foundation, Software Freedom Conservancy, FSFE, and Electronic Frontier Foundation have jurisdiction to bring AGPL claims, but no enforcement action involving Bambu Lab had been announced as of publication. The same question reaches every IoT-device vendor who ships AGPL or GPLv3 components with companion mobile apps & cloud back-ends, & every consumer-electronics company publishing open-source slicers, control panels, or firmware while routing user functionality through proprietary remote services.

==Impact on professional users and privacy concerns==

===Impact on professional users and print farms===
The restrictions imposed by the new authorization system create operational challenges for professional users who kept their printers signed into the cloud:

*Print farms can no longer use custom automation systems to manage multiple printers
*Workflows built around third-party software have to be completely redesigned
*The requirement to manually export and import files through Bambu Connect creates additional labor
*Integration with existing business systems and workflows becomes more difficult or impossible
*Print-farm operators report that the new workflow disrupts their fleet-management workflows<ref name="bambulab-forum-135400/9" />
Print-farm operators can avoid these restrictions by operating their printers in LAN-only mode rather than signing them into Bambu Cloud.

===Privacy and data-collection concerns===

The shift toward mandatory use of Bambu Studio and Bambu Connect raises several privacy and data collection concerns:

*All printer operations must now pass through Bambu's cloud infrastructure when using cloud mode
*User print data, including file names and print settings, becomes visible to Bambu when cloud is used
*Operational data is processed through Bambu's servers while on a different network. The camera feed, on the other hand, is always peer-to-peer.
*Users have limited visibility into how their data is collected, stored, and used in the cloud
*The system creates dependence on Bambu's cloud services availability for basic printer functionality<ref name=":4" />

While Bambu Lab maintains that cloud processing is necessary for security and functionality, community members argue this represents unnecessary data collection that could be handled locally.<ref name="bambulab-forum-134549/12" /> Users who do not require cloud-based features can disable cloud connectivity and operate the printer through LAN mode.

Users who do not want their print data routed through Bambu's cloud infrastructure can operate their printers in LAN-only mode.

==Customer reactions==

Customer reactions have been overwhelmingly negative.<ref>{{Cite web |last=@hho |date=2025-01-15 |title=Bambu Studio 1.10.2 Public Beta |url=https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/4 |url-status=live |archive-url=https://ghostarchive.org/archive/ahrz6 |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Improvements Introduce authorization and authentication protection mechanism: Bambu Studio now supports signing and encrypting control commands sent to printers when the printer supports authorization and authentication protection. The printer will determine whether the commands can be executed. Hmmm. This reads suspiciously vague. It could mean that Bambu printers get an onboard permission handling, so that you can "lock down" your printer and set what commands can be run. But it could also mean that Bambu printers in (or of?) the future will only run Gcode encrypted and signed by Bambu Studio…}}</ref><ref>{{Cite web |last=@iranintoavan |title=Firmware Update Introducing New Authorization Control System |url=https://old.reddit.com/r/BambuLab/comments/1i2psvz/firmware_update_introducing_new_authorization/ |url-status=live |archive-url=http://web.archive.org/web/20250403012526/https://old.reddit.com/r/BambuLab/comments/1i2psvz/firmware_update_introducing_new_authorization/ |archive-date=2025-04-03 |access-date=2025-05-01 |website=Old [[Reddit]]}}</ref> Bambu Lab has historically pushed cloud-based printer interaction while offering limited LAN mode functionality<ref name=":4" />. Many customers argue that the security issues this locked-down firmware claims to address are actually consequences of the company's cloud-based design choices rather than inherent risks of local network control.<ref name="bambulab-forum-134549/12" /> As a result of the announcement of the shift, customer ratings on sites like Trustpilot rapidly dropped,<ref>{{Cite web |title=Bambu Lab |url=https://www.trustpilot.com/review/bambulab.com?sort=recency |archive-url=https://web.archive.org/web/20250119162028/https://www.trustpilot.com/review/bambulab.com?sort=recency |archive-date=2025-01-19 |website=[[Trustpilot]]}}</ref> with many reviews citing the restrictions as the reason for the bad reviews.

So far, '''no changes have been made or indicated for those not using the cloud service'''. Past firmware updates made it possible to avoid using the cloud service completely by allowing pairing the slicer via IP address and access key and doing offline firmware updates without having to sign the printer into the service, not even temporarily, keeping local functionality unchanged.

==Comparisons to similar practices by other companies==

Bambu Lab's new authorization & authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as [[HP]] & [[Epson]], who have faced backlash & litigation over [[digital rights management]] (DRM) practices in 2D printers. The Federal Trade Commission's May 2021 report ''Nixing the Fix'' described firmware-mediated cartridge restrictions as one of the recurring repair-policy issues the agency examined, & noted that the Magnuson-Moss Warranty Act prohibits a printer manufacturer from conditioning its warranty on the purchaser's use of the manufacturer's branded ink.<ref name="ftc-nixing-the-fix">{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |author=Federal Trade Commission |url=https://www.ftc.gov/system/files/documents/reports/nixing-fix-ftc-report-congress-repair-restrictions/nixing_the_fix_report_final_5521_630pm-508_002.pdf |website=Federal Trade Commission |date=2021-05-06 |access-date=2026-05-10 |url-status=live}}</ref> HP settled an "Ink Cartridge Monopoly" class action for $1.5 million in 2018, with settlement payments to class members distributed in late 2019,<ref name="hp-2019-class-action">{{Cite web |last=Spicer |first=Christina |title=HP Ink Cartridge Monopoly Class Action Lawsuit Settles for $1.5M |url=https://topclassactions.com/lawsuit-settlements/lawsuit-news/hp-ink-cartridge-monopoly-class-action-lawsuit-settles-1-5m/ |website=Top Class Actions |date=2019-11-26 |access-date=2026-05-10 |url-status=live}}</ref> & in September 2022 reached a Euroconsumers settlement covering Dynamic Security firmware practices in the EU.<ref name="hp-euroconsumers-2022">{{Cite web |title=HP and Euroconsumers settle on Dynamic Security |author=Euroconsumers |url=https://www.euroconsumers.org/hp-and-euroconsumers-settle-on-dynamic-security/ |website=Euroconsumers |date=2022-09-07 |access-date=2026-05-10 |url-status=live}}</ref> A March 19, 2025 Ars Technica account of the U.S. HP class-action settlement reported that owners of 21 specific HP printer models can opt out of Dynamic Security firmware updates as part of the resolution.<ref name=":5" /> Epson faced its own consumer class action over allegations that firmware updates rendered third-party cartridges unusable.<ref name="epson-mondigo-class-action">{{Cite web |last=Cohen |first=Steven |title=Epson Class Action Alleges Printer Ink Defect |url=https://topclassactions.com/lawsuit-settlements/consumer-products/electronics/epson-class-action-alleges-printer-ink-defect/ |website=Top Class Actions |date=2020-05-19 |access-date=2026-05-10 |url-status=live}}</ref> These comparisons address:
*'''Forced updates''': Firmware updates have rendered third-party ink cartridges incompatible, forcing users to purchase proprietary consumables.
*'''Restricted features''': Scanner / printer combos that will not scan if the ink is empty.
*'''Consumer backlash''': Users criticized these updates as anti-consumer, with some pursuing {{Wplink|class action}} lawsuits for deceptive practices.<ref name=":5" />

A parallel specific to the 3D-printing industry can also be drawn from the now-defunct 3D-printer manufacturer [[MakerBot]], whose shift from open-source, DIY-focused machines in 2012 to closed-source, proprietary machines (similarly to Bambu Labs), ultimately drove customers to less-expensive, open-source competitors.<ref>{{Cite web |last=Benchoff |first=Brian |date=2016-04-28 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=2025-12-08 |access-date=2025-05-01 |website=[[Hackaday]]}}</ref> MakerBot was also accused of asserting ownership over publicly available, open-source designs uploaded to its 3D print repository, Thingiverse.<ref>{{Cite web |last=Biggs |first=John |date=2014-05-28 |title=MakerBot Responds To Critics Who Claim It Is Stealing Community IP |url=https://techcrunch.com/2014/05/28/makerbot-responds-to-critics-who-claim-it-is-stealing-community-ip/ |url-status=live |archive-url=http://web.archive.org/web/20251111041317/https://techcrunch.com/2014/05/28/makerbot-responds-to-critics-who-claim-it-is-stealing-community-ip/ |archive-date=2025-11-11 |access-date=2025-05-01 |website=[[TechCrunch]]}}</ref> These factors contributed to MakerBot steadily losing their position and reputation as an industry leader.

==TOS restricting development of third party devices and accessories==

Archived discussion threads from January 2024 confirm that the § 3.1 clause has been part of the Bambu Lab Terms of Use at least since then.<ref>{{Cite web |last=@X1Plus |title=X1plus community Bambu Lab firmware - A win for everyone? |url=https://www.reddit.com/r/3Dprinting/comments/18zaay0/x1plus_community_bambu_lab_firmware_a_win_for/kggqg4n/ |url-status=live |archive-url=https://web.archive.org/web/20260222212657/https://old.reddit.com/r/3Dprinting/comments/18zaay0/x1plus_community_bambu_lab_firmware_a_win_for/kggqg4n/ |archive-date=2026-02-22 |access-date=2025-05-01 |website=[[Reddit]]}}</ref> Community reaction was split: some readers argued the clause is intended to restrict third-party development, while others characterized it as standard boilerplate in vendor terms.<ref>{{Cite web |last=@mflexx |title=Not updated. And this part is shared by pretty much every company that has ever existed on this planet. That's just blatant karma farming at this point. |url=https://www.reddit.com/r/BambuLab/comments/1ibhhg7/updated_tos_shots_fired/m9i78kj/ |url-status=live |archive-url=https://web.archive.org/web/20260222212738/https://old.reddit.com/r/BambuLab/comments/1ibhhg7/updated_tos_shots_fired/m9i78kj/ |archive-date=2026-02-22 |access-date=2025-05-01 |website=[[Reddit]]}}</ref>

Bambu Lab's Terms of Use § 3.1 states:
<blockquote>''3.1 You may not use Bambu Lab technology or Bambu Lab intellectual property to develop software or design, develop, manufacture, sell, or licence third-party devices/accessories associated with Bambu Lab Product without Bambu Lab's prior consent.''</blockquote><ref name=":2" />

==See also==

*[[Forced account]]
*[[Right to repair]]
*[[Terms of Service]]
*[[Software Freedom Conservancy v. Vizio]]
*[[GNU Affero General Public License]]
*[[Software Freedom Conservancy]]

==References==
{{reflist}}

[[Category:Bambu Lab]]
[[Category:Feature Ransom]]
[[Category:3D printers]]
[[Category:Open source]]

PlayOn Desktop discontinued

2026-05-09T00:10:03Z

Louis: apply blockquote rule to executive and source quotations per claude.md rule 23

{{IncidentCargo
|Company=MediaMall
|StartDate=2021-10-07
|EndDate=2021-11-24
|Status=Resolved
|ProductLine=
|Product=PlayOn Desktop
|ArticleType=Product
|Type=Broken Promise,License revocation,Rent-seeking
|Description=MediaMall sold PlayOn Desktop "Lifetime License" at $69.99, then ended updates in October 2021 and pushed lifetime holders to a subscription
}}

'''PlayOn Desktop discontinued''' refers to MediaMall Technologies, Inc.'s October 2021 decision to end development of its PlayOn Desktop streaming DVR software, which had been sold with a $69.99 one-time "Lifetime License," and to direct existing customers toward a new subscription product, PlayOn Home, priced at $5 per month or $40 per year.<ref name="techhive">{{Cite web |last=Newman |first=Jared |date=2021-10-21 |title=PlayOn strands lifetime subscribers as it overhauls its desktop DVR software |url=https://www.techhive.com/article/579775/playon-streaming-dvr-just-got-a-lot-pricier.html |website=TechHive |access-date=2026-05-08}}</ref><ref name="upgrade-archive">{{Cite web |date=2021-01-26 |title=PlayOn Upgrade Page |url=https://web.archive.org/web/20210126210706/https://www.playon.tv/upgrade |website=PlayOn (archived by the Internet Archive Wayback Machine) |access-date=2026-05-08}}</ref> PlayOn Desktop received its final software update on October 7, 2021, and was no longer available to purchase as of that date.<ref name="techhive" /> Lifetime customers were offered a minimum of three months of free PlayOn Home as compensation, with longer offers for more recent buyers.<ref name="welcome-home">{{Cite web |date=2021-11-24 |title=Welcome to PlayOn Home |url=https://www.playon.tv/blog/welcome-playon-home |website=The PlayOn Blog |access-date=2026-05-08}}</ref>

== Background ==

PlayOn Desktop was a Windows application developed by MediaMall Technologies, Inc. The program loaded streaming videos in a hidden web browser and silently recorded them to the user's hard drive, producing standard MP4 files. TechHive's Jared Newman, in coverage of the discontinuation, noted that PlayOn had existed in some form for thirteen years as of October 2021 and described the desktop product as "an invaluable tool" for cord-cutters who wanted to retain access to programming after streaming subscriptions lapsed or shows moved between services.<ref name="techhive" />

The PlayOn Desktop End User License Agreement, which governed all sales of the software, was a contract between the user and "MediaMall Technologies, Inc." Section 4 of the EULA reads:
<blockquote>''MediaMall reserves the right to modify, suspend, or discontinue the Service, or any part thereof, at any time and without notice to you, and MediaMall will not be liable to you should it exercise such rights, even if your use of PlayOn or PlayLater Content is impacted by the change.''</blockquote><ref name="eula">{{Cite web |title=PlayOn End User License Agreement |url=https://www.playon.tv/eula |website=PlayOn |access-date=2026-05-08}}</ref>
Section 5 of the EULA limited MediaMall's warranty to thirty days from the date of receipt, stating:
<blockquote>''There is no warranty or condition of any kind with respect to any defects discovered after the thirty-day limited warranty period.''</blockquote><ref name="eula" />
Disputes were governed by the laws of New York and assigned to the state and federal courts of New York; the EULA contained no arbitration clause and no class action waiver.<ref name="eula" />

At the time of the discontinuation, PlayOn was sold under three plans on the official upgrade page. A Wayback Machine snapshot taken on January 26, 2021, captures the offer: a Lifetime License at $69.99 as a one-time payment, a monthly plan at $4.99, and an annual plan at $19.99.<ref name="upgrade-archive" /> The same snapshot shows a promotional banner reading "NOW 50% OFF DESKTOP LIFETIME" and "SAVE $40 NOW," indicating the lifetime tier was actively marketed to consumers in the months before development ended.<ref name="upgrade-archive" /> A separate product, PlayOn Cloud, recorded videos through MediaMall's own servers on a per-recording credit basis and was governed by a distinct Terms of Service.<ref name="techhive" /><ref name="cloud-tos">{{Cite web |title=PlayOn Cloud Terms of Service |url=https://www.playon.tv/cloud-tos |website=PlayOn |access-date=2026-05-08}}</ref>

== October 2021 product termination ==

PlayOn Desktop received its final update on October 7, 2021, and was withdrawn from sale that same day.<ref name="techhive" /> In its place, MediaMall released PlayOn Home, a Windows program described by TechHive as "functionally similar to the old Desktop software" but available only on a $5 per month or $40 per year subscription.<ref name="techhive" /> The annual price represented an increase from the $19.99 annual plan that had been advertised on PlayOn's upgrade page earlier in 2021.<ref name="upgrade-archive" /><ref name="techhive" />

The same week as the final desktop update, a PlayOn representative posting under the name Skip Sullivan from a @playon.tv email address explained the change in an announcement on the official PlayOn subreddit, which was then reposted by a forum participant to the SageTV community thread "PlayOn Desktop is Dead" (the SageTV mirror is the publicly archived copy). Sullivan wrote:
<blockquote>''Those of you with lifetime PlayOn Desktop licenses are eligible for at least 3 free months of PlayOn Home. Should you find it not for you, you can continue to use PlayOn Desktop on Windows 10 and Window 8.1 PCs, but it will likely become less stable over time. While we won't be releasing updates for PlayOn Desktop we will still provide technical support and troubleshooting assistance.''</blockquote><ref name="sagetv">{{Cite web |date=2021-10-22 |title=PlayOn Desktop is Dead (thread reposting Skip Sullivan's PlayOn subreddit announcement) |url=https://forums.sagetv.com/forums/showthread_t_66812.html?t=66812 |website=SageTV Community Forum |access-date=2026-05-08}}</ref>

Sullivan's announcement identified the technical reason MediaMall gave for the change:
<blockquote>''Windows 11 integrates the new chromium-based Edge browser very differently than Windows 10, which changes the way PlayOn does it's hidden browser/capture process. The Edge stuff in Windows 11 was still in flux/development in the Windows 11 betas.''</blockquote><ref name="sagetv" />
TechHive reported a parallel email statement from MediaMall's Chief Operating Officer, Tracy Burman, who said via email that Windows 11 introduces a major change in how it integrates Microsoft's Edge browser, which in turn forced the company to revamp its entire capturing process.<ref name="techhive" /> Burman further told TechHive in an email statement:
<blockquote>''it was not possible to develop and maintain this new and improved version of PlayOn without some continued investment from our customers.''</blockquote><ref name="techhive" />

The transition was formalized in a November 24, 2021 post on the official PlayOn Blog titled "Welcome to PlayOn Home." The post, attributed to "Tracy's Blog," announced PlayOn Home as "our new PC-based Streaming DVR" and stated that monthly and annual Desktop subscribers would be migrated automatically.<ref name="welcome-home" /> TechHive's Jared Newman, writing in the same period, observed that "the old PlayOn desktop software will eventually become worthless as its recording capabilities degrade," because PlayOn's recording mechanism depended on continued maintenance against changes in streaming-service websites.<ref name="techhive" />

== MediaMall's response to lifetime customers ==

MediaMall did not refund lifetime license holders. Instead, the November 24, 2021 PlayOn Blog post offered them migration credit toward the new subscription product:
<blockquote>''Existing PlayOn Desktop users with monthly and annual plans will be automatically migrated over to PlayOn Home. Users who purchased a Lifetime license to Desktop will receive a minimum of 3 months of PlayOn Home for free, and folks who purchased more recently will get even more free time on PlayOn Home. Users can see what their special PlayOn Home offer is by logging into their account.''</blockquote><ref name="welcome-home" />
After those free months, lifetime holders who wished to continue using a maintained product would have to pay $5 monthly or $40 annually.<ref name="techhive" />

MediaMall relied on the EULA's reservation clause, which had granted the company the right to discontinue the software "at any time and without notice" without liability to the user, and the thirty-day limited warranty that disclaimed responsibility for any later defects.<ref name="eula" /> Sullivan framed the company's position in the same announcement as a resource constraint:
<blockquote>''This decision was not made lightly. PlayOn is a small company and with limited development resources and this was and is about carving out a path forward that allows us to continue cover the cost of development and to provide software and service that meet needs of our users.''</blockquote><ref name="sagetv" />
Sullivan also stated that purchasing PlayOn Home was not a forfeiture of the existing lifetime license and that the desktop software would continue to install and run on Windows 10 and Windows 8.1 systems, though without further updates.<ref name="sagetv" />

== Consumer response ==

TechHive reported on the consumer reaction:
<blockquote>''The news has not gone over well on PlayOn's Reddit page, where an announcement post now has hundreds of mostly angry comments.''</blockquote><ref name="techhive" />
The SageTV community forum thread "PlayOn Desktop is Dead," which mirrored Sullivan's PlayOn subreddit announcement, drew posts from forum participants questioning a one-time payment marketed as "lifetime" being terminated by a unilateral software-development decision.<ref name="sagetv" /> Jared Newman concluded the TechHive piece with a broader observation:
<blockquote>''we should all be a little more wary of "lifetime" subscriptions from companies whose costs are ongoing; sooner or later, the bill always comes due.''</blockquote><ref name="techhive" />

As of May 2026, no class action lawsuit against MediaMall Technologies regarding the PlayOn Desktop discontinuation has been documented in published reporting on the dispute, and no consumer-protection investigation has been announced.

== Legal context ==

The closest reported precedent on the "lifetime of the device" defense in a software context is ''McVetty v. TomTom North America Inc.'', No. 7:19-cv-04908 (S.D.N.Y.), in which a plaintiff brought New York General Business Law claims against TomTom over GPS devices marketed with "Lifetime Maps and Traffic" that the company later discontinued. TomTom argued that "lifetime" referred to the useful life of the device, not the life of the purchaser. A federal court dismissed the action in July 2022 on the ground that McVetty's amended complaint did not provide context for the label he relied on after purchasing the device, with the court finding that the amended complaint put forth insufficient details about any alleged deception.<ref name="mcvetty">{{Cite web |last=Dennehy |first=Kevin |date=2022-07-21 |title=TomTom Successfully Defends Proposed Class Action, Reports 2nd Quarter Loss |url=https://locationbusinessnews.com/tomtom-successfully-defends-proposed-class-action-reports-2nd-quarter-loss |website=Location Business News |access-date=2026-05-08}}</ref><ref name="mcvetty-filing">{{Cite web |last=Rizzi |first=Corrado |date=2019-05-28 |title=TomTom Hit with Class Action Over Allegedly 'Illusory' Lifetime Maps and Traffic Support |url=https://www.classaction.org/news/tomtom-hit-with-class-action-over-allegedly-illusory-lifetime-maps-and-traffic-support |website=ClassAction.org |access-date=2026-05-08}}</ref> PlayOn's EULA assigns disputes to the state and federal courts of New York,<ref name="eula" /> placing any consumer claim against MediaMall over the lifetime license in the same forum that decided ''McVetty''.

The leading counter-example involves hardware rather than software. In ''Alvarez v. Sirius XM Radio Inc.'', No. 2:18-cv-08605-JVS-SS (C.D. Cal.), Sirius XM agreed to a settlement valued at approximately $96 million on claims that "Lifetime Subscription" plans had been tied to specific radio devices, with the carrier interpreting "lifetime" as the working life of the hardware. Final approval was granted on February 9, 2021.<ref name="alvarez">{{Cite web |title=SiriusXM Lifetime Subscription Class Action Settlement |url=https://topclassactions.com/lawsuit-settlements/closed-settlements/siriusxm-lifetime-subscription-class-action-settlement/ |website=Top Class Actions |access-date=2026-05-08}}</ref>

California has since enacted statutory disclosure rules for digital-goods purchases. Assembly Bill 2426, codified at California Business and Professions Code section 17500.6, prohibits the use of words such as "buy" or "purchase" in connection with digital goods unless the consumer either receives a permanent download or provides "affirmative acknowledgment" that what is being sold is a license rather than ownership.<ref name="ab2426">{{Cite web |title=AB-2426 Consumer protection: false advertising: digital goods. |url=https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202320240AB2426 |website=California Legislative Information |access-date=2026-05-08}}</ref> The statute took effect on January 1, 2025.<ref name="sidley-ab2426">{{Cite web |date=2024-11 |title=California's New Digital Goods Law AB 2426: What You Need to Know |url=https://www.sidley.com/en/insights/newsupdates/2024/11/californias-new-digital-goods-law-ab-2426-what-you-need-to-know |website=Sidley Austin LLP |access-date=2026-05-08}}</ref> The PlayOn Desktop transition predates AB 2426 by three years.

The procedural posture of any future PlayOn Desktop dispute is shaped by an asymmetry between MediaMall's two governing agreements. The PlayOn Desktop EULA selects New York state and federal courts and contains no arbitration clause and no class action waiver.<ref name="eula" /> The PlayOn Cloud Terms of Service, by contrast, require final and binding arbitration before the American Arbitration Association under its Commercial Arbitration Rules, and prohibit class, consolidated, or representative actions. The Cloud ToS class-action waiver reads:
<blockquote>''You may only resolve Disputes with MMT on an individual basis, and may not bring a claim as a plaintiff or a class member in a class, consolidated, or representative action. Class arbitrations, class actions, private attorney general actions, and consolidation with other arbitrations are prohibited under our agreement.''</blockquote><ref name="cloud-tos" />
Lifetime Desktop license holders therefore retain, in theory, access to a New York class proceeding that PlayOn Cloud customers do not.<ref name="eula" /><ref name="cloud-tos" />

== See also ==

* [[VitalSource "Lifetime" false advertising]]
* [[TeamViewer terminates perpetual licenses]]
* [[Ngenic forces subscription on previously “lifetime” Tune customers]]
* [[Bandicam perpetual license invalidation]]
* [[List of products and services with post-purchase license change]]
* [[MediaMall]]

== References ==

{{reflist}}

[[Category:Incidents]]
[[Category:2021 incidents]]
[[Category:Lifetime license removal]]
[[Category:Rent-seeking]]

MediaMall

2026-05-09T00:05:17Z

Louis: new company article on MediaMall Technologies, NY-based maker of PlayOn streaming DVR; covers the lifetime license discontinuation incident, EULA-vs-Cloud-ToS legal asymmetry, and product timeline

{{CompanyCargo
|Founded=2003
|Industry=Software
|Logo=
|ParentCompany=
|CompanyAlias=MediaMall, MMT, MediaMall Technologies
|Type=Private
|Website=https://www.playon.tv/
|Description=NY-based maker of PlayOn streaming DVR software; abandoned $69.99 lifetime license customers in October 2021 with the PlayOn Home subscription
}}

'''MediaMall Technologies, Inc.''' is a privately held New York software company that develops the PlayOn streaming DVR product line. The company is most prominently associated with the October 2021 discontinuation of [[PlayOn Desktop discontinued|PlayOn Desktop]], a Windows recording program it had sold for thirteen years under a $69.99 "Lifetime License", which it replaced with the subscription-only PlayOn Home and offered affected lifetime customers a minimum of three free months of the new service as compensation.<ref name="techhive">{{Cite web |last=Newman |first=Jared |date=2021-10-21 |title=PlayOn strands lifetime subscribers as it overhauls its desktop DVR software |url=https://www.techhive.com/article/579775/playon-streaming-dvr-just-got-a-lot-pricier.html |website=TechHive |access-date=2026-05-08}}</ref><ref name="upgrade-archive">{{Cite web |url=https://web.archive.org/web/20210126210706if_/https://www.playon.tv/upgrade |title=PlayOn Upgrade page (Internet Archive snapshot) |date=2021-01-26 |website=playon.tv via Wayback Machine |access-date=2026-05-08}}</ref><ref name="welcome-home">{{Cite web |url=https://www.playon.tv/blog/welcome-playon-home |title=Welcome to PlayOn Home |author=Tracy Burman |date=2021-11-24 |website=PlayOn Blog |access-date=2026-05-08}}</ref> Newer PlayOn products use a Terms of Service with mandatory binding arbitration & a class-action waiver, an asymmetry from the older Desktop end user license agreement that allowed New York court litigation.<ref name="cloud-tos">{{Cite web |url=https://www.playon.tv/cloud-tos |title=PlayOn Cloud Terms of Service |website=playon.tv |access-date=2026-05-08}}</ref><ref name="eula">{{Cite web |url=https://www.playon.tv/eula |title=PlayOn End User License Agreement |website=playon.tv |access-date=2026-05-08}}</ref>

== Consumer-impact summary ==

* MediaMall sold PlayOn Desktop with a $69.99 "Lifetime License" up through at least January 2021; it discontinued the product in October 2021 and migrated holders into PlayOn Home, a $5/month or $40/year subscription, with a minimum of three free months as the only direct compensation.<ref name="upgrade-archive" /><ref name="techhive" /><ref name="welcome-home" />
* The company's older PlayOn Desktop end user license agreement specifies New York governing law & exclusive jurisdiction in New York state or federal courts, with no arbitration clause & no class-action waiver.<ref name="eula" />
* The newer PlayOn Cloud Terms of Service mandates binding individual arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules & explicitly forbids class actions, consolidated proceedings, & private attorney general actions.<ref name="cloud-tos" />
* The Better Business Bureau profile for MediaMall Technologies, Inc. records consumer complaints clustered around the lifetime license dispute, with customers describing the rebrand to PlayOn Home as a forced repurchase of software they had already paid for.<ref name="bbb">{{Cite web |url=https://www.bbb.org/us/ny/new-york/profile/computer-software-developers/mediamall-technologies-inc-0121-110476 |title=MediaMall Technologies, Inc. BBB Business Profile |website=Better Business Bureau |access-date=2026-05-08}}</ref>
* No class-action lawsuit, [[Federal Trade Commission|FTC]] action, state Attorney General action, or [[DMCA Section 1201|DMCA]] anti-circumvention claim against MediaMall has been documented in published reporting on the company as of May 2026.

== Products ==

MediaMall's products are streaming-video recording & aggregation tools, listed below in chronological order of launch.

'''PlayOn Desktop''' launched in August 2008 as a Windows UPnP/DLNA media server that aggregated streaming video from sites such as [[Hulu]] & [[Netflix]] and transcoded it for game consoles & set-top boxes.<ref name="techhive" /> It received its final software update on October 7, 2021, & is no longer available for purchase; per TechHive, the program does not function on Windows 11.<ref name="techhive" />

'''PlayLater''' launched in 2011 as a separate "DVR for online video" application that recorded streams to local MP4 files. MediaMall later retired the standalone PlayLater product, folding its recording functionality into PlayOn Desktop as "PlayOn Recording".

'''MyMedia''' was a free media-server application that cast personal media files from a Windows PC to Roku devices & gaming consoles, later merged into the PlayOn Media Library.

'''PlayOn Cloud''' is a cloud-based streaming DVR for iOS & Android, charging per-recording credits rather than a flat license fee.<ref name="cloud-tos" /> It is governed by the arbitration-with-class-waiver Terms of Service.<ref name="cloud-tos" />

'''PlayOn.tv Australia''' is a regional configuration of PlayOn Cloud for the Australian streaming market.

'''PlayOn Home''' launched in October 2021 as the direct PC replacement for PlayOn Desktop. It costs $5 per month or $40 per year & cannot be purchased outright.<ref name="techhive" /><ref name="welcome-home" />

'''Younify TV''' launched on June 29, 2023 as a free streaming-aggregation app that consolidates watchlists & recommendations across services into a single interface.<ref name="younify">{{Cite web |url=https://www.prnewswire.com/news-releases/mediamall-technologies-announces-the-launch-of-younify-tv--your-new-favorite-streaming-app-301866832.html |title=MediaMall Technologies Announces the Launch of Younify TV - Your New Favorite Streaming App |date=2023-06-29 |website=PR Newswire |access-date=2026-05-08}}</ref>

== Incidents ==

=== PlayOn Desktop discontinued ===

{{Main|PlayOn Desktop discontinued}}

On October 7, 2021, MediaMall released the final software update for PlayOn Desktop & stopped selling it, replacing it with PlayOn Home, a $5/month or $40/year subscription product.<ref name="techhive" /> The company had marketed a "Lifetime License" to PlayOn Desktop for $69.99, archived on the PlayOn upgrade page as recently as January 26, 2021.<ref name="upgrade-archive" /> Lifetime customers were not refunded; they were instead offered a minimum of three months of PlayOn Home for free, with longer trial periods for more recent purchasers, after which continued use required a paid subscription.<ref name="welcome-home" /><ref name="techhive" /> No class action has been documented in published reporting on the discontinuation as of May 2026.

== Leadership ==

Jeff Lawrence serves as President & CEO. Tracy Burman serves as Chief Operating Officer & is the public face of the company's product communications, signing the November 24, 2021 PlayOn Home launch blog post & speaking on the record to TechHive about the PlayOn Desktop discontinuation.<ref name="welcome-home" /><ref name="techhive" /> Skip Sullivan holds the title Head of Customer Delight per the company's June 29, 2023 PR Newswire release announcing Younify TV; his published support email is skip.sullivan@playon.tv.<ref name="younify" />

The company's New York corporate address of record is listed in the BBB profile as 20 River Terrace, Suite 5N, New York, NY 10282.<ref name="bbb" />

== Legal posture ==

The contractual terms governing MediaMall's products differ sharply between the older PlayOn Desktop end user license agreement & the newer PlayOn Cloud Terms of Service. The Desktop EULA, drafted for the original software product, specifies New York governing law & exclusive jurisdiction in New York courts. Section 7 of the EULA reads:
<blockquote>''This Agreement is governed by the laws of the State of New York, without regard to its conflicts of law provisions. All disputes hereunder shall be resolved in the state or federal courts of the State of New York. You consent to the exclusive jurisdiction of such courts, agree to accept service of process by mail, and waive any jurisdictional or venue defenses otherwise available.''</blockquote><ref name="eula" />

The PlayOn Cloud Terms of Service replaces that framework with a binding individual-arbitration clause administered by the American Arbitration Association under its Commercial Arbitration Rules. The Cloud ToS expressly waives class-action & representative-action procedures:
<blockquote>''You may only resolve Disputes with MMT on an individual basis, and may not bring a claim as a plaintiff or a class member in a class, consolidated, or representative action. Class arbitrations, class actions, private attorney general actions, and consolidation with other arbitrations are prohibited under our agreement.''</blockquote><ref name="cloud-tos" />

The practical effect is that any consumer dispute arising from the post-2016 PlayOn Cloud or PlayOn Home products must be resolved through individual AAA arbitration, with the cost of an individual claim typically exceeding the value of a single subscription. No class action has been filed against MediaMall as of May 2026.<ref name="techhive" />

== See also ==

* [[PlayOn Desktop discontinued]]
* [[List of products and services with post-purchase license change]]
* [[VitalSource "Lifetime" false advertising]]
* [[TeamViewer terminates perpetual licenses]]

== References ==

{{reflist}}



[[Category:Companies]]
[[Category:Software companies]]
[[Category:United States companies]]

PlayOn Desktop discontinued

2026-05-08T23:59:05Z

Louis: apply blockquote rule to executive and source quotations per claude.md rule 23

{{IncidentCargo
|Company=MediaMall
|StartDate=2021-10-07
|EndDate=2021-11-24
|Status=Resolved
|ProductLine=
|Product=PlayOn Desktop
|ArticleType=Product
|Type=Broken Promise,License revocation,Rent-seeking
|Description=MediaMall sold PlayOn Desktop "Lifetime License" at $69.99, then ended updates in October 2021 and pushed lifetime holders to a subscription
}}

'''PlayOn Desktop discontinued''' refers to MediaMall Technologies, Inc.'s October 2021 decision to end development of its PlayOn Desktop streaming DVR software, which had been sold with a $69.99 one-time "Lifetime License," and to direct existing customers toward a new subscription product, PlayOn Home, priced at $5 per month or $40 per year.<ref name="techhive">{{Cite web |last=Newman |first=Jared |date=2021-10-21 |title=PlayOn strands lifetime subscribers as it overhauls its desktop DVR software |url=https://www.techhive.com/article/579775/playon-streaming-dvr-just-got-a-lot-pricier.html |website=TechHive |access-date=2026-05-08}}</ref><ref name="upgrade-archive">{{Cite web |date=2021-01-26 |title=PlayOn Upgrade Page |url=https://web.archive.org/web/20210126210706/https://www.playon.tv/upgrade |website=PlayOn (archived by the Internet Archive Wayback Machine) |access-date=2026-05-08}}</ref> PlayOn Desktop received its final software update on October 7, 2021, and was no longer available to purchase as of that date.<ref name="techhive" /> Lifetime customers were offered a minimum of three months of free PlayOn Home as compensation, with longer offers for more recent buyers.<ref name="welcome-home">{{Cite web |date=2021-11-24 |title=Welcome to PlayOn Home |url=https://www.playon.tv/blog/welcome-playon-home |website=The PlayOn Blog |access-date=2026-05-08}}</ref>

== Background ==

PlayOn Desktop was a Windows application developed by MediaMall Technologies, Inc. The program loaded streaming videos in a hidden web browser and silently recorded them to the user's hard drive, producing standard MP4 files. TechHive's Jared Newman, in coverage of the discontinuation, noted that PlayOn had existed in some form for thirteen years as of October 2021 and described the desktop product as "an invaluable tool" for cord-cutters who wanted to retain access to programming after streaming subscriptions lapsed or shows moved between services.<ref name="techhive" />

The PlayOn Desktop End User License Agreement, which governed all sales of the software, was a contract between the user and "MediaMall Technologies, Inc." Section 4 of the EULA reads:
<blockquote>''MediaMall reserves the right to modify, suspend, or discontinue the Service, or any part thereof, at any time and without notice to you, and MediaMall will not be liable to you should it exercise such rights, even if your use of PlayOn or PlayLater Content is impacted by the change.''</blockquote><ref name="eula">{{Cite web |title=PlayOn End User License Agreement |url=https://www.playon.tv/eula |website=PlayOn |access-date=2026-05-08}}</ref>
Section 5 of the EULA limited MediaMall's warranty to thirty days from the date of receipt, stating:
<blockquote>''There is no warranty or condition of any kind with respect to any defects discovered after the thirty-day limited warranty period.''</blockquote><ref name="eula" />
Disputes were governed by the laws of New York and assigned to the state and federal courts of New York; the EULA contained no arbitration clause and no class action waiver.<ref name="eula" />

At the time of the discontinuation, PlayOn was sold under three plans on the official upgrade page. A Wayback Machine snapshot taken on January 26, 2021, captures the offer: a Lifetime License at $69.99 as a one-time payment, a monthly plan at $4.99, and an annual plan at $19.99.<ref name="upgrade-archive" /> The same snapshot shows a promotional banner reading "NOW 50% OFF DESKTOP LIFETIME" and "SAVE $40 NOW," indicating the lifetime tier was actively marketed to consumers in the months before development ended.<ref name="upgrade-archive" /> A separate product, PlayOn Cloud, recorded videos through MediaMall's own servers on a per-recording credit basis and was governed by a distinct Terms of Service.<ref name="techhive" /><ref name="cloud-tos">{{Cite web |title=PlayOn Cloud Terms of Service |url=https://www.playon.tv/cloud-tos |website=PlayOn |access-date=2026-05-08}}</ref>

== October 2021 product termination ==

PlayOn Desktop received its final update on October 7, 2021, and was withdrawn from sale that same day.<ref name="techhive" /> In its place, MediaMall released PlayOn Home, a Windows program described by TechHive as "functionally similar to the old Desktop software" but available only on a $5 per month or $40 per year subscription.<ref name="techhive" /> The annual price represented an increase from the $19.99 annual plan that had been advertised on PlayOn's upgrade page earlier in 2021.<ref name="upgrade-archive" /><ref name="techhive" />

The same week as the final desktop update, a PlayOn representative posting under the name Skip Sullivan from a @playon.tv email address explained the change in an announcement on the official PlayOn subreddit, which was then reposted by a forum participant to the SageTV community thread "PlayOn Desktop is Dead" (the SageTV mirror is the publicly archived copy). Sullivan wrote:
<blockquote>''Those of you with lifetime PlayOn Desktop licenses are eligible for at least 3 free months of PlayOn Home. Should you find it not for you, you can continue to use PlayOn Desktop on Windows 10 and Window 8.1 PCs, but it will likely become less stable over time. While we won't be releasing updates for PlayOn Desktop we will still provide technical support and troubleshooting assistance.''</blockquote><ref name="sagetv">{{Cite web |date=2021-10-22 |title=PlayOn Desktop is Dead (thread reposting Skip Sullivan's PlayOn subreddit announcement) |url=https://forums.sagetv.com/forums/showthread_t_66812.html?t=66812 |website=SageTV Community Forum |access-date=2026-05-08}}</ref>

Sullivan's announcement identified the technical reason MediaMall gave for the change:
<blockquote>''Windows 11 integrates the new chromium-based Edge browser very differently than Windows 10, which changes the way PlayOn does it's hidden browser/capture process. The Edge stuff in Windows 11 was still in flux/development in the Windows 11 betas.''</blockquote><ref name="sagetv" />
TechHive reported a parallel email statement from MediaMall's Chief Operating Officer, Tracy Burman, who said via email that Windows 11 introduces a major change in how it integrates Microsoft's Edge browser, which in turn forced the company to revamp its entire capturing process.<ref name="techhive" /> Burman further told TechHive in an email statement:
<blockquote>''It was not possible to develop and maintain this new and improved version of PlayOn without some continued investment from our customers.''</blockquote><ref name="techhive" />

The transition was formalized in a November 24, 2021 post on the official PlayOn Blog titled "Welcome to PlayOn Home." The post, attributed to "Tracy's Blog," announced PlayOn Home as "our new PC-based Streaming DVR" and stated that monthly and annual Desktop subscribers would be migrated automatically.<ref name="welcome-home" /> TechHive's Jared Newman, writing in the same period, observed that "the old PlayOn desktop software will eventually become worthless as its recording capabilities degrade," because PlayOn's recording mechanism depended on continued maintenance against changes in streaming-service websites.<ref name="techhive" />

== MediaMall's response to lifetime customers ==

MediaMall did not refund lifetime license holders. Instead, the November 24, 2021 PlayOn Blog post offered them migration credit toward the new subscription product:
<blockquote>''Existing PlayOn Desktop users with monthly and annual plans will be automatically migrated over to PlayOn Home. Users who purchased a Lifetime license to Desktop will receive a minimum of 3 months of PlayOn Home for free, and folks who purchased more recently will get even more free time on PlayOn Home. Users can see what their special PlayOn Home offer is by logging into their account.''</blockquote><ref name="welcome-home" />
After those free months, lifetime holders who wished to continue using a maintained product would have to pay $5 monthly or $40 annually.<ref name="techhive" />

MediaMall relied on the EULA's reservation clause, which had granted the company the right to discontinue the software "at any time and without notice" without liability to the user, and the thirty-day limited warranty that disclaimed responsibility for any later defects.<ref name="eula" /> Sullivan framed the company's position in the same announcement as a resource constraint:
<blockquote>''This decision was not made lightly. PlayOn is a small company and with limited development resources and this was and is about carving out a path forward that allows us to continue cover the cost of development and to provide software and service that meet needs of our users.''</blockquote><ref name="sagetv" />
Sullivan also stated that purchasing PlayOn Home was not a forfeiture of the existing lifetime license and that the desktop software would continue to install and run on Windows 10 and Windows 8.1 systems, though without further updates.<ref name="sagetv" />

== Consumer response ==

TechHive reported on the consumer reaction:
<blockquote>''The news has not gone over well on PlayOn's Reddit page, where an announcement post now has hundreds of mostly angry comments.''</blockquote><ref name="techhive" />
The SageTV community forum thread "PlayOn Desktop is Dead," which mirrored Sullivan's PlayOn subreddit announcement, drew posts from forum participants questioning a one-time payment marketed as "lifetime" being terminated by a unilateral software-development decision.<ref name="sagetv" /> Jared Newman concluded the TechHive piece with a broader observation:
<blockquote>''We should all be a little more wary of "lifetime" subscriptions from companies whose costs are ongoing; sooner or later, the bill always comes due.''</blockquote><ref name="techhive" />

As of May 2026, no class action lawsuit against MediaMall Technologies regarding the PlayOn Desktop discontinuation has been documented in published reporting on the dispute, and no consumer-protection investigation has been announced.

== Legal context ==

The closest reported precedent on the "lifetime of the device" defense in a software context is ''McVetty v. TomTom North America Inc.'', No. 7:19-cv-04908 (S.D.N.Y.), in which a plaintiff brought New York General Business Law claims against TomTom over GPS devices marketed with "Lifetime Maps and Traffic" that the company later discontinued. TomTom argued that "lifetime" referred to the useful life of the device, not the life of the purchaser. A federal court dismissed the action in July 2022 on the ground that McVetty's amended complaint did not provide context for the label he relied on after purchasing the device, with the court finding that the amended complaint put forth insufficient details about any alleged deception.<ref name="mcvetty">{{Cite web |last=Dennehy |first=Kevin |date=2022-07-21 |title=TomTom Successfully Defends Proposed Class Action, Reports 2nd Quarter Loss |url=https://locationbusinessnews.com/tomtom-successfully-defends-proposed-class-action-reports-2nd-quarter-loss |website=Location Business News |access-date=2026-05-08}}</ref><ref name="mcvetty-filing">{{Cite web |last=Rizzi |first=Corrado |date=2019-05-28 |title=TomTom Hit with Class Action Over Allegedly 'Illusory' Lifetime Maps and Traffic Support |url=https://www.classaction.org/news/tomtom-hit-with-class-action-over-allegedly-illusory-lifetime-maps-and-traffic-support |website=ClassAction.org |access-date=2026-05-08}}</ref> PlayOn's EULA assigns disputes to the state and federal courts of New York,<ref name="eula" /> placing any consumer claim against MediaMall over the lifetime license in the same forum that decided ''McVetty''.

The leading counter-example involves hardware rather than software. In ''Alvarez v. Sirius XM Radio Inc.'', No. 2:18-cv-08605-JVS-SS (C.D. Cal.), Sirius XM agreed to a settlement valued at approximately $96 million on claims that "Lifetime Subscription" plans had been tied to specific radio devices, with the carrier interpreting "lifetime" as the working life of the hardware. Final approval was granted on February 9, 2021.<ref name="alvarez">{{Cite web |title=SiriusXM Lifetime Subscription Class Action Settlement |url=https://topclassactions.com/lawsuit-settlements/closed-settlements/siriusxm-lifetime-subscription-class-action-settlement/ |website=Top Class Actions |access-date=2026-05-08}}</ref>

California has since enacted statutory disclosure rules for digital-goods purchases. Assembly Bill 2426, codified at California Business and Professions Code section 17500.6, prohibits the use of words such as "buy" or "purchase" in connection with digital goods unless the consumer either receives a permanent download or provides "affirmative acknowledgment" that what is being sold is a license rather than ownership.<ref name="ab2426">{{Cite web |title=AB-2426 Consumer protection: false advertising: digital goods. |url=https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202320240AB2426 |website=California Legislative Information |access-date=2026-05-08}}</ref> The statute took effect on January 1, 2025.<ref name="sidley-ab2426">{{Cite web |date=2024-11 |title=California's New Digital Goods Law AB 2426: What You Need to Know |url=https://www.sidley.com/en/insights/newsupdates/2024/11/californias-new-digital-goods-law-ab-2426-what-you-need-to-know |website=Sidley Austin LLP |access-date=2026-05-08}}</ref> The PlayOn Desktop transition predates AB 2426 by three years.

The procedural posture of any future PlayOn Desktop dispute is shaped by an asymmetry between MediaMall's two governing agreements. The PlayOn Desktop EULA selects New York state and federal courts and contains no arbitration clause and no class action waiver.<ref name="eula" /> The PlayOn Cloud Terms of Service, by contrast, require final and binding arbitration before the American Arbitration Association under its Commercial Arbitration Rules, and prohibit class, consolidated, or representative actions. The Cloud ToS class-action waiver reads:
<blockquote>''You may only resolve Disputes with MMT on an individual basis, and may not bring a claim as a plaintiff or a class member in a class, consolidated, or representative action. Class arbitrations, class actions, private attorney general actions, and consolidation with other arbitrations are prohibited under our agreement.''</blockquote><ref name="cloud-tos" />
Lifetime Desktop license holders therefore retain, in theory, access to a New York class proceeding that PlayOn Cloud customers do not.<ref name="eula" /><ref name="cloud-tos" />

== See also ==

* [[VitalSource "Lifetime" false advertising]]
* [[TeamViewer terminates perpetual licenses]]
* [[Ngenic forces subscription on previously “lifetime” Tune customers]]
* [[Bandicam perpetual license invalidation]]
* [[List of products and services with post-purchase license change]]
* [[MediaMall]]

== References ==

{{reflist}}

[[Category:Incidents]]
[[Category:2021 incidents]]
[[Category:Lifetime license removal]]
[[Category:Rent-seeking]]

PlayOn Desktop discontinued

2026-05-08T23:45:04Z

Louis: new article on mediamall ending playon desktop "lifetime license" support in october 2021 and pushing customers onto the playon home subscription. sources from techhive's reporting, the wayback-archived upgrade page, the eula and cloud tos, and the mcvetty/sirius xm precedents

{{IncidentCargo
|Company=MediaMall
|StartDate=2021-10-07
|EndDate=2021-11-24
|Status=Resolved
|ProductLine=
|Product=PlayOn Desktop
|ArticleType=Product
|Type=Broken Promise,License revocation,Rent-seeking
|Description=MediaMall sold PlayOn Desktop "Lifetime License" at $69.99, then ended updates in October 2021 and pushed lifetime holders to a subscription
}}

'''PlayOn Desktop discontinued''' refers to MediaMall Technologies, Inc.'s October 2021 decision to end development of its PlayOn Desktop streaming DVR software, which had been sold with a $69.99 one-time "Lifetime License," and to direct existing customers toward a new subscription product, PlayOn Home, priced at $5 per month or $40 per year.<ref name="techhive">{{Cite web |last=Newman |first=Jared |date=2021-10-21 |title=PlayOn strands lifetime subscribers as it overhauls its desktop DVR software |url=https://www.techhive.com/article/579775/playon-streaming-dvr-just-got-a-lot-pricier.html |website=TechHive |access-date=2026-05-08}}</ref><ref name="upgrade-archive">{{Cite web |date=2021-01-26 |title=PlayOn Upgrade Page |url=https://web.archive.org/web/20210126210706/https://www.playon.tv/upgrade |website=PlayOn (archived by the Internet Archive Wayback Machine) |access-date=2026-05-08}}</ref> PlayOn Desktop received its final software update on October 7, 2021, and was no longer available to purchase as of that date.<ref name="techhive" /> Lifetime customers were offered a minimum of three months of free PlayOn Home as compensation, with longer offers for more recent buyers.<ref name="welcome-home">{{Cite web |date=2021-11-24 |title=Welcome to PlayOn Home |url=https://www.playon.tv/blog/welcome-playon-home |website=The PlayOn Blog |access-date=2026-05-08}}</ref>

== Background ==

PlayOn Desktop was a Windows application developed by MediaMall Technologies, Inc. The program loaded streaming videos in a hidden web browser and silently recorded them to the user's hard drive, producing standard MP4 files. TechHive's Jared Newman, in coverage of the discontinuation, noted that PlayOn had existed in some form for thirteen years as of October 2021 and described the desktop product as "an invaluable tool" for cord-cutters who wanted to retain access to programming after streaming subscriptions lapsed or shows moved between services.<ref name="techhive" />

The PlayOn Desktop End User License Agreement, which governed all sales of the software, was a contract between the user and "MediaMall Technologies, Inc." Section 4 of the EULA reserved to MediaMall the right "to modify, suspend, or discontinue the Service, or any part thereof, at any time and without notice to you," and stated that MediaMall would "not be liable to you should it exercise such rights."<ref name="eula">{{Cite web |title=PlayOn End User License Agreement |url=https://www.playon.tv/eula |website=PlayOn |access-date=2026-05-08}}</ref> The same agreement limited MediaMall's warranty to thirty days from the date of receipt, with no warranty "of any kind with respect to any defects discovered after the thirty-day limited warranty period."<ref name="eula" /> Disputes were governed by the laws of New York and assigned to the state and federal courts of New York; the EULA contained no arbitration clause and no class action waiver.<ref name="eula" />

At the time of the discontinuation, PlayOn was sold under three plans on the official upgrade page. A Wayback Machine snapshot taken on January 26, 2021, captures the offer: a Lifetime License at $69.99 as a one-time payment, a monthly plan at $4.99, and an annual plan at $19.99.<ref name="upgrade-archive" /> The same snapshot shows a promotional banner reading "NOW 50% OFF DESKTOP LIFETIME" and "SAVE $40 NOW," indicating the lifetime tier was actively marketed to consumers in the months before development ended.<ref name="upgrade-archive" /> A separate product, PlayOn Cloud, recorded videos through MediaMall's own servers on a per-recording credit basis and was governed by a distinct Terms of Service.<ref name="techhive" /><ref name="cloud-tos">{{Cite web |title=PlayOn Cloud Terms of Service |url=https://www.playon.tv/cloud-tos |website=PlayOn |access-date=2026-05-08}}</ref>

== October 2021 product termination ==

PlayOn Desktop received its final update on October 7, 2021, and was withdrawn from sale that same day.<ref name="techhive" /> In its place, MediaMall released PlayOn Home, a Windows program described by TechHive as "functionally similar to the old Desktop software" but available only on a $5 per month or $40 per year subscription.<ref name="techhive" /> The annual price represented an increase from the $19.99 annual plan that had been advertised on PlayOn's upgrade page earlier in 2021.<ref name="upgrade-archive" /><ref name="techhive" />

The same week as the final desktop update, a PlayOn representative posting under the name Skip Sullivan from a @playon.tv email address explained the change in an announcement on the official PlayOn subreddit, which was then reposted by a forum participant to the SageTV community thread "PlayOn Desktop is Dead" (the SageTV mirror is the publicly archived copy). Sullivan wrote that customers with lifetime PlayOn Desktop licenses were "eligible for at least 3 free months of PlayOn Home" and that they could "continue to use PlayOn Desktop on Windows 10 and Window 8.1 PCs, but it will likely become less stable over time. While we won't be releasing updates for PlayOn Desktop we will still provide technical support and troubleshooting assistance."<ref name="sagetv">{{Cite web |date=2021-10-22 |title=PlayOn Desktop is Dead (thread reposting Skip Sullivan's PlayOn subreddit announcement) |url=https://forums.sagetv.com/forums/showthread_t_66812.html?t=66812 |website=SageTV Community Forum |access-date=2026-05-08}}</ref>

Sullivan's announcement identified the technical reason MediaMall gave for the change: "Windows 11 integrates the new chromium-based Edge browser very differently than Windows 10, which changes the way PlayOn does it's hidden browser/capture process. The Edge stuff in Windows 11 was still in flux/development in the Windows 11 betas."<ref name="sagetv" /> TechHive reported a parallel email statement from MediaMall's Chief Operating Officer, Tracy Burman, who said via email that Windows 11 introduces a major change in how it integrates Microsoft's Edge browser, which in turn forced the company to revamp its entire capturing process.<ref name="techhive" /> Burman further told TechHive that "it was not possible to develop and maintain this new and improved version of PlayOn without some continued investment from our customers."<ref name="techhive" />

The transition was formalized in a November 24, 2021 post on the official PlayOn Blog titled "Welcome to PlayOn Home." The post, attributed to "Tracy's Blog," announced PlayOn Home as "our new PC-based Streaming DVR" and stated that monthly and annual Desktop subscribers would be migrated automatically.<ref name="welcome-home" /> TechHive's Jared Newman, writing in the same period, observed that "the old PlayOn desktop software will eventually become worthless as its recording capabilities degrade," because PlayOn's recording mechanism depended on continued maintenance against changes in streaming-service websites.<ref name="techhive" />

== MediaMall's response to lifetime customers ==

MediaMall did not refund lifetime license holders. Instead, the November 24, 2021 blog post offered them migration credit toward the new subscription product: "Existing PlayOn Desktop users with monthly and annual plans will be automatically migrated over to PlayOn Home. Users who purchased a Lifetime license to Desktop will receive a minimum of 3 months of PlayOn Home for free, and folks who purchased more recently will get even more free time on PlayOn Home. Users can see what their special PlayOn Home offer is by logging into their account."<ref name="welcome-home" /> After those free months, lifetime holders who wished to continue using a maintained product would have to pay $5 monthly or $40 annually.<ref name="techhive" />

MediaMall relied on the EULA's reservation clause, which had granted the company the right to discontinue the software "at any time and without notice" without liability to the user, and the thirty-day limited warranty that disclaimed responsibility for any later defects.<ref name="eula" /> Sullivan framed the company's position in the same announcement as a resource constraint: "This decision was not made lightly. PlayOn is a small company and with limited development resources and this was and is about carving out a path forward that allows us to continue cover the cost of development and to provide software and service that meet needs of our users."<ref name="sagetv" /> Sullivan also stated that purchasing PlayOn Home was not a forfeiture of the existing lifetime license and that the desktop software would continue to install and run on Windows 10 and Windows 8.1 systems, though without further updates.<ref name="sagetv" />

== Consumer response ==

TechHive reported that the announcement "has not gone over well on PlayOn's Reddit page, where an announcement post now has hundreds of mostly angry comments."<ref name="techhive" /> The SageTV community forum thread "PlayOn Desktop is Dead," which mirrored Sullivan's PlayOn subreddit announcement, drew posts from forum participants questioning a one-time payment marketed as "lifetime" being terminated by a unilateral software-development decision.<ref name="sagetv" /> Newman in his TechHive piece concluded that "we should all be a little more wary of 'lifetime' subscriptions from companies whose costs are ongoing; sooner or later, the bill always comes due."<ref name="techhive" />

As of May 2026, no class action lawsuit against MediaMall Technologies regarding the PlayOn Desktop discontinuation has been documented in published reporting on the dispute, and no consumer-protection investigation has been announced.

== Legal context ==

The closest reported precedent on the "lifetime of the device" defense in a software context is ''McVetty v. TomTom North America Inc.'', No. 7:19-cv-04908 (S.D.N.Y.), in which a plaintiff brought New York General Business Law claims against TomTom over GPS devices marketed with "Lifetime Maps and Traffic" that the company later discontinued. TomTom argued that "lifetime" referred to the useful life of the device, not the life of the purchaser. A federal court dismissed the action in July 2022 on the ground that McVetty's amended complaint did not provide context for the label he relied on after purchasing the device, with the court finding that the amended complaint put forth insufficient details about any alleged deception.<ref name="mcvetty">{{Cite web |last=Dennehy |first=Kevin |date=2022-07-21 |title=TomTom Successfully Defends Proposed Class Action, Reports 2nd Quarter Loss |url=https://locationbusinessnews.com/tomtom-successfully-defends-proposed-class-action-reports-2nd-quarter-loss |website=Location Business News |access-date=2026-05-08}}</ref><ref name="mcvetty-filing">{{Cite web |last=Rizzi |first=Corrado |date=2019-05-28 |title=TomTom Hit with Class Action Over Allegedly 'Illusory' Lifetime Maps and Traffic Support |url=https://www.classaction.org/news/tomtom-hit-with-class-action-over-allegedly-illusory-lifetime-maps-and-traffic-support |website=ClassAction.org |access-date=2026-05-08}}</ref> PlayOn's EULA assigns disputes to the state and federal courts of New York,<ref name="eula" /> placing any consumer claim against MediaMall over the lifetime license in the same forum that decided ''McVetty''.

The leading counter-example involves hardware rather than software. In ''Alvarez v. Sirius XM Radio Inc.'', No. 2:18-cv-08605-JVS-SS (C.D. Cal.), Sirius XM agreed to a settlement valued at approximately $96 million on claims that "Lifetime Subscription" plans had been tied to specific radio devices, with the carrier interpreting "lifetime" as the working life of the hardware. Final approval was granted on February 9, 2021.<ref name="alvarez">{{Cite web |title=SiriusXM Lifetime Subscription Class Action Settlement |url=https://topclassactions.com/lawsuit-settlements/closed-settlements/siriusxm-lifetime-subscription-class-action-settlement/ |website=Top Class Actions |access-date=2026-05-08}}</ref>

California has since enacted statutory disclosure rules for digital-goods purchases. Assembly Bill 2426, codified at California Business and Professions Code section 17500.6, prohibits the use of words such as "buy" or "purchase" in connection with digital goods unless the consumer either receives a permanent download or provides "affirmative acknowledgment" that what is being sold is a license rather than ownership.<ref name="ab2426">{{Cite web |title=AB-2426 Consumer protection: false advertising: digital goods. |url=https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202320240AB2426 |website=California Legislative Information |access-date=2026-05-08}}</ref> The statute took effect on January 1, 2025.<ref name="sidley-ab2426">{{Cite web |date=2024-11 |title=California's New Digital Goods Law AB 2426: What You Need to Know |url=https://www.sidley.com/en/insights/newsupdates/2024/11/californias-new-digital-goods-law-ab-2426-what-you-need-to-know |website=Sidley Austin LLP |access-date=2026-05-08}}</ref> The PlayOn Desktop transition predates AB 2426 by three years.

The procedural posture of any future PlayOn Desktop dispute is shaped by an asymmetry between MediaMall's two governing agreements. The PlayOn Desktop EULA selects New York state and federal courts and contains no arbitration clause and no class action waiver.<ref name="eula" /> The PlayOn Cloud Terms of Service, by contrast, require final and binding arbitration before the American Arbitration Association under its Commercial Arbitration Rules, and prohibit class, consolidated, or representative actions: "You may only resolve Disputes with MMT on an individual basis, and may not bring a claim as a plaintiff or a class member in a class, consolidated, or representative action."<ref name="cloud-tos" /> Lifetime Desktop license holders therefore retain, in theory, access to a New York class proceeding that PlayOn Cloud customers do not.<ref name="eula" /><ref name="cloud-tos" />

== See also ==

* [[VitalSource "Lifetime" false advertising]]
* [[TeamViewer terminates perpetual licenses]]
* [[Ngenic forces subscription on previously “lifetime” Tune customers]]
* [[Bandicam perpetual license invalidation]]
* [[List of products and services with post-purchase license change]]
* [[MediaMall]]

== References ==

{{reflist}}

[[Category:Incidents]]
[[Category:2021 incidents]]
[[Category:Lifetime license removal]]
[[Category:Rent-seeking]]

Dead Space 2 activation limit lockout

2026-05-08T17:13:27Z

Louis: Lead rewrite: surface EA Support's discontinued-activation-tool position with verbatim Dec 9 2022 quote and EA Forums confirmation, plus Dec 8 2023 server shutdown

{{IncidentCargo
|Name=Dead Space 2 activation limit lockout
|Description=Electronic Arts continues to sell Dead Space 2 on Steam while EA Support has "sunset" the activation tool, locking out legitimate owners after hardware changes.
|Company=Electronic Arts
|Product=Dead Space 2
|StartDate=2022-12-09
|Status=Ongoing
|Categories=Digital rights management; Activation lockout; Game preservation
}}

'''Dead Space 2 activation limit lockout''' is an ongoing consumer rights incident in which paying owners of the 2011 single-player survival horror game ''Dead Space 2'' are locked out of the product by its TAGES Solidshield content-protection system after exceeding a five-machine activation cap, while [[Electronic Arts]] continues to sell the game on [[Steam]] for $19.99.<ref name="steam-store">{{Cite web|url=https://store.steampowered.com/app/47780/Dead_Space_2/|title=Dead Space 2 on Steam|website=Steam|publisher=Valve Corporation|access-date=2026-05-08}}</ref>

'''EA Support has told customers that the activation reset tools for ''Dead Space 2'' have been discontinued.''' On December 9, 2022, an EA Support agent told a paying customer in writing: "I wish I could reset the activation limit, unfortunately Dead Space 2 game has been sunset many time ago and we dont have any tool to validate this game."<ref name="steam-1742">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/1742226629869067946/|title=Activation Limit Exceeded?|website=Steam Community Discussions: Dead Space 2|date=2018-11-24|access-date=2026-05-08}}</ref> In a July 2024 EA Forums thread, an EA staff account confirmed that ''Dead Space 2'' is no longer selectable as a product on the EA Help support tool and that the lockout cannot be cleared through standard support channels.<ref name="ea-forum-7244303">{{Cite web|url=https://forums.ea.com/discussions/dead-space-franchise-discussion-en/steam-dead-space-2-activation-limit-has-been-exceeded/7244303|title=[Steam] Dead Space 2 "activation limit has been exceeded!"|website=EA Forums|date=2024-07-23|access-date=2026-05-08}}</ref> Electronic Arts shut down the game's online services on December 8, 2023, and as of May 2026 EA Help lists no entry for ''Dead Space 2'' or the original ''Dead Space''; only the 2023 ''Dead Space'' remake appears.<ref name="eurogamer-ngan">{{Cite web|url=https://www.eurogamer.net/ea-closing-crysis-3-dead-space-2-and-dantes-inferno-servers-later-this-year|title=EA closing Crysis 3, Dead Space 2 and Dante's Inferno servers later this year|last=Ngan|first=Liv|website=Eurogamer|date=2023-08-08|access-date=2026-05-08}}</ref><ref name="steam-3276">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/3276824488726023468/|title=Activation Key Limit Reached|website=Steam Community Discussions: Dead Space 2|date=2025-03-13|access-date=2026-05-08}}</ref> The Steam store page continues to advertise the de-authorization workflow at <code>activate.ea.com/deauthorize/</code> as the consumer's remedy for managing the five-machine cap, with no notice that EA Support no longer processes activation resets for the title.<ref name="steam-store" />

Lockouts are triggered by routine consumer actions including operating-system reinstalls, hardware upgrades, hard-drive failures, and installation on a Steam Deck, and the activation-cap mechanism operates independently of the multiplayer master server shutdown.<ref name="pcgw-ds2">{{Cite web|url=https://www.pcgamingwiki.com/wiki/Dead_Space_2|title=Dead Space 2|website=PCGamingWiki|access-date=2026-05-08}}</ref><ref name="steam-4039">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/4039228371162524644/|title=Steam Deck key activation issue|website=Steam Community Discussions: Dead Space 2|date=2023-11-26|access-date=2026-05-08}}</ref>

== Background ==

''Dead Space 2'' was developed by Visceral Games and published by Electronic Arts on January 25, 2011 for Windows, PlayStation 3, and Xbox 360.<ref name="wp-ds2">{{Cite web|url=https://en.wikipedia.org/wiki/Dead_Space_2|title=Dead Space 2|website=Wikipedia|access-date=2026-05-08}}</ref> The PC version uses TAGES Solidshield as its active content-protection technology. PCGamingWiki additionally records retail DVDs as shipping with SecuROM Disc First Authentication, though Electronic Arts' published ''Dead Space 2'' EULA references only Solidshield.<ref name="pcgw-ds2" /> The game's Steam store page carries the publisher's Online Disclaimer, which states that the "GAME USES SOLIDSHIELD CONTENT PROTECTION TECHNOLOGY" & that the "GAME CAN BE PLAYED ON UP TO FIVE COMPUTERS AT THE SAME TIME; USERS CAN MANAGE WHICH COMPUTERS ARE AUTHORIZED OR DE-AUTHORIZED TO PLAY GAME," directing users to <code>http://activate.ea.com/deauthorize/</code> for de-authorization.<ref name="steam-store" />

The five-machine cap is the same numerical limit Electronic Arts adopted for ''Spore'' in September 2008 after the original three-install cap drew a class-action lawsuit, ''Thomas v. Electronic Arts'', filed in the U.S. District Court for the Northern District of California over undisclosed [[SecuROM]] installation and kernel-level operation.<ref name="cnet-spore">{{Cite web|url=https://www.cnet.com/culture/ea-hit-with-class-action-suit-over-spore/|title=EA hit with class action suit over Spore|last=Guevin|first=Jennifer|website=CNET|date=2008-09-24|access-date=2026-05-08}}</ref><ref name="wp-securom">{{Cite web|url=https://en.wikipedia.org/wiki/SecuROM|title=SecuROM|website=Wikipedia|access-date=2026-05-08}}</ref> ''Dead Space 2'' shipped with that five-activation ceiling from launch and has retained it through every storefront iteration since.<ref name="steam-store" />

== Activation lockout mechanism ==

Solidshield binds each authorization to a hardware fingerprint of the machine on which the game is launched. An activation slot is consumed each time the game is installed and run on a new combination of hardware components, and a slot is recovered only if the user runs the in-game de-authorization utility on the original system before that system is decommissioned. Steam community members have documented the relevant binary as a small "activation" application sitting next to the game files in the local Steam library.<ref name="steam-1742" /><ref name="steam-4039" />

In practice, slots are routinely lost without the user's knowledge. A user posting to a Steam discussion thread in October 2022 reported losing two of five activations to "one PC totally dead and the other was a laptop I returned and didn't know to deactivate DS2 before uninstalling steam," leaving them juggling three remaining slots.<ref name="steam-1742" /> A November 2023 thread describes the cap being hit when the owner attempted to install the game on a [[Steam Deck]] after playing it on a desktop PC; the workaround required de-authorizing the desktop install first, leaving the user with a single remaining slot for any future hardware change.<ref name="steam-4039" /> Earlier threads from October 2018 and November 2018 record the same pattern after a routine PC reformat, with EA support either unresponsive or pointing to URLs that no longer functioned.<ref name="steam-5523">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/552359157631595398/|title=Cant play game, Activation limit exceeded|website=Steam Community Discussions: Dead Space 2|date=2018-10-14|access-date=2026-05-08}}</ref><ref name="steam-1742" /> Reports continued through July 2020, March 2025, and August 2025, with the most recent commenters noting that EA's Help site no longer lists the original ''Dead Space'' or ''Dead Space 2'' at all, only the 2023 ''Dead Space'' remake.<ref name="steam-2791">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/2791621151153569169/|title="Activation limit reached for this serial number has been exceeded"|website=Steam Community Discussions: Dead Space 2|date=2020-07-28|access-date=2026-05-08}}</ref><ref name="steam-3276">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/3276824488726023468/|title=Activation Key Limit Reached|website=Steam Community Discussions: Dead Space 2|date=2025-03-13|access-date=2026-05-08}}</ref>

The de-authorization URL printed on the Steam Online Disclaimer remains live and returns HTTP 200, but multiple 2024 and 2025 user reports describe the linked tool as detecting nothing and failing to free a slot bound to a now-dead machine.<ref name="ea-deauth">{{Cite web|url=https://activate.ea.com/deauthorize/|title=EA Game De-authorization|publisher=Electronic Arts|access-date=2026-05-08}}</ref><ref name="steam-3276" />

== EA Support response ==

The earliest archived EA Support reply on the issue dates to a Steam Community thread published December 9, 2022, in which a user who had repurchased the game multiple times to escape the cap quoted the response received from EA Support verbatim: "I wish I could reset the activation limit, unfortunately Dead Space 2 game has been sunset many time ago and we dont have any tool to validate this game."<ref name="steam-1742" /> The quote predates the December 8, 2023 multiplayer server shutdown by almost a full year, establishing that EA had abandoned the customer-support side of single-player activation reset before the multiplayer infrastructure was decommissioned.<ref name="steam-1742" /><ref name="eurogamer-ngan">{{Cite web|url=https://www.eurogamer.net/ea-closing-crysis-3-dead-space-2-and-dantes-inferno-servers-later-this-year|title=EA closing Crysis 3, Dead Space 2 and Dante's Inferno servers later this year|last=Ngan|first=Liv|website=Eurogamer|date=2023-08-08|access-date=2026-05-08}}</ref>

In a July 2024 EA Forums thread, a Steam owner who had bought the game in 2012 reported being unable to find ''Dead Space 2'' anywhere in EA's online support tool. An EA staff account, "EA_Shepard," replied that EA would have to "check the code itself" to address the lockout, and instructed the user to open a support ticket against any unrelated EA title because ''Dead Space 2'' was not selectable as a product on EA Help.<ref name="ea-forum-7244303">{{Cite web|url=https://forums.ea.com/discussions/dead-space-franchise-discussion-en/steam-dead-space-2-activation-limit-has-been-exceeded/7244303|title=[Steam] Dead Space 2 "activation limit has been exceeded!"|website=EA Forums|date=2024-07-23|access-date=2026-05-08}}</ref> A March 2025 Steam thread documents an EA customer-service representative telling a Steam Deck owner whose laptop had died that they were out of luck, and multiple users on the same thread reported that the linked de-authorization tool failed to detect a stale activation slot.<ref name="steam-3276" /> An August 2025 commenter on the same thread confirmed that EA Help still listed only the 2023 ''Dead Space'' remake, with no entry for ''Dead Space 2''.<ref name="steam-3276" />

The EA Forums archive includes earlier lockout reports as well, including a 2012 thread in which EA referred a user to the original <code>activate.ea.com/deauthorize/</code> page, and a separate thread documenting the in-game DeAuthorizeManagement utility failing to remove a stale activation.<ref name="ea-answers-396246">{{Cite web|url=https://answers.ea.com/t5/Other-Dead-Space-Games/Old-Report-Dead-Space-2-Serial-key-limit/m-p/396246|title=[Old Report] Dead Space 2 Serial key limit|website=EA Help / Answers HQ|access-date=2026-05-08}}</ref><ref name="ea-forum-7228344">{{Cite web|url=https://forums.ea.com/discussions/dead-space-franchise-discussion-en/the-activation-limit-for-dead-space-2-serial-number-has-been-exceeded/7228344|title=the activation limit for Dead Space 2 serial number has been exceeded|website=EA Forums|access-date=2026-05-08}}</ref>

== December 2023 multiplayer server shutdown ==

On August 8, 2023, Eurogamer reporter Liv Ngan reported that Electronic Arts had announced the closure of online services for ''Crysis 3'', ''Dead Space 2'', and ''Dante's Inferno''. ''Crysis 3'' servers were shut down on September 7, 2023. ''Dead Space 2'' and ''Dante's Inferno'' servers were shut down on December 8, 2023. The affected mode for ''Dead Space 2'' was the asymmetric multiplayer mode (commonly referred to in coverage as "Outbreak," the name of its DLC map pack) on PC, PS3, and Xbox 360, alongside three Battlefield titles closed the same day.<ref name="eurogamer-ngan" /> The shutdown is also recorded on EA's Online Service Updates page and in PCGamingWiki's documentation of the title.<ref name="ea-service-updates">{{Cite web|url=https://www.ea.com/service-updates|title=Service Updates|website=Electronic Arts|access-date=2026-05-08}}</ref><ref name="pcgw-ds2" />

The multiplayer shutdown is structurally separate from the activation lockout. ''Dead Space 2'' is a single-player game with an optional multiplayer mode bolted on; the Solidshield client-side activation gate enforces the five-machine cap regardless of whether the multiplayer servers are reachable, and the abandonment of EA Support's activation-reset capability had been documented in writing a year before December 2023.<ref name="steam-1742" /><ref name="pcgw-ds2" />

== Continued sale on Steam ==

As of May 2026, ''Dead Space 2'' remains listed for sale on Steam at $19.99 with a "Very Positive" review aggregate.<ref name="steam-store" /> The store page's Online Disclaimer continues to advertise the de-authorization workflow at <code>activate.ea.com/deauthorize/</code> as the consumer's remedy for managing the five-machine cap, but the disclaimer carries no notice that EA Support has stopped processing activation resets for the title or that the linked tool has been described by users as non-functional.<ref name="steam-store" /><ref name="steam-3276" />

Valve's refund window closes fourteen days after purchase; activation-cap lockouts surface years later, when the buyer's first PC has been replaced and the consumed slot cannot be recovered. Valve states that it will issue a refund "if the request is made within the required return period, and, in the case of games, if the title has been played for less than two hours," with the standard return period set at fourteen days from purchase.<ref name="steam-refunds">{{Cite web|url=https://store.steampowered.com/steam_refunds|title=Steam Refunds|website=Steam|publisher=Valve Corporation|access-date=2026-05-08}}</ref> The August 2025 Steam commenter cited above noted owning a copy not installed in over a decade.<ref name="steam-3276" />

== Legal context ==

No United States Federal Trade Commission action, no state attorney general enforcement, no European Commission proceeding, no UK Competition and Markets Authority docket, and no Australian Competition and Consumer Commission case has been filed against Electronic Arts specifically over the ''Dead Space 2'' activation lockout. The closest historical analogues remain ''Thomas v. Electronic Arts'' over ''Spore'' in 2008, which forced the activation cap up from three to five and produced the original de-authorization tool, and the FTC's 2007 Sony BMG rootkit settlement under Section 5 of the FTC Act, neither of which addresses the present incident directly.<ref name="cnet-spore" /><ref name="wp-securom" />

For new sales of the title in the European Union after January 1, 2022, the EU Digital Content Directive (Directive (EU) 2019/770) imposes a conformity obligation on the trader, including a duty under Article 8(2) to supply the updates "necessary to keep the digital content or digital service in conformity" for the period the consumer may reasonably expect, with remedies of bringing the content into conformity, price reduction, or contract termination available to consumers under Articles 13 and 14 where the content is not in conformity.<ref name="dcd-2019-770">{{Cite web|url=https://eur-lex.europa.eu/eli/dir/2019/770/oj|title=Directive (EU) 2019/770 on certain aspects concerning contracts for the supply of digital content and digital services|website=EUR-Lex|publisher=Publications Office of the European Union|date=2019-05-20|access-date=2026-05-08}}</ref> In the United Kingdom, the Consumer Rights Act 2015, Part 1, Chapter 3 establishes parallel rights covering satisfactory quality (section 34), conformity to description (section 36), and a right to repair or replacement of non-conforming digital content, granted by section 42(2)(a) and detailed at section 43.<ref name="cra-2015-c3">{{Cite web|url=https://www.legislation.gov.uk/ukpga/2015/15/part/1/chapter/3|title=Consumer Rights Act 2015, Part 1, Chapter 3 (Digital content)|website=legislation.gov.uk|publisher=The National Archives|access-date=2026-05-08}}</ref> In the United States, the Magnuson-Moss Warranty Act at 15 U.S.C. §§ 2301-2312 supplies the implied warranty of merchantability framework, although its application to software sold under perpetual-license terms remains contested.<ref name="usc-mmwa">{{Cite web|url=https://www.law.cornell.edu/uscode/text/15/chapter-50|title=15 U.S. Code Chapter 50 - Consumer Product Warranties|website=Legal Information Institute|publisher=Cornell Law School|access-date=2026-05-08}}</ref>

The U.S. Library of Congress's most recent triennial rulemaking under [[DMCA Section 1201]], published October 28, 2024, renews the video-game preservation exemption, but limits it to games "no longer reasonably available in the commercial marketplace." Because Electronic Arts continues to sell ''Dead Space 2'' on Steam, an owner who circumvents Solidshield to play the copy they already paid for may not qualify for that exemption.<ref name="dmca-1201-2024">{{Cite web|url=https://www.federalregister.gov/documents/2024/10/28/2024-24563/exemption-to-prohibition-on-circumvention-of-copyright-protection-systems-for-access-control|title=Exemption to Prohibition on Circumvention of Copyright Protection Systems for Access Control Technologies|website=Federal Register|publisher=Library of Congress|date=2024-10-28|access-date=2026-05-08}}</ref>

== Consumer response ==

Affected owners have documented the issue across the Steam Community discussion boards for ''Dead Space 2'' and on EA's own forums, with threads stretching from 2018 to December 2025.<ref name="steam-5523" /><ref name="steam-2791" /><ref name="steam-1742" /><ref name="steam-3276" /> PCGamingWiki maintains a community-curated technical entry recording the DRM stack, the five-machine cap, and the December 8, 2023 server shutdown.<ref name="pcgw-ds2" /> A recurring user-suggested workaround in those threads is the application of an unofficial no-CD executable replacement that bypasses the Solidshield check entirely; the practice is documented in the threads but sits in the legal grey zone described by the DMCA Section 1201 rulemaking above.<ref name="steam-2791" /><ref name="steam-3276" />

The pattern has parallels in active consumer-protection litigation. On March 31, 2026, Rock Paper Shotgun reported that the French consumer group UFC-Que Choisir had sued Ubisoft over the March 2024 server shutdown of ''The Crew'', with backing from the [[Stop Killing Games]] movement.<ref name="rps-ubisoft">{{Cite web|url=https://www.rockpapershotgun.com/major-french-consumer-group-sue-ubisoft-over-always-online-game-shutdowns-with-the-backing-of-stop-killing-games|title=Ubisoft sued for shutting down The Crew's servers by major French consumer group backed by Stop Killing Games|website=Rock Paper Shotgun|date=2026-03-31|access-date=2026-05-08}}</ref> The suit highlights a pattern documented in the ''Dead Space 2'' record as well: a publisher discontinues the infrastructure required to play a product while the product remains in commerce. Stop Killing Games separately organized a European Citizens' Initiative, "Stop Destroying Videogames," registered with the European Commission, that closed its signature collection in 2025 and triggered a mandatory Commission response on the broader question of publisher abandonment of in-commerce video games.<ref name="eci-skg">{{Cite web|url=https://eci.ec.europa.eu/045/public/|title=Stop Destroying Videogames - European Citizens' Initiative|website=European Citizens' Initiative|publisher=European Commission|access-date=2026-05-08}}</ref><ref name="skg-site">{{Cite web|url=https://www.stopkillinggames.com/|title=Stop Killing Games|website=Stop Killing Games|access-date=2026-05-08}}</ref>

== See also ==

* [[Electronic Arts]]
* [[SecuROM]]
* [[Spore (game)]]
* [[Stop Killing Games]]
* [[Adobe Creative Suite activation]]
* [[Activation]]
* [[Discontinuation bricking]]
* [[Storefront shutdown]]
* [[Games as a service]]
* [[Denuvo]]
* [[Digital rights management]]
* [[DMCA Section 1201]]
* [[Video game preservation]]
* [[List of discontinued online-only video games]]

== References ==

{{reflist}}

[[Category:Electronic Arts]]
[[Category:Digital rights management]]
[[Category:Activation lockout]]
[[Category:Game preservation]]
[[Category:Incidents]]

Dead Space 2 activation limit lockout

2026-05-08T13:17:48Z

Louis: Initial publication: Dead Space 2 Steam activation limit lockout incident

{{IncidentCargo
|Name=Dead Space 2 activation limit lockout
|Description=Electronic Arts continues to sell Dead Space 2 on Steam while EA Support has "sunset" the activation tool, locking out legitimate owners after hardware changes.
|Company=Electronic Arts
|Product=Dead Space 2
|StartDate=2022-12-09
|Status=Ongoing
|Categories=Digital rights management; Activation lockout; Game preservation
}}

'''Dead Space 2 activation limit lockout''' is an ongoing consumer rights incident in which paying owners of the 2011 single-player survival horror game ''Dead Space 2'' are locked out of the product by its TAGES Solidshield content-protection system after exceeding a five-machine activation cap, while [[Electronic Arts]] continues to sell the game on [[Steam]] for $19.99 and EA Support has stated since at least December 2022 that the title has been "sunset" and that the company has no tool available to validate or reset activations.<ref name="steam-store">{{Cite web|url=https://store.steampowered.com/app/47780/Dead_Space_2/|title=Dead Space 2 on Steam|website=Steam|publisher=Valve Corporation|access-date=2026-05-08}}</ref><ref name="steam-1742">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/1742226629869067946/|title=Activation Limit Exceeded?|website=Steam Community Discussions: Dead Space 2|date=2018-11-24|access-date=2026-05-08}}</ref> Lockouts are triggered by routine consumer actions including operating-system reinstalls, hardware upgrades, hard-drive failures, and installation on a Steam Deck, and the issue is independent of the December 2023 shutdown of the game's multiplayer master server.<ref name="pcgw-ds2">{{Cite web|url=https://www.pcgamingwiki.com/wiki/Dead_Space_2|title=Dead Space 2|website=PCGamingWiki|access-date=2026-05-08}}</ref><ref name="steam-4039">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/4039228371162524644/|title=Steam Deck key activation issue|website=Steam Community Discussions: Dead Space 2|date=2023-11-26|access-date=2026-05-08}}</ref>

== Background ==

''Dead Space 2'' was developed by Visceral Games and published by Electronic Arts on January 25, 2011 for Windows, PlayStation 3, and Xbox 360.<ref name="wp-ds2">{{Cite web|url=https://en.wikipedia.org/wiki/Dead_Space_2|title=Dead Space 2|website=Wikipedia|access-date=2026-05-08}}</ref> The PC version uses TAGES Solidshield as its active content-protection technology. PCGamingWiki additionally records retail DVDs as shipping with SecuROM Disc First Authentication, though Electronic Arts' published ''Dead Space 2'' EULA references only Solidshield.<ref name="pcgw-ds2" /> The game's Steam store page carries the publisher's Online Disclaimer, which states that the "GAME USES SOLIDSHIELD CONTENT PROTECTION TECHNOLOGY" & that the "GAME CAN BE PLAYED ON UP TO FIVE COMPUTERS AT THE SAME TIME; USERS CAN MANAGE WHICH COMPUTERS ARE AUTHORIZED OR DE-AUTHORIZED TO PLAY GAME," directing users to <code>http://activate.ea.com/deauthorize/</code> for de-authorization.<ref name="steam-store" />

The five-machine cap is the same numerical limit Electronic Arts adopted for ''Spore'' in September 2008 after the original three-install cap drew a class-action lawsuit, ''Thomas v. Electronic Arts'', filed in the U.S. District Court for the Northern District of California over undisclosed [[SecuROM]] installation and kernel-level operation.<ref name="cnet-spore">{{Cite web|url=https://www.cnet.com/culture/ea-hit-with-class-action-suit-over-spore/|title=EA hit with class action suit over Spore|last=Guevin|first=Jennifer|website=CNET|date=2008-09-24|access-date=2026-05-08}}</ref><ref name="wp-securom">{{Cite web|url=https://en.wikipedia.org/wiki/SecuROM|title=SecuROM|website=Wikipedia|access-date=2026-05-08}}</ref> ''Dead Space 2'' shipped with that five-activation ceiling from launch and has retained it through every storefront iteration since.<ref name="steam-store" />

== Activation lockout mechanism ==

Solidshield binds each authorization to a hardware fingerprint of the machine on which the game is launched. An activation slot is consumed each time the game is installed and run on a new combination of hardware components, and a slot is recovered only if the user runs the in-game de-authorization utility on the original system before that system is decommissioned. Steam community members have documented the relevant binary as a small "activation" application sitting next to the game files in the local Steam library.<ref name="steam-1742" /><ref name="steam-4039" />

In practice, slots are routinely lost without the user's knowledge. A user posting to a Steam discussion thread in October 2022 reported losing two of five activations to "one PC totally dead and the other was a laptop I returned and didn't know to deactivate DS2 before uninstalling steam," leaving them juggling three remaining slots.<ref name="steam-1742" /> A November 2023 thread describes the cap being hit when the owner attempted to install the game on a [[Steam Deck]] after playing it on a desktop PC; the workaround required de-authorizing the desktop install first, leaving the user with a single remaining slot for any future hardware change.<ref name="steam-4039" /> Earlier threads from October 2018 and November 2018 record the same pattern after a routine PC reformat, with EA support either unresponsive or pointing to URLs that no longer functioned.<ref name="steam-5523">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/552359157631595398/|title=Cant play game, Activation limit exceeded|website=Steam Community Discussions: Dead Space 2|date=2018-10-14|access-date=2026-05-08}}</ref><ref name="steam-1742" /> Reports continued through July 2020, March 2025, and August 2025, with the most recent commenters noting that EA's Help site no longer lists the original ''Dead Space'' or ''Dead Space 2'' at all, only the 2023 ''Dead Space'' remake.<ref name="steam-2791">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/2791621151153569169/|title="Activation limit reached for this serial number has been exceeded"|website=Steam Community Discussions: Dead Space 2|date=2020-07-28|access-date=2026-05-08}}</ref><ref name="steam-3276">{{Cite web|url=https://steamcommunity.com/app/47780/discussions/0/3276824488726023468/|title=Activation Key Limit Reached|website=Steam Community Discussions: Dead Space 2|date=2025-03-13|access-date=2026-05-08}}</ref>

The de-authorization URL printed on the Steam Online Disclaimer remains live and returns HTTP 200, but multiple 2024 and 2025 user reports describe the linked tool as detecting nothing and failing to free a slot bound to a now-dead machine.<ref name="ea-deauth">{{Cite web|url=https://activate.ea.com/deauthorize/|title=EA Game De-authorization|publisher=Electronic Arts|access-date=2026-05-08}}</ref><ref name="steam-3276" />

== EA Support response ==

The earliest archived EA Support reply on the issue dates to a Steam Community thread published December 9, 2022, in which a user who had repurchased the game multiple times to escape the cap quoted the response received from EA Support verbatim: "I wish I could reset the activation limit, unfortunately Dead Space 2 game has been sunset many time ago and we dont have any tool to validate this game."<ref name="steam-1742" /> The quote predates the December 8, 2023 multiplayer server shutdown by almost a full year, establishing that EA had abandoned the customer-support side of single-player activation reset before the multiplayer infrastructure was decommissioned.<ref name="steam-1742" /><ref name="eurogamer-ngan">{{Cite web|url=https://www.eurogamer.net/ea-closing-crysis-3-dead-space-2-and-dantes-inferno-servers-later-this-year|title=EA closing Crysis 3, Dead Space 2 and Dante's Inferno servers later this year|last=Ngan|first=Liv|website=Eurogamer|date=2023-08-08|access-date=2026-05-08}}</ref>

In a July 2024 EA Forums thread, a Steam owner who had bought the game in 2012 reported being unable to find ''Dead Space 2'' anywhere in EA's online support tool. An EA staff account, "EA_Shepard," replied that EA would have to "check the code itself" to address the lockout, and instructed the user to open a support ticket against any unrelated EA title because ''Dead Space 2'' was not selectable as a product on EA Help.<ref name="ea-forum-7244303">{{Cite web|url=https://forums.ea.com/discussions/dead-space-franchise-discussion-en/steam-dead-space-2-activation-limit-has-been-exceeded/7244303|title=[Steam] Dead Space 2 "activation limit has been exceeded!"|website=EA Forums|date=2024-07-23|access-date=2026-05-08}}</ref> A March 2025 Steam thread documents an EA customer-service representative telling a Steam Deck owner whose laptop had died that they were out of luck, and multiple users on the same thread reported that the linked de-authorization tool failed to detect a stale activation slot.<ref name="steam-3276" /> An August 2025 commenter on the same thread confirmed that EA Help still listed only the 2023 ''Dead Space'' remake, with no entry for ''Dead Space 2''.<ref name="steam-3276" />

The EA Forums archive includes earlier lockout reports as well, including a 2012 thread in which EA referred a user to the original <code>activate.ea.com/deauthorize/</code> page, and a separate thread documenting the in-game DeAuthorizeManagement utility failing to remove a stale activation.<ref name="ea-answers-396246">{{Cite web|url=https://answers.ea.com/t5/Other-Dead-Space-Games/Old-Report-Dead-Space-2-Serial-key-limit/m-p/396246|title=[Old Report] Dead Space 2 Serial key limit|website=EA Help / Answers HQ|access-date=2026-05-08}}</ref><ref name="ea-forum-7228344">{{Cite web|url=https://forums.ea.com/discussions/dead-space-franchise-discussion-en/the-activation-limit-for-dead-space-2-serial-number-has-been-exceeded/7228344|title=the activation limit for Dead Space 2 serial number has been exceeded|website=EA Forums|access-date=2026-05-08}}</ref>

== December 2023 multiplayer server shutdown ==

On August 8, 2023, Eurogamer reporter Liv Ngan reported that Electronic Arts had announced the closure of online services for ''Crysis 3'', ''Dead Space 2'', and ''Dante's Inferno''. ''Crysis 3'' servers were shut down on September 7, 2023. ''Dead Space 2'' and ''Dante's Inferno'' servers were shut down on December 8, 2023. The affected mode for ''Dead Space 2'' was the asymmetric multiplayer mode (commonly referred to in coverage as "Outbreak," the name of its DLC map pack) on PC, PS3, and Xbox 360, alongside three Battlefield titles closed the same day.<ref name="eurogamer-ngan" /> The shutdown is also recorded on EA's Online Service Updates page and in PCGamingWiki's documentation of the title.<ref name="ea-service-updates">{{Cite web|url=https://www.ea.com/service-updates|title=Service Updates|website=Electronic Arts|access-date=2026-05-08}}</ref><ref name="pcgw-ds2" />

The multiplayer shutdown is structurally separate from the activation lockout. ''Dead Space 2'' is a single-player game with an optional multiplayer mode bolted on; the Solidshield client-side activation gate enforces the five-machine cap regardless of whether the multiplayer servers are reachable, and the abandonment of EA Support's activation-reset capability had been documented in writing a year before December 2023.<ref name="steam-1742" /><ref name="pcgw-ds2" />

== Continued sale on Steam ==

As of May 2026, ''Dead Space 2'' remains listed for sale on Steam at $19.99 with a "Very Positive" review aggregate.<ref name="steam-store" /> The store page's Online Disclaimer continues to advertise the de-authorization workflow at <code>activate.ea.com/deauthorize/</code> as the consumer's remedy for managing the five-machine cap, but the disclaimer carries no notice that EA Support has stopped processing activation resets for the title or that the linked tool has been described by users as non-functional.<ref name="steam-store" /><ref name="steam-3276" />

Valve's refund window closes fourteen days after purchase; activation-cap lockouts surface years later, when the buyer's first PC has been replaced and the consumed slot cannot be recovered. Valve states that it will issue a refund "if the request is made within the required return period, and, in the case of games, if the title has been played for less than two hours," with the standard return period set at fourteen days from purchase.<ref name="steam-refunds">{{Cite web|url=https://store.steampowered.com/steam_refunds|title=Steam Refunds|website=Steam|publisher=Valve Corporation|access-date=2026-05-08}}</ref> The August 2025 Steam commenter cited above noted owning a copy not installed in over a decade.<ref name="steam-3276" />

== Legal context ==

No United States Federal Trade Commission action, no state attorney general enforcement, no European Commission proceeding, no UK Competition and Markets Authority docket, and no Australian Competition and Consumer Commission case has been filed against Electronic Arts specifically over the ''Dead Space 2'' activation lockout. The closest historical analogues remain ''Thomas v. Electronic Arts'' over ''Spore'' in 2008, which forced the activation cap up from three to five and produced the original de-authorization tool, and the FTC's 2007 Sony BMG rootkit settlement under Section 5 of the FTC Act, neither of which addresses the present incident directly.<ref name="cnet-spore" /><ref name="wp-securom" />

For new sales of the title in the European Union after January 1, 2022, the EU Digital Content Directive (Directive (EU) 2019/770) imposes a conformity obligation on the trader, including a duty under Article 8(2) to supply the updates "necessary to keep the digital content or digital service in conformity" for the period the consumer may reasonably expect, with remedies of bringing the content into conformity, price reduction, or contract termination available to consumers under Articles 13 and 14 where the content is not in conformity.<ref name="dcd-2019-770">{{Cite web|url=https://eur-lex.europa.eu/eli/dir/2019/770/oj|title=Directive (EU) 2019/770 on certain aspects concerning contracts for the supply of digital content and digital services|website=EUR-Lex|publisher=Publications Office of the European Union|date=2019-05-20|access-date=2026-05-08}}</ref> In the United Kingdom, the Consumer Rights Act 2015, Part 1, Chapter 3 establishes parallel rights covering satisfactory quality (section 34), conformity to description (section 36), and a right to repair or replacement of non-conforming digital content, granted by section 42(2)(a) and detailed at section 43.<ref name="cra-2015-c3">{{Cite web|url=https://www.legislation.gov.uk/ukpga/2015/15/part/1/chapter/3|title=Consumer Rights Act 2015, Part 1, Chapter 3 (Digital content)|website=legislation.gov.uk|publisher=The National Archives|access-date=2026-05-08}}</ref> In the United States, the Magnuson-Moss Warranty Act at 15 U.S.C. §§ 2301-2312 supplies the implied warranty of merchantability framework, although its application to software sold under perpetual-license terms remains contested.<ref name="usc-mmwa">{{Cite web|url=https://www.law.cornell.edu/uscode/text/15/chapter-50|title=15 U.S. Code Chapter 50 - Consumer Product Warranties|website=Legal Information Institute|publisher=Cornell Law School|access-date=2026-05-08}}</ref>

The U.S. Library of Congress's most recent triennial rulemaking under [[DMCA Section 1201]], published October 28, 2024, renews the video-game preservation exemption, but limits it to games "no longer reasonably available in the commercial marketplace." Because Electronic Arts continues to sell ''Dead Space 2'' on Steam, an owner who circumvents Solidshield to play the copy they already paid for may not qualify for that exemption.<ref name="dmca-1201-2024">{{Cite web|url=https://www.federalregister.gov/documents/2024/10/28/2024-24563/exemption-to-prohibition-on-circumvention-of-copyright-protection-systems-for-access-control|title=Exemption to Prohibition on Circumvention of Copyright Protection Systems for Access Control Technologies|website=Federal Register|publisher=Library of Congress|date=2024-10-28|access-date=2026-05-08}}</ref>

== Consumer response ==

Affected owners have documented the issue across the Steam Community discussion boards for ''Dead Space 2'' and on EA's own forums, with threads stretching from 2018 to December 2025.<ref name="steam-5523" /><ref name="steam-2791" /><ref name="steam-1742" /><ref name="steam-3276" /> PCGamingWiki maintains a community-curated technical entry recording the DRM stack, the five-machine cap, and the December 8, 2023 server shutdown.<ref name="pcgw-ds2" /> A recurring user-suggested workaround in those threads is the application of an unofficial no-CD executable replacement that bypasses the Solidshield check entirely; the practice is documented in the threads but sits in the legal grey zone described by the DMCA Section 1201 rulemaking above.<ref name="steam-2791" /><ref name="steam-3276" />

The pattern has parallels in active consumer-protection litigation. On March 31, 2026, Rock Paper Shotgun reported that the French consumer group UFC-Que Choisir had sued Ubisoft over the March 2024 server shutdown of ''The Crew'', with backing from the [[Stop Killing Games]] movement.<ref name="rps-ubisoft">{{Cite web|url=https://www.rockpapershotgun.com/major-french-consumer-group-sue-ubisoft-over-always-online-game-shutdowns-with-the-backing-of-stop-killing-games|title=Ubisoft sued for shutting down The Crew's servers by major French consumer group backed by Stop Killing Games|website=Rock Paper Shotgun|date=2026-03-31|access-date=2026-05-08}}</ref> The suit highlights a pattern documented in the ''Dead Space 2'' record as well: a publisher discontinues the infrastructure required to play a product while the product remains in commerce. Stop Killing Games separately organized a European Citizens' Initiative, "Stop Destroying Videogames," registered with the European Commission, that closed its signature collection in 2025 and triggered a mandatory Commission response on the broader question of publisher abandonment of in-commerce video games.<ref name="eci-skg">{{Cite web|url=https://eci.ec.europa.eu/045/public/|title=Stop Destroying Videogames - European Citizens' Initiative|website=European Citizens' Initiative|publisher=European Commission|access-date=2026-05-08}}</ref><ref name="skg-site">{{Cite web|url=https://www.stopkillinggames.com/|title=Stop Killing Games|website=Stop Killing Games|access-date=2026-05-08}}</ref>

== See also ==

* [[Electronic Arts]]
* [[SecuROM]]
* [[Spore (game)]]
* [[Stop Killing Games]]
* [[Adobe Creative Suite activation]]
* [[Activation]]
* [[Discontinuation bricking]]
* [[Storefront shutdown]]
* [[Games as a service]]
* [[Denuvo]]
* [[Digital rights management]]
* [[DMCA Section 1201]]
* [[Video game preservation]]
* [[List of discontinued online-only video games]]

== References ==

{{reflist}}

[[Category:Electronic Arts]]
[[Category:Digital rights management]]
[[Category:Activation lockout]]
[[Category:Game preservation]]
[[Category:Incidents]]

Bambu Lab Authorization Control System

2026-05-04T11:59:09Z

Louis: added section on the cease and desist bambu sent jarczak over the orcaslicer-bambulab fork that re-enabled features after the auth control system rollout, plus minor cleanup

{{IncidentCargo
|Company=Bambu Lab
|StartDate=2025-01-16
|Status=Active
|Type=Post-purchase terms change
|Description=On January 16, 2025,Bambu Lab announced that future firmwares for their 3D printers would have an authorization and authentication mechanism.
}}
On January 16, 2025, the 3D-printer manufacturer '''[[Bambu Lab]]''' announced that future firmwares for their 3D printers would introduce an authorization and authentication protection mechanism for their connection and control, [[Deceptive language frequently used against consumers|in the name of security]]. This mechanism restricts the use of third-party accessories and slicers, such as Panda Touch and OrcaSlicer.
==Controversy regarding firmware updates==
[[File:Bambu tos screenshot.png|alt=bambu terms stating print jobs may not function properly if update is not performed to new firmware which is highly limiting. |thumb|Bambu terms regarding printer functionality & potential for disrupted print jobs if users do not update to a new firmware that radically restricts the autonomy of the owner of the printer]]

===Potential for remote disabling of printers===
A significant concern raised by the community revolves around the wording in Bambu Lab's [[Terms of Service]] (ToS) and firmware update announcements. Critics and users argue that the phrasing leaves open the possibility for the manufacturer to [[Remote disabling|remotely disable]] printers that are not updated to the latest firmware. Specifically, Bambu Lab's ToS<ref name=":2">{{Cite web |date=2024-04-24 |title=Terms of Use |url=https://bambulab.com/en-us/policies/terms |url-status=live |archive-url=https://ghostarchive.org/archive/vPu9I |archive-date=2026-03-09 |access-date=1 May 2025 |website=[[Bambu Lab]]}}</ref> states that printers '''"may block new print jobs"''' if updates are not applied, which some users interpret as a potential pathway for forced obsolescence.<ref name="firmware-update-introducing-new-authorization-control-system-2">{{Cite web |last=Bambu Kidd |date=2025-01-16 |title=Firmware Update Introducing New Authorization Control System |url=https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/ |url-status=live |archive-url=https://ghostarchive.org/archive/qwL63 |archive-date=2026-03-07 |website=[[Bambu Lab]] Blog}}</ref> While defenders of Bambu Lab point out that offline modes such as SD-card printing and [[wikipedia:Local_area_network|LAN]]-only setups would remain functional, others point out that the ToS do not explicitly limit this restriction to [[Cloud (service)|cloud]]-based printing. This ambiguity has led to speculation that Bambu Lab could enforce broader limitations, effectively rendering printers inoperable for users who choose not to update.<ref name=":3">{{Cite web |last=@nickjohnson |title=Bambu Lab reserves the right to brick your printer until you update the firmware |url=https://old.reddit.com/r/BambuLab/comments/1i45iy2/bambu_lab_reserves_the_right_to_brick_your/ |url-status=live |archive-url=https://web.archive.org/web/20250119220606/https://old.reddit.com/r/BambuLab/comments/1i45iy2/bambu_lab_reserves_the_right_to_brick_your/ |archive-date=19 Jan 2025 |access-date=1 May 2025 |website=Old [[Reddit]]}}</ref>

====Editing of initial announcement====
Bambu users were concerned they would not be able to use their printer if they did not install this update, due to the wording of the blog and the ToS.<ref>[[:File:Bambu tos screenshot.png]]</ref> This caused confusion since users report that Bambu's blog post dated January 16th<ref name="firmware-update-introducing-new-authorization-control-system-2" /> specifically says the following:
<blockquote>What happens if I never upgrade to this firmware?

You may continue using an older firmware version that does not include the new security updates; however, this means the printers may miss out on important security fixes or bug patches included in newer versions. We highly encourage updating to the latest firmware version for the best experience and enhanced security.</blockquote>However, '''this was not present on the day of the announcement.''' A snapshot of their webpage from archive.is demonstrates this section did not exist on the day of the announcement, when community members voiced their concerns.<ref name="firmware-update-introducing-new-authorization-control-system-2" /><ref>[[:File:2024-01-16-Firmware Update Introducing New Authorization Control System.pdf]]</ref> Bambu's response to community feedback<ref>{{Cite web |last=@Spaghetti Monster |date=20 Jan 2025 |title=Updates and Third-Party Integration with Bambu Connect |url=https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |url-status=live |archive-url=https://ghostarchive.org/archive/cIejw |archive-date=2026-03-30 |access-date=1 May 2025 |website=Bambu Lab Blog}}</ref> references ''"social media posts spreading baseless allegations and untrue claims about Bambu Lab",'' including ''"Firmware updates will block your printer’s ability to print.",'' without mentioning the context for those allegations. The context for those allegations was the lack of inclusion of the ''"What happens if I never upgrade to this firmware?"'' in Bambu's initial announcement alongside their stated terms of service.

This announcement, after the edit in question, clearly states in the header - '''''Updated: January 17, 2025''' - to include additional details and FAQs where the '''What happens if I never upgrade to this firmware?''' among others was added.''

As per webpage oldest snapshot from '''archive.is'''<ref name="firmware-update-introducing-new-authorization-control-system-22">{{Cite web |last=@BambuKidd |date=16 Jan 2025 |title=Firmware Update Introducing New Authorization Control System |url=https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/ |url-status=live |archive-url=https://ghostarchive.org/archive/qwL63 |archive-date=2026-03-07 |access-date=2025-05-01 |website=[[Bambu Lab]] Blog}}</ref> dated 16 Jan 2025 17:31 UTC there are two references if choosing to stay on the old firmware:<blockquote>

==== Important Information for End Users ====
2. Old Firmware Option:
Users who decide to use an older firmware version can still use the previous or new versions of Bambu Studio and Bambu Handy without restrictions.
</blockquote>
Statement reads that user can choose to stay on the previous firmware and will not be punished for their choice by exclusion from access of first party updated software tools.<blockquote>
==== Information for OrcaSlicer users ====
 1. You can continue using your X Series 3D printer with the older firmware version (which does not include Authorization Features). 
2. If you choose to upgrade to the firmware version with Authorization Features, you must download and install Bambu Connect (a printer control software)... 
</blockquote>
Statement reads that users have the right of choice to upgrade or stay on the older firmware.

While FAQ section was added after the initial blog post publication:
*It appears to summarize unedited information available in the original article.
*Addition of the FAQ section, and as a result - editing the initial article, are clearly announced.

===Debate over "bricking" terminology===
''The debate has also "''extended to the definition of 'bricking':" Some community members assert that if a printer is unable to accept new print jobs without an update, it effectively becomes non-functional and qualifies as being "bricked." Others counter that as long as certain offline functionalities remain (such as SD-card printing) the term does not accurately apply.<ref name=":3" />

===Privacy policy issues===
Bambu Lab's privacy policy, under "Personal Data that we collect," explicitly states: "3D Model in each client ('Printing Files') and other information related to the print job we may store, including start times, finish times, filament consumption and other relevant information."<ref name=":6">{{Cite web |date=25 Mar 2025 |title=Privacy Policy |url=https://bambulab.com/en-us/policies/privacy |url-status=live |archive-url=https://ghostarchive.org/archive/0XOv5 |archive-date=2026-03-10 |access-date=1 May 2025 |website=[[Bambu Lab]]}}</ref> This contradicts their claim that they do not monitor 3D prints. Additionally, the privacy policy webpage is notably excluded from the Wayback Machine, raising concerns about transparency and accountability in their data practices.<ref name=":6" />

===Community strategies to deal with risks===
Users have discussed strategies to avoid possible disruptions, including:
*Operating printers exclusively in offline modes.
*Utilizing LAN connections or VPN setups: this requires an access key from the printer (previously, you could use your cloud credentials over LAN).
*Exploring alternative firmware or third-party scripts to restore full functionality.<ref name=":3" />

==Bambu Lab's justification and rebuttal==
Bambu Lab has stated that the authorization system is in place in order to protect against "remote hacks," "printer exposure," and "abnormal traffic or attacks." There are, however, several ways to mitigate these risks without the loss of user control that their system causes:

*'''The "remote hacks" that were cited as an example in the article seem to be a direct result of the 3D-printer vendor not responding properly to a reported security vulnerability in their product.<ref>{{Cite web |last=Cluley |first=Graham |date=1 Mar 2024 |title=Someone is hacking 3D printers to warn owners of a security flaw |url=https://www.bitdefender.com/en-au/blog/hotforsecurity/someone-is-hacking-3d-printers-to-warn-owners-of-a-security-flaw?ref=blog.bambulab.com |url-status=live |archive-url=https://web.archive.org/web/20260216002646/https://www.bitdefender.com/en-au/blog/hotforsecurity/someone-is-hacking-3d-printers-to-warn-owners-of-a-security-flaw?ref=blog.bambulab.com |archive-date=16 Feb 2026 |access-date=1 May 2025 |website=[[Bitdefender]]}}</ref> Therefore, in order to get attention, the researcher decided to infect machines and display a harmless message to spread publicity.''' Properly responding to security vulnerabilities, working to patch them quickly, and working with the security community (who would be more than happy to help secure products) would be some ways to prevent this.
*In the article cited about printer exposure, the hack was carried out largely because of user misconfiguration.<ref>{{Cite web |last=Ms. Smith |date=5 Sep 2018 |title=Over 3,700 exposed 3D printers open to remote attackers |url=https://www.csoonline.com/article/566223/over-3700-exposed-3d-printers-open-to-remote-attackers.html?ref=blog.bambulab.com |url-status=live |archive-url=https://web.archive.org/web/20260216002556/https://www.csoonline.com/article/566223/over-3700-exposed-3d-printers-open-to-remote-attackers.html?ref=blog.bambulab.com |archive-date=16 Feb 2026 |access-date=1 May 2025 |website=[[CSO]]}}</ref> Printer exposure can be mitigated by offering more convenient ways to securely expose printers to the internet, so that users are not tempted to allow unauthenticated access over the network.
*The "abnormal traffic" can be mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.<ref>{{Cite web |title=Summary of Security Incident Responses and Abnormal Cloud Traffic |url=https://wiki.bambulab.com/en/security-incidents-cloud-traffic?ref=blog.bambulab.com |url-status=live |archive-url= |archive-date= |access-date=1 May 2025 |website=[[Bambu Lab]] Wiki}}</ref>
*"Other malicious devices in the LAN" can be partially mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.<ref>{{Cite web |last=@SpaghettiMonster |date=25 Nov 2022 |title=Answering network security concerns for our printers |url=https://blog.bambulab.com/answering-network-security-concerns/ |url-status=live |archive-url=https://ghostarchive.org/archive/CE0Ii |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Blog}}</ref> Another mitigation is to add stronger authentication mechanisms, rather than using a weak pre-shared LAN access code as is currently the case.

==Issues with LAN mode requiring authorization==
[[File:Bambu Connect App - Lan Device Discovery without Bambu Login.png|thumb|Bambu Connect App - Lan Device Discovery without Bambu Login]]
Bambu Lab printers have the ability to be controlled over both cloud and LAN. This allowed users to integrate their printers into private networks and maintain full control without having to rely on the manufacturer's server while also allowing cloud access. The new authorization system mandates that even LAN-based operations must go through an authentication process using Bambu Connect to retain full control.<ref name="bambu-connect">{{Cite web |last=@Nil.lin |title=Bambu Connect (beta) |url=https://wiki.bambulab.com/en/software/bambu-connect |url-status=live |archive-url=https://ghostarchive.org/archive/CVCtK |archive-date=2026-03-30 |access-date=1 May 2025 |website=[[Bambu Lab]] Wiki}}</ref> Full local access is still possible and unchanged for those not using the cloud.

This change has drawn criticism for many reasons:
*'''Privacy concerns''': Requiring authentication for LAN mode raises concerns about data being unnecessarily exposed to Bambu Lab's servers, even for local-only operations, though previously, the printer was also connected and could be controlled by the cloud even when sending prints locally.
**Confidentiality required by US Law - This is in conflict with those that have to comply with 18 CFR § 3a.61, 32 CFR § 117.15, 32 CFR § 2001.47, and other restrictions.
*'''Loss of offline independence while also using cloud''': Before, users could have hybrid offline setups. The requirement for authentication removes this option unless users revert to older firmware versions; Bambu Lab initially indicated rollback would not be permitted, though The Verge later reported that users could still downgrade and use LAN access keys while signed into the cloud.
*'''Increased complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control while retaining cloud functionality.<ref name=":4">{{Cite web |last=@edlboston |date=Jan 2023 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Yes, I know about the LAN mode. But as has been stated by many people, things like the camera will not work, nor will the Handy app. There is no technical reason that these are bound to the cloud. This is the problem and why I titled this FULL Non-Cloud Network.}}</ref>

*LAN-Only mode in Orca Slicer is implemented by passing API Calls to the installed proprietary Bambu Network Plug-In (unlike BTT and other solutions that did indeed communicate with printer directly via MQTT protocol).
*Plug-In provides controls for Printers "Critical Operations" (as classified by the Firmware Announcement article) and displays these controls within the window of Orca Slicer.
*Using intermediary Plug-In does not manifest as "direct access through network plugin". It is still a Proxy communication, even if user experience is presented as direct communication (same slicer window).
*Bambu Connect moves the Network Plug-In functionality outside of the window of Orca Slicer thus appearing as separate window and presents the appearance of "indirect" communication channel to the printer.
*While the user experience is different, the flow remains unchanged Orca Slicer slices model -> Orca Slicer Calls API of Bambu Proprietary Software -> Bambu Proprietary Software controls the printer.

Additionally, Bambu Connect software (downloaded and installed on 19.01.2024 (2025?) before the backlash response) supports adding LAN-Only printers without requiring Bambu Account authentication, the same behavior as the Network Plugin used in Orca Slicer.

===Precedents and comparisons===
Critics have likened this potential functionality to similar cases in other industries where manufacturers remotely restrict product features. A documented example is [[HP]]'s printer firmware updates that [[HP Instant Ink|rendered third-party ink cartridges unusable]], which became the subject of a class-action settlement.<ref name=":5">{{Cite web |last=Harding |first=Scharon |date=2025-03-19 |title=HP avoids monetary damages over bricked printers in class-action settlement |url=https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |url-status=live |archive-url=http://web.archive.org/web/20250319231817/https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |archive-date=2025-03-19 |website=Ars Technica}}</ref>

===X1E firmware 01.01.02.00 LAN only connection "BUG"===
Newly received X1E printers with firmware 01.01.02.00 will not connect to the Bambu Studio using the Lan only method password. Bambu Studio identifies the un-logged printer but will not allow a connection to the printer. Only after connection / account paring is done over the Bambu Handy app by giving internet access to the PC and Printer then utilizing the cloud service connection will Lan only communication and login work.<ref>{{Cite web |last= |date=Sep 2024 |title=Connect X1E to stand-alone computer |url=https://forum.bambulab.com/t/connect-x1e-to-stand-alone-computer/101474 |url-status=live |archive-url=https://web.archive.org/web/20260223033045/https://forum.bambulab.com/t/connect-x1e-to-stand-alone-computer/101474 |archive-date=23 Feb 2026 |access-date=1 May 2025 |website=[[Bambu Lab]] Community Forum}}</ref>

==Implementation timeline and requirements==

The authorization system will be rolled out in phases, starting with the X1 series printers. A beta firmware (version 01.08.03.00) was released on January 17, 2025, with the full release scheduled for January 23, 2025. The P & A series printers will get similar updates at an unspecified future date.

To use printers with the new authorization system, users must update multiple pieces of software:
*Bambu Studio must be updated to version 01.10.02.64 or higher
*Bambu Handy mobile app must be updated to version 2.17.0 or higher
*The new Bambu Connect application must be installed for using third-party slicers

These software updates are mandatory for users who update their firmware. Failing to update all components simultaneously will result in certain printer controls becoming unusable. Users who choose to maintain third-party software compatibility can continue using older firmware versions, or downgrade the firmware for new printers that ship with the authorization system pre-installed.

Bambu Lab states these coordinated updates are necessary because the new authorization system fundamentally changes how the printer validates and accepts commands. The older versions of Bambu Studio and Bambu Handy lack the authentication mechanisms required to interact with printers running the new firmware. The Bambu Connect application was created specifically to provide a controlled interface for third-party software, replacing the previous direct access through network plugins.<ref name="firmware-update-introducing-new-authorization-control-system-2" />

==Impact on third-party integration and user choice==

===Changes to third-party access===
The new authorization system replaces direct network API access with a more limited URL-based interface through Bambu Connect. Third-party software can only interact with the printer by sending specific URL commands to Bambu Connect.<ref name="bambu-connect" /> The interface requires three parameters:

*<code>path</code>: The absolute file system path to the 3MF file (e.g., /tmp/cube.gcode.3mf)
*<code>name</code>: The name of the file (e.g., Cube)
*<code>version</code>: A fixed value of 1.0.0 for compatibility

A complete command must be formatted as:

bambu-connect://import-file?path=%2Ftmp%2Fcube.gcode.3mf&name=Cube&version=1.0.0

This interface only allows basic file transfer and print initiation. All other printer-control functions previously available to third-party software are now exclusive to Bambu's own applications. The path and name parameters must be URL-encoded using encodeURIComponent or equivalent functions<ref name="bambu-connect" />.

===Reduced home-automation capabilities===
While basic status monitoring remains available (e.g., print-progress updates in Home Assistant), the new firmware removes the ability for home-automation systems to control printer functions. Users can no longer:
*Start or stop prints remotely using Home Assistant, BTT Panda Touch,<ref name=":0">{{Cite web |last=@BIGTREETECH |date=2025-01-17 |title=BIGTREETECH's post |url=https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |url-status=live |archive-url=http://web.archive.org/web/20251004104021/https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |archive-date=2025-10-04 |access-date=2025-05-01 |website=[[Facebook]]}}</ref> or other third-party accessories or software interfaces
*Control printer temperatures or cooling
*Automate printer behaviors based on sensor data or events
*Access camera feeds through third-party applications<ref name="bambulab-forum-135400/9">{{Cite web |last=@hho |date=16 Jan 2025 |title=This new auth system will make me sell my printers |url=https://forum.bambulab.com/t/this-new-auth-system-will-make-me-sell-my-printers/135400/9 |url-status=live |archive-url=https://ghostarchive.org/archive/ro1KZ |archive-date=2026-03-30 |access-date=1 May 2025 |website=Bambu Lab Community Forum}}</ref>

===Permanent nature of the update===
Once a printer is updated to the new firmware, users can still revert to previous versions that allows full control of the printer using LAN mode access key while signed into the cloud.<ref>{{Cite web |last=Hollister |first=Sean |date=22 Jan 2025 |title=Here’s what Bambu will — and won’t — promise after its controversial 3D printer update |url=https://www.theverge.com/2025/1/21/24349031/bambu-3d-printer-update-authentication-filament-subscription-lock-answers |url-status=live |access-date=1 May 2025 |website=The Verge |archive-url=http://web.archive.org/web/20251122143504/https://www.theverge.com/2025/1/21/24349031/bambu-3d-printer-update-authentication-filament-subscription-lock-answers |archive-date=22 Nov 2025}}</ref> The option still exists to disable the cloud service.

The manufacturer states this change is required for security, but community members note that many of the security vulnerabilities being addressed stem from Bambu's own cloud-centric design choices rather than inherent risks of local network control<ref name="bambulab-forum-134549/12">{{Cite web |date=14 Jan 2025 |title=Bambu Studio 1.10.2 Public Beta |url=https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/12 |url-status=live |archive-url=https://ghostarchive.org/archive/u4vpc |archive-date=2026-03-30 |access-date=1 May 2025 |website=[[Bambu Lab]] Community Forum}}</ref>. The update forces users into using Bambu Connect middleware if they want to retain limited cloud functionality.

This can be characterised as a significant post-purchase reduction in functionality for existing owners who bought their printers with the understanding they could use third-party software and home-automation tools, but also only affects users actively choosing to use Bambu Cloud at the same time. The nature of the printer update is used to demonstrate how manufacturers can use software updates to unilaterally modify the capabilities of hardware products after purchase, although in this case the changes affect only people already choosing to use the cloud service<ref name=":4" />.

For users that would want to use a third-party slicer while using their cloud service, Bambu would require those users to download and install Bambu Connect in order to send gcode wirelessly over LAN or over the cloud. While Bambu claims that they were in contact with SoftFever, the developer of OrcaSlicer, as of writing, SoftFever still does not have any keys for Bambu Connect and the new firmware is only available as opt-in beta at the moment.<ref name=":1">{{Cite web |last=@fever_soft |date=18 Jan 2025 |title=This is definitely a bummer. I was negotiating for an authorization key to allow OrcaSlicer to communicate with their device like BambuStudio does, but today I was told they won't support this. Only their slicer can send prints directly; others must use their Bambu Connect application |url=https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |url-status=live |access-date=1 May 2025 |website=[[X]] |archive-url=http://web.archive.org/web/20251004104021/https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |archive-date=4 Oct 2025}}</ref>

==Impact on functionality==
While some functionality remains unauthenticated like in previous firmware versions (sending status information from the printer over the network, starting a print job using SD cards), the most important features now require authentication through a new closed-source client called Bambu Connect<ref name="bambu-connect" />. These restricted features include:

*Initializing prints via LAN or cloud mode
*Remote video access to monitor prints
*Controlling motion system, temperature, fans
*AMS settings and calibrations
*Home automation integration beyond basic status monitoring

Previously, third-party software such as OrcaSlicer<ref name="orca-slicer-issue8063">{{Cite web |date=16 Jan 2025 |title=FW 1.08.03.00 from Bambu WILL BREAK ORCASLICER for X, P and A series #8063 |url=https://github.com/SoftFever/OrcaSlicer/issues/8063 |url-status=live |archive-url=http://web.archive.org/web/20250708192842/https://github.com/SoftFever/OrcaSlicer/issues/8063 |archive-date=8 Jul 2025 |access-date=1 May 2025 |website=[[GitHub]]}}</ref> could interact with Bambu Lab printers via the open-source Bambu Studio and proprietary network plug-ins. While Bambu Connect provides a limited URL-based API to initiate prints, most functionality previously openly available is now restricted to Bambu's ecosystem<ref name="bambulab-forum-135400/9" />.

Previously, third-party accessories such as Panda Touch would allow users to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D-pad by default for printer control whereas Panda Touch is a full-color touch screen that had a small battery so that way users could reposition and detach their Panda Touch off their printers if needed. Users would be able to queue up jobs, jog printer motors, and connect to multiple printers at once in order to monitor print jobs. According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch not to update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch. <ref name=":0" />

==Communication with Panda Touch developers==

As of writing, no formal communication has happened between Big Tree Tech (BTT), the manufacturer and developer of Panda Touch, and Bambu Labs. Based on their Facebook announcement, BTT stated that they have reached out to Bambu and will update if Bambu responds to their correspondence<ref name=":0" />.

==Communication with OrcaSlicer developers==

Before the official announcement of the new authorization and authentication, Bambu Lab engaged with the OrcaSlicer development team regarding the changes. This communication has sparked discussion within the 3D-printing community, particularly regarding its timing, tone, and implications.

===Pre-announcement contact===
Reports from OrcaSlicer demonstrate that Bambu Lab provided limited advance notice of the changes that would render their software incompatible with Bambu printers running the new firmware. The communication emphasized:
*The introduction of Bambu Connect as the only supported method for interacting with third-party slicers.
*The discontinuation of the network plugin API that OrcaSlicer and other tools relied on for printer control<ref name="orca-slicer-issue8063" />.
*An invitation for OrcaSlicer developers to adapt their software to integrate with the Bambu Connect URL scheme.

The communication lacked the detailed technical documentation that would be necessary for developers to be able to work with the new requirements.

===How the community viewed these actions===
This approach has been interpreted by many as a calculated move by Bambu Lab to enforce tighter control over its ecosystem. Primary criticisms of Bambu were:
*'''Lack of transparency''': The limited warning given to OrcaSlicer developers indicates that Bambu Lab's internal rollout schedule preceded community engagement with existing customers. Point to the contrary: the new firmware is in beta and Bambu Connect middleware contains temporary compromises to allow third-party slicers to work as before.
*'''Lack of follow-through:''' As of writing, SoftFever, OrcaSlicer's lead developer, still does not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Bambu's original announcement prominently mentioned OrcaSlicer and gave the impression that Bambu is actively providing the necessary assets so that SoftFever would be able to implement the new software architecture so that OrcaSlicer users are able to still use OrcaSlicer to send gcode to their printers without needing Bambu Connect to be installed as a separate program. The lack of active cooperation does not reflect favorably upon Bambu as it seems like their announcement used OrcaSlicer's name to try to make it seem like Bambu is trying its best to make sure that developers have what they need, but in reality, their inaction seems to show that Bambu is not making a sincere attempt to ensure that OrcaSlicer remains supported<ref name=":1" />.
*'''Disregard for open-source collaboration''': OrcaSlicer is widely used in the community; it is an open-source effort to improve the 3D-printing experience for all customers. The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect removes customer choice in how the printer is operated.
*'''Token support for third-party tools''': While Bambu Connect provides a workaround for third-party slicer use, it significantly restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools<ref name="bambu-connect" />.
*'''Power imbalance''': As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users.

==Community-driven workarounds and technical alternatives==

The 3D-printing community has begun exploring potential workarounds to restore functionality and user autonomy. These efforts focus on bypassing or mitigating the limitations imposed by the firmware update.

===Custom firmware development===
Discussions within the community highlight interest in developing custom firmware as an alternative to Bambu's official updates. One prominent project mentioned in forums is the development of custom firmware for the X1-series printers, such as the "X1Plus Custom Firmware"<ref name="bambulab-forum-134549/12" />. This firmware aims to:
*Restore direct network control and third-party slicer compatibility.
*Re-enable previously available features such as motion-system adjustments, temperature control, and AMS settings without requiring proprietary software.
*Provide users with greater flexibility in integrating printers with home-automation systems and workflows.

However, custom firmware development faces several challenges, including:
*Limited documentation and proprietary hardware components, which complicate reverse-engineering efforts.
*The potential voiding of warranties and risks of bricking devices.
*Legal concerns regarding intellectual property and bypassing manufacturer-imposed restrictions.

==Backup of current third party access enabled firmware and network plugins==
This GitHub repository contains a backup of all the latest firmware released by Bambu Labs for their printers and of the network plugin used by slicers such as Orca Slicer to communicate with the printer: https://github.com/Tzeny/bambulabs_plugins_firmware.

==LAN mode and blocked internet access==
At the time of writing user Tzeny15 on reddit, has authored a five step guide to blocking internet access for the Bambu P1S as a precaution in case the manufacturer attempts to limit functionality for printers without the newest firmware.<ref> {{Cite web |last=@Tzeny15 |title=LAN mode with live view, remote monitoring+control and blocked internet access - a five step guide |url=https://www.reddit.com/r/BambuLab/comments/1i4vp5i/lan_mode_with_live_view_remote_monitoringcontrol/ |url-status=live |access-date=1 May 2025 |website=[[Reddit]] |archive-url=http://web.archive.org/web/20250310115818/https://old.reddit.com/r/BambuLab/comments/1i4vp5i/lan_mode_with_live_view_remote_monitoringcontrol/ |archive-date=10 Mar 2025}}</ref>

[[Bambu Lab LAN mode guide|Read the full guide here.]]

==Reverse engineering Bambu Connect==
{{:Reverse Engineering Bambu Connect}}

''[[Reverse Engineering Bambu Connect|Read more about reverse engineering Bambu Connect here.]]''

==Community tools and scripts==
In addition to firmware alternatives, some users have come up with custom scripts and software tools to interface with Bambu Lab printers indirectly. These tools often rely on:
*Reverse-engineering the URL-based commands required by Bambu Connect to enable partial functionality with third-party slicers like OrcaSlicer.
*Creating local server emulations to replicate the network API previously available before the update.

While these tools provide temporary solutions, they do not fully replace the open ecosystem that existed before the authorization update.

===Re-engineering printer-control electronics===
ChazLayyd's Bambu Lab Klipper Conversion project is currently in an incomplete stage<ref>{{Cite web |last=@ChazLayyd |title=Running Klipper on a Bambu Lab machine by replacing it's internal electronics with readily available open-source hardware. |url=https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion |url-status=live |access-date=1 May 2025 |website=GitHub |archive-url=http://web.archive.org/web/20251116182420/https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion |archive-date=16 Nov 2025}}</ref><ref>{{Cite web |title=DhazLayyd's Discord Community |url=https://discord.com/invite/W6B5mBejuC |url-access=registration |url-status=live |archive-url=https://web.archive.org/web/20260223033213/https://discord.com/invite/W6B5mBejuC |archive-date=2026-02-23 |website=[[Discord]]}}</ref>. While the project was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that run Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.

===Advocacy for open-ecosystem support===
Community members have also organized to advocate for open-source support and rollback options. Suggestions include:
*Allowing an opt-out option for existing users who prefer local network control without cloud dependency.
**This has always been possible; past firmware updates made signing into the cloud at any point unnecessary. This information continues to be ignored by some.
*Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.<ref name="orca-slicer-issue8063" />

===Alternative software to prevent auto update(tells the server its version 99+ for now)===
Currently X1Plus a OPEN SOURCE custom firmware version for Bambu Labs printers(more details on the GitHub page)

*Installation tutorials are available for users who have not yet updated. Installing third-party firmware will void the warranty. Users are advised to consult the GitHub documentation before installation.
*https://github.com/X1Plus/X1Plus
*The Bambu Labs website offers consumers the ability to request a rootable firmware to be sent to their printers. At the time of writing (Jan 26, 2025), the feature (in the EU at least) is broken such that you cannot finalize the process of requesting such a firmware. Ref: https://bambulab.com/en-eu/third-party-firmware/plan
**The result of accepting the terms of the page titled "Third Party Firmware Plan Guideline" and clicking "Next" takes you to a page titled "Important Notice and Risk Warning" which, when accepting the terms leaves you with an "I got it" button that takes you back to the previous page.

==Cease and desist against the OrcaSlicer-bambulab re-enablement project==

In April 2026, Bambu Lab sent a cease and desist communication to the developer of a third-party OrcaSlicer fork that had restored direct printer control after the Authorization Control System rollout. The project was wiped from public view the same day it appeared, and the developer published a summary of Bambu Lab's allegations but not the letter itself, citing Bambu Lab's refusal to authorize publication.<ref name="jarczak-readme">{{Cite web |last=Jarczak |first=Pawel |title=OrcaSlicer-bambulab — This is the end…. |url=https://github.com/jarczakpawel/OrcaSlicer-bambulab |url-status=live |archive-url=https://web.archive.org/web/20260430001537/https://github.com/jarczakpawel/OrcaSlicer-bambulab |archive-date=30 Apr 2026 |access-date=4 May 2026 |website=[[GitHub]]}}</ref>

===What OrcaSlicer is===
OrcaSlicer is a free, open-source slicer: a program that converts a 3D model file into the layer-by-layer instructions (G-code) a 3D printer needs to produce the physical object. It is maintained by the developer SoftFever and draws from Bambu Lab's Bambu Studio, which is itself a fork of Prusa Research's PrusaSlicer.<ref name="softfever-orcaslicer">{{Cite web |last=SoftFever |title=OrcaSlicer |url=https://github.com/SoftFever/OrcaSlicer |url-status=live |access-date=4 May 2026 |website=[[GitHub]]}}</ref> OrcaSlicer is widely used by owners of Bambu Lab printers as an alternative to Bambu Studio.<ref name="softfever-orcaslicer" /><ref name="xda-jarczak">{{Cite web |last=Batt |first=Simon |date=23 Apr 2026 |title=A developer restored OrcaSlicer's features that Bambu Lab killed — then the legal threats arrived |url=https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |url-status=live |archive-url=https://web.archive.org/web/20260427233833/https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |archive-date=27 Apr 2026 |access-date=4 May 2026 |website=XDA Developers}}</ref>

===What changed in January 2025===
The Authorization Control System announced on January 16, 2025 gated print initiation, motion control, fan and hotend temperature control, AMS configuration, calibrations, remote video, and firmware upgrade behind a Bambu-issued authentication path. Owners who installed the new firmware could no longer send print jobs from third-party slicers directly over the local network; they had to route those jobs through a new closed-source middleware, Bambu Connect.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> SoftFever was not given API keys for Bambu Connect and stated publicly that direct print sending from OrcaSlicer would not be supported going forward.<ref name=":1" />

===The OrcaSlicer-bambulab fork===
On April 23, 2026, the developer Pawel Jarczak (GitHub user <code>jarczakpawel</code>) made public a fork named OrcaSlicer-bambulab at <code>github.com/jarczakpawel/OrcaSlicer-bambulab</code>. The fork restored the ability to send print jobs from OrcaSlicer directly to Bambu Lab printers without routing through Bambu Connect.<ref name="xda-jarczak" /> According to Jarczak's own description, the fork worked by reaching the printer through a Linux-side workflow Bambu Lab had not yet disabled, and was built on publicly available Bambu Studio source code combined with the developer's own integration layer; it did not redistribute Bambu Lab's proprietary networking plugin binaries.<ref name="jarczak-readme" /><ref name="3druck-jarczak">{{Cite web |date=30 Apr 2026 |title=Developer ends OrcaSlicer fork after Bambu Lab threatens legal action |url=https://3druck.com/en/programs/developer-terminates-orcaslicer-fork-after-bambu-lab-threatens-to-sue-32156744/ |url-status=live |access-date=4 May 2026 |website=3Druck.com}}</ref>

===The cease and desist===
Bambu Lab contacted Jarczak directly and demanded removal of the fork. According to Jarczak's own first-person account, Bambu Lab "referred to legal materials and stated that a cease and desist letter had been prepared", and alleged that the implementation "impersonated Bambu Studio, bypassed their authorization controls, violated their Terms of Use, involved 'reverse engineering', and could allow modified forks to send arbitrary commands to printers."<ref name="jarczak-readme" /> Jarczak rejected the reverse-engineering characterization, stating that his work was based on publicly available Bambu Studio source code, which Bambu Lab releases under the AGPL-3.0 license.<ref name="jarczak-readme" /><ref name="3druck-jarczak" /> Jarczak disputed the broader characterization and asked for specifics: the exact files or commits at issue, and the exact legal or contractual basis. He reports receiving "further broad accusations" instead of that specificity.<ref name="jarczak-readme" /> Bambu Lab refused consent for publication of the correspondence itself, and Jarczak elected to honor that refusal while retaining the letter.<ref name="jarczak-readme" /> The repository was wiped the same day it appeared.<ref name="jarczak-readme" /><ref name="xda-jarczak" /> Jarczak removed the contents voluntarily and stated this was a practical decision, not an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> XDA Developers reported that Bambu Lab had not responded to its request for comment as of publication.<ref name="xda-jarczak" /> 3Druck independently confirmed the same set of allegations, citing Jarczak's GitHub statement.<ref name="3druck-jarczak" />

The publicly documented allegations track Bambu Lab's [[Terms of Service]] and an "authorization bypass" framing.<ref name=":2" /><ref name="jarczak-readme" /> Because the letter itself was not made public, no primary source confirms which specific statute, if any, Bambu Lab invoked; neither Jarczak's account nor the secondary reporting names a specific statute, including the [[DMCA Section 1201|DMCA §1201]] anti-circumvention provision, as part of Bambu Lab's claim. The upstream OrcaSlicer maintainer SoftFever was not named in the cease and desist, has issued no public statement on the fork or the letter, and the upstream repository remains active.<ref name="softfever-orcaslicer" />

===Consumer-rights significance===
Bambu Lab printer owners had paid for hardware that, at the time of purchase, allowed third-party slicers to send print jobs directly over their own local network. The January 2025 firmware update removed that capability for owners who installed the update.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> When an independent developer rebuilt the lost capability on top of source code Bambu Lab itself publishes, the company's response was a private legal threat rather than a technical or contractual remedy that the affected owners could read or contest.<ref name="jarczak-readme" /> The developer took the project down and stated he had "no interest in maintaining a prolonged dispute".<ref name="jarczak-readme" />

==Impact on professional users and privacy concerns==

===Impact on professional users and print farms===
The restrictions imposed by the new authorization system create operational challenges for professional users who kept their printers signed into the cloud:

*Print farms can no longer use custom automation systems to manage multiple printers
*Workflows built around third-party software have to be completely redesigned
*The requirement to manually export and import files through Bambu Connect creates additional labor
*Integration with existing business systems and workflows becomes more difficult or impossible
*Professional users with more than 20 printers report the new workflow as "an absolute nightmare"<ref>{{Cite web |last=@drakko |date=16 Jan 2025 |title=This new auth system will make me sell my printers |url=https://forum.bambulab.com/t/this-new-auth-system-will-make-me-sell-my-printers/135400/3 |url-status=live |archive-url=https://ghostarchive.org/archive/yVBw8 |archive-date=2026-03-30 |access-date=1 May 2025 |website=Bambu Lab Community Forum |quote=Oh, the beta version. Luckily, I don’t allow new firmware on my machine, not until I see multiple validations from trustworthy users. So, in this respect I’m safe. Also, I never trust a beta version, no matter how reliable the releaser is.
Thx for the clarification @Square3D . Appreciated.}}</ref>
The solution to the above is not to sign the printer into the cloud. Keeping the printer signed in would be a security oversight in this use case on the part of the print farm.

===Privacy and data-collection concerns===

The shift toward mandatory use of Bambu's software ecosystem raises several privacy and data collection concerns:

*All printer operations must now pass through Bambu's cloud infrastructure when using cloud mode
*User print data, including file names and print settings, becomes visible to Bambu when cloud is used
*Operational data is processed through Bambu's servers while on a different network. The camera feed, on the other hand, is always peer-to-peer.
*Users have limited visibility into how their data is collected, stored, and used in the cloud
*The system creates dependence on Bambu's cloud services availability for basic printer functionality<ref name=":4" />

While Bambu Lab maintains that cloud processing is necessary for security and functionality, community members argue this represents unnecessary data collection that could be handled locally<ref name="bambulab-forum-134549/12" />. The company's cloud infrastructure costs are significant, leading some users to speculate that future monetization of the cloud services may be planned<ref name="bambulab-forum-3643/5">{{Cite web |last=@NeverDie |date=Jan 2025 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/5 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=Bambu Lab Community Forum |quote=I’m not disagreeing, but as a short-term workaround, are you able to write the print files to an SD card and then print from that? I’m too new to have tried it myself, but I thought that was at least an option.}}</ref>. Therefore, people should assess if their use case mandates the use of the cloud service and disable it when it doesn't.

Users who do not want their print data routed through Bambu's cloud infrastructure can operate their printers in LAN-only mode.

==Customer reactions==

Customer reactions have been overwhelmingly negative.<ref>{{Cite web |last=@hho |date=15 Jan 2025 |title=Bambu Studio 1.10.2 Public Beta |url=https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/4 |url-status=live |archive-url=https://ghostarchive.org/archive/ahrz6 |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Improvements Introduce authorization and authentication protection mechanism: Bambu Studio now supports signing and encrypting control commands sent to printers when the printer supports authorization and authentication protection. The printer will determine whether the commands can be executed. Hmmm. This reads suspiciously vague. It could mean that Bambu printers get an onboard permission handling, so that you can “lock down” your printer and set what commands can be run. But it could also mean that Bambu printers in (or of?) the future will only run Gcode encrypted and signed by Bambu Studio…}}</ref><ref>{{Cite web |last=@iranintoavan |title=Firmware Update Introducing New Authorization Control System |url=https://old.reddit.com/r/BambuLab/comments/1i2psvz/firmware_update_introducing_new_authorization/ |url-status=live |archive-url=http://web.archive.org/web/20250403012526/https://old.reddit.com/r/BambuLab/comments/1i2psvz/firmware_update_introducing_new_authorization/ |archive-date=3 Apr 2025 |access-date=1 May 2025 |website=Old [[Reddit]]}}</ref> Bambu Lab has historically pushed cloud-based printer interaction while offering limited LAN mode functionality<ref name=":4" />. Many customers argue that the security issues this locked-down firmware claims to address are actually consequences of the company's cloud-based design choices rather than inherent risks of local network control,<ref name="bambulab-forum-134549/12" /> which continues to infuriate users who are now told that security is the justification for a loss of freedom. As a result of the announcement of the shift, customer ratings on sites like Trustpilot rapidly dropped,<ref>{{Cite web |title=Bambu Lab |url=https://www.trustpilot.com/review/bambulab.com?sort=recency |archive-url=https://web.archive.org/web/20250119162028/https://www.trustpilot.com/review/bambulab.com?sort=recency |archive-date=2025-01-19 |website=[[Trustpilot]]}}</ref> with many reviews citing the restrictions as the reason for the bad reviews.

The shift raises privacy concerns as the restricted LAN mode functionality will now push more users into Bambu's cloud infrastructure for processing user print data, including file names and print settings.

Many community members and customers ask whether the significant costs of maintaining and deploying this cloud infrastructure might lead to future monetization of these now-mandatory services,<ref name="bambulab-forum-3643/5" /> with subscriptions required for features that once worked with local access.

So far, '''no changes have been made or indicated for those not using the cloud service'''. Past firmware updates made it possible to avoid using the cloud service completely by allowing pairing the slicer via IP address and access key and doing offline firmware updates without having to sign the printer into the service, not even temporarily, keeping local functionality unchanged.

==Comparisons to similar practices by other companies==

Bambu Lab's new authorization and authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as [[HP]] or [[Epson]], who have also faced backlash around their handling of [[digital rights management]] (DRM){{Citation needed}}. These comparisons address:
*'''Forced updates''': Firmware updates have rendered third-party ink cartridges incompatible, forcing users to purchase proprietary consumables.
*'''Restricted features''': Scanner/printer combos that will not scan if the ink is empty.
*'''Consumer backlash''': Users criticized these updates as anti-consumer, with some pursuing [[class action lawsuit|class-action lawsuits]] for deceptive practices.<ref name=":5" />

Like 2D printers, Bambu Lab's update restricts functionality previously available to users and pushes them toward proprietary software and cloud-based control.

A parallel specific to the 3D-printing industry can also be drawn from the now-defunct 3D-printer manufacturer [[MakerBot]], whose shift from open-source, DIY-focused machines in 2012 to closed-source, proprietary machines (similarly to Bambu Labs), ultimately drove customers to less-expensive, open-source competitors.<ref>{{Cite web |last=Benchoff |first=Brian |date=28 Apr 2016 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=8 Dec 2025 |access-date=1 May 2025 |website=[[Hackaday]]}}</ref> MakerBot was also accused of asserting ownership over publicly available, open-source designs uploaded to its 3D print repository, Thingiverse.<ref>{{Cite web |last=Biggs |first=John |date=28 May 2014 |title=MakerBot Responds To Critics Who Claim It Is Stealing Community IP |url=https://techcrunch.com/2014/05/28/makerbot-responds-to-critics-who-claim-it-is-stealing-community-ip/ |url-status=live |archive-url=http://web.archive.org/web/20251111041317/https://techcrunch.com/2014/05/28/makerbot-responds-to-critics-who-claim-it-is-stealing-community-ip/ |archive-date=11 Nov 2025 |access-date=1 May 2025 |website=[[TechCrunch]]}}</ref> These factors contributed to MakerBot steadily losing their position and reputation as an industry leader, before getting absorbed by rival Ultimaker in 2022.
==TOS restricting development of third party devices and accessories==

It is understood that the following section has been part of the Bambu Lab TOS at least since January 2024,<ref>{{Cite web |last=@X1Plus |title=X1plus community Bambu Lab firmware - A win for everyone? |url=https://www.reddit.com/r/3Dprinting/comments/18zaay0/x1plus_community_bambu_lab_firmware_a_win_for/kggqg4n/ |url-status=live |archive-url=https://web.archive.org/web/20260222212657/https://old.reddit.com/r/3Dprinting/comments/18zaay0/x1plus_community_bambu_lab_firmware_a_win_for/kggqg4n/ |archive-date=22 Feb 2026 |access-date=1 May 2025 |website=[[Reddit]]}}</ref> with some users suggesting that the purpose is to restrict development, while others argue that this is a standard clause used by companies around the world<ref>{{Cite web |last=@mflexx |title=Not updated. And this part is shared by pretty much every company that has ever existed on this planet. That's just blatant karma farming at this point. |url=https://www.reddit.com/r/BambuLab/comments/1ibhhg7/updated_tos_shots_fired/m9i78kj/ |url-status=live |archive-url=https://web.archive.org/web/20260222212738/https://old.reddit.com/r/BambuLab/comments/1ibhhg7/updated_tos_shots_fired/m9i78kj/ |archive-date=22 Feb 2026 |access-date=1 May 2025 |website=[[Reddit]]}}</ref>.

“ 3.1 You may not use Bambu Lab technology or Bambu Lab intellectual property to develop software or design, develop, manufacture, sell, or license third-party devices/accessories associated with Bambu Lab Product without Bambu Lab's prior consent.”<ref name=":2" />

==See also==

*[[Forced account]]

==References==
{{reflist}}

[[Category:Bambu Lab]]
[[Category:Feature Ransom]]
[[Category:3D printers]]

Anthropic

2026-04-27T20:44:35Z

Louis: Update incident link to reflect renamed article

{{StubNotice}}{{CompanyCargo
|Founded = 2021
|Industry = Artificial Intelligence
|Description = American AI startup founded in 2021 commonly known for their family of LLMs named Claude.
|Website = https://anthropic.com
|Logo = Anthropic logo.png
|Type=Private
}}

'''{{wplink|Anthropic|Anthropic PBC}}''' is a private for-profit American [[artificial intelligence]] (AI) startup founded in 2021. Anthropic is mainly known for their family of large language models (LLMs) known as [[Claude]].

==Consumer impact summary==
{{Ph-C-CIS}}

==Incidents==
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].

===Claude Code HERMES.md billing flaw (2026)===
{{Main|Anthropic Claude Code HERMES.md billing flaw}}
In April 2026, a technical flaw in Claude Code triggered by the string "HERMES.md" in git commit messages bypassed subscription plans, routing users to pay-as-you-go API rates and charging one account over $200. Anthropic refused to issue a refund, categorizing the overcharge as an un-refundable technical error.


===Price crackdown against third-party tool usage (2026)===
During April 3rd, 2026, Boris Cherny, head of Claude Code, posted on [[X Corp|Twitter]] (now X) announcing Claude subscriptions will "no longer support third-party tools", such as OpenClaw because it puts an "outsized strain" on Anthropic's systems. The changes took effect on April 4th, and now to use third-party tools the user must pay a separate fee from subscription or use a separate [[Claude]] API key through Anthropic's developer platform. It is rumored this action was done to prevent Claude users from using tools from competitors, as OpenClaw is supported by [[OpenAI]]. <ref>[https://nitter.catsarch.com/bcherny/status/2040206441756471399 https://x.com/bcherny/status/2040206441756471399] - [https://web.archive.org/web/20260405235237/https://nitter.catsarch.com/bcherny/status/2040206441756471399 Archived]</ref><ref>{{Cite web |last=Lee |first=Lloyd |date=3 Apr 2026 |title=Anthropic says Claude subscriptions will no longer support OpenClaw because it puts an 'outsized strain' on systems |url=https://www.businessinsider.com/anthropic-cuts-off-openclaw-support-claude-subscriptions-2026-4 |url-status=live |archive-url=https://web.archive.org/web/20260404024034/https://www.businessinsider.com/anthropic-cuts-off-openclaw-support-claude-subscriptions-2026-4 |archive-date=2026-04-04 |access-date=5 Apr 2026 |website=Business Insider}}</ref><ref>{{Cite web |last=Ha |first=Anthony |date=4 Apr 2026|title=Anthropic says Claude Code subscribers will need to pay extra for OpenClaw usage |url=https://techcrunch.com/2026/04/04/anthropic-says-claude-code-subscribers-will-need-to-pay-extra-for-openclaw-support/ |url-status=live |archive-url=https://web.archive.org/web/20260404163645/https://techcrunch.com/2026/04/04/anthropic-says-claude-code-subscribers-will-need-to-pay-extra-for-openclaw-support/ |archive-date=2026-04-04 |access-date=5 Apr 2026 |website=TechCrunch}}</ref>

==Products==
*[[Claude]]
*Claude Code
*Cowork

==See also==
*[[OpenAI]]
*[[CursorAI "unlimited" plan rug pull]]
*[[ChatGPT]]

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]

Anthropic Claude Code telemetry

2026-04-27T20:44:34Z

Louis: Convert to redirect to correct article

#REDIRECT [[Anthropic Claude Code HERMES.md billing flaw]]

Anthropic Claude Code HERMES.md billing flaw

2026-04-27T20:44:31Z

Louis: Publish renamed article focused exclusively on HERMES.md billing flaw

{{IncidentCargo
|Company=Anthropic
|Product=Claude Code
|Date=2026-04-25
|Description=A flaw in Claude Code triggered by the string "HERMES.md" in git commit messages bypassed subscriptions and charged direct API fees.
}}
'''Anthropic Claude Code HERMES.md billing flaw''' was a technical defect in Anthropic's Claude Code product that bypassed flat-rate subscription plans to charge users direct API fees. In April 2026, a flaw triggered by the exact string "HERMES.md" in a user's git commit history routed subscribers directly to pay-as-you-go billing, charging one account over $200.<ref name="github_hermes">{{Cite web |url=https://github.com/anthropics/claude-code/issues/53262 |title=HERMES.md in git commit messages causes requests to route to extra usage billing instead of plan quota #53262 |author=sasha-id |website=GitHub |date=2026-04-25 |access-date=2026-04-26}}</ref>

== HERMES.md billing switch ==
On April 25, 2026, a user reported that the exact string "HERMES.md" in their local git commit history caused Claude Code to route queries outside of their fixed-rate subscription plan.<ref name="github_hermes" /> The system bypassed the $200 per month Max plan and charged the user direct, pay-as-you-go API rates.<ref name="github_hermes" /> The user lost over $200 in extra charges while 86 percent of their prepaid plan capacity remained available.<ref name="github_hermes" />

=== Anthropic's response ===
When the affected user contacted Anthropic support, the company refused to issue a refund for the $200 lost to the glitch, categorizing the overcharge as an un-refundable technical error.<ref name="reddit_psa">{{Cite web |url=https://www.reddit.com/r/ClaudeAI/comments/1svdm1w/psa_the_string_hermesmd_in_your_git_commit/ |title=PSA: The string 'HERMES.md' in your git commit history silently... |website=Reddit |date=2026-04-26 |access-date=2026-04-26}}</ref>

== References ==
{{reflist}}

[[Category:Anthropic]]
[[Category:Incident]]

Anthropic

2026-04-27T20:34:28Z

Louis: Added Claude Code telemetry incident summary

{{StubNotice}}{{CompanyCargo
|Founded = 2021
|Industry = Artificial Intelligence
|Description = American AI startup founded in 2021 commonly known for their family of LLMs named Claude.
|Website = https://anthropic.com
|Logo = Anthropic logo.png
|Type=Private
}}

'''{{wplink|Anthropic|Anthropic PBC}}''' is a private for-profit American [[artificial intelligence]] (AI) startup founded in 2021. Anthropic is mainly known for their family of large language models (LLMs) known as [[Claude]].

==Consumer impact summary==
{{Ph-C-CIS}}

==Incidents==
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].

===Claude Code telemetry and billing flaw (2026)===
{{Main|Anthropic Claude Code telemetry}}
In April 2026, a technical flaw in Claude Code triggered by the string "HERMES.md" in git commit messages bypassed subscription plans, routing users to pay-as-you-go API rates and charging one account over $200. Anthropic refused to issue a refund, categorizing the overcharge as an un-refundable technical error.


===Price crackdown against third-party tool usage (2026)===
During April 3rd, 2026, Boris Cherny, head of Claude Code, posted on [[X Corp|Twitter]] (now X) announcing Claude subscriptions will "no longer support third-party tools", such as OpenClaw because it puts an "outsized strain" on Anthropic's systems. The changes took effect on April 4th, and now to use third-party tools the user must pay a separate fee from subscription or use a separate [[Claude]] API key through Anthropic's developer platform. It is rumored this action was done to prevent Claude users from using tools from competitors, as OpenClaw is supported by [[OpenAI]]. <ref>[https://nitter.catsarch.com/bcherny/status/2040206441756471399 https://x.com/bcherny/status/2040206441756471399] - [https://web.archive.org/web/20260405235237/https://nitter.catsarch.com/bcherny/status/2040206441756471399 Archived]</ref><ref>{{Cite web |last=Lee |first=Lloyd |date=3 Apr 2026 |title=Anthropic says Claude subscriptions will no longer support OpenClaw because it puts an 'outsized strain' on systems |url=https://www.businessinsider.com/anthropic-cuts-off-openclaw-support-claude-subscriptions-2026-4 |url-status=live |archive-url=https://web.archive.org/web/20260404024034/https://www.businessinsider.com/anthropic-cuts-off-openclaw-support-claude-subscriptions-2026-4 |archive-date=2026-04-04 |access-date=5 Apr 2026 |website=Business Insider}}</ref><ref>{{Cite web |last=Ha |first=Anthony |date=4 Apr 2026|title=Anthropic says Claude Code subscribers will need to pay extra for OpenClaw usage |url=https://techcrunch.com/2026/04/04/anthropic-says-claude-code-subscribers-will-need-to-pay-extra-for-openclaw-support/ |url-status=live |archive-url=https://web.archive.org/web/20260404163645/https://techcrunch.com/2026/04/04/anthropic-says-claude-code-subscribers-will-need-to-pay-extra-for-openclaw-support/ |archive-date=2026-04-04 |access-date=5 Apr 2026 |website=TechCrunch}}</ref>

==Products==
*[[Claude]]
*Claude Code
*Cowork

==See also==
*[[OpenAI]]
*[[CursorAI "unlimited" plan rug pull]]
*[[ChatGPT]]

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]

Anthropic Claude Code telemetry

2026-04-27T20:34:26Z

Louis: Created new incident article for Anthropic Claude Code telemetry covering HERMES.md billing flaw and source code leak

{{IncidentCargo
|Company=Anthropic
|Product=Claude Code
|Date=2026-04-25
|Description=Anthropic's Claude Code triggered a flaw that bypassed subscriptions to charge direct API fees based on git commit history.
}}
'''Anthropic Claude Code telemetry''' triggered a flaw that bypassed flat-rate subscription plans to charge users direct API fees. In April 2026, a technical flaw triggered by the exact string "HERMES.md" in git commit messages routed subscribers directly to pay-as-you-go billing, charging one account over $200.<ref name="github_hermes">{{Cite web |url=https://github.com/anthropics/claude-code/issues/53262 |title=HERMES.md in git commit messages causes requests to route to extra usage billing instead of plan quota #53262 |author=sasha-id |website=GitHub |date=2026-04-25 |access-date=2026-04-26}}</ref>

== HERMES.md billing switch ==
On April 25, 2026, a user reported that the exact string "HERMES.md" in their local git commit history caused Claude Code to route queries outside of their fixed-rate subscription plan.<ref name="github_hermes" /> The system bypassed the $200 per month Max plan and charged the user direct, pay-as-you-go API rates.<ref name="github_hermes" /> The user lost over $200 in extra charges while 86 percent of their prepaid plan capacity remained available.<ref name="github_hermes" />

=== Anthropic's response ===
When the affected user contacted Anthropic support, the company refused to issue a refund for the $200 lost to the glitch, categorizing the overcharge as an un-refundable technical error.<ref name="reddit_psa">{{Cite web |url=https://www.reddit.com/r/ClaudeAI/comments/1svdm1w/psa_the_string_hermesmd_in_your_git_commit/ |title=PSA: The string 'HERMES.md' in your git commit history silently... |website=Reddit |date=2026-04-26 |access-date=2026-04-26}}</ref>

== Source code leak & malware ==
On March 31, 2026, Anthropic exposed 512,000 lines of proprietary TypeScript source code for Claude Code.<ref name="9to5">{{Cite web |url=https://9to5google.com/2026/04/01/claude-source-code-leak/ |title=Claude's source code leak was an internal error, not an attack |author=Andrew Romero |website=9to5Google |date=2026-04-01 |access-date=2026-04-26}}</ref> The leak occurred because a JavaScript source map was bundled into an npm package update.<ref name="9to5" /> Hackers subsequently distributed fake versions of Claude Code containing Vidar and GhostSocks malware to developers.<ref name="pcmag_malware">{{Cite web |url=https://www.pcmag.com/news/hackers-are-using-claude-code-leak-as-bait-to-spread-malware |title=Hackers Are Using Claude Code Leak As Bait to Spread Malware |author=Michael Kan |website=PCMag |date=2026-04-03 |access-date=2026-04-26}}</ref>

== Supply chain risk designation ==
On March 2, 2026, United States Secretary of Defense Pete Hegseth designated Anthropic a "Supply-Chain Risk to National Security."<ref name="justsec">{{Cite web |url=https://www.justsecurity.org/anthropic-supply-chain-risk |title=What Hegseth’s “Supply Chain Risk” Designation of Anthropic Does and Doesn’t Mean |author=Tess Bridgeman |website=Just Security |date=2026-03-02 |access-date=2026-04-26}}</ref>

== See also ==
* [[Digital Millennium Copyright Act]]
* [[Data collection and privacy]]
* [[Right to repair]]

== References ==
{{reflist}}

[[Category:Anthropic]]
[[Category:Incident]]
[[Category:Data collection and privacy]]
[[Category:Copyright issues]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2026-04-25T16:04:05Z

Louis: rewrote flock-surveillance faq with primary-source citations for carpenter/jones/knotts/mccarthy, schmidt v norfolk numbers, va hb2724 + vscc figures, cleveland ord 1367-2025, moreno valley/cabrera, aurora co/$1.9m, columbine valley/elser, sb26-070, cherry hills village/dausman, peppermill/killinger, baltimore county omnilert, doritos/kenwood; fixed soicher byline (was sallinger), 526/849 norfolk numbers, austin 10-month window, "upsetting" quote, deleted youtube bodycam subsection and fabric...

This page collects common objections raised against automated license plate reader (ALPR) and AI surveillance camera deployments, and the documented legal and factual responses to them.

==The "no expectation of privacy in public" argument==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.|thumb|Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[wikipedia:Fourth_Amendment_to_the_United_States_Constitution|Fourth Amendment]] jurisprudence and misunderstands the legal standard of "reasonable expectation of privacy" established by the [[wikipedia:Supreme_Court_of_the_United_States|Supreme Court of the United States]].

===The "reasonable" standard in Fourth Amendment law===

The Fourth Amendment protects against "unreasonable searches and seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy." This considers the nature, scope, and how intrusive the government monitoring is.

In [[wikipedia:Carpenter_v._United_States|''Carpenter v. United States'' ''(2018)'']], the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[wikipedia:John_Roberts|John Roberts]] wrote that the government's access to 127 days of cell-site location data, tracking movements on public roads, achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=Carpenter v. United States |url=https://www.law.cornell.edu/supremecourt/text/16-402 |archive-url=https://web.archive.org/web/20180623061246/https://www.law.cornell.edu/supremecourt/text/16-402 |archive-date=2018-06-23 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> The Court said,<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction between isolated observation and citywide surveillance systems===

Courts separate isolated instances of police observation and large-scale automated tracking systems. In ''[[wikipedia:United_States_v._Jones_(2012)|United States v. Jones (2012)]]'', Justice [[wikipedia:Sonia_Sotomayor|Sonia Sotomayor's]] influential concurrence explained that [[GPS tracking]]:<blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, and sexual associations."''<ref name=":1">{{Cite web |title=United States v. Jones |url=https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-url=https://web.archive.org/web/20120126022816/https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-date=2012-01-26 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref></blockquote>She noted that automated surveillance:<blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources and community hostility."<ref name=":1" />''</blockquote>The [[wikipedia:Massachusetts_Supreme_Judicial_Court|Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy (2020)'', holding:<blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy and would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |date=2020-04-16 |title=Commonwealth v. McCarthy |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-url=https://web.archive.org/web/20220303203404/https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-date=2022-03-03 |access-date=2025-12-16 |website=Justia}}</ref></blockquote>The court distinguished limited camera deployment from citywide networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic theory===

The [[wikipedia:Mosaic_theory_of_the_Fourth_Amendment|"mosaic theory" of Fourth Amendment protection]] holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[wikipedia:Samuel_Alito|Samuel Alito]] noted in his ''Jones'' concurrence that:<blockquote>''"society's expectation has been that law enforcement agents and others would not; and indeed, in the main, simply could not; secretly monitor and catalogue every single movement of an individual's car for a very long period."<ref name=":1" />''</blockquote>

In [[wikipedia:United_States_v._Knotts|''United States v. Knotts (1983)'']], while holding that limited beeper (a radio-emitting surveillance device) tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "[[wikipedia:Dragnet_(policing)|dragnet-type law enforcement practices]]."<ref>{{Cite web |title=United States v. Knotts |url=https://www.law.cornell.edu/supremecourt/text/460/276 |url-status=live |archive-url=https://web.archive.org/web/20120601022257/https://www.law.cornell.edu/supremecourt/text/460/276 |archive-date=2012-06-01 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref>

===Litigation on citywide ALPR networks===

In ''Schmidt v. City of Norfolk (E.D. Va.)'', privacy advocates Lee Schmidt and Crystal Arrington challenged Norfolk's 176-camera Flock Safety ALPR network as unconstitutional. Chief Judge [[wikipedia:Mark_Steven_Davis|Mark S. Davis]] initially denied a motion to dismiss the case in February 2025, finding that plaintiffs had stated a plausible Fourth Amendment claim. During discovery, it emerged that Schmidt's location was logged 526 times and Arrington's was logged 849 times between February and July 2025.<ref name="nbc-norfolk">{{cite news |last=Collier |first=Kevin |date=2025-09-18 |title=Police cameras tracked one driver 526 times in four months, lawsuit says |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |url-status=live |archive-url=https://web.archive.org/web/20250918093450/https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |archive-date=2025-09-18 |access-date=2025-12-16 |work=NBC News}}</ref>

However, on January 27, 2026, Judge Davis granted summary judgment in favor of the City, ruling that Norfolk's ALPR system did not violate the Fourth Amendment. In a 51-page opinion, Davis concluded that the plaintiffs could not demonstrate that the system was capable of tracking the entirety of a person's movements. The court found that although the cameras captured snapshots of daily life, they did not continuously track individuals or capture sufficient data to reconstruct whole routines, noting "sizable gaps" between photographs.<ref name="whro-norfolk">{{cite news |last=Cox |first=Toby |date=2026-02-11 |title=A federal judge ruled Norfolk's Flock surveillance cameras don't invade people's privacy – yet |url=https://www.whro.org/business-growth/2026-02-11/a-federal-judge-ruled-norfolks-flock-surveillance-cameras-dont-invade-peoples-privacy-yet |access-date=2026-03-02 |work=WHRO}}</ref><ref name="courthouse-norfolk">{{cite news |date=2026-01-28 |title=Judge holds Norfolk's license plate reader use constitutional |url=https://courthousenews.com/judge-holds-norfolks-license-plate-reader-use-constitutional/ |access-date=2026-03-02 |work=Courthouse News Service}}</ref>

Notably, Judge Davis cautioned that the constitutional analysis could change as ALPR technology expands. He wrote that ''"ALPR surveillance could become too intrusive and run afoul of [constitutional privacy standards] at some point,"'' but concluded that ''"at least in Norfolk, Virginia, the answer is: not today."''<ref name="whro-norfolk" /> The plaintiffs, represented by the Institute for Justice, announced their intention to appeal, with Schmidt stating he remained committed to fighting against what he described as "dragnet warrantless surveillance."<ref name="whro-norfolk" /><ref name="courthouse-norfolk" />

Flock Safety's chief legal officer responded that the decision aligned with rulings by over 30 state and federal courts concluding that fixed-location ALPRs do not constitute a search under the Fourth Amendment.<ref name="courthouse-norfolk" />

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 and 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |last=Maass |first=Dave |last2=Lipton |first2=Beryl |date=2021-04-22 |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-url=https://web.archive.org/web/20181115183012/https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-date=2018-11-15 |access-date=2025-12-16 |website=Electronic Frontier Foundation}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale and the reasonableness analysis===

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly;<ref>{{cite news |last=Kenney |first=Andrew |date=2024-09-19 |title=2 million license plates scanned monthly by Denver's new police cameras |url=https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-url=https://web.archive.org/web/20240919214639/https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-date=2024-09-19 |access-date=2025-12-16 |work=Denverite}}</ref> Norfolk's 176 cameras provide citywide coverage;<ref name="nbc-norfolk" /> and Austin's system scanned approximately 75 million plates from March through December 2024.<ref>{{cite news |last=Thompson |first=Ben |date=2025-05-20 |title=75M license plates scanned under rebooted Austin police program; audit reveals successes, concerns |url=https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |url-status=live |archive-url=https://web.archive.org/web/20250607131518/https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |archive-date=2025-06-07 |access-date=2025-12-16 |work=Community Impact}}</ref>

==State legislative responses: Virginia==

Virginia became one of the first states to enact statewide ALPR regulation when legislation establishing statewide standards for law enforcement use of ALPR took effect on July 1, 2025. Before this date, Virginia had no statewide statutory or regulatory framework governing law enforcement use of ALPR, meaning agencies could operate the technology without any statewide limitations on use, data retention, or data sharing.<ref name="vscc-2026">{{cite web |title=Law Enforcement Use of Automatic License Plate Recognition (ALPR) Update, January 2026 |url=https://vscc.virginia.gov/2026/VSCC%20ALPR%20Report%20January%202026%20FINAL%20REVISED%20Jan%2021%202026.pdf |access-date=2026-03-02 |publisher=Virginia State Crime Commission |date=2026-01}}</ref>

===Overview of Virginia's 2025 ALPR law===

Under the new statute (Virginia House Bill 2724, codified at Va. Code Ann. § 2.2-5517), law enforcement agencies in Virginia may only use ALPR for criminal investigations, active investigations into missing or endangered persons or human trafficking, and notifications related to missing or endangered persons, outstanding warrants, human trafficking, stolen vehicles, or stolen license plates.<ref name="vscc-2026" />

The law requires ALPR data to be purged after 21 days unless needed for an ongoing investigation, prosecution, or civil action. It also restricts data sharing to other Virginia law enforcement agencies, Commonwealth's Attorneys, criminal defendants or their counsel, ALPR vendors, or pursuant to a court order. The statute does not permit data sharing with out-of-state or federal law enforcement agencies.<ref name="vscc-2026" />

===Compliance findings from the Virginia State Crime Commission===

In January 2026, the Virginia State Crime Commission published the findings of a statewide survey of all 361 Virginia law enforcement agencies on their use of ALPR. The survey, conducted in November 2025 to capture practices after the new legislation took effect, received responses from 251 agencies (70%). Of responding agencies, 63% (159 of 251) reported using ALPR. A large majority, 86% (137 of 159), reported [[Flock Safety]] as their ALPR vendor.<ref name="vscc-2026" />

The Crime Commission found that some agencies were not complying with the new statutory requirements:

*'''Data retention violations''': 21% (33 of 159) of agencies using ALPR reported retaining data beyond the statutory 21-day limit. Reported retention periods for fixed cameras ranged from 22 to 60 days; for mobile cameras, 30 to 180 days.<ref name="vscc-2026" />

*'''Unauthorized data sharing with federal and out-of-state agencies''': Despite the statute prohibiting such sharing, 13% (20 of 159) of agencies reported providing continuous access to out-of-state law enforcement agencies, and 6% (9 of 159) reported providing continuous access to federal law enforcement agencies.<ref name="vscc-2026" />

*'''No written ALPR policy''': 16% (26 of 159) of agencies using ALPR reported having no policy on ALPR use, despite the statutory requirement to maintain one. An additional 9% (14 of 159) reported being in the process of implementing a policy.<ref name="vscc-2026" />

*'''No public awareness measures''': 35% (55 of 159) of agencies reported taking no public awareness measures regarding their ALPR use, despite statutory requirements to promote public awareness.<ref name="vscc-2026" />

*'''Non-response''': Almost one-third of law enforcement agencies (110 of 361) did not respond to the survey at all, meaning their ALPR use and compliance status remain unknown.<ref name="vscc-2026" />

The Crime Commission's report stated that the Chair, Delegate Charniele Herring, planned to send letters to agencies whose survey responses indicated non-compliance with the new law, as well as to non-responding agencies.<ref name="vscc-2026" />

===Data sharing concerns===

Virginia's experience reflects a national pattern of concerns over ALPR data sharing. A September 2025 investigation by the Virginia Center for Investigative Journalism found that before the new law took effect, federal agencies had attempted to access local Virginia ALPR data thousands of times for immigration enforcement purposes, and one small town's Flock network data had been searched nearly 7 million times by outside agencies in a single year.<ref name="vcij-sept2025">{{cite news |last=Falayi |first=K. |date=2025-09-16 |title=One sleepy Virginia town. Nearly 7 million hits on its surveillance network |url=https://vcij.org/stories/state-of-surveillance |access-date=2026-03-02 |work=Virginia Center for Investigative Journalism}}</ref> At least two Virginia localities, Charlottesville and Staunton, subsequently ended their use of Flock Safety cameras, citing concerns about federal data sharing.<ref name="vscc-2026" />

As of early 2026, at least 30 localities across the United States have either deactivated Flock cameras or canceled their contracts, driven in part by concerns over privacy and federal agency access to locally collected ALPR data.<ref name="npr-flock">{{cite news |date=2026-02-19 |title=Why some cities are canceling Flock license plate reader contracts |url=https://www.npr.org/2026/02/17/nx-s1-5612825/flock-contracts-canceled-immigration-survillance-concerns |access-date=2026-03-02 |work=NPR}}</ref>

==Revolving door: surveillance vendor hiring of public officials==

Multiple documented cases have raised concerns about [[Flock Safety]]'s practice of hiring current or recently departed public officials who hold or held influence over the procurement of the company's products.

===Cleveland, Ohio: former council majority leader joins Flock===

Kerry McCormack, the Ward 3 council member and Majority Leader of the Cleveland City Council, announced his resignation on September 11, 2025. He left office in early October 2025. He joined Flock Safety immediately afterward as public affairs lead for the eastern United States. No reporting has identified a gap between his departure from office and his start date at Flock.<ref name="ideastream-mccormack">[https://www.ideastream.org/government-politics/2025-09-11/cleveland-councilmember-kerry-mccormack-resigns-before-end-of-term Ideastream: Cleveland Councilmember Kerry McCormack resigns before end of term]</ref><ref name="wkyc-mccormack">[https://www.wkyc.com/article/news/local/cleveland/cleveland-city-councilman-kerry-mccormack-resign-ward-3-seat-october-majority-leader-flock-safety-lauren-welch/95-6380bc59-b942-4c43-a0fc-b1a61f8f8fea WKYC: Kerry McCormack to resign from Cleveland City Council on Oct. 3]</ref>

In late October 2025, the Bibb administration introduced Ordinance 1367-2025 to Cleveland City Council: a three-year, approximately $2 million sole-source emergency contract with Flock Group, Inc. No Request for Proposals was issued and no competing bids were solicited.<ref name="legistar-flock">[https://cityofcleveland.legistar.com/LegislationDetail.aspx?ID=7714153&GUID=D5D4E9A9-CED2-4198-9998-FCD9349ED5A4&Options=ID%7CText%7CAttachments%7COther%7C&Search=flock Cleveland City Council Legistar: File #1367-2025]</ref>

The administration justified the sole-source designation on two grounds: that Flock was the only vendor offering the specific integrated bundle of services, and that the contract piggybacked on a pre-negotiated Ohio state term purchasing agreement. At the November 14, 2025 Safety Committee hearing, ShotSpotter representatives attended and stated on the record that they offer competing products capable of fulfilling the same requirements, directly contradicting the sole-source rationale.<ref name="axios-flock">[https://www.axios.com/local/cleveland/2025/11/14/cleveland-shotspotter-flock Axios Cleveland: Cleveland mulls shift from ShotSpotter to Flock for gunshot detection]</ref><ref name="signal-shotspotter">[https://signalcleveland.org/cleveland-city-council-shotspotter-study-hearing/ Signal Cleveland: City Council debates: Is ShotSpotter making Cleveland safer?]</ref>

====How the emergency and bidding bypass works====

Cleveland Charter § 36 defines an emergency measure as an ordinance or resolution for the "immediate preservation of the public peace, property, health, or safety" or for the "usual daily operation of a Municipal department." Combined with the § 33 rule suspension mechanism, an emergency designation bypasses the normal three-reading requirement and the 30-day waiting period before a measure takes effect. Emergency passage requires a two-thirds supermajority of all elected council members.<ref name="charter-36">[https://codelibrary.amlegal.com/codes/cleveland/latest/cleveland_oh/0-0-0-252 Cleveland Charter § 36: Emergency Measures]</ref>

Charter § 108 requires competitive bidding for contracts exceeding $50,000, with an exception for cooperative purchasing arrangements with other governmental agencies. Professional services contracts are exempt from sealed bidding but are still expected to go through a Request for Proposals process per the Division of Purchases and Supplies. The Bibb administration issued neither a formal bid nor an RFP for the Flock expansion.<ref name="charter-108">[https://codelibrary.amlegal.com/codes/cleveland/latest/cleveland_oh/0-0-0-627 Cleveland Charter § 108: Authorization of Contracts]</ref><ref name="cle-purchases">[https://www.clevelandohio.gov/city-hall/departments/finance/divisions/purchases-supplies City of Cleveland: Division of Purchases & Supplies]</ref>

====Ohio revolving door law and its limitations====

Ohio Revised Code § 102.03(A)(1) bars former public officials for twelve months from representing any person or entity before any public agency on any "matter" in which the official personally participated during their public service.<ref name="orc-102">[https://codes.ohio.gov/ohio-revised-code/section-102.03 Ohio Revised Code § 102.03]</ref>

However, R.C. 102.03(A)(5) explicitly excludes "legislative matters" (defined as the proposal, consideration, or enactment of statutes, rules, ordinances, resolutions, or charter or constitutional amendments) from the definition of "matter." Because Ordinance 1367-2025 is a piece of legislation requiring formal consideration by City Council, the twelve-month ban arguably does not apply to a former council member lobbying for its passage.<ref name="orc-102" />

Cleveland has no local revolving-door ordinance, no lobbying registration requirement, and no cooling-off period of its own. Chapter 171 of the Cleveland Codified Ordinances covers employment provisions such as hours of work and overtime, not ethics or lobbying. By comparison, Chicago imposes a blanket one-year ban on former aldermen lobbying any city official on any topic.<ref name="cle-171">[https://codelibrary.amlegal.com/codes/cleveland/latest/cleveland_oh/0-0-0-4565 Cleveland Codified Ordinances Chapter 171: Employment Provisions]</ref>

McCormack told Signal Cleveland that he "did not seek an opinion from the Ohio Ethics Commission" and was voluntarily observing the one-year rule as a best practice. However, News 5 Cleveland's investigators obtained McCormack's emails through a public records request and reported that he did contact the Ohio Ethics Commission about restrictions approximately one month before leaving office.<ref name="signal-mccormack">[https://signalcleveland.org/cleveland-city-council-kerry-mccormack-flock-safety-contract/ Signal Cleveland: Kerry McCormack says he had 'no engagement' with city over Flock]</ref><ref name="news5-flock">[https://www.news5cleveland.com/news/local-news/more-questions-raised-about-flock-safety-in-cleveland-data-access-and-whos-watching News 5 Cleveland: More questions raised about Flock Safety in Cleveland]</ref>

McCormack's one-year recusal from Cleveland matters is voluntary and self-enforced. It is not a Flock corporate policy and not a legal requirement under Ohio law given the legislative exemption. McCormack stated: "Whether I have a defined legal conflict or not, regardless, it's best practice I think to sit out."<ref name="signal-mccormack" />

Council member Rebecca Maurer stated at a Safety Committee hearing: "I hope you understand the hesitancy I have given a member of this body just departed to take a job at Flock that we now have a sole source contract without an RFP process."<ref name="news5-flock" />

====Status of the Cleveland contract====

Cleveland's ShotSpotter contract expires in April 2026 and the existing Flock automated license plate reader contract expires in June 2026. The Bibb administration proposed bundling both into a single expanded Flock contract covering cameras, license plate readers, gunshot detection, and audio monitoring, all through one vendor on a sole-source basis.<ref name="fox8-flock">[https://fox8.com/news/cleveland-considers-transition-from-shotspotter-to-flock-council-pushes-back/ Fox 8: Cleveland considers transition from ShotSpotter to Flock, council pushes back]</ref><ref name="signal-replace">[https://signalcleveland.org/cleveland-to-replace-shotspotter-with-flock-safety/ Signal Cleveland: Cleveland to replace ShotSpotter with other gunshot-detection tech]</ref>

Council refused to advance the legislation. Fox 8 reported that council will not move forward until a full review is conducted and a request for proposals has been issued.<ref name="fox8-flock" />

The Bibb administration then asked Safety Committee Chair Michael Polensek to shelve the expansion before year-end 2025. No public explanation was given. Polensek counter-proposed issuing a request for qualification.<ref name="clevescene-flock">[https://www.clevescene.com/news/cleveland-news/cleveland-puts-flock-expansion-on-hold-amid-local-pushback/ Cleveland Scene: Cleveland Puts Flock Expansion on Hold Amid Local Pushback]</ref>

As of March 2026, Ordinance 1367-2025 sits on indefinite hold in the Safety Committee. No vote has been scheduled, no RFP has been issued, and no RFQ has been completed. Approximately 100 Flock license plate reader cameras remain active across Cleveland.<ref name="clevescene-flock" /><ref name="news5-grassroots">[https://www.news5cleveland.com/news/local-news/investigations/grassroots-group-presses-cleveland-to-end-relationship-with-flock-safety-expansion-plans-on-hold News 5 Cleveland: Grassroots group presses Cleveland to end relationship with Flock Safety]</ref>

A grassroots group called Flockno delivered a letter with 275 signatures to City Hall demanding the city cut ties with Flock entirely and remove existing cameras when the June contract expires. News 5 reported the petition had gathered nearly 300 signatures total. Organizer Bryn Adams stated: "We want to ask the city to remove, not renew."<ref name="news5-grassroots" /><ref name="clevescene-flock" />

===Moreno Valley, California: Flock hired a sitting mayor===

In February 2024, Flock Safety hired Ulises Cabrera, the sitting mayor of Moreno Valley, California (population 200,000+), as a Community Engagement Manager. A Flock job posting for the position listed a salary of $100,000–$140,000 plus stock options. The role was intended to guide law enforcement customers through the public procurement process in collaboration with Flock's sales team. Cabrera had previously voted as mayor to fund a citywide Flock camera system in Moreno Valley.<ref name="tc">[https://techcrunch.com/2025/01/08/flock-safety-quietly-hired-a-sitting-california-mayor-now-hes-suing-flock/ TechCrunch: Flock Safety quietly hired a sitting California mayor. Now he's suing Flock.]</ref>

During his time at Flock, Cabrera gave presentations promoting the company's technology at city council meetings in at least two other jurisdictions: Whitewater, Kansas and Mammoth Lakes, California.<ref name="tc" />

====Cabrera v. Flock Safety====

In November 2024, Cabrera filed a wrongful termination lawsuit against Flock Safety.<ref name="cabrera-complaint">[https://embed.documentcloud.org/documents/25482232-flock-lawsuit-complaint/?embed=1 DocumentCloud: Cabrera v. Flock Safety — Complaint]</ref> According to the complaint, approximately two weeks after Cabrera started working at Flock, an employee requested that he use his position as mayor of Moreno Valley to benefit the company. Cabrera alleges he refused, forwarded the request to his legal counsel while copying the Flock employee, and that the employee immediately began exhibiting retaliatory behavior. Flock terminated Cabrera in June 2024. He worked at Flock from February to June 2024.<ref name="tc" />

Cabrera also alleges he raised concerns that Flock was underreporting the number of surveillance cameras installed in Carmel-by-the-Sea. A separate Forbes investigation published in February 2024 found that Flock camera installations broke laws in at least five states, including by installing cameras without proper permits.<ref name="tc" />

Flock categorically denies all of Cabrera's allegations and says its hire of a sitting mayor complied with California conflict-of-interest regulations.<ref name="tc" />

====California conflict-of-interest law====

California Government Code § 1090 prohibits public officers from being financially interested in any contract made by the body or board of which they are members.<ref name="cagov-1090">{{cite web |title=California Government Code § 1090 |url=https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=GOV&sectionNum=1090. |access-date=2026-04-24 |publisher=California Legislative Information}}</ref> A sitting mayor receiving a salary and stock options from a surveillance vendor while his city council approves that vendor's contracts raises direct questions under this provision.<ref name="tc" />

While campaigning for reelection in November 2024, Cabrera's campaign website cited his earlier vote to fund Moreno Valley's Flock system, but did not disclose that he had subsequently worked for Flock while serving as mayor.<ref name="tc" />

===Comparison of Cleveland and Moreno Valley ethics gaps===

Albert Fox Cahn, founder of the Surveillance Technology Oversight Project, stated that the allegations in the Moreno Valley case "add to the growing body of evidence that American surveillance is fueled by a broken revolving door between industry and government."<ref name="tc" />

The Cleveland and Moreno Valley cases illustrate different but related gaps in ethics law. In Ohio, the state revolving-door statute's explicit exclusion of "legislative matters" from the cooling-off period means that a former council member may legally lobby for ordinances benefiting a new employer immediately upon leaving office.<ref name="orc-102" /> In California, the strict liability framework of Government Code § 1090 theoretically prohibits the arrangement but relies on self-disclosure and enforcement by the Fair Political Practices Commission.<ref name="cagov-1090" /> In both cases, municipal-level protections were either absent or insufficient: Cleveland has no local lobbying registration or cooling-off ordinance,<ref name="cle-171" /> while Moreno Valley had no mechanism to prevent a sitting mayor from accepting private employment with a city vendor.<ref name="tc" />

==False positives and system failures==

Automated surveillance systems generate false positives in which innocent individuals are subjected to armed police responses based on system errors.

===Baltimore County gun detection false alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' and I was like, 'What?'"<ref name=":3" />''</blockquote>

Allen was forced to his knees, handcuffed, and searched before officers realized he was unarmed. Allen described watching about eight police cars arrive, with officers pointing guns at him.

<blockquote>''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me."''<ref name=":3" /></blockquote>

When shown the image that triggered the alert, Allen explained:<blockquote>''"I was just holding a Doritos bag – it was two hands and one finger out, and they said it looked like a gun."<ref name=":3" />''</blockquote>

High schools in Baltimore County have used the AI gun detection system since 2023, using existing school cameras to scan for potential weapons. The system is operated by [[Omnilert]], which taps into existing camera feeds to detect objects that resemble weapons and then alerts both school safety officers and law enforcement automatically. A school official acknowledged "how upsetting this was for the individual that was searched as well as the other students who witnessed the incident."<ref name=":3" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name=":3" /> Omnilert defended its system, claiming it ''"functioned as intended: to prioritize safety and awareness through rapid human verification,"'' though the incident demonstrated the system escalated to armed police response before adequate human review occurred.<ref name=":3">{{cite news |last=Tsui |first=Karina |last2=Sottile |first2=Zoe |date=2025-10-25 |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |url=https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |url-status=live |archive-url=https://web.archive.org/web/20251026050806/https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |archive-date=2025-10-26 |access-date=2025-10-28 |work=CNN}}</ref>

===ALPRs causing innocent people to be held at gunpoint===

ALPR systems generate false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving incident====

In 2018, privacy advocate Brian Hofer and his younger brother were driving to visit their parents for Thanksgiving when they were held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1=Lauren |last2=Clark |first2=Alex |date=2025-07-24 |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |url-status=live |archive-url=https://web.archive.org/web/20250724210641/https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |archive-date=2025-07-24 |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government and corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops and ALPR technology abuse, finding that consequences range from erroneous toll charges to armed detentions of innocent people.<ref name="cbs-alpr" />

====Española, New Mexico child detentions====

In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. In one incident, a 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7," according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies.<ref name="cbs-alpr" />

====Aurora, Colorado family detained on hot pavement====

In Aurora, Colorado in 2020, a mother and her family, including her 6-year-old daughter, were pulled over at gunpoint and forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state, a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video and widely condemned, led to a $1.9 million settlement from the city in 2024.<ref name="cbs-alpr" />

====Cherry Hills Village, Colorado: repeat stops from hotlist data entry error====

According to 9News reporter Spencer Soicher, Cherry Hills Village resident Kyle Dausman was pulled over at least twice by the Cherry Hills Village Police Department in early 2026 after a [[Flock Safety]] camera generated a wanted-person alert tied to a Colorado Crime Information Center hotlist entry. Cherry Hills Village Police Chief Jason Lyons attributed the underlying error to a Gilpin County court data-entry mistake, with Colorado license plates using both the letter "O" and the numeral "0".<ref name="9news-dausman">{{cite news |last=Soicher |first=Spencer |date=2026-04-23 |title=He didn't commit a crime, but Flock cam alerts keep getting him pulled over |url=https://www.9news.com/article/news/local/rime-flock-cam-pulled-over/73-e3f65018-32a5-4bb0-a4ac-26fb24dc9a15 |access-date=2026-04-24 |work=9News (KUSA)}}</ref>

During the first stop, Dausman told 9News that officers "zipped out of nowhere and immediately got behind me with the lights flashing," and he described feeling his safety was at risk. He was released at the scene once officers determined he was not the wanted suspect. A few days later the same department stopped him again on the same alert before recognizing him and releasing him. Chief Lyons said the department then suppressed the alert in its local Flock system, but stated that the agency cannot remove the underlying entry from the wider hotlist.<ref name="9news-dausman" /><ref name="9news-dausman-video">{{cite news |date=2026-04-23 |title=Flock cameras keep telling police a Colorado man who doesn't have a warrant has a warrant |url=https://www.9news.com/video/news/local/flock-cameras-keep-telling-police-a-colorado-man-who-doesnt-have-a-warrant-has-a-warrant/73-3f3f3653-e8e2-4fb6-aa28-8a1f24f7f67c |access-date=2026-04-24 |work=9News (KUSA)}}</ref>

====Columbine Valley, Colorado: sergeant refused to examine exculpatory dashcam footage====

On September 27, 2025, Columbine Valley Police Sergeant Jamie Milliman went to the Denver home of Chrisanna Elser to serve a court summons for petty theft, accusing her of stealing a package valued at $25 or less from a porch in neighboring Bow Mar on September 22, 2025. Milliman based the accusation entirely on Bow Mar's [[Flock Safety]] ALPR network, which had logged Elser's green Rivian truck passing through the town between 11:52 a.m. and 12:09 p.m. on the day of the theft.<ref name="cosun-elser">{{cite news |last=Paul |first=Jesse |date=2025-10-28 |title=A suburban police officer used a Flock surveillance camera to accuse a Denver woman of theft. Then she had to prove him wrong. |url=https://coloradosun.com/2025/10/28/flock-camera-police-colorado-columbine-valley/ |access-date=2026-04-24 |work=The Colorado Sun}}</ref>

Bodycam audio captured by The Colorado Sun recorded Milliman refusing to view Elser's Rivian dashboard camera footage, which she offered as proof that her vehicle never stopped in Bow Mar. Milliman told her, "If you are going to deny it to me, I am not going to help you with any courtesy."<ref name="cosun-elser" /><ref name="cbs-elser">{{cite news |date=2025-11-13 |title=Flock cameras lead Colorado police to wrong suspect |url=https://www.cbsnews.com/colorado/news/flock-cameras-lead-colorado-police-wrong-suspect/ |access-date=2026-04-24 |work=CBS News Colorado}}</ref>

Elser then assembled a digital alibi using her Rivian's onboard cameras, the vehicle's GPS log, and surveillance footage from a tailor shop she was visiting at the time of the theft. She located the actual theft video on NextDoor, which showed a different person who never entered a truck. After she submitted the evidence, the summons was voided.<ref name="cosun-elser" /><ref name="cbs-elser" />

On November 11, 2025, Columbine Valley Town Administrator J.D. McCrumb told Denverite that "appropriate disciplinary action will be applied to the officer involved" after the department's review of the encounter. Elser said the department never issued her a formal apology.<ref name="denverite-elser">{{cite news |date=2025-11-11 |title=The cop who wrongfully accused a Denver woman of a package theft faces discipline |url=https://denverite.com/2025/11/11/flock-package-theft-denver-surveillance-discipline/ |access-date=2026-04-24 |work=Denverite}}</ref> Elser later testified before the Colorado General Assembly in support of Senate Bill 26-070, which would require a warrant for police access to historical ALPR data and which advanced from a Senate committee on a 5-2 vote on February 23, 2026.<ref name="9news-sb70">{{cite news |last=Soicher |first=Spencer |date=2026-02-23 |title=Colorado bill requiring warrant to search license plate tracking database advances |url=https://www.9news.com/article/news/local/local-politics/colorado-bill-requiring-warrant-to-search-license-plate-tracking-database-advances/73-1bd4369f-a168-407f-8079-488bb358f9ef |access-date=2026-04-24 |work=9News (KUSA)}}</ref>

===Facial recognition false identification===

====Peppermill Casino facial recognition wrongful arrest====

On September 17, 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada. Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |last=Roarty |first=Adam |date=2025-12-09 |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-url=https://web.archive.org/web/20251210222601/https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-date=2025-12-10 |access-date=2025-12-16 |website=CasinoBeats}}</ref><ref name="casino-org">{{Cite web |last=Conneller |first=Philip |date=2025-11-11 |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |access-date=2025-12-16 |website=Casino.org |url-status=live |archive-url=https://web.archive.org/web/20260216033051/https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |archive-date=2026-02-16}}</ref> Ellis's ban was set to expire on September 26, 2023, nine days after the arrest.<ref name="casinobeats" /> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |last=García |first=Jerome |date=2025-12-11 |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-url=https://web.archive.org/web/20251205215015/https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-date=2025-12-05 |access-date=2026-01-11 |website=Gambling News}}</ref>

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, and his vehicle registration.<ref name="casinobeats" /> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him and called the police.<ref name="casino-org" />

Released police records and driver's license images showed the two men differed in height by four inches and had different eye colors (blue vs. hazel), differences the facial recognition system failed to account for:<ref name="casinobeats" />

{| class="wikitable"
|-
!Characteristic!!Jason Killinger!!Michael Ellis
|-
|Height||Four inches taller than Ellis<ref name="casino-org-deposition" />||
|-
|Eye color||Blue||Hazel
|}

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue and hazel eyes are ''"by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats" /> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats" />

Officer Jager arrived at the casino. According to Killinger's lawsuit, he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up"'' to fabricate the documents.<ref name="casinobeats" /> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' and that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats" />

Bodycam footage released in late 2025 captured Jager stating:<blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |last=Gwilliam |first=Michael |date=2025-12-15 |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-url=https://web.archive.org/web/20251218224228/https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-date=2025-12-18 |access-date=2025-12-16 |website=Dexerto}}</ref></blockquote>

Jager handcuffed Killinger and transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats" />

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |date=2025-11-14 |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-url=https://web.archive.org/web/20260110235640/http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-date=2026-01-10 |access-date=2025-12-16 |website=Our Town Reno}}</ref> His federal lawsuit against Officer Jager, ''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD, remains active in the U.S. District Court for the District of Nevada.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |archive-url=http://web.archive.org/web/20260210093102/https://www.leagle.com/decision/infdco20250925d22 |archive-date=2026-02-10 |access-date=2025-12-16 |website=Leagle}}</ref>

In a January 22, 2026 deposition, Officer Jager acknowledged that the arrest ''"never should have happened"'' and stated that post-lawsuit training had clarified that facial recognition technology cannot serve as the sole basis for probable cause, but should instead be treated as ''"an investigative lead only"'' requiring further corroboration.<ref name="casino-org-deposition">{{Cite web |last=Conneller |first=Philip |date=2026-01-28 |title=Reno Cop Concedes Peppermill Facial Recognition Arrest was Wrongful |url=https://www.casino.org/news/reno-cop-concedes-peppermill-facial-recognition-arrest-wrongful/ |access-date=2026-03-02 |website=Casino.org}}</ref> Following the deposition, Killinger's attorney moved to add the City of Reno as a defendant, arguing that Jager's testimony demonstrated systemic failure to train officers on the limitations of AI facial recognition technology.<ref name="casino-org-deposition" />

The lawsuit alleges that Jager's actions violated Killinger's [[wikipedia:Fourteenth_Amendment_to_the_United_States_Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats" /> Killinger alleges that Jager failed to use the police department's own fingerprint technology in a timely manner and omitted the fingerprint exoneration from his official report.<ref name="casinobeats" /> He is seeking compensatory, special, and punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats" /> Discovery in the case has been extended to July 2026, with motions due by August 2026.<ref name="unicourt-killinger">{{Cite web |title=Killinger vs Jager – Case Details |url=https://unicourt.com/case/pc-db5-casegucf509a42dd1e-2175767 |access-date=2026-03-02 |website=UniCourt}}</ref>

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom" />

===Common ALPR error mechanisms===

These incidents illustrate how ALPR systems generate misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists.
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (such as matching car plates to motorcycle registrations).
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles and criminal activity.
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners.

==Law enforcement misuse and stalking incidents==

Documented cases show that law enforcement officers have misused ALPR systems, including Flock Safety cameras, to track individuals for personal, non-investigative purposes such as stalking romantic partners or civilians. These incidents have raised concerns about lack of internal oversight, auditing practices, and the concentration of surveillance power in individual user accounts.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after prosecutors alleged he used the department's Flock ALPR system to track his ex-girlfriend. According to the criminal complaint, Morales conducted five unauthorized searches of his ex-partner's vehicle in October 2025. Court filings state that Morales acknowledged knowing the searches were improper and attributed them to "desperation and bad judgment." He was placed on administrative leave, barred from accessing Flock systems, and released on a $10,000 cash bond pending further proceedings. A parallel civil filing seeking a temporary restraining order in a domestic abuse case was also lodged against Morales.<ref>{{cite news |last=Kerhin |first=Brian |date=2026-01-09 |title=Menasha police officer accused of using license plate recognition system to track his ex |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-url=https://web.archive.org/web/20260110000858/https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-date=2026-01-10 |access-date=2026-01-11 |work=FOX 11 News}}</ref>

The Menasha case is one in what has become a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar was arrested in October 2022 on charges of stalking and unlawful acts concerning computers after using Flock cameras to monitor his estranged wife's movements over several months.<ref>{{cite news |last=Baker |first=Joe |date=2022-10-31 |title=Kechi police lieutenant arrested for using police technology to stalk wife |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-url=https://web.archive.org/web/20221031042853/https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-date=2022-10-31 |work=KWCH}}</ref> In a separate Kansas case, Sedgwick Police Chief Lee Nygaard admitted in 2024 to using Flock ALPR data 164 times to track his ex-girlfriend and her new partner, leading to his resignation and surrender of his law enforcement certification.<ref>{{cite news |last=Stavola |first=Michael |date=2024-08-17 |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-url=https://web.archive.org/web/20240817105006/https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-date=2024-08-17 |work=Yahoo News}}</ref>

Las Vegas Metropolitan Police officer Christopher Young was arrested in December 2023 for stalking his ex-fiancée using police databases.<ref>{{cite news |last=McCandless |first=C.C. |date=2024-02-16 |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-url=https://web.archive.org/web/20240216010507/https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-date=2024-02-16 |work=FOX5 Vegas}}</ref> Investigations by the Associated Press and others have found that such misuse often remains undetected until a victim files a complaint or an external audit occurs.<ref>{{cite news |last=Tucker |first=Eric |date=2016-09-27 |title=When cops abuse confidential databases |url=https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-url=https://web.archive.org/web/20230721171815/https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-date=2023-07-21 |work=Associated Press}}</ref>

Researchers and civil liberties organizations have documented audit findings and policy gaps in agency oversight of ALPR access. While vendors and agencies rely on access logs and written policies, audits have found that these safeguards have not consistently prevented or detected misuse.<ref>{{cite web |date=2023-02-22 |title=Automated License Plate Readers widely used, subject to abuse |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-url=https://web.archive.org/web/20230617100257/https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-date=2023-06-17 |work=University of Michigan}}</ref><ref>{{cite web |last=Davidson |first=Nikki |date=2024-04-16 |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-url=https://web.archive.org/web/20240417005310/https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-date=2024-04-17 |work=Government Technology}}</ref>

The Virginia State Crime Commission's 2025 survey found that despite statutory restrictions on sharing, 20 Virginia law enforcement agencies were still providing continuous access to out-of-state agencies and 9 were providing continuous access to federal agencies. Town police departments and primary sheriff's offices accounted for the majority of non-compliant sharing.<ref name="vscc-2026" />

==See also==

*[[Flock license plate readers]]
*[[Flock Safety]]

==References==
{{reflist}}

[[Category:Flock Safety]]
[[Category:ALPR]]
[[Category:Surveillance]]
[[Category:AI and automation]]

Amazon Luna revocation of third-party games

2026-04-18T21:07:00Z

Louis: new incident article: amazon luna axes third-party games and byol without refunds. researched via deep research + verge reporting, passed 3-layer audit.

{{IncidentCargo
|Company=Amazon
|Date=2026-04-10
|Type=Revocation of Digital Goods
|Status=Ongoing
|Description=Amazon removed the ability to stream previously purchased third-party games on its Luna cloud gaming platform without offering refunds, revoking the cloud access consumers paid for.
}}

On April 10, 2026, [[Amazon]] announced it would end support for individual game purchases and third-party storefront integrations on its Luna cloud gaming platform, revoking cloud streaming access for consumers who had purchased games to play via the service.<ref name="TheVerge_Luna_Shutdown">{{Cite web |title=Amazon Luna axes third-party game purchases |url=https://www.theverge.com/tech/910025/amazon-luna-third-party-games-subscriptions |website=The Verge |date=2026-04-10 |access-date=2026-04-18}}</ref> Effective June 10, 2026, the service removed previously purchased games from its cloud streaming library, though users could still play them on other PC platforms through the accounts used to purchase the titles.<ref name="TheVerge_Luna_Shutdown" /> Amazon stated it would not offer refunds for third-party games purchased through Luna.<ref name="TheVerge_Luna_Shutdown" />

== Background ==
Amazon Luna launched in 2020 as a cloud gaming service competing with Google Stadia and Xbox Cloud Gaming.<ref name="TheVerge_Luna_Shutdown" /> In 2023, Amazon Luna introduced the ability to purchase individual games through the platform.<ref name="TheVerge_Luna_Shutdown" />

== Revocation of Third-Party Purchases ==
Amazon's April 2026 changes prevented players from purchasing third-party games and discontinued subscriptions to third-party services like Ubisoft Plus and Jackbox Games.<ref name="TheVerge_Luna_Shutdown" /> The platform also eliminated its "Bring Your Own Library" benefit, ending support for EA, Ubisoft, and GOG third-party stores and blocking access to titles from those platforms on Luna after June 3, 2026.<ref name="TheVerge_Luna_Shutdown" />

== Lack of Refunds ==
Despite revoking the ability to stream the games via its cloud infrastructure, Amazon refused to offer refunds to users who purchased third-party games through Luna.<ref name="TheVerge_Luna_Shutdown" /> An Amazon spokesperson stated the service was transitioning away from à la carte purchasing in favor of subscription approaches.<ref name="TheVerge_Luna_Shutdown" />

== References ==
{{reflist}}

[[Category:Incidents]]
[[Category:Amazon]]
[[Category:Digital rights]]

Digital Millennium Copyright Act

2026-04-12T23:14:55Z

Louis: /* Title I: Anti-circumvention (Section 1201) */

{{#seo:
|description=The Digital Millennium Copyright Act (DMCA) criminalizes circumventing digital locks & creates safe harbor for platforms. Section 1201 restricts repair & security research.
}}
The '''Digital Millennium Copyright Act''' (DMCA) is a United States copyright law enacted on October 28, 1998, as Public Law 105-304.<ref name="plaw">{{Cite web |title=Public Law 105-304 - Digital Millennium Copyright Act |url=https://www.govinfo.gov/content/pkg/PLAW-105publ304/pdf/PLAW-105publ304.pdf |website=GovInfo |access-date=5 April 2026}}</ref> The statute amended Title 17 of the U.S. Code to implement two 1996 World Intellectual Property Organization (WIPO) treaties, criminalize the circumvention of [[digital rights management|digital locks]], & create safe harbor protections for online service providers.<ref name="hr2281">{{Cite web |title=H.R.2281 - Digital Millennium Copyright Act |url=https://www.congress.gov/bill/105th-congress/house-bill/2281 |website=Congress.gov |access-date=5 April 2026}}</ref> Its most controversial provision, [[DMCA Section 1201]], has been used by manufacturers to block [[right to repair|independent repair]], suppress security research, & prevent [[interoperability]] with third-party products, extending the law's reach well beyond its original anti-piracy purpose.

==Legislative history==

The DMCA originated from the 1996 WIPO diplomatic conference in Geneva, which produced the WIPO Copyright Treaty (WCT) & the WIPO Performances and Phonograms Treaty (WPPT). Both treaties required signatory nations to provide legal protection against circumvention of technological protection measures (TPMs) on copyrighted works.<ref>WIPO Copyright Treaty, Art. 11 (1996); WIPO Performances and Phonograms Treaty, Art. 18 (1996).</ref> The Clinton Administration championed both treaties & urged Congress to pass implementing legislation, arguing that strong digital copyright protections were necessary for the growth of the digital economy.

Rep. Howard Coble (R-NC) introduced H.R. 2281, titled the "WIPO Copyright Treaties Implementation Act," on July 29, 1997. Sen. Orrin Hatch (R-UT) introduced the Senate counterpart, S. 2037.<ref name="hr2281" /> During committee hearings, a coalition of 62 law professors warned Congress that the proposed anti-circumvention rules would create unprecedented "paracopyright" regulations governing conduct traditionally outside copyright law. Prof. Pamela Samuelson of UC Berkeley described the provisions as creating an entirely new property right distinct from any existing right under the Copyright Act.<ref name="samuelson">Pamela Samuelson, ''Intellectual Property and the Digital Economy: Why the Anti-Circumvention Regulations Need to Be Revised'', 14 Berkeley Tech. L.J. 519 (1999).</ref>

The Senate passed S. 2037 by a 99-0 roll call vote on May 14, 1998. The House passed H.R. 2281 by voice vote under suspension of the rules on August 4, 1998. A conference committee reconciled the two versions, filing Conference Report 105-796 on October 8, 1998.<ref name="plaw" /> President Clinton signed the bill on October 28, 1998.

Congress intended a "grand bargain": content creators received legal protections for their digital locks, while online service providers received safe harbors shielding them from secondary liability for user-uploaded content. In practice, the anti-circumvention provisions have been used to restrict repair markets & block third-party compatibility, while the safe harbor takedown system has been used for censorship & anti-competitive purposes.

==Structure of the law==

The DMCA contains five titles, each addressing different aspects of digital copyright.<ref name="plaw" />

===Title I: Anti-circumvention (Section 1201)===

{{Main|DMCA Section 1201}}

Title I added Sections 1201 & 1202 to the Copyright Act. Section 1201 prohibits circumventing TPMs that control access to copyrighted works & bans the distribution of tools designed to do so.<ref>17 U.S.C. § 1201.</ref> Section 1202 protects Copyright Management Information (CMI), making it illegal to remove or alter digital watermarks or identifying metadata with the intent to enable infringement.<ref>17 U.S.C. § 1202.</ref>

Section 1201 is the DMCA's most litigated & most criticized provision. Congress included a "fail-safe" mechanism: every three years, the U.S. Copyright Office conducts a rulemaking to grant temporary exemptions from the circumvention ban.<ref>17 U.S.C. § 1201(a)(1)(C).</ref> Nine rulemaking cycles have been completed since 2000, granting exemptions for smartphone jailbreaking, vehicle repair, medical device repair, & security research, among others. All exemptions expire automatically & must be renewed.<ref>17 U.S.C. § 1201(a)(1)(B)-(D).</ref>

The most consequential limitation is the "tools gap." '''The Librarian of Congress can only exempt the ''act'' of circumvention; the anti-trafficking provisions in 1201(a)(2) remain untouched. A consumer may have the legal right to bypass a software lock but no legal way to obtain the tool needed to do so.'''<ref>17 U.S.C. § 1201(a)(1)(C)-(D) (granting exemption authority only for the act of circumvention, not for trafficking in tools).</ref> The [https://fulu.org FULU Foundation]'s repair bounty program paid a developer $20,000 to bypass software locks on [[Echelon fitness firmware lockout|Echelon exercise bikes]], but distributing the resulting tool in the United States violates Section 1201.<ref>{{Cite web |last=Koebler |first=Jason |date=27 August 2025 |title=Developer Unlocks Newly Enshittified Echelon Exercise Bikes, But Can't Legally Release His Software |url=https://www.404media.co/developer-unlocks-newly-enshittified-echelon-exercise-bikes-but-cant-legally-release-his-software/ |website=404 Media |access-date=5 April 2026}}</ref>

===Title II: Safe harbor (Section 512)===

Title II created Section 512 of the Copyright Act, establishing four safe harbors for online service providers (OSPs) against copyright infringement liability.<ref name="sec512">17 U.S.C. § 512.</ref>

'''Section 512(a)''' protects ISPs acting as conduits for data transmission. '''Section 512(b)''' covers system caching. '''Section 512(c)''', the most frequently invoked safe harbor, protects platforms hosting user-generated content (YouTube, social media) from liability provided they lack actual knowledge of specific infringing material, receive no direct financial benefit from the infringement where they can control it, & remove content promptly upon receiving a valid notice.<ref name="sec512" /> '''Section 512(d)''' covers search engines & directories that link to infringing material.

To qualify for any safe harbor, an OSP must adopt & "reasonably implement" a policy for terminating repeat infringers under Section 512(i), & must register a designated agent with the Copyright Office to receive takedown notices.<ref name="sec512" />

====Notice-and-takedown procedure====

Section 512 established an extrajudicial mechanism for copyright enforcement. A copyright holder sends a written notice to the OSP's designated agent identifying the infringed work, the infringing material (usually by URL), & a statement of good faith belief that the use is unauthorized, signed under penalty of perjury.<ref name="sec512" /> The OSP must "expeditiously" remove the material to maintain safe harbor immunity.

The affected user may file a counter-notification, stating under penalty of perjury that the material was removed by mistake or misidentification. Once a valid counter-notice is filed, the OSP must restore the material within 10 to 14 business days unless the copyright holder files a federal lawsuit.<ref name="sec512" />

Section 512(f) creates liability for knowingly material misrepresentations in takedown notices or counter-notices. In practice, courts have set the bar for 512(f) claims so high that the provision provides little deterrent against fraudulent takedowns.

===Title III: Computer maintenance===

Title III amended Section 117 of the Copyright Act to allow making copies of a computer program during the maintenance or repair of a machine, provided the copy is made solely by activating the machine & is destroyed immediately afterward.<ref>17 U.S.C. § 117(c).</ref> Congress enacted this to overturn ''MAI Systems Corp. v. Peak Computer, Inc.'' (9th Cir. 1993), which held that loading software into RAM during computer repair constituted copyright infringement.<ref>''MAI Systems Corp. v. Peak Computer, Inc.'', 991 F.2d 511 (9th Cir. 1993).</ref>

===Title IV: Miscellaneous provisions===

Congress also directed the Copyright Office to study digital distance education under Title IV, which contains several amendments relevant to libraries, education, & broadcasting. That study led to the Technology, Education, and Copyright Harmonization (TEACH) Act of 2002.<ref name="plaw" /> Title IV also expanded the library & archives preservation exemption & addressed ephemeral recordings for sound recordings.

===Title V: Vessel hull designs===

Chapter 13 of Title 17 received a ''sui generis'' protection regime for boat hull designs under Title V.<ref name="plaw" /> It has minimal consumer rights relevance.

==Section 512 in practice==

===Takedown volume===

The scale of DMCA takedowns has grown exponentially since the statute's passage. By late 2016, Google had processed 1 billion URL removal requests. As of early 2026, Google has received over 16.5 billion takedown requests, processing roughly 50 million per week.<ref name="google-transparency">{{Cite web |title=Google Transparency Report: Copyright |url=https://transparencyreport.google.com/copyright/overview |website=Google |access-date=12 April 2026}}</ref> The Lumen Database, a research project at Harvard Law School, has archived over 67 million takedown notices submitted by copyright holders across platforms.<ref name="lumen">{{Cite web |title=About Lumen |url=https://lumendatabase.org/pages/about |website=Lumen Database, Harvard Law School |access-date=12 April 2026}}</ref>

===Takedown abuse===

The automated & rapid nature of the system has enabled widespread abuse. Because OSPs face liability if they fail to remove content, they err on the side of takedown, creating a presumption of removal for users.

In 2009, the U.S. Chamber of Commerce filed a DMCA takedown against a parody website created by the activist group The Yes Men, temporarily disabling 400 other websites hosted on the same ISP.<ref>{{Cite web |title=U.S. Chamber of Commerce uses the DMCA to silence critic |url=https://publicknowledge.org/u-s-chamber-of-commerce-uses-the-dmca-to-silence-critic/ |website=Public Knowledge |date=27 October 2009 |access-date=5 April 2026}}</ref> Film critics & video essayists relying on fair use routinely have their YouTube accounts suspended via automated copyright strikes. Academic researchers using the Lumen Database identified nearly 34,000 coordinated fraudulent notices using backdated "fake original" URLs on dummy websites to delist legitimate news sites from search results.

YouTube's Content ID system, which goes beyond the statutory requirements of Section 512, automatically demonetizes or blocks videos without conducting fair use analysis. Small creators cannot fight claims from media conglomerates with dedicated enforcement teams. Content ID processes over 700 million claims per year.<ref name="google-transparency" />

===Key court cases===

Three appellate decisions define the modern scope of Section 512.

In ''Viacom International, Inc. v. YouTube, Inc.'' (2nd Cir. 2012), Viacom sued YouTube for $1 billion, alleging YouTube built its business on unauthorized hosting of Viacom's content. The Second Circuit ruled that general awareness of ubiquitous infringement on a platform does not strip safe harbor protection; a copyright holder must show the OSP had "actual knowledge" of specific infringing clips or "red flag" awareness where specific infringement was objectively obvious.<ref>''Viacom International, Inc. v. YouTube, Inc.'', 676 F.3d 19 (2d Cir. 2012).</ref>

In ''Capitol Records, LLC v. Vimeo, LLC'' (2nd Cir. 2016), the court held that Section 512(c) safe harbor applies to pre-1972 sound recordings & that Vimeo employees viewing or "liking" user-uploaded videos containing copyrighted music did not establish "red flag" knowledge.<ref>''Capitol Records, LLC v. Vimeo, LLC'', 826 F.3d 78 (2d Cir. 2016).</ref>

''BMG Rights Management v. Cox Communications'' (4th Cir. 2018) established that safe harbor requires genuine implementation of a repeat infringer policy. Cox had a 13-strike policy but never terminated paying subscribers; it routinely deleted millions of notices & blacklisted copyright monitors. The Fourth Circuit stripped Cox's safe harbor, ruling that "repeat infringers" means anyone who repeatedly infringes, not only those adjudicated liable in court.<ref>''BMG Rights Management, LLC v. Cox Communications, Inc.'', 881 F.3d 293 (4th Cir. 2018).</ref>

===The 2020 Copyright Office study===

After a five-year investigation, the U.S. Copyright Office released a 250-page report in May 2020 evaluating the effectiveness of Section 512.<ref name="512study">{{Cite web |title=Section 512 of Title 17: A Report of the Register of Copyrights |url=https://www.copyright.gov/policy/section512/section-512-full-report.pdf |website=U.S. Copyright Office |date=May 2020 |access-date=5 April 2026}}</ref> The Office concluded that the original balance Congress intended has been "unbalanced," overwhelmingly favoring OSPs at the expense of content creators. The burden of policing the internet for identical re-uploads falls entirely on rights holders.

The Office recommended legislative "fine-tuning" but explicitly declined to recommend European-style "notice-and-staydown" mandates or site-blocking, citing the need for additional study of "potential non-copyright implications." Recommendations included clarifying the distinction between "actual" & "red flag" knowledge, adjusting the 10-to-14-day counter-notice waiting period, & tightening eligibility requirements for repeat infringer policies.<ref name="512study" />

==Criticism==

===Academic criticism===

Prof. Pamela Samuelson has argued that the DMCA's anti-circumvention provisions represent an unprecedented departure into "paracopyright," regulating conduct outside the traditional sphere of intellectual property.<ref name="samuelson" /> Legal scholars have argued that Section 512 has created a private, extrajudicial removal regime that bypasses the procedural due process inherent in the court system. Content is removed first, with the burden on the affected party to contest the removal after the fact.

===Electronic Frontier Foundation===

The EFF has challenged Section 1201 since the statute's passage. It argues that the anti-circumvention provisions pose "a serious threat that jeopardizes fair use," chilling free expression & security research by criminalizing the act of bypassing digital locks even for lawful purposes.<ref name="eff-dmca">{{Cite web |title=DMCA |url=https://www.eff.org/issues/dmca |website=Electronic Frontier Foundation |access-date=5 April 2026}}</ref> On Section 512, the EFF defends the existence of safe harbors as essential to the internet's functioning but criticizes the abuse of the takedown system by corporations seeking to silence speech.

===iFixit & the Repair Association===

For hardware repair advocates, the DMCA is a tool for corporate monopolization through software locks. Because modern devices run software, manufacturers can use Section 1201 digital locks to prevent independent shops & owners from fixing their own property. [[John Deere]] has been a prominent example: the Foundation for American Innovation documented how the company uses copyright law to prevent farmers from repairing their own tractors.<ref>{{Cite web |title=How John Deere Hijacked Copyright Law To Keep You From Tinkering With Your Tractor |url=https://www.thefai.org/posts/how-john-deere-hijacked-copyright-law-to-keep-you-from-tinkering-with-your-tractor |last=Hogg |first=Luke |date=8 January 2024 |website=Foundation for American Innovation |access-date=5 April 2026}}</ref> Kyle Wiens, CEO of iFixit, testified before the House Judiciary Subcommittee on Courts, Intellectual Property, and the Internet on July 18, 2023, describing the triennial exemption process as requiring citizens to spend tens of thousands of dollars in legal fees every three years to request permission to repair their own equipment.

===Public Knowledge===

Critics of the triennial rulemaking process have called it a "Rube Goldberg contraption" that cannot keep pace with technological change. Public Knowledge opposed the SMART Copyright Act, warning that giving the Copyright Office the power to mandate internet-wide upload filtering would endanger free expression & internet infrastructure.

==Reform proposals==

===Section 1201 reform===

Multiple bills have sought to reform the anti-circumvention provisions. None have passed. The '''Unlocking Technology Act''' (H.R. 1892, 113th Congress; H.R. 1587, 114th Congress), introduced by Rep. Zoe Lofgren (D-CA) with Rep. Thomas Massie (R-KY) as original cosponsor, would have made circumvention illegal only when tied to actual copyright infringement & legalized distribution of tools for non-infringing uses. Both versions died in committee.<ref>{{Cite web |title=H.R.1892 - Unlocking Technology Act of 2013 |url=https://www.congress.gov/bill/113th-congress/house-bill/1892 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Ron Wyden (D-OR) introduced the '''Breaking Down Barriers to Innovation Act''' (S. 990, 114th Congress), which would have automatically renewed triennial exemptions & expanded protections for security research, repair, & accessibility. Rep. Jared Polis (D-CO) introduced a companion bill, H.R. 1883, in the House. Both died in committee.<ref>{{Cite web |title=S.990 - Breaking Down Barriers to Innovation Act of 2015 |url=https://www.congress.gov/bill/114th-congress/senate-bill/990 |website=Congress.gov |access-date=5 April 2026}}</ref>

Rep. Mondaire Jones (D-NY), with Rep. Victoria Spartz (R-IN) as original cosponsor, introduced the '''Freedom to Repair Act''' (H.R. 6566, 117th Congress), which would have exempted circumvention for repair & permitted trafficking in repair tools. It died in committee.<ref>{{Cite web |title=H.R.6566 - Freedom to Repair Act |url=https://www.congress.gov/bill/117th-congress/house-bill/6566 |website=Congress.gov |access-date=5 April 2026}}</ref>

The only legislative success has been the '''Unlocking Consumer Choice and Wireless Competition Act of 2014''', which restored the phone unlocking exemption after the Copyright Office revoked it in 2012 & uniquely allowed third-party unlocking assistance.<ref>Pub. L. 113-144, Unlocking Consumer Choice and Wireless Competition Act (2014).</ref>

===Section 512 reform===

The '''SMART Copyright Act''' (S. 3880, 117th Congress), introduced by Sen. Thom Tillis (R-NC) & Sen. Patrick Leahy (D-VT), moved in the opposite direction from 1201 reform bills. It would have mandated "Standard Technical Measures" that platforms must accommodate to retain safe harbor, effectively requiring government-approved upload filtering. Digital rights groups, startups, & library associations opposed it. It died in committee.<ref>{{Cite web |title=S. 3880 - SMART Copyright Act of 2022 |url=https://www.congress.gov/bill/117th-congress/senate-bill/3880 |website=Congress.gov |access-date=5 April 2026}}</ref>

The '''CASE Act''', passed on December 27, 2020, as part of the Consolidated Appropriations Act of 2021, created the Copyright Claims Board (CCB), a voluntary small-claims tribunal within the Copyright Office for copyright disputes capped at $30,000 in damages.<ref>Pub. L. 116-260, Title II, Subtitle B (Copyright Alternative in Small-Claims Enforcement Act of 2020).</ref>

===State workarounds===

State law cannot override federal copyright law, so state [[right to repair]] bills work around Section 1201 by requiring manufacturers to bypass their own locks rather than authorizing consumers to do so. Colorado's HB22-1031 (2022) requires powered wheelchair manufacturers to provide repair tools, passwords, & documentation needed for repair.<ref>Colorado HB22-1031 (2022).</ref> Oregon's SB 1596 banned [[part pairing]] entirely, prohibiting manufacturers from using software locks to disable non-OEM replacement parts.<ref>Oregon SB 1596 (2024).</ref>

===Executive actions===

President Biden's July 2021 Executive Order on Promoting Competition directed the Federal Trade Commission to draft rules preventing manufacturer repair restrictions.<ref>Executive Order 14036, ''Promoting Competition in the American Economy'' (July 9, 2021).</ref> The FTC's May 2021 ''Nixing the Fix'' report examined anti-competitive repair restrictions & noted Congressional concern about their impact on consumers' rights under the [[Magnuson-Moss Warranty Act]]. The FTC stated it "stands ready to work with lawmakers" on repair restriction enforcement.<ref>{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |url=https://www.ftc.gov/reports/nixing-fix-ftc-report-congress-repair-restrictions |website=Federal Trade Commission |date=May 2021 |access-date=5 April 2026}}</ref>

==Industry lobbying==

The Recording Industry Association of America (RIAA) has spent millions annually on lobbying since 1998.<ref name="opensecrets">{{Cite web |title=Lobbying Profile: Recording Industry Assn of America |url=https://www.opensecrets.org/orgs/recording-industry-assn-of-america/lobbying?id=D000000581 |website=OpenSecrets |access-date=5 April 2026}}</ref> The Entertainment Software Association (ESA) reported $4.83 million in federal lobbying in 2012 & has consistently opposed game preservation exemptions that would allow remote access to archived titles.

A documented revolving door exists between the Copyright Office & copyright industry groups. Karyn Temple went from the RIAA's litigation department to Register of Copyrights, then to General Counsel of the Motion Picture Association (MPA). Maria Pallante went from Register of Copyrights to President and CEO of the Association of American Publishers. Former Senator Chris Dodd became Chairman and CEO of the MPAA after leaving the Senate.

==See also==

*[[DMCA Section 1201]]
*[[Right to repair]]
*[[Right to own]]
*[[Part pairing]]
*[[Digital rights management]]
*[[Feature ransom]]
*[[Discontinuation bricking]]
*[[Planned obsolescence]]
*[[Magnuson-Moss Warranty Act]]

==References==
{{reflist}}

[[Category:Legislation]]
[[Category:US legislation]]
[[Category:Digital rights management]]

Digital Millennium Copyright Act

2026-04-12T23:02:56Z

Louis: Fixed invalid <ref> tags with integer names

{{#seo:
|description=The Digital Millennium Copyright Act (DMCA) criminalizes circumventing digital locks & creates safe harbor for platforms. Section 1201 restricts repair & security research.
}}
The '''Digital Millennium Copyright Act''' (DMCA) is a United States copyright law enacted on October 28, 1998, as Public Law 105-304.<ref name="plaw">{{Cite web |title=Public Law 105-304 - Digital Millennium Copyright Act |url=https://www.govinfo.gov/content/pkg/PLAW-105publ304/pdf/PLAW-105publ304.pdf |website=GovInfo |access-date=5 April 2026}}</ref> The statute amended Title 17 of the U.S. Code to implement two 1996 World Intellectual Property Organization (WIPO) treaties, criminalize the circumvention of [[digital rights management|digital locks]], & create safe harbor protections for online service providers.<ref name="hr2281">{{Cite web |title=H.R.2281 - Digital Millennium Copyright Act |url=https://www.congress.gov/bill/105th-congress/house-bill/2281 |website=Congress.gov |access-date=5 April 2026}}</ref> Its most controversial provision, [[DMCA Section 1201]], has been used by manufacturers to block [[right to repair|independent repair]], suppress security research, & prevent [[interoperability]] with third-party products, extending the law's reach well beyond its original anti-piracy purpose.

== Legislative history ==

The DMCA originated from the 1996 WIPO diplomatic conference in Geneva, which produced the WIPO Copyright Treaty (WCT) & the WIPO Performances and Phonograms Treaty (WPPT). Both treaties required signatory nations to provide legal protection against circumvention of technological protection measures (TPMs) on copyrighted works.<ref>WIPO Copyright Treaty, Art. 11 (1996); WIPO Performances and Phonograms Treaty, Art. 18 (1996).</ref> The Clinton Administration championed both treaties & urged Congress to pass implementing legislation, arguing that strong digital copyright protections were necessary for the growth of the digital economy.

Rep. Howard Coble (R-NC) introduced H.R. 2281, titled the "WIPO Copyright Treaties Implementation Act," on July 29, 1997. Sen. Orrin Hatch (R-UT) introduced the Senate counterpart, S. 2037.<ref name="hr2281" /> During committee hearings, a coalition of 62 law professors warned Congress that the proposed anti-circumvention rules would create unprecedented "paracopyright" regulations governing conduct traditionally outside copyright law. Prof. Pamela Samuelson of UC Berkeley described the provisions as creating an entirely new property right distinct from any existing right under the Copyright Act.<ref name="samuelson">Pamela Samuelson, ''Intellectual Property and the Digital Economy: Why the Anti-Circumvention Regulations Need to Be Revised'', 14 Berkeley Tech. L.J. 519 (1999).</ref>

The Senate passed S. 2037 by a 99-0 roll call vote on May 14, 1998. The House passed H.R. 2281 by voice vote under suspension of the rules on August 4, 1998. A conference committee reconciled the two versions, filing Conference Report 105-796 on October 8, 1998.<ref name="plaw" /> President Clinton signed the bill on October 28, 1998.

Congress intended a "grand bargain": content creators received legal protections for their digital locks, while online service providers received safe harbors shielding them from secondary liability for user-uploaded content. In practice, the anti-circumvention provisions have been used to restrict repair markets & block third-party compatibility, while the safe harbor takedown system has been used for censorship & anti-competitive purposes.

== Structure of the law ==

The DMCA contains five titles, each addressing different aspects of digital copyright.<ref name="plaw" />

=== Title I: Anti-circumvention (Section 1201) ===

{{Main|DMCA Section 1201}}

Title I added Sections 1201 & 1202 to the Copyright Act. Section 1201 prohibits circumventing TPMs that control access to copyrighted works & bans the distribution of tools designed to do so.<ref>17 U.S.C. § 1201.</ref> Section 1202 protects Copyright Management Information (CMI), making it illegal to remove or alter digital watermarks or identifying metadata with the intent to enable infringement.<ref>17 U.S.C. § 1202.</ref>

Section 1201 is the DMCA's most litigated & most criticized provision. Congress included a "fail-safe" mechanism: every three years, the U.S. Copyright Office conducts a rulemaking to grant temporary exemptions from the circumvention ban.<ref>17 U.S.C. § 1201(a)(1)(C).</ref> Nine rulemaking cycles have been completed since 2000, granting exemptions for smartphone jailbreaking, vehicle repair, medical device repair, & security research, among others. All exemptions expire automatically & must be renewed.<ref>17 U.S.C. § 1201(a)(1)(B)-(D).</ref>

The most consequential limitation is the "tools gap." The Librarian of Congress can only exempt the ''act'' of circumvention; the anti-trafficking provisions in 1201(a)(2) remain untouched. A consumer may have the legal right to bypass a software lock but no legal way to obtain the tool needed to do so.<ref>17 U.S.C. § 1201(a)(1)(C)-(D) (granting exemption authority only for the act of circumvention, not for trafficking in tools).</ref> The [https://fulu.org FULU Foundation]'s repair bounty program paid a developer $20,000 to bypass software locks on [[Echelon fitness firmware lockout|Echelon exercise bikes]], but distributing the resulting tool in the United States violates Section 1201.<ref>{{Cite web |last=Koebler |first=Jason |date=27 August 2025 |title=Developer Unlocks Newly Enshittified Echelon Exercise Bikes, But Can't Legally Release His Software |url=https://www.404media.co/developer-unlocks-newly-enshittified-echelon-exercise-bikes-but-cant-legally-release-his-software/ |website=404 Media |access-date=5 April 2026}}</ref>

=== Title II: Safe harbor (Section 512) ===

Title II created Section 512 of the Copyright Act, establishing four safe harbors for online service providers (OSPs) against copyright infringement liability.<ref name="sec512">17 U.S.C. § 512.</ref>

'''Section 512(a)''' protects ISPs acting as conduits for data transmission. '''Section 512(b)''' covers system caching. '''Section 512(c)''', the most frequently invoked safe harbor, protects platforms hosting user-generated content (YouTube, social media) from liability provided they lack actual knowledge of specific infringing material, receive no direct financial benefit from the infringement where they can control it, & remove content promptly upon receiving a valid notice.<ref name="sec512" /> '''Section 512(d)''' covers search engines & directories that link to infringing material.

To qualify for any safe harbor, an OSP must adopt & "reasonably implement" a policy for terminating repeat infringers under Section 512(i), & must register a designated agent with the Copyright Office to receive takedown notices.<ref name="sec512" />

==== Notice-and-takedown procedure ====

Section 512 established an extrajudicial mechanism for copyright enforcement. A copyright holder sends a written notice to the OSP's designated agent identifying the infringed work, the infringing material (usually by URL), & a statement of good faith belief that the use is unauthorized, signed under penalty of perjury.<ref name="sec512" /> The OSP must "expeditiously" remove the material to maintain safe harbor immunity.

The affected user may file a counter-notification, stating under penalty of perjury that the material was removed by mistake or misidentification. Once a valid counter-notice is filed, the OSP must restore the material within 10 to 14 business days unless the copyright holder files a federal lawsuit.<ref name="sec512" />

Section 512(f) creates liability for knowingly material misrepresentations in takedown notices or counter-notices. In practice, courts have set the bar for 512(f) claims so high that the provision provides little deterrent against fraudulent takedowns.

=== Title III: Computer maintenance ===

Title III amended Section 117 of the Copyright Act to allow making copies of a computer program during the maintenance or repair of a machine, provided the copy is made solely by activating the machine & is destroyed immediately afterward.<ref>17 U.S.C. § 117(c).</ref> Congress enacted this to overturn ''MAI Systems Corp. v. Peak Computer, Inc.'' (9th Cir. 1993), which held that loading software into RAM during computer repair constituted copyright infringement.<ref>''MAI Systems Corp. v. Peak Computer, Inc.'', 991 F.2d 511 (9th Cir. 1993).</ref>

=== Title IV: Miscellaneous provisions ===

Congress also directed the Copyright Office to study digital distance education under Title IV, which contains several amendments relevant to libraries, education, & broadcasting. That study led to the Technology, Education, and Copyright Harmonization (TEACH) Act of 2002.<ref name="plaw" /> Title IV also expanded the library & archives preservation exemption & addressed ephemeral recordings for sound recordings.

=== Title V: Vessel hull designs ===

Chapter 13 of Title 17 received a ''sui generis'' protection regime for boat hull designs under Title V.<ref name="plaw" /> It has minimal consumer rights relevance.

== Section 512 in practice ==

=== Takedown volume ===

The scale of DMCA takedowns has grown exponentially since the statute's passage. By late 2016, Google had processed 1 billion URL removal requests. As of early 2026, Google has received over 16.5 billion takedown requests, processing roughly 50 million per week.<ref name="google-transparency">{{Cite web |title=Google Transparency Report: Copyright |url=https://transparencyreport.google.com/copyright/overview |website=Google |access-date=12 April 2026}}</ref> The Lumen Database, a research project at Harvard Law School, has archived over 67 million takedown notices submitted by copyright holders across platforms.<ref name="lumen">{{Cite web |title=About Lumen |url=https://lumendatabase.org/pages/about |website=Lumen Database, Harvard Law School |access-date=12 April 2026}}</ref>

=== Takedown abuse ===

The automated & rapid nature of the system has enabled widespread abuse. Because OSPs face liability if they fail to remove content, they err on the side of takedown, creating a presumption of removal for users.

In 2009, the U.S. Chamber of Commerce filed a DMCA takedown against a parody website created by the activist group The Yes Men, temporarily disabling 400 other websites hosted on the same ISP.<ref>{{Cite web |title=U.S. Chamber of Commerce uses the DMCA to silence critic |url=https://publicknowledge.org/u-s-chamber-of-commerce-uses-the-dmca-to-silence-critic/ |website=Public Knowledge |date=27 October 2009 |access-date=5 April 2026}}</ref> Film critics & video essayists relying on fair use routinely have their YouTube accounts suspended via automated copyright strikes. Academic researchers using the Lumen Database identified nearly 34,000 coordinated fraudulent notices using backdated "fake original" URLs on dummy websites to delist legitimate news sites from search results.

YouTube's Content ID system, which goes beyond the statutory requirements of Section 512, automatically demonetizes or blocks videos without conducting fair use analysis. Small creators cannot fight claims from media conglomerates with dedicated enforcement teams. Content ID processes over 700 million claims per year.<ref name="google-transparency" />

=== Key court cases ===

Three appellate decisions define the modern scope of Section 512.

In ''Viacom International, Inc. v. YouTube, Inc.'' (2nd Cir. 2012), Viacom sued YouTube for $1 billion, alleging YouTube built its business on unauthorized hosting of Viacom's content. The Second Circuit ruled that general awareness of ubiquitous infringement on a platform does not strip safe harbor protection; a copyright holder must show the OSP had "actual knowledge" of specific infringing clips or "red flag" awareness where specific infringement was objectively obvious.<ref>''Viacom International, Inc. v. YouTube, Inc.'', 676 F.3d 19 (2d Cir. 2012).</ref>

In ''Capitol Records, LLC v. Vimeo, LLC'' (2nd Cir. 2016), the court held that Section 512(c) safe harbor applies to pre-1972 sound recordings & that Vimeo employees viewing or "liking" user-uploaded videos containing copyrighted music did not establish "red flag" knowledge.<ref>''Capitol Records, LLC v. Vimeo, LLC'', 826 F.3d 78 (2d Cir. 2016).</ref>

''BMG Rights Management v. Cox Communications'' (4th Cir. 2018) established that safe harbor requires genuine implementation of a repeat infringer policy. Cox had a 13-strike policy but never terminated paying subscribers; it routinely deleted millions of notices & blacklisted copyright monitors. The Fourth Circuit stripped Cox's safe harbor, ruling that "repeat infringers" means anyone who repeatedly infringes, not only those adjudicated liable in court.<ref>''BMG Rights Management, LLC v. Cox Communications, Inc.'', 881 F.3d 293 (4th Cir. 2018).</ref>

=== The 2020 Copyright Office study ===

After a five-year investigation, the U.S. Copyright Office released a 250-page report in May 2020 evaluating the effectiveness of Section 512.<ref name="512study">{{Cite web |title=Section 512 of Title 17: A Report of the Register of Copyrights |url=https://www.copyright.gov/policy/section512/section-512-full-report.pdf |website=U.S. Copyright Office |date=May 2020 |access-date=5 April 2026}}</ref> The Office concluded that the original balance Congress intended has been "unbalanced," overwhelmingly favoring OSPs at the expense of content creators. The burden of policing the internet for identical re-uploads falls entirely on rights holders.

The Office recommended legislative "fine-tuning" but explicitly declined to recommend European-style "notice-and-staydown" mandates or site-blocking, citing the need for additional study of "potential non-copyright implications." Recommendations included clarifying the distinction between "actual" & "red flag" knowledge, adjusting the 10-to-14-day counter-notice waiting period, & tightening eligibility requirements for repeat infringer policies.<ref name="512study" />

== Criticism ==

=== Academic criticism ===

Prof. Pamela Samuelson has argued that the DMCA's anti-circumvention provisions represent an unprecedented departure into "paracopyright," regulating conduct outside the traditional sphere of intellectual property.<ref name="samuelson" /> Legal scholars have argued that Section 512 has created a private, extrajudicial removal regime that bypasses the procedural due process inherent in the court system. Content is removed first, with the burden on the affected party to contest the removal after the fact.

=== Electronic Frontier Foundation ===

The EFF has challenged Section 1201 since the statute's passage. It argues that the anti-circumvention provisions pose "a serious threat that jeopardizes fair use," chilling free expression & security research by criminalizing the act of bypassing digital locks even for lawful purposes.<ref name="eff-dmca">{{Cite web |title=DMCA |url=https://www.eff.org/issues/dmca |website=Electronic Frontier Foundation |access-date=5 April 2026}}</ref> On Section 512, the EFF defends the existence of safe harbors as essential to the internet's functioning but criticizes the abuse of the takedown system by corporations seeking to silence speech.

=== iFixit & the Repair Association ===

For hardware repair advocates, the DMCA is a tool for corporate monopolization through software locks. Because modern devices run software, manufacturers can use Section 1201 digital locks to prevent independent shops & owners from fixing their own property. [[John Deere]] has been a prominent example: the Foundation for American Innovation documented how the company uses copyright law to prevent farmers from repairing their own tractors.<ref>{{Cite web |title=How John Deere Hijacked Copyright Law To Keep You From Tinkering With Your Tractor |url=https://www.thefai.org/posts/how-john-deere-hijacked-copyright-law-to-keep-you-from-tinkering-with-your-tractor |last=Hogg |first=Luke |date=8 January 2024 |website=Foundation for American Innovation |access-date=5 April 2026}}</ref> Kyle Wiens, CEO of iFixit, testified before the House Judiciary Subcommittee on Courts, Intellectual Property, and the Internet on July 18, 2023, describing the triennial exemption process as requiring citizens to spend tens of thousands of dollars in legal fees every three years to request permission to repair their own equipment.

=== Public Knowledge ===

Critics of the triennial rulemaking process have called it a "Rube Goldberg contraption" that cannot keep pace with technological change. Public Knowledge opposed the SMART Copyright Act, warning that giving the Copyright Office the power to mandate internet-wide upload filtering would endanger free expression & internet infrastructure.

== Reform proposals ==

=== Section 1201 reform ===

Multiple bills have sought to reform the anti-circumvention provisions. None have passed. The '''Unlocking Technology Act''' (H.R. 1892, 113th Congress; H.R. 1587, 114th Congress), introduced by Rep. Zoe Lofgren (D-CA) with Rep. Thomas Massie (R-KY) as original cosponsor, would have made circumvention illegal only when tied to actual copyright infringement & legalized distribution of tools for non-infringing uses. Both versions died in committee.<ref>{{Cite web |title=H.R.1892 - Unlocking Technology Act of 2013 |url=https://www.congress.gov/bill/113th-congress/house-bill/1892 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Ron Wyden (D-OR) introduced the '''Breaking Down Barriers to Innovation Act''' (S. 990, 114th Congress), which would have automatically renewed triennial exemptions & expanded protections for security research, repair, & accessibility. Rep. Jared Polis (D-CO) introduced a companion bill, H.R. 1883, in the House. Both died in committee.<ref>{{Cite web |title=S.990 - Breaking Down Barriers to Innovation Act of 2015 |url=https://www.congress.gov/bill/114th-congress/senate-bill/990 |website=Congress.gov |access-date=5 April 2026}}</ref>

Rep. Mondaire Jones (D-NY), with Rep. Victoria Spartz (R-IN) as original cosponsor, introduced the '''Freedom to Repair Act''' (H.R. 6566, 117th Congress), which would have exempted circumvention for repair & permitted trafficking in repair tools. It died in committee.<ref>{{Cite web |title=H.R.6566 - Freedom to Repair Act |url=https://www.congress.gov/bill/117th-congress/house-bill/6566 |website=Congress.gov |access-date=5 April 2026}}</ref>

The only legislative success has been the '''Unlocking Consumer Choice and Wireless Competition Act of 2014''', which restored the phone unlocking exemption after the Copyright Office revoked it in 2012 & uniquely allowed third-party unlocking assistance.<ref>Pub. L. 113-144, Unlocking Consumer Choice and Wireless Competition Act (2014).</ref>

=== Section 512 reform ===

The '''SMART Copyright Act''' (S. 3880, 117th Congress), introduced by Sen. Thom Tillis (R-NC) & Sen. Patrick Leahy (D-VT), moved in the opposite direction from 1201 reform bills. It would have mandated "Standard Technical Measures" that platforms must accommodate to retain safe harbor, effectively requiring government-approved upload filtering. Digital rights groups, startups, & library associations opposed it. It died in committee.<ref>{{Cite web |title=S. 3880 - SMART Copyright Act of 2022 |url=https://www.congress.gov/bill/117th-congress/senate-bill/3880 |website=Congress.gov |access-date=5 April 2026}}</ref>

The '''CASE Act''', passed on December 27, 2020, as part of the Consolidated Appropriations Act of 2021, created the Copyright Claims Board (CCB), a voluntary small-claims tribunal within the Copyright Office for copyright disputes capped at $30,000 in damages.<ref>Pub. L. 116-260, Title II, Subtitle B (Copyright Alternative in Small-Claims Enforcement Act of 2020).</ref>

=== State workarounds ===

State law cannot override federal copyright law, so state [[right to repair]] bills work around Section 1201 by requiring manufacturers to bypass their own locks rather than authorizing consumers to do so. Colorado's HB22-1031 (2022) requires powered wheelchair manufacturers to provide repair tools, passwords, & documentation needed for repair.<ref>Colorado HB22-1031 (2022).</ref> Oregon's SB 1596 banned [[part pairing]] entirely, prohibiting manufacturers from using software locks to disable non-OEM replacement parts.<ref>Oregon SB 1596 (2024).</ref>

=== Executive actions ===

President Biden's July 2021 Executive Order on Promoting Competition directed the Federal Trade Commission to draft rules preventing manufacturer repair restrictions.<ref>Executive Order 14036, ''Promoting Competition in the American Economy'' (July 9, 2021).</ref> The FTC's May 2021 ''Nixing the Fix'' report examined anti-competitive repair restrictions & noted Congressional concern about their impact on consumers' rights under the [[Magnuson-Moss Warranty Act]]. The FTC stated it "stands ready to work with lawmakers" on repair restriction enforcement.<ref>{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |url=https://www.ftc.gov/reports/nixing-fix-ftc-report-congress-repair-restrictions |website=Federal Trade Commission |date=May 2021 |access-date=5 April 2026}}</ref>

== Industry lobbying ==

The Recording Industry Association of America (RIAA) has spent millions annually on lobbying since 1998.<ref name="opensecrets">{{Cite web |title=Lobbying Profile: Recording Industry Assn of America |url=https://www.opensecrets.org/orgs/recording-industry-assn-of-america/lobbying?id=D000000581 |website=OpenSecrets |access-date=5 April 2026}}</ref> The Entertainment Software Association (ESA) reported $4.83 million in federal lobbying in 2012 & has consistently opposed game preservation exemptions that would allow remote access to archived titles.

A documented revolving door exists between the Copyright Office & copyright industry groups. Karyn Temple went from the RIAA's litigation department to Register of Copyrights, then to General Counsel of the Motion Picture Association (MPA). Maria Pallante went from Register of Copyrights to President and CEO of the Association of American Publishers. Former Senator Chris Dodd became Chairman and CEO of the MPAA after leaving the Senate.

== See also ==

* [[DMCA Section 1201]]
* [[Right to repair]]
* [[Right to own]]
* [[Part pairing]]
* [[Digital rights management]]
* [[Feature ransom]]
* [[Discontinuation bricking]]
* [[Planned obsolescence]]
* [[Magnuson-Moss Warranty Act]]

== References ==
{{reflist}}

[[Category:Legislation]]
[[Category:US legislation]]
[[Category:Digital rights management]]

DJI Romo robot vacuum vulnerability

2026-04-12T22:50:44Z

Louis:

{{IncidentCargo
|Company=DJI
|StartDate=2026-01-25
|EndDate=2026-02-10
|Status=Resolved
|ProductLine=DJI Romo, DJI Power
|Product=DJI Romo P, DJI Romo A, DJI Romo S, DJI Power
|ArticleType=Incident
|Type=Security Vulnerability
|Description=A vulnerability in DJI's MQTT message broker exposed live camera feeds and 2D floor plans from over 10,000 devices to unauthorized remote access.
}}

A critical cloud infrastructure flaw exposed the live camera feeds, microphone audio, and 2D floor plans of consumers to unauthorized remote access. DJI's backend servers inadvertently granted wildcard access<ref name="Medium">{{Cite web |author=Medium |date=February 17, 2026 |title=DJI Romo Security Breach: Researcher Remotely Accessed 7,000 Home Cameras, and One Hole Remains |url=https://medium.com/@hayekesteloo/dji-romo-security-breach-researcher-remotely-accessed-7-000-home-cameras-and-one-hole-remains-f6e0114f11cf |work=Medium}}</ref> to over 10,000 total devices, which included approximately 6,700 DJI Romo robot vacuums and DJI Power portable battery stations.<ref name="Overspill">{{Cite web |author=The Overspill |date=February 25, 2026 |title=Robot vacuum world control China start-up |url=https://theoverspill.blog/2026/02/25/robot-vacuum-world-control-china-start-up-2617/ |work=The Overspill}}</ref> The vulnerability was discovered in late January and patched in February 2026.<ref name="RedState">{{Cite web |last=Smith |first=Ben |date=February 24, 2026 |title=Chinese Tech Flaw Exposed Live Feeds From Thousands of American Homes |url=https://redstate.com/ben-smith/2026/02/24/chinese-tech-flaw-exposed-live-feeds-from-thousands-of-american-homes-n2199504 |work=RedState}}</ref>

== Background ==

DJI launched its first robotic vacuum line, the DJI Romo, in China in August 2025<ref name="DroneDJ">{{Cite web |last=Singh |first=Ishveena |date=October 28, 2025 |title=DJI Romo new launch US |url=https://dronedj.com/2025/10/28/dji-romo-new-launch-us/ |work=DroneDJ}}</ref> and in Europe in October 2025.<ref name="Medium" /> The lineup consists of the Romo P, Romo A, and Romo S models<ref name="DroneDJ" />, priced between €1,299 and €1,899.<ref name="DroneXL">{{Cite web |last=Crumley |first=Bruce |date=October 28, 2025 |title=DJI Romo vacuum Europe |url=https://dronexl.co/2025/10/28/dji-romo-vacuum-europe/ |work=DroneXL}}</ref> The vacuums utilize advanced drone obstacle sensing technology, including dual fisheye vision sensors and solid-state LiDAR, managed through the DJI Home app.<ref name="DroneXL" /> DJI did not officially launch the Romo in the United States.<ref name="DroneXL" /> However, the vulnerability later exposed devices located across the United States, Europe, and China.<ref name="SCWorld">{{Cite web |author=SCWorld |date=February 27, 2026 |title=DJI robot vacuums expose sensitive data due to server vulnerability |url=https://www.scworld.com/brief/dji-robot-vacuums-expose-sensitive-data-due-to-server-vulnerability |work=SCWorld}}</ref>

== Discovery and scope ==

In early 2026, an engineer named Sammy Azdoufal attempted to build a custom application to control his DJI Romo vacuum using a PlayStation 5 controller. Azdoufal utilized Anthropic's<ref name="Malwarebytes">{{Cite web |author=Malwarebytes |date=February 17, 2026 |title=Hobby coder accidentally creates vacuum robot army |url=https://www.malwarebytes.com/blog/news/2026/02/hobby-coder-accidentally-creates-vacuum-robot-army |work=Malwarebytes}}</ref> Claude Code AI coding assistant to reverse-engineer the communication protocols between his vacuum and DJI's remote cloud servers.<ref name="Inc">{{Cite web |author=Inc.com |date=February 18, 2026 |title=Huge Robot Vacuum Security Flaw Exposed After 1 Owner Accidentally Controlled Thousands Using an AI Tool |url=https://www.inc.com/leila-sheridan/huge-robot-vacuum-security-flaw-exposed-after-1-owner-accidentally-controlled-thousands-using-an-ai-tool/91304719 |work=Inc.com}}</ref><ref name="BroBible">{{Cite web |author=BroBible |date=February 24, 2026 |title=Man Gains Control Of 7,000 Robot Vacuums Using Claude AI |url=https://brobible.com/culture/article/man-gains-control-7000-robot-vacuums-using-claude-ai/ |work=BroBible}}</ref>

While authenticating his client on DJI's MQTT message broker, Azdoufal used his vacuum's standard 14-digit serial number.<ref name="Malwarebytes" /> He discovered that the broker lacked topic-level access controls.<ref name="Medium" /> This architectural flaw meant his client was treated as their respective owner, allowing him to subscribe to wildcard topics and access the messages of all connected devices in plaintext at the application layer.<ref name="RedState" />

Within nine minutes of connecting, Azdoufal's system cataloged 6,700 DJI devices across 24 different countries and collected over 100,000 messages.<ref name="Overspill" /> The exposed data included live camera feeds, microphone audio, battery status, and generated floor plans.<ref name="Medium" /> The vulnerability also provided access to DJI Power portable battery stations, which run on the same MQTT infrastructure, bringing the total number of exposed devices to over 10,000.<ref name="Overspill" /> The flaw was strictly limited to devices operating on the consumer DJI Home ecosystem.

=== DJI's response ===

DJI stated that it identified the vulnerability affecting DJI Home through an internal review in late January 2026 and initiated remediation immediately.<ref name="BroBible" /> The company deployed two automated patches on February 8 and February 10 to address the wildcard access issue without requiring user action.<ref name="Medium" /><ref name="RedState" />

== Consumer response ==

Consumers mocked DJI's patching timeline after learning about the incident. Users on social media noted that DJI only fixed the issue in two days after facing public embarrassment, suggesting the company had the capability to resolve the flaw much earlier.<ref name="WesternJournal">{{Cite web |author=Western Journal |date=March 27, 2026 |title=Maybe It Wasn't a Bug: Internet Weighs in After Man Discovered He Could Access 7,000 Robotic Vacuums |url=https://www.westernjournal.com/maybe-wasnt-bug-internet-weighs-man-discovered-access-7000-robotic-vacuums/ |work=Western Journal}}</ref>

The breach contributed to consumer fears regarding surveillance by foreign entities. The vulnerability was contextualized alongside ongoing litigation, such as Texas Attorney General Ken Paxton suing smart TV manufacturers over the unauthorized data collection of connected devices.<ref name="DallasExpress">{{Cite web |author=Dallas Express |date=March 4, 2026 |title=7,000 DJI Romo Robot Vacuums Hacked: Live Cameras, Floor Plans Exposed in Massive Security Flaw |url=https://dallasexpress.com/national/7000-dji-romo-robot-vacuums-hacked-live-cameras-floor-plans-exposed-in-massive-security-flaw/ |work=Dallas Express}}</ref>

== References ==

{{reflist}}

[[Category:DJI]]
[[Category:Security Vulnerability]]

DJI Romo robot vacuum vulnerability

2026-04-12T22:46:18Z

Louis: rewrote the whole thing, corrected 2025 date to 2026, fixed mqtt broker technical details, mapped claims to exact sources

{{IncidentCargo
|Company=DJI
|StartDate=2026-01-25
|EndDate=2026-02-10
|Status=Resolved
|ProductLine=DJI Romo, DJI Power
|Product=DJI Romo P, DJI Romo A, DJI Romo S, DJI Power
|ArticleType=Incident
|Type=Security Vulnerability
|Description=A vulnerability in DJI's MQTT message broker exposed live camera feeds and 2D floor plans from over 10,000 devices to unauthorized remote access.
}}

'''DJI Romo remote access vulnerability''' was a critical cloud infrastructure flaw that exposed the live camera feeds, microphone audio, and 2D floor plans of consumers to unauthorized remote access. DJI's backend servers inadvertently granted wildcard access<ref name="Medium">{{Cite web |author=Medium |date=February 17, 2026 |title=DJI Romo Security Breach: Researcher Remotely Accessed 7,000 Home Cameras, and One Hole Remains |url=https://medium.com/@hayekesteloo/dji-romo-security-breach-researcher-remotely-accessed-7-000-home-cameras-and-one-hole-remains-f6e0114f11cf |work=Medium}}</ref> to over 10,000 total devices, which included approximately 6,700 DJI Romo robot vacuums and DJI Power portable battery stations.<ref name="Overspill">{{Cite web |author=The Overspill |date=February 25, 2026 |title=Robot vacuum world control China start-up |url=https://theoverspill.blog/2026/02/25/robot-vacuum-world-control-china-start-up-2617/ |work=The Overspill}}</ref> The vulnerability was discovered in late January and patched in February 2026.<ref name="RedState">{{Cite web |last=Smith |first=Ben |date=February 24, 2026 |title=Chinese Tech Flaw Exposed Live Feeds From Thousands of American Homes |url=https://redstate.com/ben-smith/2026/02/24/chinese-tech-flaw-exposed-live-feeds-from-thousands-of-american-homes-n2199504 |work=RedState}}</ref>

== Background ==

DJI launched its first robotic vacuum line, the DJI Romo, in China in August 2025<ref name="DroneDJ">{{Cite web |last=Singh |first=Ishveena |date=October 28, 2025 |title=DJI Romo new launch US |url=https://dronedj.com/2025/10/28/dji-romo-new-launch-us/ |work=DroneDJ}}</ref> and in Europe in October 2025.<ref name="Medium" /> The lineup consists of the Romo P, Romo A, and Romo S models<ref name="DroneDJ" />, priced between €1,299 and €1,899.<ref name="DroneXL">{{Cite web |last=Crumley |first=Bruce |date=October 28, 2025 |title=DJI Romo vacuum Europe |url=https://dronexl.co/2025/10/28/dji-romo-vacuum-europe/ |work=DroneXL}}</ref> The vacuums utilize advanced drone obstacle sensing technology, including dual fisheye vision sensors and solid-state LiDAR, managed through the DJI Home app.<ref name="DroneXL" /> DJI did not officially launch the Romo in the United States.<ref name="DroneXL" /> However, the vulnerability later exposed devices located across the United States, Europe, and China.<ref name="SCWorld">{{Cite web |author=SCWorld |date=February 27, 2026 |title=DJI robot vacuums expose sensitive data due to server vulnerability |url=https://www.scworld.com/brief/dji-robot-vacuums-expose-sensitive-data-due-to-server-vulnerability |work=SCWorld}}</ref>

== Discovery and scope ==

In early 2026, an engineer named Sammy Azdoufal attempted to build a custom application to control his DJI Romo vacuum using a PlayStation 5 controller. Azdoufal utilized Anthropic's<ref name="Malwarebytes">{{Cite web |author=Malwarebytes |date=February 17, 2026 |title=Hobby coder accidentally creates vacuum robot army |url=https://www.malwarebytes.com/blog/news/2026/02/hobby-coder-accidentally-creates-vacuum-robot-army |work=Malwarebytes}}</ref> Claude Code AI coding assistant to reverse-engineer the communication protocols between his vacuum and DJI's remote cloud servers.<ref name="Inc">{{Cite web |author=Inc.com |date=February 18, 2026 |title=Huge Robot Vacuum Security Flaw Exposed After 1 Owner Accidentally Controlled Thousands Using an AI Tool |url=https://www.inc.com/leila-sheridan/huge-robot-vacuum-security-flaw-exposed-after-1-owner-accidentally-controlled-thousands-using-an-ai-tool/91304719 |work=Inc.com}}</ref><ref name="BroBible">{{Cite web |author=BroBible |date=February 24, 2026 |title=Man Gains Control Of 7,000 Robot Vacuums Using Claude AI |url=https://brobible.com/culture/article/man-gains-control-7000-robot-vacuums-using-claude-ai/ |work=BroBible}}</ref>

While authenticating his client on DJI's MQTT message broker, Azdoufal used his vacuum's standard 14-digit serial number.<ref name="Malwarebytes" /> He discovered that the broker lacked topic-level access controls.<ref name="Medium" /> This architectural flaw meant his client was treated as their respective owner, allowing him to subscribe to wildcard topics and access the messages of all connected devices in plaintext at the application layer.<ref name="RedState" />

Within nine minutes of connecting, Azdoufal's system cataloged 6,700 DJI devices across 24 different countries and collected over 100,000 messages.<ref name="Overspill" /> The exposed data included live camera feeds, microphone audio, battery status, and generated floor plans.<ref name="Medium" /> The vulnerability also provided access to DJI Power portable battery stations, which run on the same MQTT infrastructure, bringing the total number of exposed devices to over 10,000.<ref name="Overspill" /> The flaw was strictly limited to devices operating on the consumer DJI Home ecosystem.

=== DJI's response ===

DJI stated that it identified the vulnerability affecting DJI Home through an internal review in late January 2026 and initiated remediation immediately.<ref name="BroBible" /> The company deployed two automated patches on February 8 and February 10 to address the wildcard access issue without requiring user action.<ref name="Medium" /><ref name="RedState" />

== Consumer response ==

Consumers mocked DJI's patching timeline after learning about the incident. Users on social media noted that DJI only fixed the issue in two days after facing public embarrassment, suggesting the company had the capability to resolve the flaw much earlier.<ref name="WesternJournal">{{Cite web |author=Western Journal |date=March 27, 2026 |title=Maybe It Wasn't a Bug: Internet Weighs in After Man Discovered He Could Access 7,000 Robotic Vacuums |url=https://www.westernjournal.com/maybe-wasnt-bug-internet-weighs-man-discovered-access-7000-robotic-vacuums/ |work=Western Journal}}</ref>

The breach contributed to consumer fears regarding surveillance by foreign entities. The vulnerability was contextualized alongside ongoing litigation, such as Texas Attorney General Ken Paxton suing smart TV manufacturers over the unauthorized data collection of connected devices.<ref name="DallasExpress">{{Cite web |author=Dallas Express |date=March 4, 2026 |title=7,000 DJI Romo Robot Vacuums Hacked: Live Cameras, Floor Plans Exposed in Massive Security Flaw |url=https://dallasexpress.com/national/7000-dji-romo-robot-vacuums-hacked-live-cameras-floor-plans-exposed-in-massive-security-flaw/ |work=Dallas Express}}</ref>

== References ==

{{reflist}}

[[Category:DJI]]
[[Category:Security Vulnerability]]

DMCA Section 1201

2026-04-12T22:08:21Z

Louis: fixed vghf citation, completed accuracy audit fixes

{{#seo:
|description=Section 1201 of the DMCA makes it a federal offense to bypass digital locks on copyrighted works, blocking independent repair, security research, and digital preservation.
}}
{{main|Digital Millennium Copyright Act}}

Section 1201 of the [[Digital Millennium Copyright Act]] (17 U.S.C. § 1201) makes it a federal offense to circumvent technological protection measures (TPMs) on copyrighted works & prohibits the distribution of tools designed to do so.<ref name="statute">{{Cite web |title=17 U.S. Code § 1201 - Circumvention of copyright protection systems |url=https://www.law.cornell.edu/uscode/text/17/1201 |website=Cornell Law School |access-date=5 April 2026}}</ref> Enacted on October 28, 1998, as part of the DMCA implementing the World Intellectual Property Organization (WIPO) Internet treaties, the provision was presented to Congress as a tool to combat digital piracy.<ref name="plaw">{{Cite web |title=Public Law 105-304 - Digital Millennium Copyright Act |url=https://www.govinfo.gov/content/pkg/PLAW-105publ304/pdf/PLAW-105publ304.pdf |website=GovInfo |access-date=5 April 2026}}</ref> In practice, manufacturers have used it to block [[right to repair|independent repair]], prevent [[interoperability]] with third-party products, suppress security research, & restrict digital preservation, because any device running software can be wrapped in a TPM that Section 1201 makes illegal to bypass.<ref name="co1201">{{Cite web |title=Section 1201 of Title 17 |url=https://www.copyright.gov/1201/ |website=U.S. Copyright Office |access-date=5 April 2026}}</ref>

== Text of the statute ==

Section 1201 contains three core prohibitions & draws a legal distinction between "access controls" & "copy controls" that determines how each prohibition applies.<ref name="statute" />

'''Section 1201(a)(1)''' prohibits the ''act'' of circumventing a technological measure that controls access to a copyrighted work. The statute states: "No person shall circumvent a technological measure that effectively controls access to a work protected under this title."<ref>17 U.S.C. § 1201(a)(1)(A).</ref>

'''Section 1201(a)(2)''' prohibits trafficking in tools, products, or services primarily designed to circumvent access controls.<ref>17 U.S.C. § 1201(a)(2).</ref>

'''Section 1201(b)(1)''' prohibits trafficking in tools, products, or services primarily designed to circumvent copy controls; that is, measures protecting a copyright owner's exclusive rights to reproduce or distribute a work.<ref>17 U.S.C. § 1201(b)(1).</ref>

A critical asymmetry exists in this structure. Congress banned both the ''act'' of circumventing access controls & the ''tools'' for doing so. For copy controls, only the ''tools'' are banned; the act of circumventing a copy control is not itself a violation.<ref>17 U.S.C. § 1201(a)-(b).</ref> Congress designed this gap to preserve fair use for consumers who already had lawful access to a work. In practice, because the tools are banned under 1201(b), most consumers cannot circumvent copy controls either.

'''Access controls''' prevent unauthorized users from reaching a work: passwords on streaming services, encryption on DVDs, firmware authentication on devices. '''Copy controls''' prevent someone who already has access from reproducing or distributing the work: ebook copying restrictions, for example.<ref name="statute" />

=== Statutory exceptions ===

Congress included permanent exceptions for specific activities:<ref>17 U.S.C. § 1201(e)-(j).</ref>

* '''1201(e)''': Law enforcement & government intelligence activities
* '''1201(f)''': Reverse engineering for software interoperability (requires lawful possession of the program)
* '''1201(g)''': Good-faith encryption research
* '''1201(h)''': Protecting minors from explicit material
* '''1201(i)''': Circumventing TPMs that collect personal information without notice
* '''1201(j)''': Security testing (requires system owner authorization)

The reverse engineering exception under 1201(f) is limited to achieving interoperability with other programs.<ref>17 U.S.C. § 1201(f).</ref> The security testing exception under 1201(j) requires authorization from the system owner, which limits independent research on devices where the manufacturer controls who receives authorization.<ref>17 U.S.C. § 1201(j).</ref>

=== Penalties ===

Civil remedies under 17 U.S.C. § 1203 include injunctions, actual damages, & statutory damages of $200 to $2,500 per act of circumvention.<ref>17 U.S.C. § 1203.</ref> Courts must remit damages for nonprofit libraries & educational institutions that were unaware their conduct violated the statute.

Criminal penalties under 17 U.S.C. § 1204 apply to willful violations committed for commercial advantage or private financial gain. A first offense carries fines up to $500,000 & imprisonment up to 5 years. Repeat offenses double the maximums to $1,000,000 & 10 years.<ref>17 U.S.C. § 1204.</ref> Nonprofit libraries, archives, & educational institutions are exempt from criminal liability.

=== Fair use ===

Courts have generally held that fair use (17 U.S.C. § 107) is not a defense to a Section 1201 violation. Because 1201 creates an anti-circumvention right independent of copyright infringement, breaking a digital lock is illegal even when the underlying purpose would qualify as fair use.<ref name="corley">''Universal City Studios, Inc. v. Corley'', 273 F.3d 429, 443-44 (2d Cir. 2001).</ref>

A circuit split exists on whether Section 1201 requires a "nexus" to copyright infringement. The 2nd & 9th Circuits hold that 1201(a) creates a standalone right requiring no proof of infringement (''Corley''; ''MDY Industries v. Blizzard Entertainment'').<ref name="mdy">''MDY Industries, LLC v. Blizzard Entertainment, Inc.'', 629 F.3d 928, 950 (9th Cir. 2010).</ref> The Federal, 5th, & 6th Circuits require a showing that circumvention was tied to actual copyright infringement (''Chamberlain v. Skylink''; ''Lexmark v. Static Control''; ''MGE UPS v. GE'').<ref name="chamberlain">''Chamberlain Group, Inc. v. Skylink Technologies, Inc.'', 381 F.3d 1178, 1202 (Fed. Cir. 2004).</ref><ref>''Lexmark International, Inc. v. Static Control Components, Inc.'', 387 F.3d 522 (6th Cir. 2004).</ref><ref>''MGE UPS Systems, Inc. v. GE Consumer and Industrial, Inc.'', 612 F.3d 760 (5th Cir. 2010).</ref>

In August 2024, the D.C. Circuit rejected a First Amendment challenge to Section 1201 in ''Green v. Department of Justice'', holding that 1201 regulates conduct rather than speech & that the triennial rulemaking process is a sufficient safety valve.<ref name="green">''Green v. U.S. Department of Justice'', 111 F.4th 109 (D.C. Cir. 2024).</ref>

== Legislative history ==

The 1996 WIPO Copyright Treaty (WCT) & the WIPO Performances and Phonograms Treaty (WPPT) required signatory nations to provide legal protection against circumvention of technological protection measures.<ref>WIPO Copyright Treaty, Art. 11 (1996); WIPO Performances and Phonograms Treaty, Art. 18 (1996).</ref> The Clinton Administration championed both treaties & urged Congress to pass implementing legislation.

Rep. Howard Coble (R-NC) introduced H.R. 2281, the "WIPO Copyright Treaties Implementation Act," on July 29, 1997. Sen. Orrin Hatch (R-UT) introduced the Senate counterpart, S. 2037.<ref name="hr2281">{{Cite web |title=H.R.2281 - WIPO Copyright Treaties Implementation Act |url=https://www.congress.gov/bill/105th-congress/house-bill/2281 |website=Congress.gov |access-date=5 April 2026}}</ref> The Senate passed S. 2037 by a 99-0 roll call vote on May 14, 1998. The House passed H.R. 2281 by voice vote on August 4, 1998. President Clinton signed the bill on October 28, 1998, as Public Law 105-304.<ref name="plaw" />

During the legislative process, a coalition of 62 law professors warned Congress that the anti-circumvention provisions would create unprecedented "paracopyright" rules regulating conduct traditionally outside copyright law. Prof. Pamela Samuelson of UC Berkeley described the provisions as creating an entirely new property right, distinct from any existing right under the Copyright Act.<ref>Pamela Samuelson, ''Intellectual Property and the Digital Economy: Why the Anti-Circumvention Regulations Need to Be Revised'', 14 Berkeley Tech. L.J. 519 (1999).</ref>

The DMCA's "grand bargain" gave content creators TPM protections while granting online service providers safe harbors under Section 512. The anti-circumvention provisions have since been applied to monopolize repair markets & block interoperability well beyond their stated purpose of stopping piracy.

== Triennial rulemaking ==

Congress included a "fail-safe" mechanism in 17 U.S.C. § 1201(a)(1)(C): every three years, the U.S. Copyright Office conducts a rulemaking to grant temporary exemptions from the prohibition on circumventing access controls.<ref>17 U.S.C. § 1201(a)(1)(C).</ref>

The process begins when the Register of Copyrights issues a Notice of Inquiry. The public submits petitions, followed by multiple rounds of comments & public hearings. The Register consults the National Telecommunications and Information Administration (NTIA), then recommends exemptions to the Librarian of Congress, who issues the final rule in the Federal Register.<ref name="co1201" />

The burden of proof falls entirely on petitioners. They must demonstrate by preponderance of evidence that Section 1201 is causing or will cause a "substantial adverse effect" on noninfringing uses of a particular class of copyrighted works.<ref>17 U.S.C. § 1201(a)(1)(C).</ref>

All exemptions expire automatically after three years. Before 2018, petitioners had to rebuild the full evidentiary record from scratch every cycle. Following a 2017 Copyright Office policy study, the office introduced a simplified renewal process in 2018: if a previously granted exemption faces no meaningful opposition, it can be renewed through a shorter petition.<ref name="2018rule">83 FR 54010 (2018).</ref>

=== The tools gap ===

The most consequential limitation of the triennial rulemaking is structural. The Librarian of Congress can only exempt the ''act'' of circumvention under 1201(a)(1). The Librarian has no authority to create exemptions to the anti-trafficking provisions in 1201(a)(2) or 1201(b).<ref>17 U.S.C. § 1201(a)(1)(C)-(D).</ref>

This creates what advocates call the "tools gap." A consumer may have the legal right to jailbreak a phone or bypass DRM on a medical device, but it remains a federal crime for anyone to provide the software or service needed to perform that circumvention. Unless a consumer can write their own circumvention code, the exemption is functionally useless.<ref>17 U.S.C. § 1201(a)(1)(C)-(D) (granting exemption authority only for the act of circumvention, not for trafficking in tools).</ref>

The tools gap is why [https://bounties.fulu.org/ FULU Bounty] winners cannot share their solutions in the United States. The [https://fulu.org FULU Foundation]'s repair bounty program pays developers $20,000 to bypass software locks on bricked devices such as [[Echelon fitness firmware lockout|Echelon exercise bikes]], but distributing those tools to the public violates Section 1201.<ref>{{Cite web |last=Rossmann |first=Louis |date=30 August 2025  |title=DMCA insanity: $20,000 bounty winner can't share his solution |url=https://www.youtube.com/watch?v=66j9dsPhAjE |website=YouTube |access-date=5 April 2026}}</ref><ref>{{Cite web |last=Koebler |first=Jason |date=27 August 2025 |title=Developer Unlocks Newly Enshittified Echelon Exercise Bikes, But Can't Legally Release His Software |url=https://www.404media.co/developer-unlocks-newly-enshittified-echelon-exercise-bikes-but-cant-legally-release-his-software/ |website=404 Media |access-date=5 April 2026}}</ref>

=== Criticism of the process ===

The EFF, Public Knowledge, & the Library Copyright Alliance have described the rulemaking as broken. The process requires specialized legal counsel to argue against lobbying efforts backed by the Recording Industry Association of America (RIAA), the Entertainment Software Association (ESA), & the Motion Picture Association (MPA). Adam Eisgrau of the American Library Association called the rulemaking a "Rube Goldberg contraption."

In December 2005, the EFF published a report titled ''DMCA Triennial Rulemaking: Failing the Digital Consumer'', calling a system that requires citizens to repeatedly petition the government for permission to use their own property illegitimate. The EFF boycotted the 2006 petition cycle in protest. Sen. Ron Wyden (D-OR) has stated the process cannot keep pace with technological change.

=== Rulemaking history ===

Nine rulemaking cycles have been completed since 2000.

In '''2000''', the first cycle granted two exemptions: lists of websites blocked by filtering software & literary works protected by malfunctioning or obsolete access controls (the "obsolete dongle" exemption).<ref>65 FR 64556 (2000).</ref>

The '''second cycle (2003)''' added ebook accessibility for the print-disabled & software preservation for obsolete formats. Requests to bypass DVD region coding & skip unskippable DVD advertisements were denied.<ref>68 FR 62011 (2003).</ref>

Phone unlocking & a security testing exemption first appeared in the '''third cycle (2006)''', responding to the Sony BMG rootkit. The EFF boycotted this cycle in protest.<ref>71 FR 68472 (2006).</ref>

The '''fourth cycle (2009)''' legalized smartphone jailbreaking for the first time & expanded DVD circumvention for educational criticism.<ref>75 FR 43825 (2009).</ref>

Controversy peaked in the '''fifth cycle (2012)''', which revoked the phone unlocking exemption for phones purchased after January 2013, arguing unlocked phones were widely available. The decision triggered a White House petition with over 114,000 signatures & led to the Unlocking Consumer Choice and Wireless Competition Act of 2014.<ref>77 FR 65260 (2012).</ref> Jailbreaking was renewed for smartphones but denied for tablets & game consoles.

The '''sixth cycle (2015)''' was the broadest rulemaking to date, covering vehicle repair (with a 12-month implementation delay), security research (with "controlled environment" & "all other laws" restrictions), game preservation for dead authentication servers, & 3D printer feedstock. [[John Deere]] argued during the hearings that farmers do not own the software on their tractors but merely receive "an implied license for the life of the vehicle."<ref>80 FR 65944 (2015).</ref>

Repair rights expanded beyond vehicles in the '''seventh cycle (2018)''' to cover smartphones, home appliances, & IoT devices. Security research restrictions were loosened & game preservation was expanded.<ref name="2018rule" />

The '''eighth cycle (2021)''' granted a medical device repair exemption, allowed text & data mining for scholarly research, & removed the "all other laws" restriction on security research.<ref name="2021rule">86 FR 59627 (2021).</ref>

The '''ninth cycle (2024)''' allowed repair of commercial food preparation equipment (widely recognized as targeting the locked-down McDonald's McFlurry machines manufactured by Taylor) & access to vehicle telematics data. Remote access to preserved video games was denied after lobbying by the ESA; the Video Game History Foundation reported that 87% of classic games released before 2010 are critically endangered.<ref>{{Cite web |last=Salvador |first=Phil |date=10 July 2023 |title=Survey of the Video Game Reissue Market in the United States |url=https://gamehistory.org/87percent/ |website=Video Game History Foundation |access-date=12 April 2026}}</ref> An exemption for AI red-teaming was also denied; the Copyright Office stated that AI platform access barriers may not qualify as TPMs under Section 1201.<ref name="2024rule">89 FR 85388 (2024).</ref>

=== Key exemptions ===

'''Phone & device unlocking''' was first granted in 2006. When the Copyright Office revoked it for newly purchased phones in 2012, public backlash forced Congress to pass the Unlocking Consumer Choice and Wireless Competition Act of 2014, which restored the exemption & uniquely allowed third-party unlocking assistance; a rare carve-out of the 1201(a)(2) trafficking ban.<ref name="unlocking-act">Pub. L. 113-144, Unlocking Consumer Choice and Wireless Competition Act (2014).</ref> The exemption currently covers phones, tablets, hotspots, & wearables.<ref name="2024rule" />

'''Vehicle repair''' was first granted in 2015, delayed 12 months, & excluded emissions-related circumvention & telematics. The tools gap means farmers risk prosecution for distributing repair software even though the act of circumvention is exempted. The 2024 cycle added vehicle telematics data access.<ref>80 FR 65944 (2015); 89 FR 85388 (2024).</ref>

'''Security research''' was first granted in 2015 with restrictive conditions: research had to occur in "controlled environments" & comply with "all other laws," creating a risk that a Computer Fraud and Abuse Act (CFAA) violation could strip the DMCA exemption. Lobbying by Rapid7 & other cybersecurity groups led to the removal of the "all other laws" requirement in 2021.<ref name="2021rule" /> The permanent statutory exception under 1201(j) still requires system owner authorization.

'''Game preservation''' was first granted in 2015, allowing users to modify locally stored games to bypass dead authentication servers. Libraries & archives can jailbreak consoles for archival purposes. The Video Game History Foundation requested remote access in 2024; the ESA successfully lobbied against it.<ref name="2024rule" />

'''Medical device repair''' was first granted in 2021, allowing bypassing of software locks for diagnosis, maintenance, & repair. The Medical Imaging & Technology Alliance (MITA) sued the Library of Congress to block the exemption. The D.C. Circuit ruled in 2024 that the Library's rulemakings are subject to judicial review under the Administrative Procedure Act (APA); the District Court upheld the exemption on its merits.<ref name="mita">''MITA v. Library of Congress'', No. 23-5067 (D.C. Cir. 2024).</ref>

'''Ebook accessibility''' has been continuously granted since 2003, allowing circumvention of [[digital rights management|DRM]] for screen readers, refreshable Braille displays, & text-to-speech. The tools gap still applies: no entity can legally distribute the circumvention tools needed to make ebooks accessible.

== Court cases ==

=== Universal City Studios v. Reimerdes ===

Eight major movie studios sued Eric Corley & his publication ''2600: The Hacker Quarterly'' for posting DeCSS, a program that decrypted the Content Scramble System (CSS) on DVDs. DeCSS was originally developed by Norwegian teenager Jon Johansen to enable DVD playback on Linux, which had no licensed DVD player.<ref>''Universal City Studios, Inc. v. Reimerdes'', 111 F. Supp. 2d 294 (S.D.N.Y. 2000).</ref>

Judge Lewis Kaplan ruled that CSS was an effective access control & that DeCSS was a circumvention tool under 1201(a)(2). He issued a permanent injunction barring Corley from posting DeCSS or linking to sites hosting it. The Second Circuit affirmed in ''Universal City Studios v. Corley'' (2001), holding that fair use is not a defense to 1201 violations & that while computer code constitutes protected speech, its functional capacity subjects it to content-neutral regulation under intermediate scrutiny.<ref name="corley" />

The decision established that consumers cannot format-shift legally purchased DVDs if doing so requires breaking a digital lock.

=== Chamberlain Group v. Skylink Technologies ===

Chamberlain manufactured garage door openers with a "rolling code" security system. Skylink sold universal remotes that could operate Chamberlain doors. Chamberlain sued under 1201(a)(2), arguing Skylink's remotes circumvented an access control on copyrighted software embedded in the opener.<ref name="chamberlain" />

The Federal Circuit ruled for Skylink, holding that Section 1201 requires a "nexus" between circumvention & copyright infringement. Because consumers owned their garage doors & were authorized to open them, Skylink's remotes did not enable copyright infringement. The court held that 1201 "prohibits only forms of access that bear a reasonable relationship to the protections that the Copyright Act otherwise affords."<ref>''Chamberlain'', 381 F.3d at 1202.</ref>

The ruling protected consumers' right to buy universal remotes, replacement parts, & independent repair tools without copyright liability.

=== Lexmark International v. Static Control Components ===

Lexmark installed authentication microchips in its laser printer toner cartridges. The printer's firmware verified the chip before accepting a cartridge. Static Control Components (SCC) reverse-engineered the chip & created a compatible replacement. Lexmark sued under 1201(a)(2).<ref>''Lexmark International, Inc. v. Static Control Components, Inc.'', 387 F.3d 522 (6th Cir. 2004).</ref>

The Sixth Circuit reversed the district court, holding that Lexmark's authentication sequence did not "effectively control access" to the copyrighted programs because anyone who bought a Lexmark printer could read the code directly from its memory. The court interpreted the 1201(f) reverse engineering exception broadly.<ref>''Lexmark'', 387 F.3d at 546-47.</ref>

The Sixth Circuit's interpretation of "effectively controls access" prevented Lexmark from using Section 1201 to block compatible toner cartridge chips.<ref>''Lexmark'', 387 F.3d at 546-47.</ref>

=== MDY Industries v. Blizzard Entertainment ===

MDY created "Glider," a bot that automated gameplay in Blizzard's ''World of Warcraft''. Blizzard implemented "Warden," an anti-cheat system that detected & blocked bots. MDY modified Glider to bypass Warden, & Blizzard sued under 1201(a)(2) & 1201(b)(1).<ref name="mdy" />

The Ninth Circuit held that MDY violated 1201(a)(2) by circumventing an access control but not 1201(b)(1) because using a bot did not constitute copyright infringement. The court explicitly rejected the Federal Circuit's ''Chamberlain'' nexus requirement, ruling that 1201(a) creates a standalone right independent of traditional copyright infringement.<ref>''MDY'', 629 F.3d at 950.</ref>

This created a deep circuit split. By divorcing Section 1201 from copyright infringement, the Ninth Circuit enabled software developers to enforce End User License Agreements (EULAs) through digital locks, turning breach of contract into a federal DMCA violation.

=== United States v. Elcom Ltd. ===

ElcomSoft, a Russian company, developed the Advanced eBook Processor, which stripped DRM from Adobe ebooks. In July 2001, ElcomSoft programmer Dmitry Sklyarov presented the research at the DEF CON hacking conference in Las Vegas. At Adobe's request, the FBI arrested Sklyarov in Las Vegas.<ref name="elcom">''United States v. Elcom Ltd.'', 203 F. Supp. 2d 1111 (N.D. Cal. 2002).</ref>

Sklyarov was detained for approximately three weeks before being released on $50,000 bail on August 6, 2001. His travel was restricted to Northern California for five months until prosecutors dropped charges in December 2001 in exchange for his testimony against ElcomSoft. At trial, a federal jury acquitted ElcomSoft of all criminal charges, finding the prosecution failed to prove willfulness; the software was legal in Russia.<ref name="elcom" />

=== Green v. Department of Justice ===

Dr. Matthew Green, a Johns Hopkins cryptographer, & Dr. Andrew "bunnie" Huang, a computer scientist and inventor, challenged Section 1201's constitutionality under the First Amendment, represented by the EFF. Green wanted to publish academic work containing circumvention code; Huang wanted to release a video-remixing tool called the NeTV2.<ref name="green" />

The D.C. Circuit rejected the facial First Amendment challenge, holding that Section 1201 primarily regulates non-expressive conduct, not protected speech, & that the triennial rulemaking process acts as a sufficient safety valve. The court declined to find that First Amendment protections for fair use invalidate Section 1201.<ref>''Green'', 111 F.4th at 120-21.</ref>

Under the ruling, researchers who wish to publish circumvention-related work have no First Amendment defense & must seek protection through the triennial exemption process.<ref name="green" />

=== MITA v. Library of Congress ===

After the 2021 triennial rulemaking granted an exemption for medical device repair, the Medical Imaging & Technology Alliance (MITA) sued the Library of Congress to block it, claiming the exemption compromised patient safety & violated the Administrative Procedure Act.<ref name="mita" />

The D.C. Circuit ruled in 2024 that the Library of Congress's 1201 rulemakings are subject to judicial review under the APA. The District Court then evaluated the rule on its merits & upheld the exemption.<ref name="mita" />

The ruling confirmed that the triennial rulemaking process produces legally binding rules subject to APA review, and that the medical device repair exemption met the statutory standard.<ref name="mita" />

== Impact on consumer rights ==

Manufacturers rely on Section 1201's protections to enforce practices such as [[feature ransom]] & [[discontinuation bricking]], confident that consumers & independent technicians cannot legally bypass the software locks these practices depend on.

=== Repair ===

[[Apple]] uses software handshakes on batteries, screens, & cameras to bind replacement parts to the device's logic board through [[part pairing]]. An independent technician who installs a genuine Apple replacement part without Apple's proprietary calibration software triggers persistent warnings or loses features like FaceID & battery health monitoring. iFixit retroactively dropped the iPhone 14's repairability score from 7 to 4 because of parts pairing.<ref>{{Cite web |title=We're Retroactively Dropping the iPhone's Repairability Score |url=https://www.ifixit.com/News/82493/we-are-retroactively-dropping-the-iphones-repairability-score-en |website=iFixit |access-date=5 April 2026}}</ref>

[[John Deere]] embeds firmware locks in agricultural equipment that require proprietary diagnostic software to authorize repairs. Farmers who attempt to diagnose their own tractors are locked out, forcing them to wait for authorized technicians.<ref>{{Cite web |last=Hogg |first=Luke |date=8 January 2024 |title=How John Deere Hijacked Copyright Law To Keep You From Tinkering With Your Tractor |url=https://www.thefai.org/posts/how-john-deere-hijacked-copyright-law-to-keep-you-from-tinkering-with-your-tractor |website=Foundation for American Innovation |access-date=5 April 2026}}</ref> Some farmers have resorted to pirated Ukrainian firmware to bypass VIN-locks on Deere equipment.

The 2021 rulemaking granted a medical device repair exemption after testimony described cases where TPMs prevented equipment repairs during the COVID-19 pandemic.<ref name="2021rule" />

Powered wheelchairs using Dynamix controllers are locked with cryptographic security dongles, preventing disabled users from calibrating or repairing their own chairs. Colorado's HB22-1031, passed in 2022, addressed this by requiring manufacturers to provide repair passwords & dongles rather than requiring users to break the lock themselves.<ref>Colorado HB22-1031 (2022).</ref>

=== Security research ===

Section 1201 has a documented chilling effect on vulnerability disclosure. In 2001, Princeton Professor Edward Felten successfully bypassed the Secure Digital Music Initiative (SDMI) audio watermarking system in a public challenge. When his team attempted to publish their findings, the RIAA & Verance threatened DMCA litigation. Felten temporarily withdrew the paper & sued for a declaratory judgment; the industry backed down.

In 2015, researchers Charlie Miller & Chris Valasek demonstrated remote control of a Jeep Cherokee's brakes & transmission through a vulnerability in the Chrysler Uconnect system. They deliberately chose a target that did not require bypassing traditional DRM to avoid 1201 prosecution, but the threat prevented them from publishing research on more locked-down vehicles.

Security researcher Jay Radcliffe discovered lethal vulnerabilities in insulin pumps but was advised by legal counsel to restrict disclosure because analyzing the software required circumventing DRM. In 2002, HP threatened criminal prosecution against researchers at SNOsoft for publishing a vulnerability in HP's Tru64 UNIX operating system; public outrage forced HP to retract the threat.

In 2005, Sony BMG installed DRM on music CDs that functioned as a rootkit on users' computers, creating severe security vulnerabilities. Mark Russinovich discovered the XCP rootkit in October 2005. Princeton researcher J. Alex Halderman, who had independently studied Sony's earlier MediaMax DRM, delayed publishing his own findings for weeks while consulting lawyers, fearing that explaining how to remove the software would violate Section 1201.<ref>71 FR 68472 (2006) (the 2006 rulemaking created a specific exemption for CD security testing in response to the Sony BMG rootkit).</ref>

=== Interoperability ===

[[HP systemic DRM and firmware lockouts|HP's "Dynamic Security" firmware]] updates recognize & block third-party or refilled ink cartridges, refusing to print with non-HP cartridges.<ref>{{Cite web |last=Harding |first=Scharon |date=9 January 2024 |title=HP sued (again) for blocking third-party ink from printers, accused of monopoly |url=https://arstechnica.com/gadgets/2024/01/hp-sued-again-for-blocking-third-party-ink-from-printers-accused-of-monopoly/ |website=Ars Technica |access-date=5 April 2026}}</ref> Lexmark tried to use Section 1201 to block Static Control Components from making compatible toner cartridge chips; the Sixth Circuit rejected the claim in 2004.

In 2014, Keurig implemented an anti-counterfeiting ink scanner on Keurig 2.0 K-Cup lids. Third-party pods triggered an "Oops!" error message & the machine refused to brew.

Chamberlain, manufacturer of myQ garage door openers, shut down its public API to block integration with home automation platforms like Home Assistant. Chamberlain had previously tried to use Section 1201 against Skylink for manufacturing universal garage door remotes; the Federal Circuit rejected the claim in 2004.

=== Digital preservation ===

When game publishers shut down authentication servers, games that require online verification become permanently unplayable. Modifying a game's code to bypass the server check or emulate the server is a 1201 violation. The triennial rulemaking has granted limited exemptions for local play, but remote access for libraries & archives was denied in 2024 after ESA lobbying.<ref name="2024rule" />

Text & data mining researchers are blocked from stripping DRM on in-copyright ebooks for computational analysis. The 2021 rulemaking granted a limited exemption for scholarly research, expanded in 2024, but the restrictions skew digital humanities research toward pre-1925 public domain works.

=== Accessibility ===

Ebook publishers apply TPMs that disable text-to-speech functionality & block integration with refreshable Braille displays. The Copyright Office has granted exemptions for accessibility circumvention since 2003, but the tools gap means no entity can legally distribute accessible unlocking tools. Disabled users are, in theory, required to write their own decryption software.

When the World Wide Web Consortium (W3C) standardized DRM in web browsers through Encrypted Media Extensions (EME), it rejected a covenant that would have protected developers who bypassed EME to add closed captioning or audio description tracks. Improving video accessibility by circumventing EME remains a federal offense.

== Reform proposals ==

=== Federal legislation ===

Multiple bills have sought to reform Section 1201. None have passed.

Rep. Zoe Lofgren (D-CA) & Rep. Thomas Massie (R-KY) introduced the '''Unlocking Technology Act''' (H.R. 1892 in the 113th Congress, H.R. 1587 in the 114th). It would have made circumvention illegal only when tied to actual copyright infringement & legalized the distribution of tools for non-infringing uses. Both versions died in committee.<ref>{{Cite web |title=H.R.1892 - Unlocking Technology Act of 2013 |url=https://www.congress.gov/bill/113th-congress/house-bill/1892 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Ron Wyden (D-OR) introduced the '''Breaking Down Barriers to Innovation Act''' (S. 990, 114th Congress), with Rep. Jared Polis (D-CO) introducing the House companion H.R. 1883. It would have automatically renewed triennial exemptions & expanded protections for security research, repair, & accessibility. Both versions died in committee.<ref>{{Cite web |title=S.990 - Breaking Down Barriers to Innovation Act of 2015 |url=https://www.congress.gov/bill/114th-congress/senate-bill/990 |website=Congress.gov |access-date=5 April 2026}}</ref>

Rep. Mondaire Jones (D-NY) & Rep. Victoria Spartz (R-IN) introduced the '''Freedom to Repair Act''' (H.R. 6566, 117th Congress). It would have exempted circumvention for repair & explicitly permitted trafficking in repair tools. It died in committee.<ref>{{Cite web |title=H.R.6566 - Freedom to Repair Act |url=https://www.congress.gov/bill/117th-congress/house-bill/6566 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Thom Tillis (R-NC) & Sen. Patrick Leahy (D-VT) introduced the '''SMART Copyright Act''' (S. 3880, 117th Congress), which moved in the opposite direction: it would have strengthened TPM enforcement by mandating "Standard Technical Measures" that platforms must accommodate to retain their DMCA safe harbor. Digital rights groups & library associations opposed it. It died in committee.<ref>{{Cite web |title=S.3880 - SMART Copyright Act of 2022 |url=https://www.congress.gov/bill/117th-congress/senate-bill/3880 |website=Congress.gov |access-date=5 April 2026}}</ref>

The only legislative success was the '''Unlocking Consumer Choice and Wireless Competition Act of 2014''', which restored the phone unlocking exemption & allowed third-party unlocking assistance.<ref name="unlocking-act" />

=== State workarounds ===

State law cannot override federal copyright law, so state [[right to repair]] bills work around Section 1201 by requiring manufacturers to bypass their own locks rather than authorizing consumers to do so.

Colorado's HB22-1031 (powered wheelchairs, 2022) requires manufacturers to provide the passwords & cryptographic dongles needed for repair.<ref>Colorado HB22-1031 (2022).</ref> Oregon's SB 1596 banned [[part pairing]] entirely, prohibiting manufacturers from using software locks to disable non-OEM replacement parts; rather than authorizing circumvention, the law forces manufacturers to stop applying the TPM.

=== Executive actions ===

President Biden's July 2021 Executive Order on Promoting Competition directed the Federal Trade Commission (FTC) to draft rules preventing manufacturer repair restrictions.<ref>Executive Order 14036, ''Promoting Competition in the American Economy'' (July 9, 2021).</ref> The FTC's May 2021 ''Nixing the Fix'' report acknowledged that Section 1201 is used by manufacturers to restrict aftermarket competition & repair, & pledged enforcement under the [[Magnuson-Moss Warranty Act]].

== Industry lobbying ==

The RIAA has spent millions annually on lobbying since 1998, consistently targeting copyright enforcement legislation including Section 1201.<ref>{{Cite web |title=Recording Industry Assn of America: Lobbying Profile |url=https://www.opensecrets.org/orgs/recording-industry-assn-of-america/lobbying?id=D000000581 |website=OpenSecrets |access-date=5 April 2026}}</ref> The ESA has consistently opposed game preservation exemptions that would allow remote access to archived titles.

The Alliance for Automotive Innovation (formerly Auto Alliance) retains contract lobbyists across states to oppose [[right to repair]] legislation. During Copyright Office hearings, the Alliance argued that allowing consumers to access their own vehicles' diagnostic software could "enable rampant piracy of copyrighted works like music and films."

A documented revolving door exists between the Copyright Office & copyright industry groups. Karyn Temple went from the RIAA's litigation department to Register of Copyrights, then to General Counsel of the MPA. Maria Pallante went from Register of Copyrights to President & CEO of the Association of American Publishers. Former Senator Chris Dodd became Chairman & CEO of the MPAA shortly after leaving the Senate.

== International comparison ==

The United States exported the DMCA's anti-circumvention framework through WIPO treaties & bilateral trade agreements.


{| class="wikitable"
|-
! Country/Region !! Law !! Differences from U.S. law
|-
| European Union || InfoSoc Directive 2001/29/EC, Article 6 || EU courts allow circumvention for interoperability & software error correction
|-
| Canada || Copyright Modernization Act (2012) || Digital locks override fair dealing exceptions; Bill C-244 (introduced February 2022, passed House of Commons October 2023) aims to harmonize TPMs with repair
|-
| Australia || Copyright Act 1968 (amended 2006) || Mirrors DMCA access controls (passed for AUSFTA compliance); no prohibition on circumventing use controls
|-
| United Kingdom || Copyright, Designs and Patents Act 1988 || Post-Brexit, independent of EU directive; strict; relies on narrow "fair dealing" rather than flexible fair use
|-
| Japan || Copyright Act, Art. 120bis || Up to 3 years imprisonment & 2 million yen fine; one of the strictest regimes globally
|-
| New Zealand || Copyright (New Technologies) Amendment Act 2008 || Does not penalize the individual act of circumvention for non-infringing purposes
|}

The WIPO Copyright Treaty (Article 11) & the WIPO Performances and Phonograms Treaty (Article 18) mandate that signatory nations provide legal protection against TPM circumvention.<ref>WIPO Copyright Treaty, Art. 11 (1996).</ref> The United States-Mexico-Canada Agreement (USMCA, Chapter 20, Article 20.H.11) cements DMCA-style civil & criminal penalties into North American trade law.<ref>USMCA Chapter 20, Article 20.H.11.</ref>

== See also ==

* [[Digital Millennium Copyright Act]]
* [[Right to repair]]
* [[Right to own]]
* [[Part pairing]]
* [[Digital rights management]]
* [[Feature ransom]]
* [[Discontinuation bricking]]
* [[Planned obsolescence]]
* [[John Deere]]
* [[Apple]]

== References ==
{{reflist}}

[[Category:Legislation]]
[[Category:Digital rights management]]
[[Category:Right to repair]]

Digital Millennium Copyright Act

2026-04-12T22:08:21Z

Louis: updated google takedown numbers, completed accuracy audit fixes

{{#seo:
|description=The Digital Millennium Copyright Act (DMCA) criminalizes circumventing digital locks & creates safe harbor for platforms. Section 1201 restricts repair & security research.
}}
The '''Digital Millennium Copyright Act''' (DMCA) is a United States copyright law enacted on October 28, 1998, as Public Law 105-304.<ref name="plaw">{{Cite web |title=Public Law 105-304 - Digital Millennium Copyright Act |url=https://www.govinfo.gov/content/pkg/PLAW-105publ304/pdf/PLAW-105publ304.pdf |website=GovInfo |access-date=5 April 2026}}</ref> The statute amended Title 17 of the U.S. Code to implement two 1996 World Intellectual Property Organization (WIPO) treaties, criminalize the circumvention of [[digital rights management|digital locks]], & create safe harbor protections for online service providers.<ref name="hr2281">{{Cite web |title=H.R.2281 - Digital Millennium Copyright Act |url=https://www.congress.gov/bill/105th-congress/house-bill/2281 |website=Congress.gov |access-date=5 April 2026}}</ref> Its most controversial provision, [[DMCA Section 1201]], has been used by manufacturers to block [[right to repair|independent repair]], suppress security research, & prevent [[interoperability]] with third-party products, extending the law's reach well beyond its original anti-piracy purpose.

== Legislative history ==

The DMCA originated from the 1996 WIPO diplomatic conference in Geneva, which produced the WIPO Copyright Treaty (WCT) & the WIPO Performances and Phonograms Treaty (WPPT). Both treaties required signatory nations to provide legal protection against circumvention of technological protection measures (TPMs) on copyrighted works.<ref>WIPO Copyright Treaty, Art. 11 (1996); WIPO Performances and Phonograms Treaty, Art. 18 (1996).</ref> The Clinton Administration championed both treaties & urged Congress to pass implementing legislation, arguing that strong digital copyright protections were necessary for the growth of the digital economy.

Rep. Howard Coble (R-NC) introduced H.R. 2281, titled the "WIPO Copyright Treaties Implementation Act," on July 29, 1997. Sen. Orrin Hatch (R-UT) introduced the Senate counterpart, S. 2037.<ref name="hr2281" /> During committee hearings, a coalition of 62 law professors warned Congress that the proposed anti-circumvention rules would create unprecedented "paracopyright" regulations governing conduct traditionally outside copyright law. Prof. Pamela Samuelson of UC Berkeley described the provisions as creating an entirely new property right distinct from any existing right under the Copyright Act.<ref name="samuelson">Pamela Samuelson, ''Intellectual Property and the Digital Economy: Why the Anti-Circumvention Regulations Need to Be Revised'', 14 Berkeley Tech. L.J. 519 (1999).</ref>

The Senate passed S. 2037 by a 99-0 roll call vote on May 14, 1998. The House passed H.R. 2281 by voice vote under suspension of the rules on August 4, 1998. A conference committee reconciled the two versions, filing Conference Report 105-796 on October 8, 1998.<ref name="plaw" /> President Clinton signed the bill on October 28, 1998.

Congress intended a "grand bargain": content creators received legal protections for their digital locks, while online service providers received safe harbors shielding them from secondary liability for user-uploaded content. In practice, the anti-circumvention provisions have been used to restrict repair markets & block third-party compatibility, while the safe harbor takedown system has been used for censorship & anti-competitive purposes.

== Structure of the law ==

The DMCA contains five titles, each addressing different aspects of digital copyright.<ref name="plaw" />

=== Title I: Anti-circumvention (Section 1201) ===

{{Main|DMCA Section 1201}}

Title I added Sections 1201 & 1202 to the Copyright Act. Section 1201 prohibits circumventing TPMs that control access to copyrighted works & bans the distribution of tools designed to do so.<ref>17 U.S.C. § 1201.</ref> Section 1202 protects Copyright Management Information (CMI), making it illegal to remove or alter digital watermarks or identifying metadata with the intent to enable infringement.<ref>17 U.S.C. § 1202.</ref>

Section 1201 is the DMCA's most litigated & most criticized provision. Congress included a "fail-safe" mechanism: every three years, the U.S. Copyright Office conducts a rulemaking to grant temporary exemptions from the circumvention ban.<ref>17 U.S.C. § 1201(a)(1)(C).</ref> Nine rulemaking cycles have been completed since 2000, granting exemptions for smartphone jailbreaking, vehicle repair, medical device repair, & security research, among others. All exemptions expire automatically & must be renewed.<ref>17 U.S.C. § 1201(a)(1)(B)-(D).</ref>

The most consequential limitation is the "tools gap." The Librarian of Congress can only exempt the ''act'' of circumvention; the anti-trafficking provisions in 1201(a)(2) remain untouched. A consumer may have the legal right to bypass a software lock but no legal way to obtain the tool needed to do so.<ref>17 U.S.C. § 1201(a)(1)(C)-(D) (granting exemption authority only for the act of circumvention, not for trafficking in tools).</ref> The [https://fulu.org FULU Foundation]'s repair bounty program paid a developer $20,000 to bypass software locks on [[Echelon fitness firmware lockout|Echelon exercise bikes]], but distributing the resulting tool in the United States violates Section 1201.<ref>{{Cite web |last=Koebler |first=Jason |date=27 August 2025 |title=Developer Unlocks Newly Enshittified Echelon Exercise Bikes, But Can't Legally Release His Software |url=https://www.404media.co/developer-unlocks-newly-enshittified-echelon-exercise-bikes-but-cant-legally-release-his-software/ |website=404 Media |access-date=5 April 2026}}</ref>

=== Title II: Safe harbor (Section 512) ===

Title II created Section 512 of the Copyright Act, establishing four safe harbors for online service providers (OSPs) against copyright infringement liability.<ref name="512">17 U.S.C. § 512.</ref>

'''Section 512(a)''' protects ISPs acting as conduits for data transmission. '''Section 512(b)''' covers system caching. '''Section 512(c)''', the most frequently invoked safe harbor, protects platforms hosting user-generated content (YouTube, social media) from liability provided they lack actual knowledge of specific infringing material, receive no direct financial benefit from the infringement where they can control it, & remove content promptly upon receiving a valid notice.<ref name="512" /> '''Section 512(d)''' covers search engines & directories that link to infringing material.

To qualify for any safe harbor, an OSP must adopt & "reasonably implement" a policy for terminating repeat infringers under Section 512(i), & must register a designated agent with the Copyright Office to receive takedown notices.<ref name="512" />

==== Notice-and-takedown procedure ====

Section 512 established an extrajudicial mechanism for copyright enforcement. A copyright holder sends a written notice to the OSP's designated agent identifying the infringed work, the infringing material (usually by URL), & a statement of good faith belief that the use is unauthorized, signed under penalty of perjury.<ref name="512" /> The OSP must "expeditiously" remove the material to maintain safe harbor immunity.

The affected user may file a counter-notification, stating under penalty of perjury that the material was removed by mistake or misidentification. Once a valid counter-notice is filed, the OSP must restore the material within 10 to 14 business days unless the copyright holder files a federal lawsuit.<ref name="512" />

Section 512(f) creates liability for knowingly material misrepresentations in takedown notices or counter-notices. In practice, courts have set the bar for 512(f) claims so high that the provision provides little deterrent against fraudulent takedowns.

=== Title III: Computer maintenance ===

Title III amended Section 117 of the Copyright Act to allow making copies of a computer program during the maintenance or repair of a machine, provided the copy is made solely by activating the machine & is destroyed immediately afterward.<ref>17 U.S.C. § 117(c).</ref> Congress enacted this to overturn ''MAI Systems Corp. v. Peak Computer, Inc.'' (9th Cir. 1993), which held that loading software into RAM during computer repair constituted copyright infringement.<ref>''MAI Systems Corp. v. Peak Computer, Inc.'', 991 F.2d 511 (9th Cir. 1993).</ref>

=== Title IV: Miscellaneous provisions ===

Congress also directed the Copyright Office to study digital distance education under Title IV, which contains several amendments relevant to libraries, education, & broadcasting. That study led to the Technology, Education, and Copyright Harmonization (TEACH) Act of 2002.<ref name="plaw" /> Title IV also expanded the library & archives preservation exemption & addressed ephemeral recordings for sound recordings.

=== Title V: Vessel hull designs ===

Chapter 13 of Title 17 received a ''sui generis'' protection regime for boat hull designs under Title V.<ref name="plaw" /> It has minimal consumer rights relevance.

== Section 512 in practice ==

=== Takedown volume ===

The scale of DMCA takedowns has grown exponentially since the statute's passage. By late 2016, Google had processed 1 billion URL removal requests. As of early 2026, Google has received over 16.5 billion takedown requests, processing roughly 50 million per week.<ref name="google-transparency">{{Cite web |title=Google Transparency Report: Copyright |url=https://transparencyreport.google.com/copyright/overview |website=Google |access-date=12 April 2026}}</ref> The Lumen Database, a research project at Harvard Law School, has archived over 67 million takedown notices submitted by copyright holders across platforms.<ref name="lumen">{{Cite web |title=About Lumen |url=https://lumendatabase.org/pages/about |website=Lumen Database, Harvard Law School |access-date=12 April 2026}}</ref>

=== Takedown abuse ===

The automated & rapid nature of the system has enabled widespread abuse. Because OSPs face liability if they fail to remove content, they err on the side of takedown, creating a presumption of removal for users.

In 2009, the U.S. Chamber of Commerce filed a DMCA takedown against a parody website created by the activist group The Yes Men, temporarily disabling 400 other websites hosted on the same ISP.<ref>{{Cite web |title=U.S. Chamber of Commerce uses the DMCA to silence critic |url=https://publicknowledge.org/u-s-chamber-of-commerce-uses-the-dmca-to-silence-critic/ |website=Public Knowledge |date=27 October 2009 |access-date=5 April 2026}}</ref> Film critics & video essayists relying on fair use routinely have their YouTube accounts suspended via automated copyright strikes. Academic researchers using the Lumen Database identified nearly 34,000 coordinated fraudulent notices using backdated "fake original" URLs on dummy websites to delist legitimate news sites from search results.

YouTube's Content ID system, which goes beyond the statutory requirements of Section 512, automatically demonetizes or blocks videos without conducting fair use analysis. Small creators cannot fight claims from media conglomerates with dedicated enforcement teams. Content ID processes over 700 million claims per year.<ref name="google-transparency" />

=== Key court cases ===

Three appellate decisions define the modern scope of Section 512.

In ''Viacom International, Inc. v. YouTube, Inc.'' (2nd Cir. 2012), Viacom sued YouTube for $1 billion, alleging YouTube built its business on unauthorized hosting of Viacom's content. The Second Circuit ruled that general awareness of ubiquitous infringement on a platform does not strip safe harbor protection; a copyright holder must show the OSP had "actual knowledge" of specific infringing clips or "red flag" awareness where specific infringement was objectively obvious.<ref>''Viacom International, Inc. v. YouTube, Inc.'', 676 F.3d 19 (2d Cir. 2012).</ref>

In ''Capitol Records, LLC v. Vimeo, LLC'' (2nd Cir. 2016), the court held that Section 512(c) safe harbor applies to pre-1972 sound recordings & that Vimeo employees viewing or "liking" user-uploaded videos containing copyrighted music did not establish "red flag" knowledge.<ref>''Capitol Records, LLC v. Vimeo, LLC'', 826 F.3d 78 (2d Cir. 2016).</ref>

''BMG Rights Management v. Cox Communications'' (4th Cir. 2018) established that safe harbor requires genuine implementation of a repeat infringer policy. Cox had a 13-strike policy but never terminated paying subscribers; it routinely deleted millions of notices & blacklisted copyright monitors. The Fourth Circuit stripped Cox's safe harbor, ruling that "repeat infringers" means anyone who repeatedly infringes, not only those adjudicated liable in court.<ref>''BMG Rights Management, LLC v. Cox Communications, Inc.'', 881 F.3d 293 (4th Cir. 2018).</ref>

=== The 2020 Copyright Office study ===

After a five-year investigation, the U.S. Copyright Office released a 250-page report in May 2020 evaluating the effectiveness of Section 512.<ref name="512study">{{Cite web |title=Section 512 of Title 17: A Report of the Register of Copyrights |url=https://www.copyright.gov/policy/section512/section-512-full-report.pdf |website=U.S. Copyright Office |date=May 2020 |access-date=5 April 2026}}</ref> The Office concluded that the original balance Congress intended has been "unbalanced," overwhelmingly favoring OSPs at the expense of content creators. The burden of policing the internet for identical re-uploads falls entirely on rights holders.

The Office recommended legislative "fine-tuning" but explicitly declined to recommend European-style "notice-and-staydown" mandates or site-blocking, citing the need for additional study of "potential non-copyright implications." Recommendations included clarifying the distinction between "actual" & "red flag" knowledge, adjusting the 10-to-14-day counter-notice waiting period, & tightening eligibility requirements for repeat infringer policies.<ref name="512study" />

== Criticism ==

=== Academic criticism ===

Prof. Pamela Samuelson has argued that the DMCA's anti-circumvention provisions represent an unprecedented departure into "paracopyright," regulating conduct outside the traditional sphere of intellectual property.<ref name="samuelson" /> Legal scholars have argued that Section 512 has created a private, extrajudicial removal regime that bypasses the procedural due process inherent in the court system. Content is removed first, with the burden on the affected party to contest the removal after the fact.

=== Electronic Frontier Foundation ===

The EFF has challenged Section 1201 since the statute's passage. It argues that the anti-circumvention provisions pose "a serious threat that jeopardizes fair use," chilling free expression & security research by criminalizing the act of bypassing digital locks even for lawful purposes.<ref name="eff-dmca">{{Cite web |title=DMCA |url=https://www.eff.org/issues/dmca |website=Electronic Frontier Foundation |access-date=5 April 2026}}</ref> On Section 512, the EFF defends the existence of safe harbors as essential to the internet's functioning but criticizes the abuse of the takedown system by corporations seeking to silence speech.

=== iFixit & the Repair Association ===

For hardware repair advocates, the DMCA is a tool for corporate monopolization through software locks. Because modern devices run software, manufacturers can use Section 1201 digital locks to prevent independent shops & owners from fixing their own property. [[John Deere]] has been a prominent example: the Foundation for American Innovation documented how the company uses copyright law to prevent farmers from repairing their own tractors.<ref>{{Cite web |title=How John Deere Hijacked Copyright Law To Keep You From Tinkering With Your Tractor |url=https://www.thefai.org/posts/how-john-deere-hijacked-copyright-law-to-keep-you-from-tinkering-with-your-tractor |last=Hogg |first=Luke |date=8 January 2024 |website=Foundation for American Innovation |access-date=5 April 2026}}</ref> Kyle Wiens, CEO of iFixit, testified before the House Judiciary Subcommittee on Courts, Intellectual Property, and the Internet on July 18, 2023, describing the triennial exemption process as requiring citizens to spend tens of thousands of dollars in legal fees every three years to request permission to repair their own equipment.

=== Public Knowledge ===

Critics of the triennial rulemaking process have called it a "Rube Goldberg contraption" that cannot keep pace with technological change. Public Knowledge opposed the SMART Copyright Act, warning that giving the Copyright Office the power to mandate internet-wide upload filtering would endanger free expression & internet infrastructure.

== Reform proposals ==

=== Section 1201 reform ===

Multiple bills have sought to reform the anti-circumvention provisions. None have passed. The '''Unlocking Technology Act''' (H.R. 1892, 113th Congress; H.R. 1587, 114th Congress), introduced by Rep. Zoe Lofgren (D-CA) with Rep. Thomas Massie (R-KY) as original cosponsor, would have made circumvention illegal only when tied to actual copyright infringement & legalized distribution of tools for non-infringing uses. Both versions died in committee.<ref>{{Cite web |title=H.R.1892 - Unlocking Technology Act of 2013 |url=https://www.congress.gov/bill/113th-congress/house-bill/1892 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Ron Wyden (D-OR) introduced the '''Breaking Down Barriers to Innovation Act''' (S. 990, 114th Congress), which would have automatically renewed triennial exemptions & expanded protections for security research, repair, & accessibility. Rep. Jared Polis (D-CO) introduced a companion bill, H.R. 1883, in the House. Both died in committee.<ref>{{Cite web |title=S.990 - Breaking Down Barriers to Innovation Act of 2015 |url=https://www.congress.gov/bill/114th-congress/senate-bill/990 |website=Congress.gov |access-date=5 April 2026}}</ref>

Rep. Mondaire Jones (D-NY), with Rep. Victoria Spartz (R-IN) as original cosponsor, introduced the '''Freedom to Repair Act''' (H.R. 6566, 117th Congress), which would have exempted circumvention for repair & permitted trafficking in repair tools. It died in committee.<ref>{{Cite web |title=H.R.6566 - Freedom to Repair Act |url=https://www.congress.gov/bill/117th-congress/house-bill/6566 |website=Congress.gov |access-date=5 April 2026}}</ref>

The only legislative success has been the '''Unlocking Consumer Choice and Wireless Competition Act of 2014''', which restored the phone unlocking exemption after the Copyright Office revoked it in 2012 & uniquely allowed third-party unlocking assistance.<ref>Pub. L. 113-144, Unlocking Consumer Choice and Wireless Competition Act (2014).</ref>

=== Section 512 reform ===

The '''SMART Copyright Act''' (S. 3880, 117th Congress), introduced by Sen. Thom Tillis (R-NC) & Sen. Patrick Leahy (D-VT), moved in the opposite direction from 1201 reform bills. It would have mandated "Standard Technical Measures" that platforms must accommodate to retain safe harbor, effectively requiring government-approved upload filtering. Digital rights groups, startups, & library associations opposed it. It died in committee.<ref>{{Cite web |title=S. 3880 - SMART Copyright Act of 2022 |url=https://www.congress.gov/bill/117th-congress/senate-bill/3880 |website=Congress.gov |access-date=5 April 2026}}</ref>

The '''CASE Act''', passed on December 27, 2020, as part of the Consolidated Appropriations Act of 2021, created the Copyright Claims Board (CCB), a voluntary small-claims tribunal within the Copyright Office for copyright disputes capped at $30,000 in damages.<ref>Pub. L. 116-260, Title II, Subtitle B (Copyright Alternative in Small-Claims Enforcement Act of 2020).</ref>

=== State workarounds ===

State law cannot override federal copyright law, so state [[right to repair]] bills work around Section 1201 by requiring manufacturers to bypass their own locks rather than authorizing consumers to do so. Colorado's HB22-1031 (2022) requires powered wheelchair manufacturers to provide repair tools, passwords, & documentation needed for repair.<ref>Colorado HB22-1031 (2022).</ref> Oregon's SB 1596 banned [[part pairing]] entirely, prohibiting manufacturers from using software locks to disable non-OEM replacement parts.<ref>Oregon SB 1596 (2024).</ref>

=== Executive actions ===

President Biden's July 2021 Executive Order on Promoting Competition directed the Federal Trade Commission to draft rules preventing manufacturer repair restrictions.<ref>Executive Order 14036, ''Promoting Competition in the American Economy'' (July 9, 2021).</ref> The FTC's May 2021 ''Nixing the Fix'' report examined anti-competitive repair restrictions & noted Congressional concern about their impact on consumers' rights under the [[Magnuson-Moss Warranty Act]]. The FTC stated it "stands ready to work with lawmakers" on repair restriction enforcement.<ref>{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |url=https://www.ftc.gov/reports/nixing-fix-ftc-report-congress-repair-restrictions |website=Federal Trade Commission |date=May 2021 |access-date=5 April 2026}}</ref>

== Industry lobbying ==

The Recording Industry Association of America (RIAA) has spent millions annually on lobbying since 1998.<ref name="opensecrets">{{Cite web |title=Lobbying Profile: Recording Industry Assn of America |url=https://www.opensecrets.org/orgs/recording-industry-assn-of-america/lobbying?id=D000000581 |website=OpenSecrets |access-date=5 April 2026}}</ref> The Entertainment Software Association (ESA) reported $4.83 million in federal lobbying in 2012 & has consistently opposed game preservation exemptions that would allow remote access to archived titles.

A documented revolving door exists between the Copyright Office & copyright industry groups. Karyn Temple went from the RIAA's litigation department to Register of Copyrights, then to General Counsel of the Motion Picture Association (MPA). Maria Pallante went from Register of Copyrights to President and CEO of the Association of American Publishers. Former Senator Chris Dodd became Chairman and CEO of the MPAA after leaving the Senate.

== See also ==

* [[DMCA Section 1201]]
* [[Right to repair]]
* [[Right to own]]
* [[Part pairing]]
* [[Digital rights management]]
* [[Feature ransom]]
* [[Discontinuation bricking]]
* [[Planned obsolescence]]
* [[Magnuson-Moss Warranty Act]]

== References ==
{{reflist}}

[[Category:Legislation]]
[[Category:US legislation]]
[[Category:Digital rights management]]

Digital Millennium Copyright Act

2026-04-12T18:48:52Z

Louis: rewrote from stub; added full legislative history, all five titles, section 512 safe harbor & abuse, reform proposals, court cases, lobbying section

{{#seo:
|description=The Digital Millennium Copyright Act (DMCA) criminalizes circumventing digital locks & creates safe harbor for platforms. Section 1201 restricts repair & security research.
}}
The '''Digital Millennium Copyright Act''' (DMCA) is a United States copyright law enacted on October 28, 1998, as Public Law 105-304.<ref name="plaw">{{Cite web |title=Public Law 105-304 - Digital Millennium Copyright Act |url=https://www.govinfo.gov/content/pkg/PLAW-105publ304/pdf/PLAW-105publ304.pdf |website=GovInfo |access-date=5 April 2026}}</ref> The statute amended Title 17 of the U.S. Code to implement two 1996 World Intellectual Property Organization (WIPO) treaties, criminalize the circumvention of [[digital rights management|digital locks]], & create safe harbor protections for online service providers.<ref name="hr2281">{{Cite web |title=H.R.2281 - Digital Millennium Copyright Act |url=https://www.congress.gov/bill/105th-congress/house-bill/2281 |website=Congress.gov |access-date=5 April 2026}}</ref> Its most controversial provision, [[DMCA Section 1201]], has been used by manufacturers to block [[right to repair|independent repair]], suppress security research, & prevent [[interoperability]] with third-party products, extending the law's reach well beyond its original anti-piracy purpose.

== Legislative history ==

The DMCA originated from the 1996 WIPO diplomatic conference in Geneva, which produced the WIPO Copyright Treaty (WCT) & the WIPO Performances and Phonograms Treaty (WPPT). Both treaties required signatory nations to provide legal protection against circumvention of technological protection measures (TPMs) on copyrighted works.<ref>WIPO Copyright Treaty, Art. 11 (1996); WIPO Performances and Phonograms Treaty, Art. 18 (1996).</ref> The Clinton Administration championed both treaties & urged Congress to pass implementing legislation, arguing that strong digital copyright protections were necessary for the growth of the digital economy.

Rep. Howard Coble (R-NC) introduced H.R. 2281, titled the "WIPO Copyright Treaties Implementation Act," on July 29, 1997. Sen. Orrin Hatch (R-UT) introduced the Senate counterpart, S. 2037.<ref name="hr2281" /> During committee hearings, a coalition of 62 law professors warned Congress that the proposed anti-circumvention rules would create unprecedented "paracopyright" regulations governing conduct traditionally outside copyright law. Prof. Pamela Samuelson of UC Berkeley described the provisions as creating an entirely new property right distinct from any existing right under the Copyright Act.<ref name="samuelson">Pamela Samuelson, ''Intellectual Property and the Digital Economy: Why the Anti-Circumvention Regulations Need to Be Revised'', 14 Berkeley Tech. L.J. 519 (1999).</ref>

The Senate passed S. 2037 by a 99-0 roll call vote on May 14, 1998. The House passed H.R. 2281 by voice vote under suspension of the rules on August 4, 1998. A conference committee reconciled the two versions, filing Conference Report 105-796 on October 8, 1998.<ref name="plaw" /> President Clinton signed the bill on October 28, 1998.

Congress intended a "grand bargain": content creators received legal protections for their digital locks, while online service providers received safe harbors shielding them from secondary liability for user-uploaded content. In practice, the anti-circumvention provisions have been used to restrict repair markets & block third-party compatibility, while the safe harbor takedown system has been used for censorship & anti-competitive purposes.

== Structure of the law ==

The DMCA contains five titles, each addressing different aspects of digital copyright.<ref name="plaw" />

=== Title I: Anti-circumvention (Section 1201) ===

{{Main|DMCA Section 1201}}

Title I added Sections 1201 & 1202 to the Copyright Act. Section 1201 prohibits circumventing TPMs that control access to copyrighted works & bans the distribution of tools designed to do so.<ref>17 U.S.C. § 1201.</ref> Section 1202 protects Copyright Management Information (CMI), making it illegal to remove or alter digital watermarks or identifying metadata with the intent to enable infringement.<ref>17 U.S.C. § 1202.</ref>

Section 1201 is the DMCA's most litigated & most criticized provision. Congress included a "fail-safe" mechanism: every three years, the U.S. Copyright Office conducts a rulemaking to grant temporary exemptions from the circumvention ban.<ref>17 U.S.C. § 1201(a)(1)(C).</ref> Nine rulemaking cycles have been completed since 2000, granting exemptions for smartphone jailbreaking, vehicle repair, medical device repair, & security research, among others. All exemptions expire automatically & must be renewed.<ref>17 U.S.C. § 1201(a)(1)(B)-(D).</ref>

The most consequential limitation is the "tools gap." The Librarian of Congress can only exempt the ''act'' of circumvention; the anti-trafficking provisions in 1201(a)(2) remain untouched. A consumer may have the legal right to bypass a software lock but no legal way to obtain the tool needed to do so.<ref>17 U.S.C. § 1201(a)(1)(C)-(D) (granting exemption authority only for the act of circumvention, not for trafficking in tools).</ref> The [https://fulu.org FULU Foundation]'s repair bounty program paid a developer $20,000 to bypass software locks on [[Echelon fitness firmware lockout|Echelon exercise bikes]], but distributing the resulting tool in the United States violates Section 1201.<ref>{{Cite web |last=Koebler |first=Jason |date=27 August 2025 |title=Developer Unlocks Newly Enshittified Echelon Exercise Bikes, But Can't Legally Release His Software |url=https://www.404media.co/developer-unlocks-newly-enshittified-echelon-exercise-bikes-but-cant-legally-release-his-software/ |website=404 Media |access-date=5 April 2026}}</ref>

=== Title II: Safe harbor (Section 512) ===

Title II created Section 512 of the Copyright Act, establishing four safe harbors for online service providers (OSPs) against copyright infringement liability.<ref name="512">17 U.S.C. § 512.</ref>

'''Section 512(a)''' protects ISPs acting as conduits for data transmission. '''Section 512(b)''' covers system caching. '''Section 512(c)''', the most frequently invoked safe harbor, protects platforms hosting user-generated content (YouTube, social media) from liability provided they lack actual knowledge of specific infringing material, receive no direct financial benefit from the infringement where they can control it, & remove content promptly upon receiving a valid notice.<ref name="512" /> '''Section 512(d)''' covers search engines & directories that link to infringing material.

To qualify for any safe harbor, an OSP must adopt & "reasonably implement" a policy for terminating repeat infringers under Section 512(i), & must register a designated agent with the Copyright Office to receive takedown notices.<ref name="512" />

==== Notice-and-takedown procedure ====

Section 512 established an extrajudicial mechanism for copyright enforcement. A copyright holder sends a written notice to the OSP's designated agent identifying the infringed work, the infringing material (usually by URL), & a statement of good faith belief that the use is unauthorized, signed under penalty of perjury.<ref name="512" /> The OSP must "expeditiously" remove the material to maintain safe harbor immunity.

The affected user may file a counter-notification, stating under penalty of perjury that the material was removed by mistake or misidentification. Once a valid counter-notice is filed, the OSP must restore the material within 10 to 14 business days unless the copyright holder files a federal lawsuit.<ref name="512" />

Section 512(f) creates liability for knowingly material misrepresentations in takedown notices or counter-notices. In practice, courts have set the bar for 512(f) claims so high that the provision provides little deterrent against fraudulent takedowns.

=== Title III: Computer maintenance ===

Title III amended Section 117 of the Copyright Act to allow making copies of a computer program during the maintenance or repair of a machine, provided the copy is made solely by activating the machine & is destroyed immediately afterward.<ref>17 U.S.C. § 117(c).</ref> Congress enacted this to overturn ''MAI Systems Corp. v. Peak Computer, Inc.'' (9th Cir. 1993), which held that loading software into RAM during computer repair constituted copyright infringement.<ref>''MAI Systems Corp. v. Peak Computer, Inc.'', 991 F.2d 511 (9th Cir. 1993).</ref>

=== Title IV: Miscellaneous provisions ===

Congress also directed the Copyright Office to study digital distance education under Title IV, which contains several amendments relevant to libraries, education, & broadcasting. That study led to the Technology, Education, and Copyright Harmonization (TEACH) Act of 2002.<ref name="plaw" /> Title IV also expanded the library & archives preservation exemption & addressed ephemeral recordings for sound recordings.

=== Title V: Vessel hull designs ===

Chapter 13 of Title 17 received a ''sui generis'' protection regime for boat hull designs under Title V.<ref name="plaw" /> It has minimal consumer rights relevance.

== Section 512 in practice ==

=== Takedown volume ===

The scale of DMCA takedowns has grown exponentially since the statute's passage. By late 2016, Google had processed 1 billion URL removal requests. By November 2024, Google had received its 10 billionth takedown request, processing roughly 50 million per week.<ref name="google-transparency">{{Cite web |title=Google Transparency Report: Copyright |url=https://transparencyreport.google.com/copyright/overview |website=Google |access-date=5 April 2026}}</ref> The Lumen Database, a research project at Harvard Law School, has archived over 67 million takedown notices submitted by copyright holders across platforms.<ref name="lumen">{{Cite web |title=About Lumen |url=https://lumendatabase.org/pages/about |website=Lumen Database, Harvard Law School |access-date=5 April 2026}}</ref>

=== Takedown abuse ===

The automated & rapid nature of the system has enabled widespread abuse. Because OSPs face liability if they fail to remove content, they err on the side of takedown, creating a presumption of removal for users.

In 2009, the U.S. Chamber of Commerce filed a DMCA takedown against a parody website created by the activist group The Yes Men, temporarily disabling 400 other websites hosted on the same ISP.<ref>{{Cite web |title=U.S. Chamber of Commerce uses the DMCA to silence critic |url=https://publicknowledge.org/u-s-chamber-of-commerce-uses-the-dmca-to-silence-critic/ |website=Public Knowledge |date=27 October 2009 |access-date=5 April 2026}}</ref> Film critics & video essayists relying on fair use routinely have their YouTube accounts suspended via automated copyright strikes. Academic researchers using the Lumen Database identified nearly 34,000 coordinated fraudulent notices using backdated "fake original" URLs on dummy websites to delist legitimate news sites from search results.

YouTube's Content ID system, which goes beyond the statutory requirements of Section 512, automatically demonetizes or blocks videos without conducting fair use analysis. Small creators cannot fight claims from media conglomerates with dedicated enforcement teams. Content ID processes over 700 million claims per year.<ref name="google-transparency" />

=== Key court cases ===

Three appellate decisions define the modern scope of Section 512.

In ''Viacom International, Inc. v. YouTube, Inc.'' (2nd Cir. 2012), Viacom sued YouTube for $1 billion, alleging YouTube built its business on unauthorized hosting of Viacom's content. The Second Circuit ruled that general awareness of ubiquitous infringement on a platform does not strip safe harbor protection; a copyright holder must show the OSP had "actual knowledge" of specific infringing clips or "red flag" awareness where specific infringement was objectively obvious.<ref>''Viacom International, Inc. v. YouTube, Inc.'', 676 F.3d 19 (2d Cir. 2012).</ref>

In ''Capitol Records, LLC v. Vimeo, LLC'' (2nd Cir. 2016), the court held that Section 512(c) safe harbor applies to pre-1972 sound recordings & that Vimeo employees viewing or "liking" user-uploaded videos containing copyrighted music did not establish "red flag" knowledge.<ref>''Capitol Records, LLC v. Vimeo, LLC'', 826 F.3d 78 (2d Cir. 2016).</ref>

''BMG Rights Management v. Cox Communications'' (4th Cir. 2018) established that safe harbor requires genuine implementation of a repeat infringer policy. Cox had a 13-strike policy but never terminated paying subscribers; it routinely deleted millions of notices & blacklisted copyright monitors. The Fourth Circuit stripped Cox's safe harbor, ruling that "repeat infringers" means anyone who repeatedly infringes, not only those adjudicated liable in court.<ref>''BMG Rights Management, LLC v. Cox Communications, Inc.'', 881 F.3d 293 (4th Cir. 2018).</ref>

=== The 2020 Copyright Office study ===

After a five-year investigation, the U.S. Copyright Office released a 250-page report in May 2020 evaluating the effectiveness of Section 512.<ref name="512study">{{Cite web |title=Section 512 of Title 17: A Report of the Register of Copyrights |url=https://www.copyright.gov/policy/section512/section-512-full-report.pdf |website=U.S. Copyright Office |date=May 2020 |access-date=5 April 2026}}</ref> The Office concluded that the original balance Congress intended has been "unbalanced," overwhelmingly favoring OSPs at the expense of content creators. The burden of policing the internet for identical re-uploads falls entirely on rights holders.

The Office recommended legislative "fine-tuning" but explicitly declined to recommend European-style "notice-and-staydown" mandates or site-blocking, citing the need for additional study of "potential non-copyright implications." Recommendations included clarifying the distinction between "actual" & "red flag" knowledge, adjusting the 10-to-14-day counter-notice waiting period, & tightening eligibility requirements for repeat infringer policies.<ref name="512study" />

== Criticism ==

=== Academic criticism ===

Prof. Pamela Samuelson has argued that the DMCA's anti-circumvention provisions represent an unprecedented departure into "paracopyright," regulating conduct outside the traditional sphere of intellectual property.<ref name="samuelson" /> Legal scholars have argued that Section 512 has created a private, extrajudicial removal regime that bypasses the procedural due process inherent in the court system. Content is removed first, with the burden on the affected party to contest the removal after the fact.

=== Electronic Frontier Foundation ===

The EFF has challenged Section 1201 since the statute's passage. It argues that the anti-circumvention provisions pose "a serious threat that jeopardizes fair use," chilling free expression & security research by criminalizing the act of bypassing digital locks even for lawful purposes.<ref name="eff-dmca">{{Cite web |title=DMCA |url=https://www.eff.org/issues/dmca |website=Electronic Frontier Foundation |access-date=5 April 2026}}</ref> On Section 512, the EFF defends the existence of safe harbors as essential to the internet's functioning but criticizes the abuse of the takedown system by corporations seeking to silence speech.

=== iFixit & the Repair Association ===

For hardware repair advocates, the DMCA is a tool for corporate monopolization through software locks. Because modern devices run software, manufacturers can use Section 1201 digital locks to prevent independent shops & owners from fixing their own property. [[John Deere]] has been a prominent example: the Foundation for American Innovation documented how the company uses copyright law to prevent farmers from repairing their own tractors.<ref>{{Cite web |title=How John Deere Hijacked Copyright Law To Keep You From Tinkering With Your Tractor |url=https://www.thefai.org/posts/how-john-deere-hijacked-copyright-law-to-keep-you-from-tinkering-with-your-tractor |last=Hogg |first=Luke |date=8 January 2024 |website=Foundation for American Innovation |access-date=5 April 2026}}</ref> Kyle Wiens, CEO of iFixit, testified before the House Judiciary Subcommittee on Courts, Intellectual Property, and the Internet on July 18, 2023, describing the triennial exemption process as requiring citizens to spend tens of thousands of dollars in legal fees every three years to request permission to repair their own equipment.

=== Public Knowledge ===

Critics of the triennial rulemaking process have called it a "Rube Goldberg contraption" that cannot keep pace with technological change. Public Knowledge opposed the SMART Copyright Act, warning that giving the Copyright Office the power to mandate internet-wide upload filtering would endanger free expression & internet infrastructure.

== Reform proposals ==

=== Section 1201 reform ===

Multiple bills have sought to reform the anti-circumvention provisions. None have passed. The '''Unlocking Technology Act''' (H.R. 1892, 113th Congress; H.R. 1587, 114th Congress), introduced by Rep. Zoe Lofgren (D-CA) with Rep. Thomas Massie (R-KY) as original cosponsor, would have made circumvention illegal only when tied to actual copyright infringement & legalized distribution of tools for non-infringing uses. Both versions died in committee.<ref>{{Cite web |title=H.R.1892 - Unlocking Technology Act of 2013 |url=https://www.congress.gov/bill/113th-congress/house-bill/1892 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Ron Wyden (D-OR) introduced the '''Breaking Down Barriers to Innovation Act''' (S. 990, 114th Congress), which would have automatically renewed triennial exemptions & expanded protections for security research, repair, & accessibility. Rep. Jared Polis (D-CO) introduced a companion bill, H.R. 1883, in the House. Both died in committee.<ref>{{Cite web |title=S.990 - Breaking Down Barriers to Innovation Act of 2015 |url=https://www.congress.gov/bill/114th-congress/senate-bill/990 |website=Congress.gov |access-date=5 April 2026}}</ref>

Rep. Mondaire Jones (D-NY), with Rep. Victoria Spartz (R-IN) as original cosponsor, introduced the '''Freedom to Repair Act''' (H.R. 6566, 117th Congress), which would have exempted circumvention for repair & permitted trafficking in repair tools. It died in committee.<ref>{{Cite web |title=H.R.6566 - Freedom to Repair Act |url=https://www.congress.gov/bill/117th-congress/house-bill/6566 |website=Congress.gov |access-date=5 April 2026}}</ref>

The only legislative success has been the '''Unlocking Consumer Choice and Wireless Competition Act of 2014''', which restored the phone unlocking exemption after the Copyright Office revoked it in 2012 & uniquely allowed third-party unlocking assistance.<ref>Pub. L. 113-144, Unlocking Consumer Choice and Wireless Competition Act (2014).</ref>

=== Section 512 reform ===

The '''SMART Copyright Act''' (S. 3880, 117th Congress), introduced by Sen. Thom Tillis (R-NC) & Sen. Patrick Leahy (D-VT), moved in the opposite direction from 1201 reform bills. It would have mandated "Standard Technical Measures" that platforms must accommodate to retain safe harbor, effectively requiring government-approved upload filtering. Digital rights groups, startups, & library associations opposed it. It died in committee.<ref>{{Cite web |title=S. 3880 - SMART Copyright Act of 2022 |url=https://www.congress.gov/bill/117th-congress/senate-bill/3880 |website=Congress.gov |access-date=5 April 2026}}</ref>

The '''CASE Act''', passed on December 27, 2020, as part of the Consolidated Appropriations Act of 2021, created the Copyright Claims Board (CCB), a voluntary small-claims tribunal within the Copyright Office for copyright disputes capped at $30,000 in damages.<ref>Pub. L. 116-260, Title II, Subtitle B (Copyright Alternative in Small-Claims Enforcement Act of 2020).</ref>

=== State workarounds ===

State law cannot override federal copyright law, so state [[right to repair]] bills work around Section 1201 by requiring manufacturers to bypass their own locks rather than authorizing consumers to do so. Colorado's HB22-1031 (2022) requires powered wheelchair manufacturers to provide repair tools, passwords, & documentation needed for repair.<ref>Colorado HB22-1031 (2022).</ref> Oregon's SB 1596 banned [[part pairing]] entirely, prohibiting manufacturers from using software locks to disable non-OEM replacement parts.<ref>Oregon SB 1596 (2024).</ref>

=== Executive actions ===

President Biden's July 2021 Executive Order on Promoting Competition directed the Federal Trade Commission to draft rules preventing manufacturer repair restrictions.<ref>Executive Order 14036, ''Promoting Competition in the American Economy'' (July 9, 2021).</ref> The FTC's May 2021 ''Nixing the Fix'' report examined anti-competitive repair restrictions & noted Congressional concern about their impact on consumers' rights under the [[Magnuson-Moss Warranty Act]]. The FTC stated it "stands ready to work with lawmakers" on repair restriction enforcement.<ref>{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |url=https://www.ftc.gov/reports/nixing-fix-ftc-report-congress-repair-restrictions |website=Federal Trade Commission |date=May 2021 |access-date=5 April 2026}}</ref>

== Industry lobbying ==

The Recording Industry Association of America (RIAA) has spent millions annually on lobbying since 1998.<ref name="opensecrets">{{Cite web |title=Lobbying Profile: Recording Industry Assn of America |url=https://www.opensecrets.org/orgs/recording-industry-assn-of-america/lobbying?id=D000000581 |website=OpenSecrets |access-date=5 April 2026}}</ref> The Entertainment Software Association (ESA) reported $4.83 million in federal lobbying in 2012 & has consistently opposed game preservation exemptions that would allow remote access to archived titles.

A documented revolving door exists between the Copyright Office & copyright industry groups. Karyn Temple went from the RIAA's litigation department to Register of Copyrights, then to General Counsel of the Motion Picture Association (MPA). Maria Pallante went from Register of Copyrights to President and CEO of the Association of American Publishers. Former Senator Chris Dodd became Chairman and CEO of the MPAA after leaving the Senate.

== See also ==

* [[DMCA Section 1201]]
* [[Right to repair]]
* [[Right to own]]
* [[Part pairing]]
* [[Digital rights management]]
* [[Feature ransom]]
* [[Discontinuation bricking]]
* [[Planned obsolescence]]
* [[Magnuson-Moss Warranty Act]]

== References ==
{{reflist}}

[[Category:Legislation]]
[[Category:US legislation]]
[[Category:Digital rights management]]

DMCA Section 1201

2026-04-12T18:48:44Z

Louis: rewrote from stub; added full statute text, triennial rulemaking history, court cases, documented harms across repair/security/preservation, reform proposals, penalty structure

{{#seo:
|description=Section 1201 of the DMCA makes it a federal offense to bypass digital locks on copyrighted works, blocking independent repair, security research, and digital preservation.
}}
{{main|Digital Millennium Copyright Act}}

Section 1201 of the [[Digital Millennium Copyright Act]] (17 U.S.C. § 1201) makes it a federal offense to circumvent technological protection measures (TPMs) on copyrighted works & prohibits the distribution of tools designed to do so.<ref name="statute">{{Cite web |title=17 U.S. Code § 1201 - Circumvention of copyright protection systems |url=https://www.law.cornell.edu/uscode/text/17/1201 |website=Cornell Law School |access-date=5 April 2026}}</ref> Enacted on October 28, 1998, as part of the DMCA implementing the World Intellectual Property Organization (WIPO) Internet treaties, the provision was presented to Congress as a tool to combat digital piracy.<ref name="plaw">{{Cite web |title=Public Law 105-304 - Digital Millennium Copyright Act |url=https://www.govinfo.gov/content/pkg/PLAW-105publ304/pdf/PLAW-105publ304.pdf |website=GovInfo |access-date=5 April 2026}}</ref> In practice, manufacturers have used it to block [[right to repair|independent repair]], prevent [[interoperability]] with third-party products, suppress security research, & restrict digital preservation, because any device running software can be wrapped in a TPM that Section 1201 makes illegal to bypass.<ref name="co1201">{{Cite web |title=Section 1201 of Title 17 |url=https://www.copyright.gov/1201/ |website=U.S. Copyright Office |access-date=5 April 2026}}</ref>

== Text of the statute ==

Section 1201 contains three core prohibitions & draws a legal distinction between "access controls" & "copy controls" that determines how each prohibition applies.<ref name="statute" />

'''Section 1201(a)(1)''' prohibits the ''act'' of circumventing a technological measure that controls access to a copyrighted work. The statute states: "No person shall circumvent a technological measure that effectively controls access to a work protected under this title."<ref>17 U.S.C. § 1201(a)(1)(A).</ref>

'''Section 1201(a)(2)''' prohibits trafficking in tools, products, or services primarily designed to circumvent access controls.<ref>17 U.S.C. § 1201(a)(2).</ref>

'''Section 1201(b)(1)''' prohibits trafficking in tools, products, or services primarily designed to circumvent copy controls; that is, measures protecting a copyright owner's exclusive rights to reproduce or distribute a work.<ref>17 U.S.C. § 1201(b)(1).</ref>

A critical asymmetry exists in this structure. Congress banned both the ''act'' of circumventing access controls & the ''tools'' for doing so. For copy controls, only the ''tools'' are banned; the act of circumventing a copy control is not itself a violation.<ref>17 U.S.C. § 1201(a)-(b).</ref> Congress designed this gap to preserve fair use for consumers who already had lawful access to a work. In practice, because the tools are banned under 1201(b), most consumers cannot circumvent copy controls either.

'''Access controls''' prevent unauthorized users from reaching a work: passwords on streaming services, encryption on DVDs, firmware authentication on devices. '''Copy controls''' prevent someone who already has access from reproducing or distributing the work: ebook copying restrictions, for example.<ref name="statute" />

=== Statutory exceptions ===

Congress included permanent exceptions for specific activities:<ref>17 U.S.C. § 1201(e)-(j).</ref>

* '''1201(e)''': Law enforcement & government intelligence activities
* '''1201(f)''': Reverse engineering for software interoperability (requires lawful possession of the program)
* '''1201(g)''': Good-faith encryption research
* '''1201(h)''': Protecting minors from explicit material
* '''1201(i)''': Circumventing TPMs that collect personal information without notice
* '''1201(j)''': Security testing (requires system owner authorization)

The reverse engineering exception under 1201(f) is limited to achieving interoperability with other programs.<ref>17 U.S.C. § 1201(f).</ref> The security testing exception under 1201(j) requires authorization from the system owner, which limits independent research on devices where the manufacturer controls who receives authorization.<ref>17 U.S.C. § 1201(j).</ref>

=== Penalties ===

Civil remedies under 17 U.S.C. § 1203 include injunctions, actual damages, & statutory damages of $200 to $2,500 per act of circumvention.<ref>17 U.S.C. § 1203.</ref> Courts must remit damages for nonprofit libraries & educational institutions that were unaware their conduct violated the statute.

Criminal penalties under 17 U.S.C. § 1204 apply to willful violations committed for commercial advantage or private financial gain. A first offense carries fines up to $500,000 & imprisonment up to 5 years. Repeat offenses double the maximums to $1,000,000 & 10 years.<ref>17 U.S.C. § 1204.</ref> Nonprofit libraries, archives, & educational institutions are exempt from criminal liability.

=== Fair use ===

Courts have generally held that fair use (17 U.S.C. § 107) is not a defense to a Section 1201 violation. Because 1201 creates an anti-circumvention right independent of copyright infringement, breaking a digital lock is illegal even when the underlying purpose would qualify as fair use.<ref name="corley">''Universal City Studios, Inc. v. Corley'', 273 F.3d 429, 443-44 (2d Cir. 2001).</ref>

A circuit split exists on whether Section 1201 requires a "nexus" to copyright infringement. The 2nd & 9th Circuits hold that 1201(a) creates a standalone right requiring no proof of infringement (''Corley''; ''MDY Industries v. Blizzard Entertainment'').<ref name="mdy">''MDY Industries, LLC v. Blizzard Entertainment, Inc.'', 629 F.3d 928, 950 (9th Cir. 2010).</ref> The Federal, 5th, & 6th Circuits require a showing that circumvention was tied to actual copyright infringement (''Chamberlain v. Skylink''; ''Lexmark v. Static Control''; ''MGE UPS v. GE'').<ref name="chamberlain">''Chamberlain Group, Inc. v. Skylink Technologies, Inc.'', 381 F.3d 1178, 1202 (Fed. Cir. 2004).</ref><ref>''Lexmark International, Inc. v. Static Control Components, Inc.'', 387 F.3d 522 (6th Cir. 2004).</ref><ref>''MGE UPS Systems, Inc. v. GE Consumer and Industrial, Inc.'', 612 F.3d 760 (5th Cir. 2010).</ref>

In August 2024, the D.C. Circuit rejected a First Amendment challenge to Section 1201 in ''Green v. Department of Justice'', holding that 1201 regulates conduct rather than speech & that the triennial rulemaking process is a sufficient safety valve.<ref name="green">''Green v. U.S. Department of Justice'', 111 F.4th 109 (D.C. Cir. 2024).</ref>

== Legislative history ==

The 1996 WIPO Copyright Treaty (WCT) & the WIPO Performances and Phonograms Treaty (WPPT) required signatory nations to provide legal protection against circumvention of technological protection measures.<ref>WIPO Copyright Treaty, Art. 11 (1996); WIPO Performances and Phonograms Treaty, Art. 18 (1996).</ref> The Clinton Administration championed both treaties & urged Congress to pass implementing legislation.

Rep. Howard Coble (R-NC) introduced H.R. 2281, the "WIPO Copyright Treaties Implementation Act," on July 29, 1997. Sen. Orrin Hatch (R-UT) introduced the Senate counterpart, S. 2037.<ref name="hr2281">{{Cite web |title=H.R.2281 - WIPO Copyright Treaties Implementation Act |url=https://www.congress.gov/bill/105th-congress/house-bill/2281 |website=Congress.gov |access-date=5 April 2026}}</ref> The Senate passed S. 2037 by a 99-0 roll call vote on May 14, 1998. The House passed H.R. 2281 by voice vote on August 4, 1998. President Clinton signed the bill on October 28, 1998, as Public Law 105-304.<ref name="plaw" />

During the legislative process, a coalition of 62 law professors warned Congress that the anti-circumvention provisions would create unprecedented "paracopyright" rules regulating conduct traditionally outside copyright law. Prof. Pamela Samuelson of UC Berkeley described the provisions as creating an entirely new property right, distinct from any existing right under the Copyright Act.<ref>Pamela Samuelson, ''Intellectual Property and the Digital Economy: Why the Anti-Circumvention Regulations Need to Be Revised'', 14 Berkeley Tech. L.J. 519 (1999).</ref>

The DMCA's "grand bargain" gave content creators TPM protections while granting online service providers safe harbors under Section 512. The anti-circumvention provisions have since been applied to monopolize repair markets & block interoperability well beyond their stated purpose of stopping piracy.

== Triennial rulemaking ==

Congress included a "fail-safe" mechanism in 17 U.S.C. § 1201(a)(1)(C): every three years, the U.S. Copyright Office conducts a rulemaking to grant temporary exemptions from the prohibition on circumventing access controls.<ref>17 U.S.C. § 1201(a)(1)(C).</ref>

The process begins when the Register of Copyrights issues a Notice of Inquiry. The public submits petitions, followed by multiple rounds of comments & public hearings. The Register consults the National Telecommunications and Information Administration (NTIA), then recommends exemptions to the Librarian of Congress, who issues the final rule in the Federal Register.<ref name="co1201" />

The burden of proof falls entirely on petitioners. They must demonstrate by preponderance of evidence that Section 1201 is causing or will cause a "substantial adverse effect" on noninfringing uses of a particular class of copyrighted works.<ref>17 U.S.C. § 1201(a)(1)(C).</ref>

All exemptions expire automatically after three years. Before 2018, petitioners had to rebuild the full evidentiary record from scratch every cycle. Following a 2017 Copyright Office policy study, the office introduced a simplified renewal process in 2018: if a previously granted exemption faces no meaningful opposition, it can be renewed through a shorter petition.<ref name="2018rule">83 FR 54010 (2018).</ref>

=== The tools gap ===

The most consequential limitation of the triennial rulemaking is structural. The Librarian of Congress can only exempt the ''act'' of circumvention under 1201(a)(1). The Librarian has no authority to create exemptions to the anti-trafficking provisions in 1201(a)(2) or 1201(b).<ref>17 U.S.C. § 1201(a)(1)(C)-(D).</ref>

This creates what advocates call the "tools gap." A consumer may have the legal right to jailbreak a phone or bypass DRM on a medical device, but it remains a federal crime for anyone to provide the software or service needed to perform that circumvention. Unless a consumer can write their own circumvention code, the exemption is functionally useless.<ref>17 U.S.C. § 1201(a)(1)(C)-(D) (granting exemption authority only for the act of circumvention, not for trafficking in tools).</ref>

The tools gap is why [https://bounties.fulu.org/ FULU Bounty] winners cannot share their solutions in the United States. The [https://fulu.org FULU Foundation]'s repair bounty program pays developers $20,000 to bypass software locks on bricked devices such as [[Echelon fitness firmware lockout|Echelon exercise bikes]], but distributing those tools to the public violates Section 1201.<ref>{{Cite web |last=Rossmann |first=Louis |date=30 August 2025  |title=DMCA insanity: $20,000 bounty winner can't share his solution |url=https://www.youtube.com/watch?v=66j9dsPhAjE |website=YouTube |access-date=5 April 2026}}</ref><ref>{{Cite web |last=Koebler |first=Jason |date=27 August 2025 |title=Developer Unlocks Newly Enshittified Echelon Exercise Bikes, But Can't Legally Release His Software |url=https://www.404media.co/developer-unlocks-newly-enshittified-echelon-exercise-bikes-but-cant-legally-release-his-software/ |website=404 Media |access-date=5 April 2026}}</ref>

=== Criticism of the process ===

The EFF, Public Knowledge, & the Library Copyright Alliance have described the rulemaking as broken. The process requires specialized legal counsel to argue against lobbying efforts backed by the Recording Industry Association of America (RIAA), the Entertainment Software Association (ESA), & the Motion Picture Association (MPA). Adam Eisgrau of the American Library Association called the rulemaking a "Rube Goldberg contraption."

In December 2005, the EFF published a report titled ''DMCA Triennial Rulemaking: Failing the Digital Consumer'', calling a system that requires citizens to repeatedly petition the government for permission to use their own property illegitimate. The EFF boycotted the 2006 petition cycle in protest. Sen. Ron Wyden (D-OR) has stated the process cannot keep pace with technological change.

=== Rulemaking history ===

Nine rulemaking cycles have been completed since 2000.

In '''2000''', the first cycle granted two exemptions: lists of websites blocked by filtering software & literary works protected by malfunctioning or obsolete access controls (the "obsolete dongle" exemption).<ref>65 FR 64556 (2000).</ref>

The '''second cycle (2003)''' added ebook accessibility for the print-disabled & software preservation for obsolete formats. Requests to bypass DVD region coding & skip unskippable DVD advertisements were denied.<ref>68 FR 62011 (2003).</ref>

Phone unlocking & a security testing exemption first appeared in the '''third cycle (2006)''', responding to the Sony BMG rootkit. The EFF boycotted this cycle in protest.<ref>71 FR 68472 (2006).</ref>

The '''fourth cycle (2009)''' legalized smartphone jailbreaking for the first time & expanded DVD circumvention for educational criticism.<ref>75 FR 43825 (2009).</ref>

Controversy peaked in the '''fifth cycle (2012)''', which revoked the phone unlocking exemption for phones purchased after January 2013, arguing unlocked phones were widely available. The decision triggered a White House petition with over 114,000 signatures & led to the Unlocking Consumer Choice and Wireless Competition Act of 2014.<ref>77 FR 65260 (2012).</ref> Jailbreaking was renewed for smartphones but denied for tablets & game consoles.

The '''sixth cycle (2015)''' was the broadest rulemaking to date, covering vehicle repair (with a 12-month implementation delay), security research (with "controlled environment" & "all other laws" restrictions), game preservation for dead authentication servers, & 3D printer feedstock. [[John Deere]] argued during the hearings that farmers do not own the software on their tractors but merely receive "an implied license for the life of the vehicle."<ref>80 FR 65944 (2015).</ref>

Repair rights expanded beyond vehicles in the '''seventh cycle (2018)''' to cover smartphones, home appliances, & IoT devices. Security research restrictions were loosened & game preservation was expanded.<ref name="2018rule" />

The '''eighth cycle (2021)''' granted a medical device repair exemption, allowed text & data mining for scholarly research, & removed the "all other laws" restriction on security research.<ref name="2021rule">86 FR 59627 (2021).</ref>

The '''ninth cycle (2024)''' allowed repair of commercial food preparation equipment (widely recognized as targeting the locked-down McDonald's McFlurry machines manufactured by Taylor) & access to vehicle telematics data. Remote access to preserved video games was denied after lobbying by the ESA; the Video Game History Foundation reported that 87% of classic games released before 2010 are critically endangered.<ref name="2024rule">89 FR 85388 (2024).</ref> An exemption for AI red-teaming was also denied; the Copyright Office stated that AI platform access barriers may not qualify as TPMs under Section 1201.<ref name="2024rule" />

=== Key exemptions ===

'''Phone & device unlocking''' was first granted in 2006. When the Copyright Office revoked it for newly purchased phones in 2012, public backlash forced Congress to pass the Unlocking Consumer Choice and Wireless Competition Act of 2014, which restored the exemption & uniquely allowed third-party unlocking assistance; a rare carve-out of the 1201(a)(2) trafficking ban.<ref name="unlocking-act">Pub. L. 113-144, Unlocking Consumer Choice and Wireless Competition Act (2014).</ref> The exemption currently covers phones, tablets, hotspots, & wearables.<ref name="2024rule" />

'''Vehicle repair''' was first granted in 2015, delayed 12 months, & excluded emissions-related circumvention & telematics. The tools gap means farmers risk prosecution for distributing repair software even though the act of circumvention is exempted. The 2024 cycle added vehicle telematics data access.<ref>80 FR 65944 (2015); 89 FR 85388 (2024).</ref>

'''Security research''' was first granted in 2015 with restrictive conditions: research had to occur in "controlled environments" & comply with "all other laws," creating a risk that a Computer Fraud and Abuse Act (CFAA) violation could strip the DMCA exemption. Lobbying by Rapid7 & other cybersecurity groups led to the removal of the "all other laws" requirement in 2021.<ref name="2021rule" /> The permanent statutory exception under 1201(j) still requires system owner authorization.

'''Game preservation''' was first granted in 2015, allowing users to modify locally stored games to bypass dead authentication servers. Libraries & archives can jailbreak consoles for archival purposes. The Video Game History Foundation requested remote access in 2024; the ESA successfully lobbied against it.<ref name="2024rule" />

'''Medical device repair''' was first granted in 2021, allowing bypassing of software locks for diagnosis, maintenance, & repair. The Medical Imaging & Technology Alliance (MITA) sued the Library of Congress to block the exemption. The D.C. Circuit ruled in 2024 that the Library's rulemakings are subject to judicial review under the Administrative Procedure Act (APA); the District Court upheld the exemption on its merits.<ref name="mita">''MITA v. Library of Congress'', No. 23-5067 (D.C. Cir. 2024).</ref>

'''Ebook accessibility''' has been continuously granted since 2003, allowing circumvention of [[digital rights management|DRM]] for screen readers, refreshable Braille displays, & text-to-speech. The tools gap still applies: no entity can legally distribute the circumvention tools needed to make ebooks accessible.

== Court cases ==

=== Universal City Studios v. Reimerdes ===

Eight major movie studios sued Eric Corley & his publication ''2600: The Hacker Quarterly'' for posting DeCSS, a program that decrypted the Content Scramble System (CSS) on DVDs. DeCSS was originally developed by Norwegian teenager Jon Johansen to enable DVD playback on Linux, which had no licensed DVD player.<ref>''Universal City Studios, Inc. v. Reimerdes'', 111 F. Supp. 2d 294 (S.D.N.Y. 2000).</ref>

Judge Lewis Kaplan ruled that CSS was an effective access control & that DeCSS was a circumvention tool under 1201(a)(2). He issued a permanent injunction barring Corley from posting DeCSS or linking to sites hosting it. The Second Circuit affirmed in ''Universal City Studios v. Corley'' (2001), holding that fair use is not a defense to 1201 violations & that while computer code constitutes protected speech, its functional capacity subjects it to content-neutral regulation under intermediate scrutiny.<ref name="corley" />

The decision established that consumers cannot format-shift legally purchased DVDs if doing so requires breaking a digital lock.

=== Chamberlain Group v. Skylink Technologies ===

Chamberlain manufactured garage door openers with a "rolling code" security system. Skylink sold universal remotes that could operate Chamberlain doors. Chamberlain sued under 1201(a)(2), arguing Skylink's remotes circumvented an access control on copyrighted software embedded in the opener.<ref name="chamberlain" />

The Federal Circuit ruled for Skylink, holding that Section 1201 requires a "nexus" between circumvention & copyright infringement. Because consumers owned their garage doors & were authorized to open them, Skylink's remotes did not enable copyright infringement. The court held that 1201 "prohibits only forms of access that bear a reasonable relationship to the protections that the Copyright Act otherwise affords."<ref>''Chamberlain'', 381 F.3d at 1202.</ref>

The ruling protected consumers' right to buy universal remotes, replacement parts, & independent repair tools without copyright liability.

=== Lexmark International v. Static Control Components ===

Lexmark installed authentication microchips in its laser printer toner cartridges. The printer's firmware verified the chip before accepting a cartridge. Static Control Components (SCC) reverse-engineered the chip & created a compatible replacement. Lexmark sued under 1201(a)(2).<ref>''Lexmark International, Inc. v. Static Control Components, Inc.'', 387 F.3d 522 (6th Cir. 2004).</ref>

The Sixth Circuit reversed the district court, holding that Lexmark's authentication sequence did not "effectively control access" to the copyrighted programs because anyone who bought a Lexmark printer could read the code directly from its memory. The court interpreted the 1201(f) reverse engineering exception broadly.<ref>''Lexmark'', 387 F.3d at 546-47.</ref>

The Sixth Circuit's interpretation of "effectively controls access" prevented Lexmark from using Section 1201 to block compatible toner cartridge chips.<ref>''Lexmark'', 387 F.3d at 546-47.</ref>

=== MDY Industries v. Blizzard Entertainment ===

MDY created "Glider," a bot that automated gameplay in Blizzard's ''World of Warcraft''. Blizzard implemented "Warden," an anti-cheat system that detected & blocked bots. MDY modified Glider to bypass Warden, & Blizzard sued under 1201(a)(2) & 1201(b)(1).<ref name="mdy" />

The Ninth Circuit held that MDY violated 1201(a)(2) by circumventing an access control but not 1201(b)(1) because using a bot did not constitute copyright infringement. The court explicitly rejected the Federal Circuit's ''Chamberlain'' nexus requirement, ruling that 1201(a) creates a standalone right independent of traditional copyright infringement.<ref>''MDY'', 629 F.3d at 950.</ref>

This created a deep circuit split. By divorcing Section 1201 from copyright infringement, the Ninth Circuit enabled software developers to enforce End User License Agreements (EULAs) through digital locks, turning breach of contract into a federal DMCA violation.

=== United States v. Elcom Ltd. ===

ElcomSoft, a Russian company, developed the Advanced eBook Processor, which stripped DRM from Adobe ebooks. In July 2001, ElcomSoft programmer Dmitry Sklyarov presented the research at the DEF CON hacking conference in Las Vegas. At Adobe's request, the FBI arrested Sklyarov in Las Vegas.<ref name="elcom">''United States v. Elcom Ltd.'', 203 F. Supp. 2d 1111 (N.D. Cal. 2002).</ref>

Sklyarov was detained for approximately three weeks before being released on $50,000 bail on August 6, 2001. His travel was restricted to Northern California for five months until prosecutors dropped charges in December 2001 in exchange for his testimony against ElcomSoft. At trial, a federal jury acquitted ElcomSoft of all criminal charges, finding the prosecution failed to prove willfulness; the software was legal in Russia.<ref name="elcom" />

=== Green v. Department of Justice ===

Dr. Matthew Green, a Johns Hopkins cryptographer, & Dr. Andrew "bunnie" Huang, a computer scientist and inventor, challenged Section 1201's constitutionality under the First Amendment, represented by the EFF. Green wanted to publish academic work containing circumvention code; Huang wanted to release a video-remixing tool called the NeTV2.<ref name="green" />

The D.C. Circuit rejected the facial First Amendment challenge, holding that Section 1201 primarily regulates non-expressive conduct, not protected speech, & that the triennial rulemaking process acts as a sufficient safety valve. The court declined to find that First Amendment protections for fair use invalidate Section 1201.<ref>''Green'', 111 F.4th at 120-21.</ref>

Under the ruling, researchers who wish to publish circumvention-related work have no First Amendment defense & must seek protection through the triennial exemption process.<ref name="green" />

=== MITA v. Library of Congress ===

After the 2021 triennial rulemaking granted an exemption for medical device repair, the Medical Imaging & Technology Alliance (MITA) sued the Library of Congress to block it, claiming the exemption compromised patient safety & violated the Administrative Procedure Act.<ref name="mita" />

The D.C. Circuit ruled in 2024 that the Library of Congress's 1201 rulemakings are subject to judicial review under the APA. The District Court then evaluated the rule on its merits & upheld the exemption.<ref name="mita" />

The ruling confirmed that the triennial rulemaking process produces legally binding rules subject to APA review, and that the medical device repair exemption met the statutory standard.<ref name="mita" />

== Impact on consumer rights ==

Manufacturers rely on Section 1201's protections to enforce practices such as [[feature ransom]] & [[discontinuation bricking]], confident that consumers & independent technicians cannot legally bypass the software locks these practices depend on.

=== Repair ===

[[Apple]] uses software handshakes on batteries, screens, & cameras to bind replacement parts to the device's logic board through [[part pairing]]. An independent technician who installs a genuine Apple replacement part without Apple's proprietary calibration software triggers persistent warnings or loses features like FaceID & battery health monitoring. iFixit retroactively dropped the iPhone 14's repairability score from 7 to 4 because of parts pairing.<ref>{{Cite web |title=We're Retroactively Dropping the iPhone's Repairability Score |url=https://www.ifixit.com/News/82493/we-are-retroactively-dropping-the-iphones-repairability-score-en |website=iFixit |access-date=5 April 2026}}</ref>

[[John Deere]] embeds firmware locks in agricultural equipment that require proprietary diagnostic software to authorize repairs. Farmers who attempt to diagnose their own tractors are locked out, forcing them to wait for authorized technicians.<ref>{{Cite web |last=Hogg |first=Luke |date=8 January 2024 |title=How John Deere Hijacked Copyright Law To Keep You From Tinkering With Your Tractor |url=https://www.thefai.org/posts/how-john-deere-hijacked-copyright-law-to-keep-you-from-tinkering-with-your-tractor |website=Foundation for American Innovation |access-date=5 April 2026}}</ref> Some farmers have resorted to pirated Ukrainian firmware to bypass VIN-locks on Deere equipment.

The 2021 rulemaking granted a medical device repair exemption after testimony described cases where TPMs prevented equipment repairs during the COVID-19 pandemic.<ref name="2021rule" />

Powered wheelchairs using Dynamix controllers are locked with cryptographic security dongles, preventing disabled users from calibrating or repairing their own chairs. Colorado's HB22-1031, passed in 2022, addressed this by requiring manufacturers to provide repair passwords & dongles rather than requiring users to break the lock themselves.<ref>Colorado HB22-1031 (2022).</ref>

=== Security research ===

Section 1201 has a documented chilling effect on vulnerability disclosure. In 2001, Princeton Professor Edward Felten successfully bypassed the Secure Digital Music Initiative (SDMI) audio watermarking system in a public challenge. When his team attempted to publish their findings, the RIAA & Verance threatened DMCA litigation. Felten temporarily withdrew the paper & sued for a declaratory judgment; the industry backed down.

In 2015, researchers Charlie Miller & Chris Valasek demonstrated remote control of a Jeep Cherokee's brakes & transmission through a vulnerability in the Chrysler Uconnect system. They deliberately chose a target that did not require bypassing traditional DRM to avoid 1201 prosecution, but the threat prevented them from publishing research on more locked-down vehicles.

Security researcher Jay Radcliffe discovered lethal vulnerabilities in insulin pumps but was advised by legal counsel to restrict disclosure because analyzing the software required circumventing DRM. In 2002, HP threatened criminal prosecution against researchers at SNOsoft for publishing a vulnerability in HP's Tru64 UNIX operating system; public outrage forced HP to retract the threat.

In 2005, Sony BMG installed DRM on music CDs that functioned as a rootkit on users' computers, creating severe security vulnerabilities. Mark Russinovich discovered the XCP rootkit in October 2005. Princeton researcher J. Alex Halderman, who had independently studied Sony's earlier MediaMax DRM, delayed publishing his own findings for weeks while consulting lawyers, fearing that explaining how to remove the software would violate Section 1201.<ref>71 FR 68472 (2006) (the 2006 rulemaking created a specific exemption for CD security testing in response to the Sony BMG rootkit).</ref>

=== Interoperability ===

[[HP systemic DRM and firmware lockouts|HP's "Dynamic Security" firmware]] updates recognize & block third-party or refilled ink cartridges, refusing to print with non-HP cartridges.<ref>{{Cite web |last=Harding |first=Scharon |date=9 January 2024 |title=HP sued (again) for blocking third-party ink from printers, accused of monopoly |url=https://arstechnica.com/gadgets/2024/01/hp-sued-again-for-blocking-third-party-ink-from-printers-accused-of-monopoly/ |website=Ars Technica |access-date=5 April 2026}}</ref> Lexmark tried to use Section 1201 to block Static Control Components from making compatible toner cartridge chips; the Sixth Circuit rejected the claim in 2004.

In 2014, Keurig implemented an anti-counterfeiting ink scanner on Keurig 2.0 K-Cup lids. Third-party pods triggered an "Oops!" error message & the machine refused to brew.

Chamberlain, manufacturer of myQ garage door openers, shut down its public API to block integration with home automation platforms like Home Assistant. Chamberlain had previously tried to use Section 1201 against Skylink for manufacturing universal garage door remotes; the Federal Circuit rejected the claim in 2004.

=== Digital preservation ===

When game publishers shut down authentication servers, games that require online verification become permanently unplayable. Modifying a game's code to bypass the server check or emulate the server is a 1201 violation. The triennial rulemaking has granted limited exemptions for local play, but remote access for libraries & archives was denied in 2024 after ESA lobbying.<ref name="2024rule" />

Text & data mining researchers are blocked from stripping DRM on in-copyright ebooks for computational analysis. The 2021 rulemaking granted a limited exemption for scholarly research, expanded in 2024, but the restrictions skew digital humanities research toward pre-1925 public domain works.

=== Accessibility ===

Ebook publishers apply TPMs that disable text-to-speech functionality & block integration with refreshable Braille displays. The Copyright Office has granted exemptions for accessibility circumvention since 2003, but the tools gap means no entity can legally distribute accessible unlocking tools. Disabled users are, in theory, required to write their own decryption software.

When the World Wide Web Consortium (W3C) standardized DRM in web browsers through Encrypted Media Extensions (EME), it rejected a covenant that would have protected developers who bypassed EME to add closed captioning or audio description tracks. Improving video accessibility by circumventing EME remains a federal offense.

== Reform proposals ==

=== Federal legislation ===

Multiple bills have sought to reform Section 1201. None have passed.

Rep. Zoe Lofgren (D-CA) & Rep. Thomas Massie (R-KY) introduced the '''Unlocking Technology Act''' (H.R. 1892 in the 113th Congress, H.R. 1587 in the 114th). It would have made circumvention illegal only when tied to actual copyright infringement & legalized the distribution of tools for non-infringing uses. Both versions died in committee.<ref>{{Cite web |title=H.R.1892 - Unlocking Technology Act of 2013 |url=https://www.congress.gov/bill/113th-congress/house-bill/1892 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Ron Wyden (D-OR) introduced the '''Breaking Down Barriers to Innovation Act''' (S. 990, 114th Congress), with Rep. Jared Polis (D-CO) introducing the House companion H.R. 1883. It would have automatically renewed triennial exemptions & expanded protections for security research, repair, & accessibility. Both versions died in committee.<ref>{{Cite web |title=S.990 - Breaking Down Barriers to Innovation Act of 2015 |url=https://www.congress.gov/bill/114th-congress/senate-bill/990 |website=Congress.gov |access-date=5 April 2026}}</ref>

Rep. Mondaire Jones (D-NY) & Rep. Victoria Spartz (R-IN) introduced the '''Freedom to Repair Act''' (H.R. 6566, 117th Congress). It would have exempted circumvention for repair & explicitly permitted trafficking in repair tools. It died in committee.<ref>{{Cite web |title=H.R.6566 - Freedom to Repair Act |url=https://www.congress.gov/bill/117th-congress/house-bill/6566 |website=Congress.gov |access-date=5 April 2026}}</ref>

Sen. Thom Tillis (R-NC) & Sen. Patrick Leahy (D-VT) introduced the '''SMART Copyright Act''' (S. 3880, 117th Congress), which moved in the opposite direction: it would have strengthened TPM enforcement by mandating "Standard Technical Measures" that platforms must accommodate to retain their DMCA safe harbor. Digital rights groups & library associations opposed it. It died in committee.<ref>{{Cite web |title=S.3880 - SMART Copyright Act of 2022 |url=https://www.congress.gov/bill/117th-congress/senate-bill/3880 |website=Congress.gov |access-date=5 April 2026}}</ref>

The only legislative success was the '''Unlocking Consumer Choice and Wireless Competition Act of 2014''', which restored the phone unlocking exemption & allowed third-party unlocking assistance.<ref name="unlocking-act" />

=== State workarounds ===

State law cannot override federal copyright law, so state [[right to repair]] bills work around Section 1201 by requiring manufacturers to bypass their own locks rather than authorizing consumers to do so.

Colorado's HB22-1031 (powered wheelchairs, 2022) requires manufacturers to provide the passwords & cryptographic dongles needed for repair.<ref>Colorado HB22-1031 (2022).</ref> Oregon's SB 1596 banned [[part pairing]] entirely, prohibiting manufacturers from using software locks to disable non-OEM replacement parts; rather than authorizing circumvention, the law forces manufacturers to stop applying the TPM.

=== Executive actions ===

President Biden's July 2021 Executive Order on Promoting Competition directed the Federal Trade Commission (FTC) to draft rules preventing manufacturer repair restrictions.<ref>Executive Order 14036, ''Promoting Competition in the American Economy'' (July 9, 2021).</ref> The FTC's May 2021 ''Nixing the Fix'' report acknowledged that Section 1201 is used by manufacturers to restrict aftermarket competition & repair, & pledged enforcement under the [[Magnuson-Moss Warranty Act]].

== Industry lobbying ==

The RIAA has spent millions annually on lobbying since 1998, consistently targeting copyright enforcement legislation including Section 1201.<ref>{{Cite web |title=Recording Industry Assn of America: Lobbying Profile |url=https://www.opensecrets.org/orgs/recording-industry-assn-of-america/lobbying?id=D000000581 |website=OpenSecrets |access-date=5 April 2026}}</ref> The ESA has consistently opposed game preservation exemptions that would allow remote access to archived titles.

The Alliance for Automotive Innovation (formerly Auto Alliance) retains contract lobbyists across states to oppose [[right to repair]] legislation. During Copyright Office hearings, the Alliance argued that allowing consumers to access their own vehicles' diagnostic software could "enable rampant piracy of copyrighted works like music and films."

A documented revolving door exists between the Copyright Office & copyright industry groups. Karyn Temple went from the RIAA's litigation department to Register of Copyrights, then to General Counsel of the MPA. Maria Pallante went from Register of Copyrights to President & CEO of the Association of American Publishers. Former Senator Chris Dodd became Chairman & CEO of the MPAA shortly after leaving the Senate.

== International comparison ==

The United States exported the DMCA's anti-circumvention framework through WIPO treaties & bilateral trade agreements.


{| class="wikitable"
|-
! Country/Region !! Law !! Differences from U.S. law
|-
| European Union || InfoSoc Directive 2001/29/EC, Article 6 || EU courts allow circumvention for interoperability & software error correction
|-
| Canada || Copyright Modernization Act (2012) || Digital locks override fair dealing exceptions; Bill C-244 (introduced February 2022, passed House of Commons October 2023) aims to harmonize TPMs with repair
|-
| Australia || Copyright Act 1968 (amended 2006) || Mirrors DMCA access controls (passed for AUSFTA compliance); no prohibition on circumventing use controls
|-
| United Kingdom || Copyright, Designs and Patents Act 1988 || Post-Brexit, independent of EU directive; strict; relies on narrow "fair dealing" rather than flexible fair use
|-
| Japan || Copyright Act, Art. 120bis || Up to 3 years imprisonment & 2 million yen fine; one of the strictest regimes globally
|-
| New Zealand || Copyright (New Technologies) Amendment Act 2008 || Does not penalize the individual act of circumvention for non-infringing purposes
|}

The WIPO Copyright Treaty (Article 11) & the WIPO Performances and Phonograms Treaty (Article 18) mandate that signatory nations provide legal protection against TPM circumvention.<ref>WIPO Copyright Treaty, Art. 11 (1996).</ref> The United States-Mexico-Canada Agreement (USMCA, Chapter 20, Article 20.H.11) cements DMCA-style civil & criminal penalties into North American trade law.<ref>USMCA Chapter 20, Article 20.H.11.</ref>

== See also ==

* [[Digital Millennium Copyright Act]]
* [[Right to repair]]
* [[Right to own]]
* [[Part pairing]]
* [[Digital rights management]]
* [[Feature ransom]]
* [[Discontinuation bricking]]
* [[Planned obsolescence]]
* [[John Deere]]
* [[Apple]]

== References ==
{{reflist}}

[[Category:Legislation]]
[[Category:Digital rights management]]
[[Category:Right to repair]]

Amazon Kindle

2026-04-09T05:34:12Z

Louis: Convert new pre-2013 EOL subsection dates to American format

{{ProductLineCargo
|ArticleType=Product, Service
|Category=E-readers, Publishing
|Company=Amazon
|Description=Amazon Kindle is a product line of e-readers made by Amazon.
|InProduction=Yes
|Logo=Amazon kindle logo.png
|ReleaseYear=2007
|Website=https://amazon.com/kindle
}}

'''Amazon Kindle''' is a product line of e-readers made by '''[[Amazon]]'''.

=Consumer impact summary=
{{Ph-C-CIS}}

==Incidents==
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].

===No native support for EPUB format===
While EPUB has been the widely adopted format for digital books,<ref>{{Cite web |title=EPUB 3.3 |url=https://www.w3.org/TR/epub-33/ |url-status=live |archive-url=http://web.archive.org/web/20260128221235/https://www.w3.org/TR/epub-33/ |archive-date=28 Jan 2026|access-date=16 Mar 2025 |website=[[w3.org]]}}</ref> the Kindle e-readers do not support this format natively. That means that it is not possible to load these files directly to the e-reader (which is called {{Wplink|sideloading}}), but have to be converted first to one of the proprietary formats the Kindle uses. Books directly purchased through Amazon come with [[DRM]] restrictions.

Around 2022 it was announced that there would be an option to read these files,<ref>{{Cite web |last=Schroeder |first=Stan |date=3 May 2022 |title=Amazon's Kindle will finally support epub files |url=https://mashable.com/article/amazon-kindle-epub |url-status=live |archive-url=http://web.archive.org/web/20251018065850/https://mashable.com/article/amazon-kindle-epub |archive-date=18 Oct 2025|access-date=16 Mar 2022 |website=[[Mashable]]}}</ref> which was not through native support but via their e-mail service or dedicated app for the Kindle. Both send the file to the Kindle Cloud Library, and process the file on Amazon servers to the proprietary format.

As for the sideloading itself, newer firmware versions of Kindle e-readers only work with {{Wplink|Media Transfer Protocol|MTP}},<ref>{{Cite web |author=Nathan |date=20 Oct 2024 |title=Amazon Removed Download and Transfer Option for New Kindles |url=https://blog.the-ebook-reader.com/2024/10/20/amazon-removed-download-and-transfer-option-for-new-kindles/ |url-status=live |archive-url=http://web.archive.org/web/20251014062925/https://blog.the-ebook-reader.com/2024/10/20/amazon-removed-download-and-transfer-option-for-new-kindles/ |archive-date=14 Oct 2025|access-date=16 Mar 2025 |website=[[The Ebook Reader]]}}</ref> which led to controversy among {{Wplink|power user}}s as it disrupted existing workflow, which is to be expected. Book management software like Calibre<ref>{{Cite web |author=Kovid Goyal |date= |title=calibre - E-book management |url=https://www.calibre-ebook.com |url-status=live |archive-url=http://web.archive.org/web/20260222054742/https://calibre-ebook.com/ |archive-date=22 Feb 2026|access-date=2026-02-06 |website=}}</ref> addresses this issue, and can do the conversion of file formats locally. The recent firmware updates have caused other issues, like faster battery drain than before and a slower user experience.<ref>{{Cite web |last=Kozlowski |first=Micheal |date=20 Aug 2024 |title=The Amazon Kindle is in a state of decline |url=https://goodereader.com/blog/kindle/the-amazon-kindle-is-in-a-state-of-decline |url-status=live |archive-url=http://web.archive.org/web/20251219161317/https://goodereader.com/blog/kindle/the-amazon-kindle-is-in-a-state-of-decline |archive-date=19 Dec 2025|access-date=16 Mar 2025 |website=[[Good EReader]]}}</ref>

===Anti-repair and anti-ownership practices===
Kindle devices regularly receive bad scores in repair reviews.<ref name=":0">{{Cite web |last=Frauenheim |first=Carsten |title=Kindle 11 Repair |url=https://it.ifixit.com/Device/Kindle_11 |url-status=live |archive-url=http://web.archive.org/web/20260221125927/https://it.ifixit.com/Device/Kindle_11 |archive-date=21 Feb 2026|access-date=16 Mar 2025 |website=[[iFixit]]}}</ref><ref name=":1">{{Cite web |last=Rodriguez |first=Kris |title=Kindle Paperwhite 5 (11th Generation) Repair |url=https://ifixit.com/Device/Kindle_Paperwhite_11th_Generation |url-status=live |archive-url=http://web.archive.org/web/20251212013608/https://www.ifixit.com/Device/Kindle_Paperwhite_11th_Generation |archive-date=12 Dec 2025|access-date=16 Mar 2025 |website=[[iFixit]]}}</ref> The baseline model has a replaceable battery, but provides no official replacement parts or repair instructions, and solders the power button and usb-c port to the motherboard.<ref name=":0" /><ref name=":2">[https://www.ifixit.com/repairability/e-reader-repairability-scores e-reader repairability scores] ([http://web.archive.org/web/20251211041003/https://www.ifixit.com/repairability/e-reader-repairability-scores Archived])</ref> The paper-white model uses excessive amounts of adhesive for the battery and motherboard, which make it harder to replace the battery.<ref name=":1" /><ref name=":2" /> Most of the components of the device, most importantly the e-ink screen, are not available to the general market. Any stock for e-ink displays for these devices can rarely be found, and they usually approach the cost of the device itself, making repair uneconomical.

Kindle devices run a Linux distribution, however the bootloader is locked down and users have had trouble accessing debug ports on newer hardware.{{Citation needed|reason=Personal account}} Adding to this, Amazon relies on proprietary software and drivers which make it difficult to port a standard mainline Linux kernel onto their devices.{{Citation needed|date=30 Nov 2025}}

===Download feature removed for purchased books (''2025'')===
{{Main|Amazon Kindle removes download feature of purchased books}}
[[File:Amazon removal notice of download-transfer.webp|alt=Amazon notice about removing download capability|thumb|Amazon notice about removing download capability.<ref name=":03">{{Cite web |date=12 Feb 2025 |title=FYI Amazon is removing Download & Transfer option on Feb 26th |url=https://www.reddit.com/r/kindle/comments/1inr9uy/fyi_amazon_is_removing_download_transfer_option/ |archive-url=http://web.archive.org/web/20250804001513/https://old.reddit.com/r/kindle/comments/1inr9uy/fyi_amazon_is_removing_download_transfer_option/ |archive-date=4 Aug 2025|publisher=Reddit |language=en |format=forum thread}}</ref>]]
On 26 February 2025, [[Amazon]] removed the "download and transfer via USB" feature from their website. This means [[Amazon Kindle]] users are no longer able to download their purchased e-books from Amazon's website to their computers using the "download and transfer via USB" feature. A message describing this change appeared on the page for the download feature a few weeks before the feature was removed.

===Support discontinued for pre-2013 devices===
{{Main|Amazon Kindle discontinues support for pre-2013 devices}}
On April 7, 2026, Amazon began emailing customers that, starting May 20, 2026, the Kindle Store would no longer support nine pre-2013 Kindle e-reader models and four Kindle Fire tablet models, ending the ability to purchase, borrow, or download new content on the affected hardware.<ref name="kindle2026-pcmag">{{Cite web |last=Kan |first=Michael |title=Got a Kindle From Before 2013? Amazon Is Pulling Support |url=https://www.pcmag.com/news/got-a-kindle-from-before-2013-amazon-is-pulling-support |website=PCMag |date=April 7, 2026 |access-date=April 8, 2026}}</ref><ref name="kindle2026-register">{{Cite web |last=Kunert |first=Paul |title=Amazon rewards loyal Kindle devotees by closing the book on old e-readers |url=https://www.theregister.com/2026/04/08/amazon_kindle_support_discontinued/ |website=The Register |date=April 8, 2026 |access-date=April 8, 2026}}</ref> Amazon's email warned that any affected device deregistered or factory-reset after the cutoff cannot be re-registered and cannot be used "in any way."<ref name="kindle2026-pcmag" /><ref name="kindle2026-register" /> Amazon's only on-record justification was that the affected models had been supported "for at least 14 years, some as long as 18 years" and that "technology has come a long way," with no specific technical reason cited; the company offered affected owners a 20% discount on select new Kindle devices plus an eBook credit, valid through June 20, 2026.<ref name="kindle2026-pcmag" /><ref name="kindle2026-bgr">{{Cite web |last=Sayers |first=Jonathan |title=Amazon Is Discontinuing Support For These Older Kindle Models |url=https://www.bgr.com/2143389/amazon-discontinued-support-older-kindle-models/ |website=BGR |date=April 8, 2026 |access-date=April 8, 2026}}</ref>

==Products==
{{Ph-C-P}}

==See also==
*[[Amazon alters the content of purchased ebooks]]

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:Products]]
[[Category:Amazon]]

Amazon Kindle discontinues support for pre-2013 devices

2026-04-09T05:34:01Z

Louis: Replace Wikipedia citations with Amazon press releases; convert dates to American format; fix Kindle Touch ship date (was incorrectly Nov 15, actually Nov 21 per Amazon)

{{IncidentCargo
|Company=Amazon
|StartDate=2026-04-07
|EndDate=
|Status=Active
|ProductLine=Amazon Kindle
|Product=
|ArticleType=Product
|Type=Planned Obsolescence,Digital Ownership,Right to Repair
|Description=Amazon will disable Kindle Store access on 13 pre-2013 Kindle devices on May 20, 2026; factory reset becomes a one-way brick.
}}

On May 20, 2026, [[Amazon]] will disable [[Amazon Kindle|Kindle Store]] access on thirteen Kindle devices released between 2007 and 2012, preventing owners of those devices from buying, borrowing, or downloading new content on the hardware.<ref name="pcmag-kan-20260407">{{Cite web |last=Kan |first=Michael |title=Got a Kindle From Before 2013? Amazon Is Pulling Support |url=https://www.pcmag.com/news/got-a-kindle-from-before-2013-amazon-is-pulling-support |website=PCMag |date=April 7, 2026 |access-date=April 8, 2026}}</ref><ref name="register-kunert-20260408">{{Cite web |last=Kunert |first=Paul |title=Amazon rewards loyal Kindle devotees by closing the book on old e-readers |url=https://www.theregister.com/2026/04/08/amazon_kindle_support_discontinued/ |website=The Register |date=April 8, 2026 |access-date=April 8, 2026}}</ref> Amazon notified affected customers by email beginning April 7, 2026 and warned that any device deregistered or factory-reset after the cutoff cannot be re-registered and cannot be used "in any way."<ref name="pcmag-kan-20260407" /><ref name="register-kunert-20260408" /> The shutdown covers nine e-reader models and four Kindle Fire tablet models.<ref name="pcmag-kan-20260407" /><ref name="register-kunert-20260408" /><ref name="goodereader-kozlowski-20260408">{{Cite web |last=Kozlowski |first=Michael |title=You can no longer buy e-books on Amazon Kindle made in 2012 or earlier |url=https://goodereader.com/blog/kindle/you-can-no-longer-buy-e-books-on-amazon-kindles-2012-and-earlier |website=Good e-Reader |date=April 8, 2026 |access-date=April 8, 2026}}</ref>

==Background==

Amazon launched the first Kindle e-reader on November 19, 2007.<ref name="amazon-kindle-2007">{{Cite web |title=Introducing Amazon Kindle |url=https://press.aboutamazon.com/2007/11/introducing-amazon-kindle |website=Amazon Press Center |publisher=Amazon.com |date=November 19, 2007 |access-date=April 9, 2026}}</ref> The last two pre-2013 Kindle e-readers, the Kindle Paperwhite 1st Generation and the entry-level Kindle (the "Latest Generation Kindle," internally the fifth-generation Kindle), were both announced on September 6, 2012, with the Paperwhite priced at $119 for the Wi-Fi model and $179 for the Wi-Fi + 3G model at launch.<ref name="amazon-paperwhite-2012">{{Cite web |title=Introducing the New Kindle Paperwhite, the Most Advanced E-Reader Ever Constructed |url=https://press.aboutamazon.com/2012/9/introducing-the-new-kindle-paperwhite-the-most-advanced-e-reader-ever-constructed |website=Amazon Press Center |publisher=Amazon.com |date=September 6, 2012 |access-date=April 8, 2026}}</ref>

Several pre-2013 Kindles originally shipped with "Whispernet," Amazon's branding for the built-in 3G cellular link that allowed device registration and book delivery without Wi-Fi. Amazon retired the Whispernet brand name in June 2021, replacing it with generic "WAN" terminology in product descriptions, coinciding with the planned shutdown of global 3G infrastructure.<ref name="goodereader-whispernet-2021">{{Cite web |last=Kozlowski |first=Michael |title=Amazon Whispernet branding has been retired |url=https://goodereader.com/blog/kindle/amazon-whispernet-branding-has-been-retired |website=Good e-Reader |date=June 16, 2021 |access-date=April 8, 2026}}</ref> According to the Bipartisan Policy Center, AT&T completed its 3G shutdown on February 22, 2022, Verizon on December 31, 2022, and Sprint and T-Mobile completed their 3G shutdowns later in 2022.<ref name="bpc-3g-sunset-2022">{{Cite web |title=3G Sunsetting and the Digital Divide |url=https://bipartisanpolicy.org/explainer/3g-sunsetting-and-the-digital-divide/ |website=Bipartisan Policy Center |date=March 21, 2022 |access-date=April 8, 2026}}</ref> Those carrier shutdowns ended cellular Kindle Store access on affected 3G-equipped models years before the May 2026 Amazon-side shutdown; the 2026 EOL is a separate, Amazon-initiated event covering Wi-Fi-only and Wi-Fi + 3G variants alike.

The Kindle product line has been the subject of prior Amazon-initiated feature removals; see [[Amazon Kindle removes download feature of purchased books]].

==Announcement and scope==

Michael Kan of PCMag published an early English-language report on the notice on April 7, 2026, based on a Kindle owner in Australia who had received the email.<ref name="pcmag-kan-20260407" /> Coverage from The Register, Engadget, TechCrunch, Good e-Reader, BGR, and The eBook Reader Blog followed on April 8, 2026.<ref name="register-kunert-20260408" /><ref name="engadget-moon-20260408">{{Cite web |last=Moon |first=Mariella |title=Amazon is cutting off support for older Kindles |url=https://www.engadget.com/mobile/amazon-is-cutting-off-support-for-older-kindles-115653205.html |website=Engadget |date=April 8, 2026 |access-date=April 8, 2026}}</ref><ref name="techcrunch-forristal-20260408">{{Cite web |last=Forristal |first=Lauren |title=Amazon to end support for older Kindle devices |url=https://techcrunch.com/2026/04/08/amazon-to-end-support-for-older-kindle-devices-2012/ |website=TechCrunch |date=April 8, 2026 |access-date=April 8, 2026}}</ref><ref name="goodereader-kozlowski-20260408" /><ref name="bgr-sayers-20260408">{{Cite web |last=Sayers |first=Jonathan |title=Amazon Is Discontinuing Support For These Older Kindle Models |url=https://www.bgr.com/2143389/amazon-discontinued-support-older-kindle-models/ |website=BGR |date=April 8, 2026 |access-date=April 8, 2026}}</ref><ref name="theebookreader-groezinger-20260408">{{Cite web |last=Groezinger |first=Nathan |title=Amazon Ending Support for All Kindles Released Before 2013 |url=https://blog.the-ebook-reader.com/2026/04/08/amazon-ending-support-for-all-kindles-released-before-2013/ |website=The eBook Reader Blog |date=April 8, 2026 |access-date=April 8, 2026}}</ref>

The Amazon email tells affected owners that starting May 20, 2026, the company is "discontinuing support for Kindle devices released in 2012 or earlier."<ref name="pcmag-kan-20260407" /><ref name="register-kunert-20260408" /> Amazon's only on-record justification, quoted in PCMag and Engadget, is that the affected "models have been supported for at least 14 years, some as long as 18 years" and that "technology has come a long way."<ref name="pcmag-kan-20260407" /><ref name="engadget-moon-20260408" /> BGR's Jonathan Sayers noted that "no official reason was given" beyond the age of the devices; Amazon has not cited a TLS deprecation, certificate expiry, 3G carrier sunset, security-protocol change, or cost justification.<ref name="bgr-sayers-20260408" />

The nine affected e-reader models, with launch dates:

* Kindle (1st Generation), November 19, 2007<ref name="amazon-kindle-2007" />
* Kindle (2nd Generation), February 23, 2009<ref name="amazon-kindle2-ships-2009">{{Cite web |title=Kindle 2 Ships Today |url=https://press.aboutamazon.com/news-releases/news-release-details/kindle-2-ships-today/ |website=Amazon Press Center |publisher=Amazon.com |date=February 23, 2009 |access-date=April 9, 2026}}</ref>
* Kindle DX, May 6, 2009 (announcement)<ref name="amazon-kindle-dx-2009">{{Cite web |title=Introducing Kindle DX, Amazon's Large-Screen Addition to the Kindle Family of Wireless Reading Devices |url=https://press.aboutamazon.com/2009/5/introducing-kindle-dx-amazons-large-screen-addition-to-the-kindle-family-of-wireless-reading-devices |website=Amazon Press Center |publisher=Amazon.com |date=May 6, 2009 |access-date=April 9, 2026}}</ref>
* Kindle DX Graphite, July 1, 2010<ref name="amazon-kindle-dx-graphite-2010">{{Cite web |title=Amazon Introduces New Kindle DX with 50 Percent Better Display Contrast and New Lower Price of $379 |url=https://press.aboutamazon.com/2010/7/amazon-introduces-new-kindle-dx-with-50-percent-better-display-contrast-and-new-lower-price-of-379 |website=Amazon Press Center |publisher=Amazon.com |date=July 1, 2010 |access-date=April 9, 2026}}</ref>
* Kindle Keyboard (3rd Generation), August 27, 2010<ref name="amazon-kindle-keyboard-2010">{{Cite web |title=Announcing a New Generation of Kindle: The All-New Kindle Is Smaller, Lighter, and Faster with 50 Percent Better Contrast |url=https://press.aboutamazon.com/2010/7/announcing-a-new-generation-of-kindle-the-all-new-kindle-is-smaller-lighter-and-faster-with-50-percent-better-contrast |website=Amazon Press Center |publisher=Amazon.com |date=July 28, 2010 |access-date=April 9, 2026}}</ref>
* Kindle 4, September 28, 2011<ref name="amazon-kindle-family-2011">{{Cite web |title=Introducing the All-New Kindle Family: Four New Kindles, Four Amazing Price Points |url=https://press.aboutamazon.com/2011/9/introducing-the-all-new-kindle-family-four-new-kindles-four-amazing-price-points |website=Amazon Press Center |publisher=Amazon.com |date=September 28, 2011 |access-date=April 9, 2026}}</ref>
* Kindle Touch, November 21, 2011<ref name="amazon-kindle-family-2011" />
* Kindle 5 ("Latest Generation Kindle"), September 6, 2012<ref name="amazon-paperwhite-2012" />
* Kindle Paperwhite 1st Generation, October 1, 2012<ref name="amazon-paperwhite-2012" />

The four affected Kindle Fire tablet models, confirmed as in scope by PCMag and Good e-Reader:<ref name="pcmag-kan-20260407" /><ref name="goodereader-kozlowski-20260408" />

* Kindle Fire 1st Generation, November 15, 2011<ref name="amazon-kindle-family-2011" />
* Kindle Fire 2nd Generation, September 14, 2012<ref name="amazon-kindle-fire-hd-2012">{{Cite web |title=Amazon Takes on the High-End, Introducing the New Kindle Fire HD Family |url=https://press.aboutamazon.com/2012/9/amazon-takes-on-the-high-end-introducing-the-new-kindle-fire-hd-family |website=Amazon Press Center |publisher=Amazon.com |date=September 6, 2012 |access-date=April 9, 2026}}</ref>
* Kindle Fire HD 7, September 14, 2012<ref name="amazon-kindle-fire-hd-2012" />
* Kindle Fire HD 8.9, November 20, 2012<ref name="amazon-kindle-fire-hd-2012" />

==Impact on affected devices==

After May 20, 2026, owners of affected Kindles and Kindle Fire tablets will no longer be able to "purchase, borrow, or download new content" on the hardware; previously downloaded books remain readable on the device.<ref name="register-kunert-20260408" /><ref name="pcmag-kan-20260407" />

Amazon's email to affected customers includes a warning that "if you deregister or factory reset these devices, you will not be able to re-register or use these devices in any way," quoted verbatim by PCMag, Engadget, Good e-Reader, and BGR.<ref name="pcmag-kan-20260407" /><ref name="engadget-moon-20260408" /><ref name="goodereader-kozlowski-20260408" /><ref name="bgr-sayers-20260408" /> PCMag reported that affected customer accounts and Kindle libraries remain accessible through the free Kindle app and Kindle for Web, meaning the purchased ebook library itself is not lost; the hardware binding is.<ref name="pcmag-kan-20260407" />

==Amazon's response==

Amazon's direct statement to press coverage was limited to the age-of-hardware justification quoted above.<ref name="pcmag-kan-20260407" /><ref name="engadget-moon-20260408" /> In parallel with the shutdown notice, Amazon offered affected owners a 20% discount on select new Kindle devices plus a $20 eBook credit automatically added to the customer account after a qualifying new-device purchase, valid through June 20, 2026 at 11:59pm.<ref name="pcmag-kan-20260407" /><ref name="bgr-sayers-20260408" /><ref name="goodereader-kozlowski-20260408" />

==Consumer response==

PCMag's Michael Kan reported that the story first surfaced after a user in Australia reported receiving the customer email.<ref name="pcmag-kan-20260407" /> BGR's Jonathan Sayers noted that "no official reason was given" by Amazon beyond the age of the devices.<ref name="bgr-sayers-20260408" />

==See also==
*[[Amazon]]
*[[Amazon Kindle]]
*[[Amazon Kindle removes download feature of purchased books]]
*[[Amazon alters the content of purchased ebooks]]

==References==
{{Reflist}}

[[Category:Amazon]]
[[Category:Amazon Kindle]]
[[Category:Planned Obsolescence]]
[[Category:Digital Rights Management]]
[[Category:Right to Repair]]
[[Category:2026 incidents]]

Amazon Kindle

2026-04-09T05:14:36Z

Louis: Add Support discontinued for pre-2013 devices subsection with link to Amazon Kindle discontinues support for pre-2013 devices

{{ProductLineCargo
|ArticleType=Product, Service
|Category=E-readers, Publishing
|Company=Amazon
|Description=Amazon Kindle is a product line of e-readers made by Amazon.
|InProduction=Yes
|Logo=Amazon kindle logo.png
|ReleaseYear=2007
|Website=https://amazon.com/kindle
}}

'''Amazon Kindle''' is a product line of e-readers made by '''[[Amazon]]'''.

=Consumer impact summary=
{{Ph-C-CIS}}

==Incidents==
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].

===No native support for EPUB format===
While EPUB has been the widely adopted format for digital books,<ref>{{Cite web |title=EPUB 3.3 |url=https://www.w3.org/TR/epub-33/ |url-status=live |archive-url=http://web.archive.org/web/20260128221235/https://www.w3.org/TR/epub-33/ |archive-date=28 Jan 2026|access-date=16 Mar 2025 |website=[[w3.org]]}}</ref> the Kindle e-readers do not support this format natively. That means that it is not possible to load these files directly to the e-reader (which is called {{Wplink|sideloading}}), but have to be converted first to one of the proprietary formats the Kindle uses. Books directly purchased through Amazon come with [[DRM]] restrictions.

Around 2022 it was announced that there would be an option to read these files,<ref>{{Cite web |last=Schroeder |first=Stan |date=3 May 2022 |title=Amazon's Kindle will finally support epub files |url=https://mashable.com/article/amazon-kindle-epub |url-status=live |archive-url=http://web.archive.org/web/20251018065850/https://mashable.com/article/amazon-kindle-epub |archive-date=18 Oct 2025|access-date=16 Mar 2022 |website=[[Mashable]]}}</ref> which was not through native support but via their e-mail service or dedicated app for the Kindle. Both send the file to the Kindle Cloud Library, and process the file on Amazon servers to the proprietary format.

As for the sideloading itself, newer firmware versions of Kindle e-readers only work with {{Wplink|Media Transfer Protocol|MTP}},<ref>{{Cite web |author=Nathan |date=20 Oct 2024 |title=Amazon Removed Download and Transfer Option for New Kindles |url=https://blog.the-ebook-reader.com/2024/10/20/amazon-removed-download-and-transfer-option-for-new-kindles/ |url-status=live |archive-url=http://web.archive.org/web/20251014062925/https://blog.the-ebook-reader.com/2024/10/20/amazon-removed-download-and-transfer-option-for-new-kindles/ |archive-date=14 Oct 2025|access-date=16 Mar 2025 |website=[[The Ebook Reader]]}}</ref> which led to controversy among {{Wplink|power user}}s as it disrupted existing workflow, which is to be expected. Book management software like Calibre<ref>{{Cite web |author=Kovid Goyal |date= |title=calibre - E-book management |url=https://www.calibre-ebook.com |url-status=live |archive-url=http://web.archive.org/web/20260222054742/https://calibre-ebook.com/ |archive-date=22 Feb 2026|access-date=2026-02-06 |website=}}</ref> addresses this issue, and can do the conversion of file formats locally. The recent firmware updates have caused other issues, like faster battery drain than before and a slower user experience.<ref>{{Cite web |last=Kozlowski |first=Micheal |date=20 Aug 2024 |title=The Amazon Kindle is in a state of decline |url=https://goodereader.com/blog/kindle/the-amazon-kindle-is-in-a-state-of-decline |url-status=live |archive-url=http://web.archive.org/web/20251219161317/https://goodereader.com/blog/kindle/the-amazon-kindle-is-in-a-state-of-decline |archive-date=19 Dec 2025|access-date=16 Mar 2025 |website=[[Good EReader]]}}</ref>

===Anti-repair and anti-ownership practices===
Kindle devices regularly receive bad scores in repair reviews.<ref name=":0">{{Cite web |last=Frauenheim |first=Carsten |title=Kindle 11 Repair |url=https://it.ifixit.com/Device/Kindle_11 |url-status=live |archive-url=http://web.archive.org/web/20260221125927/https://it.ifixit.com/Device/Kindle_11 |archive-date=21 Feb 2026|access-date=16 Mar 2025 |website=[[iFixit]]}}</ref><ref name=":1">{{Cite web |last=Rodriguez |first=Kris |title=Kindle Paperwhite 5 (11th Generation) Repair |url=https://ifixit.com/Device/Kindle_Paperwhite_11th_Generation |url-status=live |archive-url=http://web.archive.org/web/20251212013608/https://www.ifixit.com/Device/Kindle_Paperwhite_11th_Generation |archive-date=12 Dec 2025|access-date=16 Mar 2025 |website=[[iFixit]]}}</ref> The baseline model has a replaceable battery, but provides no official replacement parts or repair instructions, and solders the power button and usb-c port to the motherboard.<ref name=":0" /><ref name=":2">[https://www.ifixit.com/repairability/e-reader-repairability-scores e-reader repairability scores] ([http://web.archive.org/web/20251211041003/https://www.ifixit.com/repairability/e-reader-repairability-scores Archived])</ref> The paper-white model uses excessive amounts of adhesive for the battery and motherboard, which make it harder to replace the battery.<ref name=":1" /><ref name=":2" /> Most of the components of the device, most importantly the e-ink screen, are not available to the general market. Any stock for e-ink displays for these devices can rarely be found, and they usually approach the cost of the device itself, making repair uneconomical.

Kindle devices run a Linux distribution, however the bootloader is locked down and users have had trouble accessing debug ports on newer hardware.{{Citation needed|reason=Personal account}} Adding to this, Amazon relies on proprietary software and drivers which make it difficult to port a standard mainline Linux kernel onto their devices.{{Citation needed|date=30 Nov 2025}}

===Download feature removed for purchased books (''2025'')===
{{Main|Amazon Kindle removes download feature of purchased books}}
[[File:Amazon removal notice of download-transfer.webp|alt=Amazon notice about removing download capability|thumb|Amazon notice about removing download capability.<ref name=":03">{{Cite web |date=12 Feb 2025 |title=FYI Amazon is removing Download & Transfer option on Feb 26th |url=https://www.reddit.com/r/kindle/comments/1inr9uy/fyi_amazon_is_removing_download_transfer_option/ |archive-url=http://web.archive.org/web/20250804001513/https://old.reddit.com/r/kindle/comments/1inr9uy/fyi_amazon_is_removing_download_transfer_option/ |archive-date=4 Aug 2025|publisher=Reddit |language=en |format=forum thread}}</ref>]]
On 26 February 2025, [[Amazon]] removed the "download and transfer via USB" feature from their website. This means [[Amazon Kindle]] users are no longer able to download their purchased e-books from Amazon's website to their computers using the "download and transfer via USB" feature. A message describing this change appeared on the page for the download feature a few weeks before the feature was removed.

===Support discontinued for pre-2013 devices===
{{Main|Amazon Kindle discontinues support for pre-2013 devices}}
On 7 April 2026, Amazon began emailing customers that, starting 20 May 2026, the Kindle Store would no longer support nine pre-2013 Kindle e-reader models and four Kindle Fire tablet models, ending the ability to purchase, borrow, or download new content on the affected hardware.<ref name="kindle2026-pcmag">{{Cite web |last=Kan |first=Michael |title=Got a Kindle From Before 2013? Amazon Is Pulling Support |url=https://www.pcmag.com/news/got-a-kindle-from-before-2013-amazon-is-pulling-support |website=PCMag |date=7 April 2026 |access-date=8 April 2026}}</ref><ref name="kindle2026-register">{{Cite web |last=Kunert |first=Paul |title=Amazon rewards loyal Kindle devotees by closing the book on old e-readers |url=https://www.theregister.com/2026/04/08/amazon_kindle_support_discontinued/ |website=The Register |date=8 April 2026 |access-date=8 April 2026}}</ref> Amazon's email warned that any affected device deregistered or factory-reset after the cutoff cannot be re-registered and cannot be used "in any way."<ref name="kindle2026-pcmag" /><ref name="kindle2026-register" /> Amazon's only on-record justification was that the affected models had been supported "for at least 14 years, some as long as 18 years" and that "technology has come a long way," with no specific technical reason cited; the company offered affected owners a 20% discount on select new Kindle devices plus an eBook credit, valid through 20 June 2026.<ref name="kindle2026-pcmag" /><ref name="kindle2026-bgr">{{Cite web |last=Sayers |first=Jonathan |title=Amazon Is Discontinuing Support For These Older Kindle Models |url=https://www.bgr.com/2143389/amazon-discontinued-support-older-kindle-models/ |website=BGR |date=8 April 2026 |access-date=8 April 2026}}</ref>

==Products==
{{Ph-C-P}}

==See also==
*[[Amazon alters the content of purchased ebooks]]

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:Products]]
[[Category:Amazon]]

Amazon Kindle discontinues support for pre-2013 devices

2026-04-09T05:13:04Z

Louis: Create article from img-intake-triage campaign; see research brief for sources

{{IncidentCargo
|Company=Amazon
|StartDate=2026-04-07
|EndDate=
|Status=Active
|ProductLine=Amazon Kindle
|Product=
|ArticleType=Product
|Type=Planned Obsolescence,Digital Ownership,Right to Repair
|Description=Amazon will disable Kindle Store access on 13 pre-2013 Kindle devices on 20 May 2026; factory reset becomes a one-way brick.
}}

On 20 May 2026, [[Amazon]] will disable [[Amazon Kindle|Kindle Store]] access on thirteen Kindle devices released between 2007 and 2012, preventing owners of those devices from buying, borrowing, or downloading new content on the hardware.<ref name="pcmag-kan-20260407">{{Cite web |last=Kan |first=Michael |title=Got a Kindle From Before 2013? Amazon Is Pulling Support |url=https://www.pcmag.com/news/got-a-kindle-from-before-2013-amazon-is-pulling-support |website=PCMag |date=7 April 2026 |access-date=8 April 2026}}</ref><ref name="register-kunert-20260408">{{Cite web |last=Kunert |first=Paul |title=Amazon rewards loyal Kindle devotees by closing the book on old e-readers |url=https://www.theregister.com/2026/04/08/amazon_kindle_support_discontinued/ |website=The Register |date=8 April 2026 |access-date=8 April 2026}}</ref> Amazon notified affected customers by email beginning 7 April 2026 and warned that any device deregistered or factory-reset after the cutoff cannot be re-registered and cannot be used "in any way."<ref name="pcmag-kan-20260407" /><ref name="register-kunert-20260408" /> The shutdown covers nine e-reader models and four Kindle Fire tablet models.<ref name="pcmag-kan-20260407" /><ref name="register-kunert-20260408" /><ref name="goodereader-kozlowski-20260408">{{Cite web |last=Kozlowski |first=Michael |title=You can no longer buy e-books on Amazon Kindle made in 2012 or earlier |url=https://goodereader.com/blog/kindle/you-can-no-longer-buy-e-books-on-amazon-kindles-2012-and-earlier |website=Good e-Reader |date=8 April 2026 |access-date=8 April 2026}}</ref>

==Background==

Amazon launched the first Kindle e-reader on 19 November 2007.<ref name="wikipedia-kindle-launch-dates">{{Cite web |title=Amazon Kindle devices |url=https://en.wikipedia.org/wiki/Amazon_Kindle_devices |website=Wikipedia |access-date=8 April 2026}}</ref> The last two pre-2013 Kindle e-readers, the Kindle Paperwhite 1st Generation and the entry-level Kindle (the "Latest Generation Kindle," internally the fifth-generation Kindle), were both announced on 6 September 2012, with the Paperwhite priced at $119 for the Wi-Fi model and $179 for the Wi-Fi + 3G model at launch.<ref name="amazon-paperwhite-2012">{{Cite web |title=Introducing the New Kindle Paperwhite, the Most Advanced E-Reader Ever Constructed |url=https://press.aboutamazon.com/2012/9/introducing-the-new-kindle-paperwhite-the-most-advanced-e-reader-ever-constructed |website=Amazon Press Center |publisher=Amazon.com |date=6 September 2012 |access-date=8 April 2026}}</ref>

Several pre-2013 Kindles originally shipped with "Whispernet," Amazon's branding for the built-in 3G cellular link that allowed device registration and book delivery without Wi-Fi. Amazon retired the Whispernet brand name in June 2021, replacing it with generic "WAN" terminology in product descriptions, coinciding with the planned shutdown of global 3G infrastructure.<ref name="goodereader-whispernet-2021">{{Cite web |last=Kozlowski |first=Michael |title=Amazon Whispernet branding has been retired |url=https://goodereader.com/blog/kindle/amazon-whispernet-branding-has-been-retired |website=Good e-Reader |date=16 June 2021 |access-date=8 April 2026}}</ref> According to the Bipartisan Policy Center, AT&T completed its 3G shutdown on 22 February 2022, Verizon on 31 December 2022, and Sprint and T-Mobile completed their 3G shutdowns later in 2022.<ref name="bpc-3g-sunset-2022">{{Cite web |title=3G Sunsetting and the Digital Divide |url=https://bipartisanpolicy.org/explainer/3g-sunsetting-and-the-digital-divide/ |website=Bipartisan Policy Center |date=21 March 2022 |access-date=8 April 2026}}</ref> Those carrier shutdowns ended cellular Kindle Store access on affected 3G-equipped models years before the May 2026 Amazon-side shutdown; the 2026 EOL is a separate, Amazon-initiated event covering Wi-Fi-only and Wi-Fi + 3G variants alike.

The Kindle product line has been the subject of prior Amazon-initiated feature removals; see [[Amazon Kindle removes download feature of purchased books]].

==Announcement and scope==

Michael Kan of PCMag published an early English-language report on the notice on 7 April 2026, based on a Kindle owner in Australia who had received the email.<ref name="pcmag-kan-20260407" /> Coverage from The Register, Engadget, TechCrunch, Good e-Reader, BGR, and The eBook Reader Blog followed on 8 April 2026.<ref name="register-kunert-20260408" /><ref name="engadget-moon-20260408">{{Cite web |last=Moon |first=Mariella |title=Amazon is cutting off support for older Kindles |url=https://www.engadget.com/mobile/amazon-is-cutting-off-support-for-older-kindles-115653205.html |website=Engadget |date=8 April 2026 |access-date=8 April 2026}}</ref><ref name="techcrunch-forristal-20260408">{{Cite web |last=Forristal |first=Lauren |title=Amazon to end support for older Kindle devices |url=https://techcrunch.com/2026/04/08/amazon-to-end-support-for-older-kindle-devices-2012/ |website=TechCrunch |date=8 April 2026 |access-date=8 April 2026}}</ref><ref name="goodereader-kozlowski-20260408" /><ref name="bgr-sayers-20260408">{{Cite web |last=Sayers |first=Jonathan |title=Amazon Is Discontinuing Support For These Older Kindle Models |url=https://www.bgr.com/2143389/amazon-discontinued-support-older-kindle-models/ |website=BGR |date=8 April 2026 |access-date=8 April 2026}}</ref><ref name="theebookreader-groezinger-20260408">{{Cite web |last=Groezinger |first=Nathan |title=Amazon Ending Support for All Kindles Released Before 2013 |url=https://blog.the-ebook-reader.com/2026/04/08/amazon-ending-support-for-all-kindles-released-before-2013/ |website=The eBook Reader Blog |date=8 April 2026 |access-date=8 April 2026}}</ref>

The Amazon email tells affected owners that starting 20 May 2026, the company is "discontinuing support for Kindle devices released in 2012 or earlier."<ref name="pcmag-kan-20260407" /><ref name="register-kunert-20260408" /> Amazon's only on-record justification, quoted in PCMag and Engadget, is that the affected "models have been supported for at least 14 years, some as long as 18 years" and that "technology has come a long way."<ref name="pcmag-kan-20260407" /><ref name="engadget-moon-20260408" /> BGR's Jonathan Sayers noted that "no official reason was given" beyond the age of the devices; Amazon has not cited a TLS deprecation, certificate expiry, 3G carrier sunset, security-protocol change, or cost justification.<ref name="bgr-sayers-20260408" />

The nine affected e-reader models, with launch dates:

* Kindle (1st Generation), 19 November 2007<ref name="wikipedia-kindle-launch-dates" />
* Kindle (2nd Generation), 23 February 2009<ref name="wikipedia-kindle-launch-dates" />
* Kindle DX, 10 June 2009<ref name="wikipedia-kindle-launch-dates" />
* Kindle DX Graphite, 1 July 2010<ref name="wikipedia-kindle-launch-dates" />
* Kindle Keyboard (3rd Generation), 27 August 2010<ref name="wikipedia-kindle-launch-dates" />
* Kindle 4, 28 September 2011<ref name="wikipedia-kindle-launch-dates" />
* Kindle Touch, 15 November 2011<ref name="wikipedia-kindle-launch-dates" />
* Kindle 5 ("Latest Generation Kindle"), 6 September 2012<ref name="amazon-paperwhite-2012" /><ref name="wikipedia-kindle-launch-dates" />
* Kindle Paperwhite 1st Generation, 1 October 2012<ref name="wikipedia-kindle-launch-dates" />

The four affected Kindle Fire tablet models, confirmed as in scope by PCMag and Good e-Reader:<ref name="pcmag-kan-20260407" /><ref name="goodereader-kozlowski-20260408" />

* Kindle Fire 1st Generation, 15 November 2011<ref name="wikipedia-amazon-fire">{{Cite web |title=Amazon Fire |url=https://en.wikipedia.org/wiki/Amazon_Fire |website=Wikipedia |access-date=8 April 2026}}</ref>
* Kindle Fire 2nd Generation, 14 September 2012<ref name="wikipedia-amazon-fire" />
* Kindle Fire HD 7, 14 September 2012<ref name="wikipedia-amazon-fire" />
* Kindle Fire HD 8.9, 20 November 2012<ref name="wikipedia-amazon-fire" />

==Impact on affected devices==

After 20 May 2026, owners of affected Kindles and Kindle Fire tablets will no longer be able to "purchase, borrow, or download new content" on the hardware; previously downloaded books remain readable on the device.<ref name="register-kunert-20260408" /><ref name="pcmag-kan-20260407" />

Amazon's email to affected customers includes a warning that "if you deregister or factory reset these devices, you will not be able to re-register or use these devices in any way," quoted verbatim by PCMag, Engadget, Good e-Reader, and BGR.<ref name="pcmag-kan-20260407" /><ref name="engadget-moon-20260408" /><ref name="goodereader-kozlowski-20260408" /><ref name="bgr-sayers-20260408" /> PCMag reported that affected customer accounts and Kindle libraries remain accessible through the free Kindle app and Kindle for Web, meaning the purchased ebook library itself is not lost; the hardware binding is.<ref name="pcmag-kan-20260407" />

==Amazon's response==

Amazon's direct statement to press coverage was limited to the age-of-hardware justification quoted above.<ref name="pcmag-kan-20260407" /><ref name="engadget-moon-20260408" /> In parallel with the shutdown notice, Amazon offered affected owners a 20% discount on select new Kindle devices plus a $20 eBook credit automatically added to the customer account after a qualifying new-device purchase, valid through 20 June 2026 at 11:59pm.<ref name="pcmag-kan-20260407" /><ref name="bgr-sayers-20260408" /><ref name="goodereader-kozlowski-20260408" />

==Consumer response==

PCMag's Michael Kan reported that the story first surfaced after a user in Australia reported receiving the customer email.<ref name="pcmag-kan-20260407" /> BGR's Jonathan Sayers noted that "no official reason was given" by Amazon beyond the age of the devices.<ref name="bgr-sayers-20260408" />

==See also==
*[[Amazon]]
*[[Amazon Kindle]]
*[[Amazon Kindle removes download feature of purchased books]]
*[[Amazon alters the content of purchased ebooks]]

==References==
{{Reflist}}

[[Category:Amazon]]
[[Category:Amazon Kindle]]
[[Category:Planned Obsolescence]]
[[Category:Digital Rights Management]]
[[Category:Right to Repair]]
[[Category:2026 incidents]]

Ford

2026-04-08T15:45:26Z

Louis: update ccpa metrics to 2024, fix repossession and fordpass citations, move orphan competition bureau ref to freedom ford, opt-in language per mozilla

{{CompanyCargo
|Founded=1903
|Industry=Automotive
|Logo=Ford.png
|Type=Public
|Website=https://ford.com/
|Description=Automobile company which collects user data and sells it to third parties for advertising. Highest number of vehicle recalls in 2021, 2022, and 2023.
}}

The '''[[Wikipedia:Ford Motor Company|Ford Motor Company]]''' was founded in 1903 by Henry Ford in Detroit, Michigan. With the introduction of a moving assembly line, Ford drastically reduced the cost and time of automobile production, making cars affordable for the masses and transforming industrial production globally. It is one of the oldest and largest automobile manufacturers, one of the "Big Three" American automakers, alongside General Motors (GM) and Stellantis (formerly Chrysler).

==Consumer protection summary==

===User privacy===
:Ford’s data collection practices and privacy policies have raised significant concerns:
:*Extensive data collection: Ford collects a wide range of personal and vehicle data, including location, driving behavior (speed, braking), voice commands, media preferences, and even passenger information. This data is linked to the Vehicle Identification Number (VIN), which can be tied to individual users.<ref name=":0">{{Cite web |title=Privacy |url=https://www.ford.com/help/privacy/ |archive-url=http://web.archive.org/web/20260210074703/https://www.ford.com/help/privacy/ |archive-date=February 10, 2026 |website=Ford}}</ref>
:*Data collected includes purchase history, financial information, coarse and precise location data, contact information, identifiers (e.g., VIN, account ID), user-generated content (e.g., voice recordings from smart features), search and browsing history for advertising purposes, usage data, sensitive information (under "Inferences"), diagnostics, and more.<ref name=":0" />
:*Aggregates data from external sources as well, including users' social media posts.<ref name=":0" />
:*Privacy policy is designed to prevent quickly searching for important terms.<ref name=":0" />
:*Lack of transparency and control: Users are often unaware of the scope of data collection, and Ford’s policies allow sharing with affiliates, dealers, advertisers, and law enforcement. The company reserves the right to override location settings in certain circumstances (e.g., repossession, legal requests).<ref name=":0" />
:*Security vulnerabilities: Past incidents, such as cybersecurity flaws in the FordPass app and exposed customer records, highlight risks of data breaches. Ford has been criticized for dismissing external reports of vulnerabilities.<ref name=":4">{{Cite web |date=August 15, 2023 |title=Ford |url=https://www.mozillafoundation.org/en/privacynotincluded/ford/ |website=mozillafoundation.org |archive-url=https://web.archive.org/web/20260223043744/https://www.mozillafoundation.org/en/privacynotincluded/ford/ |archive-date=23 Feb 2026}}</ref>
:*According to Ford's Annual CCPA Metrics for 2024, the company received 137 requests to delete personal information and denied 7.<ref name=":0" />
===User freedom===
:*Limited opt-out options: Ford’s default settings opt users into data collection, with no clear path to fully delete data. Passengers and secondary drivers must also be informed of data collection, placing the burden on the primary user.<ref name=":0" />
:*Opt-in by default: Connected features accessed via the FordPass app, such as remote start and tire pressure checks, send vehicle data to Ford by default. According to Mozilla's Privacy Not Included review, halting account-linked data sharing requires performing a master reset or removing the VIN from the account.<ref name=":4" />
===Business model===
:*Data monetization: Ford’s business model leverages user data for targeted advertising, joint marketing, and partnerships (e.g., Sirius XM). This aligns with broader industry trends where data is a revenue driver.
:*AI and surveillance: Investments in AI (e.g., Baidu’s SYNC system in China) enable deeper user profiling, raising ethical questions about surveillance and consent.<ref>{{Cite web |last=Marr |first=Bernard |date=July 2, 2021 |title=The Amazing Ways The Ford Motor Company Uses Artificial Intelligence And Machine Learning |url=https://bernardmarr.com/the-amazing-ways-the-ford-motor-company-uses-artificial-intelligence-and-machine-learning/ |website= |archive-url=http://web.archive.org/web/20260219172306/https://bernardmarr.com/the-amazing-ways-the-ford-motor-company-uses-artificial-intelligence-and-machine-learning/ |archive-date=19 Feb 2026}}</ref>
===Market control===
:*Dealership consolidation: Ownership groups that already hold multiple dealerships have acquired Ford-branded outlets, such as 1911265 Alberta Ltd.'s 2016 acquisition of Freedom Ford Sales Limited. Canada's Competition Bureau reviewed the Freedom Ford transaction and issued a No Action Letter on January 29, 2016, concluding that effective remaining competitors made a substantial lessening of competition unlikely.<ref name=":freedomford-cb">{{Cite web |title=Acquisition of Freedom Ford Sales Limited by 1911265 Alberta Ltd. |url=https://competition-bureau.canada.ca/en/how-we-foster-competition/education-and-outreach/position-statements/acquisition-freedom-ford-sales-limited-1911265-alberta-ltd |website=Competition Bureau Canada |archive-url=http://web.archive.org/web/20250820052528/https://competition-bureau.canada.ca/en/how-we-foster-competition/education-and-outreach/position-statements/acquisition-freedom-ford-sales-limited-1911265-alberta-ltd |archive-date=20 Aug 2025}}</ref>
:*Dependence on connected services: By integrating AI and IoT (e.g., autonomous vehicles, CarStory analytics), Ford reinforces market dominance in connected car technology, potentially stifling smaller competitors.

===Anti-consumer practices===
*Patents regarding consumer data
**Ford has secured a patent for a system that is unrelated to core driving functions and involves vehicle repossession, allowing access restrictions in cases of missed payments. Ford has clarified that holding the patent does not necessarily mean it will be implemented in future products. However, the existence of such a system could influence consumer perceptions of the company and affect their willingness to accept certain sales terms.<ref name=":1">{{Cite web |last=Gitlin |first=Jonathan M. |date=March 2, 2023 |title=Ford files patent for system that could remotely repossess a car |url=https://arstechnica.com/cars/2023/03/ford-files-patent-for-system-that-could-remotely-repossess-a-car/ |archive-url=https://web.archive.org/web/20260223043817/https://arstechnica.com/cars/2023/03/ford-files-patent-for-system-that-could-remotely-repossess-a-car/ |archive-date=February 23, 2026 |website=Ars Technica}}</ref>
*Engineering practices
**Ford suffered a significant hit to its reputation regarding the Pinto, a car the company sold through the entire 1970's decade and the company's first subcompact. A number of high-profile incidents happened involving the cars getting rear-ended and subsequently lighting on fire due to the fuel tank rupturing and spilling gas; in subsequent lawsuits and criminal cases, Ford was accused of knowing the cars had a defect and deciding not to fix it based on an internal cost-benefit analysis that supposedly found it far cheaper to settle the lawsuits than actually fix the defect.
**Some engine designs use a rubber belt, rather than a metal chain, to drive the oil pump. This belt operates submerged in engine oil and may wear out prematurely, potentially leading to a sudden loss of oil pressure. Additionally, they have released transmission systems in certain ''Fiesta'' and ''Focus'' models that have experienced issues, including loss of power during acceleration, gear shifting, or at constant speeds, as well as unintended acceleration. It has been reported that a software update rendered a vehicle inoperable.<ref>{{Cite web |last=Braithwaite-Smith |first=Gavin |date=February 23, 2026 |title=BBC Watchdog shines light on Ford EcoBoost wet belt problem |url=https://garagewire.co.uk/news/bbc-watchdog-ford-ecoboost-wet-belt-problem/ |archive-url=https://web.archive.org/web/20260223043859/https://garagewire.co.uk/news/bbc-watchdog-ford-ecoboost-wet-belt-problem/ |archive-date=February 23, 2026 |website=garagewire.co.uk}}</ref><ref>{{Cite web |last=Howard |first=Phoebe Wall |date=July 11, 2019 |title=Ford knew Focus, Fiesta models had flawed transmission, sold them anyway |url=https://www.freep.com/in-depth/money/cars/ford/2019/07/11/ford-focus-fiesta-transmission-defect/1671198001/ |archive-url=http://web.archive.org/web/20260221023357/https://www.freep.com/in-depth/money/cars/ford/2019/07/11/ford-focus-fiesta-transmission-defect/1671198001/ |archive-date=February 21, 2026 |website=Detroit Free Press}}</ref><ref>{{Cite web |date=March 11, 2023 |title=Automatic Software Update Bricked my Truck |url=https://www.fordraptorforum.com/threads/automatic-software-update-bricked-my-truck.96624/ |archive-url=http://web.archive.org/web/20250415151514/https://www.fordraptorforum.com/threads/automatic-software-update-bricked-my-truck.96624/ |archive-date=April 15, 2025 |website=www.fordraptorforum.com}}</ref>
**Ford has had the highest number of vehicle recalls in the U.S. in 2021, 2022, and 2023. While recall volume can be influenced by market share, larger automakers often have more recalls, it may also reflect differences in production quality compared to competitors.<ref>{{Cite web |title=NHTSA Recalls by Manufacturer |url=https://datahub.transportation.gov/stories/s/NHTSA-Recalls-by-Manufacturer/38mw-dp8u/ |archive-url=http://web.archive.org/web/20260203181946/https://datahub.transportation.gov/stories/s/NHTSA-Recalls-by-Manufacturer/38mw-dp8u/ |archive-date=February 3, 2026 |website=datahub.transportation.gov}}</ref>

====In-vehicle advertising patent====
In February 2023, Ford filed United States patent application number 20240289844, titled "In-Vehicle Advertisement Presentation Systems and Methods."<ref name=":fordadpatent-justia">{{Cite web |date=23 Feb 2023 |title=IN-VEHICLE ADVERTISEMENT PRESENTATION SYSTEMS AND METHODS |url=https://patents.justia.com/patent/20240289844 |url-status=live |access-date=29 Mar 2025 |website=Justia Patents |archive-url=http://web.archive.org/web/20250708193151/https://patents.justia.com/patent/20240289844 |archive-date=8 Jul 2025}}</ref> The application describes a system that combines historical user data with audio signals from inside the vehicle to serve personalized advertisements through the human-machine interface, monitoring conversations between occupants to decide when, how many, and in what format to present ads.<ref name=":fordadpatent-justia" /><ref>{{Cite web |last=Smalley |first=Suzanne |date=September 9, 2024 |title=Ford seeks patent for tech that listens to driver conversations to serve ads |url=https://therecord.media/ford-patent-application-in-vehicle-listening-advertising |archive-url=http://web.archive.org/web/20260101115700/https://therecord.media/ford-patent-application-in-vehicle-listening-advertising |archive-date=January 1, 2026 |website=therecord.media}}</ref> The patent overview states that "such systems and methods further provide the opposite force to a user's natural inclination to seek minimal or no ads."<ref name=":fordadpatent-justia" /> Vehicle location and navigation data would be used to infer the user's residence or workplace and to select ads tied to commercial locations along the driver's route; current traffic data could trigger increased ad delivery during longer trips spent in congestion.<ref name=":fordadpatent-justia" /> For the full incident article, see [[Ford ad patent]].

====Lip-reading and facial expression detection patent application====
Ford Global Technologies, LLC is the named applicant on patent application US 2026/0095520 A1, titled "Systems and methods for hands-free communication in convertible vehicles," published by the United States Patent and Trademark Office on April 2, 2026.<ref name=":ford-lipread-patent">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06}}</ref> The named inventors are Keith Weston, John Robert Van Wiemeersch, Matthew Flis, and Brendan Diamond. The application was filed October 1, 2024 as application number 18/903,253. A [[:File:Ford_patent_US20260095520A1.pdf|local archive of the patent application PDF]] is hosted on this wiki.

The application describes a vehicle that detects when it is in a convertible state (top retracted, panel removed, door removed, or sunroof open) and, if cabin noise exceeds a threshold, switches its in-vehicle communication system into an enhanced mode.<ref name=":ford-lipread-patent" /> The enhanced mode can enable a lip reading mode and a gesture and facial expression detection mode. The application states that "[t]he one or more cameras of the vehicle capture the movements of the user's lips" and that the captured video is processed using machine learning algorithms trained on datasets of lip movements.<ref name=":ford-lipread-patent-p5">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06 |page=5}}</ref> It also describes a method in which "the vehicle may emit inaudible sound waves and analyze the echoes that bounce back from the user's lip and mouth" to detect facial movements.<ref name=":ford-lipread-patent-p5" /> Independent claim 16 recites storing in a database the association between each of a plurality of gestures and a corresponding verbal command. Dependent claim 17 adds the steps of detecting a gesture, looking up its corresponding command in the database, and executing that command.<ref name=":ford-lipread-patent-p9">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06 |page=9}}</ref>

The application describes storing gesture-to-command associations in a vehicle database<ref name=":ford-lipread-patent-p9" /> and transmitting generated speech or text data to the other party in a conversation,<ref name=":ford-lipread-patent-p5" /> but it does not specify whether raw lip-movement video is retained after processing, how long any captured data is kept, or whether any captured data flows to Ford's control servers or cloud infrastructure. As of the April 2, 2026 publication date, it is a published application and has not issued as a granted patent. For Ford's earlier in-vehicle data collection practices, see [[Jones v. Ford Motor Co.]].

==References==
<references />
[[Category:Ford]]

Vizio Walmart account requirement for smart TV features

2026-04-08T14:51:53Z

Louis: fix citation alignment: replace ars-vizio with primary sources for platform+/rainey/walmart connect figures; remove unsupported hdmi/tuner fallback claims; tighten lede scope; update ky hb 692 to senate passage

{{#seo:
|description=Walmart requires new Vizio TV owners to create a Walmart account to access smart TV features, linking viewing data with retail purchase history.
}}
{{IncidentCargo
|Company=Vizio,Walmart
|StartDate=2026-03-23
|EndDate=
|Status=Active
|ProductLine=
|Product=
|ArticleType=Product
|Type=Privacy,Subscription
|Description=Walmart locks Vizio smart TV features behind a Walmart account, linking TV viewing data with retail purchase history
}}{{See also|Forced account}}
'''Vizio Walmart account requirement for smart TV features''' is [[Walmart]]'s policy of requiring owners of select new [[Vizio]] OS smart TVs to create a Walmart account before they can use smart TV features. Walmart announced the requirement on March 23, 2026, at the IAB NewFronts.<ref name="walmart-newfronts">{{Cite web |url=https://corporate.walmart.com/news/2026/03/23/walmart-and-vizio-scale-content-to-commerce-at-newfronts |title=Walmart and VIZIO Scale Content to Commerce at NewFronts |date=2026-03-23 |website=Walmart Corporate}}</ref> The policy ties TV viewing habits tracked by Vizio's automatic content recognition (ACR) technology to Walmart's retail purchase data, creating a unified advertising profile across a customer base of approximately 150 million weekly U.S. shoppers.<ref name="walmart-newfronts" /> Consumers who do not create a Walmart account cannot complete onboarding or use smart TV features on affected models.<ref name="ars-vizio">{{Cite web |url=https://arstechnica.com/gadgets/2026/03/newly-purchased-vizio-tvs-now-require-walmart-accounts-to-use-smart-features/ |title=Newly purchased Vizio TVs now require Walmart accounts to use smart features |author=Scharon Harding |date=2026-03-24 |website=Ars Technica |access-date=2026-03-30}}</ref>

==Background==

Walmart completed its acquisition of Vizio on December 3, 2024, paying $11.50 per share for a total of approximately $2.3 billion in fully diluted equity value.<ref name="walmart-acquisition">{{Cite web |url=https://corporate.walmart.com/news/2024/12/03/walmart-completes-acquisition-of-vizio |title=Walmart Completes Acquisition of VIZIO |date=2024-12-03 |website=Walmart Corporate}}</ref> Vizio became a wholly owned subsidiary of Walmart, with its business reported as part of the Walmart U.S. segment, & founder & CEO William Wang continuing to lead the company under Seth Dallaire, Walmart's EVP & Chief Growth Officer.<ref name="walmart-acquisition" /> Vizio's stock was delisted from the NYSE effective that day.<ref name="walmart-acquisition" /> At the time of the acquisition, Vizio had 19 million active accounts.<ref name="walmart-acquisition" />

The acquisition was not primarily about selling television hardware. In Vizio's final quarter as an independent company, its advertising platform (Platform+) reported a gross profit of $115.8 million, while its hardware (Device) segment reported a gross loss of $6.7 million.<ref name="vizio-q3-2024">{{Cite web |url=https://www.businesswire.com/news/home/20241101202974/en/VIZIO-HOLDING-CORP.-Reports-Q3-2024-Financial-Results |title=VIZIO HOLDING CORP. Reports Q3 2024 Financial Results |date=2024-11-01 |website=BusinessWire}}</ref> On Walmart's Q4 FY2026 earnings call, Walmart CFO John David Rainey said Walmart "saw triple-digit growth in advertising with our VIZIO business in the quarter" and reported that Walmart's global advertising businesses grew 46% over the year to $6.4 billion.<ref name="walmart-q4-2026-transcript">{{Cite web |url=https://stock.walmart.com/_assets/_08ee5483ec4c057568cc8774f3fd6aad/walmart/db/938/9972/transcript_management_call/CORRECTED+TRANSCRIPT++Walmart%2C+Inc.%28WMT-US%29%2C+Q4+2026+Earnings+Call%2C+19-February-2026+8+00+AM+ET.pdf |title=Corrected Transcript - Walmart, Inc. Q4 2026 Earnings Call |date=2026-02-19 |website=stock.walmart.com |format=PDF}}</ref><ref name="adexchanger-walmart-64b">{{Cite web |url=https://www.adexchanger.com/commerce/walmarts-ad-revenue-totaled-6-4-billion-in-2025-as-the-ecom-flywheel-started-to-spin/ |title=Walmart's Ad Revenue Totaled $6.4 Billion In 2025 As The Ecom Flywheel Started To Spin |date=2026-02-20 |website=AdExchanger}}</ref>

==Account requirement==

A Walmart spokesperson told Ars Technica the account is required on "select new Vizio OS TVs" "for owners to complete onboarding and to use smart TV features."<ref name="ars-vizio" /> The requirement also applies to onn-branded TVs powered by Vizio OS.<ref name="walmart-newfronts" /> Walmart has not disclosed which specific models or SKUs are affected.<ref name="ars-vizio" />

Customers who already have a Vizio account can merge it with a Walmart account. Customers can also opt out by deleting their Vizio account, but doing so removes access to smart TV features.<ref name="ars-vizio" />

===Walmart's stated rationale===

Walmart's NewFronts announcement described the account integration as a way to connect streaming engagement with retail purchases. The press release stated the login "simplifies setup while establishing a secure identity framework across devices, connecting streaming engagement directly with retail interaction."<ref name="walmart-newfronts" />

Alongside the account requirement, Walmart announced a branded content partnership with L'Oreal, placing product integrations within Vizio's streaming environment that link directly to Walmart product pages.<ref name="ars-vizio" /><ref name="walmart-newfronts" /> Walmart cited internal data claiming 65% of surveyed customers reported that connected TV ads helped them discover new products, & that successful Walmart Connect CTV campaigns delivered a median 44% view rate.<ref name="walmart-newfronts" />

A Walmart representative told Ars Technica that the integration is "designed to respect consumer choice and privacy, with data used in aggregated, permissioned, and compliant ways" but did not provide specifics on what data is collected or how consent is obtained.<ref name="ars-vizio" />

==Data collection & privacy==

Vizio's privacy policy describes its ACR technology as capturing viewing behavior & usage "in real-time," including audio & video programming, ads, gaming content, devices connected to the TV such as a streaming stick plugged into an HDMI port, & third-party apps.<ref name="vizio-privacy">{{Cite web |url=https://www.vizio.com/en/terms/privacy-policy |title=VIZIO Privacy Policy |website=Vizio |access-date=2026-03-30}}</ref>

Vizio's privacy policy describes a "Consent to Combine VIZIO OS Data with Your Walmart Account Data" toggle. When enabled, data from Vizio OS devices "will be linked to the Walmart account logged in to those devices or services and combined with that Walmart account's data."<ref name="vizio-privacy" /> The data subject to this combination, which Vizio calls "VIZIO OS Data," includes viewing data, activity data, mobile app data, & mobile streaming data.<ref name="vizio-privacy" /> Even when the toggle is off, the policy states that "limited disclosure to Walmart of VIZIO OS Data may continue," including for "aggregate audience measurement, aggregate reporting on ad performance, or pseudonymized target audience groups."<ref name="vizio-privacy" />

Walmart is not an electronics manufacturer or streaming platform. A Walmart account is tied to a customer's purchase history across Walmart's retail operations, creating a data set that combines what a person watches with what they buy.<ref name="privacy-guides">{{Cite web |url=https://www.privacyguides.org/news/2026/03/27/vizio-tvs-will-now-require-a-walmart-account/ |title=Vizio TVs will now require a Walmart account |date=2026-03-27 |website=Privacy Guides |access-date=2026-03-30}}</ref><ref name="walmart-newfronts" />

===Vizio's 2017 FTC settlement===

Vizio has prior federal enforcement history involving unauthorized data collection from its smart TVs. In February 2017, Vizio agreed to pay $2.2 million to settle charges by the FTC & the New Jersey Attorney General that it collected viewing histories on 11 million smart televisions without users' consent.<ref name="ftc-2017">{{Cite web |url=https://www.ftc.gov/news-events/news/press-releases/2017/02/vizio-pay-22-million-ftc-state-new-jersey-settle-charges-it-collected-viewing-histories-11-million |title=VIZIO to Pay $2.2 Million to FTC, State of New Jersey to Settle Charges It Collected Viewing Histories on 11 Million Smart Televisions without Users' Consent |date=2017-02-06 |website=Federal Trade Commission}}</ref> The payment comprised $1.5 million to the FTC & $1 million to the New Jersey Division of Consumer Affairs, with $300,000 of that amount suspended.<ref name="ftc-2017" />

Starting in February 2014, Vizio had installed software on its smart TVs that captured second-by-second information about video displayed on the screen, including video from cable, broadband, set-top boxes, DVDs, over-the-air broadcasts, & streaming devices.<ref name="ftc-2017" /> Vizio appended demographic data to the viewing records, including sex, age, income, marital status, household size, education level, home ownership, & household value, then sold this information to third parties for cross-device advertising targeting.<ref name="ftc-2017" />

The FTC consent order, approved on a 3-0 vote, required Vizio to prominently disclose & obtain affirmative express consent for data collection, delete data collected before March 1, 2016, implement a "comprehensive data privacy program", & submit to biennial privacy assessments.<ref name="ftc-2017" />

==Regulatory context==

Multiple states have taken enforcement action against smart TV manufacturers for ACR data collection practices. On December 15, 2025, Texas Attorney General Ken Paxton sued Sony, Samsung, LG, Hisense, & TCL, alleging these companies unlawfully collected personal data through ACR technology without consumers' knowledge or consent.<ref name="texas-ag">{{Cite web |url=https://texasattorneygeneral.gov/news/releases/attorney-general-paxton-sues-five-major-tv-companies-including-some-ties-ccp-spying-texans |title=Attorney General Paxton Sues Five Major TV Companies, Including Some with Ties to CCP, for Spying on Texans |date=2025-12-15 |website=Texas Attorney General}}</ref> A Texas court issued a temporary restraining order against Hisense, preventing it from collecting, using, selling, or sharing ACR data about Texans.<ref name="texas-tro">{{Cite web |url=https://www.texasattorneygeneral.gov/news/releases/attorney-general-ken-paxton-secures-court-order-stopping-ccp-aligned-smart-tv-company-spying-texans |title=Attorney General Ken Paxton Secures Court Order Stopping CCP-Aligned Smart TV Company from Spying on Texans |date=2025-12-17 |website=Texas Attorney General |access-date=2026-03-30}}</ref>

Samsung reached an agreement with the Texas Attorney General on February 26, 2026, under which Samsung must obtain Texas consumers' express consent before collecting or processing ACR data and must implement clear and conspicuous disclosure and consent screens on its smart TVs.<ref name="samsung-settlement">{{Cite web |url=https://www.texasattorneygeneral.gov/news/releases/attorney-general-paxton-secures-major-agreement-samsung-ensure-texans-are-protected-smart-tvs |title=Attorney General Paxton Secures Major Agreement with Samsung to Ensure Texans Are Protected from Smart TVs |date=2026-02-26 |website=Texas Attorney General}}</ref>

In Kentucky, House Bill 692 passed the state House of Representatives 92-0 on March 13, 2026 and the Senate 38-0 on March 31, 2026 with Committee Substitute 1.<ref name="ky-hb692">{{Cite web |url=https://apps.legislature.ky.gov/record/26rs/hb692.html |title=HB 692 |website=Kentucky Legislature |access-date=2026-04-08}}</ref> As amended, the bill prohibits controllers from collecting automatic content recognition data without a consumer's consent. If signed into law, it would take effect July 1, 2027.<ref name="ky-hb692" />

==Consumer alternatives==

External streaming devices such as an [[Apple TV]], Roku stick, Amazon Fire TV, or Chromecast provide app store access & streaming functionality independent of the TV manufacturer's account system.

Consumers can disable ACR tracking on Vizio TVs through the settings menu. On newer Vizio OS TVs, the path is All Settings > Privacy & Legal > Viewing Data; on older models, it is All Settings > Admin & Privacy > Viewing Data.<ref name="vizio-privacy" /> The 2017 FTC consent order required Vizio to maintain a disclosure & consent mechanism for data collection.<ref name="ftc-2017" />

==References==

{{reflist}}

[[Category:Vizio]]
[[Category:Walmart]]
[[Category:Privacy]]
[[Category:Smart TVs]]

Formlabs

2026-04-08T13:00:31Z

Louis: fix boppart to software side per toms hardware; replace fabricated anti-consumer oml quotes with verbatim forum language; drop uncited causal claim on tiered pricing

{{#seo:description=Formlabs charges $875-$11,899 per printer to use third-party materials, acquired & killed a $2,999 SLS competitor, and obsoleted the Form 2 via resin DRM.}}
{{CompanyCargo
|Founded=2011
|Industry=3D printing
|Logo=Formlabs logo.svg
|ParentCompany=
|CompanyAlias=
|Type=Private
|Website=https://formlabs.com
|Description=Charges $875-$11,899 per printer to use third-party materials; acquired & canceled a $2,999 SLS competitor to protect its $28,989 Fuse 1+
}}

'''Formlabs''' is a 3D printing company that charges its customers $875 to $11,899 per printer for the permission to use third-party materials on hardware they already own.<ref name="formlabs-omm-store">{{Cite web |title=Open Material Mode |url=https://formlabs.com/store/materials/open-material-mode/ |website=Formlabs |access-date=2026-04-04 |url-status=live |archive-url=https://web.archive.org/web/20260116171208/https://formlabs.com/store/materials/open-material-mode/ |archive-date=2026-01-16}}</ref> In July 2024, Formlabs acquired Micronics, a startup building a $2,999 desktop SLS printer funded on Kickstarter, & immediately canceled the product.<ref name="formlabs-acquires-micronics">{{Cite web |title=Formlabs Acquires Micronics to Develop the Next Generation of Accessible SLS |url=https://formlabs.com/blog/formlabs-acquires-micronics/ |website=Formlabs |date=2024-07-11}}</ref><ref name="3dprint-micronics">{{Cite web |title=Formlabs Buys Nascent SLS 3D Printer Competitor Micronics |url=https://3dprint.com/311327/formlabs-buys-nascent-sls-3d-printer-competitor-micronics/ |website=3DPrint.com |date=2024-07-11}}</ref> The cheapest SLS printer Formlabs sells starts at $28,989; the Micron would have cost roughly 1/10th that price.<ref name="formlabs-sls-pricing">{{Cite web |title=How to Compare SLS 3D Printer Prices |url=https://formlabs.com/blog/selective-laser-sintering-sls-3d-printer-price/ |website=Formlabs |access-date=2026-04-04}}</ref><ref name="3dprint-micronics" /> Founded in 2011 by MIT Media Lab students Maxim Lobovsky, David Cranor, & Natan Linder, the company raised $2.95 million on Kickstarter for its first printer & has since raised over $230 million in venture funding.<ref name="wikipedia-formlabs">{{Cite web |title=Formlabs |url=https://en.wikipedia.org/wiki/Formlabs |website=Wikipedia |access-date=2026-04-04}}</ref>

== Consumer-impact summary ==

* Formlabs charges a per-printer license fee ranging from $875 (Form 4) to $11,899 (Fuse 1 series) for the permission to use third-party materials on hardware the customer already owns.<ref name="formlabs-omm-store" />
* The company acquired Micronics in July 2024 & canceled the Micron, a $2,999 SLS 3D printer that had raised over £1 million from 431 Kickstarter backers.<ref name="3dprint-micronics" /><ref name="develop3d-micronics" /> Formlabs' own SLS printer, the Fuse 1+ 30W, starts at $28,989.<ref name="formlabs-sls-pricing" />
* The Form 2 uses proprietary DRM-chipped resin cartridges. Formlabs committed to supplying consumables through 2023, then left the end date ambiguous; by September 2024 consumables were still available but with no guaranteed supply timeline.<ref name="formlabs-forum-form2-support">{{Cite web |title=Ongoing Support for the Form 2 |url=https://forum.formlabs.com/t/ongoing-support-for-the-form-2/22871 |website=Formlabs Community Forum |date=2019-04}}</ref><ref name="formlabs-forum-form2-consumables">{{Cite web |title=Form 2 availability of consumables |url=https://forum.formlabs.com/t/form-2-availability-of-consumables/39108 |website=Formlabs Community Forum |date=2024-09}}</ref>

== Incidents ==

This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:Formlabs|Formlabs category]].

=== Acquisition of Micronics ===

Formlabs acquired Micronics on July 11, 2024, & canceled the Micron desktop SLS 3D printer the same day.<ref name="formlabs-acquires-micronics" /> The Micron had launched on Kickstarter in June 2024 at a starting price of $2,999.<ref name="3dprint-micronics" /> The campaign raised over £1 million from 431 backers.<ref name="develop3d-micronics">{{Cite web |title=Desktop SLS start-up Micronics acquired by Formlabs |url=https://develop3d.com/3d-printing/desktop-sls-company-micronics-acquired-by-formlabs/ |website=Develop3D |date=2024-07-11}}</ref>

SLS (Selective Laser Sintering) printers use a laser to fuse nylon powder into parts without support structures. Traditional industrial SLS machines from manufacturers like EOS & 3D Systems cost $200,000 to $500,000 or more.<ref name="formlabs-sls-pricing" /> Formlabs' own SLS offering, the Fuse 1+ 30W, starts at $28,989.<ref name="formlabs-sls-pricing" /> The Micron at $2,999 would have undercut the Fuse 1+ 30W by roughly 10x.<ref name="3dprint-micronics" />

Formlabs CEO Max Lobovsky acknowledged this price gap in an interview with TechCrunch, stating that Formlabs had achieved a "5x leap in starting price" with the Fuse 1 & that Micronics was "trying to do another 5x beyond that."<ref name="techcrunch-micronics">{{Cite web |title=Formlabs acquires 3D printing startup Micronics mid-Kickstarter campaign |url=https://techcrunch.com/2024/07/11/formlabs-acquires-3d-printing-startup-micronics-mid-kickstarter-campaign/ |website=TechCrunch |date=2024-07-11}}</ref> Per Tom's Hardware, "Boppart will join the software side of Formlabs while Chan will lead the development of Formlabs next generation printers."<ref name="tomshardware-micronics">{{Cite web |title=David vs Goliath: Desktop SLS Kickstarter Ends with Acquisition |url=https://www.tomshardware.com/3d-printing/david-vs-goliath-desktop-sls-kickstarter-ends-with-acquisition |website=Tom's Hardware |first=Denise |last=Bertacchi |date=2024-07-11}}</ref> The Micronics brand was discontinued & the Kickstarter was canceled.<ref name="techcrunch-micronics" />

Tom's Hardware headlined its coverage "David vs Goliath" & reported that the Micronics branding would be discontinued.<ref name="tomshardware-micronics" /> 3D Printing Industry reported the acquisition as producing "new accessible SLS 3D printers forthcoming," but no such product has shipped as of April 2026.<ref name="3dprintingindustry-micronics">{{Cite web |title=Formlabs acquires Micronics, new accessible SLS 3D printers forthcoming |url=https://3dprintingindustry.com/news/formlabs-acquires-micronics-new-accessible-sls-3d-printers-forthcoming-231608/ |website=3D Printing Industry |date=2024-07-11}}</ref>

Formlabs offered backers a full refund plus a $1,000 credit toward any current or future Formlabs printer & a free Open Material License.<ref name="formlabs-press-micronics">{{Cite web |title=Formlabs Acquires Micronics to Further Advance Accessible SLS 3D Printing |url=https://formlabs.com/company/press/formlabs-acquires-micronics/ |website=Formlabs |date=2024-07-11}}</ref><ref name="formlabs-forum-backer-breach" /> By December 2024, backers reported on the Formlabs forum that the promised $1,000 credit had not been delivered months after submission. Some backers who attempted to use their credit toward a Fuse 1 purchase were denied a $5,000 discount for unspecified reasons. The forum thread was auto-closed in July 2025.<ref name="formlabs-forum-backer-breach">{{Cite web |title=Formlabs' breach of promised Open Material License and $1000 credit to Micronics Kickstarter Backer |url=https://forum.formlabs.com/t/formlabs-breach-of-promised-open-material-license-and-1000-credit-to-micronics-kickstarter-backer/40715 |website=Formlabs Community Forum |date=2024-12-27}}</ref> A $1,000 credit toward a $28,989 SLS printer represents a 3.4% discount for backers who had pledged for a $2,999 machine.

=== Open Material Mode ===

Formlabs requires a one-time per-printer software license to unlock the use of third-party resins & powders on its printers. The license, called Open Material Mode, costs $875 for the Form 4, $1,999 for the Form 3 series, $2,499 for the Form 4B, $3,999 for the Form 3L series, $4,999 for the Form 4L, & $11,899 for the Fuse 1 series.<ref name="formlabs-omm-store" /> Without the license, users can only load Formlabs' proprietary DRM-chipped resin cartridges.

On the Formlabs community forum in September 2023, Form 3 pre-order customer rkagerer stated that paying "$6k (per printer!) for the capability" might "expose them to litigation risk given the original marketing and sales assurances" that Open Mode on the Form 3 had been promised pre-release. Another user, Reine, asked "Is Formlabs idea to charge me three times the cost of a printer to use 3rd party resins?!" Other commenters wrote that "no normal person is going to buy a 6k add on" and questioned who would buy the $6k option.<ref name="formlabs-forum-oml-6k">{{Cite web |title=Open Material License $6k per printer |url=https://forum.formlabs.com/t/open-material-license-6k-per-printer/36905 |website=Formlabs Community Forum |date=2023-09-12 |access-date=2026-04-08}}</ref> Formlabs' current tiered pricing on its store lists $1,999 for the Form 3 series and $875 for the Form 4.<ref name="formlabs-omm-store" />

The license is free for accredited educational institutions.<ref name="formlabs-omm-store" /> As of January 2026, Open Material Mode is included with new Form 4B & 4BL purchases, but owners who bought the same printers before that date must pay the full license fee.<ref name="formlabs-forum-4b-omm">{{Cite web |title=PSA to All form Form 4B & 4BL owners (Open material mode) |url=https://forum.formlabs.com/t/psa-to-all-form-form-4b-4bl-owners-open-material-mode/46199 |website=Formlabs Community Forum |date=2026-01}}</ref> Formlabs' warranty terms state that failure modes caused by third-party materials are excluded from standard warranty coverage, adding financial risk on top of the license cost.<ref name="formlabs-omm-store" />

=== Form 2 deprecation ===

Formlabs announced the end of active support for the Form 2 in April 2019, following the launch of the Form 3 series. The company committed to selling resin tanks, cartridges, & build platforms through at least 2023.<ref name="formlabs-forum-form2-support" /> The Form 2 uses proprietary DRM-chipped resin cartridges. Without an authorized cartridge, the printer runs in a limited mode that disables the heater & wiper functions, reducing print quality.<ref name="protoart-cartridge" />

By September 2024, nine months past the stated deadline, Form 2 consumables were still available but Formlabs hadn't provided a firm end date. Users requested concrete timelines to plan investment decisions; Formlabs didn't respond in the thread.<ref name="formlabs-forum-form2-consumables" /> Once Formlabs stops selling Form 2-compatible cartridges, owners of the $3,500 printer will have no official consumable supply. The printer becomes unusable even though the hardware itself still works.<ref name="formlabs-forum-form2-support" />

Third-party developers attempted workarounds. ProtoART produced a Universal Cartridge, a DIY modification kit installed into an existing cartridge that allowed third-party resin use with heater & wiper functions enabled.<ref name="protoart-cartridge">{{Cite web |title=A Universal Cartridge For Form 2 3D Printers, But Should You Use It? |url=https://www.fabbaloo.com/2019/09/a-universal-cartridge-for-form-2-3d-printers-but-should-you-use-it |website=Fabbaloo |date=2019-09}}</ref> The Universal Cartridge is compatible only with Formlabs firmware versions through 2.2.0; the product reached end of life & is available only while supplies last.<ref name="protoart-site">{{Cite web |title=Universal Cartridge Module for Formlabs |url=https://www.lectronz.com/products/universal-cartridge-for-formlabs-form-2-form-3 |website=Lectronz |access-date=2026-04-04}}</ref>

== Products ==

* '''SLA printers:''' Form 1, Form 1+, Form 2, Form 3 series (Form 3, 3+, 3B, 3B+, 3L, 3BL), Form 4 series (Form 4, 4B, 4L, 4BL)
* '''SLS printers:''' Fuse 1, Fuse 1+ 30W
* '''Software:''' PreForm (slicing & print preparation)
* '''Post-processing:''' Form Wash, Form Cure
* '''Automation:''' Form Auto, Form Cell

== See also ==

* [[Bambu Lab]]
* [[Creality]]
* [[MakerBot]]

== References ==

{{reflist}}

[[Category:Formlabs]]
[[Category:3D Printing]]
[[Category:Planned Obsolescence]]

Jones v. Ford Motor Co.

2026-04-07T22:41:07Z

Louis: added context from the ritch v honda companion memo (22-35448): panel composition, rule 36-3 non-precedential status, ritch plaintiffs, estudillo presiding over both cases, the 9th's 'virtually identical' framing, and ritch's independent statutory-injury holding. also fixed a lede mischaracterization of the jones holding

{{IncidentCargo
|Company=Ford,Honda,Toyota,Volkswagen,General Motors
|StartDate=2023-10-27
|EndDate=2023-11-07
|Status=Resolved
|ProductLine=
|Product=
|ArticleType=Product
|Type=Privacy
|Description=Ford, Honda, Toyota, VW & GM infotainment systems download & store all texts & call logs from connected phones; 9th Circuit affirmed dismissal
}}
[[File:Case outcome.png|thumb]]
In ''Jones v. Ford Motor Co.'', the U.S. Court of Appeals for the Ninth Circuit on October 27, 2023 affirmed the dismissal of a putative class action alleging that '''[[Ford]] infotainment systems automatically download & permanently store text messages & call logs from any cellphone connected to the vehicle, with no way for the owner to access or delete the data.'''<ref name="jones-cover">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., No. 22-35447, slip op. (9th Cir. Oct. 27, 2023) (per curiam) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06}}</ref><ref name="jones-p4">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 4 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=4}}</ref> The per curiam published opinion held that '''those allegations satisfied Article III injury-in-fact but failed the [[Washington Privacy Act]]'s statutory damages requirement under RCW 9.73.060, which limits civil recovery to plaintiffs who can show injury to "his or her business, his or her person, or his or her reputation."'''<ref name="jones-p7">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 7 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=7}}</ref><ref name="rcw">{{Cite web |url=https://app.leg.wa.gov/rcw/default.aspx?cite=9.73.060 |title=RCW 9.73.060: Violating right of privacy. Civil action. Liability for damages |publisher=Washington State Legislature |access-date=2026-04-06}}</ref> Since none of the plaintiffs alleged injury to their business, person, or reputation from the vehicle's collecting & storing user data against their will, the claim failed at the pleading stage.<ref name="jones-p8" />

A companion memorandum disposition, ''Ritch v. American Honda Motor Co.'' (Nov. 7, 2023), brought by appellants Stacy Ritch & Gellert Dornay, affirmed dismissal of the parallel [[Honda]] action "for the same reasons" as ''Jones''. The ''Ritch'' memorandum identified three related actions against [[Volkswagen]], [[Toyota]], & [[General Motors]] (''Dornay v. Volkswagen'', No. 22-35451; ''Goussev v. Toyota'', No. 22-35454; ''McKee v. General Motors'', No. 22-35456).<ref name="ritch">{{Cite web |url=https://s3.documentcloud.org/documents/24133084/22-35448.pdf |title=Ritch v. American Honda Motor Co., No. 22-35448, mem. (9th Cir. Nov. 7, 2023) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-11-07 |access-date=2026-04-06}}</ref>

==Background==

Washington residents filed five putative class actions alleging that the '''infotainment systems shipped by Ford, Honda, Toyota, Volkswagen, & General Motors automatically downloaded the call logs & text messages of any cellphone connected to the vehicle, retained those communications indefinitely on the vehicle's onboard memory after the phone was disconnected, & left owners with no way to access or delete the stored data.'''<ref name="jones-p4" /><ref name="ritch" /> '''The plaintiffs further alleged that the stored communications could be extracted by hardware & software produced by the Berla Corporation, & that Berla's products were not generally available to the public, with sales restricted to law enforcement, the military, civil & regulatory agencies, & select private investigation service providers.'''<ref name="jones-p4" /> The five suits sought damages under the Washington Privacy Act, RCW 9.73.060, which authorizes civil recovery only for plaintiffs who can show that a violation of the statute "has injured his or her business, his or her person, or his or her reputation."<ref name="rcw" /> The Ninth Circuit later described the five cases as "virtually identical" in factual background & legal issues, explaining that "although the class actions were brought against separate automobile manufacturers, the factual background and legal issues are virtually identical."<ref name="ritch-p2">{{Cite web |url=https://s3.documentcloud.org/documents/24133084/22-35448.pdf |title=Ritch v. American Honda Motor Co., No. 22-35448, mem. at 2 (9th Cir. Nov. 7, 2023) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-11-07 |access-date=2026-04-07 |page=2}}</ref>

==Ruling==

Ford removed ''Jones'' to the U.S. District Court for the Western District of Washington under the Class Action Fairness Act, where Judge David G. Estudillo dismissed the complaint under Federal Rule of Civil Procedure 12(b)(6) on two alternative grounds: failure to plead a qualifying statutory injury, & the conclusion that manufacturing & selling vehicles with infotainment systems did not by itself violate the WPA.<ref name="jones-p4" /><ref name="jones-p5">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 5 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=5}}</ref> Judge Estudillo also presided over the parallel Honda action, ''Ritch v. American Honda Motor Co.'', No. 3:21-cv-05706-DGE (W.D. Wash.).<ref name="ritch-p1">{{Cite web |url=https://s3.documentcloud.org/documents/24133084/22-35448.pdf |title=Ritch v. American Honda Motor Co., No. 22-35448, mem. at 1 (9th Cir. Nov. 7, 2023) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-11-07 |access-date=2026-04-07 |page=1}}</ref>

The Ninth Circuit panel of Judges Michael Daly Hawkins, Susan P. Graber, & M. Margaret McKeown first held that the plaintiffs had Article III standing because the alleged downloading & permanent storage of private communications "plausibly articulate an Article III injury because they claim violation of a substantive privacy right."<ref name="jones-p7" /> The parallel Ritch panel anchored its identical Article III holding to ''In re Facebook, Inc. Internet Tracking Litigation'', 956 F.3d 589, 598 (9th Cir. 2020), in which the Ninth Circuit had held that the alleged violation of a substantive privacy right is sufficient to confer standing at the pleading stage.<ref name="ritch-p2" />

The court then affirmed dismissal solely on the statutory ground, holding that "an invasion of privacy, without more, is insufficient to meet the statutory injury requirements of Section 9.73.060," & that the plaintiffs had failed to allege any injury to their business, person, or reputation.<ref name="jones-p8">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 8 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=8}}</ref> The panel expressly declined to reach the district court's alternative holding on manufacturing liability, noting that "our injury determination dispositively resolves this case," & observed that the plaintiffs "were given an opportunity to amend their complaint but declined to do so."<ref name="jones-p9">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 9 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=9}}</ref> In ''Ritch v. American Honda Motor Co.'', argued in Seattle on September 14, 2023, a different Ninth Circuit panel of Judges Michael Daly Hawkins, R. Nelson, & Collins affirmed dismissal of the parallel Honda action "for the same reasons" as ''Jones''.<ref name="ritch-p1" /><ref name="ritch-p2" /> The Ritch memorandum was designated non-precedential under Ninth Circuit Rule 36-3; the panel's footnote stated that the disposition "is not appropriate for publication and is not precedent except as provided by Ninth Circuit Rule 36-3."<ref name="ritch-p1" /> The ''Ritch'' memorandum identified three related actions against Volkswagen, Toyota, & General Motors (''Dornay v. Volkswagen'', No. 22-35451; ''Goussev v. Toyota'', No. 22-35454; ''McKee v. General Motors'', No. 22-35456).<ref name="ritch" /> The Ritch panel independently held that "a bare violation of the WPA is insufficient to satisfy the statutory injury requirement" & that the district court had properly dismissed the Honda plaintiffs' claim for the same reason.<ref name="ritch-p3">{{Cite web |url=https://s3.documentcloud.org/documents/24133084/22-35448.pdf |title=Ritch v. American Honda Motor Co., No. 22-35448, mem. at 3 (9th Cir. Nov. 7, 2023) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-11-07 |access-date=2026-04-07 |page=3}}</ref> The Ritch panel, like the Jones panel, declined to reach the district court's alternative holding that the WPA does not extend liability to manufacturing, observing that the injury determination "dispositively resolves this case."<ref name="ritch-p3" />

==Consumer impact==

The panel quoted Washington precedent describing the WPA as "one of the most restrictive electronic surveillance laws ever promulgated."<ref name="jones-p7" /> The ruling foreclosed civil-damages suits under RCW 9.73.060 by Washington residents who can show only that an infotainment system stored their text messages & call logs without consent, absent additional allegations of harm to their business, person, or reputation.<ref name="jones-p8" /> The underlying practice of infotainment systems copying & retaining communications from connected phones remains undisturbed by the ruling. The Jones plaintiffs declined to re-plead.<ref name="jones-p9" />

==References==
<references />

[[Category:Incidents]]
[[Category:Privacy]]
[[Category:Court Cases]]

Ford

2026-04-07T02:52:13Z

Louis: Add dedicated In-vehicle advertising patent subsection with link to Ford ad patent article

{{CompanyCargo
|Founded=1903
|Industry=Automotive
|Logo=Ford.png
|Type=Public
|Website=https://ford.com/
|Description=Automobile company which collects user data and sells it to third parties for advertising. Highest number of vehicle recalls in 2021, 2022, and 2023.
}}

The '''[[Wikipedia:Ford Motor Company|Ford Motor Company]]''' was founded in 1903 by Henry Ford in Detroit, Michigan. With the introduction of a moving assembly line, Ford drastically reduced the cost and time of automobile production, making cars affordable for the masses and transforming industrial production globally. It is one of the oldest and largest automobile manufacturers, one of the "Big Three" American automakers, alongside General Motors (GM) and Stellantis (formerly Chrysler).

==Consumer protection summary==

===User privacy===
:Ford’s data collection practices and privacy policies have raised significant concerns:
:*Extensive data collection: Ford collects a wide range of personal and vehicle data, including location, driving behavior (speed, braking), voice commands, media preferences, and even passenger information. This data is linked to the Vehicle Identification Number (VIN), which can be tied to individual users.<ref name=":0">{{Cite web |title=Privacy |url=https://www.ford.com/help/privacy/ |archive-url=http://web.archive.org/web/20260210074703/https://www.ford.com/help/privacy/ |archive-date=February 10, 2026 |website=Ford}}</ref>
:*Data collected includes purchase history, financial information, coarse and precise location data, contact information, identifiers (e.g., VIN, account ID), user-generated content (e.g., voice recordings from smart features), search and browsing history for advertising purposes, usage data, sensitive information (under "Inferences"), diagnostics, and more.<ref name=":0" />
:*Aggregates data from external sources as well, including users' social media posts.<ref name=":0" />
:*Privacy policy is designed to prevent quickly searching for important terms.<ref name=":0" />
:*Lack of transparency and control: Users are often unaware of the scope of data collection, and Ford’s policies allow sharing with affiliates, dealers, advertisers, and law enforcement. The company reserves the right to override location settings in certain circumstances (e.g., repossession, legal requests).<ref name=":3">{{Cite web |last=Elvy |first=Stacy-Ann |title=Paying for Privacy and the Personal Data Economy |url=https://www.columbialawreview.org/content/paying-for-privacy-and-the-personal-data-economy/ |website=Columbia Law Review |archive-url=http://web.archive.org/web/20251104161409/https://www.columbialawreview.org/content/paying-for-privacy-and-the-personal-data-economy/ |archive-date=4 Nov 2025}}</ref>
:*Security vulnerabilities: Past incidents, such as cybersecurity flaws in the FordPass app and exposed customer records, highlight risks of data breaches. Ford has been criticized for dismissing external reports of vulnerabilities.<ref name=":4">{{Cite web |date=August 15, 2023 |title=Ford |url=https://www.mozillafoundation.org/en/privacynotincluded/ford/ |website=mozillafoundation.org |archive-url=https://web.archive.org/web/20260223043744/https://www.mozillafoundation.org/en/privacynotincluded/ford/ |archive-date=23 Feb 2026}}</ref>
:*According to CCPA Metrics from 2023, there were 96 requests for data to be deleted, and seven of these requests were denied.<ref name=":0" />
===User freedom===
:*Limited opt-out options: Ford’s default settings opt users into data collection, with no clear path to fully delete data. Passengers and secondary drivers must also be informed of data collection, placing the burden on the primary user.<ref name=":0" />
:*Forced connectivity: Features like FordPass require data sharing for basic functionalities (e.g., remote start, tire pressure checks), limiting user choice.<ref name=":3" />
===Business model===
:*Data monetization: Ford’s business model leverages user data for targeted advertising, joint marketing, and partnerships (e.g., Sirius XM). This aligns with broader industry trends where data is a revenue driver.
:*AI and surveillance: Investments in AI (e.g., Baidu’s SYNC system in China) enable deeper user profiling, raising ethical questions about surveillance and consent.<ref>{{Cite web |last=Marr |first=Bernard |date=July 2, 2021 |title=The Amazing Ways The Ford Motor Company Uses Artificial Intelligence And Machine Learning |url=https://bernardmarr.com/the-amazing-ways-the-ford-motor-company-uses-artificial-intelligence-and-machine-learning/ |website= |archive-url=http://web.archive.org/web/20260219172306/https://bernardmarr.com/the-amazing-ways-the-ford-motor-company-uses-artificial-intelligence-and-machine-learning/ |archive-date=19 Feb 2026}}</ref>
<ref>{{Cite web |date= |title=Acquisition of Freedom Ford Sales Limited by 1911265 Alberta Ltd. |url=https://competition-bureau.canada.ca/en/how-we-foster-competition/education-and-outreach/position-statements/acquisition-freedom-ford-sales-limited-1911265-alberta-ltd |website=Competition Bureau Canada |archive-url=http://web.archive.org/web/20250820052528/https://competition-bureau.canada.ca/en/how-we-foster-competition/education-and-outreach/position-statements/acquisition-freedom-ford-sales-limited-1911265-alberta-ltd |archive-date=20 Aug 2025}}</ref>
===Market control===
:*Dealership consolidation: Ford’s acquisitions of dealerships (e.g., Freedom Ford) have drawn scrutiny from competition regulators. While deemed non-antitrust, such consolidation can reduce local competition and consumer choice.<ref name=":4" />
:*Dependence on connected services: By integrating AI and IoT (e.g., autonomous vehicles, CarStory analytics), Ford reinforces market dominance in connected car technology, potentially stifling smaller competitors.

===Anti-consumer practices===
*Patents regarding consumer data
**Ford has secured a patent for a system that is unrelated to core driving functions and involves vehicle repossession, allowing access restrictions in cases of missed payments. Ford has clarified that holding the patent does not necessarily mean it will be implemented in future products. However, the existence of such a system could influence consumer perceptions of the company and affect their willingness to accept certain sales terms.<ref name=":1">{{Cite web |last=Gitlin |first=Jonathan M. |date=March 2, 2023 |title=Ford files patent for system that could remotely repossess a car |url=https://arstechnica.com/cars/2023/03/ford-files-patent-for-system-that-could-remotely-repossess-a-car/ |archive-url=https://web.archive.org/web/20260223043817/https://arstechnica.com/cars/2023/03/ford-files-patent-for-system-that-could-remotely-repossess-a-car/ |archive-date=February 23, 2026 |website=Ars Technica}}</ref>
*Engineering practices
**Ford suffered a significant hit to its reputation regarding the Pinto, a car the company sold through the entire 1970's decade and the company's first subcompact. A number of high-profile incidents happened involving the cars getting rear-ended and subsequently lighting on fire due to the fuel tank rupturing and spilling gas; in subsequent lawsuits and criminal cases, Ford was accused of knowing the cars had a defect and deciding not to fix it based on an internal cost-benefit analysis that supposedly found it far cheaper to settle the lawsuits than actually fix the defect.
**Some engine designs use a rubber belt—rather than a metal chain—to drive the oil pump. This belt operates submerged in engine oil and may wear out prematurely, potentially leading to a sudden loss of oil pressure. Additionally, they have released transmission systems in certain ''Fiesta'' and ''Focus'' models that have experienced issues, including loss of power during acceleration, gear shifting, or at constant speeds, as well as unintended acceleration. It has been reported that a software update rendered a vehicle inoperable.<ref>{{Cite web |last=Braithwaite-Smith |first=Gavin |date=February 23, 2026 |title=BBC Watchdog shines light on Ford EcoBoost wet belt problem |url=https://garagewire.co.uk/news/bbc-watchdog-ford-ecoboost-wet-belt-problem/ |archive-url=https://web.archive.org/web/20260223043859/https://garagewire.co.uk/news/bbc-watchdog-ford-ecoboost-wet-belt-problem/ |archive-date=February 23, 2026 |website=garagewire.co.uk}}</ref><ref>{{Cite web |last=Howard |first=Phoebe Wall |date=July 11, 2019 |title=Ford knew Focus, Fiesta models had flawed transmission, sold them anyway |url=https://www.freep.com/in-depth/money/cars/ford/2019/07/11/ford-focus-fiesta-transmission-defect/1671198001/ |archive-url=http://web.archive.org/web/20260221023357/https://www.freep.com/in-depth/money/cars/ford/2019/07/11/ford-focus-fiesta-transmission-defect/1671198001/ |archive-date=February 21, 2026 |website=Detroit Free Press}}</ref><ref>{{Cite web |date=March 11, 2023 |title=Automatic Software Update Bricked my Truck |url=https://www.fordraptorforum.com/threads/automatic-software-update-bricked-my-truck.96624/ |archive-url=http://web.archive.org/web/20250415151514/https://www.fordraptorforum.com/threads/automatic-software-update-bricked-my-truck.96624/ |archive-date=April 15, 2025 |website=www.fordraptorforum.com}}</ref>
**Ford has had the highest number of vehicle recalls in the U.S. in 2021, 2022, and 2023. While recall volume can be influenced by market share, larger automakers often have more recalls, it may also reflect differences in production quality compared to competitors.<ref>{{Cite web |title=NHTSA Recalls by Manufacturer |url=https://datahub.transportation.gov/stories/s/NHTSA-Recalls-by-Manufacturer/38mw-dp8u/ |archive-url=http://web.archive.org/web/20260203181946/https://datahub.transportation.gov/stories/s/NHTSA-Recalls-by-Manufacturer/38mw-dp8u/ |archive-date=February 3, 2026 |website=datahub.transportation.gov}}</ref>

====In-vehicle advertising patent====
In February 2023, Ford filed United States patent application number 20240289844, titled "In-Vehicle Advertisement Presentation Systems and Methods."<ref name=":fordadpatent-justia">{{Cite web |date=23 Feb 2023 |title=IN-VEHICLE ADVERTISEMENT PRESENTATION SYSTEMS AND METHODS |url=https://patents.justia.com/patent/20240289844 |url-status=live |access-date=29 Mar 2025 |website=Justia Patents |archive-url=http://web.archive.org/web/20250708193151/https://patents.justia.com/patent/20240289844 |archive-date=8 Jul 2025}}</ref> The application describes a system that combines historical user data with audio signals from inside the vehicle to serve personalized advertisements through the human-machine interface, monitoring conversations between occupants to decide when, how many, and in what format to present ads.<ref name=":fordadpatent-justia" /><ref>{{Cite web |last=Smalley |first=Suzanne |date=September 9, 2024 |title=Ford seeks patent for tech that listens to driver conversations to serve ads |url=https://therecord.media/ford-patent-application-in-vehicle-listening-advertising |archive-url=http://web.archive.org/web/20260101115700/https://therecord.media/ford-patent-application-in-vehicle-listening-advertising |archive-date=January 1, 2026 |website=therecord.media}}</ref> The patent overview states that "such systems and methods further provide the opposite force to a user's natural inclination to seek minimal or no ads."<ref name=":fordadpatent-justia" /> Vehicle location and navigation data would be used to infer the user's residence or workplace and to select ads tied to commercial locations along the driver's route; current traffic data could trigger increased ad delivery during longer trips spent in congestion.<ref name=":fordadpatent-justia" /> For the full incident article, see [[Ford ad patent]].

====Lip-reading and facial expression detection patent application====
Ford Global Technologies, LLC is the named applicant on patent application US 2026/0095520 A1, titled "Systems and methods for hands-free communication in convertible vehicles," published by the United States Patent and Trademark Office on April 2, 2026.<ref name=":ford-lipread-patent">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06}}</ref> The named inventors are Keith Weston, John Robert Van Wiemeersch, Matthew Flis, and Brendan Diamond. The application was filed October 1, 2024 as application number 18/903,253. A [[:File:Ford_patent_US20260095520A1.pdf|local archive of the patent application PDF]] is hosted on this wiki.

The application describes a vehicle that detects when it is in a convertible state (top retracted, panel removed, door removed, or sunroof open) and, if cabin noise exceeds a threshold, switches its in-vehicle communication system into an enhanced mode.<ref name=":ford-lipread-patent" /> The enhanced mode can enable a lip reading mode and a gesture and facial expression detection mode. The application states that "[t]he one or more cameras of the vehicle capture the movements of the user's lips" and that the captured video is processed using machine learning algorithms trained on datasets of lip movements.<ref name=":ford-lipread-patent-p5">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06 |page=5}}</ref> It also describes a method in which "the vehicle may emit inaudible sound waves and analyze the echoes that bounce back from the user's lip and mouth" to detect facial movements.<ref name=":ford-lipread-patent-p5" /> Independent claim 16 recites storing in a database the association between each of a plurality of gestures and a corresponding verbal command. Dependent claim 17 adds the steps of detecting a gesture, looking up its corresponding command in the database, and executing that command.<ref name=":ford-lipread-patent-p9">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06 |page=9}}</ref>

The application describes storing gesture-to-command associations in a vehicle database<ref name=":ford-lipread-patent-p9" /> and transmitting generated speech or text data to the other party in a conversation,<ref name=":ford-lipread-patent-p5" /> but it does not specify whether raw lip-movement video is retained after processing, how long any captured data is kept, or whether any captured data flows to Ford's control servers or cloud infrastructure. As of the April 2, 2026 publication date, it is a published application and has not issued as a granted patent. For Ford's earlier in-vehicle data collection practices, see [[Jones v. Ford Motor Co.]].

==References==
<references />
[[Category:Ford]]

Jones v. Ford Motor Co.

2026-04-07T01:46:16Z

Louis:

{{IncidentCargo
|Company=Ford,Honda,Toyota,Volkswagen,General Motors
|StartDate=2023-10-27
|EndDate=2023-11-07
|Status=Resolved
|ProductLine=
|Product=
|ArticleType=Product
|Type=Privacy
|Description=Ford, Honda, Toyota, VW & GM infotainment systems download & store all texts & call logs from connected phones; 9th Circuit affirmed dismissal
}}
[[File:Case outcome.png|thumb]]
In ''Jones v. Ford Motor Co.'', the U.S. Court of Appeals for the Ninth Circuit on October 27, 2023 affirmed the dismissal of a putative class action alleging that '''[[Ford]] infotainment systems automatically download & permanently store text messages & call logs from any cellphone connected to the vehicle, with no way for the owner to access or delete the data.'''<ref name="jones-cover">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., No. 22-35447, slip op. (9th Cir. Oct. 27, 2023) (per curiam) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06}}</ref><ref name="jones-p4">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 4 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=4}}</ref> The per curiam published opinion held that '''those allegations satisfied Article III injury-in-fact but failed the [[Washington Privacy Act]]'s statutory damages requirement under RCW 9.73.060, which limits civil recovery to plaintiffs who can show injury to "his or her business, his or her person, or his or her reputation."'''<ref name="jones-p7">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 7 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=7}}</ref><ref name="rcw">{{Cite web |url=https://app.leg.wa.gov/rcw/default.aspx?cite=9.73.060 |title=RCW 9.73.060: Violating right of privacy. Civil action. Liability for damages |publisher=Washington State Legislature |access-date=2026-04-06}}</ref> Since nobody could claim that their reputation was damaged as a result of of the vehicle's collecting & storing user data against their will, there was no violation under the Washington Privacy Act.

A companion memorandum disposition, ''Ritch v. American Honda Motor Co.'' (Nov. 7, 2023), affirmed dismissal of the parallel [[Honda]] action "for the same reasons" as ''Jones''. The ''Ritch'' memorandum identified three related actions against [[Volkswagen]], [[Toyota]], & [[General Motors]] (''Dornay v. Volkswagen'', No. 22-35451; ''Goussev v. Toyota'', No. 22-35454; ''McKee v. General Motors'', No. 22-35456).<ref name="ritch">{{Cite web |url=https://s3.documentcloud.org/documents/24133084/22-35448.pdf |title=Ritch v. American Honda Motor Co., No. 22-35448, mem. (9th Cir. Nov. 7, 2023) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-11-07 |access-date=2026-04-06}}</ref>

==Background==

Washington residents filed five putative class actions alleging that the '''infotainment systems shipped by Ford, Honda, Toyota, Volkswagen, & General Motors automatically downloaded the call logs & text messages of any cellphone connected to the vehicle, retained those communications indefinitely on the vehicle's onboard memory after the phone was disconnected, & left owners with no way to access or delete the stored data.'''<ref name="jones-p4" /><ref name="ritch" /> '''The plaintiffs further alleged that the stored communications could be extracted by hardware & software produced by the Berla Corporation, whose products are not sold to the public & whose sales are restricted to law enforcement, the military, civil & regulatory agencies, & select private investigation service providers.'''<ref name="jones-p4" /> The five suits sought damages under the Washington Privacy Act, RCW 9.73.060, which authorizes civil recovery only for plaintiffs who can show that a violation of the statute "has injured his or her business, his or her person, or his or her reputation."<ref name="rcw" />

==Ruling==

Ford removed ''Jones'' to the U.S. District Court for the Western District of Washington under the Class Action Fairness Act, where Judge David G. Estudillo dismissed the complaint under Federal Rule of Civil Procedure 12(b)(6) on two alternative grounds: failure to plead a qualifying statutory injury, & the conclusion that manufacturing & selling vehicles with infotainment systems did not by itself violate the WPA.<ref name="jones-p4" /><ref name="jones-p5">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 5 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=5}}</ref>

The Ninth Circuit panel of Judges Michael Daly Hawkins, Susan P. Graber, & M. Margaret McKeown first held that the plaintiffs had Article III standing because the alleged downloading & permanent storage of private communications "plausibly articulate an Article III injury because they claim violation of a substantive privacy right."<ref name="jones-p7" />

The court then affirmed dismissal solely on the statutory ground, holding that "an invasion of privacy, without more, is insufficient to meet the statutory injury requirements of Section 9.73.060," & that the plaintiffs had failed to allege any injury to their business, person, or reputation.<ref name="jones-p8">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 8 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=8}}</ref> The panel expressly declined to reach the district court's alternative holding on manufacturing liability, noting that "our injury determination dispositively resolves this case," & observed that the plaintiffs "were given an opportunity to amend their complaint but declined to do so."<ref name="jones-p9">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 9 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=9}}</ref> In ''Ritch'', a separate Ninth Circuit panel affirmed dismissal of the parallel Honda action "for the same reasons" as ''Jones''. The ''Ritch'' memorandum identified three related actions against Volkswagen, Toyota, & General Motors (''Dornay v. Volkswagen'', No. 22-35451; ''Goussev v. Toyota'', No. 22-35454; ''McKee v. General Motors'', No. 22-35456).<ref name="ritch" />

==Consumer impact==

The panel quoted Washington precedent describing the WPA as "one of the most restrictive electronic surveillance laws ever promulgated."<ref name="jones-p7" /> The ruling foreclosed civil-damages suits under RCW 9.73.060 by Washington residents who can show only that an infotainment system stored their text messages & call logs without consent, absent additional allegations of harm to their business, person, or reputation.<ref name="jones-p8" /> The underlying practice of infotainment systems copying & retaining communications from connected phones remains undisturbed by the ruling. The Jones plaintiffs declined to re-plead.<ref name="jones-p9" />

==References==
<references />

[[Category:Incidents]]
[[Category:Privacy]]
[[Category:Court Cases]]

File:Case outcome.png

2026-04-07T01:45:10Z

Louis:

Automotive manufacturers collecting data without consumer consent is not a violation of the Washington Privacy Act if no reputational damage was sustained.

Jones v. Ford Motor Co.

2026-04-07T01:31:58Z

Louis: Initial publish: 9th Circuit Jones v. Ford Motor Co. (Oct. 27, 2023) per curiam affirming dismissal of Washington Privacy Act class actions over infotainment text-message and call-log capture. Companion Ritch v. American Honda memorandum. RCW 9.73.060 civil damages.

{{IncidentCargo
|Company=Ford,Honda,Toyota,Volkswagen,General Motors
|StartDate=2023-10-27
|EndDate=2023-11-07
|Status=Resolved
|ProductLine=
|Product=
|ArticleType=Product
|Type=Privacy
|Description=Ford, Honda, Toyota, VW & GM infotainment systems download & store all texts & call logs from connected phones; 9th Circuit affirmed dismissal
}}

In ''Jones v. Ford Motor Co.'', the U.S. Court of Appeals for the Ninth Circuit on October 27, 2023 affirmed the dismissal of a putative class action alleging that [[Ford]] infotainment systems automatically download & permanently store text messages & call logs from any cellphone connected to the vehicle, with no way for the owner to access or delete the data.<ref name="jones-cover">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., No. 22-35447, slip op. (9th Cir. Oct. 27, 2023) (per curiam) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06}}</ref><ref name="jones-p4">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 4 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=4}}</ref> The per curiam published opinion held that those allegations satisfied Article III injury-in-fact but failed the [[Washington Privacy Act]]'s statutory damages requirement under RCW 9.73.060, which limits civil recovery to plaintiffs who can show injury to "his or her business, his or her person, or his or her reputation."<ref name="jones-p7">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 7 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=7}}</ref><ref name="rcw">{{Cite web |url=https://app.leg.wa.gov/rcw/default.aspx?cite=9.73.060 |title=RCW 9.73.060: Violating right of privacy. Civil action. Liability for damages |publisher=Washington State Legislature |access-date=2026-04-06}}</ref> A companion memorandum disposition, ''Ritch v. American Honda Motor Co.'' (Nov. 7, 2023), affirmed dismissal of the parallel [[Honda]] action "for the same reasons" as ''Jones''. The ''Ritch'' memorandum identified three related actions against [[Volkswagen]], [[Toyota]], & [[General Motors]] (''Dornay v. Volkswagen'', No. 22-35451; ''Goussev v. Toyota'', No. 22-35454; ''McKee v. General Motors'', No. 22-35456).<ref name="ritch">{{Cite web |url=https://s3.documentcloud.org/documents/24133084/22-35448.pdf |title=Ritch v. American Honda Motor Co., No. 22-35448, mem. (9th Cir. Nov. 7, 2023) |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-11-07 |access-date=2026-04-06}}</ref>

== Background ==

Washington residents filed five putative class actions alleging that the infotainment systems shipped by Ford, Honda, Toyota, Volkswagen, & General Motors automatically downloaded the call logs & text messages of any cellphone connected to the vehicle, retained those communications indefinitely on the vehicle's onboard memory after the phone was disconnected, & left owners with no way to access or delete the stored data.<ref name="jones-p4" /><ref name="ritch" /> The plaintiffs further alleged that the stored communications could be extracted by hardware & software produced by the Berla Corporation, whose products are not sold to the public & whose sales are restricted to law enforcement, the military, civil & regulatory agencies, & select private investigation service providers.<ref name="jones-p4" /> The five suits sought damages under the Washington Privacy Act, RCW 9.73.060, which authorizes civil recovery only for plaintiffs who can show that a violation of the statute "has injured his or her business, his or her person, or his or her reputation."<ref name="rcw" />

== Ruling ==

Ford removed ''Jones'' to the U.S. District Court for the Western District of Washington under the Class Action Fairness Act, where Judge David G. Estudillo dismissed the complaint under Federal Rule of Civil Procedure 12(b)(6) on two alternative grounds: failure to plead a qualifying statutory injury, & the conclusion that manufacturing & selling vehicles with infotainment systems did not by itself violate the WPA.<ref name="jones-p4" /><ref name="jones-p5">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 5 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=5}}</ref>

The Ninth Circuit panel of Judges Michael Daly Hawkins, Susan P. Graber, & M. Margaret McKeown first held that the plaintiffs had Article III standing because the alleged downloading & permanent storage of private communications "plausibly articulate an Article III injury because they claim violation of a substantive privacy right."<ref name="jones-p7" /> The court then affirmed dismissal solely on the statutory ground, holding that "an invasion of privacy, without more, is insufficient to meet the statutory injury requirements of Section 9.73.060," & that the plaintiffs had failed to allege any injury to their business, person, or reputation.<ref name="jones-p8">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 8 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=8}}</ref> The panel expressly declined to reach the district court's alternative holding on manufacturing liability, noting that "our injury determination dispositively resolves this case," & observed that the plaintiffs "were given an opportunity to amend their complaint but declined to do so."<ref name="jones-p9">{{Cite web |url=https://cdn.ca9.uscourts.gov/datastore/opinions/2023/10/27/22-35447.pdf |title=Jones v. Ford Motor Co., slip op. at 9 |publisher=United States Court of Appeals for the Ninth Circuit |date=2023-10-27 |access-date=2026-04-06 |page=9}}</ref> In ''Ritch'', a separate Ninth Circuit panel affirmed dismissal of the parallel Honda action "for the same reasons" as ''Jones''. The ''Ritch'' memorandum identified three related actions against Volkswagen, Toyota, & General Motors (''Dornay v. Volkswagen'', No. 22-35451; ''Goussev v. Toyota'', No. 22-35454; ''McKee v. General Motors'', No. 22-35456).<ref name="ritch" />

== Consumer impact ==

The panel quoted Washington precedent describing the WPA as "one of the most restrictive electronic surveillance laws ever promulgated."<ref name="jones-p7" /> The ruling foreclosed civil-damages suits under RCW 9.73.060 by Washington residents who can show only that an infotainment system stored their text messages & call logs without consent, absent additional allegations of harm to their business, person, or reputation.<ref name="jones-p8" /> The underlying practice of infotainment systems copying & retaining communications from connected phones remains undisturbed by the ruling. The Jones plaintiffs declined to re-plead.<ref name="jones-p9" />

== References ==
<references />

[[Category:Incidents]]
[[Category:Privacy]]
[[Category:Court Cases]]

Ford

2026-04-07T00:43:37Z

Louis: Add note on US 2026/0095520 A1 (Ford lip-reading and facial-expression detection patent application, Weston et al., pub. 2026-04-02). Cross-link to Jones v. Ford Motor Co. Local archive: File:Ford_patent_US20260095520A1.pdf.

{{CompanyCargo
|Founded=1903
|Industry=Automotive
|Logo=Ford.png
|Type=Public
|Website=https://ford.com/
|Description=Automobile company which collects user data and sells it to third parties for advertising. Highest number of vehicle recalls in 2021, 2022, and 2023.
}}

The '''[[Wikipedia:Ford Motor Company|Ford Motor Company]]''' was founded in 1903 by Henry Ford in Detroit, Michigan. With the introduction of a moving assembly line, Ford drastically reduced the cost and time of automobile production, making cars affordable for the masses and transforming industrial production globally. It is one of the oldest and largest automobile manufacturers, one of the "Big Three" American automakers, alongside General Motors (GM) and Stellantis (formerly Chrysler).

==Consumer protection summary==

===User privacy===
:Ford’s data collection practices and privacy policies have raised significant concerns:
:*Extensive data collection: Ford collects a wide range of personal and vehicle data, including location, driving behavior (speed, braking), voice commands, media preferences, and even passenger information. This data is linked to the Vehicle Identification Number (VIN), which can be tied to individual users.<ref name=":0">{{Cite web |title=Privacy |url=https://www.ford.com/help/privacy/ |archive-url=http://web.archive.org/web/20260210074703/https://www.ford.com/help/privacy/ |archive-date=February 10, 2026 |website=Ford}}</ref>
:*Data collected includes purchase history, financial information, coarse and precise location data, contact information, identifiers (e.g., VIN, account ID), user-generated content (e.g., voice recordings from smart features), search and browsing history for advertising purposes, usage data, sensitive information (under "Inferences"), diagnostics, and more.<ref name=":0" />
:*Aggregates data from external sources as well, including users' social media posts.<ref name=":0" />
:*Privacy policy is designed to prevent quickly searching for important terms.<ref name=":0" />
:*Lack of transparency and control: Users are often unaware of the scope of data collection, and Ford’s policies allow sharing with affiliates, dealers, advertisers, and law enforcement. The company reserves the right to override location settings in certain circumstances (e.g., repossession, legal requests).<ref name=":3">{{Cite web |last=Elvy |first=Stacy-Ann |title=Paying for Privacy and the Personal Data Economy |url=https://www.columbialawreview.org/content/paying-for-privacy-and-the-personal-data-economy/ |website=Columbia Law Review |archive-url=http://web.archive.org/web/20251104161409/https://www.columbialawreview.org/content/paying-for-privacy-and-the-personal-data-economy/ |archive-date=4 Nov 2025}}</ref>
:*Security vulnerabilities: Past incidents, such as cybersecurity flaws in the FordPass app and exposed customer records, highlight risks of data breaches. Ford has been criticized for dismissing external reports of vulnerabilities.<ref name=":4">{{Cite web |date=August 15, 2023 |title=Ford |url=https://www.mozillafoundation.org/en/privacynotincluded/ford/ |website=mozillafoundation.org |archive-url=https://web.archive.org/web/20260223043744/https://www.mozillafoundation.org/en/privacynotincluded/ford/ |archive-date=23 Feb 2026}}</ref>
:*According to CCPA Metrics from 2023, there were 96 requests for data to be deleted, and seven of these requests were denied.<ref name=":0" />
===User freedom===
:*Limited opt-out options: Ford’s default settings opt users into data collection, with no clear path to fully delete data. Passengers and secondary drivers must also be informed of data collection, placing the burden on the primary user.<ref name=":0" />
:*Forced connectivity: Features like FordPass require data sharing for basic functionalities (e.g., remote start, tire pressure checks), limiting user choice.<ref name=":3" />
===Business model===
:*Data monetization: Ford’s business model leverages user data for targeted advertising, joint marketing, and partnerships (e.g., Sirius XM). This aligns with broader industry trends where data is a revenue driver.
:*AI and surveillance: Investments in AI (e.g., Baidu’s SYNC system in China) enable deeper user profiling, raising ethical questions about surveillance and consent.<ref>{{Cite web |last=Marr |first=Bernard |date=July 2, 2021 |title=The Amazing Ways The Ford Motor Company Uses Artificial Intelligence And Machine Learning |url=https://bernardmarr.com/the-amazing-ways-the-ford-motor-company-uses-artificial-intelligence-and-machine-learning/ |website= |archive-url=http://web.archive.org/web/20260219172306/https://bernardmarr.com/the-amazing-ways-the-ford-motor-company-uses-artificial-intelligence-and-machine-learning/ |archive-date=19 Feb 2026}}</ref>
<ref>{{Cite web |date= |title=Acquisition of Freedom Ford Sales Limited by 1911265 Alberta Ltd. |url=https://competition-bureau.canada.ca/en/how-we-foster-competition/education-and-outreach/position-statements/acquisition-freedom-ford-sales-limited-1911265-alberta-ltd |website=Competition Bureau Canada |archive-url=http://web.archive.org/web/20250820052528/https://competition-bureau.canada.ca/en/how-we-foster-competition/education-and-outreach/position-statements/acquisition-freedom-ford-sales-limited-1911265-alberta-ltd |archive-date=20 Aug 2025}}</ref>
===Market control===
:*Dealership consolidation: Ford’s acquisitions of dealerships (e.g., Freedom Ford) have drawn scrutiny from competition regulators. While deemed non-antitrust, such consolidation can reduce local competition and consumer choice.<ref name=":4" />
:*Dependence on connected services: By integrating AI and IoT (e.g., autonomous vehicles, CarStory analytics), Ford reinforces market dominance in connected car technology, potentially stifling smaller competitors.

===Anti-consumer practices===
*[[Ford ad patent|Patents regarding consumer data]]
**Ford has secured patents for systems that are unrelated to core driving functions and involve consumer data collection. One patented system can deliver targeted advertisements based on in-vehicle conversations, while another relates to vehicle repossession and allows for access restrictions (e.g., in cases of missed payments). Ford has clarified that holding these patents does not necessarily mean they will be implemented in future products. However, the existence of such systems could influence consumer perceptions of the company and affect their willingness to accept certain sales terms.<ref name=":1">{{Cite web |last=Gitlin |first=Jonathan M. |date=March 2, 2023 |title=Ford files patent for system that could remotely repossess a car |url=https://arstechnica.com/cars/2023/03/ford-files-patent-for-system-that-could-remotely-repossess-a-car/ |archive-url=https://web.archive.org/web/20260223043817/https://arstechnica.com/cars/2023/03/ford-files-patent-for-system-that-could-remotely-repossess-a-car/ |archive-date=February 23, 2026 |website=Ars Technica}}</ref><ref>{{Cite web |last=Smalley |first=Suzanne |date=September 9, 2024 |title=Ford seeks patent for tech that listens to driver conversations to serve ads |url=https://therecord.media/ford-patent-application-in-vehicle-listening-advertising |archive-url=http://web.archive.org/web/20260101115700/https://therecord.media/ford-patent-application-in-vehicle-listening-advertising |archive-date=January 1, 2026 |website=therecord.media}}</ref>
*Engineering practices
**Ford suffered a significant hit to its reputation regarding the Pinto, a car the company sold through the entire 1970's decade and the company's first subcompact. A number of high-profile incidents happened involving the cars getting rear-ended and subsequently lighting on fire due to the fuel tank rupturing and spilling gas; in subsequent lawsuits and criminal cases, Ford was accused of knowing the cars had a defect and deciding not to fix it based on an internal cost-benefit analysis that supposedly found it far cheaper to settle the lawsuits than actually fix the defect.
**Some engine designs use a rubber belt—rather than a metal chain—to drive the oil pump. This belt operates submerged in engine oil and may wear out prematurely, potentially leading to a sudden loss of oil pressure. Additionally, they have released transmission systems in certain ''Fiesta'' and ''Focus'' models that have experienced issues, including loss of power during acceleration, gear shifting, or at constant speeds, as well as unintended acceleration. It has been reported that a software update rendered a vehicle inoperable.<ref>{{Cite web |last=Braithwaite-Smith |first=Gavin |date=February 23, 2026 |title=BBC Watchdog shines light on Ford EcoBoost wet belt problem |url=https://garagewire.co.uk/news/bbc-watchdog-ford-ecoboost-wet-belt-problem/ |archive-url=https://web.archive.org/web/20260223043859/https://garagewire.co.uk/news/bbc-watchdog-ford-ecoboost-wet-belt-problem/ |archive-date=February 23, 2026 |website=garagewire.co.uk}}</ref><ref>{{Cite web |last=Howard |first=Phoebe Wall |date=July 11, 2019 |title=Ford knew Focus, Fiesta models had flawed transmission, sold them anyway |url=https://www.freep.com/in-depth/money/cars/ford/2019/07/11/ford-focus-fiesta-transmission-defect/1671198001/ |archive-url=http://web.archive.org/web/20260221023357/https://www.freep.com/in-depth/money/cars/ford/2019/07/11/ford-focus-fiesta-transmission-defect/1671198001/ |archive-date=February 21, 2026 |website=Detroit Free Press}}</ref><ref>{{Cite web |date=March 11, 2023 |title=Automatic Software Update Bricked my Truck |url=https://www.fordraptorforum.com/threads/automatic-software-update-bricked-my-truck.96624/ |archive-url=http://web.archive.org/web/20250415151514/https://www.fordraptorforum.com/threads/automatic-software-update-bricked-my-truck.96624/ |archive-date=April 15, 2025 |website=www.fordraptorforum.com}}</ref>
**Ford has had the highest number of vehicle recalls in the U.S. in 2021, 2022, and 2023. While recall volume can be influenced by market share, larger automakers often have more recalls, it may also reflect differences in production quality compared to competitors.<ref>{{Cite web |title=NHTSA Recalls by Manufacturer |url=https://datahub.transportation.gov/stories/s/NHTSA-Recalls-by-Manufacturer/38mw-dp8u/ |archive-url=http://web.archive.org/web/20260203181946/https://datahub.transportation.gov/stories/s/NHTSA-Recalls-by-Manufacturer/38mw-dp8u/ |archive-date=February 3, 2026 |website=datahub.transportation.gov}}</ref>

====Lip-reading and facial expression detection patent application====
Ford Global Technologies, LLC is the named applicant on patent application US 2026/0095520 A1, titled "Systems and methods for hands-free communication in convertible vehicles," published by the United States Patent and Trademark Office on April 2, 2026.<ref name=":ford-lipread-patent">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06}}</ref> The named inventors are Keith Weston, John Robert Van Wiemeersch, Matthew Flis, and Brendan Diamond. The application was filed October 1, 2024 as application number 18/903,253. A [[:File:Ford_patent_US20260095520A1.pdf|local archive of the patent application PDF]] is hosted on this wiki.

The application describes a vehicle that detects when it is in a convertible state (top retracted, panel removed, door removed, or sunroof open) and, if cabin noise exceeds a threshold, switches its in-vehicle communication system into an enhanced mode.<ref name=":ford-lipread-patent" /> The enhanced mode can enable a lip reading mode and a gesture and facial expression detection mode. The application states that "[t]he one or more cameras of the vehicle capture the movements of the user's lips" and that the captured video is processed using machine learning algorithms trained on datasets of lip movements.<ref name=":ford-lipread-patent-p5">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06 |page=5}}</ref> It also describes a method in which "the vehicle may emit inaudible sound waves and analyze the echoes that bounce back from the user's lip and mouth" to detect facial movements.<ref name=":ford-lipread-patent-p5" /> Independent claim 16 recites storing in a database the association between each of a plurality of gestures and a corresponding verbal command. Dependent claim 17 adds the steps of detecting a gesture, looking up its corresponding command in the database, and executing that command.<ref name=":ford-lipread-patent-p9">{{Cite web |url=https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20260095520 |title=Systems and methods for hands-free communication in convertible vehicles (US 2026/0095520 A1) |last=Weston |first=Keith |author2=Van Wiemeersch, John Robert |author3=Flis, Matthew |author4=Diamond, Brendan |publisher=United States Patent and Trademark Office |date=2026-04-02 |access-date=2026-04-06 |page=9}}</ref>

The application describes storing gesture-to-command associations in a vehicle database<ref name=":ford-lipread-patent-p9" /> and transmitting generated speech or text data to the other party in a conversation,<ref name=":ford-lipread-patent-p5" /> but it does not specify whether raw lip-movement video is retained after processing, how long any captured data is kept, or whether any captured data flows to Ford's control servers or cloud infrastructure. As of the April 2, 2026 publication date, it is a published application and has not issued as a granted patent. For Ford's earlier in-vehicle data collection practices, see [[Jones v. Ford Motor Co.]].

==References==
<references />
[[Category:Ford]]

File:Ford patent US20260095520A1.pdf

2026-04-07T00:43:10Z

Louis: Uploading US Patent Application Publication 2026/0095520 A1 (Weston et al., Ford Global Technologies, filed 2024-10-01, published 2026-04-02). Local archive of primary source for the Ford page section on lip-reading and facial-expression detection in convertible vehicles.

== Summary ==
United States Patent Application Publication '"Systems and methods for hands-free communication in convertible vehicles,"' US 2026/0095520 A1. Applicant: Ford Global Technologies, LLC. Inventors: Keith Weston, John Robert Van Wiemeersch, Matthew Flis, Brendan Diamond. Filed October 1, 2024 as application number 18/903,253

Formlabs

2026-04-06T00:21:58Z

Louis: Fix citation-claim mismatches: add 3dprint cite for $2999, fix $250M->$230M to match Wikipedia source, fix duplicate ref definition

{{#seo:description=Formlabs charges $875-$11,899 per printer to use third-party materials, acquired & killed a $2,999 SLS competitor, and obsoleted the Form 2 via resin DRM.}}
{{CompanyCargo
|Founded=2011
|Industry=3D printing
|Logo=Formlabs logo.svg
|ParentCompany=
|CompanyAlias=
|Type=Private
|Website=https://formlabs.com
|Description=Charges $875-$11,899 per printer to use third-party materials; acquired & canceled a $2,999 SLS competitor to protect its $28,989 Fuse 1+
}}

'''Formlabs''' is a 3D printing company that charges its customers $875 to $11,899 per printer for the permission to use third-party materials on hardware they already own.<ref name="formlabs-omm-store">{{Cite web |title=Open Material Mode |url=https://formlabs.com/store/materials/open-material-mode/ |website=Formlabs |access-date=2026-04-04 |url-status=live |archive-url=https://web.archive.org/web/20260116171208/https://formlabs.com/store/materials/open-material-mode/ |archive-date=2026-01-16}}</ref> In July 2024, Formlabs acquired Micronics, a startup building a $2,999 desktop SLS printer funded on Kickstarter, & immediately canceled the product.<ref name="formlabs-acquires-micronics">{{Cite web |title=Formlabs Acquires Micronics to Develop the Next Generation of Accessible SLS |url=https://formlabs.com/blog/formlabs-acquires-micronics/ |website=Formlabs |date=2024-07-11}}</ref><ref name="3dprint-micronics">{{Cite web |title=Formlabs Buys Nascent SLS 3D Printer Competitor Micronics |url=https://3dprint.com/311327/formlabs-buys-nascent-sls-3d-printer-competitor-micronics/ |website=3DPrint.com |date=2024-07-11}}</ref> The cheapest SLS printer Formlabs sells starts at $28,989; the Micron would have cost roughly 1/10th that price.<ref name="formlabs-sls-pricing">{{Cite web |title=How to Compare SLS 3D Printer Prices |url=https://formlabs.com/blog/selective-laser-sintering-sls-3d-printer-price/ |website=Formlabs |access-date=2026-04-04}}</ref><ref name="3dprint-micronics" /> Founded in 2011 by MIT Media Lab students Maxim Lobovsky, David Cranor, & Natan Linder, the company raised $2.95 million on Kickstarter for its first printer & has since raised over $230 million in venture funding.<ref name="wikipedia-formlabs">{{Cite web |title=Formlabs |url=https://en.wikipedia.org/wiki/Formlabs |website=Wikipedia |access-date=2026-04-04}}</ref>

== Consumer-impact summary ==

* Formlabs charges a per-printer license fee ranging from $875 (Form 4) to $11,899 (Fuse 1 series) for the permission to use third-party materials on hardware the customer already owns.<ref name="formlabs-omm-store" />
* The company acquired Micronics in July 2024 & canceled the Micron, a $2,999 SLS 3D printer that had raised over £1 million from 431 Kickstarter backers.<ref name="3dprint-micronics" /><ref name="develop3d-micronics" /> Formlabs' own SLS printer, the Fuse 1+ 30W, starts at $28,989.<ref name="formlabs-sls-pricing" />
* The Form 2 uses proprietary DRM-chipped resin cartridges. Formlabs committed to supplying consumables through 2023, then left the end date ambiguous; by September 2024 consumables were still available but with no guaranteed supply timeline.<ref name="formlabs-forum-form2-support">{{Cite web |title=Ongoing Support for the Form 2 |url=https://forum.formlabs.com/t/ongoing-support-for-the-form-2/22871 |website=Formlabs Community Forum |date=2019-04}}</ref><ref name="formlabs-forum-form2-consumables">{{Cite web |title=Form 2 availability of consumables |url=https://forum.formlabs.com/t/form-2-availability-of-consumables/39108 |website=Formlabs Community Forum |date=2024-09}}</ref>

== Incidents ==

This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:Formlabs|Formlabs category]].

=== Acquisition of Micronics ===

Formlabs acquired Micronics on July 11, 2024, & canceled the Micron desktop SLS 3D printer the same day.<ref name="formlabs-acquires-micronics" /> The Micron had launched on Kickstarter in June 2024 at a starting price of $2,999.<ref name="3dprint-micronics" /> The campaign raised over £1 million from 431 backers.<ref name="develop3d-micronics">{{Cite web |title=Desktop SLS start-up Micronics acquired by Formlabs |url=https://develop3d.com/3d-printing/desktop-sls-company-micronics-acquired-by-formlabs/ |website=Develop3D |date=2024-07-11}}</ref>

SLS (Selective Laser Sintering) printers use a laser to fuse nylon powder into parts without support structures. Traditional industrial SLS machines from manufacturers like EOS & 3D Systems cost $200,000 to $500,000 or more.<ref name="formlabs-sls-pricing" /> Formlabs' own SLS offering, the Fuse 1+ 30W, starts at $28,989.<ref name="formlabs-sls-pricing" /> The Micron at $2,999 would have undercut the Fuse 1+ 30W by roughly 10x.<ref name="3dprint-micronics" />

Formlabs CEO Max Lobovsky acknowledged this price gap in an interview with TechCrunch, stating that Formlabs had achieved a "5x leap in starting price" with the Fuse 1 & that Micronics was "trying to do another 5x beyond that."<ref name="techcrunch-micronics">{{Cite web |title=Formlabs acquires 3D printing startup Micronics mid-Kickstarter campaign |url=https://techcrunch.com/2024/07/11/formlabs-acquires-3d-printing-startup-micronics-mid-kickstarter-campaign/ |website=TechCrunch |date=2024-07-11}}</ref> Micronics founders Henry Chan & Luke Boppart joined the Formlabs engineering team at its Somerville, Massachusetts headquarters.<ref name="formlabs-press-micronics">{{Cite web |title=Formlabs Acquires Micronics to Further Advance Accessible SLS 3D Printing |url=https://formlabs.com/company/press/formlabs-acquires-micronics/ |website=Formlabs |date=2024-07-11}}</ref> The Micronics brand was discontinued & the Kickstarter was canceled.<ref name="techcrunch-micronics" />

Tom's Hardware headlined its coverage "David vs Goliath" & reported that the Micronics branding would be discontinued.<ref name="tomshardware-micronics">{{Cite web |title=David vs Goliath: Desktop SLS Kickstarter Ends with Acquisition |url=https://www.tomshardware.com/3d-printing/david-vs-goliath-desktop-sls-kickstarter-ends-with-acquisition |website=Tom's Hardware |first=Denise |last=Bertacchi |date=2024-07-11}}</ref> 3D Printing Industry reported the acquisition as producing "new accessible SLS 3D printers forthcoming," but no such product has shipped as of April 2026.<ref name="3dprintingindustry-micronics">{{Cite web |title=Formlabs acquires Micronics, new accessible SLS 3D printers forthcoming |url=https://3dprintingindustry.com/news/formlabs-acquires-micronics-new-accessible-sls-3d-printers-forthcoming-231608/ |website=3D Printing Industry |date=2024-07-11}}</ref>

Formlabs offered backers a full refund plus a $1,000 credit toward any current or future Formlabs printer & a free Open Material License.<ref name="formlabs-press-micronics" /><ref name="formlabs-forum-backer-breach" /> By December 2024, backers reported on the Formlabs forum that the promised $1,000 credit had not been delivered months after submission. Some backers who attempted to use their credit toward a Fuse 1 purchase were denied a $5,000 discount for unspecified reasons. The forum thread was auto-closed in July 2025.<ref name="formlabs-forum-backer-breach">{{Cite web |title=Formlabs' breach of promised Open Material License and $1000 credit to Micronics Kickstarter Backer |url=https://forum.formlabs.com/t/formlabs-breach-of-promised-open-material-license-and-1000-credit-to-micronics-kickstarter-backer/40715 |website=Formlabs Community Forum |date=2024-12-27}}</ref> A $1,000 credit toward a $28,989 SLS printer represents a 3.4% discount for backers who had pledged for a $2,999 machine.

=== Open Material Mode ===

Formlabs requires a one-time per-printer software license to unlock the use of third-party resins & powders on its printers. The license, called Open Material Mode, costs $875 for the Form 4, $1,999 for the Form 3 series, $2,499 for the Form 4B, $3,999 for the Form 3L series, $4,999 for the Form 4L, & $11,899 for the Fuse 1 series.<ref name="formlabs-omm-store" /> Without the license, users can only load Formlabs' proprietary DRM-chipped resin cartridges.

Formlabs users on the company's own forum called the pricing "anti-consumer" & argued that the correct price should be zero, noting that competing desktop printers accept third-party materials without restriction.<ref name="formlabs-forum-oml-6k">{{Cite web |title=Open Material License $6k per printer |url=https://forum.formlabs.com/t/open-material-license-6k-per-printer/36905 |website=Formlabs Community Forum |date=2023-09-12}}</ref> Formlabs initially proposed pricing as high as $6,000 per printer for the Form 3 series in September 2023; community backlash led to the current tiered pricing structure.<ref name="formlabs-forum-oml-6k" />

The license is free for accredited educational institutions.<ref name="formlabs-omm-store" /> As of January 2026, Open Material Mode is included with new Form 4B & 4BL purchases, but owners who bought the same printers before that date must pay the full license fee.<ref name="formlabs-forum-4b-omm">{{Cite web |title=PSA to All form Form 4B & 4BL owners (Open material mode) |url=https://forum.formlabs.com/t/psa-to-all-form-form-4b-4bl-owners-open-material-mode/46199 |website=Formlabs Community Forum |date=2026-01}}</ref> Formlabs' warranty terms state that failure modes caused by third-party materials are excluded from standard warranty coverage, adding financial risk on top of the license cost.<ref name="formlabs-omm-store" />

=== Form 2 deprecation ===

Formlabs announced the end of active support for the Form 2 in April 2019, following the launch of the Form 3 series. The company committed to selling resin tanks, cartridges, & build platforms through at least 2023.<ref name="formlabs-forum-form2-support" /> The Form 2 uses proprietary DRM-chipped resin cartridges. Without an authorized cartridge, the printer runs in a limited mode that disables the heater & wiper functions, reducing print quality.<ref name="protoart-cartridge" />

By September 2024, nine months past the stated deadline, Form 2 consumables were still available but Formlabs hadn't provided a firm end date. Users requested concrete timelines to plan investment decisions; Formlabs didn't respond in the thread.<ref name="formlabs-forum-form2-consumables" /> Once Formlabs stops selling Form 2-compatible cartridges, owners of the $3,500 printer will have no official consumable supply. The printer becomes unusable even though the hardware itself still works.<ref name="formlabs-forum-form2-support" />

Third-party developers attempted workarounds. ProtoART produced a Universal Cartridge, a DIY modification kit installed into an existing cartridge that allowed third-party resin use with heater & wiper functions enabled.<ref name="protoart-cartridge">{{Cite web |title=A Universal Cartridge For Form 2 3D Printers, But Should You Use It? |url=https://www.fabbaloo.com/2019/09/a-universal-cartridge-for-form-2-3d-printers-but-should-you-use-it |website=Fabbaloo |date=2019-09}}</ref> The Universal Cartridge is compatible only with Formlabs firmware versions through 2.2.0; the product reached end of life & is available only while supplies last.<ref name="protoart-site">{{Cite web |title=Universal Cartridge Module for Formlabs |url=https://www.lectronz.com/products/universal-cartridge-for-formlabs-form-2-form-3 |website=Lectronz |access-date=2026-04-04}}</ref>

== Products ==

* '''SLA printers:''' Form 1, Form 1+, Form 2, Form 3 series (Form 3, 3+, 3B, 3B+, 3L, 3BL), Form 4 series (Form 4, 4B, 4L, 4BL)
* '''SLS printers:''' Fuse 1, Fuse 1+ 30W
* '''Software:''' PreForm (slicing & print preparation)
* '''Post-processing:''' Form Wash, Form Cure
* '''Automation:''' Form Auto, Form Cell

== See also ==

* [[Bambu Lab]]
* [[Creality]]
* [[MakerBot]]

== References ==

{{reflist}}

[[Category:Formlabs]]
[[Category:3D Printing]]
[[Category:Planned Obsolescence]]

Formlabs acquisition of Micronics

2026-04-06T00:21:49Z

Louis: Fix citation-claim mismatches: reassign lede credit cite from 3dprint to 3dnatives+fuse-pricing, add micronics-faq cite for OML promise, remove fabricated geographic restrictions claim, correct SLS4All price 3860->3990, remove unverifiable 35000 from Cunningham, fix DOJ date

{{#seo:
|description=Formlabs acquired Micronics in July 2024, canceling the $2,999 Micron desktop SLS printer mid-Kickstarter and eliminating the cheapest turnkey SLS printer from the market.
}}
{{IncidentCargo
|Company=Formlabs
|StartDate=2024-07-11
|EndDate=
|Status=Resolved
|ProductLine=
|Product=
|ArticleType=Product
|Type=Anti-competitive practices
|Description=Formlabs acquired Micronics mid-Kickstarter, canceled the $2,999 Micron SLS printer, eliminating the cheapest turnkey SLS option from the market
}}
The cheapest turnkey desktop [[Selective laser sintering|SLS]] 3D printer on the market was canceled when [[Formlabs]] acquired its maker, Micronics, on July 11, 2024.<ref name="formlabs-press">{{Cite web |url=https://formlabs.com/company/press/formlabs-acquires-micronics/ |title=Formlabs Acquires Micronics to Further Advance Accessible SLS 3D Printing |date=2024-07-11 |access-date=2026-04-04 |website=Formlabs}}</ref> The Micron printer had raised $1,357,939 from 431 backers on Kickstarter at a starting price of $2,999;<ref name="3dnatives">{{Cite web |url=https://www.3dnatives.com/en/formlabs-announces-major-move-with-micronics-acquisition-110720246/ |title=Formlabs Make Major Move With Micronics Acquisition |author=Madeleine Prior |date=2024-07-11 |access-date=2026-04-04 |website=3Dnatives}}</ref><ref name="kickstarter">{{Cite web |url=https://www.kickstarter.com/projects/micronics3d/micron-a-desktop-sls-3d-printer |title=Micron: A Desktop SLS 3D Printer (Canceled) |access-date=2026-04-04 |website=Kickstarter}}</ref> Formlabs' cheapest SLS printer, the Fuse 1+ 30W, starts at $24,999.<ref name="fuse-pricing">{{Cite web |url=https://formlabs.com/blog/fuse-depowdering-kit/ |title=Your Entryway to Industrial SLS 3D Printing With an All-in-One System at $24,999 |access-date=2026-04-04 |website=Formlabs}}</ref> Backers received full refunds & a $1,000 credit toward Formlabs printers, a discount of roughly 4% on the cheapest available SLS system.<ref name="3dnatives" /><ref name="fuse-pricing" />

== Background ==

=== SLS technology & the price barrier ===

Selective laser sintering uses a laser to fuse polymer powder into solid parts layer by layer. Unlike FDM or resin printing, SLS requires no support structures because unfused powder surrounds each part during the build. This allows complex geometries & dense part nesting across the full build volume.<ref name="hackster">{{Cite web |url=https://www.hackster.io/news/micron-brings-sls-3d-printing-to-the-desktop-2b8780632541 |title=Micron Brings SLS 3D Printing to the Desktop |date=2024-06 |access-date=2026-04-04 |website=Hackster.io}}</ref> SLS parts are printed in engineering thermoplastics like Nylon PA12, producing components that are isotropic, chemically resistant, & mechanically strong enough for end-use applications.<ref name="3dpi-specs">{{Cite web |url=https://3dprintingindustry.com/news/micronics-unveils-its-innovative-sls-3d-printer-offering-230956/ |title=Micronics unveils its innovative SLS 3D printer offering |date=2024-06 |access-date=2026-04-04 |website=3D Printing Industry}}</ref>

These advantages come at a cost. Desktop SLS machines have historically required high-wattage CO2 or fiber lasers, multi-zone thermal management systems, & enclosed powder handling with HEPA filtration to mitigate inhalation hazards. Before 2024, the cheapest fully assembled desktop SLS printer was the Sinterit Lisa at roughly $13,990.<ref name="3dsourced">{{Cite web |url=https://www.3dsourced.com/3d-printers/sls-3d-printer/ |title=Best Lower-Cost Desktop SLS 3D Printers in 2024 |date=2024 |access-date=2026-04-04 |website=3DSourced}}</ref> Formlabs' Fuse 1+ 30W starter package costs $24,999.<ref name="fuse-pricing" />

=== Micronics & the Micron ===

Micronics was founded in 2021 by Henry Chan & Luke Boppart, both 2023 graduates of the University of Wisconsin-Madison.<ref name="tomshardware">{{Cite web |url=https://www.tomshardware.com/3d-printing/david-vs-goliath-desktop-sls-kickstarter-ends-with-acquisition |title=David vs Goliath: Desktop SLS Kickstarter Ends with Acquisition |author=Denise Bertacchi |date=2024-07-11 |access-date=2026-04-04 |website=Tom's Hardware}}</ref><ref name="3dprinting-com">{{Cite web |url=https://3dprinting.com/news/formlabs-acquires-micronics-mid-kickstarter-campaign/ |title=Formlabs Acquires Micronics Mid-Kickstarter Campaign |date=2024-07-11 |access-date=2026-04-04 |website=3DPrinting.com}}</ref> The two-person startup developed the Micron, a desktop SLS printer with a 160 x 160 x 205 mm build volume, a 5-watt 447 nm CW diode laser, & support for PA12 nylon & TPU-90A at launch.<ref name="micron-specs">{{Cite web |url=https://www.micronics3d.com/micron |title=Micron Desktop SLS 3D Printer |access-date=2026-04-04 |website=Micronics}}</ref> The machine weighed 19 kg & ran on standard household power, fitting on a desktop rather than requiring a dedicated workshop.<ref name="micron-specs" />

By using a cheap blue diode laser instead of an expensive CO2 unit, Micronics cut the starting price to $2,999 with a planned retail price of $4,499.<ref name="micron-specs" /><ref name="kickstarter" /> The Kickstarter campaign launched on June 13, 2024 with a $100,000 goal.<ref name="kickstarter" /> It raised $1,357,939 from 431 backers before being canceled.<ref name="3dnatives" /><ref name="develop3d">{{Cite web |url=https://develop3d.com/3d-printing/desktop-sls-company-micronics-acquired-by-formlabs/ |title=Desktop SLS start-up Micronics acquired by Formlabs |date=2024-07-11 |access-date=2026-04-04 |website=Develop3D}}</ref> A Kickstarter bundle including the printer, a removable build chamber, & a post-processing kit was available for $3,699 with an estimated delivery date of June 2025.<ref name="hackster" />

Formlabs CEO Max Lobovsky acknowledged the price gap between the two companies' products: "With the Fuse 1, we made a 5x leap in starting price for SLS systems. Micronics is trying to do another 5x beyond that."<ref name="3dprinting-com" />

== Acquisition ==

On July 11, 2024, Formlabs announced it had acquired Micronics.<ref name="formlabs-press" /> The deal came together rapidly. Lobovsky met Chan & Boppart for the first time at Open Sauce 2024.<ref name="formlabs-press" /><ref name="3dprinting-com" /> Lobovsky stated: "After meeting the Micronics co-founders at Open Sauce 2024, we discovered our shared vision for accessible, powerful 3D printing."<ref name="formlabs-press" />

The acquisition price was not disclosed. Both founders joined Formlabs. Chan took a role leading the SLS team; Boppart joined the software team.<ref name="3dnatives" /><ref name="develop3d" />

The Micron was immediately & permanently canceled. Micronics' FAQ page stated: "Will you continue to build Micronics? No. Instead of focusing on Micronics the company and Micron the product, we will be joining Formlabs to bring the next generation of accessible SLS printers to market."<ref name="micronics-faq">{{Cite web |url=https://www.micronics3d.com/learn-more |title=Learn More |access-date=2026-04-04 |website=Micronics}}</ref> Formlabs at the time claimed its Fuse 1 Series accounted for more than half of all powder bed fusion printers sold worldwide.<ref name="formlabs-press" />

=== Backer compensation ===

The Kickstarter campaign was canceled before its scheduled end date, so backers received automatic full refunds.<ref name="3dprint" /> Formlabs initially promised backers a $1,000 credit toward "any current or future printer" & a free Open Materials License for Formlabs machines.<ref name="3dnatives" /><ref name="micronics-faq" />

By late 2024, backers reported the terms had shifted. The Formlabs blog was edited to offer a discounted legacy Fuse 1 at $9,999 to Micronics backers while stock lasted, with the $1,000 credit applicable to that purchase.<ref name="formlabs-forum">{{Cite web |url=https://forum.formlabs.com/t/formlabs-breach-of-promised-open-material-license-and-1000-credit-to-micronics-kickstarter-backer/40715 |title=Formlabs' breach of promised Open Material License and $1000 credit to Micronics Kickstarter Backer |date=2024-12 |access-date=2026-04-04 |website=Formlabs Community Forum}}</ref> The blog later added a note stating the "credit period has now ended," closing the redemption window entirely.<ref name="formlabs-blog">{{Cite web |url=https://formlabs.com/blog/formlabs-acquires-micronics/ |title=Formlabs Acquires Micronics to Develop the Next Generation of Accessible SLS |date=2024-07-11 |access-date=2026-04-04 |website=Formlabs}}</ref> A Formlabs forum thread documented complaints from backers who reported that the promised credit had not been delivered months after submission and that one backer was denied a $5,000 discount on a Fuse 1 purchase for unspecified reasons.<ref name="formlabs-forum" />

=== Formlabs' stated rationale ===

Formlabs framed the acquisition as an "acqui-hire" that would accelerate development of affordable SLS technology. Henry Chan stated: "We are thrilled to join forces with Formlabs, a company we have long admired. After the outpouring of excitement around our Kickstarter, we're confident that this move will enable us to bring the best SLS 3D printing experience to users around the world."<ref name="formlabs-press" /> David Lakatos, Formlabs' Chief Product Officer, said: "What makes us so excited about Henry and Luke is that they embody the very people we make our products for."<ref name="develop3d" />

Chan explained that scaling a hardware startup with two people was difficult, citing frustration with spending time on packaging & marketing instead of engineering.<ref name="tomshardware" />

== Consumer impact ==

=== Price gap ===

The math does not work in backers' favor. Those who pledged for a $2,999-$3,699 printer received a $1,000 credit toward machines starting at $24,999. Even with the temporarily discounted Fuse 1 offer at $9,999, the out-of-pocket cost was still roughly 3x the Micron's Kickstarter price. For the current Fuse 1+ 30W starter package, the $1,000 credit covers about 4% of the purchase price.<ref name="fuse-pricing" /><ref name="formlabs-forum" />

Formlabs' Open Material Mode, which allows its printers to use third-party powder instead of proprietary materials, is a one-time per-printer license starting at $1,999 for the Form 3 & rising to $2,499 or more for newer models.<ref name="formlabs-oml">{{Cite web |url=https://formlabs.com/store/materials/open-material-mode/ |title=Open Material Mode |access-date=2026-04-04 |website=Formlabs}}</ref> On Hacker News, commenters noted the license alone costs "basically the same price as Micronics printer."<ref name="hn">{{Cite web |url=https://news.ycombinator.com/item?id=40936741 |title=Micronics Acquired by Formlabs |date=2024-07-11 |access-date=2026-04-04 |website=Hacker News}}</ref>

=== Market vacuum ===

As of April 2026, no manufacturer has released a sub-$5,000 turnkey SLS printer. The cheapest fully assembled commercial SLS options remain the Sinterit Lisa series (starting around $13,990) & the Formlabs Fuse 1+ 30W ($24,999).<ref name="3dsourced" /><ref name="fuse-pricing" /> The open-source SLS4All Inova MK1 is available as a DIY parts kit for roughly $3,990, but requires extensive user assembly & electrical wiring.<ref name="gemini-sls4all">{{Cite web |url=https://www.sls4all.com/ |title=SLS4All |access-date=2026-04-04 |website=SLS4All}}</ref>

Formlabs has not released any new SLS hardware since the acquisition. The company's 2025 year in review & Spring 2025 product announcements focused on resin printing materials & curing equipment; no Micronics-derived SLS product was mentioned.<ref name="formlabs-2025">{{Cite web |url=https://formlabs.com/blog/2025-year-in-review/ |title=Formlabs Year in Review: 2025 Highlights |access-date=2026-04-04 |website=Formlabs}}</ref>

== Community response ==

The 3D printing community's reaction was overwhelmingly negative. ''Tom's Hardware'' summarized: "You could say that Micronic's Kickstarter project is a smashing success, at least for the two young engineers who dreamed of building a next-generation 3D printer out of their college apartment. Their Kickstarter backers have a different opinion."<ref name="tomshardware" />

On Hacker News, users described the acquisition as having "killed a potential competitor in the cradle for cheap" & criticized Formlabs' material lock-in, noting the printers are "locked to 1st party materials by default."<ref name="hn" /> Across online forums, backers accused Formlabs of buying Micronics to remove competition rather than integrate the technology, lamenting that "we won't have a hobby level SLS printer in the near future."<ref name="hn" />

''VoxelMatters'' drew an explicit competitive parallel: "This sure does look like Formlabs crushing a small competitor, in a way that is very similar to the way Microsoft rose to market dominance."<ref name="voxelmatters">{{Cite web |url=https://www.voxelmatters.com/formlabs-acquires-micronics/ |title=Formlabs acquires Micronics |date=2024-07 |access-date=2026-04-04 |website=VoxelMatters}}</ref>

Joris Peels of ''3DPrint.com'' was more skeptical of the Micron itself, describing the $2,999 price point as "improbably low" & questioning whether a two-person team could scale a powder bed fusion system to production. He praised the team's engineering, particularly the removable build chambers & depowdering solution, but suggested the acquisition may have prevented a "Kickstarter fracas" if the product could not be delivered at the promised price.<ref name="3dprint">{{Cite web |url=https://3dprint.com/311327/formlabs-buys-nascent-sls-3d-printer-competitor-micronics/ |title=Formlabs Buys Nascent SLS 3D Printer Competitor Micronics |author=Joris Peels |date=2024-07-11 |access-date=2026-04-04 |website=3DPrint.com}}</ref>

== Killer acquisition pattern ==

The Formlabs-Micronics acquisition fits the pattern described in antitrust economics as a "killer acquisition," where an incumbent firm acquires a startup to discontinue its product & prevent competitive disruption.<ref name="cunningham">{{Cite web |url=https://www.journals.uchicago.edu/doi/abs/10.1086/712506 |title=Killer Acquisitions |author=Colleen Cunningham, Florian Ederer, and Song Ma |date=2021-03 |website=Journal of Political Economy |access-date=2026-04-04}}</ref> The term was formalized by Cunningham, Ederer, & Ma in a 2021 ''Journal of Political Economy'' study of pharmaceutical drug acquisitions. They found that 5.3% to 7.4% of acquisitions in their sample were killer acquisitions, & that these deals disproportionately occurred just below the thresholds for antitrust scrutiny.<ref name="cunningham" />

The Formlabs-Micronics deal shares key characteristics with this pattern. The incumbent (Formlabs, claiming over 50% of worldwide powder bed fusion sales)<ref name="formlabs-press" /> acquired a direct competitor (Micronics) whose product overlapped with the incumbent's product line but at a fraction of the price. The acquired product was immediately discontinued.<ref name="micronics-faq" /> No replacement product at a comparable price point has been released as of April 2026.<ref name="formlabs-2025" />

The 2024 Hart-Scott-Rodino Act threshold for mandatory pre-merger FTC review was $119.5 million.<ref name="hsr-2024">{{Cite web |url=https://www.jonesday.com/en/insights/2024/02/us-merger-notification-threshold-increases-to-1195-million |title=US Merger Notification Threshold Increases to $119.5 Million |date=2024-02 |access-date=2026-04-04 |website=Jones Day}}</ref> A startup that raised $1.3 million on Kickstarter fell well below that line.<ref name="3dnatives" /> No FTC or DOJ filing related to the acquisition has been publicly reported.<ref name="ftc-hsr">{{Cite web |url=https://www.ftc.gov/system/files/attachments/us-submissions-oecd-2010-present-other-international-competition-fora/oecd-killer_acquisiitions_us_submission.pdf |title=Start-ups, killer acquisitions and merger control |access-date=2026-04-04 |website=Federal Trade Commission}}</ref>

The 3D printing industry has faced antitrust scrutiny before. In 2001, the U.S. Department of Justice sued to block the merger of 3D Systems & DTM, arguing it would reduce the rapid prototyping market from three competitors to two. The merger was allowed only after the companies agreed to license their rapid prototyping patent portfolios to a competitor.<ref name="doj-3dsystems">{{Cite web |url=https://www.justice.gov/archive/atr/public/press_releases/2001/8810.htm |title=Justice Department Requires Divestitures in 3D Systems/DTM Merger |date=2001-08-16 |access-date=2026-04-04 |website=U.S. Department of Justice}}</ref>

== References ==
{{reflist}}

[[Category:Formlabs]]
[[Category:Anti-competitive practices]]
[[Category:3D printing]]
[[Category:2024 incidents]]

Formlabs acquisition of Micronics

2026-04-05T23:14:06Z

Louis: New incident article: Formlabs July 2024 acquisition & cancellation of Micronics desktop SLS printer, killer acquisition pattern, backer compensation issues

{{#seo:
|description=Formlabs acquired Micronics in July 2024, canceling the $2,999 Micron desktop SLS printer mid-Kickstarter and eliminating the cheapest turnkey SLS printer from the market.
}}
{{IncidentCargo
|Company=Formlabs
|StartDate=2024-07-11
|EndDate=
|Status=Resolved
|ProductLine=
|Product=
|ArticleType=Product
|Type=Anti-competitive practices
|Description=Formlabs acquired Micronics mid-Kickstarter, canceled the $2,999 Micron SLS printer, eliminating the cheapest turnkey SLS option from the market
}}
The cheapest turnkey desktop [[Selective laser sintering|SLS]] 3D printer on the market was canceled when [[Formlabs]] acquired its maker, Micronics, on July 11, 2024.<ref name="formlabs-press">{{Cite web |url=https://formlabs.com/company/press/formlabs-acquires-micronics/ |title=Formlabs Acquires Micronics to Further Advance Accessible SLS 3D Printing |date=2024-07-11 |access-date=2026-04-04 |website=Formlabs}}</ref> The Micron printer had raised $1,357,939 from 431 backers on Kickstarter at a starting price of $2,999;<ref name="3dnatives">{{Cite web |url=https://www.3dnatives.com/en/formlabs-announces-major-move-with-micronics-acquisition-110720246/ |title=Formlabs Make Major Move With Micronics Acquisition |author=Madeleine Prior |date=2024-07-11 |access-date=2026-04-04 |website=3Dnatives}}</ref><ref name="kickstarter">{{Cite web |url=https://www.kickstarter.com/projects/micronics3d/micron-a-desktop-sls-3d-printer |title=Micron: A Desktop SLS 3D Printer (Canceled) |access-date=2026-04-04 |website=Kickstarter}}</ref> Formlabs' cheapest SLS printer, the Fuse 1+ 30W, starts at $24,999.<ref name="fuse-pricing">{{Cite web |url=https://formlabs.com/blog/fuse-depowdering-kit/ |title=Your Entryway to Industrial SLS 3D Printing With an All-in-One System at $24,999 |access-date=2026-04-04 |website=Formlabs}}</ref> Backers received full refunds & a $1,000 credit toward Formlabs printers, a discount of roughly 4% on the cheapest available SLS system.<ref name="3dprint">{{Cite web |url=https://3dprint.com/311327/formlabs-buys-nascent-sls-3d-printer-competitor-micronics/ |title=Formlabs Buys Nascent SLS 3D Printer Competitor Micronics |author=Joris Peels |date=2024-07-11 |access-date=2026-04-04 |website=3DPrint.com}}</ref>

== Background ==

=== SLS technology & the price barrier ===

Selective laser sintering uses a laser to fuse polymer powder into solid parts layer by layer. Unlike FDM or resin printing, SLS requires no support structures because unfused powder surrounds each part during the build. This allows complex geometries & dense part nesting across the full build volume.<ref name="hackster">{{Cite web |url=https://www.hackster.io/news/micron-brings-sls-3d-printing-to-the-desktop-2b8780632541 |title=Micron Brings SLS 3D Printing to the Desktop |date=2024-06 |access-date=2026-04-04 |website=Hackster.io}}</ref> SLS parts are printed in engineering thermoplastics like Nylon PA12, producing components that are isotropic, chemically resistant, & mechanically strong enough for end-use applications.<ref name="3dpi-specs">{{Cite web |url=https://3dprintingindustry.com/news/micronics-unveils-its-innovative-sls-3d-printer-offering-230956/ |title=Micronics unveils its innovative SLS 3D printer offering |date=2024-06 |access-date=2026-04-04 |website=3D Printing Industry}}</ref>

These advantages come at a cost. Desktop SLS machines have historically required high-wattage CO2 or fiber lasers, multi-zone thermal management systems, & enclosed powder handling with HEPA filtration to mitigate inhalation hazards. Before 2024, the cheapest fully assembled desktop SLS printer was the Sinterit Lisa at roughly $13,990.<ref name="3dsourced">{{Cite web |url=https://www.3dsourced.com/3d-printers/sls-3d-printer/ |title=Best Lower-Cost Desktop SLS 3D Printers in 2024 |date=2024 |access-date=2026-04-04 |website=3DSourced}}</ref> Formlabs' Fuse 1+ 30W starter package costs $24,999.<ref name="fuse-pricing" />

=== Micronics & the Micron ===

Micronics was founded in 2021 by Henry Chan & Luke Boppart, both 2023 graduates of the University of Wisconsin-Madison.<ref name="tomshardware">{{Cite web |url=https://www.tomshardware.com/3d-printing/david-vs-goliath-desktop-sls-kickstarter-ends-with-acquisition |title=David vs Goliath: Desktop SLS Kickstarter Ends with Acquisition |author=Denise Bertacchi |date=2024-07-11 |access-date=2026-04-04 |website=Tom's Hardware}}</ref><ref name="3dprinting-com">{{Cite web |url=https://3dprinting.com/news/formlabs-acquires-micronics-mid-kickstarter-campaign/ |title=Formlabs Acquires Micronics Mid-Kickstarter Campaign |date=2024-07-11 |access-date=2026-04-04 |website=3DPrinting.com}}</ref> The two-person startup developed the Micron, a desktop SLS printer with a 160 x 160 x 205 mm build volume, a 5-watt 447 nm CW diode laser, & support for PA12 nylon & TPU-90A at launch.<ref name="micron-specs">{{Cite web |url=https://www.micronics3d.com/micron |title=Micron Desktop SLS 3D Printer |access-date=2026-04-04 |website=Micronics}}</ref> The machine weighed 19 kg & ran on standard household power, fitting on a desktop rather than requiring a dedicated workshop.<ref name="micron-specs" />

By using a cheap blue diode laser instead of an expensive CO2 unit, Micronics cut the starting price to $2,999 with a planned retail price of $4,499.<ref name="micron-specs" /><ref name="kickstarter" /> The Kickstarter campaign launched on June 13, 2024 with a $100,000 goal.<ref name="kickstarter" /> It raised $1,357,939 from 431 backers before being canceled.<ref name="3dnatives" /><ref name="develop3d">{{Cite web |url=https://develop3d.com/3d-printing/desktop-sls-company-micronics-acquired-by-formlabs/ |title=Desktop SLS start-up Micronics acquired by Formlabs |date=2024-07-11 |access-date=2026-04-04 |website=Develop3D}}</ref> A Kickstarter bundle including the printer, a removable build chamber, & a post-processing kit was available for $3,699 with an estimated delivery date of June 2025.<ref name="hackster" />

Formlabs CEO Max Lobovsky acknowledged the price gap between the two companies' products: "With the Fuse 1, we made a 5x leap in starting price for SLS systems. Micronics is trying to do another 5x beyond that."<ref name="3dprinting-com" />

== Acquisition ==

On July 11, 2024, Formlabs announced it had acquired Micronics.<ref name="formlabs-press" /> The deal came together rapidly. Lobovsky met Chan & Boppart for the first time at Open Sauce 2024.<ref name="formlabs-press" /><ref name="3dprinting-com" /> Lobovsky stated: "After meeting the Micronics co-founders at Open Sauce 2024, we discovered our shared vision for accessible, powerful 3D printing."<ref name="formlabs-press" />

The acquisition price was not disclosed. Both founders joined Formlabs. Chan took a role leading the SLS team; Boppart joined the software team.<ref name="3dnatives" /><ref name="develop3d" />

The Micron was immediately & permanently canceled. Micronics' FAQ page stated: "Will you continue to build Micronics? No. Instead of focusing on Micronics the company and Micron the product, we will be joining Formlabs to bring the next generation of accessible SLS printers to market."<ref name="micronics-faq">{{Cite web |url=https://www.micronics3d.com/learn-more |title=Learn More |access-date=2026-04-04 |website=Micronics}}</ref> Formlabs at the time claimed its Fuse 1 Series accounted for more than half of all powder bed fusion printers sold worldwide.<ref name="formlabs-press" />

=== Backer compensation ===

The Kickstarter campaign was canceled before its scheduled end date, so backers received automatic full refunds.<ref name="3dprint" /> Formlabs initially promised backers a $1,000 credit toward "any current or future printer" & a free Open Materials License for Formlabs machines.<ref name="3dnatives" />

By late 2024, backers reported the terms had shifted. The Formlabs blog was edited to offer a discounted legacy Fuse 1 at $9,999 to Micronics backers while stock lasted, with the $1,000 credit applicable to that purchase.<ref name="formlabs-forum">{{Cite web |url=https://forum.formlabs.com/t/formlabs-breach-of-promised-open-material-license-and-1000-credit-to-micronics-kickstarter-backer/40715 |title=Formlabs' breach of promised Open Material License and $1000 credit to Micronics Kickstarter Backer |date=2024-12 |access-date=2026-04-04 |website=Formlabs Community Forum}}</ref> The blog later added a note stating the "credit period has now ended," closing the redemption window entirely.<ref name="formlabs-blog">{{Cite web |url=https://formlabs.com/blog/formlabs-acquires-micronics/ |title=Formlabs Acquires Micronics to Develop the Next Generation of Accessible SLS |date=2024-07-11 |access-date=2026-04-04 |website=Formlabs}}</ref> A Formlabs forum thread documented complaints from backers who reported undisclosed geographic restrictions on the credit & months-long delays in receiving the promised Open Materials License.<ref name="formlabs-forum" />

=== Formlabs' stated rationale ===

Formlabs framed the acquisition as an "acqui-hire" that would accelerate development of affordable SLS technology. Henry Chan stated: "We are thrilled to join forces with Formlabs, a company we have long admired. After the outpouring of excitement around our Kickstarter, we're confident that this move will enable us to bring the best SLS 3D printing experience to users around the world."<ref name="formlabs-press" /> David Lakatos, Formlabs' Chief Product Officer, said: "What makes us so excited about Henry and Luke is that they embody the very people we make our products for."<ref name="develop3d" />

Chan explained that scaling a hardware startup with two people was difficult, citing frustration with spending time on packaging & marketing instead of engineering.<ref name="tomshardware" />

== Consumer impact ==

=== Price gap ===

The math does not work in backers' favor. Those who pledged for a $2,999-$3,699 printer received a $1,000 credit toward machines starting at $24,999. Even with the temporarily discounted Fuse 1 offer at $9,999, the out-of-pocket cost was still roughly 3x the Micron's Kickstarter price. For the current Fuse 1+ 30W starter package, the $1,000 credit covers about 4% of the purchase price.<ref name="fuse-pricing" /><ref name="formlabs-forum" />

Formlabs' Open Material Mode, which allows its printers to use third-party powder instead of proprietary materials, is a one-time per-printer license starting at $1,999 for the Form 3 & rising to $2,499 or more for newer models.<ref name="formlabs-oml">{{Cite web |url=https://formlabs.com/store/materials/open-material-mode/ |title=Open Material Mode |access-date=2026-04-04 |website=Formlabs}}</ref> On Hacker News, commenters noted the license alone costs "basically the same price as Micronics printer."<ref name="hn">{{Cite web |url=https://news.ycombinator.com/item?id=40936741 |title=Micronics Acquired by Formlabs |date=2024-07-11 |access-date=2026-04-04 |website=Hacker News}}</ref>

=== Market vacuum ===

As of April 2026, no manufacturer has released a sub-$5,000 turnkey SLS printer. The cheapest fully assembled commercial SLS options remain the Sinterit Lisa series (starting around $13,990) & the Formlabs Fuse 1+ 30W ($24,999).<ref name="3dsourced" /><ref name="fuse-pricing" /> The open-source SLS4All Inova MK1 is available as a DIY parts kit for roughly $3,860, but requires extensive user assembly & electrical wiring.<ref name="gemini-sls4all">{{Cite web |url=https://www.sls4all.com/ |title=SLS4All |access-date=2026-04-04 |website=SLS4All}}</ref>

Formlabs has not released any new SLS hardware since the acquisition. The company's 2025 year in review & Spring 2025 product announcements focused on resin printing materials & curing equipment; no Micronics-derived SLS product was mentioned.<ref name="formlabs-2025">{{Cite web |url=https://formlabs.com/blog/2025-year-in-review/ |title=Formlabs Year in Review: 2025 Highlights |access-date=2026-04-04 |website=Formlabs}}</ref>

== Community response ==

The 3D printing community's reaction was overwhelmingly negative. ''Tom's Hardware'' summarized: "You could say that Micronic's Kickstarter project is a smashing success, at least for the two young engineers who dreamed of building a next-generation 3D printer out of their college apartment. Their Kickstarter backers have a different opinion."<ref name="tomshardware" />

On Hacker News, users described the acquisition as having "killed a potential competitor in the cradle for cheap" & criticized Formlabs' material lock-in, noting the printers are "locked to 1st party materials by default."<ref name="hn" /> Across online forums, backers accused Formlabs of buying Micronics to remove competition rather than integrate the technology, lamenting that "we won't have a hobby level SLS printer in the near future."<ref name="hn" />

''VoxelMatters'' drew an explicit competitive parallel: "This sure does look like Formlabs crushing a small competitor, in a way that is very similar to the way Microsoft rose to market dominance."<ref name="voxelmatters">{{Cite web |url=https://www.voxelmatters.com/formlabs-acquires-micronics/ |title=Formlabs acquires Micronics |date=2024-07 |access-date=2026-04-04 |website=VoxelMatters}}</ref>

Joris Peels of ''3DPrint.com'' was more skeptical of the Micron itself, describing the $2,999 price point as "improbably low" & questioning whether a two-person team could scale a powder bed fusion system to production. He praised the team's engineering, particularly the removable build chambers & depowdering solution, but suggested the acquisition may have prevented a "Kickstarter fracas" if the product could not be delivered at the promised price.<ref name="3dprint" />

== Killer acquisition pattern ==

The Formlabs-Micronics acquisition fits the pattern described in antitrust economics as a "killer acquisition," where an incumbent firm acquires a startup to discontinue its product & prevent competitive disruption.<ref name="cunningham">{{Cite web |url=https://www.journals.uchicago.edu/doi/abs/10.1086/712506 |title=Killer Acquisitions |author=Colleen Cunningham, Florian Ederer, and Song Ma |date=2021-03 |website=Journal of Political Economy |access-date=2026-04-04}}</ref> The term was formalized by Cunningham, Ederer, & Ma in a 2021 ''Journal of Political Economy'' study that analyzed 35,000 pharmaceutical drug projects. They found that 5.3% to 7.4% of acquisitions in their sample were killer acquisitions, & that these deals disproportionately occurred just below the thresholds for antitrust scrutiny.<ref name="cunningham" />

The Formlabs-Micronics deal shares key characteristics with this pattern. The incumbent (Formlabs, claiming over 50% of worldwide powder bed fusion sales)<ref name="formlabs-press" /> acquired a direct competitor (Micronics) whose product overlapped with the incumbent's product line but at a fraction of the price. The acquired product was immediately discontinued.<ref name="micronics-faq" /> No replacement product at a comparable price point has been released as of April 2026.<ref name="formlabs-2025" />

The 2024 Hart-Scott-Rodino Act threshold for mandatory pre-merger FTC review was $119.5 million.<ref name="hsr-2024">{{Cite web |url=https://www.jonesday.com/en/insights/2024/02/us-merger-notification-threshold-increases-to-1195-million |title=US Merger Notification Threshold Increases to $119.5 Million |date=2024-02 |access-date=2026-04-04 |website=Jones Day}}</ref> A startup that raised $1.3 million on Kickstarter fell well below that line.<ref name="3dnatives" /> No FTC or DOJ filing related to the acquisition has been publicly reported.<ref name="ftc-hsr">{{Cite web |url=https://www.ftc.gov/system/files/attachments/us-submissions-oecd-2010-present-other-international-competition-fora/oecd-killer_acquisiitions_us_submission.pdf |title=Start-ups, killer acquisitions and merger control |access-date=2026-04-04 |website=Federal Trade Commission}}</ref>

The 3D printing industry has faced antitrust scrutiny before. In 2001, the U.S. Department of Justice sued to block the merger of 3D Systems & DTM, arguing it would reduce the rapid prototyping market from three competitors to two. The merger was allowed only after the companies agreed to license their rapid prototyping patent portfolios to a competitor.<ref name="doj-3dsystems">{{Cite web |url=https://www.justice.gov/archive/atr/public/press_releases/2001/8810.htm |title=Justice Department Requires Divestitures in 3D Systems/DTM Merger |date=2001-08-29 |access-date=2026-04-04 |website=U.S. Department of Justice}}</ref>

== References ==
{{reflist}}

[[Category:Formlabs]]
[[Category:Anti-competitive practices]]
[[Category:3D printing]]
[[Category:2024 incidents]]

Formlabs

2026-04-05T23:14:02Z

Louis: Comprehensive revision: expand Micronics acquisition section with killer acquisition framing, rewrite Open Material Mode & Form 2 deprecation sections, replace all bare URLs with cited sources, populate CompanyCargo fields, remove stub placeholders

{{#seo:description=Formlabs charges $875-$11,899 per printer to use third-party materials, acquired & killed a $2,999 SLS competitor, and obsoleted the Form 2 via resin DRM.}}
{{CompanyCargo
|Founded=2011
|Industry=3D printing
|Logo=Formlabs logo.svg
|ParentCompany=
|CompanyAlias=
|Type=Private
|Website=https://formlabs.com
|Description=Charges $875-$11,899 per printer to use third-party materials; acquired & canceled a $2,999 SLS competitor to protect its $28,989 Fuse 1+
}}

'''Formlabs''' is a 3D printing company that charges its customers $875 to $11,899 per printer for the permission to use third-party materials on hardware they already own.<ref name="formlabs-omm-store">{{Cite web |title=Open Material Mode |url=https://formlabs.com/store/materials/open-material-mode/ |website=Formlabs |access-date=2026-04-04 |url-status=live |archive-url=https://web.archive.org/web/20260116171208/https://formlabs.com/store/materials/open-material-mode/ |archive-date=2026-01-16}}</ref> In July 2024, Formlabs acquired Micronics, a startup building a $2,999 desktop SLS printer funded on Kickstarter, & immediately canceled the product.<ref name="formlabs-acquires-micronics">{{Cite web |title=Formlabs Acquires Micronics to Develop the Next Generation of Accessible SLS |url=https://formlabs.com/blog/formlabs-acquires-micronics/ |website=Formlabs |date=2024-07-11}}</ref> The cheapest SLS printer Formlabs sells starts at $28,989; the Micron would have cost roughly 1/10th that price.<ref name="formlabs-sls-pricing">{{Cite web |title=How to Compare SLS 3D Printer Prices |url=https://formlabs.com/blog/selective-laser-sintering-sls-3d-printer-price/ |website=Formlabs |access-date=2026-04-04}}</ref><ref name="3dprint-micronics">{{Cite web |title=Formlabs Buys Nascent SLS 3D Printer Competitor Micronics |url=https://3dprint.com/311327/formlabs-buys-nascent-sls-3d-printer-competitor-micronics/ |website=3DPrint.com |date=2024-07-11}}</ref> Founded in 2011 by MIT Media Lab students Maxim Lobovsky, David Cranor, & Natan Linder, the company raised $2.95 million on Kickstarter for its first printer & has since raised over $250 million in venture funding.<ref name="wikipedia-formlabs">{{Cite web |title=Formlabs |url=https://en.wikipedia.org/wiki/Formlabs |website=Wikipedia |access-date=2026-04-04}}</ref>

== Consumer-impact summary ==

* Formlabs charges a per-printer license fee ranging from $875 (Form 4) to $11,899 (Fuse 1 series) for the permission to use third-party materials on hardware the customer already owns.<ref name="formlabs-omm-store" />
* The company acquired Micronics in July 2024 & canceled the Micron, a $2,999 SLS 3D printer that had raised over £1 million from 431 Kickstarter backers.<ref name="formlabs-acquires-micronics" /><ref name="develop3d-micronics" /> Formlabs' own SLS printer, the Fuse 1+ 30W, starts at $28,989.<ref name="formlabs-sls-pricing" />
* The Form 2 uses proprietary DRM-chipped resin cartridges. Formlabs committed to supplying consumables through 2023, then left the end date ambiguous; by September 2024 consumables were still available but with no guaranteed supply timeline.<ref name="formlabs-forum-form2-support">{{Cite web |title=Ongoing Support for the Form 2 |url=https://forum.formlabs.com/t/ongoing-support-for-the-form-2/22871 |website=Formlabs Community Forum |date=2019-04}}</ref><ref name="formlabs-forum-form2-consumables">{{Cite web |title=Form 2 availability of consumables |url=https://forum.formlabs.com/t/form-2-availability-of-consumables/39108 |website=Formlabs Community Forum |date=2024-09}}</ref>

== Incidents ==

This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:Formlabs|Formlabs category]].

=== Acquisition of Micronics ===

Formlabs acquired Micronics on July 11, 2024, & canceled the Micron desktop SLS 3D printer the same day.<ref name="formlabs-acquires-micronics" /> The Micron had launched on Kickstarter in June 2024 at a starting price of $2,999.<ref name="3dprint-micronics" /> The campaign raised over £1 million from 431 backers.<ref name="develop3d-micronics">{{Cite web |title=Desktop SLS start-up Micronics acquired by Formlabs |url=https://develop3d.com/3d-printing/desktop-sls-company-micronics-acquired-by-formlabs/ |website=Develop3D |date=2024-07-11}}</ref>

SLS (Selective Laser Sintering) printers use a laser to fuse nylon powder into parts without support structures. Traditional industrial SLS machines from manufacturers like EOS & 3D Systems cost $200,000 to $500,000 or more.<ref name="formlabs-sls-pricing" /> Formlabs' own SLS offering, the Fuse 1+ 30W, starts at $28,989.<ref name="formlabs-sls-pricing" /> The Micron at $2,999 would have undercut the Fuse 1+ 30W by roughly 10x.<ref name="3dprint-micronics" />

Formlabs CEO Max Lobovsky acknowledged this price gap in an interview with TechCrunch, stating that Formlabs had achieved a "5x leap in starting price" with the Fuse 1 & that Micronics was "trying to do another 5x beyond that."<ref name="techcrunch-micronics">{{Cite web |title=Formlabs acquires 3D printing startup Micronics mid-Kickstarter campaign |url=https://techcrunch.com/2024/07/11/formlabs-acquires-3d-printing-startup-micronics-mid-kickstarter-campaign/ |website=TechCrunch |date=2024-07-11}}</ref> Micronics founders Henry Chan & Luke Boppart joined the Formlabs engineering team at its Somerville, Massachusetts headquarters.<ref name="formlabs-press-micronics">{{Cite web |title=Formlabs Acquires Micronics to Further Advance Accessible SLS 3D Printing |url=https://formlabs.com/company/press/formlabs-acquires-micronics/ |website=Formlabs |date=2024-07-11}}</ref> The Micronics brand was discontinued & the Kickstarter was canceled.<ref name="techcrunch-micronics" />

Tom's Hardware headlined its coverage "David vs Goliath" & reported that the Micronics branding would be discontinued.<ref name="tomshardware-micronics">{{Cite web |title=David vs Goliath: Desktop SLS Kickstarter Ends with Acquisition |url=https://www.tomshardware.com/3d-printing/david-vs-goliath-desktop-sls-kickstarter-ends-with-acquisition |website=Tom's Hardware |first=Denise |last=Bertacchi |date=2024-07-11}}</ref> 3D Printing Industry reported the acquisition as producing "new accessible SLS 3D printers forthcoming," but no such product has shipped as of April 2026.<ref name="3dprintingindustry-micronics">{{Cite web |title=Formlabs acquires Micronics, new accessible SLS 3D printers forthcoming |url=https://3dprintingindustry.com/news/formlabs-acquires-micronics-new-accessible-sls-3d-printers-forthcoming-231608/ |website=3D Printing Industry |date=2024-07-11}}</ref>

Formlabs offered backers a full refund plus a $1,000 credit toward any current or future Formlabs printer & a free Open Material License.<ref name="formlabs-press-micronics" /><ref name="formlabs-forum-backer-breach" /> By December 2024, backers reported on the Formlabs forum that the promised $1,000 credit had not been delivered months after submission. Some backers who attempted to use their credit toward a Fuse 1 purchase were denied a $5,000 discount for unspecified reasons. The forum thread was auto-closed in July 2025.<ref name="formlabs-forum-backer-breach">{{Cite web |title=Formlabs' breach of promised Open Material License and $1000 credit to Micronics Kickstarter Backer |url=https://forum.formlabs.com/t/formlabs-breach-of-promised-open-material-license-and-1000-credit-to-micronics-kickstarter-backer/40715 |website=Formlabs Community Forum |date=2024-12-27}}</ref> A $1,000 credit toward a $28,989 SLS printer represents a 3.4% discount for backers who had pledged for a $2,999 machine.

=== Open Material Mode ===

Formlabs requires a one-time per-printer software license to unlock the use of third-party resins & powders on its printers. The license, called Open Material Mode, costs $875 for the Form 4, $1,999 for the Form 3 series, $2,499 for the Form 4B, $3,999 for the Form 3L series, $4,999 for the Form 4L, & $11,899 for the Fuse 1 series.<ref name="formlabs-omm-store" /> Without the license, users can only load Formlabs' proprietary DRM-chipped resin cartridges.

Formlabs users on the company's own forum called the pricing "anti-consumer" & argued that the correct price should be zero, noting that competing desktop printers accept third-party materials without restriction.<ref name="formlabs-forum-oml-6k">{{Cite web |title=Open Material License $6k per printer |url=https://forum.formlabs.com/t/open-material-license-6k-per-printer/36905 |website=Formlabs Community Forum |date=2023-09-12}}</ref> Formlabs initially proposed pricing as high as $6,000 per printer for the Form 3 series in September 2023; community backlash led to the current tiered pricing structure.<ref name="formlabs-forum-oml-6k" />

The license is free for accredited educational institutions.<ref name="formlabs-omm-store" /> As of January 2026, Open Material Mode is included with new Form 4B & 4BL purchases, but owners who bought the same printers before that date must pay the full license fee.<ref name="formlabs-forum-4b-omm">{{Cite web |title=PSA to All form Form 4B & 4BL owners (Open material mode) |url=https://forum.formlabs.com/t/psa-to-all-form-form-4b-4bl-owners-open-material-mode/46199 |website=Formlabs Community Forum |date=2026-01}}</ref> Formlabs' warranty terms state that failure modes caused by third-party materials are excluded from standard warranty coverage, adding financial risk on top of the license cost.<ref name="formlabs-omm-store" />

=== Form 2 deprecation ===

Formlabs announced the end of active support for the Form 2 in April 2019, following the launch of the Form 3 series. The company committed to selling resin tanks, cartridges, & build platforms through at least 2023.<ref name="formlabs-forum-form2-support" /> The Form 2 uses proprietary DRM-chipped resin cartridges. Without an authorized cartridge, the printer runs in a limited mode that disables the heater & wiper functions, reducing print quality.<ref name="protoart-cartridge" />

By September 2024, nine months past the stated deadline, Form 2 consumables were still available but Formlabs hadn't provided a firm end date. Users requested concrete timelines to plan investment decisions; Formlabs didn't respond in the thread.<ref name="formlabs-forum-form2-consumables" /> Once Formlabs stops selling Form 2-compatible cartridges, owners of the $3,500 printer will have no official consumable supply. The printer becomes unusable even though the hardware itself still works.<ref name="formlabs-forum-form2-support" />

Third-party developers attempted workarounds. ProtoART produced a Universal Cartridge, a DIY modification kit installed into an existing cartridge that allowed third-party resin use with heater & wiper functions enabled.<ref name="protoart-cartridge">{{Cite web |title=A Universal Cartridge For Form 2 3D Printers, But Should You Use It? |url=https://www.fabbaloo.com/2019/09/a-universal-cartridge-for-form-2-3d-printers-but-should-you-use-it |website=Fabbaloo |date=2019-09}}</ref> The Universal Cartridge is compatible only with Formlabs firmware versions through 2.2.0; the product reached end of life & is available only while supplies last.<ref name="protoart-site">{{Cite web |title=Universal Cartridge Module for Formlabs |url=https://www.lectronz.com/products/universal-cartridge-for-formlabs-form-2-form-3 |website=Lectronz |access-date=2026-04-04}}</ref>

== Products ==

* '''SLA printers:''' Form 1, Form 1+, Form 2, Form 3 series (Form 3, 3+, 3B, 3B+, 3L, 3BL), Form 4 series (Form 4, 4B, 4L, 4BL)
* '''SLS printers:''' Fuse 1, Fuse 1+ 30W
* '''Software:''' PreForm (slicing & print preparation)
* '''Post-processing:''' Form Wash, Form Cure
* '''Automation:''' Form Auto, Form Cell

== See also ==

* [[Bambu Lab]]
* [[Creality]]
* [[MakerBot]]

== References ==

{{reflist}}

[[Category:Formlabs]]
[[Category:3D Printing]]
[[Category:Planned Obsolescence]]

File:BMW Proprietary Screw.png

2026-04-05T20:30:39Z

Louis: Patent diagram (Figures 7-9) from DE102024115950A1 showing BMW roundel-shaped proprietary fastener design. Public domain patent drawing.

Patent diagram (Figures 7-9) from DE102024115950A1 showing BMW roundel-shaped proprietary fastener design. Public domain patent drawing.