Privacy & product notes

This page describes the current evaluation release, version 1.9.0. It is a description of product behavior, rather than a district compliance certification or a complete legal privacy policy for a future hosted service.

This website

The pilot planner generates a text checklist in your browser. The pilot inquiry button opens your email app with an editable draft addressed to sales@classguard.org. You review and send the email yourself. This website does not submit your form entries to a server, create an account, or automatically send email. No analytics script or third-party advertising script is included in the website source. Hosting-provider infrastructure may process normal website requests.

Web filtering

The extension applies configured browser domain rules. It includes custom allow and block lists, category rules, an education allowlist, and an optional .edu rule. The extension does not collect browsing history or send tab URLs to the pairing server. During a website-restricted class, it checks current HTTP/HTTPS tab URLs locally to redirect pages outside the teacher’s list. Teachers can set a temporary website allowlist for a scheduled class period. It remains after the sharing page closes; an extension background poll updates or releases it when the teacher changes policy or ends the class. If the server is unreachable or Chrome restarts, the last list stays until scheduled expiry. Class metadata is stored locally and the server credential stays in Chrome extension session storage, which clears on browser exit. The district should inspect the source and configure policies that fit its requirements.

Local HTML game inspection

The installed extension reads bounded portions of accessible page content and checks script metadata, known game embeds, controls, and scoreboards locally. It observes page changes and rechecks policy. Full HTML, page text, input values, and URLs are not uploaded to a remote classifier or pairing server. Boolean/count signals pass only to the extension worker. Short detection reason codes stay in Chrome session storage for the blocked-page explanation, displayed for up to two minutes and cleared on navigation, tab close, or browser exit. This does not create a browsing-history log or HTML archive. Administrators can disable inspection or exempt trusted activity domains; domain and class rules still apply. Heuristics can miss disguised games and flag legitimate educational activities. Page code may run before detection because inspection follows loading. Protected browser pages, closed shadow DOM content, and inaccessible frames are outside the scanner’s reliable coverage.

Classroom screen sharing

Screen sharing is required for active participation in a teacher-created monitored class. After approval, students must establish sharing within 60 seconds using Chrome’s native picker. The teacher viewer must confirm a received screen before participation becomes active. Canceling the picker, stopping the stream, or losing the screen connection ends the class session. Students must rejoin and share again to participate. Chrome’s screen prompt and Stop control remain available; this requirement does not lock the device or enforce attendance in unrelated software. Teachers can remove students or close the class. The current implementation has no screen recording feature and does not request microphone or camera capture.

Live video is transmitted over WebRTC. A school-configured TURN relay may carry media when a direct connection is unavailable. The pairing server holds temporary class and signaling metadata in memory. For retention details and deployment configuration, read the included server guide.

District roster and enrollment

The downloadable school server supports CSV import of up to 20,000 students. IDs, names, optional emails, class groups, and hashed enrollment codes are stored in its private roster file and persist across restarts. Administrators can download raw personal codes for distribution; code generation replaces earlier codes for future entries. The installed extension saves a student’s code locally on that device. Browser previews keep it in tab session storage. Enrollment links use fragments, removed from the address bar after filling the form. Codes are bearer credentials, not verified Google or email identities. The public marketing website does not receive or host these rosters. Retention and reset instructions are in the bulk enrollment guide.

Current limits

All connected screens play together in the teacher grid, up to 30 students per class. Teacher authentication uses a private staff key. Roster classes use enrollment codes and registered names; open classes use self-reported names. School SSO, verified email identity, SIS synchronization, and central fleet policy synchronization are not included. Chrome managed-policy configuration is available. Real deployments need HTTPS, managed extension distribution, and testing on the school network.

District review

Before deploying to students, review the source, authentication, server configuration, privacy notices, retention behavior, and applicable district requirements. This site makes no FERPA, COPPA, or other certification claim. It does not advertise an established customer base or paid service plan.