When planning a beta test, a common error by app developers is not taken into account with respect to the legality of the test. Just because the application is still in the pre-release phase doesn`t mean it`s normal to give up formalities. In fact, it is doubly important for a beta test specifically because it is not yet out of development and has not been released for the public. For more information on these agreements (including full NDA and BPA models), check out our Beta Test Agreement kit. If you are interested in other good practices for keeping the beta secret, download our eBook to keep beta tests confidential. After Square`s internal evaluation is complete or within two (2) days of Square`s written request, the recipient destroys all confidential information, erases or returns all tangible beta products, and updates each beta version of a Square mobile app to the latest published version of this Square mobile app. The provisions of this agreement will apply to all confidential information disclosed. On the other hand, a beta participation agreement (BPA) is a beta-specific document that defines the policies and expectations of your test. This is an opportunity to tell your testers what is expected (or not) of them during the test. A BPA is a legally binding document in case one of your testers becomes a rogue, but it is also a good opportunity to ensure that your testers understand the time and energy obligation you expect before having the beta product in hand. What is contained in this document depends on the company and the product. In the document, you can include warranty and liability information, restrictions on copying or cutting the beta product, and an overview of the tester`s obligations (and yours) during the beta test.