Your data

Corvis is operated by Dhruv Kumar, a sole proprietor based in Ludhiana, Punjab, India. For the personal data described here, Dhruv Kumar is the data controller. For anything about privacy, write to hello@usecorvis.com.

• Account: your name, email address and profile picture from GitHub when you sign in, and the workspaces and teams you belong to.
• Connected services: the access keys you give Corvis (stored encrypted), and the events those services send us, such as code pushes, pull requests, failed payments, uptime checks and AI usage.
• Conversations: your phone number and chat ids if you link Telegram, WhatsApp or phone calls, the questions you ask, and transcripts of voice notes and calls.
• Billing: your plan, subscription status, name, email and country. Card details go to Paddle and never reach us.
• Waitlist: your email address and the date you joined.
• Technical: IP addresses, held in memory for up to an hour to stop abuse of the free scan and waitlist, never written to disk.

Corvis is built to see secrets without keeping them. Detected secrets are never stored, logged or shown in full: we keep only a redacted preview and a one-way fingerprint.

When you scan a public repository we download its current code from GitHub, scan it in memory and keep only the summary (grade and counts) for ten minutes so repeat visits are fast. Public results never reveal where a secret is. A live key found this way is added to the Corvis network as a one-way fingerprint marked "public", with no repo or file name.

If you turn on pull request reviews, failing build fixes or feature briefs, Corvis sends the pull request diff, the end of the failed build log or your request to Anthropic's API to write the review, diagnosis or brief. Secrets are redacted first. Corvis keeps the comment, diagnosis or issue it wrote, not your code.

When a key leaks in a repo Corvis watches, or a bad package is flagged in your app, Corvis records a keyed one-way fingerprint of the key, or the public advisory id, and when it was seen. Other customers only ever see a count, never your name, repo, code or the key. You can stop sharing any time in Settings.

• To run the service you signed up for: watching your apps, alerting you, fixing what you allow (performance of our contract with you).
• To keep Corvis and its users secure and prevent abuse (our legitimate interests).
• To bill you and keep records that tax law requires (legal obligation).
• To send product news, only if you opted in, and you can opt out at any time (consent).

We never sell your data. We share it only with the providers that run Corvis, and only what each one needs:

• Paddle.com, our Merchant of Record, which processes orders, payments, taxes and invoices;
• Vercel (hosting) and Neon (database);
• Anthropic (AI analysis and answers) and Groq (voice note transcription);
• Telegram, Meta (WhatsApp) and Twilio (phone calls), when you use those channels;
• GitHub and the other services you connect, to act on your behalf.

We may also share data with professional advisers, or with authorities when the law requires it.

Account and workspace data is kept while your account is open and deleted within 30 days after you ask us to close it. Uptime check history is kept for 35 days, scan summaries for ten minutes, and abuse-prevention IP addresses for an hour. Billing records are kept by Paddle and by us for as long as tax law requires.

Our providers store and process data in the United States, the European Union and other countries. Where data leaves your country, we rely on the providers' standard contractual clauses or equivalent safeguards.

You can ask us to access, correct, delete or export your data, to restrict or object to how we use it, and you can withdraw consent at any time. Email hello@usecorvis.com and we'll reply within one month. You can also complain to your local data protection authority.

Everything travels over HTTPS. Access keys for your connected services are encrypted at rest with a key kept separate from the database, Corvis asks for the narrowest permissions it needs, and every action it takes is recorded in your audit log.

Corvis uses only essential cookies: one to keep you signed in, and short-lived ones that protect sign-in, remember a team invite or the plan you picked. No advertising or tracking cookies.

If we change this policy we'll post the new version here first, and email account owners about significant changes.