Privacy Policy

At DiffVet, operated by [COMPANY NAME] (“we”, “us”, or “our”), we believe privacy and data security are fundamental requirements for developer tooling. This Privacy Policy describes how we collect, handle, protect, and process information when you use our web application, GitHub integration, and Model Context Protocol (MCP) server.

1. Information We Store

We practice strict data minimization. We only store the minimal operational metadata required to deliver and meter our service:

• GitHub Profile Information: When you authenticate via GitHub OAuth, we receive and store your public GitHub username, avatar URL, and GitHub user identifier.
• Email Address: Your primary verified email associated with your GitHub account, used solely for account identification and essential transactional communications.
• Hashed API Keys: API keys generated for Pro MCP access are hashed using irreversible SHA-256 before storage. Plaintext API key secrets are never stored in our database and cannot be recovered if lost.
• Usage Counts: An aggregate counter of checks performed during the active calendar month (e.g., 5/20 or 142/2,000) to enforce plan quotas and display in your dashboard.
• Masked-Item Counts: Aggregate counts of credentials, tokens, or PII instances detected and redacted (e.g., items masked this month) for security auditing in your dashboard.
• Payment and Subscription Data: Handled entirely by our third-party merchant of record and payment provider. DiffVet never receives, stores, or processes complete credit card numbers, CVVs, or billing street addresses. We only retain the external customer ID, subscription ID, and subscription status (active, past due, cancelled).

2. Code and Diff Processing

The security of your intellectual property is our top priority:

• Processed in Memory Only: Source code snippets, unified diffs, pull request payloads, and review questions sent via /check, GitHub webhooks, or the /mcp endpoint are held transiently in RAM during analysis and discarded immediately upon completion.
• Never Stored on DiffVet Systems: We do not log, persist, or cache customer code on any DiffVet storage medium or database.
• Model Processing and Training: Code is processed by the Google Gemini API. On Google's free API tier, Google may use submitted content to improve its services per its terms; on the paid tier it does not. We are moving to the paid tier before launch. DiffVet itself never uses your code for training.

3. Pre-Analysis Secret & Personal Data Masking

Before any submitted code or diff leaves our execution environment to be analyzed by the reasoning engine, it passes through our integrated security scanner:

• The scanner automatically identifies sensitive credentials including AWS keys, GitHub tokens, Stripe secrets, generic API keys, private keys, password assignments, emails, phone numbers, and national IDs.
• Every detected item is replaced in-memory with a fixed neutral mask (e.g., [REDACTED:stripe_key]), preserving diff line counts and syntax before model inference.
• Masking is best-effort: automated scanners cannot catch every custom format or obfuscated credential, so any secret committed to version control should always be revoked and rotated immediately.

4. Cookies and Local Storage

DiffVet uses only essential first-party cookies necessary for authentication and session management:

• diffvet_session: A secure, HTTP-only, encrypted session cookie used to maintain your logged-in state.

We do not use third-party tracking cookies, advertising beacons, or cross-site behavioral analytics scripts.

5. Data Deletion on Request

You have the right to request deletion of your account and all associated operational data at any time. Upon receiving a verified request sent from your registered account email to [CONTACT EMAIL], we will permanently delete:

• Your user account record and GitHub profile association;
• All associated API key hashes and webhook installation records; and
• All historical usage meter counts and audit tallies.

Account deletion requests are processed within thirty (30) business days.

6. Governing Law

This Privacy Policy and any disputes related to privacy or data protection are governed by the laws of [JURISDICTION].

7. Contact and Inquiries

For privacy questions, data protection requests, or deletion inquiries, please contact our team at [CONTACT EMAIL].