> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/store/onside-rules-and-policies-united-states/free-apps-agreement.md).

# Free Apps Agreement

*Last Updated: 4 March 2025*

This Onside Developer Distribution Agreement (the “Agreement”) is a legally binding contract between Onside (the operator of the Onside application marketplace) and you, the Developer. This Agreement governs the distribution of software applications (“Applications”) by Developer through the Onside platform to end users. By clicking “Accept” or by uploading an Application to Onside, you acknowledge that you have read and agree to the terms of this Agreement. If you do not agree you are not permitted to distribute any Applications via Onside or otherwise engage with our platform.

## 1. Definitions

**1.1.** “Onside” refers to the online digital distribution platform and services (including any website, app, or console) provided by Onside.io BV or its affiliates for the distribution of software applications to end users.

Onside.io B.V.\
Keizersgracht 555\
1017 DR Amsterdam\
The Netherlands

Owner Contact Email: <info@onside.io>

**1.2.** “Developer” (or “you”) means the individual or legal entity that has agreed to this Agreement and that provides Applications for distribution via Onside.

**1.3.** “Application” (or “App”) means any software programme, including all included content, media, APIs, data, and services (e.g. digital products, in-app content) that Developer offers to users through Onside under this Agreement. For clarity, “Application” includes any updates, upgrades, new versions, patches, or modifications to that software provided by Developer.

**1.4.** “User” or “user” means any end user who accesses, downloads, or uses an Application through Onside’s platform.

**1.5. Intellectual Property Rights.** “Intellectual Property Rights” means all worldwide rights associated with patent, copyright, trademark, database trade secret, moral and other proprietary rights (whether registered or unregistered) in any jurisdiction.

**1.6.** “Developer Account” means the account issued to Developer by Onside that enables the distribution of Applications via Onside’s platform and access to related services and tools (e.g. developer console).

**1.7.** “Onside Policies” means any rules, guidelines, requirements, technical content or usage standards provided, made available or referred to by Onside regarding the distribution of Applications (including but not limited to content standards, developer programme policies, privacy requirements, and any applicable Onside developer documentation). Onside Policies are incorporated into this Agreement by reference. Onside may update the Onside Policies from time to time, and Developer is responsible for reviewing and complying with the current Onside Policies.

**1.8.** “Confidential Information” means any non-public information disclosed by one party to the other in connection with this Agreement, which is designated as confidential or which by its nature should reasonably be understood to be confidential. Confidential Information may include, without limitation, business plans, technical data, software, APIs, beta features, and other proprietary information. Confidential Information does not include information that is or becomes publicly available without breach of this Agreement, that was lawfully known to the receiving party without confidentiality obligation, or that is independently developed without use of the other party’s Confidential Information.

## 2. License and Intellectual Property Rights

**2.1. Ownership.** Except for the licenses expressly granted in this Agreement, each party retains all right, title, and interest in and to its own intellectual property. Developer retains all Intellectual Property Rights in and to its Applications (including any title, logos, trademarks, and content within the Applications). Onside and its affiliates retain all Intellectual Property Rights in and to the Onside platform, website, services, software, and any Onside trademarks, logos, or brand features. There is no transfer of ownership under this Agreement; instead, Developer grants certain rights to Onside as described below to allow distribution of Applications, and Onside grants certain rights to Developer as needed to use Onside’s platform for the duration of Agreement, after which they automatically expire.

**2.2. License to Onside.** Developer grants to Onside and its affiliated companies a worldwide, non-exclusive, royalty-free, sub-licensable license for the term of this Agreement to host, store, copy, reproduce, modify (for the purposes of format, hosting, security, or technical requirements), publicly display, publicly perform (if applicable), test, distribute, and otherwise use each Application (including any description, metadata, graphics, trademarks, or logos that Developer provides to Onside for the Application) for the purposes of: (a) listing the Application in the Onside marketplace; (b) making the Application available for download and use by Users; (c) performing review, scanning, testing, or analysis of the Application for security, compliance, or technical functionality; and (d) promoting the availability of the Application on Onside (for example, by using screenshots or trailers provided by Developer, or by identifying the Application as an offering on Onside). This license to Onside also permits Onside to make the Application available for re-download by Users who have previously downloaded it (e.g. to enable Users to restore purchases or downloads), and to allow updates or upgrades to be delivered to Users.

**2.3. End User Licensing.** Developer is responsible for providing a license agreement or terms of use for Users of the Application (“End User License Agreement” or “EULA”). Developer may include a custom EULA with its Application, provided that: (a) the EULA is consistent with and does not conflict with this Agreement or the Onside Policies; and (b) the EULA contains at least the minimum terms required by Onside (as described below). If Developer does not provide a custom EULA, or if the provided EULA does not meet the minimum requirements required by Onside, then Developer agrees that Onside’s default end user license terms (the “Standard EULA”) will apply between Developer and each User as the governing license for use of the Application. In either case, Developer acknowledges that the license to the User is granted by Developer (not by Onside), and Developer (or Developer’s licensor) remains the licensor of the Application to the User.

**2.4. Minimum EULA Terms.** Whether using Developer’s own EULA or the Standard EULA, the license granted to Users for the Application must, at a minimum, include terms stating that: (a) the EULA is between Developer and the User (Onside is not a party to the EULA); (b) the license to use the Application is non-exclusive, worldwide (subject to legal restrictions), and perpetual or for the duration of any time period Developer specifies, and allows the User to install and use the Application on any compatible device that they own or control for personal, non-commercial use; (c) the User may not reverse engineer, decompile, or disassemble the Application except to the extent that such activities are expressly permitted by law; (d) the User’s rights to use the Application will terminate if the User fails to comply with the EULA; (e) Developer (and not Onside) is solely responsible for the Application, its maintenance, support, and any warranties or claims relating to it; (f) Onside disclaims all warranties and liabilities on behalf of itself (as further described in Section 8 below) to the User, and the User must acknowledge that Onside has no responsibility for the Application’s content, quality, or performance; and (g) Onside and its affiliates are third-party beneficiaries of the EULA to the extent necessary to enable Onside to enforce the terms of this Agreement and the EULA (such as provisions disclaiming Onside’s liability). Developer shall ensure that each User is notified of or has access to the applicable EULA (either by showing the EULA or by reference to the Standard EULA) before or at the time the User first launches or uses the Application.

**2.5. License to Developer (Onside Tools and Branding).** Onside grants to Developer a limited, non-exclusive, non-transferable, revocable license during the term of this Agreement to use Onside’s software development kits, application programming interfaces (APIs), sandbox environments, and other developer tools or documentation provided by Onside solely for the purpose of developing, testing, and submitting Applications for distribution via Onside. Furthermore, Onside grants Developer a limited license to use Onside’s name, logo, and other Onside brand features (the “Onside Brand Features”) solely to identify the Onside marketplace as a distribution channel for the Application, provided that such use is in accordance with Onside’s branding guidelines and does not mislead or imply any endorsement by Onside. Developer will not modify or remove any proprietary notices (e.g., copyright, trademark symbols) in Onside’s tools or brand assets, and Onside reserves all rights not expressly granted. Upon termination of this Agreement, Developer must immediately cease all use of Onside Brand Features and any Onside confidential or proprietary tools.

**2.6. Reservation of Rights.** All rights not expressly granted in this Agreement are reserved by the respective party. There are no implied licenses under this Agreement. Onside does not obtain any ownership rights in Developer’s Applications, and Developer does not obtain any ownership rights in the Onside platform, services or policies. This Agreement does not create any exclusive relationship—Developer is free to distribute its Applications through other platforms, and Onside may distribute applications from other developers (including applications that may compete with Developer’s Applications).

## 3. Content and Security Requirements

**3.1. Compliance with Policies and Laws.** Developer and all Applications must fully comply with the Onside Policies (including content standards and security requirements) and all applicable laws and regulations in each territory where the Application is distributed or used. It is Developer’s responsibility to understand and adhere to all applicable requirements, which include, without limitation, laws relating to intellectual property, data privacy, data protection, import/export controls, sanctions, consumer protection, online safety, and the protection of minors.

**3.2. Prohibited Content.** Developer shall not include or publish via Onside any Application content that is illegal, harmful, or otherwise violates Onside’s content standards. Prohibited content includes, but is not limited to:

* **Illegal Activities:** Content that promotes or facilitates unlawful acts (e.g. drug use, hacking, violence), or that itself is unlawful to possess or distribute (such as child sexual abuse material or extremist propaganda).
* **Hate Speech and Discrimination:** Content that incites hatred or violence, or promotes discrimination, harassment, or harm against any individual or group based on race, ethnicity, religion, gender, sexual orientation, disability, or other protected characteristics.
* **Defamation and Impersonation:** Content that defames an individual or entity, or falsely purports to be from or endorsed by another person or organisation (no impersonation or fraudulent representation).
* **Malicious or Dangerous Content:** Any viruses, worms, trojan horses, malicious code, or backdoors. Content that exploits vulnerabilities, or secretly intercepts or collects data from a user without consent. Applications must not engage in phishing, distribute malware, or install unwanted software on a user’s device.
* **Privacy Violation:** Content that violates privacy or data protection rights of individuals. Developer must not include spyware or any functionality that records audio, video, or other personal data without clear disclosure and user consent.
* **Intellectual Property Infringement:** Any content (including software, music, text, images, or trademarks) that Developer does not have the lawful right to use or distribute. This includes pirated software, unlicensed media, or any material that infringes or misappropriates the copyrights, patents, trademarks, trade secrets, or other proprietary rights of any third party.
* **Spam and Misleading Content:** Content that is deceptive, misleading, or intended to spam or scam users. Applications should not mislead users about their purpose or content, and should not engage in unauthorised advertising techniques (e.g. adware that serves ads outside of the Application’s context without user knowledge).

Onside reserves the right to define and interpret what constitutes prohibited content or activities under the Onside Policies. Developer is responsible for reviewing the then-current content requirements regularly to ensure compliance.

**3.3. Data Privacy and User Data.** If an Application collects, accesses, uses, transmits, or shares any personal data or sensitive information from Users or their devices, Developer must: (a) comply with all applicable privacy and data protection laws (including but not limited to GDPR, CCPA, and COPPA, as applicable); (b) provide a clear and legally adequate privacy policy that is easily accessible to Users (for example, via the Application’s Onside listing or within the Application) explaining what data is collected and how it is used, shared, and protected; (c) obtain all necessary user consents (informed and express where required by law) before accessing sensitive data or device features such as location, contacts, photos, microphone, camera, or health information; and (d) use and retain user data only for purposes that are reasonably necessary for the Application’s functionality or as permitted by the user and law. Developer shall implement appropriate technical and organisational measures to safeguard any personal data processed through the Application and promptly notify Onside of any security breaches or data incidents involving user data that relate to the Application’s distribution on Onside.

**3.4. Security and Quality.** Developer must ensure that its Applications are safe for Users and do not jeopardise the security or functionality of Users’ devices or the Onside platform. At a minimum, Developer agrees that:

* Applications will be free from malware, vulnerabilities, or defects that could cause harm to a user’s device, data, or the Onside platform. Developer will test Applications for viruses, worms, spyware, and other malicious code before submitting to Onside.
* Applications will not bypass or undermine device security features or operating system protections. For example, Apps must not root/jailbreak a device, install unauthorised certificates or profiles, or download executable code outside of approved methods.
* Applications will only request device permissions or data access that are necessary for their legitimate functionality, and such requests must be transparent to the user. Apps should not abuse permissions (e.g., accessing background location or microphone without justification) and must stop accessing data if the user revokes consent.
* If Developer uses any encryption within the Application, it will comply with all applicable laws (including export/import and regulatory requirements) for cryptography.
* Applications must meet Onside’s technical requirements and quality standards (as specified in documentation or testing guidelines), including acceptable performance (e.g., reasonable loading times, no excessive battery drain or network usage beyond what is disclosed), and stability (not crashing or freezing excessively). Developer will use best efforts to design Applications to be compatible with supported devices and operating system versions as listed in Onside’s documentation.
* Developer will promptly address any security vulnerabilities or critical bugs in its Applications. If Developer becomes aware of a material security issue, privacy flaw, or other critical problem in the Application, Developer must immediately notify Onside and work to provide a patch or updated version to Users as soon as possible. Onside may remove or disable an Application that is found to contain critical vulnerabilities until an adequate fix is provided without notification to Developer.

**3.5. Age Ratings and Content Classification.** Developer is responsible for providing accurate information about the content of each Application to enable proper content ratings or age classifications in accordance with Onside’s requirements and any applicable laws (for example, laws protecting minors from harmful content). Developer shall use any rating tools provided by Onside (or follow Onside’s rating process) to self-classify the Application’s content (such as violence, language, sexual content, etc.) and assign an appropriate age rating. Developer must ensure that the content information is truthful and complete. Onside may edit or override Developer’s rating if it determines the rating is not accurate or appropriate. If an Application is rated for a mature audience or contains content not suitable for minors, Developer must implement any required measures to restrict access by underage users as mandated by applicable law or Onside Policies.

**3.6. Third-Party Components and Services.** If the Application includes any third-party software, libraries, or services (such as open source components, advertiser SDKs, analytics, etc.), Developer is responsible for ensuring all such components are compliant with this Agreement, Onside Policies and applicable law. This includes obtaining any necessary permissions to use and distribute the third-party materials, providing any required notices or attributions within the Application, and complying with any open source license obligations (in a manner that does not conflict with this Agreement or impose any obligations on Onside or Users beyond those of the Application itself). Developer must not incorporate any third-party software or content into the Application that would require Onside or Users to license or disclose their own source code, or that would otherwise impose any additional obligations on Onside or Users (for example, Developer should avoid copyleft licenses that could be interpreted to apply to the Onside platform or the device’s software). If use of any third-party service (e.g., an external API) within the Application could impose obligations or data collection on Users, Developer must clearly inform Users and obtain any necessary permissions.

**3.7. No Interference or Unauthorised Use of Onside.** Developer and its Applications must not interfere with the normal operation of Onside’s platform or any User’s use of Onside. Prohibited behaviours include attempting to manipulate the Onside platform’s search or ranking algorithms (for instance, by fake downloads or reviews), engaging in denial-of-service attacks, exploiting any vulnerabilities in Onside’s systems, or circumventing Onside’s intended processes (such as trying to publish apps without going through review, or using automated tools in an unauthorised manner). Developer will not use the Onside platform or any User data obtained through Onside for any purpose that is not expressly permitted by this Agreement.

## 4. Developer Obligations

**4.1. Account Registration and Information.** To distribute Applications on Onside, Developer must register and maintain an Onside Developer Account. Developer agrees to provide truthful, current, and complete information during registration and to keep all account information (including contact details, business name, address, and billing information if applicable) up to date. Developer must have a valid email address on file with Onside for communication. If any of the provided information becomes outdated or inaccurate, Developer shall promptly update it through the developer account portal or promptly notify Onside as required. Developer is responsible for maintaining the confidentiality and security of its Developer Account credentials and for all activities that occur under its account. If Developer suspects any unauthorised access to its account, it must notify Onside immediately.

**4.2. Responsibility for Content and Support.** Developer is solely responsible for the Applications it distributes via Onside, including their development, operation, and content. Developer is also solely responsible for providing adequate support and maintenance to Users of Applications:

* **User Support:** Developer must provide Users with an accessible means to contact Developer to ask questions, file complaints, or seek support regarding the Application (for example, a support email address, website or phone number). Developer shall respond to user support inquiries and resolve issues in a timely and professional manner. Onside is not responsible for, and will not be obligated to provide, end-user support for any third-party Application. Developer must not direct Users to Onside for Application support issues or any other issues (other than for issues relating to Onside accounts or downloads that are under Onside’s control).
* **Maintenance and Updates:** Developer will maintain its Applications to ensure continued functionality, compatibility, and security. When appropriate, Developer should release updates or bug fixes to address defects, improve performance, or comply with updated requirements from Onside or changes in law. If Onside notifies Developer of any issue in the Application (for example, a security vulnerability, or non-compliance with content requirements), Developer must promptly remedy the issue (such as by issuing an update or removing offending content) and promptly notify Onside of the corrective action taken.
* **Compatibility:** Developer shall use best efforts to keep Applications compatible with the then-current version of the Onside platform and supported operating systems or devices. Onside is not responsible for ensuring compatibility of Developer’s Application with any software or hardware (that responsibility lies with Developer), but Onside will provide, but is not obligated to make, available technical guidelines or requirements to facilitate compatibility. Developer should monitor announcements from Onside regarding any changes that could affect Application functionality (e.g., API deprecations, new OS versions) and timely update the Application if needed.

**4.3. Accurate Listing and Disclosures.** Developer must provide accurate and complete information about each Application in its Onside listing (and any related materials submitted to Onside). This includes the Application’s name, description, screenshots, icons, category, keywords, version notes, and any other metadata. Developer is responsible for ensuring that none of this information is false or misleading. Any special requirements or important characteristics of the Application must be disclosed (for example, if the Application requires additional hardware, a persistent internet connection, login credentials, or if it involves user-generated content or interactions with other users). If the Application contains advertising, in-app purchases, or other monetization (even if the Application itself is free to download), Developer shall clearly inform users in the description and comply with any Onside disclosure requirements (e.g., marking an app as having in-app purchases or ads). Developer will also accurately represent the content and age rating of the Application as required in Section 3.5 above. If any information provided to Onside or Users about the Application changes or is discovered to be inaccurate, Developer must promptly update it.

**4.4. Developer’s Conduct.** Developer agrees to conduct itself in a professional manner in all interactions with Onside and Users. This includes refraining from any fraudulent, unethical, or harmful behaviour in relation to the distribution of Applications. Developer shall not:

* Buy, incentivise, or otherwise manipulate downloads, ratings, or reviews of its Application or any other application on Onside. Reviews and ratings should reflect the honest opinions of real Users.
* Post false or defamatory reviews for competitors’ applications or attempt to unduly influence Onside’s review or ranking systems.
* Engage in activities that violate any anti-corruption or anti-bribery laws. Developer shall not offer any form of bribe, kickback or incentive to Onside employees or contractors in exchange for favourable treatment of any of its Applications.
* Misuse any Onside-provided resources, such as by making excessive or malicious API calls that could impair Onside’s services, or scraping data from Onside in unauthorised or unlawful ways.

**4.5. Legal Compliance (Worldwide).** Developer is responsible for ensuring that the development, content, distribution, and usage of its Applications comply with all applicable laws and regulations in every jurisdiction where the Application is made available and used. This includes:

* **Intellectual Property Laws:** Developer must respect copyrights, patents, trademarks, trade secrets, and other intellectual property rights of others. If the Application uses third-party content (code, libraries, media, etc.), Developer must have the necessary licenses or permissions. Developer will not submit any Application that infringes someone else’s rights or that has been banned or restricted by any applicable court order or government.
* **Export and Sanctions Laws:** Developer must ensure that neither Developer nor any Application is subject to any trade sanctions or export control restrictions. Developer warrants that it is not located in, under control of, or a national or resident of any country or region that is embargoed or restricted by Onside’s country of operation or by international treaties (including but not limited to countries designated by the United Nations, U.S. government, EU or UK as subject to sanctions). Developer also warrants it is not on any restricted parties list (such as the U.S. Treasury Department’s list of Specially Designated Nationals or the U.S. Commerce Department’s Entity List). Developer’s Applications shall not contain or use any cryptographic or other technology in violation of export or import laws. If an Application is subject to specific export classification (e.g., using strong encryption), Developer will promptly provide Onside with all requested information to comply with export requirements.
* **Consumer Protection and Local Regulations:** If a law in a target country requires certain disclosures, warranties, or operational practices for apps (for example, specific language translations, warranty statements, or special handling of user content), Developer will comply with those requirements. Developer will adhere to any legal requirements concerning advertising to consumers, promotions, contests within the Application, or other consumer-facing activities.
* **Open Source and Licensing:** If applicable law requires that the source code of any portion of the Application be made available (for example, due to use of certain open-source licenses), Developer will comply with such obligations independently of Onside. Under no circumstances will Developer’s compliance with open source licenses impose any obligation on Onside to disclose any Onside software or platform source code.

**4.6. Cooperation and Information Sharing.** Developer agrees to cooperate with Onside and any authorised authority in investigating any violation of this Agreement or alleged misconduct related to the Applications. This includes promptly providing information about the Application or its operation upon reasonable request by Onside (for example, explaining how the Application processes data, or providing test accounts to reproduce a user complaint). If a third party (including a User or a government agency) contacts Onside with concerns or legal claims about the Application, Onside may forward the inquiry to Developer or share Developer’s contact information with the third party, so that the concerned party can address the issue directly with Developer. Developer must make a good-faith effort to resolve such disputes or inquiries promptly and responsibly. In the event of an intellectual property dispute or any claim that an Application’s content is unlawful or infringes any rights, Developer is expected to handle the matter with the claimant (including by taking necessary remedial actions such as removing or modifying infringing content) and keep Onside informed of the progress and the resolution.

**4.7. Fees and Payments.** This Agreement covers distribution of free-of-charge Applications. Onside does not charge Users for downloading or using the Application (aside from any data/connection fees outside the scope of Onside). Accordingly, no revenue share or payment is due from Onside to Developer for distribution of free-of charge Applications. If Developer chooses to offer in-app purchases, subscriptions, advertising, or other forms of monetization within a free-of charge Application, Developer must do so in compliance with Onside Policies (which may require using Onside’s in-app purchase system or complying with certain advertising standards). Those monetization activities shall be subject to separate terms (for example, if Onside provides, or seeks to provide, a payment processing service for in-app purchases, the parties will need to agree to separate payment terms and/or schedules). Developer is responsible for all taxes and/or fees associated with its own revenue from the Applications. Onside may, purely at Developer’s direction and as Developer’s agent, facilitate certain transactions (such as collecting payments for in-app purchases on Developer’s behalf if applicable). However, as this Agreement governs free of charge Applications, such scenarios will be governed by an additional addendum between the parties if Developer later seeks to engage in paid distribution or in-app sales (“Sales”). For the avoidance of doubt, Developer agrees not to engage in any Sales on Onside platform before notifying Onside, with a view to negotiating applicable terms for this proposed offering. The parties agree that there is no obligation on the parties to reach an agreement concerning Sales.

## 5. Developer Representations and Warranties

Developer makes the following representations and warranties to Onside, each of which is a continuing obligation throughout the term of this Agreement:

* **(a) Authority and Capacity:** Developer has the full right, power, and authority to enter into this Agreement and to perform its obligations. If Developer is an entity, the person accepting this Agreement has been duly authorised to bind the entity. This Agreement constitutes a legal, valid, and binding obligation of Developer, enforceable against Developer in accordance with its terms.
* **(b) Right to Distribute and License:** Developer owns or controls all necessary rights in the Applications (and all content and components therein) to grant the licenses and permissions to Onside and Users as contemplated by this Agreement. Submission of the Application to Onside and any distribution, download, and/or use of the Application by Users in accordance with this Agreement will not violate any agreement or obligation to which Developer is a party or any rights of any third party.
* **(c) No Infringement:** To the best of Developer’s knowledge, none of the Applications (including their titles, content, icons, and any provided metadata), nor the provision or use of any Application by Onside or Users as permitted hereunder, infringe or misappropriate the Intellectual Property Rights or other rights (such as rights of privacy, publicity, or personality) of any third party. Developer has not received any notice or claim alleging that any Application or its content violates the rights of any person or entity, and there are no current disputes in this regard.
* **(d) Compliance with Law:** Each Application, and Developer’s own actions in connection with this Agreement, comply and will continue to comply with all applicable laws and regulations. Developer warrants that it will not knowingly or negligently introduce into the Application any content or code that violates any law (including export/import laws, data protection laws, obscenity laws, or any other regulations mentioned in Sections 3 and 4 above). If the Application is distributed in multiple jurisdictions, Developer warrants that the Application (and its use) is lawful and permitted in each such jurisdiction. Developer also represents that it will promptly comply with any legal orders or government directives of which it is aware that affect the Application (for example, if a certain content is required by law to be removed or restricted in a country, Developer will do so and inform Onside).
* **(e) No Malicious Code:** Developer’s Applications do not and will not contain any malicious code, viruses, spyware, or other harmful software or components. Developer has used industry-standard methods to test and ensure that the Applications are free of any such harmful code. The Applications do not secretly collect any information or engage in any surveillance of users without proper notice and consent (per Section 3.3). Developer further warrants that the Applications do not contain any hidden “backdoor” or mechanism that would allow Developer or a third party to surreptitiously access or control a user’s device or data without the user’s knowledge.
* **(f) Content Standards:** None of the Applications contains, or will contain, content that is prohibited by Section 3.2 (Prohibited Content). Specifically, Developer warrants that Applications do not contain unlawful content, hateful or obscene material, or any other content that would violate Onside’s content policies. Any content in the Application that might be considered sensitive or objectionable to some audiences has been properly disclosed and age-rated in accordance with Section 3.5. Developer will ensure that any user-generated content in its Application is moderated as necessary to comply with the content standards.
* **(g) Accuracy of Information:** All information that Developer provides to Onside or to Users through the Onside platform is and will remain accurate, truthful, and non-misleading. This includes information in Developer’s account registration, Application listings, metadata, promotional materials, and any communications with Onside or Users. Developer will update any such information that becomes outdated or incorrect. Developer has disclosed any material information regarding the Applications to Onside (especially any that might affect the security or integrity of Onside’s platform or users’ devices).
* **(h) Developer’s Status:** Developer represents that it (including any parent or affiliate with substantial control, and its officers and directors if an entity) is not: (i) located in, under the control of, or a resident of any country or region that is subject to comprehensive economic sanctions or trade restrictions relevant to the Onside platform’s operations; (ii) identified on any government-issued sanctions or watch list (including but not limited to the U.S. Office of Foreign Assets Control’s Specially Designated Nationals List, the U.S. Commerce Department’s Denied Persons List, or similar lists by the EU, UK, or other jurisdictions); and (iii) not engaged in any activities that would violate anti-money laundering or counter-terrorism financing laws, or any applicable law. Developer will immediately notify Onside if its status with respect to the above changes, and understands that any false statement in this regard is, in addition to the other rights available to Onside, grounds for immediate termination of this Agreement, without notice to Developer.
* **(i) No Conflicts of Interest:** Developer represents that distribution of Applications via Onside does not conflict with any obligation Developer has to a third party (for example, if Developer’s employer or another platform has certain ownership or exclusivity rights on software developed by Developer, Developer has obtained all necessary permissions to distribute via Onside). Developer also confirms that to the best of its knowledge, there are no litigation, investigations, or legal proceedings that would adversely affect Developer’s ability to perform under this Agreement or that could subject or expose Onside or its affiliates to liability, potential or otherwise.

Developer acknowledges that Onside is relying on all the above representations and warranties in permitting Developer to use the Onside platform. Developer agrees to immediately notify Onside in writing if any of the above representations or warranties becomes untrue or inaccurate at any time. Onside’s receipt of or failure to act on any such notice shall not waive any of Onside’s rights.

## 6. App Review, Application and Approval

**6.1. Submission of Applications.** Developer must submit each Application (including any new version, update, or patch of an existing Application) to Onside through the designated submission process (e.g., via Onside’s developer console). Developer will provide all materials and information requested by Onside as part of the submission, which typically includes the Application binary or package, icons and images, a written description, category selection, content rating information, required metadata, and any test credentials or instructions needed to review the Application’s features. By submitting an Application, Developer certifies that the Application complies with this Agreement and all Onside Policies. Developer is responsible for testing the Application on appropriate devices or emulators prior to submission to ensure basic functionality and compliance.

**6.2. Onside’s Review Rights.** Developer acknowledges that Onside may conduct a review of each submitted Application (and each update) before making it available to Users. Onside may review the Application for compliance with this Agreement, adherence to Onside Policies, security scanning, and overall quality and functionality. Onside may use manual or automated methods (including static or dynamic analysis, virus scanning tools, or human testers) to evaluate Applications. Developer agrees not to interfere with or circumvent the review process. This includes not attempting to distribute an Application via Onside without going through proper submission, and not including any hidden or dormant functionality in the Application that might bypass review (for example, Developer must not include code that alters the Application’s behaviour after review in ways that would violate requirements).

**6.3. Approval or Rejection.** Onside, in its sole discretion, will determine whether an Application is accepted for distribution on the Onside platform. Onside reserves the right to reject any Application (or any update to an existing Application) that does not meet its standards or requirements. If an Application is rejected, Onside may (but is not obligated to) provide Developer with a summary of the reasons for rejection, referencing any specific policy violations or issues found. Developer may then correct the issues and resubmit the Application for re-evaluation. However, repeated submission of an Application that remains non-compliant may result in permanent rejection or other enforcement actions (including termination of Developer’s account in serious cases). Developer understands and accepts that Onside’s content standards and policies may evolve, and that acceptance of an Application for distribution in once instance does not guarantee that the Application will remain available indefinitely if it later is found non-compliant with updated policies or standards.

**6.4. Conditional Approval; Required Changes.** Onside may approve an Application conditional on certain changes or requirements. For example, Onside might require that Developer make specific disclosures in the app description, change the content rating, modify or remove certain content/features, or integrate required APIs (such as an Onside compatibility library or ad attribution SDK) before the Application can be finally published. Onside will communicate any required changes to Developer, and Developer must implement those changes and resubmit the Application (or otherwise demonstrate compliance) to receive final approval. Failure to implement required modifications can result in rejection or removal of the Application.

**6.5. No Guarantee of Publication Timeline.** Onside strives to review submissions in a timely manner, but makes no guarantees as to any turnaround time for Application review or approval. Developer should not assume an Application will be reviewed, approved or can go live by a specific date. Onside is not liable for any costs, losses, or damages to Developer or any third party due to delays in reviewing or publishing an Application. Developer is encouraged to submit updates or new Applications well in advance of any desired release date to account for the review process.

**6.6. Post-Publication Monitoring.** Onside’s rights of review of any Application extend beyond initial approval. Onside may, at any time, test or scan published Applications (for example, via automated systems or user feedback analysis) to ensure ongoing compliance. If an Application is updated by Developer or if Onside otherwise becomes aware of new information (such as a security issue or user complaints), Onside may re-evaluate the Application. Developer must cooperate with any inquiries during such post-publication reviews.

**6.7. Suspension or Removal After Review or Approval.** Approval of an Application by Onside does not waive any right to enforce this Agreement. If at any time Onside determines that an Application (a) violates any term of this Agreement or the Onside Policies, (b) poses a security or legal risk, (c) has become incompatible or significantly dysfunctional, or (d) may cause harm to Onside’s users or reputation, Onside may take action as described in Section 7 (Removal of Application and Termination), including suspension or removal of the Application without notice to you. Onside may also require Developer to submit future updates for additional review or testing before they are delivered to users, even if minor, if an Application has a history of issues.

**6.8. Confidentiality of Review Process.** Developer agrees that any non-public correspondence or notice from Onside regarding the review and approval process (including rejection rationales, suggestions, or test results) is considered Onside’s Confidential Information. Developer shall not disclose such communications or any specific details about Onside’s review process to the public or any third party. Likewise, Onside acknowledges that prior to an Application’s public release, the Application and its features are Developer’s Confidential Information; Onside will use such information only for review and testing and will not disclose it to unauthorised parties, subject to the terms of Section 11.3 (Confidentiality).

**6.9. No Endorsement or Certification.** Onside’s approval of an Application for distribution is not an endorsement, certification, or warranty by Onside of the Application’s quality or legality. It means only that the Application met Onside’s requirements at the time of review. Developer may not state or imply to users or third parties that the Application is certified or guaranteed by Onside. Developer may indicate that the Application is available on Onside (as permitted by Section 2.5 regarding use of Onside’s name), but should not misrepresent the nature of Onside’s involvement.

## 7. Removal of Applications and Termination

**7.1. Developer Removal or Unpublishing.** Developer may elect to remove (unpublish) an Application from distribution on Onside at any time, by using the provided tools in the Developer Account or by requesting removal through Onside’s support channels. Unpublishing an Application will make it no longer available to new users on Onside. Developer should provide reasonable advance notice to Onside and to existing Users (if feasible) before removing an Application, especially if the Application will become unusable or unsupported after removal. Even after unpublishing, Developer remains responsible for continuing support of existing Users as appropriate (for example, enabling them to use the Application if it does not rely on Onside’s services, or handling requests for data export/deletion if applicable) and for any ongoing obligations under this Agreement. Onside may retain a copy of the Application for archival, legal, or support purposes after removal, but will not redistribute it to new users.

**7.2. Removal or Suspension by Onside.** In addition to the other rights and remedies available to Onside under this Agreement, Onside reserves the right to remove, unpublish, or suspend the availability of any Application from the Onside platform, at any time, with or without prior notice to Developer, in the following circumstances:

* **Policy or Agreement Violation:** If the Application (or Developer) is found to be in violation of this Agreement, the Onside Policies, or any certification Developer made during submission. This includes situations where an Application was initially approved but later is discovered to violate requirements (due to new information, updates, or re-review).
* **Legal Compliance:** If Onside determines or is notified that the Application, or Developer’s distribution of it, may violate any applicable law, regulation, or order. For example, if Onside receives a credible notice of copyright infringement (such as a valid DMCA takedown notice) regarding content in the Application, or if a government authority requests removal due to unlawful content, Onside may remove the Application. Onside will endeavor to promptly notify Developer of such removals and, where legally and practically feasible, provide Developer an opportunity to respond or remedy the issue (for instance, by removing infringing content and re-publishing). However, in cases of legal mandate or urgent risk, Onside may remove first and notify Developer afterward.
* **Security or Privacy Risk:** If the Application is determined to contain a security vulnerability, malware, or to engage in improper handling of user data such that it poses a risk to users or their devices. Onside may remove or disable the Application until the risk is resolved. In some cases, Onside may allow Developer to provide an immediate fix (such as a patched version) rather than remove the Application, but this is at Onside’s discretion. If a severe security issue is detected (for example, the Application is part of a widespread malware incident), Onside may coordinate with device manufacturers or use its platform capabilities to disable or uninstall the Application from users’ devices as necessary to protect users. Developer will cooperate with any such emergency measures.
* **Inactivity or Abandonment:** If Developer’s account is inactive for an extended period or if Developer explicitly abandons the Application (e.g., publicly announces it is no longer maintained) and the Application becomes non-functional or a potential security hazard, Onside may remove the Application after attempting to reach Developer.
* **Risk of Harm to Onside or Others:** If Developer or its Application is, in Onside’s reasonable judgment, causing or could cause reputational, financial, or legal harm to Onside, its users, or partners. For example, if an Application is the subject of numerous serious user complaints, or if Developer is involved in fraudulent or illegal conduct (on or off the platform) that could affect Onside’s business, Onside may take protective action including removal of Developer’s Applications.

Onside will make reasonable efforts to inform Developer of removals or suspensions, via the Developer Account email or console notifications, along with the reason for the action (unless any notice is legally prohibited or if the circumstances require immediate action without time for notice). Where appropriate, Onside may allow Developer to cure the issue and request reinstatement of the Application. However, Onside is not obligated to restore any Application that has been removed, especially if the underlying cause is serious or remains unresolved.

**7.3. Effect on Users; No Liability for Removal.** When an Application is removed (whether by Developer or Onside), users who have already downloaded or installed the Application may generally continue to use it on their devices, but they will no longer receive updates through Onside, and the Application’s listing will indicate it is no longer available. Onside has no obligation to provide alternate download methods or backups to users for removed Applications. Developer should consider providing support or information to existing users after removal, especially if the Application may cease to function (for example, if it relies on servers that will be shut down). Onside is not liable to Developer for any costs or losses resulting from the removal or suspension of an Application in accordance with this Agreement. This includes, without limitation, any lost opportunities, revenues, or damage to Developer’s reputation. Developer agrees that Onside’s decision to remove or not remove an Application, and any communications (or lack thereof) about removal, are within Onside’s sole discretion and that Onside may comply with legal processes and its own policies without incurring liability to Developer.

**7.4. Termination by Developer.** Developer may terminate this Agreement at any time by: (a) removing all of Developer’s Applications from Onside (unpublishing them) and (b) providing written notice to Onside of termination (or using any account termination feature provided in the developer console). If Developer terminates the Agreement, Developer must immediately cease all use of the Onside developer services and tools, and must not attempt to publish new Applications. Termination by Developer will not waive or affect any obligations which by their nature are intended to survive (see for example section 11.7) nor any liability or obligation Developer incurred prior to termination (for example obligations to users). Developer understands that terminating the Agreement or removing Applications will not automatically notify Users, so Developer should take reasonable steps to inform Users if the Applications will no longer be supported or operational.

**7.5. Termination or Suspension by Onside.** In addition to any other rights expressly outlined in this Agreement, Onside may terminate this Agreement (and close Developer’s Account) or suspend Developer’s access to the Onside platform, under the following conditions:

* **For Cause (Immediate):** Onside may terminate immediately upon written notice (which may be via email) to Developer if Developer has materially breached this Agreement or any incorporated Onside Policy, or if Developer has engaged in fraud, willful misconduct, or actions that harm Onside’s interests. Material breaches include, but are not limited to, serious or repeated violations of content or security requirements, egregious infringement or unlawful content in Applications, failure to comply with a critical safety directive from Onside, or any attempt by Developer to circumvent Onside’s systems.
* **Legal Requirement:** Onside may terminate or suspend if it is required to do so by law or by a binding order of a court or competent authority. For example, if distribution of Developer’s Applications becomes unlawful or if Developer is sanctioned by a government.
* **Inactive or Revoked Status:** If Developer ceases to be an authorised developer (e.g., if Developer’s account information is found to be false, or Developer is a company that has been dissolved), or if Developer is barred from using the Onside platform by Onside due to prior violations, Onside may terminate.
* **Platform Changes:** Onside may terminate this Agreement with at least thirty (30) days’ prior notice if Onside decides to discontinue the Onside marketplace or developer programme in its entirety, or to cease distribution of Applications generally. (In such a case, Onside would likely provide broad communication to all developers and, if possible, offer alternative options or transitions for Users.)
* **Without Cause:** In jurisdictions where applicable law allows, Onside may terminate this Agreement without specific cause by providing Developer with at least thirty (30) days’ advance written notice. Onside will typically exercise this right only in extraordinary circumstances (for example, if Onside is restructuring its programme or has concerns about continuing a relationship with Developer for reasons not rising to a breach).

In the event of a suspension (rather than full termination), Onside may disable certain functionality of Developer’s account (such as the ability to publish updates or new apps) while investigating potential breach or awaiting Developer’s action to cure a breach. Onside will notify Developer of any such suspension and what steps need to be taken (if any) to have the suspension lifted. If Developer fails to address the issues or if the investigation confirms a breach, Onside may proceed to termination.

**7.6. Effect of Termination.** Upon termination of this Agreement for any reason:

* All rights and licenses granted by Onside to Developer will cease immediately, and vice versa. Developer must immediately stop using and accessing the Onside developer console, APIs, and any Onside confidential materials. Developer may no longer identify itself as an Onside developer with immediate effect.
* Onside will cease distribution of Developer’s Applications. Onside may, however, retain copies of the Applications and associated materials for purposes of archive, audit, legal compliance, or to support Users who previously downloaded the Applications (for example, enabling re-download for Users if legally required, or retaining review records). Onside will handle any retained data in accordance with its privacy policy and security standards.
* Developer remains responsible for its Applications previously distributed to Users. Termination does not automatically remove the Application from Users’ devices. If continued use of an Application by existing Users could cause harm (e.g., due to a known critical issue), Developer should notify Onside (and Users if possible), and may request Onside’s assistance in issuing a warning or removal of the Application from devices (Onside may cooperate at its sole discretion or if required by law).
* Any payment obligations that arose prior to termination (if any) and Sections of this Agreement that are meant to survive (such as indemnification, confidentiality, liability limitations, etc.) will survive in accordance with Section 11.7.

**7.7. Reinstatement.** After termination, Developer may only re-apply or create a new Developer Account with Onside’s express written permission. If termination was due to Developer’s breach or misconduct, Onside is under no obligation to allow Developer back on the platform. Any attempt to circumvent a termination (for example, by registering a new account under a different name) is a further breach of this Agreement and Onside reserves the right to ban Developer (and associated parties) or take legal action against such conduct.

**7.8. Notice to Users.** In certain cases of removal or termination, Onside may, at its sole discretion, notify Users who have downloaded the affected Application. For example, if an Application is removed for a policy violation or for safety reasons, Onside might send Users an alert that the Application is no longer available or recommend uninstallation. Developer agrees that Onside may take such actions without liability to Developer, and that such communications may reference Developer’s Application and/or Developer as necessary to inform users (e.g., “The app \[App Name] by \[Developer Name] has been removed from Onside because it violated our policies”).

## 8. Limitation of Liability and Disclaimers

**8.1. Onside Platform Provided “As Is.”** Developer acknowledges that Onside (including the marketplace,platform, developer console, APIs, and any services or software provided by Onside under this Agreement) is provided on an “as is” and “as available” basis. To the maximum extent permitted by applicable law, Onside disclaims all warranties, representations, and conditions of any kind, express or implied, with respect to the Onside platform, services, and offerings, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, satisfactory quality, accuracy, title, or non-infringement. Onside does not guarantee that the platform or any tools will be uninterrupted, error-free, secure, or free of harmful components, or that any content (including Applications) will be available on the marketplace. All use of the Onside platform by Developer is at Developer’s own risk. Developer is solely responsible for making backup copies of its Application and any important data; Onside is not responsible for any loss of, or inability to access or use, data.

**8.2. No Warranty on Outcomes.** Onside makes no guarantee of the commercial or technical success of any Application distributed via its platform. Onside does not warrant or ensure that Developer’s Application will be accessed or downloaded by any minimum number of users, or that it will receive any positive ratings or reviews. Onside’s approval of an Application for distribution is not a warranty or certification by Onside that the Application is free of defects or compliant with all laws; Developer remains solely responsible for the Application. Additionally, Onside does not guarantee that it will continue to distribute any Application indefinitely. Onside may, as described in Section 7, remove Applications at any time. Developer accepts the risk that its participation in the Onside marketplace is subject to Onside’s policies and the competitive environment, which may change over time.

**8.3. Limitation of Liability.** To the maximum extent permitted by law, Onside’s total liability to Developer arising out of or in connection with this Agreement or the Onside platform, service or offering shall be limited to the greater of: (a) the total fees (if any) paid by Developer to Onside under this Agreement in the twelve (12) months prior to the event giving rise to liability , or (b) one hundred U.S. dollars (USD $100) (or the equivalent in local currency). In no event will Onside or its affiliates, or their respective officers, directors, employees, or agents, be liable to Developer for any indirect, incidental, consequential, special, punitive, or exemplary damages whatsoever arising out of or related to this Agreement or Developer’s use of the Onside platform, even if Onside has been advised of the possibility of such damages or if the remedy otherwise fails of its essential purpose. This exclusion of damages includes, without limitation: loss of profits, revenues, business opportunities, goodwill or reputation, loss or corruption of data, device damage, or costs of procuring substitute goods or services.

**8.4. Scope of Limitations.** The limitations and exclusions of liability in this Section apply regardless of the theory of liability (e.g. contract, tort, negligence, strict liability, statute, or any other legal theory). Developer acknowledges that Onside could not make the platform available to Developer on an economically feasible basis without these limitations. Nothing in this Agreement is intended to exclude or limit Onside’s liability for matters for which liability cannot be lawfully excluded or limited, such as willful misconduct, gross negligence, or personal injury or death caused by Onside’s negligence, or any statutory liability that cannot be disclaimed. However, to the extent that applicable law allows the limitation or exclusion of liability or damages, those limitations set forth above shall apply.

**8.5. Developer’s Responsibility for Claims and Backups.** Developer acknowledges that it is in the best position to ascertain and mitigate any potential damages it might suffer related to this Agreement. Developer agrees that it will mitigate damages, for example by backing up its software and data, and by obtaining adequate insurance if desired. Developer releases Onside from any and all liability, claims, and demands for damages or losses beyond the limitations set forth in this Agreement. If applicable law does not allow some or all of the above exclusions or limitations to apply to Developer, those exclusions or limitations will apply to the fullest extent permitted by law.

**8.6. No Liability for Developer’s Obligations.** Developer remains solely liable for all claims, damages, and losses arising out of its own breach of this Agreement or violation of law, and nothing herein limits Developer’s liability towards Onside or third parties. Onside’s liability limitations do not limit Developer’s indemnification obligations under Section 9 or other obligations to Onside and Users.

## 9. Indemnification

**9.1. Developer’s Indemnification Obligation.** Developer agrees to defend, indemnify, and hold harmless Onside, its parent company, subsidiaries, and affiliates, and their respective directors, officers, employees, agents, partners, and licensors (each an “Indemnified Party”) from and against any and all claims, suits, actions, proceedings, judgments, losses, damages, liabilities, costs, and expenses (including reasonable attorneys’ fees and legal costs) arising out of or related to:

* **(a) Developer’s Breach:** Any breach or alleged breach by Developer of any term, condition, representation, or warranty of this Agreement or the Onside Policies. This includes, without limitation, any claim that Developer failed to meet its obligations under Sections 3, 4, or 5 (such as claims that Developer misrepresented the Application’s content, or failed to obtain necessary licenses for third-party material).
* **(b) Application Content and Conduct:** The content, operation, distribution, or use of any Application provided by Developer. This covers any claim by a third party or User that the Application (or its use) caused harm or damage, including (i) Intellectual Property Claims – claims that the Application infringes or violates a third party’s patent, copyright, trademark, trade secret, privacy/publicity right, or other proprietary right; (ii) Product Liability and Personal Injury – claims arising from the malfunction, improper design, or unsafe nature of the Application (for example, an Application causing damage to devices or health-related apps causing personal injury due to misinformation); (iii) Privacy and Data – claims that the Application improperly collected, used, or disclosed personal data or violated privacy rights or data protection laws; (iv) Content Issues – claims related to defamation, obscenity, or other content-based harms caused by the Application; and (v) Consumer Protection – claims such as fraud, misrepresentation, or violations of consumer protection statutes by the Application or Developer.
* **(c) Developer’s Violation of Law:** Any actual or alleged violation by Developer (or its employees, contractors, or agents) of any applicable law, regulation, or rights of a third party in connection with Developer’s activities under this Agreement. This includes any fines or penalties imposed by a government or regulatory authority due to Developer’s actions (for example, a regulatory action for a GDPR violation by the Application, or an export control violation).
* **(d) Disputes with Users or Third Parties:** Any dispute between Developer and a User, or Developer and any third party, arising from Developer’s activities on or with Onside, including the Onside platform. For example, if a User alleges that Developer failed to honour a support or warranty obligation, or if a payment processor or advertiser seeks compensation due to Developer’s dealings, Developer will handle this matter and agrees to indemnify Onside for such disputes if they involve a claim against Onside or any Indemnified Party.
* **(e) Taxes and Fees:** Any taxes, duties, and other governmental fees or penalties that Onside may be required to pay (outside of those based on Onside’s net income) that are attributable to Developer’s distribution of Applications or any transactions related to Developer’s Applications. (This is generally not expected for free Applications, but for completeness covers any unforeseen liabilities such as sales tax disputes related to in-app monetization, etc.)

**9.2. Indemnification Procedure.** If an Indemnified Party seeks indemnification under this Section, it agrees to notify Developer in writing of the claim (however, failure to promptly notify will not relieve Developer of its indemnification obligations except to the extent Developer is materially prejudiced by such delay). Developer shall immediately take control of the defence, conduct and investigation of such claim and shall employ counsel of its own choosing to handle and defend the same, at Developer’s cost. The Indemnified Party shall cooperate with Developer (at Developer’s expense) in the defence of such claim. Onside (or other Indemnified Party) reserves the right to participate in the defence of the claim with counsel of its own choosing, at its own expense, if it so wishes; however, Developer will have full control of the defence and shall not be liable for fees and costs of separate counsel engaged by Onside, except if Developer fails to diligently assume or pursue the defence. If Developer does not promptly assume the defence, conduct or investigation of the claim (or fails to notify the Indemnified Party in writing that it will do so within a reasonable time, not exceeding 14 days of notice of the claim), then Onside may assume control of the defence at Developer’s cost, and Developer will be bound by the results obtained by Onside (including any settlement reasonably entered into).

**9.3. Settlement.** Developer may not settle any claim under this Section 9 in a manner that admits liability or fault on the part of any Indemnified Party, or that imposes any obligation or liability on any Indemnified Party (other than purely monetary damages fully covered by Developer), without Onside’s prior written consent. Onside’s consent will not be unreasonably withheld for settlements that fully release all Indemnified Parties and impose no non-monetary obligations on them. If a settlement involves relief other than the payment of money (such as an injunction against Onside, or a change in Onside’s business practices), Onside may withhold consent in its sole discretion. Onside may, at its own expense, assume control of the defence and settlement of any claim at any time if it determines that Developer is not adequately defending the Indemnified Parties’ interests, or if such claim potentially impacts Onside’s rights beyond the scope of this Agreement.

**9.4. Additional Liability for Costs.** In addition to Developer’s duty to indemnify, defend, and hold harmless, Developer agrees to reimburse Onside on demand for all costs and expenses as they are incurred by Onside in enforcing this Section 9 or in the context of any claim for which Developer has indemnified Onside (including reasonable attorneys’ fees and any damages or amounts Onside is required to pay). Onside will provide reasonable documentation for any costs or expenses requested for reimbursement under this clause upon request by Developer.

**9.5. Exceptions.** The indemnification obligations in this Section will not apply to the extent that a claim arises solely from Onside’s: (i) unauthorised modifications of the Application (if any, outside the scope of what Onside is licensed to do under Section 2.2) that were not made at Developer’s request or direction; or (ii) combination of the Application with other materials or services not provided by Developer, where the claim would not have arisen but for such combination. In such cases, Onside will be responsible for its own defence. However, this exception does not apply if the claim arises from combining the Application with Onside’s own platform or software in the normal course of distribution and use (since such combination is contemplated by this Agreement).

**9.6. Independent Obligation.** Developer’s duty to indemnify is independent of its other obligations under this Agreement. The indemnification obligations survive any termination or expiration of this Agreement, and apply even if the claim arises after the Agreement is terminated, so long as it relates to Developer’s activities under this Agreement during the time it was in effect.

## 10. Governing Law and Dispute Resolution

**10.1. Governing Law.** This Agreement and any disputes arising out of or relating to this Agreement or the distribution of Applications on Onside shall be governed by and construed in accordance with the laws of Holland (excluding its conflict of laws principles). The United Nations Convention on Contracts for the International Sale of Goods does not apply to this Agreement.

**10.2. Jurisdiction and Venue.** The parties agree that all disputes arising under or related to this Agreement that are not subject to arbitration (if provided below) shall be subject to the exclusive jurisdiction of the courts of Amsterdam, Holland, and each party consents to the personal jurisdiction of such courts. Each party waives any objection (on grounds of inconvenient forum or otherwise) to the exercise of such jurisdiction. Notwithstanding the foregoing, either party may seek injunctive or equitable relief in any jurisdiction to protect its intellectual property or confidential information.

**10.3. Dispute Resolution Process.** Before initiating any legal action, the parties agree to attempt in good faith to resolve any dispute or claim through informal negotiations. Either party may initiate this process by sending written notice to the other party describing the dispute and proposed resolution. The parties shall discuss the matter and attempt to resolve it within 30 days of receipt of the notice. If the dispute is not resolved within that time, either party may pursue legal remedies as provided by this Agreement.

**10.4. Arbitration (if applicable).** Subject to Section 10.3, in the event of any dispute arising out of or relating to this Agreement, the parties may agree in writing to submit the matter to binding arbitration. If agreed: The arbitration will be administered by the ICC under its, Commercial Arbitration Rules. The number of arbitrators shall be one (1), selected by mutual agreement (or if none, by the administering body). The arbitration proceedings shall be conducted in English. The seat or legal place of arbitration shall be Amsterdam, Holland. The arbitrator shall have authority to award any relief that a court of competent jurisdiction could award, including injunctive relief and attorneys’ fees. Judgment on the arbitration award may be entered in any court having jurisdiction. The parties agree that any arbitration shall be conducted on an individual basis and not on a class, collective, or representative action basis. This Section does not preclude either party from seeking provisional remedies (like a preliminary injunction) in aid of arbitration from a court of appropriate jurisdiction. If the parties do not agree to binding arbitration within 60 days of a party raising a request with the other party, either party may commence proceedings in the courts of Holland.

**10.5. Attorneys’ Fees.** In any legal action or proceeding to enforce rights or remedies under this Agreement (including arbitration), the prevailing party shall be entitled to recover its reasonable attorneys’ fees and costs from the other party, in addition to any other relief that may be granted. However, this provision does not apply to the extent it would conflict with the rules of an arbitration forum or with applicable law in the context of an individual consumer’s (non-developer’s) claims.

**10.6. Time Limitation.** To the extent permitted by law, any claim or cause of action arising out of this Agreement must be brought within two (2) years after the cause of action has accrued, otherwise such claim or cause of action is permanently time-barred. This does not apply to Onside’s claims for unpaid fees or misuse of intellectual property, nor to Developer’s indemnification obligations, which are continuing.

## 11. General Provisions

**11.1. Entire Agreement.** This Agreement (including any documents and policies incorporated by reference, such as the Onside Policies) constitutes the entire agreement between Developer and Onside regarding the subject matter herein and supersedes all prior or contemporaneous agreements, understandings, or communications, whether written or oral, relating to such subject matter. Any additional or different terms proposed by Developer (for example, in any purchase order, communication, or in the Application submission metadata) are hereby rejected and shall be of no effect unless expressly agreed to in writing by an authorised representative of Onside. Developer acknowledges that it has not relied on any representation, warranty, or statement not expressly set out in this Agreement.

**11.2. Amendments.** Onside may modify or update the terms of this Agreement (including the Onside Policies) from time to time. Onside will provide notice to Developer of material changesby posting the updated Agreement in the developer console or by email notification, at least 30 days before the effective date of the change (unless a change is required by law to take effect sooner, in which case Onside will notify Developer as soon as practicable). It is Developer’s responsibility to check for updates and review any modifications. If Developer does not agree to the revised terms, Developer must cease distributing Applications on Onside and may terminate this Agreement in accordance with Section 7.4 before the effective date of the changes. By continuing to access or use the Onside platform or to distribute Applications after the updated Agreement becomes effective, Developer indicates acceptance of the modified terms. Except as set forth in this Section or as otherwise expressly agreed by the parties in writing, this Agreement may not be amended or modified.

**11.3. Confidentiality.** Each party (the “Receiving Party”) may receive Confidential Information of the other party (the “Disclosing Party”) in connection with this Agreement. The Receiving Party agrees that it will: (a) use the Disclosing Party’s Confidential Information solely for the purpose of performing its obligations and exercising its rights under this Agreement; (b) not disclose or permit disclosure of the Confidential Information to any third party without the Disclosing Party’s prior written consent, except to the Receiving Party’s employees, contractors, or advisors who have a need to know it for the Receiving Party to fulfill its obligations or exercise rights under this Agreement and who are bound by confidentiality obligations at least as protective as those herein; and (c) protect the Disclosing Party’s Confidential Information using at least the same degree of care as it uses to protect its own confidential information of a similar nature, and no less than a reasonable standard of care. If the Receiving Party is required by law, regulation, or court order to disclose Confidential Information, it shall give prompt written notice to the Disclosing Party (if legally permitted) to allow the Disclosing Party an opportunity to seek a protective order or other relief. Confidential Information remains the property of the Disclosing Party, and disclosure of Confidential Information does not constitute any express or implied license or ownership transfer of any intellectual property. The confidentiality obligations in this Section 11.3 will survive for 5 years after the termination of this Agreement, except with respect to trade secrets for which the obligations shall survive so long as such information remains a trade secret under applicable law.

**11.4. No Waiver.** No failure or delay by either party in exercising any right or remedy under this Agreement will operate as a waiver of that right or remedy, nor will any single or partial exercise of any right or remedy preclude any further exercise of that right or remedy or the exercise of any other right or remedy. Any waiver of any provision of this Agreement will be effective only if in writing and signed by the party giving the waiver. The rights and remedies of the parties under this Agreement are cumulative and not exclusive of any rights or remedies provided by law.

**11.5. Severability.** If any provision of this Agreement is held to be invalid, illegal, or unenforceable by a court or tribunal of competent jurisdiction, that provision will be enforced to the maximum extent permissible, and the remaining provisions of this Agreement will remain in full force and effect. The parties will, in good faith, negotiate a valid and enforceable substitute provision that most nearly reflects the original intent and economic effect of the invalid provision.

**11.6. Assignment.** Developer may not assign, or otherwise transfer this Agreement (in whole or in part), nor delegate any of its obligations, without Onside’s prior written consent, and any attempt to do so without consent will be null and void. Onside may freely assign or otherwise transfer this Agreement, in whole or in part, including to any affiliate or in connection with a merger, acquisition, corporate reorganisation, or sale of all or substantially all of its assets related to this Agreement, without prior consent from Developer. Subject to the foregoing, this Agreement will bind and inure to the benefit of the parties and their respective successors and permitted assigns.

**11.7. Survival.** Any provisions of this Agreement that by their nature should survive termination or expiration shall survive, including but not limited to: Sections 2.1 (Ownership), 2.2 (License to Onside) to the extent of Onside’s continued use for support purposes, 2.4 (Minimum EULA Terms, particularly Onside’s third-party beneficiary status), 2.5 (post-termination obligations regarding Onside Tools and Brand Features), 4.6 (Cooperation) to the extent of pending matters, 5 (Representations and Warranties) for any claims arising from breaches during the term, 7.6 and 7.7 (Effects of Termination, Reinstatement conditions), 8 (Disclaimers and Limitation of Liability), 9 (Indemnification), 10 (Governing Law and Dispute Resolution), and 11 (General Provisions). All accrued rights and obligations (such as any outstanding liability for breach or indemnification duty) shall also survive.

**11.8. No Agency.** The relationship of Onside and Developer is that of independent contractors. Nothing in this Agreement is intended to or shall create any partnership, joint venture, agency, employment, or fiduciary relationship between the parties. Developer has no authority to make or accept any offers or representations on behalf of Onside or to bind Onside to any contract or obligation. Developer agrees not to represent itself as an agent or representative of Onside or the Onside platform. Note: Distribution of free Applications under this Agreement does not designate Onside as Developer’s agent for any purpose; however, if in a specific jurisdiction or context Onside’s role in distributing free Applications is deemed by law to constitute an agency, Developer appoints Onside as its agent solely for the purpose of delivering the Application to Users, in accordance with the terms of this Agreement. This appointment does not create any duty of loyalty, fiduciary duty, or other legal obligations beyond those expressly set forth herein.

**11.9. Third-Party Beneficiaries.** This Agreement is intended for the sole and exclusive benefit of Onside and Developer and is not intended to benefit any third party, except as expressly provided otherwise. No person or entity not a party to this Agreement shall have any right to enforce any term of this Agreement. Notwithstanding the foregoing, Onside’s affiliates and licensors are intended third-party beneficiaries of the disclaimers of warranties, limitations of liability, and indemnification provisions in this Agreement, and they may enforce rights under those provisions. Additionally, as set forth in Section 2.4, Onside and its affiliates are third-party beneficiaries of the end-user license between Developer and any User to the extent necessary to give full effect to the protections and disclaimers intended by this Agreement.

**11.10. Notices.** Onside may provide notices to Developer under this Agreement by email to the email address associated with Developer’s account, through notifications within the developer console, or via certified mail/overnight courier to the physical address on record (if provided). Developer is responsible for ensuring its contact information is up to date. Notices sent by email or developer console shall be deemed received on the day they are sent (or, if sent after business hours, on the next business day). Notices sent by courier shall be deemed received when delivered, as evidenced by delivery records. Developer shall send any formal legal notices or breach notices to Onside at the address in clause 1.1 (or such other address as Onside advises Developer in writing from time to time), with a copy via email to <info@onside.io> . Notices are effective upon receipt as evidenced by delivery confirmation or acknowledgment of receipt.

**11.11. Language.** This Agreement is drafted in the English language, which shall be the governing language for its interpretation. Any translations of this Agreement are provided for convenience only. In the event of any conflict or discrepancy between the English version and a translated version, the English version shall prevail. All communications and notices to be made or given pursuant to this Agreement must be in the English language (unless otherwise agreed by Onside in writing).

**11.12. Force Majeure.** Onside will not be liable for any failure or delay in performing its obligations (including reviewing or distributing Applications) if such failure or delay is due to circumstances beyond its reasonable control, such as acts of God, war, terrorism, civil unrest, pandemic, governmental action, labour disputes, failure of the internet or utility services, or other events of force majeure. Onside will use reasonable efforts to mitigate the impact of any force majeure event and resume performance as soon as practicable. This provision does not excuse Developer from any obligations (for example, Developer’s obligations to comply with law and not upload malicious content are not excused by force majeure).

**11.13. Interpretation.** Section headings and titles are for convenience only and shall not affect the interpretation of this Agreement. Terms such as “including” or “for example” shall be construed as illustrative and not limiting. Unless the context requires otherwise, words in the singular include the plural and vice versa. References to “days” mean calendar days unless specified as “business days.” If this Agreement is being agreed to electronically, no wet ink signature is required; Developer’s electronic acceptance or commencement of performance constitutes binding acceptance of this Agreement..

**11.14. Counterparts and Electronic Acceptance.** If this Agreement is executed via a click-through or electronic process, it shall be deemed an original executed agreement. If this Agreement is ever printed and signed in counterparts, each counterpart will be deemed an original, and all counterparts together will constitute one and the same instrument.

By agreeing to this Agreement, Developer acknowledges that it has read and understood this Agreement and agrees to be bound by all of its terms.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onside.io/store/onside-rules-and-policies-united-states/free-apps-agreement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
