Listing and Content Standards

Overview

To list on SprukoMarket, your Items must meet quality, safety, and upload preparation rules. These standards align with our Review Process, Exclusivity Policy, Security, and IP Takedown. For a step-by-step uploader guide, see How to Upload Your Items to SprukoMarket.

1) Quality & accuracy

• Works as described. Features in description and demo must be present and functional.
• Clean packaging. Clear file structure; no unnecessary binaries; no passworded archives.
• Docs. Installation, configuration, dependencies, supported versions/browsers/frameworks, and change log.
• Performance. Reasonable load times; avoid excessive bundle size; disclose minimum system requirements.
• Localization-ready (where applicable). Strings externalized; RTL guidance if advertised.

2) Upload workflow & packaging

• Main archive. Provide a single .zip with your production files. Put optional “documentation” and “license/credits” in clearly labeled folders.
• Don’t include previews in the buyer archive. Previews (covers, watermarked screenshots, demo media) must be uploaded as preview assets, not mixed with source files.
• Help file. Include a readable README/HELP with setup, configuration, support scope, and version history.
• Upload methods. Use the dashboard uploader. If alternative methods (e.g., large-file/FTP/API) are enabled, follow the method-specific instructions.
• Final checks. Validate assets, remove unused files, and ensure relative paths work after extraction.

3) Previews & presentation

• Cover image & gallery. Supply crisp, accurate imagery that reflects the current version and license scope. Follow our size/aspect guidance in the Review Process.
• Live demo. If you provide a live demo, remove hard-coded credentials and destructive endpoints; label sample data.
• No misleading composites. Don’t show features or content not included.

4) Metadata, titles & tags

• Clear, concise titles. Use English characters, avoid stuffing, and keep titles concise; follow length limits shown in the uploader.
• Accurate tags & categories. Tag for use-cases and technologies actually included; avoid competitor brand names or trademarks you don’t own.
• Change log & version. Use semantic versioning (MAJOR.MINOR.PATCH) and date entries (YYYY-MM-DD) in your listing.

5) AI, datasets & training

• Disclose material AI assistance. If AI materially contributed to assets/code/text, say so in docs/readme.
• No training on Buyer data without explicit consent. Support conversations and Buyer uploads are off-limits for training unless the Buyer opts in.
• Datasets. Provide provenance notes, licenses, and any personal-data handling details. Remove sensitive or unlawfully sourced data.
• Model weights. If included, state license and usage limits; no hidden remote fetches of weights without disclosure.

6) Third-party assets, OSS & releases

• Attribution & notices. Include a THIRD_PARTY_NOTICES listing licenses (MIT, Apache-2.0, etc.).
• Open-source compliance. Honor license terms (copyright, notices, copyleft obligations).
• Commercial assets. Only use assets you own or have a valid license for; keep purchase/permission records for ≥ 24 months.
• Model/property releases. Where required (people/brands/locations), include release details or ensure assets are cleared.

7) Privacy, tracking & data

• No covert collection. Don’t collect or transmit personal data without a clear purpose and consent where required.
• Regional laws. Handle personal data per applicable laws (e.g., India DPDP 2023, GDPR/UK GDPR, CCPA/CPRA).
• Telemetry. If your Item phones home, document what, why, where it goes, and how to disable. Offer an opt-out when appropriate.

8) Security requirements

• No malicious code. No obfuscation intended to hide harmful behavior.
• Vulnerability patching. Critical fixes ≤ 72 hours; high severity ≤ 7 days; others promptly. See Security & Responsible Disclosure.
• Dependency hygiene. Keep third-party packages updated; remove known-vulnerable versions.
• Secrets. Do not ship hard-coded credentials or production keys.

9) Themes/Code preparation (extra)

For templates, themes, and code-heavy items, follow these additional prep rules:

• Pre-submission steps. Save the main distributable, validate assets, prepare the help file, choose a clear title, and run final checks.
• Platform checks. If your item targets a framework/CMS, run the recommended linters/validators and include minimum version support in docs.
• Privacy in code. No data sent to third-party servers without an informed opt-in; provide an opt-out.
• Public docs. Host documentation that buyers can access, or ship a complete local copy in a documentation/ folder.

10) Accessibility & internationalization

• Where you claim accessibility, meet common patterns (semantic HTML, focus states, alt text, ARIA where appropriate).
• Provide language/localization guidance if the Item advertises multi-language support.

11) Enforcement & reporting

• We may reject, edit, hide, or remove Items that don’t meet standards (see §20).
• For IP concerns, use IP Infringement & Takedown. For security issues, see Security.
• Repeat or egregious breaches can lead to penalties, holds, or termination (see §24).

12) Examples (Do / Don’t)

13) Pre-submission checklist

• Features match description & demo; no broken links.
• No malware/backdoors; dependencies updated.
• THIRD_PARTY_NOTICES present; releases/licenses retained ≥ 24 months.
• Privacy/telemetry documented; no covert tracking.
• Docs complete; change log with dates; semantic versioning used.
• For themes/code: validators passed; minimum versions stated; no silent outbound calls.

Questions? Email [email protected].