Technical documentation

How the copy/paste block works

We intercept the paste, copy, cut, drop, and right-click events on text response fields client-side, plus the equivalent keyboard shortcuts (Ctrl/Cmd+V, Shift+Insert). It's an effective deterrent against casual copy/pasting, but like any client-side control it can be bypassed by a sufficiently motivated user (devtools, browser extensions, manually retyping text prepared elsewhere).

How the integrity score works

The score (0-100) is a heuristic computed from these signals, recalculated server-side on every submission:

• Text that appeared "in one block" (>40 characters in <100ms): a possible paste-block bypass.
• Typing cadence that's unusually regular (low variance between keystrokes).
• Little to no editing/backspacing on long answers.
• An anomalous characters-to-time ratio (too fast to be a plausible human typing speed).
• Number of blocked paste attempts on the same question.

This score is not proof that a piece of text was or wasn't written by an AI: it's a probabilistic signal meant to help you prioritize which responses to review manually. Both false positives (people who type unusually evenly, assistive-technology users) and false negatives (someone manually retyping AI-generated text) are possible.

Third-party AI-detection API: planned for a future Pro release (e.g. GPTZero or Originality.ai as an additional signal). Not available yet.

Turning the heuristic off for accessibility

Every form's settings include a toggle to disable the pattern-detection heuristic, intended especially for forms aimed at people using assistive technologies, where natural typing patterns can differ significantly from the average.