Privacy Policy

We collect the following categories of personal and operational data:

We do not store your source code. The cloned repository is held in an ephemeral per-scan container, analysed, and then permanently deleted. Only the findings and reasoning generated from the analysis are stored.

1. GitHub OAuth — you authenticate via GitHub. We receive your GitHub user ID, username, and primary email. We do not receive your private repositories unless you explicitly grant that scope.
2. Repository cloning — when you submit a scan, the worker clones your repository into an isolated, network-isolated container. The clone is deleted immediately after the scan pipeline finishes.
3. Static analysis — cargo-clippy, cargo-audit, and Semgrep (11 custom rules) run deterministically on the cloned code inside the sandbox. No source code leaves the sandbox during this phase.
4. LLM reasoning — code excerpts (not full files) are sent to Anthropic Claude to reason about potential vulnerabilities. Excerpts are transmitted over HTTPS and used solely to generate the findings for your report. Anthropic's API usage policies apply.
5. Findings storage — vulnerability descriptions, severity scores, evidence excerpts, and LLM reasoning steps are stored in our PostgreSQL database. These are your security-sensitive findings, treated as confidential (see Terms of Service §3).
6. PDF report — a PDF report is generated and stored in object storage (Cloudflare R2 or similar). Access is protected by a short-lived signed URL tied to your account.
7. Notifications — completion and alert emails are sent via Resend. You may opt out at any time via the unsubscribe link in each email or via Settings → Notifications.

You can request early deletion of your account and associated data at any time via Settings → Danger Zone or by emailing privacy@solguard.dev. See §8 for the full list of your rights.

SolGuard is operated from the Czech Republic (EU). Several subprocessors (GitHub, Stripe, Resend, Anthropic, Railway/Fly.io) are based in the United States, which does not have an EU adequacy decision for general commercial data transfers.

We rely on Standard Contractual Clauses (SCCs — Commission Implementing Decision (EU) 2021/914) as the transfer mechanism for personal data sent to these processors. Copies of the applicable SCCs are available on request.

PostHog analytics traffic is routed to the EU-hosted instance (eu.posthog.com) and does not leave the EEA.

Under the GDPR you have the following rights with respect to your personal data:

• Access (Art. 15) — request a copy of the data we hold about you.
• Rectification (Art. 16) — correct inaccurate data.
• Erasure / Right to be forgotten (Art. 17) — delete your account and all associated personal data. You can do this yourself via Settings → Danger Zone → Delete account in the dashboard, or by emailing us.
• Restriction (Art. 18) — restrict processing in certain circumstances.
• Portability (Art. 20) — receive your data in a structured, machine-readable format.
• Objection (Art. 21) — object to processing based on legitimate interests (e.g. analytics).
• Withdraw consent — where we rely on consent, you may withdraw it at any time without affecting prior processing.

To exercise any of these rights, email privacy@solguard.dev. We will respond within 30 days. You also have the right to lodge a complaint with your local supervisory authority (in the Czech Republic: Úřad pro ochranu osobních údajů (UOOU)).

We use PostHog (EU-hosted) for product analytics. PostHog receives your user ID, subscription tier, and anonymised usage events (page views, feature interactions). We do not send your email address to PostHog's identify API.

You can opt out of analytics at any time via Settings → Privacy or by emailing privacy@solguard.dev. Opting out does not affect the service.

We do not use tracking cookies for advertising. Session-management cookies are strictly necessary for authentication and are not subject to consent requirements.

We apply the following technical and organisational measures:

• All data in transit encrypted via TLS 1.2+.
• Per-scan network-isolated containers — scanned code cannot make outbound network calls.
• Short-lived signed URLs for report downloads (15-minute expiry).
• JWT-based authentication with rotating refresh tokens.
• Findings stored as confidential security data, visible only to the account owner.