Creator Safety Guide

Effective date: July 29, 2026

Last updated: July 29, 2026

Purpose

Help creators protect their work, accounts, customers, and reputation without using abusive licensing or retaliation.

Scope

Applies to listing preparation, release delivery, support, licensing, commissioned access, suspected leaks, reviews, and private report evidence.

1. Protect the creator account

1. Use a unique password and available account-security controls.

2. Do not share the owner account with team members.

3. Give collaborators only the access needed for their role.

4. Remove access when a collaboration ends.

5. Keep signing keys, upload credentials, payment credentials, and source repositories out of listing files and support messages.

2. Prepare releases safely

1. Build releases from a known source revision.

2. Remove secrets, customer data, internal logs, and development-only files.

3. Record version, file hashes, build inputs, dependencies, and a concise changelog privately.

4. Test installation and upgrade in a clean environment.

5. Keep a recoverable copy of each published release and its license terms.

6. Treat an unexpected binary, outbound connection, or dependency as a stop condition until explained.

3. Use licensing proportionately

1. Tell buyers what a license check does before purchase.

2. Collect only what is needed for the stated license purpose.

3. Provide a private method to resolve activation errors and false positives.

4. Do not harvest credentials, secretly administer a server, delete files, disable unrelated services, or punish players.

5. Do not publish a suspected leaker's identity, IP address, purchase record, server data, or personal information.

6. Support legitimate transfers when the published license permits them.

7. Licensing and customer-data practices must follow applicable Legion privacy requirements and law.

4. Handle commissioned access

1. Ask for a temporary account or scoped token, not a permanent owner password.

2. State what systems and data will be accessed.

3. Keep customer information out of local test fixtures and screenshots.

4. Record handoff, remove access, and return or delete customer material under the approved process.

5. Report an accidentally exposed credential privately and ask the customer to rotate it. Do not quote or test it.

5. Respond to support and reviews

1. Keep the support channel current.

2. Separate reproducible support issues from review moderation.

3. Do not pressure a buyer to change a rating.

4. Answer factual criticism with evidence and a fix where possible.

5. Report a review only for a policy reason such as fabricated experience, conflict, private information, threats, or irrelevant content.

6. Do not retaliate through license cancellation, service denial, or public accusations merely because feedback is negative.

6. Report suspected leaks privately

1. Preserve the minimum lawful evidence.

2. Do not download from a leak site when doing so creates additional risk or infringement.

3. Use the Report control on the affected listing or Contact Us at https://legionnetwork.org/index.php?/contact/ for private routing.

4. Identify the product/version, the location, why distribution appears unauthorized, and any non-sensitive matching evidence.

5. Allow staff to assess authorization, open-source rights, transfer claims, false positives, and privacy risk before action.

Practical example

A license server sees two activations after a hosting migration. The safe response is to pause only the disputed activation, contact the buyer privately, and offer a reset/review. Remotely deleting the server or posting the buyer's IP address is prohibited.

How to report a violation

Use the Report control on the affected listing or Contact Us at https://legionnetwork.org/index.php?/contact/ for routing. Do not place personal information, license keys, or sensitive leak evidence in a public post.

Possible enforcement outcomes

Possible outcomes may include a correction request, listing or release hold, licensing-practice review, support restriction, review moderation, account restriction, or legal escalation. Legion does not promise recovery of leaked copies.

Appeal or review path

Ask for review through the same private contact path with the existing reference and non-sensitive evidence.

Published guidance

Creator and Listing Guidelines: https://legionnetwork.org/index.php?/forums/topic/20-creator-and-listing-guidelines/

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

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

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