Rooms and Tunnels Terms
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 Beam Rooms and Beam Tunnels 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:
- deciding who may join a Room or reach a Tunnel, and for the distribution of any link, code, or credential that grants access;
- everything exposed through a Tunnel, including any service, file system, or device made reachable from the public internet, and for securing it independently of the Tunnel;
- the conduct of Session Participants it admits, and for the content they send or receive;
- closing a Session or revoking access when it is no longer required; and
- ensuring that exposing a service or sharing content through the Services is lawful and permitted by any third party whose systems or data are involved.
Beam will not be responsible for any defect, failure, liability, or vulnerability in the operation or security of Rooms or Tunnels caused by Customer’s configuration, by the services Customer chooses to expose, by the parties Customer admits, or by Customer’s failure to meet the obligations in sections 1.1 to 1.5 above.
A Tunnel makes a service reachable by anyone who can reach its endpoint. Customer should treat an active Tunnel as public unless it has applied its own access control.
2. Data Retention
2.1 Session content
Rooms and Tunnels carry data between participants. Beam’s control plane records session metadata rather than session content, and does not retain a durable copy of content carried through a Session after the Session ends.
2.2 Session records
Beam retains the records required to operate, bill, and audit a Session — including its configuration, lifetime, participant counts, and usage measurements — for as long as the account is active and thereafter as required for billing, audit, and legal purposes.
2.3 Expiry
A Session may carry an expiry. On expiry the Session ends and its endpoint stops being reachable. Expiry is an operational control, not a guarantee of deletion at any third party to which content was sent.
3. Additional Definitions
“Room” means a Beam session through which two or more parties exchange data directly with one another.
“Tunnel” means a Beam session that makes a service running on Customer’s machine or network reachable at an endpoint provided by Beam.
“Session” means an instance of a Room or a Tunnel, from creation until it ends or expires.
“Session Participant” means any party that joins a Room or connects to a Tunnel.
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.