Privacy Policy

We collect basic account information like your name and email when you sign in with Google or GitHub.

Payments are handled by Stripe. We never see or store your full card number.

We process the repository files and code you upload so we can run analysis.

We also collect product usage analytics, like feature use and session activity, to improve reliability and performance.

This is the most important part: your code is uploaded only so Quorium can analyze it and generate a report.

To run that analysis, we send code to multiple AI providers through their enterprise API tiers.

These providers do not use API data submitted through enterprise tiers to train their models.

Your code is permanently deleted immediately after analysis completes.

We keep only the analysis output, such as findings, scores, and recommendations.

We do not store source code in logs. Logs include metadata only, such as timestamps, file counts, and repository name.

Stripe: Receives billing and payment transaction data to process subscriptions and invoices.

Google and GitHub: Receive authentication requests when you sign in with OAuth and return identity details like your name and email.

AI Analysis Providers: Receive code and analysis prompts through enterprise APIs to produce analysis results. All providers operate under enterprise agreements that prohibit use of customer data for model training.

Vercel (or our hosting provider): Processes application traffic, infrastructure logs, and deployment/runtime data needed to host Quorium.

Uploaded code is deleted immediately after analysis finishes.

Reports are stored until you delete them or close your account.

Account data is retained while your account is active.

You can view your stored account data.

You can download your analysis reports.

You can delete your account and all associated data.

You can opt out of marketing emails at any time.

We use required session cookies to keep you authenticated.

We do not use tracking cookies.

We do not use third-party advertising cookies.

We protect data in transit with TLS 1.3.

We use encryption at rest, strict access controls, and audit logging.

For implementation details, see our Security page.

If we make material changes to this policy, we will notify you by email.

Continuing to use Quorium after changes are published means you accept the updated policy.