LEGAL · ACCEPTABLE USE

Acceptable Use Policy

The rules that keep Jumbi useful, available, and safe for teams preparing with readiness assessments.

LAST UPDATED · JUNE 23, 2026

01

Overview

This Acceptable Use Policy (“AUP”) explains what is and is not allowed when using Jumbi. It is designed to protect users, the Service, and the integrity of the readiness assessments teams rely on to prepare for what’s next.

02

Authorized Use Only

You may use Jumbi to assess readiness for work or initiatives you own or are authorized to evaluate. Do not submit inputs that describe situations you have no lawful basis to assess, and do not use readiness assessments in ways that violate the rights of others.

03

Prohibited Conduct

  • Using Jumbi to violate laws, regulations, contracts, or third-party rights
  • Attempting to access another user's account, inputs, assessments, or workspace
  • Bypassing rate limits, quotas, authentication, authorization, or security controls
  • Submitting inputs intended to generate harmful, deceptive, or unlawful content
  • Scraping, benchmarking, or bulk-exporting the Service without written permission
  • Interfering with the availability, integrity, or performance of the Service
04

Security Testing

Good-faith security research is allowed only when it follows the Vulnerability Disclosure Policy. Do not run denial-of-service tests, access other users' data, or test systems outside the stated scope.

05

AI and Output Use

Readiness assessments are provided to accelerate your preparation. You are responsible for reviewing, validating, and applying every score, gap, and recommendation with judgment before acting on it.

06

Enforcement

We may investigate suspected violations and may suspend, limit, or terminate access when needed to protect the Service or other users. We will try to provide notice when practical, but urgent security or abuse situations may require immediate action.

07

Contact

Questions about acceptable use can be sent through the contact page or to hello@jishulabs.com.

Questions about this document? Get in touch.