Privacy Policy
Last updated: September 28, 2026
Our Core Architectural Privacy Promise
ShipGauge never collects, transmits, or stores the body text of your LLM prompts, completions, embeddings, or context messages. This is enforced by architecture, not by a user-facing toggle.
1. Information We Collect
When you use the ShipGauge SDKs, REST Ingest API, or Web Dashboard, we only collect operational and billing metadata:
- LLM Execution Metadata: Model identifier (e.g.
gpt-4o-mini), input token count, output token count, latency in milliseconds, status codes, and user-assigned tags (feature_id,customer_id). - Account Information: Your email address, authentication credentials, organization name, and billing details processed securely via Stripe.
- CI & Integration Data: GitHub repository names, check-run statuses, and evaluation metrics uploaded through the CLI or GitHub Action.
2. How We Use Information
We use collected metadata strictly to provide core ShipGauge services:
- Calculating per-feature and per-project cost trends.
- Executing pull request CI eval gates and regression comparisons.
- Enforcing budget limits and firing webhook/Slack alerts when thresholds are reached.
- Managing subscription tiers and usage quotas.
3. Data Retention & Deletion
Event metadata is retained according to your plan tier (7 days on Hobby, 90 days on Pro, 1 year on Team). You can trigger full account data deletion or export your audit logs at any time from your Account Settings.
4. Sub-processors & Security
We host our platform on industry-standard, encrypted cloud infrastructure (Cloudflare, Supabase, Stripe). All communications use TLS 1.3 encryption in transit.
5. Contact Us
If you have questions about our privacy practices, please contact us at privacy@shipgauge.dev or visit our Security Documentation.