Reporting Listings, Users, and Conduct

Effective date: July 29, 2026

Last updated: July 29, 2026

Purpose

Route marketplace concerns to the smallest appropriate reporting path while keeping public forums free of evidence, accusations, and personal information.

Scope

Applies to listing accuracy, user conduct, reviews, transactions, copyright, security, malware, licensing abuse, and anti-leak concerns.

1. Choose the current path

1. Creator support: installation, configuration, or reproducible product problems.

2. Listing Report control: misleading content, impersonation, harassment, spam, prohibited products, suspected copyright issues, malware, licensing abuse, or other listing-specific concerns.

3. Contact Us: general routing, account, payment, delivery, or scope questions when the listing Report control is not the right fit. Use https://legionnetwork.org/index.php?/contact/.

Do not include payment credentials, license keys, passwords, malware files, exploit instructions, or unnecessary personal information in an initial report. Staff may request an appropriate private follow-up method when needed.

2. What to include

1. Public URL or stable listing/user reference.

2. Concise description of the issue.

3. Dates and version where relevant.

4. The specific rule or claim involved.

5. Minimal redacted evidence.

6. Steps already taken, if safe.

7. Requested review or outcome, without assuming entitlement.

3. What not to include

Do not submit or publish:

- account passwords, access tokens, recovery codes, cookies, or API secrets;

- full payment credentials or unnecessary transaction records;

- license keys or activation identifiers;

- personal information not strictly required;

- live malware in a generic attachment field;

- exploit instructions in a public topic;

- private messages unrelated to the issue;

- public accusations intended to pressure an outcome.

Do not send sensitive security or copyright evidence until staff provides an appropriate private method.

4. Public discussion rules

Marketplace Questions must not host:

1. private order information;

2. payment details;

3. license keys;

4. personal information;

5. security exploits or malware;

6. copyright evidence containing private information;

7. public scam accusations during a private investigation.

Staff may close or remove exposed material and direct the member to a private path. That action protects the case; it does not decide its merits.

5. Staff handling

When a report is accepted for staff review, handling may include:

1. acknowledge and classify the report without promising an outcome;

2. restrict access to need-to-know staff;

3. redact or isolate sensitive attachments;

4. preserve relevant marketplace state and audit references;

5. check conflicts of interest;

6. request only the missing evidence needed;

7. separate platform-rule decisions from payment or legal decisions;

8. give the affected user a fair opportunity to respond where safe and lawful;

9. record the outcome and appeal path;

10. escalate urgent security, safety, or legal matters.

No response-time guarantee is approved.

6. Abuse of reporting

Knowingly false reports, fabricated evidence, impersonation, repeat submission after a final decision without new information, threats, retaliation, and public pressure campaigns may result in action. Good-faith reports are not violations merely because staff cannot substantiate them.

Practical examples

- A wrong compatibility claim: Listing or User Report.

- A plugin crash after installation: creator support first.

- A promised deliverable not supplied: Transaction Dispute.

- A copied map owned by the reporter: Copyright or IP Notice.

- An undisclosed credential webhook: Security or Malware Report.

- A low rating with no rule issue: not a report merely because it is negative.

Possible enforcement outcomes

Possible outcomes may include routing guidance, a correction request, evidence preservation, privacy redaction, review action, listing restriction, release hold, account restriction, no action, or referral to an appropriate payment or legal process.

Appeal or review path

Ask for review through the same private contact path with the original reference, claimed error, and new or overlooked evidence.

Published guidance

Start Here: https://legionnetwork.org/index.php?/forums/topic/19-start-here-how-legion-market-works/

Marketplace FAQ: https://legionnetwork.org/index.php?/forums/topic/21-marketplace-faq/

Buyer Safety Guide: https://legionnetwork.org/index.php?/forums/topic/22-buyer-safety-guide/

Creator Safety Guide: https://legionnetwork.org/index.php?/forums/topic/23-creator-safety-guide/

Marketplace Policy Questions: https://legionnetwork.org/index.php?/forums/topic/25-marketplace-policy-questions/