Prove the process, not just the product.
ProveProcess helps instructors verify how a piece of academic work was created — using privacy-preserving process signals, never the content of what students write. It is not an AI detector, and it never accuses anyone.
Request a pilot Read our privacy policyHow it works
Students work in the tools they already use. ProveProcess records the shape of the work — not the words.
Work where you already write
A lightweight extension runs in Google Docs or VS Code while a student works on an assignment. No new app to learn.
Capture process, not content
It records privacy-preserving signals — counts, timing, and one-way hashes of the text. The writing itself is processed on-device and discarded.
A clear process report
Instructors see a process-strength summary — strong, moderate, weak, or not assessable — with the evidence behind it.
What ProveProcess is — and isn't
We built this to support fair assessment, not surveillance or accusation.
What it is
- A way to show that work developed gradually over time
- A privacy-first record of process signals
- Evidence an instructor can interpret in context
What it isn't
- An "AI detector" or plagiarism scanner
- A tool that reads or stores your writing
- A system that accuses any individual of misconduct
Your writing never leaves your device
We do not collect, transmit, or store the content of your documents. Text is read locally to compute counts and one-way SHA-256 hashes, then discarded. A hash is a fingerprint — it can show that content changed, but it can never be reversed back into your words.
When connected to Google Docs, ProveProcess requests only read-only access (documents.readonly), uses it solely to compute these privacy-preserving signals on-device, and never uses Google user data for advertising or to train AI models. See the full privacy policy.