Developer Agreement and Rules

4 vues Markdown

The programme's rules live in three places: the agreement you accept, the confirmations you give on each submission, and the decisions moderation makes.

Overview

You accept the Developer Agreement on the application form, and the application cannot be sent until the box is ticked. Its full text lives on its own page and is always read from there.

The agreement states the obligations; the portal enforces them. The three confirmations on every submission, the moderation decisions and the review rules are the working parts of one frame.

This article does not replace the agreement. It shows where each rule meets you in the portal and what it changes.

Prerequisites

Having read the agreement The link on the application form opens the agreement page. The server checks the confirmation as well.

Distribution rights You must hold the right to distribute everything you publish. Third-party content whose licence forbids distribution cannot go in the package.

A reachable support address Buyers need somewhere to reach you, and your profile carries it. Response time is one of the certification criteria.

Verified identity When the operator asks for documents, you upload them to your account. Your product does not enter the queue before they are approved.

Structure

The rules are not all in one place. The table below shows where each one meets you.

Where	What it binds
Developer Agreement	The full text: rights, obligations and termination terms
Application confirmation	Records that you accepted the agreement and the privacy policy
Submission confirmations	Three per product and release: distribution rights, testing, installation documentation
Moderation decision	Requesting changes, cancelling and writing the reason, which you read on the record
Review rules	Your right to answer a review, and how reporting one works

Accepting the agreement does not stand in for the confirmations: you give them again on every submission, because each release is its own commitment.

Walkthrough

Meet the obligations

Read the agreement before applying; the confirmation box gates the form.
Audit what goes in your package: remove any library, theme fragment or image you do not hold the rights to.
Keep installation and configuration documentation where buyers can reach it, which is what you confirm on submission.

Answer the decisions

When changes are requested, read the reason and correct what it names.
A cancelled product carries its reason on the record. You cannot send the same record again; open a new draft from a copy of it.
Retire a product you no longer sell instead of deleting it, so buyers keep their access and the reviews stay.

Work with reviews

You may answer any review on your product, signed with your studio name.
Report a review only when it breaks a rule. The report button is shown to the product's owner alone.
A report takes the review down until a decision is made. Use it for a violation, not for a rating you dislike.

Reference

Distribution rights confirmation Given on every submission. Content you do not hold the rights to is one of the grounds for cancelling a product.

Testing confirmation States that you actually tested the range written in the compatibility section.

Documentation confirmation States that installation and configuration steps are open to the buyer.

Changes requested A correctable decision. The reason is written onto the record and the product can be sent again.

Cancelled The record closes and cannot be resubmitted. A new draft starts from a copy of it.

Review report Only the product's developer can report, and the report returns the review to moderation at once.

Example

Reporting a review does three things at the same moment.

After a report

Review  -> taken down, no longer shown on the product page
Rating  -> recounted, that review no longer counts
Decision -> the review returns to the moderation queue

If the decision does not go your way the review is published again. That is why reporting belongs to a review that breaks a rule, not to one you disagree with.

Pitfalls

Using a report as an appeal

A report silences the review until a decision is made. Removing an honest but negative review this way damages trust in the programme and turns the decision against you.

Content with unclear rights

Dropping a library or an image into the package because you found it online voids the distribution rights confirmation. Verify the source licence before you submit.

The agreement can change

The programme text may be updated. The version in force is always the one on the agreement page; articles summarise it and do not replace it.

Cet article vous a-t-il été utile ?

Merci pour votre retour !

Besoin d'aide supplémentaire ?

Notre équipe d'assistance est disponible 24h/24 pour tout ce que vous ne trouvez pas ci-dessus.

Nous contacter Ouvrir un ticket