Privacy
Privacy policy
How LaunchGlint handles scanned URLs, public scorecards, payment metadata, and support email.
What we collect
LaunchGlint collects the URLs you submit for scanning, public HTTP response metadata, generated findings, public scorecard snapshots, and payment metadata returned by Stripe or PayPal for paid reports.
First-party analytics
LaunchGlint uses app-owned anonymous visitor and session ids to understand the funnel. Analytics events avoid raw IP addresses, user agents, full submitted URLs, payment emails, and report contents; scanned targets are hashed by default.
What we do not do
LaunchGlint does not ask for source-code credentials, production secrets, private repository access, passwords, or card numbers. Payments are handled by Stripe-hosted Checkout or PayPal-hosted checkout.
Public scorecards
When you create a share card, LaunchGlint puts a signed public snapshot in the URL. Anyone with that link can see the target URL, score, severity counts, and preview findings.
Retention
Stateless scorecards live in the signed URL itself. Hosted checkout metadata is used to verify paid report access. PayPal Orders and Stripe Checkout Sessions can deliver reports automatically after approval; payment-link fallback orders are fulfilled manually when that mode is configured. Server logs may be retained by the hosting provider.
Contact
Questions or deletion requests: RavivYatom@gmail.com.