Security

Last updated November 17, 2026

This page describes how Larpy protects candidate data. If your security questionnaire asks something it does not cover, send it to security@getlarpy.com and we will answer in writing.

Hosting and data location

Interviews are run and scored on servers in Toronto, Canada. The database, the web application and recordings are stored in the United States. Code from a coding round runs in an isolated sandbox in Germany.

Encryption

Candidate data is encrypted in transit. The database and the storage that hold recordings, transcripts and evaluations are encrypted at rest.

Access control

Each customer’s data is logically separated. A customer can reach only their own roles and candidates, and that is enforced on every request. Account owners control who on their team has access.

Inside Larpy, access to production data is limited to the staff who operate the service. Administrative changes to a customer account, overrides of a recommendation and data exports are recorded in an audit log.

API tokens for integrations are read-only by default and can be revoked at any time.

AI and candidate data

Candidate data is used only to run and evaluate your interviews. It is not used to train AI models, it is not shared between customers, and our staff do not read it except to operate the service or when you ask us to look at something.

The AI model receives what it needs to conduct and evaluate the interview: the conversation, your role and criteria, and any material the candidate submits or chooses to share on screen. It does not receive the recording or the camera feed.

Larpy never rejects a candidate automatically. That decision is made by a person. Criteria that touch a protected characteristic, such as age, health or family status, are refused when they are written.

Demographic information a candidate volunteers for bias auditing is kept apart from interview data. It is not available to the interviewer or the evaluation, and it is reported only in aggregate.

Recordings

Candidates are told that the interview is conducted by AI and recorded, and they must agree before it starts.

Recordings are kept in private storage that is not publicly accessible. Signed-in members of your team play them through links that expire within minutes. A team member can also share a candidate’s report, including the recording, through a link that expires and can be revoked.

Retention and deletion

Recordings are deleted automatically after 90 days. Transcripts and evaluations are deleted after 12 months. You can delete a candidate sooner, and a candidate can delete their own recording, transcript and evaluation from their interview link.

When you stop using Larpy, we delete the candidate data we hold for you within 30 days of your request.

Code execution

Candidate code runs in an isolated sandbox with no network access and fixed limits on time and memory.

Subprocessors

We use a small number of providers for hosting, storage, speech, AI models, code execution and email. Each is bound by contract to use candidate data only to provide its service to us. The current list is available to customers on request and is provided with every agreement.

Incident response

If a security incident affects your candidates’ data, we notify you without undue delay, with what we know and what we are doing about it. The terms are set out in our data processing agreement.

Reliability

The service is monitored continuously, and alerts go to a person. An interview that cannot be scored is reported as unscored. It is never given a default score.

Reporting a vulnerability

Report security issues to security@getlarpy.com. We will not take legal action against anyone who reports a vulnerability in good faith, gives us reasonable time to fix it, and does not access or change other people’s data.

Questionnaires and documents

We complete security questionnaires and will walk your reviewer through the system on a call. Our data processing agreement and privacy notice are published on this site.

Security | Larpy