Sample Beta Test Agreement

Parties who enter into the beta agreement may indicate in this clause their preferential method of settlement. You can indicate a jurisdiction and jurisdiction to which disputes are settled in accordance with the laws of that jurisdiction. Alternatively, both parties may agree to submit to binding arbitration, in which they resolve their disputes through mutually elected arbitrators. In addition, a mixture of the two approaches can be used if you indicate the arbitration procedure as non-binding. Here is an example of Splunk: the licensee is responsible for all costs and expenses related to the use of the beta product and the completion of all testing and evaluation activities. 2. The recipient agrees that it is strictly confidential at all times and does not pass on confidential information (as defined below) to third parties, unless this information has been approved in writing by the Entity and does not use the confidential information for any purpose other than the Service`s evaluation. The recipient only authorizes staff members who need to be aware of and who have signed confidentiality agreements or who are subject to confidentiality obligations at least as restrictive as those contained in them. “confidential information,” any non-public material and information made available to the recipient or made available to the recipient by the company, including products and services, information about technology, know-how, processes, software programs, research, development, financial information and information provided by the entity through third parties; You will certainly have some criteria that will define who can participate in your beta test, and you will 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: Scope of Agreement. Beta customers will be allowed to take advantage of this contract to test and provide information feedback and other feedback on PlanGrid on one or more proprietary hosted software applications, non-commercial, application platform interfaces, services, features and/or features related to the existing account, as described in more detail in the beta test order form (the “beta products”). This agreement applies to all beta products made available to PlanGrid`s beta client, including, but not exclusively, all beta products identified by PlanGrid as “beta” or a similar stage of development. PlanGrid reserves the exclusive and absolute discretion of the beta products made available to the Beta customer during their lifetime. While the beta customer is not obligated to use or activate beta products, the beta customer, if he chooses to do so, is subject to the terms of this agreement. The non-disclosure agreement (NDA) is absolutely necessary for a closed beta to ensure that your trade secrets are not disclosed to the market until you have validated and perfected your application. In the beta phase, your application still has some annoying errors and stability issues to solve. Discussions about these issues should remain private to prevent them from affecting the way your version is received. these issues need to be resolved before they are published.