Security and data handling
Pre-launch processing summary
Repository analysis
Analysis uses a temporary server-side clone. Cleanup is attempted after analysis; crashes and cleanup failures mean immediate deletion cannot be guaranteed. Signed-in history saves analysis metadata with source-bearing report fields removed; this is not a claim that the entire data lifecycle has been independently audited.
AI processing and access
AI features process repository context. Optional source explanations send a selected excerpt and filename to Gemini after separate confirmation. Ask about provider-retention terms before sharing private code. Private repository workflows require authorized provider access.
Limits
Available checks are not a complete security assessment and do not establish runtime exploitability. Contact hello@xolvyn.dev for data-handling questions or deployment requirements.