Before payment
Launch Readiness Review service terms
Effective 23 August 2026
These terms explain the standard BuildVetted review, its limits, and what each side must do. A project-specific written scope may add narrower boundaries; if it conflicts with general marketing copy, the accepted project scope controls.
1. The service
A Launch Readiness Review is an independent, fixed-scope review of one named app and authorized environment. Nine founder-risk areas are considered; the critical paths actually reviewed are those applicable to your app, agreed in writing before the review begins. It normally includes a private recorded walkthrough, written findings, an evidence-backed GO / CONDITIONAL GO / NO-GO verdict, a prioritized developer handoff, seven days of written clarification, and one recheck of agreed P0/P1 fixes submitted within seven days of delivery.
2. What is not included
The standard review is not a formal penetration test, exploit campaign, denial-of-service or load test, legal or regulatory advice, compliance certification, production data extraction, implementation engagement, architecture rewrite, or ongoing monitoring. It does not test every route, parameter or risk within the nine areas, and it is not a guarantee that every vulnerability, bug, fraud path, or operational risk has been found.
3. Your authorization
You confirm that you own the named app or have authority to request the review. Authorization covers only the targets, environments, accounts, roles, and actions agreed in writing. You must not provide access to third-party systems you are not authorized to test. BuildVetted may pause or stop work if authorization is unclear.
4. Access and customer responsibilities
You provide accurate scope information, dedicated test accounts, test-mode payment credentials, and the minimum usable collaborator access requested. Do not send shared master passwords, real card data, customer personal data, production datasets, API keys, or tokens through the qualification form or ordinary email. You remain responsible for backups, production changes, launch decisions, and revoking BuildVetted access after delivery.
5. Delivery clock
The 48-hour review window starts after payment, written authorization, agreed scope and complete usable access are all in place. If access or evidence becomes unavailable, the clock pauses while the blocker is documented. Delivery occurs through the private channel agreed during onboarding.
6. Payment, cancellation, and refunds
Payment reserves capacity for the accepted project. You may cancel for a full refund before review work begins. The founding offer also carries a 30-day value guarantee: email BuildVetted within 30 days after report delivery for a full refund, with no call or explanation required. BuildVetted may decline an unsuitable or unsafe request and refund any payment received. Refunds are returned through the original payment method and may take the payment provider’s normal processing time.
7. Findings and decisions
Findings reflect the evidence available during the agreed review window and are labelled REPRODUCED, VERIFIED, OBSERVED, NOT VERIFIED, or OUT OF SCOPE. Missing evidence is not treated as assurance. You decide whether and how to launch, fix, or rely on the app, and should obtain specialist legal, compliance, privacy, tax, or security advice where your product requires it.
8. Confidentiality and permitted learning
BuildVetted uses project material only to provide and administer the service, subject to the privacy notice. Client names, screenshots, findings, testimonials, and identifying details are not published without permission. Anonymized learnings or testimonials are used only when you separately opt in; purchase does not imply permission.
9. Contact and changes
Questions, cancellations, or refund requests can be sent to rohit@buildvetted.com. Material changes to these terms apply prospectively and will be shown with a new effective date. The scope accepted at purchase remains the scope for that review unless both sides agree otherwise in writing.