Talos Agent - Security & Liability Disclaimer (Safety Notice)
This Security and Liability Disclaimer / Safety Notice (the "Notice") is a legally binding disclosure that governs your deployment and operation of the native downloadable Talos Agent software ("Agent").
The Talos Agent is a powerful native application daemon designed to automate complex desktop interactions, operating system functions, file modifications, and network operations. Because the Agent executes locally on your endpoint infrastructure, it operates with the privileges, permissions, and security scope of the user account under which it is installed.
1. AGENT AUTHORIZATION & PRIVILEGE STATEMENT
During installation, the Talos Agent requests system permissions sufficient to control your operating system's user interface, run system shell scripts, and connect to remote hosts. You hereby acknowledge that:
- Elevated Access Permissions: The Agent requires permissions to read/write directories, inspect process handles, interact with local keystroke listeners, manipulate browser sessions, and execute local executables.
- Explicit Consent: By proceeding with the installation of the Agent binary and running any Customer-Generated Workflows, you grant the Agent explicit and ongoing authorization to perform these native operations on your system.
- Local Environment Security: You are solely responsible for securing the host operating system, restricting access to the folder in which the Agent binary resides, and ensuring that no unauthorized parties can modify the workflow configurations or local settings files.
2. LIMITATION OF LIABILITY & DAMAGE EXCLUSIONS
:::danger Disclaimer of Consequential & System Damage TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL TALOS RPA SUITE INC., ITS AFFILIATES, OR THEIR DIRECTORS, OFFICERS, EMPLOYEES, OR LICENSORS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, EXEMPLARY, OR PUNITIVE DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF REVENUE, LOSS OF PROFITS, DATA LOSS, SYSTEMS CORRUPTION, HARDWARE INSTABILITY, OUTAGES, CRITICAL PROCESS ERRORS, OR THIRD-PARTY ACCOUNT SUSPENSIONS) ARISING FROM OR IN CONNECTION WITH THE DEPLOYMENT, INTENDED OR UNINTENDED AUTOMATION, AND LOCAL EXECUTION OF WORKFLOWS BY THE TALOS AGENT. :::
2.1 Financial Liability Cap
Except as otherwise provided in your Master Services Agreement (MSA) or enterprise subscription Order Form, the total cumulative liability of Talos and its Affiliates for all claims arising out of this Software’s installation, execution, or performance shall be strictly capped at and limited to the total fees actually paid by you to Talos in the twelve (12) months preceding the first event giving rise to liability.
2.2 System Damage Acknowledgment
You explicitly agree that Talos has no insight into, and no control over, the specific commands, parameters, mouse targets, and keystrokes written into your local Workflows. The execution of incorrect, unvalidated, or looping automated steps remains your sole business and technical risk.
3. SECURITY RESPONSIBILITY MATRIX
The secure operation of an RPA suite is a joint responsibility. To protect your enterprise network, systems, and data, the security obligations are split as follows:
| Security Domain | Talos Responsibilities | Customer Responsibilities |
|---|---|---|
| Platform Cryptography | • Multi-tenant isolation on Cloud databases • TLS 1.3 in-transit logs • AES-256 Cloud rest keys | • Enforcing strong multi-factor authentication (MFA) • Disabling insecure browser configurations |
| Local OS Security | • Digitally signed binaries and automated malware scans • Safe execution APIs | • Hardening the host OS • Restricting folder and write permissions |
| Workflow Validation | • Provisioning Process Designer boundary guards • Type safety validations | • Testing all loop limits and action outcomes in a sandbox environment |
| Credentials & Tokens | • Envelope encryption on cloud secret lockers • Transient memory decryption | • Avoiding hardcoded keys in workflow definitions • Utilizing local environment variables on nodes |
4. CRITICAL RUNTIME SAFETY RULES FOR USERS
To prevent severe systems damage, all developers and administrators of the Talos RPA Suite must strictly adhere to the following safety rules:
1. Sandbox Validation
Never deploy a new Workflow directly to a production server. Always test execution parameters in a dedicated, isolated test virtual machine (sandbox).
2. Boundary Checks
Always configure explicit loop termination conditions and timeout limits on your Actions to prevent infinite UI execution loops that can freeze OS rendering loops.
3. Error Handling Blocks
Ensure that all critical steps (e.g., writing to database, copying files, closing applications) are nested within try-catch or exception-handling blocks to prevent unhandled Agent termination.
4. Anti-Virus Exclusions
If your company's Endpoint Detection and Response (EDR) or anti-virus system flags the Agent's simulated keystroke/mouse injection driver as high-risk, verify the binary's cryptographic SHA-256 hash against the official Talos release page before adding a whitelist exception.