Developer Brand and Trademark Use Policy
Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers and Partners that name, describe, or display anything connected to the Company or the Platform.
Article 1: Introduction and Scope
1.1 This Policy governs the use of the Company's trademarks by Developers and Partners: the limited licence the Company grants, the references a Developer may make without permission, the uses that always require written permission, the quality standards that attach to any permitted use, and the end of the licence when participation ends. The Platform-wide rules for the protection of the Company's marks are governed by the Trademark and Brand Protection Policy; this Policy states the licence and duties for Developers and Partners.
1.2 This Policy controls the use of the Marks by Developers and Partners. On a conflict with the Solution Provider Program or the Integration Certification Policy as to a badge, this Policy controls the visual and naming rules and those documents control who earns the badge. On a conflict with the App Listing Standards as to listing copy, this Policy controls the use of a Mark and that document controls listing quality.
1.3 If a provision of this Policy conflicts with the Terms of Use, this Policy controls for the subject it governs. If a provision of this Policy conflicts with the terms of a program in which the Developer participates, the program terms control for that program. Policies and help pages explain this Policy; they do not amend it, and in any conflict this Policy prevails.
Article 2: Definitions
2.1 Account: the account a person or business establishes with the Company to use the Platform.
2.2 Application: a software application, integration, or service the Developer offers through the Platform or the App Marketplace.
2.3 Company: All About Pawz, LLC, a Tennessee limited liability company.
2.4 Developer: a person or business the Company has accepted to build on the Platform's application programming interface or to participate in a partner program, including a publisher and a solution provider.
2.5 Marks: the Company's trademarks, service marks, trade names, and logos, including: the "Pawz Shop" word mark; the name "All About Pawz" and the name All About Pawz, LLC; the paw logo and any logo lockup the Company issues; the certification mark issued under the Integration Certification Policy; the tier marks under the Solution Provider Program; and the "Built for Pawz Shop" badge for marketplace applications.
2.6 Platform: the websites, applications, and services the Company operates under the name All About Pawz, including aapawz.com.
Article 3: The Limited Licence
3.1 The Company grants the Developer a limited, non-exclusive, non-transferable, revocable licence to use the Marks only as this Policy permits. The licence carries no right to sublicense. Any use beyond this Policy requires the written permission Article 4 describes.
3.2 No implied licence arises from interface access, a partnership discussion, certification, or a marketplace listing. A working integration is not permission to use a logo; certification is not permission to claim an official status.
3.3 The licence terminates automatically when the Developer's participation in the program under which the use was made ends, whether by termination, withdrawal, or expiry of the status on which the use depended. On termination of the licence, all use of the Marks shall cease, subject only to the badge-removal period in Article 7.4.
Article 4: Uses That Require Written Permission
4.1 Each of the following always requires the Company's prior written permission, because each use trades on the Company's identity rather than referring to it: (a) reproduction of the paw logo or any logo lockup, in any medium, at any size; (b) an application, company, or product name that begins with, consists of, or is built on "Pawz," "Pawz Shop," or anything confusingly similar; (c) the words "official," "certified," "endorsed," "authorized," or "partner" applied to the Developer's relationship with the Company, beyond the exact status the Developer holds: a certified category under the Integration Certification Policy, a tier under the Solution Provider Program, or a published marketplace application under the App Marketplace Terms; (d) a domain name, subdomain, or social-media handle incorporating a Mark; (e) paid-search or paid-social use that diverts the Company's brand traffic, subject to the narrow permitted form in Article 8.3; and (f) merchandise, packaging, or signage bearing a Mark.
4.2 A permission, when granted, is specific: the permission names the Mark, the use, the medium, and the term. Permission to use a word mark in descriptive copy is not permission to use the logo; permission for a presentation slide is not permission for a website. An expired permission is no permission, and the use shall come down when the term ends.
Article 5: Nominative Use Without Permission
5.1 A Developer may refer to the Platform by name without permission when all three of the following hold: (a) the reference is necessary to identify the Platform, because the Application genuinely interoperates with the Platform; (b) the Developer uses only so much of the Mark as the reference needs: the words, in plain type, never the logo; and (c) nothing in the presentation suggests sponsorship, endorsement, or authorship by the Company.
5.2 The Developer's own brand shall lead. The Platform's name appears in descriptive copy, subordinate in size and prominence to the Developer's brand: a sentence about compatibility, not a headline.
5.3 By way of illustration of a compliant reference: a fictitious developer, Acme Inc., builds an order-synchronization tool. The site headline reads "Acme Order Sync" in Acme's own branding. In body text, the site states that the tool connects an Acme account to a Pawz Shop seller account and keeps orders, inventory, and tracking numbers in step. The footer states that the tool is built by Acme Inc. and is not affiliated with or endorsed by All About Pawz, LLC. No logo appears, and no status word is claimed. The Platform's name does exactly one job: stating what the tool connects to: and no permission is required.
5.4 By way of illustration of a violating use: the same tool launched under the name "Pawz Shop Order Sync Pro," with the Platform's Mark as the product name in the largest type on the page, an application icon reproducing the paw logo, a headline claiming the tool is the official Pawz Shop synchronization solution, and documentation signed in the Platform's name. Each element states or implies that the Company built or approved the tool, and none is true. The use violates Article 4.1(a), (b), and (c) together, and the cure is to rename the product, remove the logo, remove the status claim, and add the disclaimer in Article 5.5, which produces the case in Article 5.3.
5.5 The disclaimer: a statement that the Application is not affiliated with or endorsed by All About Pawz, LLC: is required wherever a reference could confuse: a marketplace listing, an application-store page, a paid advertisement, and any page where the Platform's name appears in a headline or hero position. The disclaimer is not required inside running descriptive prose where the Developer's brand clearly leads. A close question is resolved in favor of including the disclaimer.
Article 6: Quality Standards for Permitted Use
6.1 Where permission to use a logo or badge exists, the Developer shall use only the assets the Company issues in its brand kit. The Developer shall not redraw, recreate, or take a Mark from a screenshot. The Developer shall not recolor, stretch, rotate, or add a shadow, an outline, or any other effect to a Mark, and shall use the approved lockups without typesetting the word mark in a treatment resembling the logo.
6.2 Clear space around a logo equals the height of the "P" in the lockup, on all sides, at a minimum. A Mark shall not be reduced below the minimum size the brand kit states. A Mark shall not be placed on a busy background, a clashing color, or photography that obscures the Mark. The dark lockup is used on a light background and the light lockup on a dark background, as issued.
6.3 The paw logo shall never appear in an application icon. An icon is read as a statement of who made the application, and the Company did not make the Developer's application. Permission to use the logo under Article 4.1(a) does not extend to an icon.
6.4 A certification or tier badge shall be used whole: the category line is not cropped, the badge is not separated from its year, and the badge is not combined with the Developer's own award graphics in a manner that implies a broader endorsement.
6.5 Every use of a Mark under this Policy is subject to the Company's quality control. The Company may inspect a use on request and may require correction of a use that departs from the brand kit or from this Article. A use the Company directs to be corrected and that is not corrected within the period the direction states is a violation of this Policy.
Article 7: No Implied Endorsement; Badges
7.1 The permitted vocabulary for the relationship is exact and limited to: "works with Pawz Shop" or "integrates with Pawz Shop," stated truthfully and subordinately under Article 5; "Built for Pawz Shop," for a published marketplace application in good standing only; "Pawz Shop Certified Integration," with the categories and year, for a current certification only; and the tier name the Developer actually holds under the Solution Provider Program. Every other formulation: including "official," "recommended," "preferred," "powered by," and "in partnership with," and any presentation of the Developer's support as the Company's support: is prohibited unless the underlying status is actually held and the words match the status exactly.
7.2 "Powered by" is prohibited in particular. An Application that reads Platform data is powered by the Developer's own code; a "powered by" claim states Company authorship of the mechanism and is false.
7.3 A marketplace Application shall make the publisher relationship unmistakable: the listing and the Application's own information page state plainly that the Application is built and supported by the named publisher, not by All About Pawz, LLC: as the App Marketplace Terms make the publisher the seller of the Application, this Article makes the branding state the same fact. An Installer who believes the Installer bought a Company product has been misled, and the publisher bears the responsibility.
7.4 Badge rules are as follows. (a) The certification badge is governed by the Integration Certification Policy: usable only while certified status is current, only for the categories passed, in the issued form: "Pawz Shop Certified Integration," with the categories and the year: and linking to the Application's directory listing. (b) A tier badge is usable only while the tier is held; a downgrade ends the right to display the badge. (c) The "Built for Pawz Shop" badge is available to a published marketplace application in good standing and links to the Application's marketplace listing. (d) Every badge use comes down within five (5) business days of suspension, revocation, downgrade, expiry, or delisting, whichever first ends the status. Display of an unearned or expired badge is deceptive conduct under the Partner Code of Conduct and a listing violation under the App Listing Standards. The five (5) business day period runs from the Company's notice; failure to update a site by day five is a new violation, not a continuation of the earlier one.
Article 8: Prohibited Uses
8.1 A Developer shall never use a Mark: (a) on deceptive, unlawful, or adult content; (b) in a manner that implies the Company warrants, guarantees, or is liable for the Developer's Application; (c) to register a trademark, domain, or handle confusingly similar to a Mark: a permission under Article 4.1(d) is a licence to use, never a transfer, and the Company may require transfer or cancellation of an unapproved registration as a condition of continued interface access; or (d) in a comparative claim that misstates the Platform, including a claim to be the only integration of a kind where the claim is not true.
8.2 A Developer shall not state or imply that the Developer handles the Company's money. Payment for marketplace transactions moves through the Company's payment path; a Developer shall not state that the Developer processes Pawz Shop payments and shall not display a Mark on a checkout flow, because each implies custody of buyer funds the Developer does not hold. The Developer describes what the Application actually does with orders and payouts.
8.3 Paid search on the words "Pawz Shop" is permitted only where the advertisement names the Developer as the advertiser in the headline or first line, links to the Developer's own domain, and does not imitate the Company's site, logo, or voice. An advertisement that could be read as the Company's own advertisement: no advertiser named, presented in the Company's branding: is diversion and is prohibited.
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 Policy, 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 Policy shall not exceed the greater of (a) the amounts the Developer paid to the Company under this Policy 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 Policy; (b) liability for fraud or willful misconduct, including trademark infringement by the Developer; (c) amounts owed for Orders, fees, chargebacks, or refunds under the Company's documents; 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 Policy, including an unauthorized or misleading use of a Mark; (b) the Developer's Applications, services, listings, or content; (c) the Developer's violation of any law or of the rights of any person, including the trademark rights of a third party in a name the Developer chose; and (d) taxes for which the Developer is responsible under the Company's documents.
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 Policy and of the licence in Article 3.
Article 11: Enforcement and Appeals
11.1 Investigation. The Company may investigate any suspected violation of this Policy. The Developer shall cooperate with an investigation and shall produce the records this Policy requires the Developer to keep. Evidence of a use: a screenshot, an archived page, an advertisement copy: is preserved with the violation record.
11.2 Notice and takedown. A first violation is addressed by a written takedown notice identifying the offending use, the rule violated, and the fix required, with a ten (10) day cure period under the Partner Suspension, Termination and Appeals. Correction within the period closes the matter, recorded.
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. Continued misuse after notice, and a repeat violation of the same rule within twelve (12) months, receive no further cure period and escalate by one measure under the Partner Suspension, Termination and Appeals, which may include credential revocation, listing removal, or termination of the Developer relationship. A counterfeit badge, and a false official-status claim maintained after notice, are treated as willful. No cure period applies where misuse is actively misleading Buyers or Sellers at scale: including an application presented as official that collects Seller credentials: in which case the Company may suspend first and give the cure notice at the same time. The cure period is a grace for a good-faith mistake, not a licence to infringe for ten (10) days, and nothing in this Policy limits the Company's trademark remedies, including injunctive relief, damages, and recovery of a confusingly similar registration.
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 removal of the offending use; (c) remove or suppress a listing or content; (d) suspend the Developer's credentials or program participation, in whole or in part; (e) terminate this Policy, the licence in Article 3, and the Account; and (f) exercise any other right or remedy available under this Policy 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 Policy takes effect when the Developer is accepted into a developer or partner program and continues until terminated under this Article.
12.2 Termination by the Company. The Company may terminate this Policy, the licence in Article 3, and the Account on thirty (30) days' written notice for any reason, and immediately on written notice if the Developer materially breaches this Policy, engages in fraud, or becomes ineligible to participate.
12.3 Termination by the Developer. The Developer may terminate this Policy on thirty (30) days' written notice to support@aapawz.com, provided the Developer has no investigation outstanding.
12.4 Effect of termination. On termination: (a) the licence in Article 3 ends and all use of the Marks shall cease under Article 3.3; (b) obligations that arose before termination: including indemnification obligations and liability for a use made before termination: survive until satisfied; and (c) the Company shall disburse amounts owed, less amounts the Company may set off under the Company's documents, within thirty (30) days, except amounts held in connection with an open investigation or dispute.
12.5 Survival. The Definitions, Liability, Indemnification, Enforcement and Appeals (for measures taken before termination), Dispute Resolution, and General Provisions Articles survive termination.
Article 13: Dispute Resolution
13.1 Any dispute arising out of or relating to this Policy, or to the relationship it governs, is governed by the Dispute Resolution Policy, which is incorporated into this Policy by reference.
Article 14: General Provisions
14.1 Amendments. The Company may amend this Policy by posting the amended Policy 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 obligations takes effect thirty (30) days after notice; other amendments take effect on posting. Continued use of a Mark 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 Policy, including a request for permission under Article 4, 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.
14.3 Governing law. This Policy 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 Policy 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 Policy 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 Policy, 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 Policy, the licence in Article 3, or any right or obligation under either without the Company's prior written consent, and an assignment without consent is void. The Company may assign this Policy 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 Policy 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 Policy shall not be construed against a party as its drafter. The English-language text controls over any translation.