Common Benchmark

Data-flow sheet: Standing

For IT security, privacy, and teaching-center reviewers · as of September 26, 2026 · questions: privacy@commonbenchmark.com

One paragraph. Standing is a browser application an instructor uses with a quiz export they already graded. In its default mode no student data leaves the instructor's computer: the file is parsed, student identifiers are replaced with local placeholders, and all statistics are computed in the browser. One optional step, which the instructor must turn on per quiz, sends de-identified answer text only (no names, IDs, emails, or sections) to an AI model provider for concept analysis and returns the result to the browser. Common Benchmark stores nothing from either step. The AI never assigns or changes a grade.

1. What data exists and where it goes

Data elementRead in browserSent to Common BenchmarkSent to AI provider (opt-in step only)Stored anywhere by us
Student name, LMS ID, SIS ID, email, sectionYesNeverNever (replaced by "Student NN" before the request)No
Per-student scores and totalsYesNeverPoints for each sent answer, keyed to the placeholderNo
Question text and points possibleYesNeverYes, for the questions the instructor selectsNo
Student written answersYesNeverYes, de-identified, for the questions the instructor selectsNo
Multiple-choice selectionsYesNeverNeverNo
The uploaded file itselfYes (in memory)NeverNeverNo
Instructor's institution selectionYesNot in the beta (no accounts)NeverNo
Instructor's email (beta sign-in)—Cloudflare Access sign-in log (email, time, IP)NeverAccess logs, per Cloudflare retention

"Never" means the application contains no code path that transmits the element; the request payload to the AI step is validated server-side and rejected if any student field is not a placeholder of the form Student NN.

2. The two steps

Step A — Score analysis (default). The instructor drops in a graded quiz export (Canvas Classic "Student Analysis" CSV, or any CSV with a column mapping). Parsing, pseudonymization, per-question statistics, and per-student standing run entirely in the browser (JavaScript, no server round-trip). The page can be printed; the printout carries a header stating that no student data was sent. Closing the tab discards everything.

Step B — Written-answer analysis (opt-in, per quiz). After reviewing the data-handling notes on screen and confirming that AI-tool use is permitted at their institution, the instructor selects which written questions to send. The browser builds a payload containing only: question text, points possible, placeholder student labels, answer text, and the instructor's score for each answer. Emails, phone numbers, and long digit strings inside answer text are additionally masked. The payload is sent over TLS to Common Benchmark's API, which validates it and forwards it to the AI model provider. The provider returns structured analysis (concepts missed, similar answers scored differently, ambiguous questions), which is passed back to the browser and displayed against the local placeholder-to-name lookup. Nothing is written to disk on our side.

3. Providers and locations

ProviderRoleWhat it seesRetention / training
CloudflareHosting (Workers), TLS, and beta access control (Access, one-time email code)Application files; request metadata; sign-in email for the beta allowlist; the opt-in payload in transitStandard edge logs; no payload storage by our configuration
Anthropic (API)AI model for the opt-in stepDe-identified payload described in Step BNot used for model training; retained up to 30 days for abuse monitoring, then deleted ◇ (verify against the provider's current API data terms before relying on this line)
Common BenchmarkOperatorNothing persisted from either step; support email if the instructor writes to usNo student data at rest, ever, in the beta

4. Controls the instructor sees

5. Security notes

6. Regulatory framing

FERPA. In Step A, education records never leave the instructor's device and no third party receives them. In Step B, the instructor transmits de-identified answer text; whether de-identified student work may be sent to a third-party AI tool is governed by the institution's own policy, which is why the application asks the instructor to confirm it. When an institution formally adopts the tool, Common Benchmark will sign the institution's data-processing agreement and act as a school official under its direct control.

Accessibility. WCAG 2.1 AA self-assessment and a VPAT/ACR are in preparation for the beta. HECVAT. A HECVAT Lite self-assessment is in preparation; the answers to the AI section follow from this sheet.