How we protect candidates and the teams that run interviews, described as it works today.
Less data in the first place
No recordings
In the app, speech becomes text on the candidate's computer; in a browser, the browser's speech recognition does it, or the device where the browser has none. Intaviu never receives or stores camera pictures or voice recordings, only the text.
Only the place
When an interview needs the candidate's location, we keep the state and country, never the exact position.
No card numbers
Payments go through Paystack. We never see or store full card numbers, and we check the signature on every payment notice from Paystack before acting on it.
Accounts and access
Sign-in
Intaviu runs its own sign-in: accounts and passwords are held by Intaviu itself, and passwords are stored only as salted hashes. New passwords are checked against lists of passwords exposed in breaches. You stay signed in with a cookie only this site can read, and every request to the Intaviu API carries a sign-in token that lasts a few minutes and that our server checks.
The desktop app
The app signs in through your browser and you confirm it with a code, so your password is never typed into the app.
Workspaces
A team's interviews, candidates and files belong to its workspace, and only its members can reach them. Owners manage members and billing.
One interview, one token
During an interview, the room talks to the interviewer with a short-lived token that works for that one interview and carries no account details.
Limits on public endpoints
What works without signing in, such as looking up an interview code or sending a confirmation email, is limited in how often it can be called.
Keys stay on our servers
The keys for the AI, video and payment services live only on our servers, never in the website or the app.
Files
Checked by what they are
Files are checked by their content, not their name. Only PDF, Word, text and PNG, JPEG or WebP images are accepted, up to 10 MB each; scripts, archives and web pages are refused. Older Word files, which can carry macros, are accepted only from the interview creator.
Downloaded, never opened in the page
Files always download as attachments, with headers that stop browsers from guessing their type or running anything in them.
Information, never instructions
The interviewer treats files and answers as information about the candidate and doesn't follow instructions hidden in them. We test that telling the interviewer what to score doesn't raise a score.
Encryption in transit
The website and the API are served over HTTPS, and in production browsers are told to use HTTPS only (HSTS). Other sites can't show our pages in a frame, and webhooks we send are signed so your systems can check they came from Intaviu.
AI and video services
Interview text and the text read from files go to the language model service that runs the conversation and the scoring. In a video interview, only the interviewer's synthesised voice goes to the video service. The privacy notice says who processes what.
Keeping and deleting data
Each workspace chooses how long to keep candidate records: 3, 6, 12 or 24 months after the interview, or until the team deletes them. Expired records, with their interviews, transcripts, notes and files, are deleted every day, never while the candidate is still interviewing. A team can delete a candidate's data at any time.
Activity log
Each workspace keeps an activity log of what happens in it, such as interviews created or changed, candidates added or deleted, files added and changes to members.
Report a security problem
Email [email protected] with what you found and how to reproduce it. Please don't access other people's data or disrupt the service while you look.