BLODCO PROTECT / PILOT
Pilot privacy notice
This development notice describes the current pilot. District approval and final service terms are required before real student deployment.
Google sign-in
Portal users sign in with Google. The service verifies the Google account identifier and email, then matches the account to a school-assigned invitation or an existing authorized account. Sign-in requests identity scopes only. Optional school roster access through Google Workspace or Skyward is a separate setup and consent step.
What this pilot stores
School and district names, enrolled names, school-assigned email addresses, roles, device credentials stored as hashes, classroom commands, blocked-site incidents, help requests, chat messages, and administrative audit events.
Purpose and access
Directory access is not connected. Any future roster integration must use directory information for school account and roster provisioning. Separate classroom activity and chat records support the school functions described in the portal. Students can access their own incident and chat records; authorized staff can access school records within this single-school workspace.
No sale or advertising
This pilot has no data-selling, behavioral advertising, or marketing integration. Hosting and authentication providers process information necessary to operate the service. Authorized school staff can access the records described above, so this notice does not promise that information is never shared with anyone.
Chat and observation
Approved classroom chat is recorded. A basic blocked-word filter is used; it is not comprehensive or AI moderation. Screen and audio capture are not implemented. No live observer is currently connected.
Retention and removal limits
Incident access expires after 24 hours. Storage is bounded by record counts in this development build; expiration is not a guaranteed physical deletion process. Automated retention, school offboarding, export, and deletion workflows are not implemented. Do not use the pilot for real student data until the operator and district establish retention, access, and deletion procedures.
Google and device permissions
No Google Workspace data has been imported. Google administrator authorization, managed extension installation, and device certificate enrollment are separate setup steps. They are not granted by accepting this notice.
Notice version: pilot-2026-11-06. Legal entity, contact, final contractual privacy commitments, and district agreements remain to be configured.