Legal

Content Policy

What you may publish on Projonexa Developers Console, including Software, Hardware, and Hybrid standards, what is prohibited, and how project review works.

Last updated: 6 September 2026

1. Purpose

This Content Policy sets publishing standards for projects submitted through Projonexa Developers Console. It supplements the Terms of Service. Submit-time confirmations are summarized in Listing Declarations. If this Policy conflicts with the Terms on commercial, account, fee, or platform rules, the Terms control.

2. Allowed content

You may submit original, lawful developer projects that fit Console categories, Software, Hardware, or Hybrid (both), including web and mobile apps, AI/ML, IoT, embedded systems, research, and related technical work, provided they are accurately described, reasonably documented, and ready for review. Projects must not mislead buyers about features, ownership, license terms, or hardware condition and inclusions.

3. Software projects

For Software-focused listings, you must ensure:

  • The project runs as described, with a working demo reviewers can access
  • Source repository (and any packaged archive) matches what the listing promises
  • Documentation and README are sufficient for a competent buyer to understand and set up the project
  • Tech stack, features, and “what’s included” are complete and not exaggerated
  • No malware, backdoors, or intentionally harmful behavior (see Safety)

4. Hardware projects

For Hardware-focused listings (including saleable prototypes), you must ensure:

  • Accurate description of working condition, components, quantity, and what is included
  • Prototypes are verified as working as claimed before handover or shipping, within reasonable professional care
  • No counterfeit or intentionally misrepresented hardware
  • Essential parts listed as included are actually provided
  • Firmware or companion tools, if provided, follow the same safety rules as Software

Defective or misrepresented hardware may result in withheld payouts, cost recovery, and other remedies under the Terms, Hardware prototypes.

5. Hybrid projects (Software + Hardware)

Hybrid listings must satisfy both Software and Hardware standards for the respective parts of the project. Do not use a strong software demo to overstate incomplete hardware (or the reverse). Admin panels, live portals, and hardware prototypes, when included, must each be described and deliverable as claimed.

6. Submission requirements

As applicable, submissions should include:

  • Complete project details and documentation
  • A proper working demo
  • A demo URL and demo login credentials so reviewers can verify claims
  • Clear licensing and ownership information
  • For hardware or hybrid: accurate working condition, components, and inclusions
  • When an admin panel is offered and deployed: admin panel live link and reviewer credentials as requested in the Console
  • Any other materials Projonexa requests to assess quality and authenticity

7. Safety and malware

Projects must not contain malware, ransomware, credential stealers, cryptominers installed without clear disclosure and consent, intentionally harmful scripts, or deceptive security threats. This applies to source code, packaged archives, demos, firmware, flashing utilities, and companion apps for Software, Hardware, and Hybrid listings.

Educational security tooling must be clearly labeled, lawfully intended, and must not ship weaponized payloads against third parties. Projonexa may reject or remove listings that create unreasonable risk to buyers, reviewers, or the platform.

8. Accurate description and deliverables

Titles, summaries, features, tech stacks, galleries, demos, pricing, “what’s included,” source access, admin panel claims, and hardware details must be accurate and not misleading. Demos should reasonably reflect the packaged deliverable. If something is incomplete, experimental, or unavailable, say so clearly in the listing.

  • Software: Claimed features must work as described under the stated setup.
  • Hardware: Condition, components, and inclusions must match what is shipped or handed over.
  • Hybrid: Accuracy obligations apply to both software and hardware portions.

9. Prohibited content

You may not submit or promote content that includes:

  • Illegal material or material that facilitates unlawful activity
  • Malware, intentionally harmful code, or deceptive security threats
  • Stolen, scraped, or otherwise infringing intellectual property
  • Hate, harassment, or discriminatory content
  • Adult sexual content or pornography
  • Spam, scam tooling, or misleading commercial claims
  • False claims about functionality, authorship, or rights, including misleading claims about hardware prototypes

10. Licensing and originality

You must have the rights needed to publish and license the project as submitted. Do not upload third-party code, assets, designs, or trademarks without permission. See the Copyright Policy for ownership, notices, and takedowns.

11. Review and resubmission

Projects are reviewed with AI-assisted checks and human reviewers. Approval is required before listing. If rejected, you may be invited to fix issues and resubmit with a clear explanation of what changed. Incomplete or unclear resubmissions may be rejected again.

12. Enforcement

Violations may result in a balanced enforcement path: warning, restriction of publishing rights, then suspension or termination. The registration fee remains non-refundable under the Terms when accounts are restricted, suspended, or closed for policy breaches. Commercial remedies for defective, incomplete, or misrepresented hardware prototypes, including withholding of payouts, cost recovery, and administrative penalties, are governed by the Terms of Service.

13. Relationship to Terms

This Policy works with Listing Declarations, the Community Guidelines, and the full suite on the Legal overview.

Contact

Questions about this document: support@projonexa.com.