For schools and IT
What it does, what it can see, and what it never does
This page is for IT teams and administrators to understand how the extension works on a technical level. Everything below can be verified in the open-source code.
It does
- Read the Schoology grades pages the signed-in user can already see, using the browser's existing session.
- Work out what's missing, what's due and grade summaries locally, in the browser.
- Save results in the browser's local extension storage only.
It does not
- Ask for, store or see a Schoology password, API key or OAuth token.
- Send data to any server. There's no backend, no analytics and no tracking. The only network requests go to the school's own
schoology.comaddress. - Change anything in Schoology: no submissions, no edits, nothing posted.
- Use the Schoology API, or run on sites other than Schoology.
Data kept in the browser only
| What | Details |
|---|---|
| Latest grades | Course and assignment names, due dates, scores, Missing flags. Replaced on each refresh. |
| Daily log | One small summary per day (missing count, class grades), kept for about two school years, for trends and records. |
| Records, marks, settings | Personal bests, the family's "turned in" and "done" ticks, and family rules. |
Settings → Clear data removes all of it. Uninstalling the extension removes it too.
Review the code
The full source is public under the MIT license: the GitHub repository has the extension, its tests (with a mock Schoology server and made-up data), and the build. Questions are welcome. Use Send feedback in the extension or open a GitHub issue.
Why it helps students
It puts teacher-marked missing work first, the signal shown to reduce course failures when parents see it weekly.[1] It avoids surveillance-style designs: no alerts, rankings or reset-to-zero streaks. See the research.