Is Nearpod COPPA Compliant?

Nearpod's own privacy notice states that it complies with COPPA and does not knowingly collect personal information from children under 13 without the required consent path. That is a vendor self-attestation, not a government certificate. Nearpod is a signatory of the Student Privacy Pledge and offers a Data Processing Agreement (DPA) to districts, but as of this writing, its parent company's own privacy hub lists an independent COPPA/FERPA review of the Nearpod product as "coming soon," not completed.

Quick Answer: Nearpod claims COPPA compliance through self-attestation, a signed Student Privacy Pledge, and a district-level DPA, all real and verifiable steps, but not an FTC-approved Safe Harbor certification. Renaissance Learning, Nearpod's parent company since 2021, already has three of its other products (Star Phonics, Lalilo, Freckle) independently certified by iKeepSafe. Nearpod itself is listed on Renaissance's own privacy page as pending that same certification. Verify current status directly before a district-wide rollout.

That gap between "self-attested" and "independently reviewed" is the whole story here, and it's worth sitting with before the rest of this article. A tool can be genuinely well-intentioned about student privacy and still not have completed the one process that would let a district point to outside verification instead of a vendor's own word.

This article walks through what COPPA actually requires of a platform like Nearpod, what Nearpod's own materials say, what the Renaissance/iKeepSafe relationship actually means in practice, and what a teacher or technology director should check before rostering a class under 13.

Why COPPA Applies to an Interactive Lesson Platform at All

COPPA doesn't care whether a product looks like a chat tool or a slide deck; it applies to any operator that collects personal information from a user it knows is under 13. Nearpod is built around interactive presentations where students join a live or self-paced lesson, answer embedded quizzes, draw on virtual whiteboards, and sometimes submit open-response text or audio.

Two join paths exist, and they carry very different data footprints:

1. Anonymous or code-based join. A student enters a session code and, in many setups, only a first name or nickname, without a persistent account tied to that identity across sessions.
2. Rostered student accounts. A teacher or IT department creates managed accounts, which pulls in first and last name, email address, institution name, a reference account number, and, optionally, a profile photo.

The second path is where COPPA's verifiable-parental-consent requirement becomes directly relevant, since it creates a persistent, identifiable record tied to a specific child rather than a one-off session interaction.

The School-as-Agent Consent Path

Longstanding FTC guidance lets a school consent on a parent's behalf when a tool is used strictly for an authorized educational purpose and the data isn't used commercially. That's the mechanism Nearpod, like most classroom platforms, relies on for students under 13. It only works, though, if the underlying contract between the district and Nearpod actually reflects those restrictions in writing.

For the full legal mechanics behind that school-consent pathway, including exactly what a DPA needs to contain, see the pillar guide: AI, FERPA & COPPA: The Complete School Data-Privacy Guide (2026). This article stays specific to Nearpod's own claims and status.

What Nearpod Itself Claims About COPPA and FERPA

Nearpod's privacy notice states directly that "Nearpod and the Nearpod Materials comply with, and are designed to allow responsible parties to comply with, applicable law, including FERPA and COPPA." That's a self-description written by the company about its own product, the same category of claim nearly every edtech vendor makes.

Beyond that headline sentence, Nearpod's public materials back it up with several concrete, checkable practices:

• No sale of user data and no marketing tools deployed on the student-facing side of the platform, according to the company's privacy notice.
• A signed Student Privacy Pledge, a voluntary industry commitment administered jointly by the Future of Privacy Forum and the Software & Information Industry Association, which Nearpod has reaffirmed under the pledge's 2020 update.
• TLS 1.2-grade encryption or better for data in transit, plus a stated commitment to notify users in the event of a breach.
• Sub-processor contracts that bind third parties handling Nearpod data to use it only for the purposes Nearpod specifies, not their own separate goals.

What the Student Privacy Pledge Actually Is (and Isn't)

The Student Privacy Pledge is real and worth taking seriously, but it isn't a COPPA Safe Harbor. It's a voluntary, self-certifying commitment a company makes publicly, without the recurring third-party audits that define an FTC-approved Safe Harbor program under 16 CFR § 312.11. A signatory promises specific practices (no behavioral advertising to students, no sale of student data); nobody outside the company checks the promise against the practice on an ongoing basis the way PRIVO, iKeepSafe, or kidSAFE would.

Nearpod's Data Processing Agreement

Nearpod offers a DPA to districts, the mechanism that satisfies FERPA's "school official" exception under 34 CFR § 99.31(a)(1) by putting the confidentiality and use restrictions in an enforceable contract rather than a public-facing policy page. A district considering Nearpod at scale should request this document directly and route it through legal or a designated privacy officer, not assume the public privacy notice alone covers the same ground.

The Renaissance/iKeepSafe Question: Where Does Third-Party Review Actually Stand?

This is the fact that separates Nearpod's current compliance posture from a vendor like Quizlet, which has a confirmed, active third-party COPPA certification. Renaissance Learning acquired Nearpod in an all-cash deal completed in March 2021, folding it into a portfolio that already included assessment and reading products like Star 360 and Freckle.

Renaissance's own privacy hub states that the company engages iKeepSafe, an FTC-approved COPPA Safe Harbor organization, to review and certify select products for FERPA and COPPA compliance. That page currently lists Star Phonics, Lalilo, and Freckle as products with an active iKeepSafe certification. Nearpod appears on the same page under a separate heading, marked "Coming soon."

That table isn't a reason to avoid Nearpod. It's a reason to ask a specific, answerable question before a district-wide rollout: has the Nearpod-specific iKeepSafe certification completed since this article was published, and can the vendor confirm it in writing? Renaissance's own page is the fastest way to check current status directly.

Why the Verification Gap Is Worth Taking Seriously

COPPA enforcement runs directly against the operator, not through a district's federal funding the way a FERPA violation would, which is exactly why the certification question matters more for an AI-adjacent platform than it might first appear. The Federal Trade Commission can assess civil penalties per violation, and once every affected under-13 account in a large rollout gets counted, that exposure scales quickly for the vendor, though it doesn't directly threaten the school's own funding the way FERPA's rare enforcement mechanism does.

That distinction matters for how a district should read a "pending" certification. It isn't necessarily a red flag; verification programs take time, and Renaissance already has a demonstrated track record of completing them for other products. It does mean a district's own risk sits with the strength of its DPA and its own configuration choices in the meantime, not with a badge that hasn't posted yet.

What the 2025 COPPA Amendments Add to This Picture

The FTC's COPPA Rule amendments, effective June 23, 2025 with most provisions requiring compliance by April 22, 2026, tightened exactly the area where a subprocessor-heavy platform like Nearpod needs to show its work: operators must now take documented steps to verify that third parties receiving children's data can maintain adequate security, with written assurances required rather than a general reasonable-security promise (FTC, 2025). Nearpod's stated use of contractually bound sub-processors is the right shape of answer; the amendment just raises the bar on how documented that binding needs to be.

A district's DPA request should specifically ask whether Nearpod's sub-processor list and retention timeline have been updated to reflect that 2025 standard, not just whether a DPA exists at all in some earlier form.

What Data Nearpod Actually Collects From Students

How much personal information Nearpod touches depends heavily on which join method a teacher uses, which is itself a meaningful privacy lever a teacher controls directly, not just something a vendor's policy dictates.

Anonymous Join Codes vs. Rostered Accounts

A teacher running a single interactive lesson with a class-generated code, and no persistent student login, keeps the data footprint close to a first name or nickname tied to that one session. Rostering the same class with managed accounts through a school's single sign-on system pulls in a fuller profile: full name, email, institution, and a reference number, plus whatever content that student generates inside the platform.

What Happens to Student-Created Content

Nearpod's interactive activities can capture open-response text, drawings on a collaborate board, and in some activity types, audio. According to the company's privacy materials, that student-generated content is treated as part of the same data set subject to its no-sale and no-marketing commitments, and is shared only with contractually bound sub-processors, not sold or used for targeted advertising.

A teacher who wants to minimize what's captured has a genuinely practical lever available:

• Use anonymous session codes for a single lesson rather than rostering accounts when a persistent record isn't actually needed.
• Avoid open-response or audio activity types for younger grades where anonymized multiple-choice or matching activities can meet the same learning objective.
• Turn off optional profile photo uploads at the account level if your district's SSO provisioning allows it.

Nearpod's Paid Tiers and What Changes With Them

Nearpod's individual educator pricing sits on three tiers, and the tier a teacher is on affects storage limits and the number of students who can join a single session, though not the core COPPA data-handling commitments described above.

Schools and districts can also negotiate a custom Platinum Plus license, which typically bundles in centralized rostering and admin controls, the exact features that make a district-wide DPA and consistent account-provisioning policy worth setting up in the first place rather than leaving each teacher to self-serve on the free tier.

A Teacher's Checklist Before Rostering Nearpod for a Class Under 13

Say you teach 4th grade science and want to run a unit on the water cycle using Nearpod's interactive slides, with students submitting short written responses and labeled diagrams. Before assigning individual student logins to the whole class, a few concrete checks take less time than building the lesson itself:

1. Confirm whether your district already has a signed Nearpod DPA on file, rather than relying on the public privacy notice as your only reference point.
2. Ask whether the Nearpod-specific iKeepSafe certification has completed, since Renaissance's own page marks it pending as of this writing.
3. Choose anonymous join codes over rostered accounts for any single lesson where a persistent student record isn't pedagogically necessary.
4. Check your district's activity-type policy for audio or open-response Nearpod activities involving students under 13, since those capture more identifiable content than a multiple-choice poll.
5. Confirm your state's own student-data statute, since a Nearpod DPA satisfying FERPA and COPPA at the federal level doesn't automatically satisfy a stricter law like Illinois's SOPPA or California's SOPIPA.

How Nearpod Compares to Other Classroom Platforms on This Specific Point

This is a narrow, factual comparison of publicly stated third-party COPPA verification, not a ranking of overall product quality or classroom usefulness.

For the fuller breakdown of Quizlet's own confirmed PRIVO membership and what a district should still ask about it, see Is Quizlet Safe for Students?, which covers the separate question of content and platform safety rather than legal certification status.

A district weighing an interactive-lesson tool like Nearpod against an AI content-generation platform should apply the same standard either way. EduGenius, for example, is built around teacher-managed class profiles rather than individual student logins, letting a teacher generate a differentiated water-cycle worksheet or quiz for the whole class without any student account existing on the platform at all, which changes the underlying COPPA exposure surface regardless of a vendor's certification timeline.

Related Reading

• AI, FERPA & COPPA: The Complete School Data-Privacy Guide (2026)
• Diffit and Student Data Privacy: What Teachers Should Know
• FERPA and AI in Education: A Guide for Administrators
• Is Quizlet Safe for Students?
• A COPPA Compliance Checklist for AI Tools in Schools
• SchoolAI vs Khanmigo: Which Is Better for Teachers?