I’ve written before about why a website or mobile app’s Terms of Service are a vitally important part of the developer’s relationship with the end user. However, I think that a few points need to be emphasized with regard to these agreements that developers hate and users hate even more. If attention isn’t paid to these critical steps, the Terms of Service may not be able to protect the developer if there is a lawsuit. In this and Thursday’s posts, we’ll look at two of these critical moves that you should make.
“Clickwrap” versus “Browsewrap” agreements:
There are generally two types of Terms of Service agreements in use these days:
- Clickwrap agreements – these are the industry standard agreements that require a user to affirmatively click on a button, check a box, scroll down the agreement or any combination of the above in order to assent to the Terms of Service;
The industry standard is to use Clickwrap agreements, and for good reason. While the Internet provides lots of unique ways to interpret laws that existed before it was invented, there are some things that just don’t change. One of these things is the basic building blocks of a contract.
Requirements for a valid contract:
Contracts require three things to be valid:
- An offer – pretty self-explanatory, at least for our purposes;
- Acceptance – this is where we run into trouble here; and
- Consideration – we’ll talk about this in the next post.
If there is no acceptance of an offer, then there is no contract. When the user affirmatively clicks the button or checks the box in a Clickwrap agreement, this is enough assent that courts have found a contract. However, with Browsewrap agreement cases, such as one case involving the Zappos website, courts have found that merely putting a link to the Terms of Service on the site (a Browsewrap agreement) does not create a valid contract.
We all know that pretty much no one reads the Terms of Service before agreeing to it. However, the law doesn’t give an excuse for those who don’t read the contracts that they assent to. When push comes to shove and the site or app developer gets sued, however, that Terms of Service could save a ton of time and hassle.
photo credit: bloomgal via photopin cc