This clause, also known as the beta „non-responsibility clause,“ explicitly states that the „AS IS“ application provided is authorized and contains errors and stability issues. Testing is the only goal behind the use of the application and the developer disclaims any responsibility for data loss, damage or loss of profit resulting from the use of the beta application. Similarly, the developer refuses all explicit and unspoken guarantees for the application to be tested and the tester uses the application at his own risk. As you send beta updates, it`s a good place to explicitly state that they are subject to the same conditions. Here`s an example of Paragoni apps: you`ll certainly have some criteria that will define who can participate in your beta test, and you`ll indicate them here. A „No-Conflict“ provision must be included to keep your competitors away from your beta test. You should also mention the registration channels and the process by which your testers can join the program. This clause is often ignored for closed beta versions, as participating testers have been previously verified and selected by the developer. However, for an open beta agreement to be opened, these rules and mechanisms must be clearly stated and clarified. Here is an example of Square Enix: 7. The beneficiary`s obligations under this agreement remain at each termination of this agreement.