Legal
Effective date: November 13, 2026. This policy describes how Provix collects, uses, and protects information when you sign in, connect a GitHub repository, run a security or architecture scan, or open a fix pull request.
Provix is an automated Next.js and Supabase code security and architecture auditing platform. It scans repositories you connect, reports findings, and can open verified fix pull requests. Provix is not a hiring marketplace, talent network, or recruiting service.
When you create an account, Provix stores the sign-in details needed to identify you, such as your email address and the account record created by our authentication provider.
When you install the Provix GitHub App, we store the installation and the repository names you connected so we can tell which repos your account may scan.
When you run a scan or open a fix pull request, we read repository files from GitHub for that request. A personal access token you paste is used for that request. We also store records of fix pull requests we open, such as the repository, file path, and pull request reference.
We collect ordinary product logs, such as pages you open, errors, and browser type, so we can run and debug the service.
We use this information to sign you in, scan repositories you are allowed to access, show security and architecture findings, and open fix pull requests you request.
We do not sell personal information. We do not publish your repository contents as a public profile or directory listing.
We may use aggregated, de-identified usage data to understand which parts of the product fail and to improve scans and fixes.
Repository source code is processed ephemerally for static analysis, bounded AI-assisted remediation, and pull request generation. File contents are read for the active request, used to produce findings or patches, and are not retained as a permanent code archive at rest on Provix systems.
Provix does not use your repository code to train AI models. Any model provider involved in a remediation request receives only the context needed for that request and is not authorized by Provix to retain your private code for model training.
We may keep limited operational metadata (for example repository name, file path, finding category, and pull request URL) so your workspace can show scan history and opened fixes. That metadata is not a copy of your full repository.
Supabase stores accounts and the GitHub installation records tied to your user.
Vercel hosts the application.
GitHub receives API calls to list files, read content, and open pull requests on repositories you connect.
Those providers process data to deliver their services and have their own privacy terms.
Traffic to Provix uses HTTPS. Account passwords are handled by the authentication provider; the application does not keep raw passwords.
We keep account and installation records while your account is active, and pull-request records so the workspace can show what was opened. You can ask us to delete your account data, except where we need to keep a record for security, fraud, or legal reasons.
You may ask to access, correct, or delete personal information we hold about you.
Email support@getprovix.com. We will respond within a reasonable time.
If we change this policy, we will update the date on this page.