Privacy Policy
Last updated: September 1, 2026 • Effective immediately
1. Zero AI Model Training Guarantee
We do not use your code, pull request diffs, commits or repository metadata to train AI models. Your chosen cloud provider or Ollama operator controls its own processing and retention policies.
2. Code Handling, Storage & Deletion
When a GitHub webhook triggers a review job:
- Code diffs are fetched securely over TLS directly from the GitHub API using temporary installation access tokens.
- To give the AI the code surrounding your changes, we also read repository files reachable from the files you edited. Those files are encrypted at rest with AES-256-GCM, using a unique initialization vector and per-record key derivation for each file.
- Cached files are stored under a content-addressed fingerprint rather than by path, and are scoped per repository. Files are never shared between repositories or customers.
- Cached files are kept for as long as your repository stays connected to PullPilot, and are deleted when you disconnect or uninstall the GitHub App.
- Review jobs themselves (status, findings, and metadata) are retained according to the job retention period described in section 4.
Deleting a repository, disconnecting the GitHub App, or uninstalling it removes its cached file content. See section 4 for how to request deletion of your data.
3. Encrypted API Key Vault
If you choose to provide custom API keys (e.g. for OpenAI, Anthropic Claude, or Google Gemini), your keys are encrypted at rest using AES-256-GCM with unique per-record initialization vectors and scrypt key derivation. Plaintext keys only exist in worker memory for the milliseconds required to complete the API request.
4. Data Collected & Stored
We collect and store only the minimal operational metadata required to provide the service:
- Account Info: Your GitHub user ID, username, and avatar URL provided via GitHub OAuth.
- Installation Data: Connected repository IDs and names authorized by your GitHub App installation.
- Audit Logs: Timestamps, status (e.g. completed/failed), and high-level finding summaries (file path, line number, issue description) displayed on your dashboard.
5. Third-Party Service Providers
Review diffs and selected context are sent to the configured AI provider. Cloud provider connections use HTTPS. An operator-configured Ollama endpoint may use HTTP on a trusted local network; the operator controls that connection and server. Review the selected provider or operator policies before connecting a repository.
6. Contact Us
If you have questions about this privacy policy or our data security practices, please contact us at privacy@shehzaib.com.