Hackpads are smart collaborative documents. .
440 days ago
0 / 2
Unfiled. Edited by Adrie van der Luijt 440 days ago
  • Suggested approach
  1. Establish whether there is a real user need to have a set of terms and conditions. If there is no need, then don't do them.
  1. Write the terms and conditions in plain language, or translate them to plain language
  1. Publish the full terms and conditions on your site. Do not require log-in access. Make the terms and conditions page available at a consistent URL between servces, for example /terms-and-conditions.
  1. Make  it clear when terms change, including making all previous versions of  terms and conditions available online with data about when they were  applicable.
  1. If the terms depart from what could reasonably be expected from a digital servicethen make sure that they are explicitly stated within the transaction -  ideally from the part of the transaction that relates to those terms.

Stop sharing the collection with ?

This pad is open to "", so will still be able to access it.
Cancel
T&C Feed

Contact Support



Please check out our How-to Guide and FAQ first to see if your question is already answered! :)

If you have a feature request, please add it to this pad. Thanks!


Log in