What can a website Terms of Service require? I heard of a study where participants were asked to sign up for a fake social media platform with absurd terms (such as giving up your first-born child). I was curious as to what can actually be put into a ToS. For example, can I put in a clause like this: Upon signing up for this, you agree that I have the right to enter your house at any time without notice and use any motor vehicles you own without notice. Or something else like that.
This paper describes a website created to test the hypothesis that nobody bothers to read the TOS, and it contained a privacy clause saying that &quot;we may share everything, and a clause that by agreeing to these Terms of Service, and in exchange for service, all users of this site agree to immediately assign their first-born child to NameDrop, Inc. If the user does not yet have children, this agreement will be enforceable until the year 2050. All individuals assigned to NameDrop automatically become the property of NameDrop, Inc. No exceptions. Since this was not a real webpage, there was no attempt to enforce. TOS is just another kind of contract, so the question is which kinds of contract conditions are enforceable and which kinds are not. It depends on whose laws you are operating under, which explains the use of expressions like &quot;void where prohibited by law&quot;. There are innumerable conditions that could be included in a contract which are unenforceable. A contract requiring a person to commit a crime is unenforceable. Many jurisdictions have laws prohibiting a person from waiving certain rights, for example you cannot sign away your right to be represented by legal counsel in a dispute. There are related &quot;unfair / deceptive&quot; practices laws, which might include meta-conditions that any clause disclaiming liability must be prominently displayed. These are terms that a reasonable person would clearly know in advance are illegal and unenforceable. There is also a concept of &quot;unconscionability&quot;, a finding that a certain condition favors the business to the point of &quot;shocking the conscience&quot;, which may take a deeper legal analysis to evaluate. A requirement to litigate small disputes in California might be deemed unconscionable for a customer in an East Coast state, but it might not be. A typical characterization of an unconscionable contract is one that &quot;leaves one party with no real, meaningful choice and is unreasonably advantageous to the other party&quot;, especially when due to asymmetrical negotiation power. For example, Ellis v. McKinnon , 18 Cal. App. 4th 1796 (employment contract for a salesman, commissions were forfeit if company had not received payment from the customer by the termination of employment). The main case law in the US in this area is Williams v. Walker-Thomas Furniture, 350 F.2d 445, where a customer bought furniture on credit, with a clause allowing repossession of all of the furniture in case of default by the customer. The doctrine is encoded in UCC 2-302. However, &quot;unconscionable&quot; does not mean &quot;I don't like it&quot;. In lieu of statutory price controls, a customer probably cannot avoid paying an agreed on exorbitant price for a product ($100 for a dozen rolls of toilet paper). Here is a bit more legal analysis of unconscionability, which focuses on three factors: one-sidedness, oppressiveness, and likeliness to result in unfair surprise.
Yes A software license is just a contract and parties to a contract are free to agree whatever terms they wish under the doctrine of freedom to contract. Government can restrict what terms can be used in a contract either in general (e.g. for being against public policy) or specifically (e.g. by requiring wages be paid in money). None of the terms you mention fall foul of any restrictions I know of.
No. That clause does not give other users a licence to reproduce the work (other than what is necessary to access or use it) or create derivative works. The copyright owner has the exclusive right to do those things. (See 17 USC 106.) The clause you quote only indicates that other users can "access" (download for viewing) your "information" and use it, too. It doesn't give away any of your exclusive copyright in the work. You do grant Facebook a licence to do certain things with your work in section 2.1 of the Terms of Service, though.
When a platform has the right to kick you out as they deem fit, without any evidence why they did it, does that change if you have a paid? It depends on the purpose of payment and the terms &amp; conditions it triggers. Your description reflects that payment entitles the user to have no ads &quot;and stuff&quot; (?). Payment does not necessarily entitle the user to continued access, diligence from customer service, or other features. Without fully knowing the platform's terms &amp; conditions regarding payment it is impossible to identify what obligations (other than not displaying advertisements) your payment creates on the platform. The information you provide here is insufficient for assessing whether you have a viable claim such as fraud or breach of contract. On the other hand, the platform's apparent arbitrariness and lack of response might support a finding of unfair or deceptive practices if the platform does not honor or proportionally reimburse your payment. Many jurisdictions have legislation prohibiting practices which are unfair, deceptive, or unconscionable (example: MCL 445.903). Oftentimes statutory law establishes an agency in charge of addressing customers' complaints.
The so-called 'cookie law' obliges you to inform the user about the site's cookies (or use of Storage or such on the user's computer) and ask for consent for those that are not "strictly necessary for the provision of an information society service requested by the subscriber or user". It does not require you to seek consent for the use of any cookie no matter what function it has. "Strictly necessary" cookies include those necessary for the website to comply with the law. Per guidance from the Information Commissioner's Office (ICO) in the UK (see the example box), a cookie set in relation to such consent or refusal is fine - it's for compliance with the cookie law. I would expect similar guides throughout the EU. You must consider its duration or lifespan: "For example, whilst it may be technically possible to set the duration of a cookie to “31/12/9999” this would not be regarded as proportionate in any circumstances." And consider including information about it in your cookie policy or such that users can find out more if they want.
I can't find any law that would prevent an employer from requiring this. Under current Florida law, an employer can even demand passwords and access to an employee's social media accounts. A bill was proposed to prohibit this, but it hasn't passed. Generally, an employer can require anything they want as a condition of employment, as long as it is not illegal. Florida has at-will employment so the employer could certainly fire the employee if they don't comply.
TOS are a contract. If you have a contract through the App, you have incorporated the TOS as a term of your contract. Contracts mean what they say they do, what you are thinking of as "basic contract law" is actual just an ordinary and customary term that people in your industry usually make a part of the contract, not contract law itself.
The question reads: I see an NDA as a pseudo-public document, something you need to read in detail before you acknowledge and opt-in to limit rights (discussion of topic/tech). Unfortunately for this view, the law normally sees an NDA as a private contract, except when it is alleged that it violates public policy. If an NDA explicitly or implicitly includes itself in the list of things not to be disclosed, then posting it would be a violation of the contract. In such a case the party posting the agreement would be subject to whatever consequence the agreement specifies for violation, unless that person had a valid defense. The operator of a web site where the document might be posted would not normally ne a party to the agreement, and so would not be liable for hosting it, unless some other limitation applies, beyond the NDA itself. An NDA can indeed be a significant limitation on the signer's freedom to discuss certain topics, and a person would be wise to consider it in detail, and perhaps consult a lawyer, before signing one. But that does not mean that the person should post or distribute it publicly, nor that the person is automatically entitled to consult NDAs that others have signed. There are sufficient sample NDA forms available that a person can compare an offered NDA with other possibilities, and get an idea if an offered NDA goes beyond the usual terms.