LR

LaunchRoast AI

TermsHome

Policy

Privacy

LaunchRoast AI keeps the current product intentionally simple. The notes below explain how request handling, local usage tracking, and passive website status checks work in this version.

Section

What we store

We store a small audit usage counter in localStorage for basic product feedback and a lighter repeat-use experience. Submitted landing page URLs or copy are processed for the current audit request, and a fuller production policy should describe logging, retention, and processor details more explicitly before launch.

Section

How audit requests are handled

Audit requests are sent to the app server route. If OPENROUTER_API_KEY is configured, the request may be forwarded to OpenRouter for live AI analysis. If no API key is configured, the app falls back to a local mock response instead of failing the request.

Section

Website status checks

For public URLs, the app can run a passive availability check to confirm whether the page is reachable, whether it redirects, whether HTTPS is used, and how long the request takes. It does not scan vulnerabilities, probe hidden paths, or inspect private networks.

Section

Contact

Publish a clear support contact before launch so visitors have a reliable path for deletion requests, policy questions, or data handling concerns.