Software locks

❗Article Status Notice: This Article is a stub

Notice: This Article Requires Additional Expansion

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

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

How You Can Help:

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

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

Software locks are security measures used to control access & features in consumer electronic hardware & software. ^[1] ^[2] Software locks by themselves are not considered bad practice and are necessary for basic cyber security and operation of most hardware, however, abuse of them will be recorded in the following sections.

Noteworthy bad practice examples[edit | edit source]

Anti Interoperability[edit | edit source]

Also see: Proprietary protocols, Anti Interoperability, Hardware Anti Interoperability^[3]

wip stub example you can't use our competitors Bluetooth headset with our XYZ operating system because we invented a our own new proprietary XYZ Bluetooth audio codec and that product doesn't support it.

real example apple mfi certifications on charging and data transfer accessories

apple's history of anti-Interoperability

Account-required products[edit | edit source]

Mobile phones[edit | edit source]

ref Small preamble focused on how mobile phones require an account in order to be used, reference Google Pixels and specific Android devices requiring a Google account, and iPhones needing an Apple account.

in appliances[edit | edit source]

hvac app activation of furnace control boards (also an example of Forced app download (editors note hard to find credible ref this is a thing with ruud furnace control boards) )

Binding hardware features to non-transferable user accounts / activation & licensing locks[edit | edit source]

-wip

Server connectivity reliance[edit | edit source]

Also see: Subscription service, Digital rights management