What we collect
If you sign in: your email, plus name and avatar when you sign in with LinkedIn or Google. Your onboarding and settings answers: role, experience, country, language, time zone.
Runs: topic, mode, your questions and the candidate's answers (the transcript), scorecard, debrief, rating and its changes.
Technical: a hash of your IP address (the address itself isn't stored) for limits and abuse protection, an anonymous browser id in a cookie, the interface language. For our own visit statistics: which pages are opened, where the visit came from (a site or a link tag), the country by IP address and the device type. Only we see these statistics. If you allow analytics, Microsoft Clarity also runs (see “Cookies”).
Where it's stored
In a Supabase database and on Vercel servers. Interview text is processed by Anthropic models (Claude) to play the candidate and write the debrief.
How long we keep it
Transcripts: 12 months, then deleted. Aggregates (rating, level, leaderboard places): for as long as the account exists.
Who can see it
Only you see your transcripts. An administrator can see them for support and moderation. Public profiles never show transcripts.
How to delete
Settings → “Delete account” removes your profile, runs, transcripts and team memberships. In past weekly leaderboards you'll appear as “Deleted user”.
HiringAssist: the live interview copilot and the Chrome extension
Call audio is processed only after the interviewer presses “Connect the call” or invites the bot, and only until the interview ends. Before starting, the interviewer confirms the candidate was told about the transcription.
Audio is cut into short phrases and sent for speech recognition (OpenAI). We don't store audio recordings: only the transcript text, the hints and the notes. When the call goes through the bot, Recall.ai (EU region) joins it, and Recall.ai or Deepgram transcribe it.
The text, the vacancy and the CV are processed by Anthropic's models (Claude) to give hints and prepare notes. The copilot doesn't assess the candidate's emotions or personality and makes no hiring decisions. Our providers don't use this data to train models.
The Chrome extension stores only your personal access key in the browser. It receives a tab's audio only after you press “Connect this tab” and doesn't collect browsing history. On a Google Meet call page it reads the participants' names and the caption labels to know who is speaking; this is used only during a connected interview. It doesn't read other pages.
Only the interviewer who ran the interview sees its transcript and notes. Interviews, transcripts, notes and vacancies are kept while the account exists and are deleted with it; we delete a single interview on request at the address below.
Emails
Besides sign-in emails, HiringAssist sends a few service emails to your account's address: if no interview happened after you signed up, if a call didn't connect, after your first interview and at the end of the trial. Each one comes at most once; we send them through Resend.
You can unsubscribe with the link at the bottom of any of them or in your account settings. We send no ads or third-party mailings and share your address with no one.
Cookies
Necessary ones, without which the site doesn't work: sign-in, language, an anonymous browser id and where your first visit came from (for statistics, 90 days).
Analytics, only with your consent: Microsoft Clarity (Microsoft) records how the public pages of the site are used (clicks, scrolling, session replays, heatmaps) so we can make the site easier to use. Typed text is masked. Clarity never runs in the HiringAssist workspace, on the interview screen, in your profile or in the admin. You can withdraw consent at any time: “Cookie settings” at the bottom of the page.
No ad trackers.
Contact
info@pimbom.com