Skip to content
Zevqi

Security

Security questionnaire answers

The questions a vendor review usually asks, answered as they are today. “No” means we have not built it yet, not that we are hiding it.

Data we handle

Do you receive or store customer source code?

Source code, diffs and commit messages never reach Zevqi. The command-line tool reads code on the developer machine and sends only what the security page lists.

No

What personal data do you store?

Each developer’s email and optional name, with timestamps, file paths and review results. The git scan stores authors as one-way hashes of their email, not the email.

Yes

Do you store personal data of people who are not users?

Only as a pseudonymous hash of a commit author’s email from the git scan. It is not reversible, but someone holding a list of candidate emails could test a guess.

Partly

Do you sell or share data with third parties?

Only the subprocessors listed on the security page touch team data, and only for the purpose shown there.

No

Can the customer delete their data?

The team owner can delete the team and everything stored for it from Settings. Payment records are kept separately, because accounting rules require it.

Yes

Is customer data used to train AI models?

Zevqi does not train models. With no key, no model is called. With a developer’s own key, the diff goes to that provider under that developer’s agreement.

No

Access and authentication

Do users sign in with SSO (SAML or OIDC)?

Not yet. Owners sign in with a one-time emailed code. SSO is on the enterprise roadmap.

No

Is there role-based access to the dashboard?

Two roles. The owner signs in and can change everything. The owner can invite people by email as read-only viewers, who sign in with a one-time code and cannot see keys or billing or change settings. There is no separate admin role yet. The shared dashboard link is still a bearer link: anyone who has it can view the page, so treat it like a password or rotate it.

Partly

Are credentials stored securely?

There are no passwords. Team keys and dashboard tokens are generated with 192 bits of randomness and stored only as SHA-256 hashes. Sign-in codes are stored as hashes, expire in 10 minutes, work once and lock after five wrong guesses.

Yes

Is there an audit log of administrative actions?

Not yet. It is on the enterprise roadmap.

No

Is multi-factor authentication available?

Sign-in is already by one-time code to the owner’s email, so the security of the mailbox is the security of the account. There is no second factor on top of it.

No

Infrastructure and application security

Where is data hosted?

The website and API run on Vercel. Team records are in Supabase Postgres. See the subprocessor table on the security page.

Yes

Is data encrypted in transit?

All traffic to zevqi.com is over HTTPS, provided by the hosting platform.

Yes

Is data encrypted at rest?

Through our database provider’s storage encryption. We do not add our own application-level encryption on top.

Yes

How is database access restricted?

Row-level security is enabled with no public policies, so only our server can read or write team data.

Yes

Have you had an independent penetration test?

Not yet. We test our own code with automated checks, and we welcome reports (see the disclosure section on the security page).

No

Do you have a vulnerability disclosure process?

Email hello@zevqi.com. We acknowledge within 2 business days. The command-line tool also has a SECURITY.md on GitHub.

Yes

Is the command-line tool open source?

Yes, MIT licensed at github.com/zevqi/zevqi, so a customer can read exactly what it sends. `zevqi scan --dry-run` shows an upload without sending it.

Yes

Compliance and legal

Do you have SOC 2 or ISO 27001?

Not yet, and we will not imply otherwise. We can walk through how our controls map to the common criteria during a review.

No

Will you sign a data processing agreement?

Yes. Email hello@zevqi.com and we will send one for you to review.

On request

Do you list your subprocessors?

On the security page: Vercel, Supabase, Resend, PostHog, Razorpay and, only if you add your own key, your model provider.

Yes

Where is the company based?

Noida, India. Payments are processed by Razorpay.

Yes

Do you have a business continuity or incident response plan?

Not a formal written plan yet. The tool is built so an outage never blocks a developer: hooks always exit successfully, and the pull-request check passes through on a server outage unless you ask it to be strict.

No

More detail

Where to look next

The security page lists exactly what is sent and stored. Your own questionnaire format is fine too: email it to hello@zevqi.com and we will fill it in with the same honesty.

Need something that is not here?

Tell us what your review requires. If we have not built it, we will say so.