Developer Agreement

Effective August 20, 2026 · version 2026-08-20

This agreement is between you (the developer) and zlarp. It covers the simulator apps you build for zlarp. You accept it when your developer account is opened, and again for each app you deliver — the per-app acceptance is the one that counts if a specific app is ever disputed. It sits on top of the Terms of Use, which apply to you as a user of zlarp too.

1. How we work together

zlarp builds and sells its own simulator apps, and works with developers on a project basis to build them. For each project we agree in writing what you will build and on what terms before the work starts. This agreement covers every project; it does not by itself commission any work.

zlarp is the seller and the licensor of every app on the site. We list it, host it, sell it, take the payment, support the people who subscribe to it and market it. Listings are zlarp's and do not name you. You are not a party to any subscription, and the obligations a seller owes a consumer are ours, not yours.

2. Accurate details

The listing material you deliver (name, subtitle, description, screenshots, category) must describe what the app actually does. No claims the app cannot deliver, and no borrowed screenshots.
Your developer profile must identify you truthfully.
You keep a working contact with us, and you keep it working. If we cannot reach you about an app you built, we may take it down.
We do not ask for identity documents or company records to open a developer account. That is a convenience, not a waiver: if a legal notice, a tax obligation or a payment for your work requires us to verify who you are, we will ask, and we can hold a payment or an app until you answer.

3. Delivery and maintenance

You deliver the app as agreed for the project, and you fix defects in it for as long as the project terms say. Subscribers come to zlarp for support, and we come to you when a question is really about the code.

If you are no longer able to maintain an app, tell us before you stop, so we can decide whether to keep it on sale, hand it to another developer or retire it. Leaving an app on sale that you know no longer works, without telling us, is a violation of this agreement.

4. The licence you grant us

For each app you deliver, you grant zlarp a worldwide licence, paid for as section 6 describes, to store, build, host, run, display, transmit, distribute, sell and sublicense the app and its listing material (name, icon, screenshots, description), for as long as zlarp offers the app. That includes the technical steps it requires: unpacking your bundle, injecting the platform shell described in our documentation, generating icons, deploying it, and serving it through our gateway. A project's written terms may assign the app to zlarp outright instead; where they do, they take precedence over this section.

The licence covers marketing zlarp too — showing the app's icon and name in a shelf, a search result, an email, an ad or a screenshot of the site. Subscribers who hold an active period keep access under it until that period ends, even after the app is retired.

We claim nothing in your code beyond what selling, running and marketing the app needs. The licence above, and whatever the project's written terms add, is the whole of what you give us.

5. What you may build

Every app must comply with the Acceptable Use Policy. In short: nothing malicious, deceptive or unlawful; no collecting user data beyond what the app reasonably needs; no code that tries to escape the platform shell or defeat the entitlement gateway.

Attempting to unregister, replace or scope around the platform service worker, to cache an app for offline boot, or otherwise to bypass the gateway is a direct violation — those mechanisms are what make a subscription mean anything.

You must have the right to deliver everything in the app: code, assets, fonts and libraries, under terms that allow zlarp to use them as section 4 describes.

6. Payment for your work

What zlarp pays you for a project, and when, is agreed in writing before the project starts. It can be a fixed fee, a royalty (a percentage of what zlarp takes in from sales of the app you built), or both. A royalty is zlarp paying you for your work out of its own revenue: the buyer pays zlarp, and zlarp is the seller either way. This agreement does not set a rate, a share or a schedule, and nothing on the site should be read as one. Taxes on what you are paid are yours to handle.

7. Review, removal and suspension

We may review any app at any time and may change, remove or suspend one at our discretion, including for security, legal, quality or commercial reasons. We can take an app out of the store while we fix or review it; existing subscribers keep access in the meantime. A suspension ends access for everyone.

We will tell you why, and you can respond through @zlarpofficial.

8. Ending the relationship

Either of us can end this agreement at any time by telling the other. Projects already agreed are finished or wound down on their own terms. Apps already delivered stay licensed to zlarp under section 4, so subscribers are not cut off; sections about payment for work already done, the licence, and liability survive.

9. Contact

Questions about this agreement? Message @zlarpofficial on Telegram.