What we capture, and what we never will

What is captured during an assessment

• Activity within the assessment workspace tab: documents opened, searches run, edits made, and the artifact history.
• Microphone audio for think-aloud, where the candidate has chosen the spoken path. Olive processes it: what is said is transcribed, and how it is said is read too. Typed annotation is an equal path to the same assessment and captures text instead.
• The candidate's AI exchanges, as added to the session transcript from the workspace panel.
• Answers to the questions asked aloud during the assignment, spoken or typed.
• Debrief responses, spoken or typed.

What is never captured

• Webcam or any camera. There is none in the product.
• Room scans, screen area outside the assessment workspace, or any other browser tab or application.
• Biometric identifiers of any kind, including voiceprints and facial geometry.
• Keystrokes outside the assessment workspace.

What is never scored

Prose quality, prompt syntax, tool trivia, completion speed, how a candidate sounds, and the volume of AI usage. What a voice carries helps the reviewer understand the work, and nothing from it is used to identify anyone. Nothing drawn from how a candidate sounds enters the six findings, and none of it reaches an employer as a rating.

Retention and deletion

Assessment records are kept while a session is reviewed and for as long as the employer's account holds them. Deletion is asked for rather than automatic, and a request opens a 30-day window before anything is removed.

The delay is deliberate, not latency being excused. A deletion that fired instantly could not be withdrawn, and a record somebody is obliged to keep is far easier to notice before it is gone than after. The request can be withdrawn at any point inside the window, and its state is visible the whole time — a deletion nobody can observe is indistinguishable from one that never happened.

• Requesting it: from the dashboard, or by writing to support@hr.olive.is.
• What it reaches: the session, its events, the AI exchanges, the deliverable history, the capture, the think-aloud audio and its transcript, the released report, and the reviewer's private integrity notes with it.
• When it runs: on the first scheduled pass after the 30 days elapse.
• Immutable while it lives: a released result carries rubricVersion, scorerVersion and bankVersion and cannot be re-saved or edited.

Taking a copy

Every released report can be exported in two forms: a self-contained readable file that opens in any browser and prints to PDF, and an archival JSON file carrying the version strings on every finding. Employers can export every released report at once; a candidate can export their own.

The readable file fetches nothing — no stylesheet, no font, no image — so it still opens years later from a disk with no network. That matters most for candidates, who have no account: access to the report lives with the browser session it was taken in, so the downloaded copy is the one that survives a cleared cache.

Human review

Every result is reviewed by a person before an employer sees it. Candidates are told this before starting, and it is stated on the report. A model drafts a first reading of each session for the reviewer, and the draft is not stored; the reviewer writes or edits every finding and decides what is released.

Candidate rights

Candidates are granted the identical report the employer receives, free, as soon as a reviewer releases it, and can download it in both forms from the report itself. One limitation worth stating plainly: a candidate does not make an account, so in-app access is tied to the anonymous session in the browser they used — a different device or cleared storage loses the link to it, which is exactly why the download exists and why the report page says so. If it is lost anyway, write to support@hr.olive.is. Requests for access, correction or deletion go to the same address.

This page

This is a product privacy summary written to be readable, not a substitute for the contractual data-processing terms that accompany a paid account. Where the two differ, the contract governs — and if you find a place where they differ, tell us, because that is a bug.