Quizizz and Student Data Privacy: What Teachers Should Know

Say it is the first week of school and you are opening the quiz platform you have used for years, except the login screen now reads Wayground instead of Quizizz. Before you assign a single review game, the setup choices you make in the next ten minutes will shape more student data than any line in the privacy policy.

Quizizz, now operating as Wayground, ties student data to your class based on how you configure it, not by default. The practical privacy levers sit with the teacher: guest versus account joining, the roster you sync from, the assignment mode you pick, and whether you retire old classes in June.

Quick Answer: The most consequential privacy decisions in a Wayground (formerly Quizizz) classroom are workflow choices a teacher controls directly. Guest joining collects the least data, persistent accounts and roster syncs collect more, and self-paced homework leaves a longer data trail than a one-off live game. This guide covers the practical setup, assignment, and cleanup habits. The consent law and the content-safety questions each live in a separate companion piece.

This is a workflow guide, not a legal one. For how COPPA consent actually works and why the platform's privacy badges are not the same as an FTC Safe Harbor certification, see Is Quizizz COPPA Compliant?. For content moderation, nickname filtering, and the public quiz bank, see Is Quizizz Safe for Students?. This article deliberately leaves those threads to their own pages.

A Two-Name Platform: What Changed When Quizizz Became Wayground

Quizizz rebranded to Wayground in 2025, moving from quizizz.com to wayground.com, and the underlying company, account data, and stated privacy practices carried over unchanged. Quizizz Inc. remains the legal parent entity, according to the company's own transition materials (Wayground, 2025). Nothing about the rename resets what data a class already generated.

For a teacher, the transition is mostly a matter of a few housekeeping items rather than a data event. Old links still resolve, so your library did not vanish overnight.

• Bookmarks and shared quizzes to quizizz.com redirect automatically to wayground.com, so a saved activity from two years ago still opens.
• Account settings, including anything touching student data and class controls, stayed where they were, just under new branding on the screen.
• The rename added features rather than removing controls, including curriculum alignment, lesson bundles, and expanded accommodations across video, slides, and assessments (Wayground, 2025).

The one thing worth doing early: update any classroom handout, syllabus link, or family newsletter that still points students to quizizz.com. The redirect works, but a link that matches the name on the screen avoids a confused parent emailing to ask whether "Wayground" is a new tool the school never mentioned. Adoption has genuinely outpaced family communication in most districts, and a mismatched link only widens that gap.

Where Student Data Enters a Wayground Classroom

Student data does not enter Wayground at a single moment; it enters at four distinct touchpoints, and each one is a place where a teacher's setup choice changes how much gets collected. Mapping those touchpoints first makes every later decision easier to reason about.

Classroom tools spread faster than any privacy office can vet them individually. Instructure's LearnPlatform usage data found that districts now have access to roughly 2,600 to 3,000 distinct edtech tools in a typical year (Instructure, 2025). A gamified quiz platform used across nearly every grade band is exactly the kind of tool a teacher adopts on their own, which is why knowing where the data enters matters more than assuming IT already mapped it.

A single sentence of takeaway: three of those four rows are optional or adjustable, which means most of the data footprint of a Wayground classroom is a setting, not a given. The sections below walk each lever in the order a teacher actually encounters it.

Setting Up Your Class Without Collecting More Than You Need

The setup screen is the highest-leverage privacy decision you will make, because it determines whether a student is a nameless guest for fifteen minutes or a persistent profile that lives in the platform for the year. Both are legitimate; they just serve different purposes.

Guest Joining vs Persistent Student Accounts

Guest joining lets a student enter a live game with only a nickname, no email and no stored account, and it is the lowest-data-footprint option the platform offers. For a single review session before a Friday quiz, that is usually all you need.

Reach for persistent accounts only when the instructional goal genuinely requires memory across sessions:

1. You want to track an individual student's progress across multiple assignments over a unit, not just one game.
2. You are assigning self-paced homework that students complete on their own time and you grade later.
3. Your school has a managed single sign-on setup where accounts are provisioned centrally rather than created ad hoc.

If none of those apply, a guest session does the same instructional job with a smaller data trail. A common mistake is defaulting every class to full accounts because it feels more "official," when the activity is a one-time review that a nickname would have covered.

Rostering Through Clever, ClassLink, or Google Classroom

Wayground connects to Google Classroom, Schoology, and Canvas, with rostering available through Clever and ClassLink (Wayground, 2025). A managed roster sync is genuinely convenient, but it also pulls identifiable student data into the platform automatically, so it belongs to your school's integration, not an individual classroom improvisation.

• Sync only the sections that need saved data. A roster sync that scoops in every class you teach, including ones where you only ever run guest games, collects more than the instruction requires.
• Confirm who owns the integration. If your rostering runs through Clever or ClassLink, an administrator configured that, and questions about what it shares route to them rather than to a per-classroom setting.
• Ask whether a signed agreement backs the sync. A districtwide roster integration should sit on top of a data agreement, the same standard applied to any vendor, which the companion legal guide covers in full.

Say you teach a Grade 4 class and your school syncs rosters through Clever. You likely do not need to build a class list by hand at all, but you also cannot quietly switch that class to guest-only joining without talking to whoever manages the integration, since the account provisioning happens upstream of your classroom login.

Assigning Quizzes: How Each Mode Shapes the Data Trail

The assignment mode you choose, live game, self-paced practice, or homework, directly determines how long per-student data persists and how much of it is stored. A live game can be nearly ephemeral; a homework assignment is designed to be a durable record.

RAND's 2025 survey of US teachers and principals found that roughly a quarter of teachers used AI and digital tools for instructional planning during the 2023 to 2024 school year (RAND, 2025). As those tools move from planning into graded student-facing work, the mode you assign in is where a review activity turns into a stored gradebook entry.

Live Games, Self-Paced Practice, and Homework

Match the mode to the shortest data lifespan that still meets the goal. A live review game does not need to become a permanent per-student record, and a homework assignment should not be run as an anonymous guest game you cannot grade.

• For a one-off review, run a teacher-paced live game with guest joining. The data barely outlives the class period.
• For ongoing practice, self-paced mode with accounts stores attempt history, which is the point, so keep it only as long as the practice unit is active.
• For graded homework, use accounts and expect durable records. This is the mode where retention and cleanup, covered next, actually matter.

The discipline is simple: do not use a heavier mode than the task needs. A gradebook-tracked assignment for something you never intend to grade generates a stored record for no instructional reason.

Roster Hygiene and End-of-Year Cleanup

A stale roster is the most common way student data lingers in a quiz platform longer than it should, because "the school year ended" is not, by itself, a deletion event. Accounts, classes, and stored results persist until someone actively retires them.

Common Sense Media's 2025 family research found that 83% of parents said their child's school had not communicated with them about how classroom digital tools use student data at all (Common Sense Media, 2025). Good roster hygiene is one of the few parts of that gap a single teacher can close without waiting for a district policy.

A short cleanup routine, worth running each June:

1. Archive or delete classes you will not reuse, rather than leaving last year's roster active indefinitely.
2. Remove students who transferred or withdrew mid-year, since a synced roster does not always drop them automatically.
3. Confirm what happens to results when a class is archived, and if you are unsure, ask your technology office rather than assuming they are purged.
4. Recheck the current privacy settings once a year, since defaults and integration behavior can shift with a product update the classroom never hears about.

If your rostering is centrally managed through Clever or ClassLink, some of this cleanup happens at the administrator level when a student is deprovisioned. Verify that rather than assuming it, especially for a student who left partway through the year.

Who Controls the Class: Teacher-Created vs District-Managed

Whether you built the class yourself or it arrived through a district roster sync changes who can adjust its privacy settings, and knowing which situation you are in saves a lot of wasted effort. The two setups behave differently in practice.

• A teacher-created class is yours to configure directly: you choose guest versus account joining, and you archive or delete it yourself.
• A district-managed or roster-synced class was provisioned upstream, so join methods and account creation are set by an administrator, and some changes simply are not available from your classroom login.
• A mixed setup is common: your section list syncs from the district, but you still control the assignment mode and whether a given activity runs as a guest game.

The fastest tell for which applies is whether you can add or remove a student yourself. If you cannot, an administrator owns that layer, and roster or deletion questions route to them rather than to a setting on your screen.

Talking to Parents About What the Platform Collects

A parent asking what a quiz app knows about their child deserves a plain answer, and a teacher who made deliberate setup choices can give one confidently. The response follows directly from the levers this guide has covered.

A workable, non-technical script covers three things:

• What is collected depends on how the class joins. For a guest live game, it is a nickname and that session's answers; for an account-based class, it is a name and stored progress over time.
• Who can see it. Results are visible to the teacher, and to a student for their own work, not to other families or the public by default.
• How long it stays. Stored results persist until a class is archived or deleted, which you do at year's end rather than the platform doing it automatically.

Keeping a short written note of what you told families at the start of the year makes a spring follow-up question easy to answer consistently, rather than reconstructing it from memory.

Where a Content Generator Fits Into the Workflow

Wayground is built to deliver quizzes as live and self-paced games; it is not the tool that writes the underlying question set, worksheet, or unit exam in the first place. Those two jobs are worth keeping separate in your workflow.

A teacher could use EduGenius to generate a curriculum-aligned quiz, worksheet, or set of flashcards for Grades KG-9 from a class profile configured with grade level and subject, complete with Bloom's Taxonomy alignment and an automatic answer key, without creating individual student accounts for the content-generation step at all. You could then bring a subset of those questions into a Wayground live game for the engagement layer. Keeping authorship inside a controlled generation step, and delivery inside the game platform, means each tool touches only the data its job actually requires.

Related Reading

• AI, FERPA & COPPA: The Complete School Data-Privacy Guide (2026)
• Is Quizizz COPPA Compliant?
• Is Quizizz Safe for Students?
• Diffit and Student Data Privacy: What Teachers Should Know
• Is Curipod Safe for Students?
• SchoolAI vs Khanmigo: Which Is Better for Teachers?