Current implementation snapshot

Data-collection map

What data exists, where it lives, why it is used, and what changes when an educator chooses optional signed-in Word Lab tools.

Read common questions
Key distinction: “Browser-local” means information is stored by the site in that browser profile and may be visible to anyone using the same profile. “Server-stored” means information is sent to and retained by the hosted service for the named feature.

At-a-glance map

Site / featureInformationLocationPurposeUser control / caution
Learning Labs hubNo student profile requested. Pages/assets may be cached.Browser cache and ordinary hosting systemsDeliver the site and support reliable/offline return visitsClear browser/site data; do not submit student records through feedback.
Word Lab public practicePractice responses are used in the active page. Fluency recordings are temporary.Current browser/tab or device memoryImmediate practice feedback and playbackNo student account required. Refresh/close removes temporary recording.
Word Lab aggregate analyticsDate, page, general country/state or region, device category, referring domain when available, and new tab-session markerWord Lab analytics database; session marker in browser tabUnderstand overall use and improve activitiesCurrent notice says no names, emails, responses, exact location, GPS, or IP addresses are stored in this analytics database.
Word Lab Teacher Lab plansInitials, date, notes, and selected planning optionsEducator’s browser local storageReturn to a locally saved planNot sent to analytics; clearing browser data removes it.
Word Lab signed-in teacher workspaceTeacher account identity; educator-entered student identifiers; groups, goals, baselines, targets, notes, assignments/results, elapsed time, missed-skill patterns, sessions, progress checks, custom lists/questions, and family invitationsServer database tied to the teacher accountPrivate intervention planning, delivery, monitoring, and reportingOptional. Use minimum school-approved data. Records are described as isolated by teacher account.
Word Lab check-inRoster display identifier, one-way hash of student code, check-in/out action, and server timestampServer database tied to the teacher accountOptional classroom attendance/check-in workflowPublic kiosk does not display a roster. Attendance use should receive district approval.
Word Lab student portal / share linksPrivate code verification; assigned activity/result for that roster record; random sharing codesServer request and database; code not stored in student browserShow an individual student’s assigned workAnyone with a sharing link may open that activity; avoid identifying titles and distribute privately.
Math LabOptional name/initials, checks, practice, mastery, attempts, probe history, support preferences, goals, streaks, and private badgesCurrent browser local storagePrivate progress, reports, instructional decisions, and preferencesNo account or roster required. Clear controls are available; shared browser users may see saved data.
Life LabAccessibility preferences, lesson completion/support level, transfer plans, and personal support plansCurrent browser local storagePrivate progress and return-to-plan featuresNo account/roster currently. Do not enter identifying or sensitive information; clear between shared-device users.
All hosted sitesOrdinary technical request information necessarily processed by hosting infrastructureHosting/network systemsDeliver, protect, and troubleshoot the serviceTechnical processing is distinct from product databases; district teams may request contractual detail before approving server-stored features.

Data minimization rules for schools

Default anonymous

Start with public practice and browser-local features. Require sign-in only when the instructional benefit justifies stored records.

Use the minimum

Prefer initials or approved codes. Do not enter dates of birth, school IDs, diagnoses, IEP/medical information, addresses, passwords, or sensitive case notes.

Plan the exit

Decide who can export, how long information is kept, how deletion requests are handled, and what happens when staff or students leave.

Source notices and review limits

This map is a product-facing summary, not a network log, security audit, subprocessor list, retention schedule, DPA, or legal conclusion. Districts considering server-stored features should request and review any additional contractual or technical materials they require.