SDK License Terms

Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers who use, modify, or distribute a Platform software development kit or a client library for the Platform application programming interface.

Article 1: Introduction and Scope

1.1 This document states the licence for a software development kit the Company publishes (the "SDK"), the limits on modification and redistribution, and the terms for a client library the Company has not published. The SDK licence does not expand the API licence in the Developer Agreement.

1.2 If a provision of this document conflicts with the Terms of Use, this document controls for SDK use. If a provision of this document conflicts with the Developer Agreement, the Developer Agreement controls, except that this document controls for the SDK itself. For a community client, Article 8 of this document and the Developer Brand and Trademark Use (Developer Brand and Trademark Use Policy) control. Policies and help pages explain this document; they do not amend it.

Article 2: Definitions

2.1 In this document, terms defined in the Developer Agreement have the same meaning, and Community Client: a client library, a wrapper, a helper package, or an integration kit for the API that the Company has not published.

SDK: a client library, code sample, command-line tool, and developer tooling the Company publishes through an official channel, each release identified by a version number and a distribution package.

Article 3: Licence Grant

3.1 Subject to this document and the Developer Agreement, the Company grants the Developer a non-exclusive, non-transferable, revocable licence to use, reproduce, and distribute the SDK solely as integrated into an Application that uses the API under the Developer Agreement and §Developer Agreement–2.7.25.

3.2 "Integrated into" means the SDK is included inside an Application the Developer operates, as a component of that Application. Repackaging the SDK as a standalone developer product, including a toolkit offered separately from an Application, is outside the grant.

3.3 The licence is licensed, not sold. No perpetual or irrevocable right arises under this document. The licence ends in accordance with Article 7 of this document and ends automatically on termination of the Developer's API access under the Partner Suspension, Termination and Appeals.

Article 4: Modification and Redistribution

4.1 The Developer may modify SDK source for the Developer's own Applications, including adaptation, removal of an unneeded part, and correction of a defect the Developer finds. A modified SDK shall not be represented as official, as unmodified, or as endorsed by the Company. The Developer assumes full responsibility for a defect the Developer's modification introduces.

4.2 Redistribution is permitted only as integration under clause 3.2, with every licence notice, attribution heading, and diagnostic identifier of the SDK intact. The Developer shall not redistribute the SDK on a standalone basis as a competing developer product.

Article 5: Restrictions

5.1 The Developer shall not: (a) use the SDK to access the API outside the licence in the Developer Agreement: inclusion of a prohibited use in official code does not make the use permitted; (b) remove or alter an SDK licence notice, an attribution heading, or a diagnostic identifier; (c) use the SDK to operate a competing marketplace; or (d) reverse-engineer an SDK component to circumvent the API's authentication or rate limits, and no reverse engineering the law permits the Developer to perform may be used for that purpose.

5.2 Diagnostic reporting in the SDK: the SDK version, the operating environment, an error report, and a deprecation signal described in the Deprecation and Breaking Changes Policy: is part of the SDK. The Developer may disable diagnostic reporting only where the SDK documentation for the release concerned states an opt-out. Removal of diagnostic reporting by modification, or blocking of the diagnostic address while the SDK's API functions are used, is prohibited.

Article 6: Version Support and Security Updates

6.1 Each major SDK version is supported for twelve (12) months after release of its successor. A security correction is made available for the prior major version during that period.

6.2 An Application shall not run an SDK version with a known uncorrected critical vulnerability beyond thirty (30) days after release of the correction. Continued use after thirty (30) days is a security violation under the Partner Security Requirements, and the Company may suspend the Application's access until the Application is updated.

6.3 A breaking SDK change follows the notice rules of the Deprecation and Breaking Changes Policy. The Developer shall test an SDK update before production deployment.

Article 7: Warranty and Liability for the SDK

7.1 The SDK is provided without warranty of any kind, express or implied, including a warranty of merchantability, fitness for a particular purpose, and non-infringement, to the fullest extent permitted by law and in addition to Article 9. The Company does not warrant that the SDK is free of error, that the SDK operates in every environment, or that an Application built on the SDK satisfies the App Listing Standards or the Integration Certification Policy.

7.2 The Company is not liable for an Application defect arising from the Developer's modification of the SDK, or for a loss caused by the Developer's failure to apply a security correction under clause 6.2, except as Article 9 provides and as applicable law requires.

Article 8: Community Clients

8.1 A Community Client is permitted, subject to this article. The author of a Community Client is a Developer under this document for the acts of that client.

8.2 Naming and endorsement. A Community Client shall not use a Company name or mark in its name, package name, repository title, or marketing in a manner that implies the Company published or endorsed it, in accordance with the Developer Brand and Trademark Use (Developer Brand and Trademark Use Policy). A name that states the unofficial character of the client plainly satisfies this clause; a name that presents the client as the Company's SDK does not.

8.3 Identification. Every Community Client shall identify itself on every request with a client identifier containing the client name, the version, and a contact the Company can reach, in the form the API Policies prescribe. The Company uses the identifier for deprecation notice under the Deprecation and Breaking Changes Policy and for contact about abuse. Rotation or falsification of the identifier is Circumvention under the Scraping Prohibition.

8.4 Rate discipline. A Community Client shall observe the API Rate Limits and Quotas. Multiplication of client instances, sessions, or addresses to multiply the effective limit is prohibited. A client that requires greater throughput shall proceed by Tier change under the API Access Tiers.

8.5 No credential collection. A Community Client shall not ask an End User for a Platform password, a credential issued for internal or service use, or any credential the Company did not issue to that End User. Collection of a credential the client cannot legitimately use is treated as malicious conduct and is a material breach without a cure period under Article 10.

8.6 Security duties of the author. The author of a Community Client shall: (a) require an encrypted connection and refuse to operate over an unencrypted connection for a request carrying Credential Data as defined in the Data Use, Retention and Deletion; (b) store a token and a session on the server side only, and not in storage accessible to client-side scripts for a server-to-server integration; (c) publish a security contact; and (d) issue a correction for a critical vulnerability within thirty (30) days of becoming aware of it and notify known users of the client. Breach notice for a defect in a Community Client follows the Breach Notification Requirements.

8.7 Migration. On release of an official SDK, a Community Client remains permitted under this article. An Application built on a Community Client shall migrate within the support period the Company announces under the Deprecation and Breaking Changes Policy.

Article 9: Liability

9.1 Exclusion of certain damages. To the fullest extent permitted by law, neither party is liable to the other for indirect, incidental, special, punitive, or consequential damages, or for lost profits, lost revenue, or loss of goodwill, arising out of or relating to this document, even if the party has been advised of the possibility of those damages.

9.2 Cap. To the fullest extent permitted by law, the Company's total liability arising out of or relating to this document, including a claim arising from an SDK defect, an interruption, a breaking change, or a documentation error, shall not exceed the greater of (a) the amounts the Developer paid to the Company under this document in the twelve months before the event giving rise to the claim, or (b) one hundred dollars ($100).

9.3 Carve-outs. This article does not limit (a) a party's indemnification obligations under this document; (b) liability for fraud or willful misconduct; (c) amounts the Developer owes for Orders, fees, chargebacks, or refunds under this document; or (d) liability that cannot be limited under applicable law.

9.4 Essential purpose. The parties agree that this article allocates risk between them, that it is an essential part of the basis of their bargain, and that it applies even if a limited remedy fails of its essential purpose.

Article 10: Indemnification

10.1 Duty. The Developer shall indemnify, defend, and hold harmless the Company and its members, managers, employees, and agents from and against every claim, demand, action, loss, liability, judgment, settlement, cost, and expense (including reasonable attorneys' fees) arising out of or relating to: (a) the Developer's breach of this document; (b) the Developer's Applications, SDK modifications, and Community Clients; (c) the Developer's violation of any law or of the rights of any person; and (d) taxes for which the Developer is responsible under this document.

10.2 Procedure. The Company shall give prompt written notice of a claim under this article. The Developer shall control the defense with counsel reasonably acceptable to the Company. The Company may participate in the defense at its own expense. The Developer shall not settle a claim in a manner that imposes any obligation or restriction on the Company, or that does not release the Company fully, without the Company's prior written consent.

10.3 Survival. This article survives the termination of this document.

Article 11: Enforcement and Appeals

11.1 Investigation. The Company may investigate any suspected violation of this document. The Developer shall cooperate with an investigation and shall produce the records this document requires the Developer to keep. SDK diagnostic records and client identifier records are the records principally relied on under this document; a client that removes both has made itself unreachable, and unreachability is treated as non-cooperation.

11.2 Notice. If the Company determines that the Developer has violated this document, the Company shall give written notice stating the provision violated and the facts relied on, except where notice would compromise an investigation of fraud, a safety risk, or a legal obligation.

11.3 Opportunity to cure. Where a violation is capable of cure, the Developer has ten (10) business days from notice to cure it and to confirm the cure in writing. No cure period applies to credential collection under clause 8.5, to Scraping under the Scraping Prohibition, to sale of data under the Data Use, Retention and Deletion, to fraud, or to a violation that by its nature cannot be cured.

11.4 Measures. If a violation is established and is not cured within the period allowed, the Company may, proportionate to the violation: (a) issue a written warning; (b) require renaming of a Community Client and removal of a credential prompt, within fifteen (15) days where Article 8 is concerned; (c) block a traffic pattern at the network edge pending compliance; (d) suspend or revoke a Credential or SDK licence; (e) suspend the Account or a program participation, in whole or in part; (f) terminate this document and the Account; and (g) exercise any other right or remedy available under this document or at law. Procedure is further governed by the Partner Suspension, Termination and Appeals.

11.5 Appeal. The Developer may appeal a measure under this article by written notice to legal@aapawz.com within thirty (30) days of the measure, stating the grounds and attaching the records relied on. The appeal is decided by a person who did not make the original decision. The Company's decision on appeal is final. A measure remains in effect during an appeal unless the Company directs otherwise in writing.

11.6 No waiver by delay. The Company's delay in acting on a violation is not a waiver of the violation or of any later violation of the same kind.

Article 12: Term and Termination

12.1 Term. This document takes effect when the Developer first uses the SDK or publishes a Community Client, whichever occurs first, and continues until terminated under this article.

12.2 Termination by the Company. The Company may terminate the SDK licence for cause: breach of Articles 3–6 or Article 8, breach of the Developer Agreement, a security violation under the Partner Security Requirements, or termination of API access under the Partner Suspension, Termination and Appeals: in accordance with the cure procedure in Article 11 for a curable breach and immediately for a violation described in clause 11.3. The Company may terminate this document for any other reason on thirty (30) days' written notice.

12.3 Termination by the Developer. The Developer may terminate this document on thirty (30) days' written notice to support@aapawz.com, provided the Developer has no investigation outstanding and has performed clause 12.4.

12.4 Effect of termination. On termination of the SDK licence: (a) the Developer shall stop distributing the SDK within thirty (30) days; (b) the Developer shall remove the SDK from an Application the Developer controls at the next release and in any event within ninety (90) days; (c) the Developer shall certify compliance in writing to support@aapawz.com; (d) an End User who received the Application before termination may continue to use the installed copy, and the Developer shall not issue a new copy containing the SDK; and (e) obligations that arose before termination survive until satisfied.

12.5 Survival. The Definitions, Liability, Indemnification, Enforcement and Appeals (for measures taken before termination), Dispute Resolution, and General Provisions articles survive termination, together with Article 7.

Article 13: Dispute Resolution

13.1 Any dispute arising out of or relating to this document, or to the relationship it governs, is governed by the Dispute Resolution Policy, which is incorporated into this document by reference.

Article 14: General Provisions

14.1 Amendments. The Company may amend this document by posting the amended document in the Document Center and giving notice to the Developer at the email address in the Account. An amendment that materially increases the Developer's fees or obligations takes effect thirty (30) days after notice; other amendments take effect on posting. Continued use of the Platform after the effective date of an amendment is acceptance of it. If the Developer does not accept an amendment, the Developer's remedy is to terminate under Article 12 before the amendment takes effect.

14.2 Notices. Legal notices under this document shall be sent to legal@aapawz.com. Operational notices, including a certification under clause 12.4, and all other communications shall be sent to support@aapawz.com. A notice to the Company is effective when the Company acknowledges receipt or, for email, one business day after sending, whichever is earlier. Notices to the Developer are effective when sent to the email address in the Account or posted to the Account's notice facility in the portal, whichever occurs first. The Developer shall keep the email address in the Account current. DMCA notices are given as provided in the DMCA and Copyright Policy, to the designated agent at legal@aapawz.com.

14.3 Governing law. This document is governed by the laws of the State of Tennessee, without regard to its conflict-of-laws rules. Subject to the Dispute Resolution Policy, any proceeding arising out of this document shall be brought in the state or federal courts located in Shelby County, Tennessee, and the parties consent to personal jurisdiction there.

14.4 Severability. If any provision of this document is held unenforceable, the provision shall be enforced to the fullest extent permitted, and the remaining provisions continue in full effect.

14.5 Entire agreement. This document, together with the documents it incorporates by reference, is the entire agreement between the Company and the Developer for the subject it governs and supersedes every prior or contemporaneous statement, communication, or agreement on that subject, whether written or oral.

14.6 Assignment. The Developer shall not assign this document or any right or obligation under it without the Company's prior written consent, and an assignment without consent is void. The Company may assign this document to an affiliate or in connection with a sale of all or part of its business, on notice to the Developer.

14.7 Waiver. A waiver of any provision of this document is effective only in writing and only for the instance stated. No waiver is a waiver of any other provision or instance.

14.8 Interpretation. Headings are for convenience only. "Including" means "including without limitation." This document shall not be construed against a party on the ground that the party prepared it. The English-language text controls over any translation.