Developer Agreement

This agreement is between you — the developer selling on the Paradox Labs marketplace — and Paradox Labs. You accept it once, before you can use the seller portal or the seller API.

It is in addition to, not instead of, our Terms of Service and Privacy Policy. Where this document is silent, those apply. Where it says something more specific about selling, this one governs.

You are an independent developer using our platform. You are not our employee, contractor, agent or partner, and nothing here creates a joint venture. You decide what to build, what to charge for it, and who to support.

That cuts both ways. Your plugins are yours; we do not claim ownership of them by hosting them. And what you do with your customers is yours: we are not responsible or liable for your acts or omissions, and your customers are told plainly on every product page that they are buying from you.

You are responsible for your own tax and any registration your country requires of somebody selling software. We do not withhold, report or file anything on your behalf, and we cannot give you tax advice.

$10 a month, for access to the platform. That is all. We do not take a percentage of your sales, a listing fee, a per-download fee or a cut of anything else you earn here — not now and not on any plan.

Your customers pay you. Sales are charged on your own connected payment account, and the money lands there rather than with us and later being passed on. Your payment processor’s own fees are between you and them.

The membership is what keeps your listings on sale. If it lapses, new sales stop until it is paid again — but everyone who already bought from you keeps their downloads and their licences. A customer never loses what they paid for because a subscription expired.

You agree to comply with our Terms of Service and Privacy Policy at all times while using the platform, the marketplace, our APIs, our licensing system, our Discord and anything else Paradox Labs operates — as they stand at the time, including changes we publish.

That includes, and is not limited to:

• →Not uploading anything that is malicious, obfuscated to hide what it does, or that collects data from a server owner's players without their knowledge.
• →Not selling work that is not yours to sell — no reselling somebody else's plugin, no code you do not have the rights to, no assets you have not licensed.
• →Describing your products accurately: what they do, what they need, and what they do not do.
• →Handling any personal information you receive from your customers lawfully. For your own sales you are the data controller, not us.
• →Not using the platform to route customers off it to avoid the membership, and not using our name to imply we endorse or back your product.

Breaking this is grounds for us to take a listing down, suspend your ability to sell, or end this agreement — section 10.

Any plugin or build you upload may be installed and run on our test servers so we can verify that it works, that it is compatible, and that the code does what the listing says. We may read the source, compile it, run it under Oxide or Carbon, and exercise it against a test load.

This is why the review queue exists: an untrusted seller’s build waits for a person to do exactly that before it reaches a customer. Once we have run enough of your work to trust your judgement, your uploads publish on their own — and we may still test any of them afterwards.

This is our review, and it is separate from the test server you are issued and run your demos on — that is section 6.

Review is a compatibility and sanity check, not a warranty. Approving a build does not make it our product, does not make us responsible for what it does on somebody else’s server, and does not shift your liability for it onto us.

A test server is an optional add-on at $10 a month, taken from your membership page. We used to issue one to every developer; a free box per seller does not hold up against a $10 membership, so the devs who want one take one and nobody else pays for a machine they never log into.

If you take one, use it. Test your plugins on it, and leave them installed and running so that customers can join and try your work before they decide whether to buy it. It is at testserver.paradoxlabs.dev, and you sign in to it with Discord.

That is the point of it. A Rust plugin is hard to judge from a screenshot and a paragraph, and a buyer who can walk onto a server and use the thing is a buyer who asks for fewer refunds — which is money and time back in your pocket, since the refunds are yours (section 7).

• →Keep your listed plugins installed on it and working, for as long as you keep the add-on.
• →Keep them current: when you push a new build, put it on the test server too, so what a customer tries is what a customer buys.
• →It is a demo and a test bed, not somewhere to run a community, resell access, or host anything unrelated to your listings.
• →Do not put anything on it you are not licensed to distribute, and do not use it to give away paid work.

We run the box and keep it up; you look after what you put on it. Cancelling the add-on ends this section for you — nothing else about your account changes, and your listings stay exactly where they are. Anything at all about the test server, including if it is down or you need something installed on it, goes to discord.paradoxlabs.dev, where a person will answer.

You are liable for your own refunds and your own disputes. A customer who bought your plugin bought it from you: the money went to your account, and the refund comes out of it. The same is true of a chargeback, a payment processor’s dispute, and any fee that comes with one.

Refunds must follow the Paradox Labs Terms of Service. The refund rules in section 7 of those terms are the floor for every sale on this platform — what qualifies, what does not, and the window a customer has to ask. You may be more generous than that. You may not be less.

• →Answer refund requests within a reasonable time. Ignoring them is a breach of this agreement, not a way of declining them.
• →When you refund, the licence goes with it — our system revokes it, so the customer cannot keep using what they were paid back for.
• →Tell us if a dispute is heading somewhere we should know about. We would rather hear it from you than from a chargeback.

We may issue a refund ourselves, or revoke a licence, where we are required to by law or a payment processor, or where a customer is plainly owed one and cannot get an answer from you. We will tell you when we do, and we would much rather not have to.

You indemnify us against claims arising from your products, your sales and your handling of your customers, as set out in the Terms of Service.

You can give away your own work, and only your own.Your developer portal will give a free copy of any plugin you sell to anybody with an account here. They get the download, the licence key and the notification exactly as a paying customer does; it simply costs them nothing and pays you nothing. The button reaches your catalogue and no one else’s.

A free copy is a sale in every other respect. The licence terms apply to it, the seat limit applies to it, and section 7 applies to it — you are still the one who answers for the plugin you gave away.

There is a limit on how many copies the button gives out in a day. It is generous, and it is there so that a loop or a mistyped script cannot send a thousand licence keys out in your name before anybody notices. If you are running a promotion bigger than that, open a developer ticket and say so — we would rather set it up with you than have you find the limit in the middle of it.

Discount codes are generated at random, by us. You cannot mint one yourself, and neither can we make one that says a particular word on request as a matter of course. If you would like to run a special promotion — a launch discount, a seasonal offer, a free run of something — open a developer ticket in our Discord and ask a founding member. We will generate a code for you and tell you what it does and how long it lasts.

A discount on your product comes out of your payment, not ours, because the money goes to your account and never passes through us. We will say so plainly before we issue a code, and we will not issue one against your products without your agreement.

We may grant a licence to one of your products ourselves where a customer is owed one: a problem on our side, a server fault, a support case where giving somebody a copy is the fair answer, or to settle a complaint. This is the same mechanism you have and it is used sparingly. It costs you no money — no refund is taken from you and no payout is reversed — and we will tell you when we do it.

You confirm that everything you list is yours to sell, that it does not infringe anybody’s rights, and that you have the licences for any third-party code or assets inside it. If somebody makes a credible claim otherwise, we may take the listing down while it is sorted out.

Keep your own backups. We store your builds so we can serve them, but the copy of record is yours.

You may stop selling here whenever you like: unlist your products and cancel your membership. We may suspend or end your selling access for a breach of this agreement or of our terms, for a payment processor closing your account, or where the law requires it.

We may also archive your seller account, or one of your products. Archiving is lighter than ending your access and is usually housekeeping — an account that has not sold anything in a long time, a duplicate, a listing you asked us to take down. An archived account comes off our seller lists and everything under it comes off the store; an archived product comes off the store on its own. Nothing is deleted: your builds, your payouts, your history and your customers’ licences are all untouched, and restoring puts it back exactly as it was. We will tell you when we archive something of yours, and we will restore it on request unless we have told you why we will not.

Either way, customers who already bought keep their downloads and their licences, and you stay responsible for refunds and disputes on the sales you already made. Sections 2, 5, 7, 8 and 9 survive the end of this agreement.

If we end your access — or archive your account — for something other than a serious breach, you may appeal within 14 days of the deactivation or the archiving through discord.paradoxlabs.dev.

We may change this agreement. When a change is substantive — the fee, what we may do with your uploads, who carries a refund — we will ask you to agree again before you can carry on selling, and we record which version you accepted and when. Small corrections are published without asking, and the date at the top tells you when it last changed.