Ready? Check… Launch!
Ready? Check… Launch!

Privacy Policy

Plain-English privacy notes for the Ready? Check… Launch! website and intake process.

Starter policy — requires qualified legal review before paid launch.

This page is starter website policy language and is not a substitute for legal advice.

Privacy

Data minimization

Ready? Check… Launch! is designed to collect only the metadata needed to understand fit, launch risk, and safe next steps. The public website is not intended to collect production data, raw customer records, secrets, cardholder data, or regulated data.

Privacy

Public intake data

Public intake may collect name, email, company or project name, public app URL, public GitHub repo URL, stack, AI tools used, launch timeline, selected service preferences, budget range, data-risk category selections, selected launch-risk areas, safe access preference, yes/no/not-sure launch metadata, and an optional short sanitized note.

Privacy

Prohibited data

Do not submit production secrets, private keys, API tokens, passwords, raw cardholder data, database dumps, PHI, children’s data, regulated data, private customer records, or sensitive user-generated content through forms or ordinary email.

Privacy

Private repository access

Private repository access is coordinated separately after intake and written scope. Ready? Check… Launch! prefers read-only, least-privilege, time-limited access, guided screen share, redacted screenshots, synthetic/test data, or staging/test-mode context where appropriate.

Privacy

AI-assisted work

Business-grade AI coding and review tools may support analysis, drafting, review, or implementation. Ready? Check… Launch! does not intentionally submit secrets, production credentials, private customer records, raw payment data, regulated data, database dumps, or sensitive user-generated content into AI tools.

Privacy

Subprocessors / third-party tools

Third-party tools may include hosting, email delivery, analytics, scheduling, payment processing, repository hosting, communication tools, and AI-assisted coding or review tools. These tools should be used within the data-minimization and no-secrets model.

Privacy

Retention and deletion

Inquiry metadata may be retained for follow-up, scoping, accounting, security, legal, or legitimate business purposes. Accidental secrets or prohibited data may be redacted or deleted where practical. You can request deletion of inquiry data by email, subject to necessary retention obligations.

Privacy

Regulated data exclusion

Health/PHI, children’s data, regulated financial data, legal-client materials, government/defense data, safety-critical data, raw payment data, and similar high-risk materials are excluded from standard public intake and may require a custom lawyer-reviewed scope before any paid engagement.

Contact

Privacy questions

Privacy questions can be sent to hello@readychecklaunch.com.

Beta audit spots available

No secrets in forms.

Start auditScorecard