Acceptable Use Policy

This policy applies to every JestBot account holder, every human agent added under an account’s teams, and every visitor who interacts with a JestBot-powered widget embedded on a customer’s site. By creating a bot, uploading or linking content, embedding the widget, or logging in as an agent, you agree to follow these rules. Account holders are responsible for the conduct of any agent they add to their teams.

You may not upload, paste, link to (via URL ingestion), or otherwise feed a bot’s knowledge base with content that:

• Is illegal in the jurisdictions where you operate or where your bot’s visitors are located
• Infringes someone else’s copyright, trademark, trade secret, or other intellectual property rights
• Contains malware, exploit code, phishing content, or anything designed to compromise a visitor’s device or account
• Is sexually explicit involving minors, or otherwise sexually exploitative of any person
• Promotes violence, terrorism, self-harm, or hatred against a protected group
• Contains someone else’s personal or sensitive data (medical records, government ID numbers, financial account details) uploaded without a lawful basis to process it
• Facilitates the sale of illegal goods, controlled substances, or weapons
• Is knowingly false and configured to be presented as factual/authoritative to deceive visitors (e.g. fake medical or financial claims)

You may not use JestBot, in any part of the platform, to:

• Send spam, unsolicited bulk messages, or use the widget, lead-capture form, or agent messaging tools to harass, threaten, or stalk any individual
• Scrape, copy, or systematically extract another company’s website or product content via URL ingestion for the purpose of competitive replication rather than legitimate reference
• Resell, sublicense, white-label without authorization, or provide access to your account, API keys, or seats to third parties outside your own organization
• Circumvent plan limits — for example, splitting one use case across multiple free accounts specifically to avoid paying for a plan that fits your actual usage
• Attempt to reverse-engineer, probe, load-test, or disrupt JestBot’s infrastructure, embedding logic, authentication, or rate limits
• Impersonate another person, business, or JestBot itself, including via a bot’s configured name/persona used to deceive rather than brand a legitimate business
• Use the platform to build a directly competing chatbot/helpdesk SaaS product using JestBot’s own infrastructure or outputs

You may only embed a bot’s widget on domains you own or are explicitly authorized to publish content on. Domain allowlisting exists specifically to enforce this — attempting to work around it (e.g. by proxying requests through an unauthorized domain, or sharing a public key for use on a domain outside your allowlist) is a violation regardless of technical method.

Bots must not be configured to deceive a visitor about whether they are talking to an AI system when directly asked. Widgets should not be styled or worded to impersonate a different, unrelated business than the one that owns the bot.

The pre-chat lead capture form (name, email/phone, optional OTP) must only be used to collect contact details from visitors for the bot owner’s own legitimate customer communication purposes. Using it to build contact lists for resale, unrelated third-party marketing, or any purpose the visitor wasn’t reasonably made aware of is not permitted. Bot owners are responsible for having a lawful basis to collect and retain visitor personal data captured this way, consistent with applicable privacy law in the visitor’s jurisdiction.

Once a conversation is handed over to a human agent, that agent is communicating directly with a real visitor and is expected to do so professionally. Agents may not use the handover channel to send unrelated marketing, misrepresent themselves, or share visitor conversation data outside the legitimate purpose of resolving that visitor’s query. Canned responses containing prohibited content (Section 2) are not permitted regardless of who authored them.

Public keys (pk_...) and secret keys (sk_...) are scoped to your own bots and must not be shared outside your organization. Automated or scripted use of the chat or data APIs must stay within your plan’s message and document limits, and must not be used to load-test JestBot’s infrastructure, scrape other customers’ bots, or attempt to enumerate or guess other accounts’ keys or data.

If you configure your own OpenAI, Anthropic, Google Gemini, Groq, or Mistral key, your use of that provider through JestBot must also comply with that provider’s own acceptable use policies. JestBot is not responsible for enforcing a third-party provider’s policies, but a violation severe enough to get your key revoked or flagged by that provider may also result in action on your JestBot account if it reflects a violation of this policy.

We don’t manually review every document uploaded to every bot. We do use automated signals — abuse reports, unusual usage patterns, and, where necessary, targeted review following a specific complaint — to detect violations of this policy. We do not use customer content to train shared models, and access to your data for enforcement purposes is limited to what’s necessary to investigate a specific, credible report.

Depending on severity, a violation of this policy can result in:

• Removal of the specific offending content, document, or URL source from a bot’s knowledge base
• Temporary suspension of a specific bot or agent account
• Suspension of the entire account, pending review
• Permanent termination of the account for severe or repeat violations

We’ll generally notify you of the action taken and the reason, except where doing so would itself create a safety risk (e.g. tipping off an account engaged in active abuse). Paid balances are not automatically refunded on a for-cause termination — see our Cancellation & Refund Policy.

If you believe an enforcement action was taken in error, you can appeal via the contact page with subject line “AUP Appeal.” Include your account email and the bot/content in question. We’ll review and respond with our decision.

If you believe a JestBot-powered bot is violating this policy — whether you’re a visitor, a competitor, or an unrelated third party — report it via the contact page with the bot’s domain and a description of the issue. Copyright-specific reports should instead use our DMCA policy so they’re routed through the correct process.

We may update this policy as new features and abuse patterns emerge. Material changes will be reflected here with an updated date, and significant changes affecting what’s permitted may also be communicated by email to active account holders.