Software locks

❗Article Status Notice: This Article is a stub

---

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. Learn more ▼

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, please visit the Moderator's noticeboard, or 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 and features in consumer electronic hardware and software.^{These are Wikipedia citations!} Software locks are not considered bad practice and are necessary for basic cybersecurity and operation of most hardware, though they can be abused.

Noteworthy bad practice examples

Anti Interoperability

See also: Proprietary protocols 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

Mobile phones

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

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

-wip

Server connectivity reliance

Also see: Subscription service, Digital rights management

-wip

Further reading

Digital rights management

Proprietary software

Walled garden / Software Ecosystem

Bootloader unlocking

Proprietary firmware