Security
Security and access policy
Ready? Check… Launch! is designed around a simple rule: do not send secrets through public forms.
What not to send
- passwords
- API keys
- private keys
- production credentials
- customer data
- health, financial, or regulated data
- database dumps
- session tokens
Preferred audit access
- read-only GitHub access where possible
- screen share for sensitive context
- sanitized environment examples
- temporary access with least privilege
- access removed after engagement
How we handle AI-assisted work
Ready? Check… Launch! may use AI coding and review tools to assist with analysis and implementation. Human review remains responsible for final judgment. Secrets and sensitive production data should not be submitted to AI tools.
Limitations
No audit can guarantee complete security. Ready? Check… Launch! focuses on practical launch readiness, high-risk blockers, and production-hardening recommendations.
Responsible disclosure contact
Security reports can be sent to security@readychecklaunch.com.