What Gets Recorded

The whole point of Ducker is showing an employer how you worked, not just what you submitted. So the working session is recorded. Here is precisely what that means.

Recorded

• Your prompts to the agent, and its responses
• Tool calls the agent makes and what they return
• Code you write yourself, and code the agent generates — and which is which
• File changes, diffs, and changes you reverted
• Terminal commands and their output
• Tests you run and their results
• Application runs and database operations in the workspace
• Suggestions you accepted or rejected
• Timestamps, time spent, token usage, iterations, and errors
• Your final submission and workspace snapshots

Not recorded

• No webcam. Ducker never requests camera access.
• No microphone.
• No screen recording. Only what happens inside the workspace.
• No keystroke logging outside the workspace.
• No access to your other tabs, files, browsing history, or clipboard.
• Nothing after you submit. Recording ends with the attempt.

Reverting is fine

Reverted changes are recorded, and that is a good thing. Trying something, seeing it was wrong, and backing it out is engineering. It is not counted against you.

Where it goes

To the employer who invited you, as a report and a replayable timeline. It is stored in the European Union and kept for up to 24 months, or until the employer deletes it.

Your work is not used to train AI models.

Your rights

The employer who invited you controls your assessment data. Ask them first if you want it corrected or deleted, and write to privacy@ducker.ai in parallel — we will help them act on it.

Full detail is in the Candidate Privacy Notice.