This policy forms part of the CodeElveza marketplace agreement. Mandatory rights under applicable law are not excluded.
Effective date: 2026-07-30 Last reviewed: 2026-07-30
This Acceptable Use Policy protects buyers, sellers, infrastructure, payment partners and the wider public. It applies to products, uploads, demos, messages, reviews, APIs, downloads, support interactions and all other use of CodeElveza.
1. Prohibited software and content
- Malware, ransomware, destructive payloads, botnets, rootkits, credential theft, cryptojacking or code designed to gain unauthorised access.
- Spyware, stalkerware, keyloggers, covert recording or tracking, or surveillance tools marketed or configured for unlawful use.
- Phishing kits, payment-card theft, account-takeover tools, fake login pages or products designed to deceive users about identity or purpose.
- Pirated, cracked, nulled, leaked or stolen software; licence bypasses; counterfeit products; or material that infringes intellectual-property rights.
- Tools primarily intended for denial-of-service attacks, exploitation without authorisation, evasion of lawful controls or concealment of malicious activity.
- Products that unlawfully discriminate, facilitate abuse, exploit children, promote terrorism, traffic illegal goods or otherwise violate applicable law.
- Misleading products, fabricated demonstrations, hidden subscriptions, undisclosed advertising, unauthorised telemetry or deceptive installation behaviour.
- Personal data, confidential source code, secret keys, credentials or datasets uploaded without a valid legal basis and appropriate protection.
2. Security and testing tools
Legitimate defensive-security, education and authorised testing tools may be accepted where their lawful purpose, safeguards, documentation and limitations are clear. Sellers must not include real stolen credentials, active malicious infrastructure or instructions primarily aimed at unauthorised harm. CodeElveza may require additional review or refuse high-risk products.
3. Prohibited platform conduct
- Attempting to access another account, private file, administrator area, database or system without authorisation.
- Scanning, probing, load testing or exploiting CodeElveza without written permission, except through an approved vulnerability-disclosure process.
- Circumventing download limits, payment verification, licence controls, moderation, seller review, geographic restrictions or security mechanisms.
- Automated scraping, harvesting, bulk messaging or API use that is unauthorised, excessive or harmful.
- Manipulating prices, orders, commissions, payouts, rankings, views, ratings, reviews, refunds or chargebacks.
- Impersonation, harassment, threats, hate, doxxing, spam, extortion or publication of another person’s confidential information.
- Using CodeElveza to facilitate fraud, money laundering, sanctions evasion, tax evasion or other unlawful financial conduct.
- Interfering with service availability, introducing malicious code or placing an unreasonable load on the platform.
4. Responsible disclosure
Report suspected vulnerabilities privately to security@codeelveza.com with clear reproduction steps and avoid accessing unnecessary data, disrupting services or publicly disclosing an unresolved issue. Authorisation for testing must be obtained in advance unless a published disclosure programme states otherwise.
5. Enforcement
Depending on severity and risk, CodeElveza may warn the user, request changes, block a file, remove a listing, restrict downloads, hold funds, cancel transactions, suspend or terminate accounts, preserve evidence, notify affected users or report conduct to payment partners or competent authorities. Emergency action may occur before notice where necessary to prevent harm.
6. Reporting and appeals
Report violations to legal@codeelveza.com with the relevant URL, account or order information and supporting evidence. A user affected by enforcement may submit a reasoned appeal. CodeElveza may decline repetitive, abusive or unsupported appeals.
Database record last updated August 1, 2026. Configure the legal identity and contact fields under Admin → Settings before public launch.