App Marketplace Terms
Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers who publish an Application in the App Marketplace and all Sellers and merchants who install a marketplace Application.
Article 1: Introduction and Scope
1.1 This document states the distribution terms for the App Marketplace: eligibility to publish, review, the duties owed to an installer, the Company's removal rights, and the duties on uninstall and on removal. Listing content is governed in detail by the App Listing Standards and revenue is governed by the Partner Revenue Share Policy.
1.2 If a provision of this document conflicts with the Terms of Use, this document controls for marketplace participation. If a provision of this document conflicts with the Developer Agreement, this document controls for marketplace matters and the Developer Agreement controls for all other matters. 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 the Developer who publishes in the marketplace is the "Publisher" for purposes of this document. In addition Install: the act by which an Installer authorizes an Application to access the Installer's data within the scopes the listing discloses. Removal of the Application by the Installer is the "Uninstall" and revokes that authorization.
Installer: a Seller or merchant who installs an Application.
Listing: the marketplace page for an Application: the name, the description, the images, the price, the requested scopes, the support terms, and the privacy disclosures. A Listing is a binding representation by the Publisher: the Application shall do what the Listing states, and an omission from the Listing is treated as an undisclosed matter at review.
Article 3: Eligibility to Publish
3.1 Publishing requires all of the following: (a) Elevated Tier under the API Access Tiers; (b) an approved Application under the OAuth App Registration and Review; (c) a passing listing review under the App Listing Standards; (d) acceptance of the revenue terms in the Partner Revenue Share Policy; and (e) a published support commitment that meets the standard in the Partner Support and Incident Escalation Policy for the Application's category.
3.2 One Publisher, one identity. The legal identity on the Listing shall match the identity on the Publisher's partner intake and Developer account. A shell publisher, a pass-through Listing that conceals the real operator, and a Listing filed under another firm's credentials are rejected at review and are cause for removal if discovered after publication.
3.3 The Company may limit the number of Applications in a category to protect marketplace quality. A limit is published per category with written criteria that state what counts as the same category, how an existing Publisher is treated, and when the limit re-opens. A limit shall be applied on content-neutral criteria.
Article 4: Review
4.1 Listing review examines: truthfulness: the Application does what the Listing states and the Listing discloses what the Application does, with every requested scope justified in plain language on the Listing; safety: no credential collection, no session pooling, no undisclosed transfer of data, and data handling consistent with the Data Use, Retention and Deletion; and fitness: the Application operates on the API, handles an error without corrupting merchant data, and uninstalls cleanly under Article 7. The content standards applied at review are stated in the App Listing Standards, which controls for listing content and review outcomes in the event of a conflict.
4.2 The reviewer may require a change to the Listing, to a scope request, or to data handling. The Publisher shall make the required change and resubmit. A material change after approval: a new scope, a new class of data touched, or a new subprocessor: requires re-review before deployment. Deployment of a material change without re-review is a breach, and the Listing may be suspended pending review.
4.3 The Company may require a security re-review at any time: on report of a vulnerability, on a material change, on a pattern of Installer complaints, or on a published schedule. Re-review is not a penalty; refusal of re-review is cause for suspension.
Article 5: The Publisher and Installer Relationship
5.1 The Publisher–Installer relationship is direct. The Publisher is the seller of the Application and is responsible for its function, for support at the published standard, and for refunds under the Publisher's published terms. The Publisher's refund terms shall meet or exceed clause 5.2 and shall be linked from the Listing.
5.2 Minimum refund term: a full refund within fourteen (14) days of Install if the Application fails to perform the functions the Listing describes. The Listing is the measure of the described functions. The Publisher may offer a more generous term and shall not offer a lesser term.
5.3 The Company is not a party to the Publisher–Installer contract. The Company does not warrant the Application, does not decide a dispute about a feature, and does not hold an Installer's money for the Publisher. The Company may intervene for a violation of policy, a security matter, an unresolved dispute affecting a Buyer, or fraud, by a measure in Article 8.
5.4 Price honesty. The Listing shall state the price plainly: the amount, the billing interval, what event triggers a usage charge, and what occurs at a plan limit. A low headline price with a mandatory addition disclosed only after Install is a deceptive practice and is cause for removal. A free trial shall state what occurs at the end of the trial: conversion to a paid plan, reduction to a lesser plan, or Uninstall: and the outcome shall be the one the Installer selected in advance, not a silent default.
Article 6: Revenue
6.1 Marketplace fees, the collection method, payout timing to a Publisher, and the treatment of a refund and a chargeback are governed by the Partner Revenue Share Policy. The Company calculates a fee at the transaction, pays the Publisher on the schedule that document states, reverses a fee automatically on an Installer refund within the period in clause 5.2, and maintains a Publisher-visible record of every fee assessed, which the Publisher may inspect.
6.2 The Company's fee is for marketplace participation: distribution, trust, and billing facilities. The fee is not a commission on the Publisher–Installer relationship and does not make the Company a party to that relationship.
Article 7: Installer Protections and Uninstall
7.1 An Application may request only the scopes justified in its Listing. The Installer sees the full scope list at Install, in plain language, before authorizing. Use of a scope for a purpose the Listing did not justify is a violation of the Data Use, Retention and Deletion as well as of this document.
7.2 Uninstall is absolute. An Installer may uninstall at any time, for any reason, through a control the Company provides, and not only through a support request to the Publisher. Uninstall revokes authorization immediately. An Application that continues to call the API after Uninstall acts without authorization.
7.3 An Application shall not degrade Platform performance for the Installer or for another person: no repeated polling at a rate the API Rate Limits and Quotas do not permit, no repeated full-catalog retrieval on a timer, and no acknowledgement failure that forces a redelivery cycle under the Webhook Obligations. The API Rate Limits and Quotas applies to a marketplace Application as to every other API consumer; marketplace distribution grants no greater capacity.
7.4 Installer data remains the Installer's. The Publisher's licence to Installer data is the licence in the Data Use, Retention and Deletion: limited to the Application's stated function and ending at Uninstall. Use of Installer data to build a competing product, and sale of Installer data, are governed by that document and by Article 8 of this document in the same proceeding.
7.5 On Uninstall, the Publisher shall: (a) stop every API Call for that Installer immediately; (b) delete the Installer's Personal Data within thirty (30) days and Order Data in accordance with the Data Use, Retention and Deletion, or sooner if the Installer requests earlier deletion where that document permits; (c) destroy the Installer's credentials immediately; and (d) confirm deletion to the Installer in writing within forty-five (45) days, in the certification form the Data Use, Retention and Deletion requires.
7.6 On termination of the Publisher or removal of the Listing under Article 8, the duties in clause 7.5 apply to every Installer at once: all Installer Personal Data deleted within thirty (30) days of the removal date, certification delivered to the Company within forty-five (45) days, and backup rotation completing removal of the last copies within ninety (90) days. Retention of Installer data for a possible reactivation is retention without authorization. The Company verifies compliance after removal, by confirmation of the certification and by examination where examination is technically feasible, and records the outcome. A Publisher that cannot produce the certification is treated as non-compliant, and non-compliance is disclosed to an Installer who asks.
Article 8: Suspension and Removal of a Listing
8.1 The Company may suspend or remove a Listing for: failure at re-review under clause 4.3; a material falsehood in the Listing; scope overreach under clause 7.1; an unresolved security vulnerability; misuse of data under the Data Use, Retention and Deletion; resource abuse under clause 7.3; fraud; or breach of the Partner Revenue Share Policy.
8.2 Immediate removal without a cure period is reserved for: a security vulnerability under active exploitation; disclosure or transfer of data in progress; fraud against an Installer or a Buyer; and credential collection. In such a case the Company acts first: suspension of the Listing and revocation of the Application's credentials: and notifies the Publisher with the reasons within twenty-four (24) hours.
8.3 Any other removal follows the Partner Suspension, Termination and Appeals: written notice stating the grounds, a cure period proportionate to the violation: fifteen (15) days for a Listing and scope matter and thirty (30) days for a support failure: and the right to appeal under Article 10. A Publisher that cures within the period is reinstated. A Publisher that does not cure is removed, and the duties in clause 7.6 attach on the removal date.
8.4 Removal is disclosed to the extent an Installer requires: the Listing page states that the Application is unavailable, and each Installer with the Application installed is notified with the reason category (security, policy, or Publisher request) and the Installer's rights under clause 7.5. The Company does not publish investigative detail.
8.5 A removed Publisher may apply again after twelve (12) months, with a new listing review and disclosure of the prior removal. A Publisher removed for disclosure or sale of data, for fraud, or for credential collection shall not apply again, and neither shall its principals under a new entity.
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 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, including a refund owed to an Installer under clause 5.2; 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 and Listings, including a claim by an Installer; (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, including review records, the Install and Uninstall authorization record, the fee record under clause 6.1, and deletion certifications.
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, and except as clause 8.2 provides for immediate removal with notice within twenty-four (24) hours.
11.3 Opportunity to cure. Where a violation is capable of cure, the Developer has the cure period stated in clause 8.3 for the class of violation concerned, and otherwise ten (10) business days from notice, to cure it and to confirm the cure in writing. No cure period applies to a violation described in clause 8.2, 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 a change to the Application or the Listing and suspend the Listing pending review; (c) suspend or remove the Listing and revoke the Application's credentials, in accordance with Article 8; (d) suspend the Account or a program participation, in whole or in part; (e) terminate this document and the Account, with the re-application bar in clause 8.5 where it applies; and (f) exercise any other right or remedy available under this document or at law.
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 publishes or seeks to publish in the marketplace and continues until terminated under this article or until the Developer Agreement terminates, whichever occurs first.
12.2 Termination by the Company. The Company may terminate this document on thirty (30) days' written notice for any reason, and immediately on written notice if the Developer materially breaches this document, engages in fraud, or becomes ineligible to participate. Removal under Article 8 is a termination of marketplace participation under this clause.
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 completed the duties in clause 7.6 for every Installer.
12.4 Effect of termination. On termination: (a) every Listing is removed and marketplace participation ends; (b) the duties in clause 7.6 apply; (c) revenue accrued through the termination date is settled in accordance with the Partner Revenue Share Policy; (d) obligations that arose before termination survive until satisfied; and (e) the Company shall pay amounts owed, less amounts the Company may set off under this document, within thirty (30) days, except amounts held in connection with an open investigation or dispute.
12.5 Survival. The Definitions, Fees and revenue settlement (for accrued amounts), Liability, Indemnification, Enforcement and Appeals (for measures taken before termination), Dispute Resolution, and General Provisions articles survive termination, together with clauses 7.5 and 7.6 until satisfied.
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 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.