ThemeGet
Page

Marketplace Rules

1. Seller eligibility

  • Use a real account and provide accurate seller and payout information.
  • Respond to ownership, security and support verification requests.
  • Do not create replacement accounts to avoid a warning, reserve, rejection or suspension.

2. Ownership and licensing evidence

  • The seller must have created the product or possess written commercial distribution rights.
  • Every included third-party component must have a licence compatible with resale and distribution inside the product.
  • Keep source files, invoices, licence certificates, contributor agreements and permission records. The marketplace may request them before or after publication.
  • Open-source components must retain notices and comply with attribution, source-disclosure or copyleft obligations where applicable.

3. Prohibited products and content

  • Nulled, cracked, leaked, pirated, copied or stolen themes, plugins, scripts, applications, source code or licence keys.
  • Malware, ransomware, spyware, backdoors, credential theft, phishing kits, destructive code or concealed remote-control functions.
  • Tools whose primary purpose is bypassing licences, access controls, payments, platform security or another person’s account.
  • Fake payment proof, counterfeit documents, stolen accounts, spam systems, fraudulent traffic, fake engagement or review manipulation.
  • Products that unlawfully use a person’s identity, confidential information, copyrighted material, trademark, logo, brand name, screenshot or trade dress.
  • Content that is illegal, exploitative, hateful, threatening, sexually abusive or designed to facilitate serious wrongdoing.

4. Listing accuracy

  • Use an original title, description, thumbnail and preview that accurately represent the delivered package.
  • State the product type, platform, current version, required software, compatibility, files included, licence scope and support period.
  • Do not use false scarcity, fake discounts, fabricated sales, copied reviews, unsupported performance claims or misleading “official” branding.
  • External demo links must use HTTPS and must not redirect users to malware, unrelated advertising or payment outside the approved checkout.

5. Package quality and security

  • Upload a complete, working ZIP without passwords that prevent review.
  • Include installation instructions, dependencies and licence notices needed for lawful use.
  • Do not hide dangerous behaviour through encryption, packing or obfuscation. Reasonable minification or source protection must not prevent security review.
  • Patch reported critical vulnerabilities promptly and notify the marketplace when a published package is unsafe.

6. Pricing, sales and payments

  • Use the marketplace checkout for marketplace transactions. Do not redirect buyers to undisclosed payment channels to avoid commission or verification.
  • Do not submit duplicate, recycled or fabricated transaction references.
  • Sales and ratings must come from genuine approved orders; self-purchases, coordinated manipulation and paid fake reviews are prohibited.
  • Chargebacks, refunds and confirmed fraud may reverse download access and seller earnings.

7. Buyer conduct

  • Do not redistribute, leak, mirror or resell a product unless its licence expressly allows that activity.
  • Do not threaten sellers, publish private information or misuse disputes and reviews to demand benefits outside the listing.
  • Report security or infringement concerns privately through support before publicly sharing exploit details or protected files.

8. Support and updates

Sellers must provide only the support and updates promised on the listing, but must respond reasonably to delivery failures, missing files, serious defects, malware reports and ownership disputes. Buyers must provide enough information to reproduce a reported problem.

9. Enforcement

Possible actions include requesting evidence, editing or rejecting a listing, delaying publication, quarantining a file, withholding a payout, refunding an order, removing a product, restricting downloads, issuing a warning, suspending an account or permanently terminating repeat or serious violators. Enforcement may consider intent, harm, history, cooperation and legal requirements.

10. Reporting a violation

A report should identify the product URL, the specific rule or right affected, supporting evidence and the reporter’s contact details. Copyright reports should also identify the protected work and the reporter’s authority. Knowingly false, abusive or retaliatory reports may result in account action.

Contact

Questions, requests, complaints or legal notices may be sent using the details below.