Blooket Safety & Privacy: what teachers and parents should know

How Blooket handles student data

Blooket's data model is intentionally light. Account holders supply an email, username, and password; gameplay produces statistics tied to the account. Students who join a class with only a Game ID generate session data — nickname, answers, scores — that's associated with the host's report but doesn't create a persistent account.

COPPA, FERPA, and consent

In the U.S., COPPA governs data collection from children under 13 and FERPA governs school records. Blooket's public materials state compliance with these frameworks when the platform is used as intended. For under-13 students, schools and parents are the appropriate consent gatekeepers. District-wide deployments typically go through an instructional-technology review.

Classroom best practices

• Use the Game ID join flow for routine class games — no account needed.
• If students will create accounts, send a one-paragraph note home explaining what data is collected.
• Establish a nickname standard (first name + last initial) so you can map players to students.
• Kick players whose nicknames slip past the auto-filter.
• Encourage students to sign out on shared devices.

Password and account hygiene

• Use unique passwords; consider a school-issued password manager for staff.
• Prefer Google Sign-In where supported — it removes Blooket-specific password handling from the loop.
• Rotate passwords annually and after any shared-device incident.

Reporting issues

If you encounter a safety concern — inappropriate user-generated content, suspected unauthorized access, or anything else — contact Blooket support directly through their site. For platform-level concerns, your district's instructional tech team is the right escalation path.