In plain language
A quick orientation. The numbered sections below are the binding text.
- A Bot acts for you inside the limits you set. You decide what it may do on its own and what it must ask you about first.
- Consequential actions can be held for your Approve, Edit or Decline. Each Bot has a monthly model-cost cap, and a platform kill switch can stop new Bot work.
- You are responsible for what your Bots do within those limits. Start narrow and widen access as you build trust.
1. Approvals
When a Bot proposes an action that needs your approval, the conversation shows what it wants to do and the values it will use. You can Approve, Edit or Decline. An approval controls the proposed action. It does not reverse work a Bot has already completed.
Review the target, scope and values before you approve. If you cannot tell what an action will do, ask the Bot to explain it or to produce a draft first.
2. Set boundaries in the brief
Tell the Bot what it can do and where it must stop. Prefer explicit boundaries for:
- sending messages or invitations
- publishing content
- purchases and financial transfers
- deleting or overwriting data
- changing permissions
- production changes
- accepting legal terms
3. Limits, caps and the kill switch
- Autonomy setting. Choose how much a Bot may do without asking.
- Monthly model-cost cap. Every Bot has a monthly cap (the default is $25 and you can change it per Bot). You get a warning at 80 percent and the Bot stops at the cap, and tells you in the conversation.
- Routines. A routine does not stack a new run behind one that is waiting on you. After repeated blocked runs it pauses itself and tells you.
- Archive or delete. You can archive a Bot, which pauses its routines and cancels its open work, or delete it for good.
- Kill switch. Zoft can stop all new Bot work across the platform.
4. Passwords, codes and secrets
- Do not paste passwords or one-time codes into a normal chat message.
- Connect tools through the connection dialog so credentials are stored encrypted, not typed into a conversation.
- Give a Bot only the tools and permissions a task needs, and start with read-only or draft tasks.
- Review connected tools and active routines regularly, and pause a routine when its source system changes.
5. What you are responsible for
You are responsible for the actions your Bots take and the messages they send within the limits you set, and for having the consents the law requires. See the Acceptable Use Policy and the Terms of Service. AI output can be wrong, so keep a person in the loop for consequential decisions. Report a problem with a Bot to security@zoft.ai, or misuse by someone else on the abuse page.
See also the Privacy Policy and our Trust page.