API and SDK Terms
These API and SDK Terms, together with any and all appendices, attachments, exhibits and amendments hereto (referred to herein as these “Terms”) are entered by and between League, Inc. (“League”) and the customer set out in the signature line below (“Customer”) and each of League and Customer, for the purposes of these Terms, a “Party” and collectively, the “Parties”) and will be effective as of the earlier of: (1) the date of Customer’s first access to the APIs or SDKs (as defined below); and (2) the Effective Date (as defined in the signature line below).
Customer has entered into a platform master services agreement with League for the license of the League Platform (the “Underlying Agreement”). Customer now requests, and League hereby grants, Customer the right to access and use League’s proprietary application programming interfaces (each, an “API”) and software development kits for the APIs (each, an “SDK”), as well as any related materials, including installation tools, sample code, source code, software libraries, and documentation (“Related Materials”), in order for Customer to enhance the League Platform and Customer’s other application(s) and/or website(s) as permitted herein, (“Customer Developed App(s)”). Each Party agrees to comply with these Terms and agrees that these Terms control Customer’s relationship with League with respect to all licensed APIs, SDKs and Related Materials. If Customer uses the APIs, SDKs or Related Materials as an interface to, or in conjunction with, other League products or services, then the terms for those other products or services also apply. Any capitalized terms used, but not defined, shall have the meanings given to such terms in the Underlying Agreement.
Part A: APIs
1. API Account and Registration
In order to access the APIs, Customer or Customer’s Users will be required to provide certain information (such as identification or contact details) as part of the registration process for the APIs, or as part of Customer’s continued use of the APIs. Customer will ensure that any registration information Customer gives to League will be accurate and will promptly inform League of any updates or inaccuracies to or in such information that it becomes aware of.
2. Use of the APIs
a. API Availability. League shall make the licensed APIs (and associated Documentation) available to Customer set out in Appendix 1 or the Underlying Agreement for the approved Use Cases specified in Appendix 1 or the Underlying Agreement.
b. Permitted Access. Customer will only access (or attempt to access) an API by the means described in the Documentation of that API and using the applicable security key (“API Key”) that League provisions, causes or permits to be provisioned, or otherwise makes available to Customer now or in the future for the purpose of accessing such API. Customer will not misrepresent or mask either Customer’s identity or the identity of the Customer Developed Apps when using the APIs or the API Key. Notwithstanding anything to the contrary herein, Customer shall not use any API Key, or any other means, to access (or attempt to access) any API that League has not licensed to Customer, even though such API Key may enable or provide Customer with the ability to access such unlicensed APIs.
c. API Limitations. League may enforce reasonable limits and other functional restrictions built into the APIs relating to the access, timing, or usage thereof. Customer will not circumvent, or attempt to circumvent, such limitations or restrictions on the applicable APIs. If Customer would like to use any API beyond these limits, the Parties agree to negotiate in good faith any additional terms and conditions applicable to such usage.
d. Non-Exclusivity. Customer acknowledges that League may independently develop products or services that incorporate similar functionality as the Customer Developed Apps or any other products or services; provided League does not use any Confidential Information of Customer or use any Customer Intellectual Property Rights in such products or services.
3. Customer Developed Apps
a. Use Generally. League shall provide and Customer may use the APIs solely as agreed upon between League and Customer herein and in any additional applicable terms (including as set out in the Underlying Agreement), and in compliance with all applicable Laws and with any usage guidelines, standards, or requirements that the Parties may agree to from time to time. Customer shall not be permitted to use the APIs for any other purpose without League’s express prior written consent.
b. Monitoring. CUSTOMER AGREES THAT LEAGUE MAY MONITOR CUSTOMER’S USE OF ANY API BY THE CUSTOMER DEVELOPED APPS THROUGH ANY TECHNICAL MEANS IN ORDER TO ENSURE QUALITY, IMPROVE LEAGUE’S PRODUCTS AND SERVICES, AND VERIFY CUSTOMER’S COMPLIANCE WITH THESE TERMS. Without limiting the foregoing, League may access and use the Customer Developed Apps for the purpose of identifying security issues that could affect League, its customers, and/or partners, and any of their networks or systems. Customer will not interfere with League’s monitoring of Customer Developed Apps, provided that in doing so, League will not overcome or circumvent (or attempt to do so) any security measures incorporated into the Customer Developed Apps. League may temporarily suspend access to the APIs by Customer in accordance with suspension rights set out in the Underlying Agreement or in the event of any material breach by Customer of these Terms that causes or results in a material threat to the security, integrity, or availability of the League Platform or to the APIs, provided that League provides Customer with prompt notice of the breach and security threat and will use commercially reasonable efforts to impose the least disruptive restrictions on or suspension of access to the APIs as are available to implement the required protections.
c. Security. Customer will protect user information collected by the Customer Developed Apps, including all Personal Information, from unauthorized access or use and will promptly report to League any unauthorized access or use of such information to the extent required by applicable Law. Customer will implement security measures to protect its own systems and data when using the APIs and the Customer Developed Apps that are no less restrictive than the obligations and requirements that apply to League as set forth in the, Underlying Agreement as applicable to Customer, mutatis mutandis.. Customer agrees to implement and maintain appropriate technical and organizational measures to safeguard the security of the APIs and the API Keys from infringement, misappropriation, theft, misuse, or unauthorized access, including the deployment and operation of industry standard end-to-end encryption, secure coding practices, firewalls, access controls, multi-factor authentication of all Users of the Customer Developed Apps, and monitoring systems. Customer agrees to treat the APIs as Confidential Information of League pursuant to the confidentiality provisions set forth of the Underlying Agreement and, as such, will not share any of the APIs with any unauthorized Third Party.
d. Ownership. As between Customer and League, League owns all right, title, and interest in and to the APIs (including all Intellectual Property Rights). Without limiting the generality of the foregoing, League and Customer further agree that the APIs are included in the definition of Intellectual Property, Intellectual Property Rights, and League IP in the Underlying Agreement, including the sections of the Underlying Agreement covering intellectual property and data use rights, confidentiality and privacy, indemnities, representations and warranties disclaimers and limitations of liability and general or miscellaneous.
e. Virus Prevention. Customer agrees to implement and maintain current industry state-of-the-art anti-virus measures to detect, prevent and remove viruses and other contaminants designed to damage, alter, delete, disable, or permit unauthorized access to, the Party’s respective databases, systems, equipment or property, and to prevent the spread of computer viruses between the Parties.
f. Privacy. Customer will comply with all applicable privacy Laws s including those applying to Personal Information and/or personal health information. Customer will provide and adhere to a privacy policy for the API App(s) that clearly and accurately describes to users of the Customer Developed Apps, what user information Customer collects, and how Customer uses and shares such information (including for advertising) with League and Third Parties.
g. Testing and Review. Customer will test all Customer Developed Apps for security, operability, and quality assurance purposes, and for conformance applicable industry standards and with these Terms (the “Standards”). Customer agrees that it will conduct such testing to the Standards and will, if requested by League, certify to League that each applicable Customer Developed App has been tested for conformance with the Standards. League retains the right, but not the obligation, to independently test or review the Customer Developed Apps for the purpose of ensuring compliance with the Standards and with these Terms, at any time, in League’s sole discretion. Customer agrees to notify League of any Customer Developed Apps that do not conform to the Standards or to these Terms. In the event that Customer or League determines that the Customer Developed Apps are non-compliant with any Standards or with these Terms, Customer shall refrain from deploying the Customer Developed Apps until compliance is attained. League will not be liable to Customer for any damages incurred by Customer or to any Users of the Customer Developed Apps to the extent that such damages are attributable to Customer’s failure to test the Customer Developed Apps against the Standards.
h. Customer Obligations to Users. Customer will be solely responsible for hosting, serving, operating, supporting, and maintaining all Customer Developed Apps, including, as applicable, providing Users of the Customer Developed Apps with: (i) technical documentation, (ii) FAQs, (iii) information regarding support (including without limitation support contact information), (iv) technical information, and (v) instructions on how to use and navigate the Customer Developed Apps, known limitations, information to be exchanged, and other pertinent information about the Customer Developed Apps for the Customer Developed Apps that is viewable and can be downloaded from Customer’s website or from within the Customer Developed Apps.
i. End User License Agreement. In addition to the requirements in the Underlying Agreement, the Customer’s User or end user terms of use will include terms that are no less restrictive than these Terms. Customer will monitor use of the Customer Developed Apps for any activity by Users that violates such terms of use, applicable Laws, or these Terms, including any fraudulent, inappropriate, or potentially harmful behavior, and promptly restrict the access of any such Users from making any further use of the Customer Developed Apps.
j. End User Support. Customer will be responsible for providing all support to Users purchasing or using the Customer Developed Apps as well as all documentation, upgrades, and bug fixes for the Customer Developed Apps, unless otherwise agreed to by the Parties hereto in writing. Customer must provide support contact information for its end users.
k. Use of APIs. Customer is responsible for all use of the APIs by Customer or its Users using the API Keys that League provides to Customer, directly or indirectly, whether such access or use is permitted by or in violation of these Terms. Without limiting the generality of the foregoing, Customer is responsible for all acts and omissions of Customer’s Users in connection with the Customer Developed Apps and for any and all use of the API by such Users. Any act or omission by Customer’s User that would constitute a breach of these Terms if taken by Customer will be deemed a breach of these Terms by Customer. Customer will make reasonable efforts to make all of Customer’s Users aware of these Terms’ as applicable to such User’s use of the APIs and shall cause Users to comply with such provisions.
l. Regulatory Approval. Customer agrees not to pursue any regulatory or marketing permissions, without first obtaining League’s written consent, where obtaining such permissions may require or result in any League’s Confidential Information or the League Platform being or becoming subject to regulation or that might otherwise impose any obligation, limitation, or restriction on League. At League’s request, Customer will provide, as soon as is reasonably practicable, any clearance Documentation that supports or authorizes the marketing of the Customer Developed App. Without limiting the generality of the foregoing, Customer will not market the Customer Developed Apps that require pre-market clearance or approval unless such clearance and approval has been obtained in accordance with all relevant regulations and regulatory approvals.
4. API Prohibitions
When using the licensed APIs, Customer may not (or may not allow those acting on Customer’s behalf to):
a. Distribute, publish, sell, lease, lend, make available, or sublicense access to an API, either in whole or in part, for use by a Third Party except to the extent used by the Customer Developed Apps as expressly permitted under these Terms or the Underlying Agreement.
b. Design or build any Customer Developed Apps that function substantially the same as, or which operate by passing through direct access to, the APIs, and distribute, publish, sell, lease, lend, or otherwise make available such Customer Developed Apps for use by Third Parties.
c. Perform an action with the intent of introducing to League products and services any viruses, worms, defects, Trojan horses, malware, or any items of a destructive nature.
d. Interfere with or disrupt the APIs or the servers or networks providing the APIs, or circumvent any access, timing, or usage limitations or other functional restrictions built into the APIs.
e. Reverse engineer or attempt to extract the source code from any API or any related software, except to the extent that this restriction is expressly prohibited by applicable Law.
f. Share any API Key used to access an API with any Third Party (except for Customer’s authorized subcontractors and representatives), or store any API Key in any locations that are not protected by reasonable safeguards designed to protect the security and integrity of the API Key.
5. Application Data and Content
a. Submission of Application Data. League does not acquire any ownership of or license to use any Intellectual Property Rights in any data (“Application Data”) that Customer submits to the APIs, except as expressly provided in the Underlying Agreement, and nothing in these Terms provides League any rights to use or access such Application Data. Before Customer submits Application Data, or causes or allows Application Data to be submitted, to the APIs through the Customer Developed Apps Customer will ensure that Customer has the necessary rights (including the necessary rights from Customer’s Users) with respect to such Application Data in order for League to perform its obligations under these Terms and the Underlying Agreement.
b. Prohibitions on Application Content. Except where authorized or permitted under applicable Laws, Customer will not, and will not permit Customer’s Users or others acting on Customer’s behalf to:
- Except as necessary for the operation of the Customer Developed App(s) oras permitted by Customer, copy, translate, modify, create a derivative work of, sell, lease, lend, convey, distribute, publicly display, or sublicense to any third party any content or other materials (“Application Content”) that an API returns to the Customer Develop App(s) from the League Platform; or
- Misrepresent the source or ownership of the Application Content.
Part B: SDKs
1. SDK Availability
League shall make the licensed SDKs set out in the Underlying Agreement or in Appendix 1, together with the Related Materials, available to Customer for the approved Use Cases set out in the Underlying Agreement or in Appendix 1.
2. Permitted Uses
Subject to these Terms, and without limiting the generality of the foregoing section, League authorizes Customer to: (i) use the SDKs solely for Customer’s internal business purposes of, as described in the Underlying Agreement to communicate and interoperate with the APIs and League’s Systems; (ii) incorporate, modify, or merge any sample code provided with the SDKs into the Customer Developed Apps solely to the extent necessary for incorporation of the SDKs into the Customer Developed Apps; (iii) package any libraries provided as part of the SDKs for redistribution with the Customer Developed Apps; (iv) compile or otherwise transform the SDKs, or any component thereof, into an object or other machine-readable program format that is suitable for distribution; and (v) use, reproduce and redistribute the SDKs in executable or object form only and only as incorporated into the Customer Developed Apps. Customer acknowledges and agrees that there are no implied licenses granted under these Terms, and that the SDKs may be used only for the purposes set out in the Underlying Agreement subject to these Terms. No license is granted hereunder to combine the SDKs with any software other than the Customer Developed Apps, distribute or otherwise make the SDKs available to a Third Party on a standalone basis, or to use the SDKs for any other purpose not permitted by these Terms. League reserves all rights that are not expressly granted.
3. SDK Restrictions
Customer may not use the SDKs to: (i) design or develop anything other than the Customer Developed Apps in a manner consistent with these Terms; (ii) make any more copies of the SDKs than are reasonably necessary for Customer’s authorized use thereof; (iii) modify, create derivative works of, reverse engineer, reverse compile, or disassemble the SDK, or any portion thereof, other than sample code included therein; (iv) distribute, publish, sell, transfer, assign, lease, rent, lend, or sublicense the SDKs, either in whole or any component thereof, to any Third Party except to the extent embedded into the Customer Developed Apps as permitted herein; or (v) remove or otherwise obfuscate any proprietary notices or labels from the SDK. Without limiting the generality of the foregoing, Customer may not use the SDKs except in accordance with applicable Laws, nor may Customer export the SDKs from and outside the United States of America or Canada, except as permitted under the applicable Laws of the United States of America or Canada.
4. Users
If any constituent file of the SDKs is distributed with the Customer Developed Apps, then Customer will ensure that any User obtaining access to such Customer Developed Apps will be subject to an end-user license agreement that is consistent with the end user license requirements set forth in the Underlying Agreement and no less restrictive or protective of League than these Terms.
5. Copyright Notice
Customer must not remove any copyright and other proprietary rights notices that accompany the SDK in any copies of the SDKs that Customer creates.
6. Proprietary Rights
As between Customer and League, League owns all right, title, and interest in and to the SDKs (including all Intellectual Property Rights therein), and Customer will be the sole and exclusive owner of all right, title, and interest in and to the Customer Developed Apps (including all Intellectual Property Rights therein), exclusive of League’s ownership of the SDKs.
7. Open Source Software
Some of the software included in or distributed as part of the SDKs may be offered under an open source license (the “Open Source Components”). Open Source Components are not licensed under these Terms, but are rather licensed under the terms of the open source license associated with such Open Source Components. League represents and warrants that no Open Source Components are or will be subject to restrictions or licenses that would require Customer to redistribute any of Customer’s source code for free or otherwise. Upon Customer’s reasonable request, League will provide Customer with an up-to-date list of Open Source Components included in or distributed as part of the SDKs.
Part C: General Terms
1. Fees
Customer’s use of the APIs and SDKs is subject to payment of the fees set forth in Appendix 1 or the Underlying Agreement.
2. Third Party Content
The Third Party Content terms (if applicable) in the Underlying Agreement shall apply to Third Party Content contained in the APIs and SDKs.
3. Ownership
Customer understands and acknowledges that the software, code, proprietary methods and systems that make up the APIs, SDKs and Related Materials will be League IP owned by League.
4. Rules of Conduct
Except as otherwise expressly permitted herein, Customer agrees not to use the APIs or SDKs in a manner that violates League’s Acceptable Use Policy, as set forth in Appendix 2. In the event of any conflict between the Acceptable Use Policy and these Terms, the applicable provision of these Terms shall prevail.
5. Term and Termination
These Terms shall commence upon Effective Date and will continue in force in accordance with the term of the Underlying Agreement. These Terms will be co-terminus with the Underlying Agreement. Upon any termination or expiration of these Terms or discontinuation of Customer’s access to an API or SDK, Customer will immediately stop using the API or SDK and delete any cached or stored content. League may independently communicate with any account owner whose account(s) are associated with Customer and developer credentials to provide notice of the termination of Customer’s right to use an API or SDK.
6. Geographical Restrictions
League makes no representation that any of the APIs and SDKs are appropriate or available for use in locations outside the United States or Canada or all territories within the United States or Canada. If Customer chooses to use an API or SDK internationally, Customer does so on its own initiative and will be responsible for compliance with local laws.
7. Training Support and Updates
a. Training Support. League will provide Customer with the training support services as set forth in Appendix 3. Any additional training support services to be provided by League must be agreed to by the Parties and described and set forth in the Underlying Agreement.
b. Updates. League reserves the right to publish, for any reason in its sole discretion, any updates to or new releases or versions of, any of the APIs or SDKs (collectively “Updates”), each of which shall form part of the APIs or SDKs, as applicable, and be subject to these Terms and to the terms of conditions of the Underlying Agreement. League will, at no additional charge, provide Customer with all Updates as they generally become available from time to time. Customer acknowledges that Updates to the SDKs may adversely affect the operation of the Customer Developed Apps and how such applications communicate with an API or with League’s systems and products. Where an Update has an adverse effect on the operation of the Customer Developed Apps (“Breaking Change Update”), it will be Customer’s responsibility, at Customer’s sole cost and expense, to make any and all necessary changes to such Customer Developed Apps that are or may be required as a result of such Breaking Change Update; provided that League will: (i) not release a new Breaking Change Update within three (3) months of the last Breaking Change Update; and (ii) for every Breaking Change Update, provide Customer with an additional six (6) month deprecation period following the release of the Breaking Change Update, during which time League will support both the current Breaking Change Update in general release and the previous Update that was superseded by the Breaking Change Update. Following the expiry of the deprecation period, League’s obligation to support previous versions of the SDKs or APIs will cease and any continued use by Customer of a now deprecated version of the SDKs or APIs will be unsupported and at Customer’s sole risk.
8. Feedback
In the event that Customer provide League any ideas, thoughts, criticisms, suggested improvements or other feedback related to the services, (collectively “Feedback”), Customer agrees League may use the Feedback to modify its products and services and that Customer will not be due any compensation, including any royalty related to the product or service that incorporates Customer Feedback. Customer grants to League a worldwide, royalty-free, fully paid, perpetual, irrevocable license to use, reproduce, modify, translate, distribute, perform, display, import, sell, offer for sale, make, have made and otherwise exploit the Feedback in any form, media, or technology, whether now known or hereafter developed, and to allow others to do the same.
9. DISCLAIMERS AND LIABILITY
FOR CLARITY, THE DISCLAIMERS AND LIABILITY PROVISIONS SET OUT IN THE UNDERLYING AGREEMENT SHALL APPLY TO THE SDKS AND APIS.
10. Indemnification
In addition to the indemnities set out in the Underlying Agreement, Customer agrees to indemnify, defend, and hold harmless League, and its officers, directors, employees, agents, affiliates, successors, and assigns from and against any and all losses, damages, liabilities, deficiencies, claims, actions, judgments, settlements, interest, awards, penalties, fines, costs, or expenses of whatever kind, including reasonable legal fees, arising from or relating to:
a. Use of the APIs or SDKs by Customer or Users of the Customer Developed Apps in violation of these Terms;
b. Customer’s failure to implement security measures to protect its own systems and data when using the APIs and Customer Developed Apps in accordance with Customer’s obligations herein;
c. The development, use, distribution, license, lease, sale, offer or sale, or sublicense of the Customer Developed Apps by or on behalf of Customer including any claims that the Customer Developed Apps, or any portion thereof, infringe any third-party Intellectual Property Rights or claims for any damage to any Person or tangible property that is caused, or alleged to be caused, by the Customer Developed Apps or use thereof
d. the failure by Customer or the Customer Developed Apps to comply with these Terms or any applicable Laws including any and all applicable privacy or other Laws that govern the collection, processing, storage, and use of Personal Information of any User of the Customer Developed Apps.
e. any Claim by a User arising from Customer’s breach of any obligation to a User of the Customer Developed Apps under any User license or other agreement with the User, except to the extent that such claim is directly caused by League’s failure to comply with these Terms.
In the event League seeks indemnification or defense from Customer under this provision, League will promptly notify Customer in writing of the claim(s) brought against League for which League seeks indemnification or defense. League reserves the right, at League option and in League sole discretion, to assume full control of the defense of claims with legal counsel of League choice. Customer may not enter into any third-party agreement that would, in any manner whatsoever, constitute an admission of fault by League or bind League in any manner, without League prior written consent. In the event League assumes control of the defense of such claim, League will not settle any such claim requiring payment from Customer without Customer prior written approval.
11. Cooperation on Issues
To the extent that either Party determines in good faith that there is an issue with the Customer Developed Apps, API or SDK that adversely affects the other Party or their customer’s security or compliance with laws, then such Party shall promptly notify such other Party and the Parties shall work together to: (a) fix the issue, or (b) identify a temporary workaround (if available). If neither of the foregoing are possible, then League may suspend Customer’s access to the affected software until the issue is resolved.
12. Publicity
Customer will not make any statement regarding Customer’s use of an API or SDK which suggests partnership with, sponsorship by, or endorsement by League without League’s prior written approval.
13. League DMCA Policy
League provides information to help copyright holders manage their intellectual property online, but League cannot determine whether something is being used legally or not without their input. League responds to notices of alleged copyright infringement and may terminate accounts of repeat infringers according to the process set out in the U.S. Digital Millennium Copyright Act. If Customer believes someone is violating Customer’s copyrights, Customer may notify League.
14. U.S. Federal Agency Entities
The APIs and SDKs were developed solely at private expense and are commercial computer software and related documentation within the meaning of the applicable U.S. Federal Acquisition Regulation and agency supplements thereto.
15. Application of Applicable Terms and Survival
All applicable terms of the Underlying Agreement shall apply to Customer’s use of the APIs and SDKs, except as otherwise set forth herein. The SDKs and APIs are accessed by various League customers, vendors and partners, as such, any restrictive covenants such as non competition or exclusivity, resource or data center location restrictions or requirements, business continuity and disaster recovery requirements, acceptance testing terms, professional service terms, subcontracting terms, updates or upgrade terms, monitoring, audit or reporting terms, escrow terms set forth in the Underlying Agreement as an League obligation do not apply to the SDKs and APIs. To the extent that there is a conflict between the Underlying Agreement and these Terms as relates to use of the APIs and SDKs, the provision contained in these Terms will control. When these Terms expire or are terminated, those terms that by their nature are intended to continue indefinitely will continue to apply.
IN WITNESS WHEREOF the Parties have executed these Terms as of the Effective Date.
Customer
Per:
Name:
Title:
Signature Date and Effective Date:
League, Inc.
Per:
Name:
Title:
Signature Date and Effective Date:
APPENDIX 1
USE CASES AND PARAMETERS ON USE,LICENSED APIS AND SDKS, AND FEES
[to be provided]
APPENDIX 2
ACCEPTABLE USE POLICY
This AUP is effective as of the Effective Date. All references herein to the “Services” shall mean the APIs and SDKs, as applicable.
1. Prohibited Activities
The Services must not be used to engage in or encourage any activity that is unlawful, deceptive, harmful, a violation or infringement of another person’s rights, or which is harmful to League’s business operations or reputation including any:
- Reverse Engineering. Reverse engineering, copying, disassembling, or decompiling the Services, or in any other manner using the Services for the purpose of designing, building, promoting, or marketing a service that is competitive with the Services.
- Resell or Distribution. Selling, licensing, distributing, or otherwise making available the Services to a third party (such as, but not limited to, timesharing or by operating of a service bureau) either on a standalone basis or embedded as part of a toolkit or library intended primarily for use by software developers and not by end users.
- Inappropriate Content. Transmitting or storing any content or communications (commercial or otherwise) that are illegal, harmful, unwanted, inappropriate, obscene, excessively profane, objectionable, defamatory, tortious, or which infringe upon, misappropriate, or violate the rights (including Intellectual Property Rights) of others, or which target minor children, are confirmed to be criminal misinformation, pose a threat to public health or safety, or propagate or advocate for violence, exploitation, abuse, discrimination against individuals or groups, or hate toward others.
- Commercial Electronic Messages. Transmitting commercial electronic messages in violation of applicable laws, regulations, or governmental orders in any jurisdiction that apply to either end users or the Services that require (a) consent to be obtained prior to processing personal information, transmitting, recording, collecting, or monitoring communications or data, or (b) compliance with requests to opt out of receiving any further communications or data.
- Falsification of Identity or Origin. Creating a false identity or any attempt to mislead others as to the identity of the sender or the origin of any data or communications.
- Unlawful Products. Promoting or advertising any product, service, or other item that violates applicable federal, provincial, state, or local law or regulation.
- High Risk Activities. Develop any product or service intended for use in a high risk environment requiring failsafe performance (such as operation of nuclear facilities, aircraft navigation or aircraft communications systems, mass transit, air traffic control, life support machines, or weapons systems), in which the failure of the product or services could result in death, personal injury, or severe physical or environmental damage.
- Export Control. Export, directly or indirectly, any technical information or any products using such technical information to a location or in a manner that at the time of export requires an export license or other governmental approval, without first obtaining the written consent to do so from the appropriate agency or other governmental entity.
2. Integrity of the Services
Users must at all times maintain and not knowingly or intentionally threaten the integrity of the Services. This includes any conduct aimed at:
- Interference with the Services. Interfering with or otherwise negatively impacting any aspect of the Services or any third-party networks that are linked to the Services.
- Bypassing Service Limitations. Attempting to bypass, exploit, defeat, or disable any limitations or restrictions that have been placed on the Services
- Probing Security Vulnerabilities. Attempting to uncover security vulnerabilities for the purpose of exploiting the Services or attempting to bypass any security mechanism or filtering capabilities
- Disabling the Services. Any denial of service (DoS) attack on the Services or any other conduct that attempts to disrupt, disable, or overload the Services
- Deployment of Harmful Code. Transmitting code, files, scripts, agents, or programs intended to do harm, including viruses or malware, or using automated means, such as bots, to gain access to or use the Services, or that otherwise create a vulnerability in or security risk to the integrity of the Services
- Gaining Unauthorized Access. Attempting to gain unauthorized access to the Services or any part thereof.
APPENDIX 3
API AND SDK TRAINING SUPPORT SERVICES
League will provide Customer with the following support services in relation to the APIs and SDKs made available to Customer hereunder:
1. Training Support
League’s training program will provide Customer and its developers with a comprehensive understanding of the APIs, SDKS, and Related Materials and their use in developing and configuring applications. In addition, Customer will have access to various resources like sample apps, Documentation, and videos, which will aid in expediting the learning process and allow for experimentation with the code.
2. Content
Learning content focuses on APIs, SDKS, and Related Materials; this content provides learners with knowledge on building apps to suit their customer and business needs.
3. Delivery mode
League’s mode of training is instructor-led, live training delivered via Zoom and delivered post training as a recording. Learners will receive direct invites from League for this scheduled training. Access to a knowledgebase containing developer Documentation and sample apps on github will also be provided.
4. Sessions
League shall provide training that consists of 3-4 sessions containing all topics related to building an App using the League APIs and/or SDKs. League’s API and SDK subject matter experts shall also perform ongoing training support of no more than 6 hours per quarter per year at Customer’s request at no additional cost or expense.
5. Updates
Training content and Documentation will be refreshed by League reasonably as and when new releases or updates to APIs, SDKS, and Related Materials become available. This will allow Customer to stay up to date on the latest updates and new staff an opportunity to learn how to build on APIs and SDKs.