Default anonymous
Start with public practice and browser-local features. Require sign-in only when the instructional benefit justifies stored records.
What data exists, where it lives, why it is used, and what changes when an educator chooses optional signed-in Word Lab tools.
| Site / feature | Information | Location | Purpose | User control / caution |
|---|---|---|---|---|
| Learning Labs hub | No student profile requested. Pages/assets may be cached. | Browser cache and ordinary hosting systems | Deliver the site and support reliable/offline return visits | Clear browser/site data; do not submit student records through feedback. |
| Word Lab public practice | Practice responses are used in the active page. Fluency recordings are temporary. | Current browser/tab or device memory | Immediate practice feedback and playback | No student account required. Refresh/close removes temporary recording. |
| Word Lab aggregate analytics | Date, page, general country/state or region, device category, referring domain when available, and new tab-session marker | Word Lab analytics database; session marker in browser tab | Understand overall use and improve activities | Current notice says no names, emails, responses, exact location, GPS, or IP addresses are stored in this analytics database. |
| Word Lab Teacher Lab plans | Initials, date, notes, and selected planning options | Educator’s browser local storage | Return to a locally saved plan | Not sent to analytics; clearing browser data removes it. |
| Word Lab signed-in teacher workspace | Teacher 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 invitations | Server database tied to the teacher account | Private intervention planning, delivery, monitoring, and reporting | Optional. Use minimum school-approved data. Records are described as isolated by teacher account. |
| Word Lab check-in | Roster display identifier, one-way hash of student code, check-in/out action, and server timestamp | Server database tied to the teacher account | Optional classroom attendance/check-in workflow | Public kiosk does not display a roster. Attendance use should receive district approval. |
| Word Lab student portal / share links | Private code verification; assigned activity/result for that roster record; random sharing codes | Server request and database; code not stored in student browser | Show an individual student’s assigned work | Anyone with a sharing link may open that activity; avoid identifying titles and distribute privately. |
| Math Lab | Optional name/initials, checks, practice, mastery, attempts, probe history, support preferences, goals, streaks, and private badges | Current browser local storage | Private progress, reports, instructional decisions, and preferences | No account or roster required. Clear controls are available; shared browser users may see saved data. |
| Life Lab | Accessibility preferences, lesson completion/support level, transfer plans, and personal support plans | Current browser local storage | Private progress and return-to-plan features | No account/roster currently. Do not enter identifying or sensitive information; clear between shared-device users. |
| All hosted sites | Ordinary technical request information necessarily processed by hosting infrastructure | Hosting/network systems | Deliver, protect, and troubleshoot the service | Technical processing is distinct from product databases; district teams may request contractual detail before approving server-stored features. |
Start with public practice and browser-local features. Require sign-in only when the instructional benefit justifies stored records.
Prefer initials or approved codes. Do not enter dates of birth, school IDs, diagnoses, IEP/medical information, addresses, passwords, or sensitive case notes.
Decide who can export, how long information is kept, how deletion requests are handled, and what happens when staff or students leave.
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.