Acceptable Use Policy
This Runloop acceptable use policy (“AUP”) sets forth certain terms, conditions and restrictions relating to the access to, and use of, any products or services provided by Runloop (the “Services”) by or on behalf of any Runloop customer (“Customer”) under Customer’s agreement with Runloop applicable to the Services (the “Agreement”). The restrictions set forth in this AUP are in addition to those set forth in the Agreement (and in the event of any conflict between any provision of this AUP and any provision of the Agreement, the provision that is more protective of Runloop and the Services shall control). Any capitalized terms used but not defined herein shall have the meaning set forth in the Agreement.
This AUP may be updated by Runloop from time-to-time upon reasonable notice (e.g., via email, through the Services or by posting an updated version of this AUP). Updates of the AUP become binding, including on existing users, on the later of the date specified in the updated AUP or thirty (30) days after posting. Any violation of this AUP may result in the suspension or termination of Customer’s access to and use of the Runloop Services.
The Services are intended for use in deploying, orchestrating, running, observing and debugging AI-related workflows for AI applications, and any use that is inconsistent with the foregoing is not permitted. Without limiting the foregoing, Customer shall not (and shall not permit its authorized users to):
- interfere with or disrupt (or attempt to interfere with or disrupt) the Services, or gain (or attempt to gain) access to any systems, networks, platforms or services (collectively “Systems”) that connect thereto (except as required to appropriately access, deploy, maintain, or use the Services);
- use the Runloop Services to violate the security or integrity of, or otherwise abuse, any System of any party (including without limitation the Services), including but not limited to gaining unauthorized access to any System (including attempting to probe, scan, monitor, or test the vulnerability of a System), forging any headers or other parts of any message describing its origin or routing, interfering with the proper functioning of any System (including any deliberate attempt by any means to maliciously overload a System), implementing denial-of-service attacks, operating non-permissioned network services (including open proxies, mail relays or recursive domain name servers), using any means to bypass System usage limitations, or storing, transmitting or installing malicious code;
- attempt to access, search, or create accounts for any of Runloop’s services by any means other than Runloop’s publicly supported interfaces or as otherwise authorized by Runloop;
- use the Services to engage in or promote any other fraudulent, deceptive or illegal activities;
- use the Services to process, store or transmit material, including any Customer Data, in violation of any law or any third party rights, including without limitation intellectual property or privacy rights; GDSVF&H\10211846.1
- disclose to any third party (1) the results of any testing or benchmarking of the Services that Customer might conduct or (2) the results of any other performance-related statistics pertaining to the Services; or
- use the Services in any circumstances involving high-risk activities, including where failure could lead to death, personal injury or environmental damage, and Customer further acknowledges that the Services are not designed or intended for such use.
- use the services to mine cryptocurrencies
Scale your AI coding solution faster.
Stop building infrastructure. Start building your AI engineering product.