Author & Seller Guidelines

YTL is built for launch-ready digital products that give buyers a real starting point. Each listing should have clear buyer value, working core functionality, and honest documentation.

• Apps and SaaS kits
• Source code projects
• Website templates
• UI kits and design systems where applicable
• Plugins and extensions
• AI tools and automation kits
• Launch-ready business tools
• Developer utilities

Buyers should be able to understand what they are getting and set up the product without hidden surprises.

• The product must work as described in the listing
• The product must be reasonably complete for its stated purpose
• Setup instructions must be clear and accurate
• Hidden paid services, APIs, or dependencies must be disclosed
• Products must not contain malware, backdoors, credential stealers, or exploit kits
• Products must not include stolen code or assets
• Screenshots, demos, and claims must reflect the actual product
• License expectations must be stated clearly
• Code should be maintainable and structured for the target audience

• Product title and short description
• Full description with honest scope
• Category and tech stack
• Feature list and system requirements
• Included files and folder structure overview
• Installation and setup guide
• Screenshots or preview media
• Demo link when available
• Version number and changelog
• Support scope and response expectations
• License options and limitations
• Known limitations and unsupported use cases
• Third-party dependencies and external services
• Refund-relevant details such as setup complexity or missing integrations

• Clean, understandable project structure
• No secrets, API keys, or production credentials in source files
• No malicious scripts or hidden remote execution
• No obfuscated code unless clearly justified and documented
• No unnecessary tracking beyond what is disclosed
• Project must build or run as documented
• No missing core files required for basic use
• Dependencies must not conflict with stated license terms
• Environment variable examples must be provided
• README or equivalent documentation must exist
• Basic security defaults for auth, input handling, and configuration

• README with project overview
• Installation guide
• Configuration guide
• Deployment notes
• Environment variable reference
• Common troubleshooting steps
• Customization notes
• License notes for buyers
• Support instructions and contact expectations

Every submitted product goes through review before publication. Approval is not guaranteed.

• Author submits the product and listing details
• YTL checks listing completeness and policy fit
• YTL reviews files, documentation, and buyer-facing claims
• YTL may request changes, fixes, or additional proof
• Products may be approved, rejected, or held for clarification
• Approved products may still be removed later if issues are discovered

Authors should define support scope clearly on the listing. Buyers rely on this when deciding whether a product fits their team.

• Support may include installation guidance, bug clarification, or documentation help
• Support does not automatically include custom development, hosting setup, new features, or business consulting
• Authors should respond professionally and within a reasonable timeframe
• YTL may assist with delivery, access, or policy issues separate from author support

During early access, author payouts and revenue-share terms may be handled through approved author agreements. Public self-serve payouts will be introduced when the author program is fully opened.

Revenue share, payout timing, and program terms may depend on account status, product category, beta terms, or future marketplace rules.

• Malware, phishing kits, spam tools, credential stealers, botnets, or exploit kits
• Stolen or copyright-infringing products
• Products designed for fraud or deception
• Products that bypass platform, payment, app store, or hosting rules
• Misleading AI-generated products with no real buyer value
• Products with hidden tracking, backdoors, or undisclosed remote access

• Listing rejection or request for changes
• Product unpublishing or download restriction
• Account suspension during investigation
• Revenue hold while a dispute or violation is reviewed
• Refund or buyer dispute escalation
• License revocation in severe or repeated cases