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 listing controller. 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.
• When sending a request to one service, address that builder honestly and keep secrets or unnecessary personal data out of the brief. Editorial approval delivers the request privately; it does not obligate the builder to respond or accept.
• A selected builder may decline a private service request with a useful, respectful reason. Do not copy, disclose, or republish another participant’s private brief, proposal, or decline reason without permission.
• 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, private service requests, services, proposals, project messages, acquisition-room messages, and cancellation reasons. Listing-control proof is deliberately public: publish only the exact current MVP Place challenge in the required verification file or homepage meta tag, with no credentials, customer data, or unrelated secrets.
• Submit a proposal or acquisition offer only when you can reasonably follow through; do not use placeholder prices, hidden conditions, spam, or coordinated fake offers.
• Use private project and acquisition rooms for relevant decisions and handoff context. Delivery notes, confirmations, change requests, disputes, and cancellation reasons must describe the work precisely without threats, abuse, or fabricated evidence.
• Confirm a handoff only after the outside asset handoff you agreed to is complete. Request or accept a listing-control transfer only when both accepted-offer participants agree and the buyer is authorized to control the official domain and represent the product. Do not share, intercept, reuse, or fabricate another party’s challenge. Either participant may withdraw before approval, and moderators may return mismatched, stale, or incomplete evidence for correction. Listing control never gives the buyer another member’s private messages, received feedback, or authorship.
• 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, accept terms they have not reviewed, confirm an incomplete handoff, publish a verification challenge, or continue a listing transfer. Selecting a builder, confirming a handoff, transferring an MVP Place listing, or closing an acquisition records platform workflow state, not payment, legal title, 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, project reviews, catalog ownership claims, and listing-control transfers enter editorial review before publication, private delivery, or attribution change. Moderators may approve, request changes, restrict, or restore public content, and may approve or return private service requests without publishing them. A listing-transfer decision note is shared with its participants so they can act on the outcome; separate internal notes and immutable audit events preserve moderation accountability. 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 public content from discovery, search, social actions, sitemaps, and outbound redirects, and can pause access or actions in private marketplace workflows. Internal notes preserve why a decision was made. Review does not guarantee a product’s or builder’s performance, legality, safety, ownership, payment, or acceptance of a request.

09 · REPORTING

Point to the issue, not the outrage.

Use the report control on a listing, profile, MVP request, public acquisition offer, 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.