1
Use projects you own
Upload or import only projects you own, control, or have permission to review.
Terms of Use
Clear terms for a bounded launch review.
Before Users helps you review project signals before launch. The report is guidance, not certification, approval, or a guarantee that an application is secure.
Terms snapshot
Use agreement in three rules
2
Understand report limits
The Launch Readiness Report is guidance from static signals, not approval to launch.
3
You decide and verify
You remain responsible for fixes, testing, credentials, and launch decisions.
Agreement snapshot
Use it for authorized projects. Treat the report as guidance.
The Terms page is about rules and responsibility: what you may scan, what the report means, how paid access works, and when access can be limited.
1
Use projects you own
Upload or import only projects you own, control, or have permission to review.
2
Understand report limits
The Launch Readiness Report is guidance from static signals, not approval to launch.
3
You decide and verify
You remain responsible for fixes, testing, credentials, and launch decisions.
01
Service basics
What Before Users provides
Before Users provides a static pre-launch review and organizes findings into a Launch Readiness Report.
Before Users provides static pre-launch reviews for web apps, SaaS products, and AI-assisted projects.
You may upload a project ZIP or connect a selected read-only GitHub repository.
The service generates a Launch Readiness Report with findings, business impact, masked evidence, and fix-first guidance.
The service, limits, pricing, and report behavior may evolve over time.
02
Responsible use
Permission to scan is required
Before Users is for projects you own, control, or are authorized to review.
Allowed
Projects you own or control
Projects your client or team has authorized you to review
Launch-stage apps where you want static risk signals before users arrive
Not allowed
Third-party private code without permission
Malware, harmful payloads, or service-disruption attempts
Attempts to attack, bypass, or exploit third-party systems
Using the service to harvest secrets or sensitive data from others
03
Review boundaries
What the review does not mean
The review is static and signal-based. These limits are part of the service terms, not hidden fine print.
Uploaded or imported code is not executed.
Dependencies are not installed.
Package-manager commands are not run.
Potential secrets are flagged as risk signals, not validated as live credentials.
The product is not a penetration test.
The product is not compliance certification.
The product does not guarantee that an application is secure.
Reports are based on available static signals.
04
Reports and responsibility
You own fixes, testing, and launch decisions
The Launch Readiness Report helps prioritize work. It does not replace engineering judgment or testing.
1
Review findings and decide whether they apply to your product.
2
Verify evidence before making launch or business decisions.
3
Apply fixes yourself, with your developer, or with an AI coding tool.
4
Test authentication, payments, data access, and launch-critical flows after fixes.
5
Rotate credentials if exposed credential patterns are flagged.
6
Review exported reports before sharing them with teammates or third parties.
05
Payment and access
Paid report access is a one-time purchase
The Launch Readiness Report is not described here as a subscription. Pricing and included access are shown on the Pricing page.
Paid product
Launch Readiness Report access is sold as a one-time purchase.
Pricing
Current pricing is shown on the Pricing page.
Payment processor
Paddle is used for checkout and may calculate taxes or VAT based on buyer location.
Included access
Paid access may include one full launch review, the full interactive report, sanitized export, and one follow-up review for the same project.
Refunds
Refund requests are reviewed under the Refund Policy.
06
Free preview and limits
Limits protect the service
Free access and scan limits may apply to keep the product reliable and prevent abuse.
Verified users may receive a limited free preview if available.
Free access, scan counts, report visibility, ZIP size, repository size, file size, timeouts, and exports may be limited.
Limits help protect the service from cost, abuse, and heavy project inputs.
Limits and access rules may change as the product evolves.
07
Platform rules
Account, provider, and service changes
These terms also cover account access, provider involvement, and changes to the service.
Account access
You are responsible for keeping your account access secure. Access may be limited or blocked for abuse, misuse, payment issues, or attempts to disrupt the service.
Third-party services
Before Users may use third-party service providers for authentication, hosting, payments, data storage, and repository import. Those providers may process data according to their own terms and privacy policies.
Changes
Before Users may update the service, limits, pricing, features, and these terms over time.
These terms are practical launch-stage terms for the current product and are not a substitute for lawyer-drafted legal advice.
Ready to review your launch risks?