Transfer Studio Terms

These Product Terms apply to Beam Transfer Studio and plug into the Beam General Terms. Capitalised terms not defined here have the meaning given in the General Terms.

1. Customer Responsibilities

Customer is solely responsible for:

• the design and correctness of each Workflow, including its triggers, schedules, branching, and error handling;
• the consequences of Unattended Execution, including work a Workflow performs when no person is present to review it;
• the credentials it stores as Connections, the scope of access they grant, and their rotation and revocation;
• reviewing any Action package a Workflow invokes before relying on it, including packages published by third parties and the trust level assigned to them;
• testing Workflows before enabling them against production systems or data; and
• ensuring sufficient Credits are available for scheduled runs to complete.

Beam will not be responsible for any defect, failure, liability, or vulnerability in the operation or security of Transfer Studio caused by Customer’s Workflows, Customer’s Connections, third-party Action packages, or Customer’s failure to meet the obligations in sections 1.1 to 1.6 above.

2. Data Retention

2.1 Connections

Credentials stored as Connections are held so that Workflows can run without a person present. They are retained until Customer deletes the Connection or closes the account. Deleting a Connection does not revoke the underlying credential at the third-party service; Customer must revoke it there.

2.2 Workflow definitions and run history

Workflow definitions are retained until deleted by Customer. Run records, including status, timings, and diagnostics, are retained for as long as the account is active and thereafter as required for billing, audit, and legal purposes.

2.3 Diagnostics

Diagnostic output captured from a run may include values a Workflow passes between steps. Customer should not place secrets in Workflow parameters or step output where a Connection is the appropriate mechanism.

3. Additional Definitions

“Workflow” means an automation Customer defines in Transfer Studio, comprising the steps to run, the order in which they run, and the conditions under which they run.

“Connection” means a credential or authorisation Customer stores in Transfer Studio so that Workflows may access a third-party service on Customer’s behalf.

“Unattended Execution” means the running of a Workflow on a schedule or trigger, without a person initiating or supervising that run.

“Action” means a packaged unit of functionality a Workflow may invoke, as further described in the Action Registry Terms.