Process Flow privacy policy
This policy covers the Process Flow Chrome extension by Classwork Lab, which reads a Google Doc’s revision history and reports how the writing came together. The analysis runs in your browser. The extension has no server, no accounts, and no sign-in of its own. The Classwork Lab privacy policy covers the web app and does not apply here.
Last updated November 16, 2026.
What it reads
When you click the Process Flow icon on an open Google Doc, the extension asks Google for two things about that one document, using the Google session already signed in to your browser:
- The document’s revision history — the same record of edits that the document’s own File → Version history menu shows: what changed, when, and which collaborator made the change. This is why edit access is required; Google does not expose this to viewers or commenters.
- The document’s text — the plain-text export of the document, used to report how much of the finished text the revision history actually accounts for.
It reads only the document you have open and only when you ask it to. It does not run in the background, does not watch you type, and has no permission to list your other tabs or your browsing history. It never uses the camera, the microphone, or screenshots.
What it stores
Process Flow computes the report fresh each time you run it, so it keeps no library of past documents. While a report or replay is open, it hands the analysis between its own pages through the browser’s session storage for the extension, which Chrome clears when you close the browser. The replay removes its copy as soon as it has read it. Nothing is written to a file unless you print or save it yourself.
What it transmits
Nothing to us. The extension makes network requests to exactly one place: Google, for the revision history and text of the document you opened. There is no Classwork Lab server, no API key, no third-party service, no analytics, no error reporting, and no telemetry. Document content, student names, and the report itself never leave your machine.
The permissions it asks for
- Access to docs.google.com — to request the revision history of the document you are looking at, and to draw the replay over the page.
- Access to googleusercontent.com — Google answers the text-export request by redirecting to that address, so the request cannot complete without it.
- Storage — to pass the analysis from the popup to the report and replay pages, in the session storage described above.
- Scripting — to run the extension’s own code in the Google Docs tab you have open, which is how the replay appears over the document.
The reports you create
A report is about a person’s writing, so handle it the way you would handle their draft. Every finding separates what was observed from a hedged reading of it, with a confidence level and a question to ask, because revision history supports a conversation rather than a verdict: a large insertion can be a quotation, a move from another draft, or dictation, and work done on paper or in another app does not appear at all. If you print or share a report, that copy is a file under your control, subject to your school’s student records practices. What it needs and what it can’t do has the full list of limits.
Keeping and deleting data
There is nothing of yours for us to keep or delete: no account, no server, no stored documents. Closing the browser clears the session storage; removing the extension on chrome://extensions removes it entirely. Reports you printed or saved are yours to delete. Revision history itself belongs to the document in Google Drive; Process Flow only reads it and never changes the document.
Questions or data requests
Email hello@classworklab.com with privacy questions about Process Flow. Installation and use are covered on the Process Flow page.