1. Student installs extension and logs in with Google account. 2. Extension identifies student via email and connects to the Classview server. 3. Teacher sends rules (focus mode, blocked sites, etc.) to the extension. 4. Extension enforces rules by blocking URLs or pausing internet access. 5. Teacher can request screenshots or chat with students.

Target users: Teachers / Students

The extension relies on a backend service (Classview server) for rule management and teacher-student communication. The analysis is based on the client-side extension code only. The exact server URL is constructed dynamically based on the school slug extracted from the student's email, so the specific destination service domain is not hardcoded in the extension.

Monetization

No paid features detected

No evidence of paid features, subscription gating, or billing logic within the extension code. The extension appears to be a free tool for classroom management. The heuristic hits for 'pro' and 'upgrade' were false positives (e.g., 'protected', 'socket.io upgrade packet type').

Confidence: 90
Payment platform: --
Source: AI / High
Login required: Yes
Reason: The extension requires a Google account (via chrome.identity.getProfileUserInfo) to identify the student and connect to the Classview server. The core workflow of screen monitoring and classroom session management depends on this identity to authenticate with the destination service (the teacher's dashboard/server). Without a logged-in Google account, the extension cannot function.

Permission risk

High-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

扩展能力较强：tabs、activeTab、storage、history
主机权限覆盖范围较宽

Publisher

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access