Marketplace Submission Terms

Effective: 28 May 2026 Last updated: 28 May 2026

1. Acceptance and definitions

These Marketplace Submission Terms ("Terms") govern the relationship between you ("Publisher," "you," or "your") and Praxa Lab ("Praxa Lab," "we," "us," or "our") with respect to publishing games on the Caputchin marketplace.

In these Terms:

"Caputchin" means the Caputchin product.
"Marketplace" means the Caputchin marketplace at caputchin.com/marketplace.
"Manifest" means a caputchin.json file in a Publisher's repository.
"Game" means a game packaged with a Manifest and listed under the caputchin-game GitHub topic.

You accept these Terms by setting terms_accepted: true in the Manifest of a repository listed under the caputchin-game GitHub topic. Customer use of Caputchin is governed separately by our Terms of Service.

2. License grant

You grant Praxa Lab a worldwide, royalty-free, non-exclusive, sublicensable license to:

Access your Manifest and the Game files it points to.
Host, mirror, and distribute the Game through our infrastructure.
Display your Manifest metadata (game name, description, preview, author block) on the Marketplace.
Continue making previously published versions of the Game available for as long as our customers' integrations depend on them.

You retain all other rights in your code, including the right to publish, distribute, and license it elsewhere.

3. Publisher warranties

By setting terms_accepted: true you represent and warrant that:

You have the right to grant the license in Section 2 (either you own the code and assets, or every component is covered by a license that permits redistribution).
The license field in your Manifest accurately identifies the license that applies to the Game's code and assets.
The Game does not knowingly include code or assets that infringe third-party rights, contain malware, fingerprint visitors, or transmit visitor data to any party.

These warranties are continuous. They apply each time we publish or republish your Game.

4. Approved licenses

Only Games whose license field evaluates to an SPDX identifier on the approved list below are eligible for the Marketplace.

Permissive code licenses

MIT
MIT-0
Apache-2.0
BSD-2-Clause
BSD-3-Clause
0BSD
ISC
Zlib
Unlicense
BSL-1.0 (Boost Software License; not BUSL-1.1, the Business Source License)
NCSA
PostgreSQL
Python-2.0
PHP-3.01
Ruby
TCL
MS-PL
AFL-3.0
MulanPSL-2.0
WTFPL

File-scope weak-copyleft (we host unmodified bundles, so file-scope obligations do not propagate)

MPL-2.0
MS-RL

Asset licenses (for art, audio, fonts bundled into the Game)

CC0-1.0
CC-BY-3.0
CC-BY-4.0
OFL-1.1

SPDX OR and AND expressions are evaluated per the SPDX specification: any branch of an OR must appear above; every branch of an AND must appear above. SPDX exceptions (WITH clauses) and the + (or-later) suffix are not accepted.

First-party copyleft

First-party Games published by Caputchin (the Game's source repository is owned by the caputchin GitHub organization) may additionally declare the strong-copyleft license below. This allowance does not extend to third-party submissions: for our own Games we control the bundle, publish the complete corresponding source, and accept the distributor obligations knowingly, and the sandboxed-iframe embed keeps the Game a separate work from the host page.

GPL-2.0-only (first-party games only)

AGPL and its network-use clause remain excluded for every Game, first-party included.

We may add identifiers to the approved list at any time. We may remove identifiers from the approved list with thirty days advance notice via the Marketplace dashboard. Removing an identifier does not retroactively take down already-pinned bundles using that identifier. The companion page at Marketplace publish errors reference provides background and diagnostic guidance; if it disagrees with the list above, the list above governs.

5. Runtime constraints

We enforce the warranties in Section 3 through technical controls in the environment Games run in. Behaviors a Publisher attempts to ship in violation of Section 3 may not function in production.

You agree not to attempt to defeat or circumvent these technical controls, or to author code that probes for the boundaries of those controls with the intent of exploiting them.

6. Retention of previously published versions

We retain copies of previously published versions of your Game so that customer integrations that depend on a specific version (for security validation or audit purposes) continue to function. You grant us the right to continue making those previously published versions available for as long as customer integrations depend on them, including after you withdraw your Manifest under Section 8.

If a specific previously-published version must be removed for an urgent legal reason (for example a copyright takedown notice), see Section 8.

7. Visitor privacy and telemetry

We do not pass visitor IP, User-Agent, or other visitor-identifying signals into Game code, as described in our Privacy Policy. The Game must not attempt to collect, derive, or transmit any visitor-identifying signal. This is a product invariant, not a configurable concern.

8. Takedown and removal

If you receive a third-party complaint about your Game or wish to remove your Game from the Marketplace:

For a third-party DMCA-shaped notice (someone claiming your Game infringes their rights), send the notice to info@caputchin.com. Our designated agent will process it under standard host-of-content procedures.
For voluntary withdrawal, remove terms_accepted from your Manifest or remove the Manifest entirely. We will stop publishing new versions of your Game. Previously published versions remain available under Section 6.

We may take down any Game we believe in good faith infringes a third party's rights, violates these Terms, or violates applicable law.

9. Termination

You may stop publishing at any time using the withdrawal mechanism in Section 8.

We may suspend or end the publishing relationship if you breach these Terms.

10. Notifications

If your Manifest sets marketplace.author.email, we may use that address to notify you when we are unable to publish your Game. The notification names the failure and links to the relevant fix steps.

To stop receiving these notifications, edit your caputchin.json and do one of the following:

Remove the email subfield from the marketplace.author block.
Change the address to a different value you want notifications to reach instead.
Remove the whole marketplace.author block.

The change takes effect the next time we re-read your Manifest (manually published, or on our next index run).

There is no separate server-side opt-out. Marketplace authors are not Caputchin user accounts; we have no identifier other than the Manifest-declared address to bind a preference to. The Manifest field is the control, and removing it is the unsubscribe action.

11. Disclaimer of warranty and limitation of liability

The Marketplace is provided as is. To the extent permitted by law:

We make no warranty about Marketplace traffic, customer adoption, or commercial outcomes for your Game.
Neither party is liable to the other for indirect, incidental, special, consequential, or punitive damages.
Our total liability to you, if any, is limited to USD $100 in any twelve-month period.

If you are a consumer protected by the Australian Consumer Law or another consumer-protection regime, statutory rights apply on top of these Terms, not despite them.

12. Changes to these Terms

We may update these Terms. Material changes are announced by email to author addresses listed in published Manifests, by a dashboard banner, and on our blog, at least thirty days before they take effect. Your continued maintenance of terms_accepted: true in your Manifest after the effective date constitutes acceptance of the updated Terms. If you do not accept them, remove terms_accepted (or the Manifest) before the effective date.

13. Governing law

These Terms are governed by the laws of Australia. Any dispute will be heard by the Federal Court of Australia.

14. Contact

info@caputchin.com.