CODE SECURITY & PERMISSION BOUNDARIES

Privacy Policy

Last updated: August 2026

1. Source Code Protection & Zero Storage

Parity processes repository ASTs in memory on ephemeral sandboxes to generate migration Pull Requests. We never retain, store, or train models on your proprietary source code.

Source code fetched via the GitHub App integration is accessed strictly in ephemeral memory within isolated disposable sandbox containers to detect API calls, generate AST migrations, and run verification tests.

2. Information We Collect

  • GitHub Authentication Data: GitHub OAuth token, organization permissions, repository names, and default branch configurations.
  • API Dependency Metadata: Detected package names (e.g. `stripe`, `openai`, `twilio`), versions, and used API endpoints.
  • Billing Information: Billed via Stripe under PCI-DSS Level 1 compliance.

3. Disposable Execution Sandboxes

All build and test executions run in single-tenant disposable containers with zero shared persistent disks. Once a repair job completes or times out, the container and all cloned files are destroyed.