← General Terms

Transfer Service Terms

Version 2026v1Last updated
Draft — not yet in force

This document is a working draft pending review by legal counsel. It contains unresolved placeholders, it has not been adopted, and it does not currently bind Beam or any user of Beam services.

These Product Terms apply to the Beam Transfer Service 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 correctness of each transfer definition, including its sources, destinations, routes, and transformation settings;
  • obtaining and maintaining valid credentials for every source and destination, and for the scope of access those credentials grant;
  • verifying that it holds the rights necessary to read data from each source and to write it to each destination, including in every jurisdiction the transfer touches;
  • the capacity, quota, retention, and billing terms of the third-party storage and network providers it nominates, which Beam does not control;
  • validating delivered data against its own requirements before relying on it; and
  • ensuring sufficient Credits are available for a transfer to complete.

Beam will not be responsible for any defect, failure, liability, or vulnerability in the operation or security of the Transfer Service caused by Customer’s configuration, Customer’s credentials, a third-party source or destination, or Customer’s failure to meet the obligations in sections 1.1 to 1.6 above.

2. Data Retention

2.1 Transferred content

The Transfer Service moves data between the endpoints Customer nominates. Beam’s control plane records transfer metadata rather than the contents of transferred data. Content held transiently by network infrastructure while a transfer is in flight is not retained by Beam as a durable copy after the transfer reaches a terminal state.

2.2 Transfer records

Beam retains the records required to schedule, verify, bill, and audit a transfer — including the transfer definition, delivery evidence, and usage measurements — for as long as the account is active and thereafter as required for billing, audit, and legal purposes. Task-level execution records, including attempt and per-chunk verification records, are retained for 7 days after the transfer reaches a terminal state.

2.3 Audit records

Audit records relating to a transfer are retained for a defined period, currently 365 days.

3. Additional Definitions

“Destination” means a storage location, endpoint, or service to which Customer directs the Transfer Service to write data.

“Source” means a storage location, endpoint, or service from which Customer directs the Transfer Service to read data.

“Delivery Evidence” means the records Beam produces to establish that data was carried and delivered as instructed, including integrity measurements and participant attestations.

“Terminal State” means the state in which a transfer has completed, failed, or been cancelled, and no further attempts will be made.

Beam makes this document available for information purposes. It may not reflect the most current legal developments, and Beam does not represent, warrant, or guarantee that it is complete, accurate, or up to date. This information is subject to change without notice. The materials on this page are not intended to constitute legal advice. You should not act, or refrain from acting, on the basis of this page without obtaining professional advice regarding your particular facts and circumstances.

Transfer Service Terms — Beam