Privacy Policy
Last Updated: November 11, 2026
This Privacy Policy explains how GitSeed ("we", "us", or "our") handles information across our open-source self-hosted platform, our website, and our official native desktop, mobile, and wearable client applications.
1. Summary of Principles
- Self-Hosted Core = Zero Telemetry: The open-source GitSeed control plane, stage runner, CLI, and MCP server contain no telemetry, no analytics beacons, and no call-home tracking.
- Your Code & Secrets Stay on Your Infrastructure: Source code, prompts, specifications,
plans, diffs, and encrypted credentials (
GITSEED_SECRET_KEY) reside exclusively on the servers and databases you operate. - Cookieless Website Analytics: Our public website uses Cloudflare Web Analytics, which is privacy-first, uses no cookies or tracking storage, and does not fingerprint or track individuals across sites.
- No Sale of Data & No Model Training: We never sell, rent, or monetize personal data or source code, and we never use your source code or prompts to train AI models.
2. Self-Hosted Open-Source Platform (gitseed)
When you deploy the open-source GitSeed platform via Docker Compose, Kubernetes/Helm, or source:
- Data Controller: You (or your organization) are the sole controller and custodian of all data stored in your PostgreSQL database, Valkey/Redis instance, and runner containers.
- No Outbound Telemetry: GitSeed does not transmit usage metrics, crash reports, repository metadata, prompts, or user identities to us.
- Third-Party Integrations Configured by You: Your self-hosted instance only communicates with external services that you explicitly configure, such as Git providers (GitHub, GitLab, Bitbucket) and AI model providers or CLI runtimes (Anthropic/Claude Code, OpenAI/Codex, Google Gemini, Antigravity, xAI Grok, or local Ollama/vLLM endpoints).
3. Native Desktop, Mobile & Wearable Clients
When you use official GitSeed native client applications (for macOS, Windows, iOS, iPadOS, watchOS, Android, or Wear OS):
- Direct Connection to Your Server: The client applications connect directly to the self-hosted GitSeed server URL that you configure. Credentials and session tokens are stored locally on your device using platform-native secure storage (iOS/macOS Keychain, Android Keystore, or Windows Credential Manager / DPAPI).
- Optional Mobile Push Notification Relay: If you enable mobile push notifications on your
self-hosted server (
MOBILE_PUSH_RELAY_URL), your server encrypts APNs/FCM device push tokens at rest using HKDF-SHA256 / MultiFernet and dispatches minimal, HMAC-SHA256 signed notification payloads (event type, seed number, stage name, and non-sensitive notification text) so Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) can wake your device. Source code, repository diffs, prompts, and secrets are never included in push notification payloads, and relay requests are forwarded transiently without persistent storage. - Crash Reports & App Store Diagnostics: If you opt in to sharing crash diagnostics through Apple (App Store / TestFlight) or Google Play, we may receive anonymized crash stack traces and device model/OS version metadata solely to fix bugs and improve stability.
4. Website & Cookieless Web Analytics
When you visit our public website:
- Cloudflare Web Analytics: We use Cloudflare Web Analytics to understand aggregate,
de-identified website traffic (such as page views, referring websites, country-level geography, and browser
type). Cloudflare Web Analytics does not use cookies, does not use browser
localStorageorsessionStoragefor tracking, does not collect or persist client IP addresses for analytics profiling, and does not track visitors across websites. - Local Theme Preference & Public Assets: The website stores a single
gitseed_themekey (darkorlight) in browserlocalStoragesolely to remember your display preference, loads static web fonts from Google Fonts, and queries the public GitHub repository API to display the current star count. - Optional Release Updates Signup: Emails are collected only when you voluntarily submit your address in the website’s release-updates form (stored in Cloudflare D1 alongside a timestamp and approximate 2-letter country code from Cloudflare’s edge header, without storing your IP address). Submitted emails are used solely to send GitSeed release notes and major updates, are never sold or shared for marketing, and are deleted promptly upon unsubscribe or request.
- Security & CDN Logs: Our DNS, CDN, and DDoS protection provider (Cloudflare) and source code host (GitHub) process standard HTTP request metadata transiently to deliver web pages and protect against abuse (including salted, non-reversible rate-limit hashes on form endpoints).
5. Data Retention & Your Rights
- Self-Hosted Data: You have complete control over all data stored in your self-hosted GitSeed PostgreSQL database, Valkey store, and container volumes, and may modify or delete it at any time.
- Device & Push Tokens: You can revoke device Personal Access Tokens
(
DELETE /api/v1/auth/tokens/{id}) and unregister mobile push devices (DELETE /api/v1/auth/push-devices/{device_id}) at any time from the GitSeed Web UI, CLI, or mobile app settings, or by uninstalling the app. - Privacy Requests (GDPR / CCPA / Global): Depending on your jurisdiction, you may have the right to request access to, correction of, or deletion of any personal information we hold about you (such as an email address submitted via our release-updates form, support, or GitHub).
6. Contact Us
For privacy questions or requests, please open an issue or discussion at github.com/gitseed-dev/gitseed or see SECURITY.md.