It's funny because Stalin very blatantly had photos doctored when he stopped being friendly with someone.

First things first. Is "company data" - email, contacts, files - accessible from your phone? If so, they have a vested interest in making sure that data is not compromised when your phone is lost or stolen. As a result, PIN/password requirements, encryption, antivirus, and remote wipe capabilities are generally required. In some cases where devices have a tunnel to the corporate network (Blackberry), they will possibly want to control what apps you install to prevent malicious ones from accessing the corporate network via your BES server.

Most laypeople don't have any clue about protecting company data on a regular basis, they just want their data instantly and aren't concerned with what happens in a worst-case scenario. "Oops, it got stolen. Guess I need to get the latest model now!"

You don't need a clean room implementation to avoid a derivative work. You merely need to avoid copying protected elements from the first work.

From a biochemical standpoint, the important factor is fructose content and nothing else. Glucose does have less adverse effects than fructose.

Anything of yours can be subpoenaed in a lawsuit. Northwest Airlines subpoenaed the *personal* computers of their employees when they suspected their employees were getting too uppity^H^H^H^H^H^H, I mean, striking by calling in sick.

It hardly matters if you use encryption, etc... the legal discovery process can violate whatever privacy you thought you had. It only takes a credible allegation of wrongdoing - not even "beyond a reasonable doubt" - to discover all of your personal files, etc... and, because only money is involved, the plaintiff needs only show guilt by a "preponderance of the evidence", or more succinctly, that it is likely that you did it. If you think you can get smart by encrypting your files, it's likely you'll be held in contempt of court, and have a summary judgment entered against you.

The only thing paying for the hardware means is that you'll eventually get it back, usually.

So they should give all their rights up in return for a promise? How about you sign a job contract binding you to work 80 hours a week for 5$ an hour in return for a promise of really big bonuses. Promises dont count. Contracts and licenses do. Besides, llfonic's representative clearly stated they had no plans to contribute anything back.

The domain "registers" you, doesn't make sense? They are documenting domain owners. Hence, they are "registered." Soviet doesn't make sense, but that helps make the connection.
 
I actually thought it was kind of funny.

Because they want someone they can call up and say, "Product X is broke. Fix it."

That's pretty much the main reason that I've ran into. A support contract being available.