Draft · Not yet effective · Requires legal review.

Free product terms

The current product contract has no subscription, paid license tier, paid upgrade, or automatic directory-submission fee. Availability, supported platforms, providers, and features depend on the verified released build shown on the Download and Changelog pages.

OAuth account responsibility

Users are responsible for maintaining access to their Google, Apple, or GitHub account, protecting connected sessions, reviewing organization membership, and revoking access when a device, account, or team member should no longer use the service.

Ownership and accuracy of submitted product materials

Users must have the right to submit the product name, copy, logos, screenshots, company facts, founder facts, URLs, and other materials. Users are responsible for confirming that the Launch Master is accurate and does not include misleading, infringing, illegal, or fabricated claims.

Authorization to create accounts and submit listings

Starting a campaign authorizes the app to perform the approved normal account-creation, email-verification, field-adaptation, upload, and final-submit actions for applicable targets in the active signed registry release, subject to the published safety boundary and user controls.

Third-party directory terms

Every directory remains an independent third party with its own eligibility, review, privacy, content, account, removal, and publication rules. Vibe Launch Master cannot accept a paid, exclusive, unusual, or high-risk term on the user’s behalf.

Prohibited spam, impersonation, abuse, and policy evasion

Users may not use the product to submit unrelated, deceptive, duplicate, infringing, malicious, or unlawful products; impersonate another person or organization; evade a suspension; bypass platform rules; create fake evidence; or overwhelm a directory, inbox, browser profile, or service endpoint.

No automatic payment or paid placement

The app does not enter credit-card details, authorize payment, purchase promoted placement, accept automatic renewal, or choose paid-only directory paths. A third-party charge must remain a separate, explicit user decision governed by that provider’s terms.

No guarantee of acceptance, publication, traffic, rankings, downloads, or sales

The service can reduce repetitive work and increase the number of relevant places where a product may appear. It does not control editorial approval, public availability, search indexing, backlinks, AI citation, ranking, visitor behavior, conversion, downloads, users, or revenue.

Human-attention requirements

Users must complete CAPTCHA, 2FA, Passkeys, identity verification, native dialogs, payment decisions, unusual legal confirmations, and uncertain-result reviews. The product may pause or skip a target rather than bypass or assume the result of these steps.

Suspension and termination for abuse

Access can be limited or terminated when behavior threatens users, directories, browser accounts, infrastructure, legal compliance, security, or the integrity of the registry and submission workflow. The production policy must describe notice, appeal, and data-handling procedures before enforcement begins.

Warranty and liability boundaries

Final warranty, limitation-of-liability, indemnity, service-availability, and dispute terms require legal review and must reflect the actual operator and governing law. This development draft does not create or waive legal rights by inventing those clauses.

Governing law and correction contact

The legal entity, governing law, venue, official contact, and effective correction route have not yet been approved for public use. They must be added before these terms become effective.

Effective date and change history

These terms are a development draft and are not effective. A production version must show an effective date, version or change history, material amendments, and the relationship between the terms, privacy policy, product facts, and released application behavior.