Developer Program Agreement

Effective: September 18, 2026
Updated: September 18, 2026
Version: 1.1

On this page

Status Notice — Program Launch Pending. The Tanqory App Marketplace and the Developer Program described in this Agreement are scheduled for public launch in a future release. Until Tanqory issues a written launch announcement at https://dev.tanqory.com and on its trust center at https://trust.tanqory.com, the obligations and rights of the parties under this Agreement take effect only upon Tanqory's onboarding of the Developer into the program. This Agreement is published in advance to provide transparency to prospective developers, app-store reviewers, and regulators about the terms that will govern third-party applications once the marketplace is live. Tanqory may revise this Agreement before launch; the version in force at the time of Developer onboarding controls.

Part 1: Definitions and License Grant

Preamble

This Developer Program Agreement (the “Agreement”) is made by Tanqory Inc., a company incorporated under the laws of the State of Delaware, United States. Its primary purpose is to establish a clear and fair business framework, rights and obligations, and legal responsibilities between the company and software/application developers who wish to join Tanqory’s Developer Program and build digital products on the company’s platform.

This Agreement is critical to creating a stable, transparent, and innovation‑friendly digital ecosystem by setting clear rules of engagement. It enables developers to leverage infrastructure, tools, and resources that the company provides to build high‑quality products that meet end‑user needs efficiently. At the same time, it protects the interests of both parties and users, and sets mandatory standards for security, privacy, and service quality.

The scope of this document covers every material aspect of the business relationship between developers and the company: registration processes and IP licensing, technical requirements and product quality standards, personal data handling and security measures, revenue sharing and payments, each party’s rights and duties, legal liability and indemnification, dispute resolution, and termination terms and consequences. Annexes, schedules, and referenced documents form an inseparable part of this Agreement.

The relationship between the developer and Tanqory under this Agreement is that of an independent strategic partnership. The developer is not an employee, agent, partner, or legal representative of the company and has no authority to bind the company. Each party operates independently within the cooperative framework set out here: the developer is responsible for developing and maintaining its own products and serving end users; the company provides technology infrastructure, distribution channels, and support services to facilitate access to markets and users.

This Agreement becomes legally binding immediately once the developer clearly indicates acceptance of all terms (including signing, electronic acceptance, or any legally recognized manifestation of consent) and remains in force until terminated under its terms. Any breach of the terms constitutes a contractual violation that may lead to civil and, depending on the nature of the breach, criminal liability, and may result in claims for damages, service suspension, or termination at the company’s discretion. This Agreement is governed by the laws of the Republic of Singapore and disputes are resolved via SIAC arbitration as described below (with interim injunctive relief available in competent courts). If any translated version of this Agreement conflicts with the English version, the English version controls for interpretation and enforcement.

1. Definitions

In this Agreement, the following terms have the meanings set out below unless the context requires otherwise:

1.1 “Agreement” means this Developer Program Agreement, including all annexes, schedules, and referenced documents that form part of it, and any amendments made later. All such documents are legally binding as if part of the main body. If there is a conflict between the main body and any annex or schedule, the main body prevails unless expressly stated otherwise. “Agreement” also includes policies, guidelines, and other requirements the company issues from time to time relating to the Developer Program, and the developer acknowledges having read and understood all such documents before accepting.

1.2 “Developer” means an individual or legal entity registered for and accepted into Tanqory’s Developer Program that has agreed to comply with all terms of this Agreement, including employees, agents, subcontractors, and others acting on the developer’s behalf. If the developer is a legal entity, the authorized signatory must have legal authority to bind the entity, and the entity is jointly liable. The developer must keep its account in good standing, comply with applicable law, and operate honestly and fairly. If the developer is a minor or lacks legal capacity, consent of a guardian or lawful representative is required.

1.3 “Tanqory” means Tanqory Inc., registered under Delaware law, with registered address at c/o Harvard Business Services, Inc., 16192 Coastal Highway, Lewes, DE 19958, USA, including its affiliates, subsidiaries, parent, joint ventures, related entities, and lawful successors, present or future, domestic or foreign. All such entities may benefit from and enforce this Agreement. “Tanqory” also covers directors, officers, employees, agents, and designees acting on the company’s behalf. The company may assign rights and duties under this Agreement to affiliates or specialized third parties without prior developer consent.

1.4 “Developer Product” means any application, software, service, content, or digital product the developer builds, produces, publishes, or distributes via the Tanqory platform using APIs, SDKs, or other resources provided by Tanqory, including add‑ons, plugins, modules, extensions, templates, themes, and other components designed to interoperate with or enhance Tanqory. It includes updates, bug fixes, new versions, and improvements. Developer Products must meet Tanqory’s technical, quality, security, and policy standards and must not contain illegal content or infringe third‑party rights (e.g., hotel booking apps, multiplayer games, task management software, payment APIs, analytics tools).

1.5 “SDK” means a Software Development Kit provided by Tanqory, comprising libraries, frameworks, classes, functions, interfaces, compile/debug tools, technical documentation, sample code, models, templates, and other resources needed to build Developer Products that work efficiently with the Tanqory platform. SDKs may have multiple versions and support multiple languages/platforms (e.g., iOS, Android, Web, Windows, Linux). Each SDK may have specific license terms the developer must study and comply with. Use of SDKs must be solely for developing, testing, and publishing Developer Products on Tanqory.

1.6 “API” means the application programming interfaces Tanqory provides for integrating Developer Products with the Tanqory platform, including endpoints, request/response formats, authentication credentials, rate limits, and technical documentation.

1.7 “Documentation” means all technical manuals, implementation guides, FAQs, sample code, and other materials Tanqory provides to support use of the SDKs, APIs, and platform.

1.8 “Platform” means Tanqory’s technology environment, including infrastructure, services, dashboards, marketplaces, distribution channels, and related tools that enable deployment, sale, or distribution of Developer Products.

1.9 “User” or “End User” means any individual or entity that uses a Developer Product or interacts with the Tanqory platform through such product.

1.10 “Account” means the registered developer account used to access the SDKs, APIs, dashboards, and related services, including associated authentication credentials and permissions.

1.11 “Credentials” means API keys, tokens, passwords, certificates, or other authentication/authorization data Tanqory issues to the developer to access SDKs, APIs, or platform resources.

1.12 “Intellectual Property” or “IP” means all copyrights, patents, trademarks, service marks, trade secrets, moral rights, database rights, design rights, domain names, and other proprietary rights recognized by law, whether registered or unregistered, including applications, renewals, extensions, and rights to sue for past infringement.

1.13 “Confidential Information” means any non‑public information disclosed by one party to the other relating to business, technology, products, customers, pricing, security, or operations, whether oral, written, or electronic, that is marked or reasonably understood as confidential. Platform metrics, roadmaps, and security details are confidential. Exceptions apply to information that is public through no fault of the recipient, already known without duty of confidentiality, independently developed, or rightfully received from a third party without duty of confidentiality.

1.14 “Personal Data” means any information relating to an identified or identifiable natural person, including data defined under applicable privacy laws such as PDPA (Singapore), GDPR, CCPA, or other equivalent laws, including names, contact details, IDs, online identifiers, device data, and any data that can directly or indirectly identify a person.

1.15 “Processing” means any operation performed on data, such as collection, recording, organization, storage, adaptation, retrieval, use, disclosure, transmission, alignment, combination, restriction, erasure, or destruction.

1.16 “Data Controller” means the party that determines purposes and means of processing Personal Data.

1.17 “Data Processor” means the party that processes Personal Data on behalf of the Data Controller.

1.18 “Security Incident” means any actual or reasonably suspected unauthorized access, use, disclosure, alteration, or destruction of data; compromise of credentials; or event that impacts the confidentiality, integrity, or availability of systems or data relating to the Developer Product or the Tanqory platform.

1.19 “Open Source Software” (OSS) means software distributed under an open source license, including copyleft or permissive licenses, such as GPL, LGPL, AGPL, MIT, BSD, Apache, and similar.

1.20 “Third‑Party Service” means any product, service, content, or component provided by a third party that the Developer Product uses or integrates (e.g., payment gateways, analytics tools, cloud services).

1.21 **“Store” or **“Marketplace”** means Tanqory’s marketplace or distribution channel through which Developer Products may be offered, listed, or sold.

1.22 “Listing” means the presentation of a Developer Product in the Store/Marketplace, including descriptions, pricing, images, disclosures, and any associated claims.

1.23 “Revenue Share” means the allocation of revenue between Tanqory and the developer according to the applicable schedule or Order Form.

1.24 “Order Form” means any mutually agreed document or online form specifying plan type, commercial terms, feature scope, pricing, credits, SLAs, and any special conditions for the Developer Product on the platform.

1.25 “Service Credits” means credits Tanqory may grant in accordance with an SLA for failure to meet uptime or service levels, subject to the applicable terms and caps.

1.26 **“Service Level Agreement” or **“SLA”** means the service level commitments (e.g., uptime) Tanqory provides for applicable services or APIs, including measurement, exclusions, remedies, and credit processes.

1.27 “Support” means technical or customer support provided by Tanqory to the developer, or by the developer to end users, as defined in this Agreement or an Order Form.

1.28 “Maintenance” means updates, patches, bug fixes, or changes made to SDKs, APIs, or the platform, or to Developer Products, to ensure proper and secure operation.

1.29 “Brand Assets” means Tanqory’s trade names, trademarks, service marks, logos, domain names, and other brand elements.

1.30 “Attribution” means crediting or referencing Tanqory (or third‑party IP owners) as required by this Agreement or specific SDK/API terms, including placement and prominence rules.

1.31 “Export Control Laws” means all export control and sanctions laws applicable to the parties, including those of Singapore, the United States (e.g., EAR, OFAC sanctions), the EU, UN, and other relevant jurisdictions.

1.32 “Sanctioned Person” / “Sanctioned Country” means any person or country/territory subject to trade or economic sanctions or other restricted party lists under applicable law.

1.33 “Feedback” means any suggestion, idea, proposal, or recommendation provided by the developer to Tanqory regarding SDKs, APIs, the platform, or other services.

1.34 “Testing Environment” means a non‑production environment provided by Tanqory for development or testing of Developer Products, subject to limitations on data and usage.

1.35 “Production Environment” means the live environment for real end‑user interactions and transactions.

1.36 “Data Minimization” means collecting, using, and retaining only the personal data necessary for specified purposes, consistent with privacy laws such as GDPR and PDPA.

1.37 “Data Subject Rights” means rights granted to individuals under privacy laws (e.g., access, correction, deletion, objection, restriction, portability).

1.38 “Incident Response” means the processes and measures for detecting, responding to, containing, and remediating Security Incidents, including notification obligations.

1.39 “Business Continuity and Disaster Recovery” (BC/DR) means policies and procedures to ensure continued operations and recovery from disruptions.

1.40 “Data Localization” means legal or contractual requirements to store or process data in specific geographic locations.

1.41 “Encryption” means cryptographic processes and algorithms that transform plaintext into ciphertext unreadable without the correct key, to protect confidentiality, integrity, and authenticity. It includes symmetric (e.g., AES‑256, ChaCha20) and asymmetric (e.g., RSA, ECC) methods. Developers must use industry‑standard encryption (e.g., NIST FIPS 140‑2/3, ISO/IEC 27001) for personal data at rest and in transit (e.g., TLS 1.3 or higher), manage keys securely (rotation, storage, destruction), and avoid obsolete algorithms (e.g., DES, MD5, SHA‑1).

1.42 “Data Security” means measures, processes, policies, technologies, and practices to protect data from cyber threats, including unauthorized access, misuse, disclosure, destruction, loss, alteration, theft, or service disruption. It encompasses confidentiality, integrity, and availability (CIA triad), including access control (least privilege/need‑to‑know), MFA, encryption, backup, monitoring/auditing, intrusion detection/prevention, vulnerability management, and training. Developers must follow standards such as ISO/IEC 27001, ISO/IEC 27701, NIST CSF, SOC 2 Type II, and applicable laws (e.g., PDPA Section 24, GDPR Article 32).

1.43 “Security Vulnerability” means any weakness, flaw, or error in design, development, configuration, or operation of information systems, software, hardware, networks, or security processes that could be exploited to violate security policies, gain unauthorized access, damage integrity, harm systems, or disrupt services. Examples include buffer overflow, SQL injection, XSS, CSRF, RCE, default credentials, misconfigurations, weak authentication, social engineering. Severity follows CVSS v3.1 (Critical, High, Medium, Low). Developers must track CVE/NVD and OWASP Top 10, and identify, assess, remediate, and report vulnerabilities promptly (e.g., Critical within 24–72 hours; High within 7–30 days).

1.44 “Security Testing” means systematic technical processes to assess and test security of Developer Products, software, applications, infrastructure, and processes to find vulnerabilities and risks before production release. Methods include SAST, DAST, IAST, penetration testing/ethical hacking, code reviews, configuration reviews, API/mobile security testing, and fuzzing. Security testing should be part of the secure SDLC/DevSecOps and performed regularly (pre‑release, post‑update, periodic), with reports and remediation plans per standards (OWASP Testing Guide, NIST SP 800‑115, ISO/IEC 27034, OWASP ASVS).

1.45 “Legal/Regulatory Compliance” means processes, measures, policies, and business/technical actions the developer must implement to comply with all applicable laws, regulations, rules, orders, notifications, industry standards, best practices, codes of ethics, and contractual requirements. This includes privacy/data protection laws (e.g., PDPA, GDPR, Singapore PDPA, CCPA), IP laws (copyright, patent), electronic transactions and computer crime laws, consumer protection, tax, AML/CTF, and sector‑specific rules (e.g., HIPAA, PCI DSS). Developers must maintain a compliance program (risk assessments, training, internal audits, reporting, continuous improvement) consistent with standards such as ISO 37301.

1.46 “Audit” means any review, inspection, or assessment (internal or external) of the developer’s compliance with this Agreement, security requirements, or applicable law, including evidence requests and remediation.

1.47 “Penetration Test” means controlled testing simulating attacks to identify exploitable vulnerabilities in systems, applications, or infrastructure.

1.48 “Business Records” means all records required to evidence compliance, transactions, consents, notices, logs, price displays, or other operational actions under this Agreement.

1.49 “Notice” means any formal communication required under this Agreement (e.g., breach notice, termination notice), delivered per the communication clauses.

1.50 “Consent” means freely given, specific, informed, and unambiguous indication of a data subject’s wishes, expressed by a statement or clear affirmative action, as required by applicable law.

1.51 “Controller-to-Processor Terms” means the data protection clauses governing processing of Personal Data by the developer or Tanqory, including any Data Processing Addendum (DPA).

1.52 “Subprocessor” means any third party engaged by the developer (or by Tanqory, where applicable) to process Personal Data on behalf of the controller.

1.53 “Indemnity” / “Indemnification” means the obligation of one party to compensate, defend, and hold harmless the other party (and its affiliates, officers, directors, employees, and agents) from losses, damages, costs, fees, legal expenses, or liabilities arising from actions, omissions, breaches, or third‑party claims (e.g., user lawsuits, government claims, IP infringement, privacy violations), subject to notice, control of defense, and cooperation requirements.

1.54 “Losses” means all damages, costs, expenses, fines, penalties, settlements, and reasonable attorneys’ fees arising out of or relating to claims covered by an indemnity or breach.

1.55 “Limitation of Liability” means caps, exclusions, or ceilings on legal liability and damages under this Agreement, whether for breach of contract, tort, negligence, or otherwise, including monetary caps, exclusions of indirect/special/consequential damages, and exceptions (e.g., IP infringement, confidentiality breach, indemnity, willful misconduct/gross negligence, non‑excludable legal liabilities). Caps must be reasonable under laws such as the Singapore Unfair Contract Terms Act (UCTA).

1.56 “Force Majeure” means events beyond a party’s reasonable control that prevent performance of contractual obligations.

1.57 “Dispute” means any conflict, controversy, or claim arising between the parties relating to this Agreement or its performance.

1.58 “Mediation” means a voluntary dispute resolution process facilitated by a neutral third party to help parties reach agreement.

1.59 “Arbitration” means dispute resolution through appointed arbitrator(s) empowered to issue binding awards.

1.60 “Jurisdiction” means the court system having authority to adjudicate disputes arising out of or relating to this Agreement.

1.61 “Governing Law” means the law of the country or jurisdiction designated to interpret and enforce this Agreement.

1.62 “Annex” means any additional document attached to this Agreement that forms part of it, including fee schedules, technical requirements, and policies.

1.63 “Amendment” means any change, modification, or addition to the text or conditions of this Agreement after its effective date.

1.64 “Waiver” means an explicit relinquishment or non‑exercise of a right under this Agreement.

1.65 “Assignment” means a transfer of rights, duties, or obligations under this Agreement to another person or entity.

1.66 “Third Party” means any natural or legal person who is not a party to this Agreement.

1.67 “Subcontractor” means any person or entity engaged by the developer to perform any portion of obligations under this Agreement.

1.68 “Warranty” means a representation or promise by one party to the other regarding facts, quality, or condition of something.

1.69 “Disclaimer of Warranties” means a statement that a party does not provide certain warranties, express or implied.

1.70 “Business Day” means Monday through Friday, excluding public holidays and days declared by the Singapore government.

1.71 “User‑Generated Content” means any data, content, or media created, uploaded, or shared by end users through a Developer Product.

1.72 “Content Moderation” means processes to review and control content appearing in Developer Products to comply with policies and law.

1.73 “Prohibited Content” means content that is illegal, harmful, inappropriate, or contrary to Tanqory policies and is not allowed in Developer Products.

1.74 “Community Standards” means the guidelines and rules defining acceptable and unacceptable behavior for users and developers on the Tanqory platform.

1.75 “Customer Service” means support and assistance the developer provides to end users of the Developer Product.

2. License Grant

2.1 Rights Tanqory Grants to the Developer

2.1.1 Subject to this Agreement, Tanqory grants the developer a limited, non‑exclusive, non‑transferable, non‑sublicensable, revocable license to access and use the SDKs, APIs, development tools, and technical documentation solely to develop, test, and publish Developer Products on the Tanqory platform.

2.1.2 SDK rights: (a) The developer may download, install, and use the SDK in its development environment to build and test Developer Products.
(b) The developer may integrate the SDK into Developer Products according to Tanqory’s technical requirements.
(c) The developer is entitled to updates and new versions of the SDK released by Tanqory at no additional charge.
(d) SDK use must comply with any SDK‑specific license terms issued separately.

2.1.3 API rights: (a) The developer may access and call Tanqory APIs so Developer Products can interact with the Tanqory platform.
(b) The developer must use Tanqory‑issued authentication credentials to access APIs and must keep them confidential.
(c) Tanqory may impose API usage limits (e.g., request rates, data volumes, accessible functions).
(d) The developer must follow Tanqory’s API usage guidelines and technical requirements.

2.1.4 Access to documentation and support resources: (a) The developer may access user guides, technical references, sample code, and training materials provided by Tanqory.
(b) Tanqory may provide technical support channels as described in the Documentation or applicable Order Form.

2.2 License Restrictions

2.2.1 The developer agrees not to:
(a) reverse engineer, disassemble, or decompile the SDKs, APIs, or Tanqory technology except as expressly permitted by law;
(b) modify, adapt, or create derivative works of the SDKs or APIs without Tanqory’s prior written consent;
(c) remove, obscure, or alter any copyright, trademark, or proprietary notices in SDKs, APIs, or documentation;
(d) use SDKs or APIs to develop products or services that directly compete with Tanqory or mimic Tanqory’s core platform features.

2.2.2 Sublicensing and transfer limits:
(a) The developer may not sublicense, lease, lend, sell, or transfer SDK/API usage rights or tools obtained from Tanqory to any third party.
(b) The developer may not share authentication credentials or allow others to access the developer account without Tanqory approval.
(c) SDK and API use must occur only through the registered developer account.

2.2.3 Commercial use limits:
(a) The developer must obtain Tanqory approval before using SDKs/APIs in commercial or paid products/services.
(b) Usage beyond permitted scope or the developer’s plan may incur additional fees at Tanqory’s rates.
(c) The developer must comply with payment and billing terms in this Agreement.

2.2.4 Technical and usage limits:
(a) The developer must comply with API rate limits, usage quotas, and other technical requirements set by Tanqory.
(b) The developer must not use SDKs/APIs in ways that damage the platform, disrupt service, or impact other users.
(c) Abnormal, improper, or restriction‑violating usage may result in suspension or limitation of access.

2.2.5 Security and data protection limits:
(a) The developer must not attempt to access or use any Tanqory system areas not expressly authorized.
(b) The developer must not take actions that could harm the security, integrity, or availability of the platform.
(c) The developer must promptly report any security vulnerabilities or issues discovered to Tanqory.

2.2.6 Content and use limits:
(a) The developer must not develop or publish products containing prohibited, illegal, or rights‑infringing content.
(b) Developer Products must not be used for illegal, deceptive, or harmful activities.
(c) The developer must comply with Tanqory community standards and content policies.

2.3 Tanqory’s Reservation of Rights

2.3.1 Tanqory reserves all rights not expressly granted to the developer. The licenses to use SDKs, APIs, and resources do not transfer ownership or IP rights to the developer.

2.3.2 Tanqory reserves the right to:
(a) modify, improve, update, or discontinue SDKs, APIs, or platform features with or without notice;
(b) add, modify, or change technical requirements, usage limits, or policies related to SDK/API use;
(c) review, approve, or reject Developer Products before or after publication under Tanqory’s review process;
(d) suspend, limit, or revoke developer access to SDKs, APIs, or the platform if this Agreement or Tanqory policies are violated.

2.3.3 Tanqory may collect and use anonymized and aggregated data from use of SDKs, APIs, and Developer Products to improve services, analyze trends, and develop new products, in compliance with applicable data protection laws.

2.3.4 Tanqory may prioritize support, resource allocation, and access to new features based on membership level, usage history, or other factors it deems appropriate.

2.3.5 Tanqory reserves the right to enforce its IP and take legal action against infringement, including unauthorized use of Tanqory trademarks, copyrights, patents, or other IP.

3. Developer Requirements and Obligations

3.1 General Obligations

3.1.1 Compliance with this Agreement and policies:
(a) The developer will comply with all terms of this Agreement, including annexes, policies, and guidelines Tanqory issues and updates from time to time.
(b) The developer must monitor and stay current on changes to Tanqory policies, requirements, and practices.
(c) If the developer disagrees with any change, it may terminate per this Agreement’s procedures.

3.1.2 Quality standards:
(a) Developer Products must be high‑quality, correct, stable, and deliver a good user experience.
(b) The developer must thoroughly test products before release and after each update.
(c) The developer must promptly fix bugs, issues, and security weaknesses.
(d) Developer Products must meet Tanqory’s technical specs, design standards, and UX guidelines.

3.1.3 Responsibility to end users:
(a) Provide clear, accurate, complete information about the product (features, functions, limits, conditions).
(b) Provide adequate customer service to answer questions, resolve issues, and support end users.
(c) Provide clear contact channels and respond effectively to complaints/feedback.
(d) Respect end‑user rights and act fairly and transparently.

3.1.4 Legal and regulatory compliance:
(a) Comply with all laws, regulations, and rules applicable to development, publication, and operation of Developer Products.
(b) Obtain and maintain required licenses, approvals, and registrations.
(c) Comply with data protection, consumer protection, IP, and other applicable laws.
(d) Be solely responsible for tax and financial obligations related to product revenue.

3.1.5 Security and data protection:
(a) Implement appropriate security measures to protect products, user data, and systems from threats and unauthorized access.
(b) Encrypt sensitive personal data at rest and in transit.
(c) Notify Tanqory and affected users immediately upon a data breach or security incident.
(d) Regularly review and update security measures in line with industry best practices.

3.1.6 Data accuracy and integrity:
(a) Provide accurate, current, complete information in the developer account and product data.
(b) Notify Tanqory of material changes (contact, financial, business status).
(c) Do not provide false, misleading, or deceptive information to Tanqory or end users.

3.2 Security and Confidentiality

3.2.1 Protection of Confidential Information: the developer will (i) treat SDKs, developer services, technical documents, and any information received under this Agreement as Tanqory confidential trade secrets; (ii) not disclose to anyone except authorized personnel on a need‑to‑know basis under confidentiality terms no less protective than these; (iii) use safeguards at least as protective as for its own confidential information and not less than reasonable care; (iv) use confidential information only to perform this Agreement; and (v) promptly notify Tanqory of any unauthorized disclosure or security incident affecting confidential information.

3.2.2 Exceptions: confidentiality obligations do not apply to information that (a) is public without the developer’s fault; (b) was lawfully known to the developer without duty of confidence, evidenced in writing; (c) is received lawfully from a third party without duty of confidence, evidenced in writing; (d) is independently developed without use/reference to Tanqory confidential information, evidenced in writing; or (e) must be disclosed by law/court/government order, with prior notice to Tanqory where permitted and limited to what is required.

3.2.3 Return or destruction: upon termination or Tanqory’s request, the developer will either return all confidential information (and copies) or destroy it irreversibly and certify destruction, except for copies retained as required by law/regulation, which remain subject to confidentiality.

3.2.4 Technical security: the developer must maintain appropriate technical/organizational security, including (i) encrypting key data and personal data at rest and in transit using strong industry algorithms (e.g., AES‑256; TLS 1.2+); (ii) access controls per least‑privilege/need‑to‑know; (iii) MFA for sensitive systems; (iv) comprehensive audit/access logs; (v) timely OS/software patching; (vi) anti‑virus/IDS and appropriate security controls; (vii) regular backups and tested restores; and (viii) an incident response plan.

3.3 Personal Data Protection

3.3.1 Lawful basis and compliance: the developer must collect, use, disclose, and process personal data lawfully, with proper notice and consent (where required), in line with applicable privacy laws (e.g., PDPA, GDPR, CCPA). The developer must implement privacy by design/default, data minimization, purpose limitation, retention limits, and honor data subject rights.

3.3.2 Controller/processor roles: where the developer is a controller, it bears full legal responsibility for lawful processing; where acting as a processor for Tanqory or others, it must follow controller instructions, execute a DPA/Standard Contractual Clauses as required, and support data subject requests.

3.3.3 Cross‑border transfers: comply with transfer mechanisms (e.g., SCCs, approved transfer tools, adequacy, or local derogations) and document transfer impact assessments where needed.

3.3.4 Security incidents: maintain procedures to detect, assess, contain, and notify of personal data breaches. Notify Tanqory without undue delay of any breach affecting Tanqory or platform users, and cooperate on remediation and notifications required by law.

3.3.5 Privacy notices and user rights: provide clear privacy notices covering purposes, lawful bases, categories of data, sharing, retention, rights, and contacts. Enable users to exercise access, correction, deletion, objection, restriction, and portability rights within statutory timelines.

3.3.6 Data retention and deletion: retain personal data only as necessary for stated purposes or legal requirements; delete or anonymize upon expiry of purpose/retention, account closure, or valid user request, subject to legal holds.

3.3.7 Subprocessors: engage subprocessors only with appropriate contracts, confidentiality, security, and privacy safeguards; maintain and provide a current list upon request; remain liable for subprocessors’ acts/omissions.

3.3.8 DPIA/records: conduct Data Protection Impact Assessments where required; maintain Records of Processing Activities (RoPA) and make them available to regulators/Tanqory upon lawful request.

3.4 Intellectual Property

3.4.1 Ownership of Developer IP: the developer retains ownership of its pre‑existing IP and IP in Developer Products, subject to the licenses granted herein.

3.4.2 Third‑party/OSS compliance: the developer must ensure it has necessary rights to third‑party components and comply with all license terms, including attribution, source disclosure (if applicable), and use conditions. Avoid using strong copyleft OSS (e.g., GPL, AGPL) in ways that would require Tanqory or Developer Products to open source unless Tanqory gives prior written consent. Maintain a Software Bill of Materials (SBOM) listing OSS name, version, license, source URL, usage (static/dynamic), modifications, and provide/refresh upon request. Do not use OSS with known vulnerabilities without appropriate patch/mitigation; check NVD/CVE/GitHub advisories. Ensure license compatibility among OSS components.

3.4.3 Attributions/markings: include required OSS attribution and copyright notices clearly in the product and related materials.

3.4.4 License to Tanqory: by publishing a Developer Product via the App Marketplace or Tanqory Platform, the developer grants Tanqory a non‑exclusive, worldwide, royalty‑free, sublicensable, transferable, perpetual and irrevocable (subject to 3.4.4(b)) license to:
(a) publish, list, advertise, promote, and distribute the Developer Product via the App Marketplace and Tanqory channels;
(b) allow end users to download, install, access, and use the Developer Product under the developer’s terms;
(c) make backup, host, cache, and distribute the Developer Product on Tanqory or provider infrastructure;
(d) test, review, analyze, and certify quality, security, compatibility, and performance;
(e) use the developer’s name, logo, trademarks, screenshots, demos, descriptions, and marketing materials as needed for promotion (including featured listings/case studies);
(f) provide technical support and customer service to end users;
(g) modify/adapt/convert the Developer Product as needed to interoperate with Tanqory or user systems, optimize for devices/OS/environments, fix urgent bugs/security issues if the developer cannot do so timely, or comply with law.

This license: (a) remains in force while the Developer Product is listed and for 180 days after removal to allow authorized end users to continue lawful use; and (b) survives termination as needed for authorized end users’ continued lawful use.

3.4.5 License to end users: the developer will provide an EULA that is accessible, clear, and not conflicting with this Agreement or Tanqory’s terms; defines scope, limits, prohibitions; complies with consumer laws; does not unlawfully exclude/limit liability; and includes privacy/data rights terms. If no EULA is provided, Tanqory’s standard EULA applies.

3.4.6 Respect for Tanqory IP: Tanqory owns all rights, title, and interest in the platform, developer software/services, documented APIs, technical docs, “Tanqory”/“Tanq” marks and logos, domains, and other IP. No IP is transferred except limited licenses herein. The developer will not (i) contest or assist contesting Tanqory IP validity/enforceability; (ii) register or attempt to register confusingly similar marks/names/domains; or (iii) use Tanqory marks outside the express permissions or guidelines.

3.4.7 Use of Tanqory trademarks: permitted only to indicate compatibility or distribution (e.g., “for Tanqory,” “works with Tanqory”), subject to Tanqory Trademark Usage Guidelines. Marks must appear in prescribed form without alteration; must not imply Tanqory makes, certifies, endorses, or approves the product unless true; must not be used in the developer’s company/product/domain names; must include appropriate disclaimers (e.g., “Tanqory is a trademark of Tanqory Inc. This product is developed by [Developer] and is not an official Tanqory product”). Tanqory may revoke permission at any time.

3.4.8 Patent provisions:

The developer represents and warrants that (a) the Developer Product does not infringe any valid and enforceable third‑party patent in any jurisdiction; (b) if the developer owns patents covering the Developer Product, it grants Tanqory and end users a non‑exclusive, worldwide, royalty‑free, irrevocable patent license to use, run, offer for sale, and sell such product; and (c) the developer will not sue, threaten, or seek damages from Tanqory, end users, or any third party for patent infringement arising from authorized use of the Developer Product.

If a third party alleges patent infringement by the Developer Product, the developer must: (a) notify Tanqory immediately; (b) be solely responsible for defense, settlement, or resolution; and (c) indemnify Tanqory under Section 11 (Indemnification).

4. Developer Product Requirements

4.1 Quality and Performance Standards

4.1.1 Technical requirements:

Developer Products must:

Function as described in documentation, product descriptions, and marketing materials without critical bugs or errors affecting core use.
Interoperate smoothly and efficiently with the Tanqory Platform, using only Documented APIs and Tanqory best practices.
Perform efficiently without excessive use of system resources (CPU, memory, disk I/O, network) that degrade the platform or other products.
Provide reasonable response times, avoiding unnecessary delays or freezes.
Handle errors properly with exception handling, user‑friendly error messages, and error logging for diagnosis.
Be fully tested (unit, integration, UAT) before release or updates.

4.1.2 Security requirements:

Developer Products must:

Be free of malware, viruses, trojans, spyware, ransomware, and other harmful software.
Avoid known or avoidable security vulnerabilities (e.g., SQL injection, XSS, CSRF, remote code execution, privilege escalation, auth bypass, OWASP Top 10).
Use industry‑standard encryption/security for sensitive data (passwords, card data, personal data) at rest and in transit.
Validate and sanitize user input to prevent injection attacks.
Use appropriate authentication and access controls to prevent unauthorized access/actions.
Patch discovered vulnerabilities promptly; high/critical issues must be fixed within 7 days of discovery or public disclosure.

4.1.3 Design and user experience:

Developer Products should:

Provide an intuitive, easy‑to‑use UI consistent with good usability principles.
Align where feasible with Tanqory Platform look and feel.
Support responsive design across devices/screen sizes (for web/UI products).
Meet accessibility standards (e.g., WCAG) for users with disabilities.
Provide clear feedback on action status, progress, and results.
Include adequate user docs or in‑app help that is easy to understand.

4.2 Content and Behavior Requirements

4.2.1 Prohibited content:

Developer Products must not contain or promote content that is illegal; defamatory; infringing; threatening; harassing; harmful; obscene; hateful; violates IP, privacy, publicity, or other rights; depicts/promotes violence, torture, self‑harm (especially involving minors/animals); child sexual abuse material or child endangerment; discrimination based on protected characteristics; illegal activity (money laundering, human trafficking, illegal weapons, narcotics, illegal gambling, other crimes); terrorism or violent extremism; impersonation or source falsification; false/misleading content that may harm health/safety/public security; promotion of illegal drugs or harmful substance abuse; or unlawful alcohol/tobacco abuse.

4.2.2 Prohibited behaviors:

Developer Products must not:

Collect/store/transmit personal data without proper consent or legal basis;
Track/monitor/spying on users without consent or lawful purpose;
Send spam/unsolicited ads/communications;
Phish or deceive users to obtain personal/financial/sensitive data;
Hack, access without authorization, or attempt to disrupt other systems;
Mine cryptocurrency without clear notice and explicit user consent;
Tamper with or interfere with Tanqory Platform, other apps, or OS without authorization;
Scrape or collect data about other Tanqory users for unauthorized purposes;
Facilitate or encourage violations of Tanqory Terms of Service.

4.2.3 User‑generated content (UGC):

If UGC is allowed, the developer must:

Implement appropriate moderation/review to prevent illegal or inappropriate content.
Provide user reporting mechanisms for abusive/violating content.
Respond promptly and remove/block violating content; illegal/harmful content must be addressed within 24 hours.
Provide clear terms/community guidelines for users.
Cooperate with Tanqory and law enforcement on investigations and actions for illegal content.
Maintain sufficient logs for tracking/review of UGC as required by law.

4.3 Publishing and Updates

4.3.1 Submission for review:

To publish via the App Marketplace, the developer must submit through the Developer Portal with complete information, including:

Product info: name, detailed description, key features, user value, system/prerequisites, supported languages.
Marketing materials: 3–5 high‑quality screenshots, demo/intro video (if any), logo/icon, cover/illustrations.
Technical docs: install/config guides, end‑user guides, API docs (if applicable), FAQs, troubleshooting.
Pricing: model (free, one‑time, subscription, freemium, etc.), plan details, supported currencies, trial periods (if any).
Privacy/security: privacy policy, data collection/use details, OSS licenses used, permissions required, security measures.
Support: customer support channels (email/ticket/live chat), hours/expected response times, help center/site.
Terms: EULA, terms of service, refund/cancellation policies.
Provide accurate, complete, current, non‑misleading information; false/misleading info may lead to rejection or removal. Do not publish to end users before Tanqory approval.

4.3.2 Review and approval:

Tanqory may review via:
(a) Automated review: malware/virus scanning; known vulnerability scanning; private/unauthorized API use check; performance profiling; metadata validation; baseline technical compliance.
(b) Manual review: functional/feature testing; content/marketing quality; usability assessment; content/behavior policy compliance; privacy policy/data practices review; documentation completeness; interoperability/integration checks.
(c) Deep security audit (high‑risk products): penetration testing; in‑depth code analysis; security architecture review; risk assessment.

Estimated timelines: general products 5–7 business days; complex/high‑risk 10–14; minor updates 2–3. These are estimates only; no guaranteed timing.

Review outcomes:

Approved: passes all checks; developer notified and may set publish date.
Conditionally Approved: minor issues to fix within a set period (typically 30 days) or approval may be withdrawn.
Rejected: fails due to violations; feedback provided; may resubmit after fixes.
Review Suspended: awaiting additional info/clarification; resumes after info received.

4.3.3 Tanqory rights to reject or remove products:

Tanqory may, at its discretion, reject any submission for reasons including violations of this Agreement; low quality/insufficient user value; duplication/overlap; security/legal/reputational risk; misalignment with Tanqory strategy/direction/values. Tanqory may remove a product at any time after approval if it violates this Agreement, the developer breaches elsewhere, there are substantiated user/third‑party complaints, security/stability issues arise, continued listing risks harm to Tanqory/users/third parties, court/government orders require removal, or the product is obsolete/unmaintained (e.g., ≥12 months). Tanqory may limit visibility/access by region/user type/context for legal/business/technical reasons or adjust placement/ranking/prominence in the App Marketplace. Tanqory will attempt to give prior notice unless urgent/emergency or legally prohibited.

4.3.4 Publication and availability:

After approval, the developer may set a launch date/time or publish immediately. After publishing, the product appears in the App Marketplace for discovery/installation; the developer can monitor stats via the Developer Portal (downloads, installs, active users, ratings/reviews, revenue, etc.) and is responsible for customer support.

4.3.5 Product updates:

Developers should update periodically to fix bugs/security, add features, improve performance/UX, maintain compatibility, and update documentation. Update types:
(a) Minor Updates: non‑critical bug fixes, small performance tweaks, copy/translation fixes, minor metadata/docs updates (expedited review, typically 2–3 business days).
(b) Major Updates: significant new features/functionality, architecture/tech changes, substantial UI changes, pricing/terms changes (full review).
(c) Critical Security Updates: fixes for critical/high vulnerabilities or active threats/attacks (prioritized; may be approved within hours if urgency and details provided).

Update requirements: submit via Developer Portal and await approval (unless Tanqory permits auto‑approval for certain types); provide clear changelog/release notes; updates must not introduce new Agreement violations; maintain backward compatibility where feasible—if breaking changes, clearly notify users and allow reasonable adaptation time; thoroughly test updates before submission.

4.3.6 User notifications for updates:

Tanqory may notify end users of updates via in‑app notices, email (for major/security updates), Developer Portal, and App Marketplace. Developers may configure automatic updates (recommended for fixes/security), manual updates, or optional updates. For severe security updates, Tanqory may mandate automatic updates to protect users and the platform.

4.3.7 Product withdrawal from the App Marketplace:

Developers may withdraw products by giving at least 30 days’ notice to Tanqory (unless emergency/accepted special reason), optionally providing reasons, and appropriately handling existing users by notifying them, offering migration/export or alternatives, providing refunds/credits as required for prepaid users per refund policy/law, and continuing support for a reasonable period (recommended ≥90 days post‑withdrawal). After withdrawal, the product is removed from listing and new installs; existing users may continue use for a set period (typically 180 days) unless immediate disablement is required for security/legal reasons. Licenses granted to Tanqory under 3.4.4 remain in effect for existing users during that period.

4.3.8 Beta testing and staged rollout:

Tanqory may offer:
(a) Beta testing: limited beta channel for testers before public release to gather feedback, detect bugs, and improve; users should understand beta risks.
(b) Staged rollout/gradual deployment: release to increasing percentages (e.g., 10%, 25%, 50%, 100%) to reduce risk; monitor metrics/feedback per cohort; pause/rollback if severe issues arise.

4.3.9 Product settings/configuration:

Through the Developer Portal, developers may configure categorization/subcategories; tags/keywords; supported regions; supported languages; target audience (SMB/mid‑market/enterprise/industry); age rating; availability (immediate, future date, invite‑only).

4.3.10 Promotion and marketing:

Tanqory may promote products via featured placements, Tanqory marketing channels (blog, social, newsletter), special groupings (“new,” “top,” “editor’s picks”), and opportunities (events, webinars, developer activities). Promotion is discretionary, considering product quality/innovation, user demand, compliance, and readiness to collaborate on marketing materials. Developers remain primarily responsible for their own marketing (strategy/GTMS, owned channels, educational content, community engagement).

5. Payments and Revenue

5.1.1 Free products:

End users can download/use at no charge.
No revenue to the developer from downloads/installs.
Tanqory charges no commission/fees for free products (unless there are in‑app transactions).
Developers may monetize via ads, premium services, consulting, etc., subject to this Agreement.

5.1.2 Paid products:
(a) One‑time purchase: end users pay once for a perpetual or specified‑term license; developer sets price reasonably; Tanqory deducts commission (see 5.1.4).
(b) Subscription: recurring payments (monthly/quarterly/annually); developer sets price/billing cycle; may offer free trial/long‑term discounts; auto‑renews unless user cancels; commission on each billing cycle.
(c) Freemium: free basic version plus paid premium features; commission applies only to paid portion.
(d) Usage‑based / pay‑as‑you‑go: charges based on actual usage (e.g., transactions, users, data volume, API calls); developer must provide accurate, transparent usage tracking; commission applies to actual revenue.

5.1.3 In‑app purchases:

All in‑app purchases must run through Tanqory Payment System unless Tanqory approves otherwise in writing.
Clearly disclose what is being purchased, price, and what is delivered.
Purchases must not mislead or deceive.
Tanqory deducts commission on each in‑app purchase.

5.1.4 Commission rates:
(a) Standard: 30% of gross revenue for general products (gross = total paid by end users before taxes/fees/charges).
(b) Reduced: 15% for small developers with ≤USD 1,000,000 total annual platform revenue; 20% for subscriptions renewing beyond one year (from year two onward); 25% for special categories (education, non‑profit, public‑benefit) with Tanqory approval.
(c) Premium partner programs: developers in premium programs may receive lower rates under separate terms, based on Tanqory criteria (product quality, revenue volume, customer satisfaction, ecosystem contribution).
(d) Changes: Tanqory may change commission rates with at least 90 days’ notice; new rates apply prospectively; if not accepted, the developer may terminate during the notice period.

5.2 Payment processing

5.2.1 Tanqory Payment System:
All payments for Marketplace products are processed by Tanqory’s system, which supports multiple payment methods (cards, bank transfer, e‑wallets, others), manages recurring billing, tax handling/compliance, fraud protection and transaction verification, refunds/cancellations, and receipts/accounting for end users.

5.2.2 Payment data:

Tanqory receives/stores end‑user payment data (e.g., card details); the developer has no direct access.
The developer receives only data necessary for service/support (e.g., name, email, subscription type, payment status—not full card details).
The developer must protect received data under this Agreement’s data protection terms.

5.2.3 Currency and FX:

Developers may set prices in Tanqory‑supported base currencies (e.g., USD, EUR, GBP, SGD).
Tanqory converts to local user currency using Tanqory‑set FX rates.
Developers may set country/region‑specific prices if desired.
FX risk rests with the developer; Tanqory pays in the transacted currency or converts to the developer’s requested currency (FX fees may apply).

5.3 Payouts to developers

5.3.1 Payout schedule:

Standard: monthly, paid by the 15th of the following month (e.g., January revenue paid by 15 February).
Accelerated (for high‑tier developers): weekly or bi‑weekly for high revenue or premium partners.

5.3.2 Minimum payout:

Minimum accumulated balance USD 50 (or equivalent) for payout; smaller balances roll forward.
Developer may request a lower threshold case‑by‑case.

5.3.3 Payment methods:
Bank/wire transfer (recommended for larger amounts); ACH (US); SEPA (EU); PayPal/Payoneer (fees may apply); other methods as offered/accepted by Tanqory.

5.3.4 Transfer fees:

Domestic transfer fees borne by Tanqory.
International wire/intermediary/FX fees may be deducted from payouts or borne by the developer.
Provide accurate bank details to avoid unnecessary fees.

5.3.5 Reports and financial data:
Monthly Revenue Reports (revenue, commission, deductions, net payout); real‑time data via Developer Portal (revenue, transactions, payout status); tax documents (e.g., Form 1099 or local equivalents).

5.3.6 Deductions and setoff:
Tanqory may deduct for refunds; chargebacks (and related fees); fines/damages for developer breaches; tax withholdings; other amounts owed under this or other agreements. If deductions exceed amounts due, the developer must pay the shortfall within 15 days of notice.

5.4 Taxes and tax compliance

5.4.1 Developer tax responsibility:
Developer is solely responsible for determining, calculating, and paying all taxes on revenue from Tanqory (income tax, VAT/GST, sales/service tax, business tax, etc.), registering where required, filing/ paying on time, keeping accurate accounting records, and providing tax info to Tanqory (Tax/VAT IDs, certificates, etc.).

5.4.2 Withholding tax:
If Tanqory is legally required to withhold tax from payouts, it will do so and remit to authorities; amounts withheld appear on payout reports/tax docs. Developer may reduce/waive withholding by providing proper documents (e.g., Tax Residency Certificate for treaty rates; Form W‑8BEN for non‑US, Form W‑9 for US).

5.4.3 VAT/GST/sales tax:
Where required, Tanqory will charge end users applicable VAT/sales tax, remit to authorities, and issue tax invoices. Commissions Tanqory charges may include or exclude VAT depending on jurisdiction and developer tax status. VAT‑registered developers may request tax invoices for fees/commissions.

5.4.4 Tax law changes:
If tax law changes affect calculations or payouts, Tanqory will notify the developer and explain impacts; the developer will cooperate (provide info, register, adjust pricing if needed). Parties may adjust financial terms if necessary to comply with new law.

6. Support and Maintenance

6.1 Developer support responsibilities

6.1.1 End‑user support: the developer is solely responsible for technical/customer support to end users, including answering questions, diagnosing/fixing bugs/issues, advising on best practices, handling complaints professionally and promptly, and providing/updating guides, videos, FAQs, and learning resources.

6.1.2 Support channels: provide at least one suitable channel (support email; ticketing system/forum; live chat/real‑time support; phone for enterprise products; help center/knowledge base). Display support contacts clearly in the Marketplace listing and within the product.

6.1.3 Response times: publish expected response times and strive to meet them: general questions 24–48 business hours; medium‑impact issues within 24 hours; severe/critical issues within 4–8 hours; security issues within 2–4 hours with immediate remediation start.

6.1.4 Support quality: support must be professional, courteous, accurate, helpful, timely, and consistent with promises/warranties. Tanqory may monitor support quality via user satisfaction surveys, ratings/reviews, and spot‑checking communications.

6.2 Tanqory support responsibilities

6.2.1 Platform support: Tanqory supports platform‑wide issues (platform use, accounts/authentication, payments/billing via Tanqory, installs/updates via the Marketplace, platform security/privacy issues, and mediating user‑developer disputes).

6.2.2 Escalation/coordination: Tanqory may receive user questions/complaints about Developer Products and will seek to identify/forward them to the relevant developer promptly; the developer must cooperate and respond within required timeframes.

6.2.3 Developer support: Tanqory provides Developer Portal resources (docs, guides, tools); technical documentation (API references, SDK guides, integration tutorials); developer forums/communities; technical assistance for integration/troubleshooting/API use; and updates/communications via email/blog/other channels.

6.3 Maintenance and updates

6.3.1 Maintenance obligations: developers will regularly maintain products (update to fix bugs, improve performance, add features), ensure compatibility with current Tanqory Platform versions, promptly remediate security vulnerabilities (especially severe), and provide ongoing support—do not abandon products/users without a migration/alternative plan.

6.3.2 Unmaintained products: if a product is not updated/maintained for an extended period (generally ≥12 months) without reasonable cause, Tanqory may contact the developer about status/maintenance plans, may warn users that the product may no longer be maintained, and may take further steps consistent with platform policies.

6.3.3 End of Life: if the developer decides to permanently end the product, it must (a) give at least 6 months’ prior notice to Tanqory and end users (longer for critical/high‑user products); (b) advise users on options, data migration, and next steps; (c) refund/credit appropriately for prepaid subscriptions; and (d) continue support during the transition.

6A. API Technical Requirements and Service Level Agreement

6A.1 API use and limits

6A.1.1 API access: use only the API key/secret issued; keep credentials secure; use APIs solely for authorized purposes per API Documentation.

6A.1.2 Rate limits: Standard: 1,000 requests/hour/API key; Professional: 5,000; Enterprise: 20,000 or as specially agreed. Exceeding limits returns HTTP 429; persistent violations may result in suspension.

6A.1.3 API changes/deprecation: Tanqory may change/improve/deprecate APIs; ≥90 days’ notice for breaking changes; ≥30 days’ notice for non‑breaking; legacy versions supported at least 180 days after a new version launches.

6A.2 Service Level Agreement

6A.2.1 Uptime: target 99.9% monthly (≤43.8 minutes downtime/month). Planned maintenance with ≥72 hours’ notice at low‑impact times. Emergency downtime may occur without notice for security/stability.

6A.2.2 Response times: Read (GET) avg ≤200ms; Write (POST/PUT/PATCH) avg ≤500ms; Batch (100 records) avg ≤2s.

6A.2.3 Notifications: incidents posted on status.tanqory.com; email for major impact; post‑incident reports for significant outages.

6A.2.4 SLA exclusions: force majeure/external factors; misuse or violations by developer; developer’s own network/systems; planned maintenance with notice.

6A.3 Technical security requirements

6A.3.1 Encryption: TLS 1.3+ in transit; AES‑256 at rest for stored data (especially personal/payment); store API credentials encrypted and never hard‑code.

6A.3.2 AuthZ/AuthN: use OAuth 2.1 or API key auth per docs; apply least‑privilege; do not share/transfer credentials without approval.

6A.3.3 Application security: comply with OWASP Top 10; validate/sanitize all inputs (SQLi, XSS, command injection); keep dependencies current and free of known vulnerabilities; apply security patches within 30 days for critical/high issues.

6A.3.4 Security assessment: conduct regular security assessments; PCI DSS if handling card data; Tanqory may request security audit reports or conduct penetration tests.

6A.3.5 Vulnerability disclosure: report issues to security@tanqory.com immediately; do not disclose publicly until fixed; Tanqory may provide bug bounty for significant reports.

7. Warranties and Disclaimers

7.1 Developer warranties

The developer represents and warrants that:
7.1.1 Quality: products operate as described in docs/descriptions/marketing for at least 90 days from first install/use (or throughout the subscription term); free of material defects affecting core functions; professionally developed to industry standards.
7.1.2 Security: products are free of malware and known avoidable security vulnerabilities at release; appropriate safeguards protect user data/privacy.
7.1.3 Legal compliance: products and their development/distribution/use do not violate laws or third‑party rights; developer has full authority to enter and perform this Agreement.
7.1.4 Compliance with this Agreement: products comply with all requirements and applicable data protection/consumer/IP laws.
7.1.5 Remedies: if products breach warranties, developer will remedy within a reasonable time (typically 30 days, sooner for severe issues), provide an appropriate alternative/fix, or refund affected end users if unresolved.

7.2 Tanqory disclaimers

7.2.1 AS‑IS/AS‑AVAILABLE: developer software, services, Marketplace, and other services are provided “AS IS” and “AS AVAILABLE” without any warranties.
7.2.2 Disclaimed warranties: Tanqory disclaims all express/implied/statutory warranties, including merchantability, fitness for a particular purpose, non‑infringement, accuracy, reliability, and uninterrupted/secure/error‑free service.
7.2.3 Developer responsibility: developer is solely responsible for its products, content, and use of developer software/services and will not claim damages from Tanqory for losses arising from such use.

8. Limitation of Liability

8.1 Tanqory liability limits

8.1.1 Excluded damages: to the extent permitted by law, Tanqory and its affiliates/officers/employees/agents/providers are not liable for indirect, punitive, special, consequential, loss of profits/revenue/business/data/goodwill, replacement costs, or incidental damages, whether in contract, tort, negligence, strict liability, or otherwise.
8.1.2 Cap: if liability cannot be fully disclaimed, total liability will not exceed (a) for free products: USD 100; (b) for paid products: the net amount the developer actually received from Tanqory in the 12 months preceding the event or USD 50,000, whichever is less. Cap applies in aggregate for all claims.
8.1.3 Exceptions: caps/exclusions do not apply to fraud, willful misconduct, intentional confidentiality breach by Tanqory, death/personal injury from gross negligence/intent, or other non‑excludable liabilities.
8.1.4 Basis of bargain: limitations apply even if remedies fail of essential purpose and even if Tanqory knew of possible damages.

8.2 Developer liability

Developer is solely responsible for its products, content, acts/omissions, and third‑party claims relating to its products; developer will protect and hold Tanqory harmless per Section 11.

9. Notices of Violations and Handling

9.1 IP infringement notices (notice/takedown)

If Tanqory receives a third‑party IP complaint: Tanqory will forward it; developer has 5 business days to respond with evidence; absent sufficient response, Tanqory may remove/suspend the product; if infringement is proven, developer must remove/modify infringing content immediately or face permanent removal.

Counter‑notice: developer may submit a detailed counter‑notice (originality/license/fair use) with evidence and sworn statement; Tanqory may restore the product if the counter‑notice has merit.

9.2 Handling Agreement violations

Warning ladder (minor breaches): 1st warning with 7 days to cure; 2nd warning and temporary suspension until cured; 3rd warning removal and possible account suspension.
Immediate suspension (serious breaches): Tanqory may remove and suspend immediately for malware, severe IP infringement, illegal/harmful content, fraud/deception, or unremediated critical security issues.

10. Term and Termination

10.1 Term

Initial term: 1 year from acceptance (click‑accept, registration, or use) and auto‑renews yearly unless either party gives 30 days’ written notice before expiry.

10.2 Termination by developer

Developer may terminate anytime by written notice via Developer Portal or email to developer@tanqory.com; effective within 30 days of Tanqory’s receipt. Developer must fulfill obligations during notice.

Effects: licenses to developer tools/services end; products removed from Marketplace within 30 days; developer must support existing users for a reasonable period (at least 90 days); Tanqory pays final balances per schedule, net of amounts owed.

10.3 Termination by Tanqory

For convenience: with 90 days’ prior written notice.
For cause (immediate): if developer materially breaches and fails to cure within 15 days of notice; repeated breaches; fraud/deception/bad faith; bankruptcy/insolvency/liquidation; government/court prohibition; unauthorized assignment/transfer.
Suspension: Tanqory may temporarily suspend access for investigations, security/technical needs, legal orders, or unpaid debts; lifted when resolved.

10.4 Effects of termination

10.4.1 End of rights: all licenses to developer end; developer must cease use of developer software/services and Tanqory IP; return or destroy developer software, docs, and Tanqory confidential information.
10.4.2 Existing products: removed from Marketplace; existing users may continue use per 3.4.4 (typically 180 days); developer must reasonably support existing users.
10.4.3 Final settlement: Tanqory will calculate and pay final amounts within 60 days, less offsets (refunds, penalties, damages, taxes). If developer owes more than amounts due, developer must pay the shortfall within 30 days.
10.4.4 Surviving obligations: confidentiality (3.2); IP (3.4); indemnity (11); warranty/limitation (7, 8); governing law/disputes (13, 14); general provisions (15); and other provisions that by nature should survive.

11. Indemnification

11.1 Developer indemnity

Developer will indemnify, defend, and hold harmless Tanqory and its affiliates, parents, subs, officers, directors, employees, agents, contractors, providers, and licensors (“Indemnified Parties”) from claims, suits, losses, damages, fines, fees, costs (including attorneys’ fees), and liabilities arising from: (a) development/distribution/use/operation of Developer Products, defects/errors/malfunctions, IP infringement allegations, or product content/data; (b) breach/alleged breach of this Agreement, law, or third‑party rights; (c) acts/omissions of developer/personnel/agents/subcontractors; (d) collection/use/disclosure/processing of personal data, data breaches, or unauthorized disclosures related to Developer Products.

11.2 Indemnity procedure

Prompt written notice (delay does not waive unless materially prejudicial); developer controls defense/settlement, with Tanqory cooperation; developer pays its and Tanqory’s defense costs; no settlement binding Tanqory without prior written consent. Tanqory may participate with its own counsel at its expense.

11.3 Tanqory indemnity

Tanqory will indemnify and defend the developer against third‑party claims that authorized use of developer software/services under this Agreement infringes third‑party IP, provided the developer gives prompt written notice, Tanqory controls defense/settlement, and developer reasonably cooperates. Exclusions: modifications/uses not authorized; combinations with non‑Tanqory items; failure to use updates provided to avoid infringement.

12. Trade Secrets and Non‑Compete

12.1 Confidential information

Developer acknowledges developer software/services, technical docs, and other disclosures contain Tanqory trade secrets. Confidentiality obligations in 3.2 survive for 5 years after termination, or indefinitely for trade secrets by law.

12.2 Non‑compete

During the term, developer will not: (a) develop/publish/promote products that directly compete with core Tanqory Platform features without genuine added value/innovation; or (b) use program‑derived information/know‑how to build competing products. This does not bar complementary/integrated products, differentiated products in the same category/industry, or products for other platforms/markets.

Customer solicitation: developer will not solicit or attempt to solicit Tanqory customers to leave or switch using Tanqory‑provided customer data; will not use customer lists/contacts obtained via Tanqory except to support the Developer Product.

13. Governing Law and Forum

Governing law: laws of the Republic of Singapore, excluding conflict‑of‑laws principles; UN CISG does not apply.

Disputes are resolved by arbitration under Section 14 (SIAC). Nothing in this Section limits Tanqory’s right to seek interim or injunctive relief in any court of competent jurisdiction to protect IP or confidential information or to enforce an arbitral award. Parties consent to such courts for these limited purposes.

14. Dispute Resolution and Arbitration

14.1 Good‑faith negotiation

Parties will attempt to resolve disputes through good‑faith negotiation for at least 30 days after written notice of dispute by decision‑makers of each party.

14.2 Mediation (disputes ≤ USD 50,000)

If negotiations fail, disputes up to USD 50,000 may be mediated under a mutually agreed mediator; fees shared unless agreed otherwise; mediation does not waive arbitration rights.

14.3 Arbitration (SIAC)

Unresolved disputes will be finally settled by arbitration under SIAC Rules: seat Singapore; language English; one arbitrator (or as rules/parties agree); arbitrator decisions final/binding and enforceable in courts; parties waive appeals to the extent permitted. Costs allocated per award (typically loser pays, subject to arbitrator discretion).

14.4 Interim relief

Tanqory may seek injunctive/interim/provisional relief from courts to protect IP, prevent disclosure of confidential info, or stop ongoing/imminent violations.

15. General Provisions

15.1 Amendments

Tanqory may amend this Agreement with notice via email/Developer Portal/website/blog. Effective 30 days after notice for material changes; 7 days for minor/clarifications; immediate for legal/security changes. Continued use after effective date = acceptance; if not accepted, developer may terminate during notice.

15.2 Assignment

Developer may not assign/transfer/subcontract rights/obligations without Tanqory’s prior written consent; unauthorized attempts are void. Tanqory may assign to affiliates/subs/parent or successors (merger, acquisition, restructuring, sale of all/substantially all assets) without consent; assignee assumes rights/obligations.

15.3 Relationship

Parties are independent contractors; no employment, partnership, joint venture, agency, or franchise is created. Developer has no authority to bind Tanqory or make promises/warranties on Tanqory’s behalf.

15.4 Waiver and severability

No failure to exercise/enforce is a waiver; waivers must be in writing. If any provision is illegal/unenforceable/void, it will be modified or construed to be enforceable to effect parties’ intent, and remaining provisions stay in force.

15.5 Entire agreement

This Agreement plus referenced documents/policies form the entire agreement, superseding prior or contemporaneous agreements/communications (written or oral) on the subject. Priority: (1) this Agreement; (2) mutually signed addenda; (3) referenced policies/guidelines. Amendments only per 15.1 or written agreement signed by both parties.

15.6 Notices

Written notices deemed given when delivered personally/courier with tracking; registered mail with return receipt prepaid; email to designated addresses; or posted in Developer Portal (for general notices/policy changes).

Notices to Tanqory:

Tanqory Inc.
c/o Harvard Business Services, Inc.
16192 Coastal Highway
Lewes, DE 19958, USA
Email: legal@tanqory.com
Attn: Legal Department

Notices to developer go to the registered address/email. Developer must notify Tanqory within 10 days of address/email changes.

15.7 Third‑party beneficiaries

No third‑party rights/benefits except as expressly stated (e.g., Indemnified Parties).

15.8 Interpretation

Headings are for convenience only. “Including” means “including without limitation.” If translations conflict, the English version governs.

15.9 Survival

Survives: 3.2 (Confidentiality); 3.4 (IP); 5 (payment obligations accrued); 7 (as applicable); 8; 10.4; 11; 12; 13; 14; 15; and other provisions that by nature should survive.

16. Contact and Company Information

Registered Agent (Delaware, USA):
Tanqory Inc.
c/o Harvard Business Services, Inc.
16192 Coastal Hwy
Lewes, DE 19958
United States

EU Operations (GDPR Art. 27 representative):
Tanqory OÜ
Ahtri tn 12
Kesklinna linnaosa, Harju maakond
10151 Tallinn
Estonia

Contacts:

Website: https://tanqory.com
Developer Portal: https://developer.tanqory.com
General: legal@tanqory.com
Developer: developer@tanqory.com
Security: security@tanqory.com

Acceptance

By clicking “Accept,” registering for the Developer Program, or using developer software/services, you confirm that you (1) have read, understood, and agree to all terms; (2) have legal capacity/authority to enter this Agreement; (3) if acting for an entity, are duly authorized to bind it; and (4) will comply with all terms.

Effective Date: 28 May 2026 Last Updated: 28 May 2026 Version: 1.0