Buyer Safety Guide

Effective date: July 29, 2026

Last updated: July 29, 2026

Purpose

Help buyers evaluate digital products and commissioned services before sharing money, access, or server data.

Scope

Applies to Legion Market listings, service offers, creator support, downloads, license systems, and transaction evidence.

1. Check the listing before purchase

1. Match the resource to your exact platform, version, runtime, proxy, and dependencies.

2. Read what is included and excluded.

3. Compare screenshots and demonstrations with the promised files.

4. Check current version, last update, changelog, support route, license, and known limitations.

5. Confirm any external purchase, account, activation, or paid dependency.

6. Treat “lifetime,” “all versions,” “fully secure,” “guaranteed,” and urgent scarcity claims as questions to verify, not facts to assume.

2. Protect accounts and servers

1. Never send a password, recovery code, API secret, private key, payment credential, or unrelated license key.

2. Use temporary, least-privilege access for installation work.

3. Back up configuration and data before installing or updating.

4. Test unfamiliar code in an isolated environment appropriate to the file type.

5. Review documented outbound connections, licensing checks, analytics, webhooks, commands, permissions, and file changes.

6. Stop if the product requests unexplained administrator access or disables security tools.

3. Understand licensing

1. A purchase gives only the rights stated in the applicable license.

2. Do not share the download with friends, customers, public repositories, leak sites, or resale buyers unless the license permits it.

3. Confirm project/use limits, activation limits, transfer rules, and offline behavior before purchase.

4. If a legitimate activation is blocked, use the creator's private false-positive process and keep the license key out of public posts.

4. Commissioned service safety

1. Put scope, files, milestones, revisions, deadlines, acceptance checks, price, ownership, license, and handoff in writing.

2. Divide large work into reviewable milestones when the agreed payment arrangement supports it.

3. Confirm who supplies third-party assets and who pays for licenses.

4. Use a temporary role instead of a shared owner account.

5. Remove access and rotate exposed credentials after handoff.

5. Keep useful evidence privately

Keep:

- the listing and terms shown at purchase;

- approved scope and changes;

- redacted payment confirmation;

- delivery dates and file/version identifiers;

- support attempts and reproducible errors.

Do not post those records publicly. Provide only the minimum needed through the private follow-up method staff requests.

Warning signs

- pressure to move payment or discussion away from approved records;

- a dependency or activation fee revealed only after purchase;

- copied screenshots or ownership claims that cannot be explained;

- requests for full server, hosting, email, Discord, or payment credentials;

- unexplained outbound traffic, obfuscation, remote commands, or data upload;

- threats over reviews or refund questions;

- instructions to disable antivirus, logging, backups, or licensing checks for unrelated products.

Practical example

If a setup requires three premium plugins, the listing should name them and state that they are not included. Discovering those costs after purchase is a listing/report issue, not something a buyer should reveal through a one-star review containing order details.

How to report a problem

- Support/installation: creator's stated support route.

- Misleading listing or conduct: use the Report control on the affected listing.

- Payment, delivery, or scope conflict: contact the creator through the stated support channel, then use Contact Us for routing if needed.

- Copyright or security concern: use the listing Report control and Contact Us for routing; do not include sensitive evidence or malware in the initial message.

- General routing help: https://legionnetwork.org/index.php?/contact/

Possible enforcement outcomes

Depending on the issue and available authority, staff may ask for redacted evidence, request a listing correction, restrict content, or take account action. Refund, chargeback, and payment outcomes depend on approved terms and the actual processor.

Appeal or review path

Ask for review through the same private contact path. Do not threaten the creator, publish personal information, or recruit public pressure around an active matter.

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/

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

Reporting Listings, Users, and Conduct: https://legionnetwork.org/index.php?/forums/topic/24-reporting-listings-users-and-conduct/