Last updated 2026-06-18 · Draft — describes how GitSpider actually handles data, but not yet reviewed by a lawyer.
GitSpider reads your GitHub Actions data to show CI analytics, recommendations, and alerts. This explains what we store and why.
Only to operate the product: compute analytics, generate config recommendations, and send the alerts you set up. We also compute anonymized, aggregated benchmarks across all monitored repos (e.g. typical CI failure rates and durations) so you can see how your CI compares — these are pure aggregate numbers, contain no repo names or identifiers, and are only published over a large enough group that no individual repo is identifiable. We do not sell your data or use it for advertising.
Sub-processors strictly to run the service: GitHub (source of the data; we read CI + workflow files and post comments on your pull requests, but never modify your code or access secrets), Stripe (billing), and — only if you enable them — Slack and Resend (alert delivery). Hosting/database are on Fly.io and Neon.
Individual workflow runs are kept ~30 days; aggregated daily rollups longer. Login sessions expire after 30 days. Uninstalling the GitHub App stops all further collection.
Uninstall the GitSpider GitHub App at any time to revoke access and halt collection. Email us to request deletion of your stored data.
Questions: privacy@gitspider.com