Privacy & Cookies

You submit code in one of two ways: by uploading a ZIP archive of your project, or by giving ProofCode the URL of a public GitHub repository, which it clones. The code is copied into a temporary workspace on our server, where the analysis runs.

Please do not upload secrets — API keys, passwords, or production credentials should never be part of a submission.

Analysis results are stored in a Supabase database: the project name and source, file counts, the issues found (file, line, severity, explanation), quality scores, health scores, test results, and verification history snapshots. Your project’s source files (text files only) are also stored with the project, so analysis, fixes, and verification keep working reliably over time — and they are deleted when you delete the project.

ProofCode uses Google sign-in, handled by Supabase Auth. When you sign in, Google shares your name and email address with us; the email identifies your account, and your projects are visible only to you. The workspace owner’s account can see every project. We never see or store your Google password.

Your code is sent to an AI provider only when you request an AI-generated fix for an issue. In that case the relevant code is sent to Google Gemini, or to OpenRouter if Gemini is not configured, so the provider can propose the fix. The deterministic scanner and the built-in patches run entirely on our server and send nothing anywhere.

If you add your own Gemini key in Settings, AI fixes run on your key instead of the server’s. Your key is stored only in your browser, is sent only with your fix requests so the request can be made, and is never stored on our server.

Deleting a project deletes its stored data — the project record, its issues, scores, and history — together with its stored file copies and its workspace copy from the server. There is no separate archive copy kept behind.

ProofCode sets no advertising, analytics, or tracking cookies, and your data is never sold. The site uses only functional browser storage: your theme preference and your Google sign-in session kept in your browser so the interface can call the API on your behalf — plus, only if you choose to add one, your own AI key, which also never leaves your browser except with your fix requests.

ProofCode is built by Ahmad Raza — Ahmad Digital Studio (ahmadrazaa.me).