Does LeetCode Record Your Screen or Webcam?

No. As of September 9, 2026, LeetCode documents no screen recording and no webcam capture on any surface: not in contests, not in practice, not in Mock Assessment, and not as a stored artifact of LeetCode Interview. What LeetCode does keep is a keystroke-level Code Replay of contest submissions, and what LeetCode Interview does is stream your camera and microphone live to the interviewer. The privacy policy names IP address and cookies as the collected data and nothing else.

What the privacy policy lists

LeetCode's privacy policy, last modified December 13, 2017, is the only first-party inventory of collected data. It says LeetCode collects "personally identifiable information, in the form of Persistent Identifiers, including IP Address," uses "session ID cookies," and then states: "Through our services and site, no other personal information is collected and the persistent identifiers are not used or disclosed to contact a specific individual."

There is no mention of video, audio, images, screen content, or biometrics. The policy predates Code Replay and LeetCode Interview, so it is incomplete as a description of current features, but it is the document LeetCode publishes, and it claims nothing beyond identifiers and cookies.

Contests: a replay of the editor, not of you

The one behavioral record LeetCode documents is Code Replay. The feature release notes introduced it in May 2025, "Now you can replay your contest performance from the Contest Ranking," and extended it in May 2026 with "editor activity status information."

Code Replay is a recording of what happened inside the LeetCode editor: the order in which characters arrived and, since May 2026, some indication of when the editor was active. It is public from the ranking page. It is not a screen capture; nothing outside the editor is in it. The contest rules require no camera and no screen share, and enforcement runs on code similarity, as described in how LeetCode detects contest cheating.

LeetCode Interview: live video, no documented recording

LeetCode Interview does use your camera and microphone, because it is a call. The launch post describes "Video and voice chat along with code collaboration. See, hear, and code with your candidates all in one place," and the product page describes "advanced WebRTC technology plus LeetCode's in-house Socket service."

Two things follow. First, the browser will ask for camera and microphone permission when you join, and the interviewer sees and hears you for the length of the session. Second, LeetCode documents nothing about storing that stream. No recording feature, no playback, no retention period appears on the product page, the launch post, or the release notes. Whether the session is recorded is therefore an employer question: ask before the call, and expect the answer to come from the company, not from LeetCode. What interviewers can see when you share your screen applies if the interviewer asks you to share beyond the editor.

Practice and Mock Assessment: nothing

Practice problems and Mock Assessment request no camera and no screen permission. A browser cannot open either without a prompt, so the absence of a prompt is a reliable indicator. LeetCode ships an AI assistant into the practice editor; it is not monitoring you there.

If a camera turned on, you were not on LeetCode

A webcam prompt, a screen-share prompt, a monitor check, or an installer means the assessment is on another platform. Those features are documented by HackerRank, CodeSignal, and Codility, and their rules apply. What a LeetCode online assessment actually is shows how the invitation reveals the real platform, and the HackerRank proctoring inventory covers what the most common one captures.

What this means for candidates

On leetcode.com, your screen and camera are not recorded. In a contest, the editor's history is public and the rules ban outside help. In a LeetCode Interview, a person sees and hears you live, and any recording is the employer's to disclose. If a permission prompt appears that this article says should not, check the domain before you click allow.

The full inventory by surface is in what LeetCode records across contests, Interview, and mock tests.