Software License Agreement Procedure

This section applies to the limitations of liability related to the software. In addition, insurance rules are important when the software provider will have its staff delivered to the customer on site. This is a certain type of liability risk that may need to be addressed in the same way. 4.1. Third Party Products. You may choose (including your authorized users) to use or obtain other third-party products or services in connection with the Software, including third-party applications (see Section 4.2 (Marketplace Applications) or implementation, adaptation, training or other services. Your receipt or use of third-party products or services is subject to a separate agreement between you and the third party. If you activate or use third-party products (including third-party applications in accordance with Section 4.2 (Marketplace Applications)) with the Software, you acknowledge that third parties may access or use your data if this is necessary to ensure the interoperability of their products and services with the Software. This may include transferring, transferring, modifying or deleting your data or storing your data on third-party or third-party systems. The use of your data by a third party is subject to the agreement in force between you and that third party. We are not responsible for the access or use of your data by third parties or their products or services, or for the security or privacy practices of any third party or its products or services. You are solely responsible for your decision to allow a third party or a third party product or service to use your data. It is your responsibility to carefully verify the agreement between you and the third party, as provided by the relevant third party.

ATLASSIAN DISCLAIMS ALL LIABILITY AND LIABILITY FOR THIRD PARTY PRODUCTS OR SERVICES (SUPPORT, AVAILABILITY, SECURITY OR OTHERWISE) OR FOR THE ACTIONS OR OMISSIONS OF THIRD PARTIES OR SUPPLIERS. « Licensed Copies » means the number of copies of the Software and Documentation that are granted to Licensee. As a general rule, the licensor should be required to resolve problems immediately; However, it is reasonable that response times should be proportionate to the severity of the problem. Therefore, the licensor would ideally propose a « service level agreement » that would require the licensor to respond to a system reduction/attenuation problem within a very short period of time (z.B. 1-2 hours) and make efforts to address it. to quickly resolve a serious obstacle (for example.B. 4 hours); and other material errors and defects in a reasonable and immediate manner (for example. B 8-hour response and 24-48 hour correction). If the correction cannot be completed during these periods, the licensor must provide a « problem treatment », i.e.: A temporary correction that allows the licensee to continue to use the software for the most part as originally intended. The licensor should also be required to continue to do their best to completely resolve the issue thereafter (although it is fair for the licensor to fix some really minor issues with their next software release or cycle). If training is required, the obligation for the licensor to provide (when and where) must be indicated.

Maintenance and support (fixed, patched versions, new updates/updates, telephone advice, online support and/or programming services) are almost always required. Thus, either the agreement should define the licensee`s right to assistance, or, at the same time, a separate maintenance contract should be signed, or the agreement should give the licensee the right to enter into a maintenance contract. . . .