Terms of Service
Last revised: October 2026. Effective immediately for all PreLaunchQA users and scans.
1. Who may run a check
You may only request a check for a web application that you own or for which you have explicit written authorization from the owner to test. We verify ownership by DNS TXT record, HTML meta tag, or a well-known verification file before any automated check is queued or executed. Requesting a check for an application or domain you do not control is strictly prohibited and constitutes a material breach of these terms. We reserve the right to immediately terminate access and notify affected domain administrators if unauthorized testing is suspected.
2. What a check covers and scope limitations
PreLaunchQA performs passive, non-destructive browser-level verification. Our workers load your specified target URLs in an isolated Chromium browser and record browser console errors, failed network requests, broken or dead links, basic accessibility standards (image alt attributes and form labels), mixed content warnings, and responsive layout hygiene. We do not attempt offensive security attacks (such as SQL injection, fuzzing, cross-site scripting exploitation, or denial of service), and we never attempt to bypass access control barriers.
3. Nature of findings and disclaimer of warranty
All reports and findings generated by PreLaunchQA reflect observational data collected in an isolated browser session at a specific point in time. A clean or passed report is not an audit, certification, guarantee of complete security, or guarantee that your application is entirely free of defects or vulnerabilities. You remain solely responsible for your software release decisions, compliance obligations, and manual quality assurance.
4. Data handling, test credentials and evidence retention
Our system stores diagnostic evidence (console strings, failed HTTP request URLs, and element HTML snippets) to substantiate report findings. When interactive test flows requiring test credentials are configured, credentials must be designated solely for test accounts and are encrypted in transit and at rest using AES-GCM. Ephemeral credentials are permanently purged within 24 hours of check completion. Associated screenshot evidence and report artifacts are retained for 30 calendar days, after which they are systematically deleted.
5. Fees, billing, and refund policy
Paid launch checks and monthly re-test subscriptions are billed in U.S. Dollars (USD) through our authorized payment processor (Stripe). Subscription plans renew automatically on a monthly billing cycle unless canceled prior to the renewal date via your dashboard. We offer a 7-day money-back guarantee: if a purchased check fails to complete or cannot generate an evidence report due to an infrastructure or worker error on our end, contact [email protected] within 7 days of purchase for a prompt, unconditional full refund.
6. Limitation of liability and indemnification
To the maximum extent permitted by applicable law, PreLaunchQA and its operators shall not be liable for any indirect, incidental, punitive, or consequential damages arising from the use of our service or any reliance on generated reports. In no event shall our total aggregate liability exceed the total fees paid by you to PreLaunchQA in the twelve (12) months preceding the incident. You agree to defend, indemnify, and hold harmless PreLaunchQA against any third-party claims or damages resulting from your unauthorized testing of any domain or service.
7. Governing law and dispute resolution
These terms are governed by and construed in accordance with the laws of the State of Delaware, United States, without regard to conflict of law principles. Any dispute arising under or relating to these terms shall be resolved exclusively through confidential binding arbitration under the rules of the American Arbitration Association (AAA), or in small claims court where applicable. For formal legal notices or inquiries, contact [email protected].