Candidate data, handled with care. Encrypted, kept briefly and never used for training.
Interviews hold people's voices and careers. Here is how we protect them, who can see them and where they are stored.
Data handling. We keep less, for less time.
01Encrypted in transit and at rest
All traffic uses TLS, and data is encrypted at rest in the database and in file storage.
02Signed, expiring links
Recordings and CVs are private. Each view uses a signed link that stops working after a short time.
03Recordings deleted after 30 days
A daily job deletes interview recordings 30 days after they are made, or after 90, 180 or 365 days with the recording retention add-on. Transcripts and scores follow the workspace setting: 180 days after the role closes by default, from 30 days to 3 years.
04Never used for training
Candidate answers and recordings are never used to train AI models, ours or anyone else's.
05Personal details stripped
Names, phone numbers and other personal details are removed before an answer is sent for scoring.
06Zero retention at providers
Our AI and speech providers are set to keep nothing after a request and never to train on it.
Access. The right people, and a record of what they did.
Roles
Owners, recruiters, hiring managers and viewers each see only what their role allows.
Two-factor sign-in
Two-step sign-in is available to everyone. Workspace owners can require it for owners and recruiters.
Work account sign-in
Teams sign in with a link by email or with their Google, Microsoft or Apple account.
Audit log
Sign-ins, decisions, score changes and exports are logged with who did what and when.
Each company kept apart
Each company's data is isolated at the database level, and tests check that one company can never read another's.
Hardened by default
Security headers, rate limits and dependency checks protect every page and API.
Hosting. Singapore by default. The UK, Australia or the US on request.
Every workspace, unless its owner chooses another region.
Chosen per workspace when it is created, on Enterprise or by arrangement.
Singapore
Database on Neon in AWS Singapore (ap-southeast-1). The app on Vercel in Singapore (sin1). Files on Cloudflare R2 in Asia Pacific. Email from Amazon SES in Singapore.
United Kingdom
Database on Neon in AWS London (eu-west-2). The app on Vercel in London (lhr1). Files on Cloudflare R2 under its EU jurisdiction, so they stay in the European Union. Email from Amazon SES in London.
Australia
Database on Neon in AWS Sydney (ap-southeast-2). The app on Vercel in Sydney (syd1). Files on Cloudflare R2 in Oceania. Email from Amazon SES in Sydney.
United States
Database on Neon in AWS N. Virginia (us-east-1). The app on Vercel in Washington, D.C. (iad1). Files on Cloudflare R2 in Eastern North America. Email from Amazon SES in N. Virginia.
Moving a workspace
Settings > Privacy > Data location shows where a workspace is hosted. An owner can ask to move it: we copy every record and file, share a checksum report and wipe the source only after the owner confirms.
Background jobs run on Cloudflare Workers placed near the region's database. Some processing, such as the interviewer, speech to text, face checks and SMS, is done by the providers listed in our data processing agreement and may happen outside the region.
Responsible disclosure. Found a weakness? Tell us first.
If you think you have found a security issue in SeekIQ, email us with the steps to reproduce it. Please do not access or change other people's data, and give us reasonable time to fix the issue before you share it.
We will confirm that we received your report, keep you updated and credit you if you would like to be named.