Draft, pending legal review. This page has not been reviewed by a lawyer. Text in [square brackets] is a placeholder to be completed before launch.
Security
Last updated: [DATE]
How we protect your data, and how to report a vulnerability.
What we do
- Read-only repository access. Source code is never stored; checkouts are deleted after a scan.
- Access tokens are encrypted at rest (AES-256-GCM, envelope encryption). Sessions are opaque random tokens stored hashed.
- Tenant isolation, audit logging of security-relevant actions, and rate limiting on every public endpoint.
- Public summaries are opt-in, aggregate-only, and signed with hybrid Ed25519 + ML-DSA-65 attestations you can verify.
See the privacy policy for the full data map.
Report a vulnerability
Email [SECURITY CONTACT EMAIL] with steps to reproduce. Please do not access other users' data, degrade the service, or publish details before we have had a reasonable chance to fix the issue. We will acknowledge reports within [ACKNOWLEDGEMENT TIME]. The machine-readable contact is at /.well-known/security.txt once published, and the full policy is in the repository's SECURITY.md.