Usage Policy
Last Updated: August 2026
01Acceptable AI Content
Butler AI is operated and maintained by Sevorse. Users must inspect and verify all generative outputs (text drafts, marketing workflows, and assistant responses) initiated via Butler before publishing. Generating malicious spam, harassment, disinformation, or material in violation of safety standards is strictly prohibited.
02Platform Limits & API Health
Butler soft-limits simultaneous executions to ensure balanced resource allocation. These parameters restrict automated scraping, simultaneous high-frequency query spamming, and headless automation from degrading third-party model connections.
03Public Chat Sharing & Continuable Conversations
When sharing chats via public links, Butler provides configurable options regarding recipient interaction and data preservation:
- Private vs. Public Links: By default, chats are kept private to your account. Creating a public link creates a sharable URL that allows anyone with the link to view the conversation up to the point of sharing.
- Continuable Chat Option: When enabling a public link, you can choose whether to allow "Continuable chat". If enabled, recipients can continue the conversation and ask follow-up questions with Butler in their own session without altering your original chat history. If disabled, the link remains a frozen read-only snapshot.
- Responsible Sharing: Do not share conversations containing personal sensitive information, private credentials, or copyrighted third-party assets without authorization. You can revoke public access at any time by toggling the chat back to "Keep private".
04Manual Confirmations & High-Risk Actions
Certain high-risk parameters require explicit manual confirmations to proceed. Butler enforces explicit dialog verification rules when:
- Initiating external subscription models or Razorpay payments.
- Overwriting local credentials, stored API keys, or clearing system memory.
- Purging stored chat sessions permanently from your local workspace.
05Compliance & Diagnostics
Butler periodically runs diagnostic audits against local configurations to prevent programmatic loops that trigger API rate limits. Local logs are not shared and exist solely inside the user's localized workspace parameters.