Test Candidates is run by Neuroworx Ltd, registered in England and Wales under company number 14612373. This page says where data is held, which other companies handle it, how long it is kept and how access is controlled. It describes the service as it runs today. The legal detail is in our privacy policy and terms. Last updated 19 October 2026.
Who is responsible for what
When an employer uses Test Candidates to assess candidates, the employer decides who is tested and how the results are used. It is the controller of that candidate data, and we process it on the employer's instructions. For employer accounts, billing, support and our website, we are the controller.
Where data is held
| Data | Where it is held |
|---|---|
| Candidate records, answers, scores, reports and assessment observations | Our application database, run by Fortrabbit on Amazon Web Services in Ireland (EU) |
| Employer accounts and workspace settings | Amazon Web Services in the United States (Ohio) |
| Candidate camera photos, only when an employer turns the camera on | A private Amazon Web Services storage bucket in the United States (Ohio). Photos have no public address and are viewed only through links that expire after a few minutes |
| Our websites, the employer app and the support hub | Netlify, served from its global network |
| Card details | Stripe. We never see or store full card numbers |
If your policy needs candidate data held only in the UK or the EU, email us before you start and we will tell you plainly what is and is not possible.
Who else handles data
These are the companies that process data for us. We update this list when it changes.
| Provider | What it does for us |
|---|---|
| Amazon Web Services | Hosts our database (through Fortrabbit), employer account records and camera photos |
| Fortrabbit | Runs our application servers and database on Amazon Web Services in Ireland |
| Netlify | Hosts our websites, the employer app and the support hub |
| Stripe | Takes payments and issues invoices |
| Postmark | Sends invitation, sign-in and notification emails |
| Cloudinary | Stores logos and images uploaded for company branding |
| Sentry | Error reporting from the app, with names, answers and other personal details removed before anything is sent |
| Optional Google sign-in for employers; Google Tag Manager and Analytics on our website, according to your cookie choices; Google Workspace for our support mailbox | |
| Microsoft | Optional Microsoft sign-in for employers; Microsoft Advertising tagging on our website |
| Xero | Accounting records for invoices and payments |
Slack, Microsoft Teams, Zapier and Make receive candidate names and unlocked results only when an admin in your workspace connects them. They act on your instruction and you can disconnect them at any time. Our check for cloud networks uses a database held on our own servers, so no candidate's address is sent to anyone.
Some of these providers process data outside the UK. Where that is a restricted transfer, we rely on the safeguards described in our privacy policy. Ask us for the detail that applies to your organisation.
How long data is kept
- Candidate records, answers, results and observations are kept until you delete them or close your account. An admin can delete a candidate at any time, and observations are deleted with the result they belong to. We do not delete recruitment data automatically, because the retention period is yours to set. We recommend deleting unsuccessful candidates' data six months after the decision, unless you have a documented reason to keep it longer.
- Camera photos are deleted automatically six months after they are taken, or earlier when you delete the candidate.
- Closing your account is done by email from an address on the account. We confirm before anything is removed, and you choose whether the data is deleted or kept for a period you name.
- Our own records, such as account details, support messages and invoices, are kept for as long as their purpose needs, including the statutory period for accounting records.
Access controls
- No passwords. Employers sign in with a single-use email link that expires after 15 minutes, or with a Google or Microsoft work account. Single sign-on through your own identity provider can be arranged for your email domain on request.
- Roles and teams. Admins control billing, people, integrations, branding and deletion. Members build assessments and read results. Teams limit what a person sees to the assessments in their teams, and someone with no teams sees nothing.
- One workspace. Every request is checked on our servers against the workspace it belongs to. The same rule applies to the API, webhooks, Slack and Teams: a locked result stays locked everywhere, and an id from another workspace is answered as if it did not exist.
- Candidates reach a test only through their invitation link and never see other candidates.
- Leavers. Removing someone from the People page ends their access at once. Disconnecting a sign-in provider signs out any other device. Regenerating an API key stops the old key immediately.
- API keys are visible to admins only. The secret is shown once, and each key is limited to 120 requests a minute.
- Encrypted connections. All traffic uses HTTPS. Webhooks are sent only to HTTPS addresses and every delivery is signed, so your system can check it came from us. Microsoft Teams webhook addresses are stored encrypted.
Scoring and integrity
- Tests are scored on our servers, not in the candidate's browser.
- Every test blocks copy and paste, records tab switches and time away from the test, and looks for signs of automated answering. Employers can also ask for full screen, vary question order and turn on camera photos. Candidates are told what is on before they start.
- We do not record video or audio, and we do not use face recognition or any automated analysis of photos.
- Observations are shown to the employer as context. They are not proof of misconduct, and no check can rule out outside help completely. See integrity checks in the support hub.
Availability
We aim to keep the service available at all times and we monitor errors so that faults are seen quickly. We do not guarantee a level of uptime, and no service level applies unless we agree one with you in writing. Our service commitments page says how we handle problems and how quickly we aim to reply.
Security reviews
If your security review needs written answers, email us and we will answer your questions in writing.
Data processing agreement
Email support@testcandidates.com to ask for our data processing agreement. It sets out our role as processor, the providers listed above, the measures on this page and how we help with candidate requests.
Candidate requests
Candidates can ask for a copy of their information, ask for it to be corrected, or ask for it to be deleted. Because the employer controls the assessment data, these requests normally go to the employer first. If a candidate contacts us, we help direct the request and support the employer in acting on it.
Reporting a security concern
Email support@testcandidates.com with "Security" in the subject line. Please do not test against accounts or candidates other than your own.