01 · PRODUCT MEASUREMENT
What the analytics count.
When you open a product passport or deliberately follow an MVP Place link to its official destination, the application can add one daily unique-browser count for that product and event. It uses a random, server-authenticated first-party cookie with an authenticated issue time that expires after 48 hours and stores only a one-way daily token—not the cookie value itself.
A missing, malformed, fabricated, or expired cookie is not counted until the browser returns a newly authenticated value. To bound repeated cookie rotation, MVP Place immediately transforms the hosting-provided network address into a keyed daily digest and uses that digest only for a small, short-lived issuance counter. The raw address is never written to the application database, and the digest is not used to recognize a person or count product activity. Raw uniqueness records are pruned after 90 days. Aggregate daily counts may be retained to show founders durable product trends. The application does not attach those counts to a signed-in identity.
Hosting and security providers may process ordinary network information to deliver and protect the service. MVP Place does not copy raw IP addresses into its product analytics or abuse-counter tables.
02 · ACCOUNTS & COMMUNITY
What signed-in use requires.
Sign in with ChatGPT supplies a stable account identifier, email address, and available display name so MVP Place can keep private drafts, saves, follows, feedback, public supports, confidential content reports, founder profiles, product submissions, MVP requests and proposals, progress updates, inbox seen state, and moderation decisions connected to the correct account.
Founder profiles are private until their owner turns on public visibility. Product drafts, progress updates, and uploaded logos remain private until the owner submits them and a moderator approves publication. Logo artwork is normalized in the browser to a square PNG before upload; the reviewed version becomes a public product asset only after approval. Public profile, product, approved-update, and aggregate support fields are intentionally visible to visitors and search engines.
Before a founder listing can enter review, MVP Place requests a generated challenge from the product’s HTTPS origin and checks for that exact token in a well-known file or homepage meta tag. Before each request or redirect, the application resolves the destination and rejects loopback, private, link-local, documentation, multicast, or otherwise non-public network answers. DNS answers are used only for that immediate safety decision and are not stored. The verification method, origin, and timestamp are stored with the listing. Verification must be no more than 30 days old at submission, and a verified origin can belong to only one active owner listing at a time. The check sends no founder account details to the product website.
Product feedback is delivered privately to the product owner. The author’s public founder profile is included only when the author explicitly enables that option for the note; it is off by default.
Founder Q&A is a separate public surface available on reviewed founder products. A participant must have a public founder profile, and each question or verified-owner reply stays private until editorial approval. Published posts show the profile name and handle, can be reported confidentially, and can be removed by their author. MVP Place stores the post, product, parent thread, author account, review status, moderation note, timestamps, and reviewer.
The founder inbox keeps one account-level timestamp for the most recent “mark all seen” action. It distinguishes new feedback and social activity from items already reviewed; MVP Place does not create per-item read receipts or disclose this state to other members.
Content reports are confidential to authorized moderators. The reported content, reason, reporter’s context, review status, and an internal decision note are retained to investigate abuse and preserve an accountable review trail; report authors are not identified to the reported account or public visitors.
When a moderator restricts reported content, MVP Place stores the target, reason, internal decision note, reviewer, and any later restoration note. An active restriction removes that content from public pages, discovery, search, social actions, sitemaps, and outbound redirects. Restriction details are visible only to authorized moderators and, for owner-submitted content, in that owner’s account export.
To protect verification, uploads, feedback, reports, Q&A, marketplace submissions, and social actions from abuse, MVP Place keeps short-lived request counters under a one-way hash of the account identifier rather than the raw identifier. Expired counters are pruned during later protected activity, and remaining counters are removed when the account’s MVP Place data is deleted.
03 · CATALOG OWNERSHIP CLAIMS
Private proof before public attribution.
A signed-in member with a public founder profile may claim an existing official catalog product. MVP Place stores the product slug, claimant account, private verification token, verification method and time, workflow state, timestamps, moderation note, and reviewer. Pending claims and their tokens are not public.
Approval connects the existing catalog record and official logo to the claimant’s public founder profile. It proves that the claimant demonstrated control of the product’s stored official domain and passed attribution review; it does not certify legal company identity, revenue, security, quality, or performance. Claim records are included in the claimant’s private account export and removed when that claimant deletes their MVP Place data. Reviewer identity is anonymized on unrelated retained claims.
04 · PUBLIC PRODUCT SOURCES
Attribution, not impersonation.
MVP Place may show information observed from official product destinations or public launch records. Each real-world claim is labelled with its source type and observation date. Founder-submitted listings are identified separately and connected to the authenticated founder profile that submitted them.
Authorized moderators can run a limited HTTPS reachability check against a product’s already-published official destination. MVP Place stores the destination, response status, redirect result, response time, check time, failure streak, and reviewer account identifier. A successful check means only that the destination responded; it does not re-verify claims, ownership, pricing, safety, or product quality.
05 · NETWORK NOTIFICATIONS
Relationships choose the inbox.
When you privately save a product, publicly support it, or follow its verified founder, reviewed product updates can appear in your private network inbox and unread total. MVP Place derives this relevance when the inbox is loaded; it does not publish the relationship or create a separate notification-recipient record.
One private account-level timestamp records when you last marked the inbox seen. Product or founder restrictions remove affected updates from the inbox and unread total. Removing the save, support, or follow stops future relationship-based update notifications.
06 · MVP MARKETPLACE
Public briefs, services, and acquisition offers. Private project work.
When you post an MVP request or builder service, MVP Place stores its description, category, skills, deliverables, pricing or budget guidance, delivery timing, workflow status, review decision, timestamps, and controlling account. Submissions stay private during review. Approved requests and active services become public; account email addresses and individual build-proposal contents do not.
A verified product owner may separately opt a published project into public acquisition offers and provide an optional asking price. Signed-in buyers can publish, update, or withdraw a whole-dollar offer and a short public note. The amount, note, status, time, and a public founder identity when available are visible to everyone. Accepting one offer marks the project sale agreed and closes competing live offers.
A builder must publish a founder profile before proposing or listing a service. The client can privately compare builder profile context, approach, total price, delivery date, milestones, and proposal status. Accepting a proposal creates a participant-only project room and records the selection. That room stores milestone states, delivery and response notes, private messages, dispute details and moderator resolution, and post-completion reviews. Reviews are public only after editorial approval.
MVP Place does not currently collect payment, hold escrow, create bank records, receive payment-card information, perform due diligence, or transfer project ownership. Proposal, milestone, asking-price, and acquisition-offer amounts are marketplace records, not charges. These records are included in account export and removed with the connected account data.
07 · YOUR CHOICES
Controls that work without dark patterns.
- Enable Global Privacy Control or Do Not Track in your browser to exclude product measurement events.
- Keep a founder profile private, or turn off its public visibility from Founder Studio.
- Remove a product from your private watchlist, withdraw a public product support, or unfollow a founder at any time; doing so also stops future update notifications from that relationship.
- Public support totals show how many signed-in members currently support a product; member identities are not displayed.
- Pause acquisition offers on a product you own, or update or withdraw your own active acquisition offer before it is accepted.
- Withdraw an eligible marketplace proposal before selection, or confidentially report a public MVP request.
- Withdraw an unpublished progress update or revise one returned by editorial review.
- Remove a Q&A post you authored, or submit a confidential report when a public listing, profile, request, or Q&A post appears unsafe, abusive, misleading, or incorrectly attributed.
- Download a portable JSON copy of your account, profile, product, marketplace, acquisition-offer, update, logo, feedback, Q&A, inbox seen state, report, moderation-history, source-check, follow, save, and support data from Account & data.
- Permanently delete all data connected to your MVP Place account. This removes public listings and requests, offers, proposals, supports, updates, Q&A posts, inbox seen state, reports, moderation and source-check history tied to deleted content, and product-linked analytics. Moderator identity is anonymized on unrelated retained records. This does not delete the ChatGPT account used to sign in.
- Do not publish information you do not want shown on a public founder, product, or marketplace request page.
MVP Place does not sell personal information or use product analytics for behavioral advertising.
08 · SERVICE CHANGES
When the boundary changes, this page changes.
Material changes to collection, retention, public visibility, or marketplace payment capabilities will be reflected here with a new effective date. New analytics or payment categories will not be silently folded into existing labels.