Make it useful.
Make it yours.

01 · PURPOSE

Discovery should create understanding.

MVP Place is for founders and developers sharing software products, real progress, and useful context. Product pages are durable records, not disposable promotions. Founder profiles should make the person behind the work legible without requiring private information.

02 · PRODUCT PUBLICATION

Claim only what you can stand behind.

• Submit or claim a product only when you control it or have clear authorization to represent it.
• When an official catalog page already exists, use its ownership-claim control instead of creating a duplicate listing. A claim stays private until domain verification and human attribution review both succeed.
• Use the product’s official name, destination, and current mark. Do not imitate another company’s identity or imply a partnership that does not exist.
• Describe the actual product, intended user, current stage, latest change, and feedback need. Avoid invented customers, fabricated metrics, unsupported superlatives, or misleading comparisons.
• Keep destinations safe, functional, and relevant. No deceptive redirects, credential harvesting, malware, forced downloads, or unrelated affiliate funnels.
• Use domain verification only on an origin you are authorized to modify. Verification must be no more than 30 days old at submission, and one product can have only one active ownership claim. Verification proves control of that destination—not company identity, revenue, quality, security, or commercial success.
• Keep progress updates material and specific. Repeated promotional posts without a real product change may be returned or removed.

03 · FOUNDER IDENTITY

Be recognizable without oversharing.

Use a name, role, bio, website, and skills that accurately describe you. Do not impersonate another person, create confusingly similar handles, manufacture credentials, or publish another person’s private information.

Public visibility is optional. If enabled, the profile may appear in discovery, search, founder attribution, structured data, and feeds. Your ChatGPT email is never a public profile field.

04 · FEEDBACK & CONDUCT

Critique the work without diminishing the person.

Useful feedback names a concrete friction, question, validation, or idea and gives enough context for the founder to act. Do not harass, threaten, shame, discriminate, sexually exploit, dox, or repeatedly contact someone after they have made a boundary clear.

Private feedback stays private to the receiving founder unless the author explicitly shares a public profile with that note. Founders must not republish a private note as a testimonial without separate permission.

Founder Q&A is public and attributable. Ask about the product, its tradeoffs, implementation, or evidence; answer directly as the verified product owner. Questions and replies enter editorial review before publication and must not be used for anonymous reviews, customer-support escalation, personal disputes, or promotional link drops.

05 · SIGNAL INTEGRITY

Support is a choice, not a growth hack.

Follows, saves, supports, reports, views, and official visits must reflect genuine member actions. Do not buy, trade, automate, coordinate, or coerce engagement; create duplicate accounts to inflate totals; or offer rewards whose purpose is to manipulate ranking.

Private saves and follows are personal organization tools. Public support is an aggregate endorsement signal, but supporting member identities are not displayed publicly.

06 · MARKETPLACE CONDUCT

Commission, build, and review in good faith.

• Post requests only for lawful work you genuinely intend to commission, using a realistic budget, timeline, and testable deliverables.
• List a builder service only when the offer is specific, repeatable, honestly priced, and supported by an accurate public profile.
• Keep credentials, secrets, private customer data, payment-card information, and bank details out of public briefs, services, proposals, and project messages.
• Submit a proposal only when you can reasonably perform the work. Use one transparent total, final delivery day, and milestone plan; do not bait with placeholder prices, hide required work, spam requests, or coordinate fake proposals.
• Use the private project room for relevant decisions and handoff context. Delivery notes, approval, change requests, and disputes must describe the work precisely without threats or fabricated evidence.
• Review only a completed project you participated in. Do not trade, coerce, or manufacture ratings, and keep the review specific to that engagement.
• Do not pressure another member to use an unsafe payment method, begin unpaid speculative work, or accept terms they have not reviewed. Selecting a builder records intent, not payment or a guarantee.

07 · PROHIBITED MATERIAL

Some content does not belong here.

Do not publish or link to illegal goods or conduct, malicious code, phishing, fraud, exploitative sexual content, credible threats, hateful conduct, non-consensual personal information, intellectual-property infringement, or instructions primarily intended to bypass security or harm people.

Security and developer tools are welcome when their legitimate purpose, authorization boundary, and destination are clear.

08 · REVIEW & ENFORCEMENT

Context matters. The audit trail matters too.

Founder products, progress updates, Q&A posts, MVP requests, builder services, and project reviews enter editorial review before publication. Moderators may approve, request changes, restrict, or restore public content. Authorized moderators may also review a participant-opened project dispute and record a resolution note; that process governs platform workflow and conduct, not outside payment or legal rights.

Active restrictions remove affected content from public pages, discovery, search, social actions, sitemaps, and outbound redirects. Internal notes preserve why a decision was made. Review does not guarantee a product’s or builder’s performance, legality, or safety.

09 · REPORTING

Point to the issue, not the outrage.

Use the report control on a listing, profile, MVP request, or Q&A post for misleading claims, impersonation, unsafe destinations, abuse, spam, or rights concerns. Include the specific claim, link, attribution, or behavior that needs review. Reports are confidential to authorized moderators.