Agentic Actions may be wrong or unintended; approval controls are aids only and Provider is not liable if they fail
Agentic Actions may be inaccurate, incomplete, delayed, unsuccessful or unintended. Approval and automated-review controls are provided as aids only, may not identify or prevent every unintended, unauthorized or harmful action, and do not reverse completed actions. The Provider is not liable for any Agentic Action that an approval or automated-review control fails to prevent.
Supporting quotations
Agentic Actions may be inaccurate, incomplete, delayed, unsuccessful, or unintended.
Approval and automated-review controls are provided as aids only, may not identify or prevent every unintended, unauthorized, or harmful action, and do not reverse completed actions.
Provider is not liable for any Agentic Action that an approval or automated-review control fails to prevent.
Not stated here
Whether the Provider offers any way to undo a completed Agentic Action is not stated.
Security & Safeguards · Restriction or exception
Customer must use appropriate human review before permitting Agentic Actions, especially high-impact ones
The Customer will use appropriate human review before permitting Agentic Actions, including those involving external communications, financial transactions, data deletion, permission changes, production systems, legal commitments or material effects on third parties.
Supporting quotations
Customer will use appropriate human review before permitting Agentic Actions, including those involving external communications, financial transactions, data deletion, permission changes, production systems, legal commitments, or material effects on third parties.
Not stated here
What counts as appropriate human review is not defined.
Security & Safeguards · Restriction or exception
Bots for the same User share an environment, deleting a Bot may not delete shared items, and Customer must clean up
Bots associated with the same User may share the persistent environment and must not be treated as separate security boundaries. Deleting a Bot may not delete shared files, sessions, credentials or routines. The Customer is responsible for deleting or disabling bots, removing data, revoking access and disabling routines when no longer required.
Supporting quotations
Bots associated with the same User may share that environment and must not be treated as separate security boundaries.
Deleting a Bot may not delete shared files, sessions, credentials, or routines.
Customer is responsible for deleting or disabling bots, removing data, revoking access, and disabling routines when no longer required.
Not stated here
How a Customer can remove shared files, sessions, credentials or routines is not described here.