Privacy

VibeHire is built so a developer’s real work can speak for them without handing over their code. This page explains, plainly, what stays private, what’s shared, and what we store.

What stays on the candidate’s computer

These are read locally to build the summary and are never uploaded:

• Source code, diffs, and commit contents
• Full chat transcripts with AI agents
• Plan files and internal notes
• File paths and raw repository names
• Any email addresses found in the code

What’s shared with the employer

Only a redacted, allowlist-only summary — built and checked on the candidate’s own machine before anything is sent:

• Counts, ratios, and durations (e.g. commits, sessions, how often they steer an agent)
• Category labels only — like feature, fix, or refactor — never the underlying text
• Behavioral-pattern counts, drawn from a fixed public list
• Commit IDs, repository names, and author identity are one-way pseudonymized

There is no free text, no code, and no file paths in what’s shared. A fail-closed check runs before sending — anything not on the allowlist is blocked — and the candidate reviews the exact summary first.

What VibeHire stores

• Candidates: the name, email, phone number, and optional GitHub link you provide when confirming a run, plus the redacted summary and the report generated from it — tied to the position that invited them.
• Recruiters: the work email used to sign in.
• Waitlist: the email submitted on the landing page.

We never receive raw code, diffs, or transcripts, so we can’t store them.

How reports are generated

The redacted summary is processed by an AI model (GPT-5.5) to produce the report. The model only ever sees the redacted numbers and labels — never raw code or messages. When there isn’t enough data, the report reads as “not enough evidence,” never a low score.

Your choices

Candidates approve the summary before anything is shared — and can simply choose not to run it. To request access to or deletion of your data, email privacy@vibehire.in.

Changes

If these practices change, we’ll update this page; the date above always reflects the latest version.