Privacy FAQ

No student account is required for the Learning Labs hub, Math Lab, Life Lab, or public Word Lab practice. Word Lab offers optional signed-in teacher tools. A student can access teacher-assigned work through a private code connected to an educator-created roster record.

The current notices state that the Labs do not sell student information, create advertising profiles, or use third-party behavioral advertising. The sites do use ordinary hosting services needed to deliver and protect the service.

Math Lab and Life Lab progress/preferences are saved in the current browser. Anyone using that same browser profile may be able to see them. Optional Word Lab teacher workspace records are stored on the server and linked to the signed-in educator’s account.

The current Word Lab notice lists date, page, general country/state or region supplied by the hosting network, device category, referring domain when available, and whether a visit began a new browser-tab session. It states that its analytics database does not store names, email addresses, student responses, exact street locations, GPS coordinates, or IP addresses.

No. Word Lab Fluency Studio requests microphone access only after the recording button is pressed. The recording is available for immediate playback on that device and is not uploaded to the Word Lab server or included in analytics. Refreshing or closing the page removes it.

Optional signed-in tools can store student display identifiers, groups, goals, baselines, targets, instructional notes, assignments and results, elapsed time, missed-skill patterns, session records, progress checks, custom word lists/question sets, check-in/out records, and family invitations. Districts should approve these features and define allowed data before use.

The current Word Lab notice states that teacher workspace records and check-in data are isolated from other teacher accounts. Assignment and custom-practice links use random sharing codes, but anyone who receives a link may open that activity; teachers should share links only with the intended audience and avoid identifying titles.

Unless a district has explicitly approved a specific secured workflow, do not enter full names, birth dates, addresses, school IDs, passwords, diagnoses, IEP details, medical information, disciplinary narratives, family circumstances, or other confidential records. Use initials or district-approved codes when a label is needed.

Math Lab and Life Lab include controls to clear their locally saved site data. Clearing browser/site data also removes local preferences, progress, and cached assets. On a shared device, confirm the correct browser profile before clearing because deletion affects that profile’s saved Lab information.

Begin through the feedback page without including student records in the message. The requester’s identity and authority may need to be verified. Districts considering broader use should establish written correction, export, retention, account-transition, and deletion procedures before adoption.

No automatic compliance claim is made. FERPA responsibilities depend on the school’s control, approved use, records, notices, and agreements. The FTC explains that school authorization under COPPA is limited to the educational context and use for the school’s benefit, not unrelated commercial purposes. District or school review is the appropriate path before collecting children’s personal information.

Teachers should follow district policy. U.S. Department of Education guidance advises educators to check whether an app is approved and explains that use under FERPA’s school-official exception requires specific conditions, including school control over personally identifiable information. Local administrators or privacy staff should decide when formal approval or an agreement is required.

Browser-local information may remain visible to the next person using the same browser profile. Use a separate profile or private-browsing session when appropriate, clear local Lab data between students, close tabs, and protect printouts or exports under district policy.

Lab privacy pages include an effective or revision date and should be updated when practices materially change. Districts should re-review optional stored-data features after major product changes.