Acceptable Use Policy

We’re delighted you’ve decided to use Jumble and we’re happy to offer Jumble software and services for free to our personal users. However, whether you’re a paid business user or a free personal user we trust you to use our services responsibly.

You agree not to misuse the Jumble software and/or services ("Services") or help anyone else to do so. For example, you must not even try to do any of the following in connection with the Services:

  • probe, scan, or test the vulnerability of any system or network;
  • breach or otherwise circumvent any security or authentication measures;
  • access, tamper with, or use non-public areas or parts of the Services, or shared areas of the Services you haven't been invited to;
  • interfere with or disrupt any user, host, or network, for example by sending a virus, overloading, flooding, spamming, or mail-bombing any part of the Services;
  • access, search, or create accounts for the Services by any means other than our publicly supported interfaces (for example, "scraping" or creating accounts in bulk);
  • send unsolicited communications, promotions or advertisements, or spam;
  • send altered, deceptive or false source-identifying information, including "spoofing" or "phishing";
  • sell the Services unless specifically authorized to do so;
  • advocate bigotry or hatred against any person or group of people based on their race, religion, ethnicity, sex, gender identity, sexual preference, disability, or impairment;
  • violate the law in any way;
  • perform acts of terrorism; or
  • violate the privacy or infringe the rights of others.

Changes to this Policy

Jumble has the discretion to update this Acceptable Use Policy at any time. When we do, we will revise the updated date at the bottom of this page. We encourage Users to frequently check this page for any changes to stay informed about how you, as a consumer of Services, are expected to interact with Jumble. You acknowledge and agree that it is your responsibility to review this policy periodically and become aware of modifications.

This document was last updated on May 29, 2015