COPPA Compliance
Last updated: November 2026
Edusfere's Position Under COPPA
The Children's Online Privacy Protection Act (COPPA) restricts how online services collect personal information from children under 13. It applies to operators whose services are directed at children, or who have actual knowledge they are collecting personal information from children under 13.
Edusfere is not directed at children, and we do not knowingly collect personal information from children under 13.
Our platform is designed exclusively for educators, curriculum leads, school administrators, and content providers. Students do not have accounts on Edusfere, do not log in, and do not interact with the platform in any capacity.
We do not ask for, and do not set out to collect, personal information about individual students. Teachers may describe a class in general terms (such as class size) to help them plan. Edusfere’s free-text fields accept whatever a user chooses to type, so we cannot prevent a teacher from entering a student’s name in a lesson note; what we can say is how any such entry is treated, which is set out below.
What Data We Collect and From Whom
Edusfere collects information only from registered adult users: teachers, administrators, and content providers, in the course of providing our platform. This includes account details (name, email, institutional affiliation) and content created within the platform (curriculum maps, lesson plans, standards alignments).
We do not request personal information from or about students, and we do not ask schools to send it to us. If a user does include identifying information about a student within a free-text field (such as a lesson plan note), that text is treated exactly like the rest of the lesson content it sits in: it is not used for any secondary purpose, not sold, not used for advertising, and not used to train AI models. It is handled only by the service providers we need to operate the platform, and sent only to the tools your school has itself chosen to connect.
We encourage educators to avoid entering student-identifying information into any Edusfere field, as this falls outside the intended use of the platform.
This holds for our integrations too. Where a school connects Edusfere to Google Drive, single sign-on, or FACTS SIS, those connections send lesson content out of Edusfere or make a staff member's own files available inside it. The FACTS SIS integration is one-way: no student information is pulled into Edusfere from a student information system, and we do not import student rosters.
Schools, Parental Consent, and COPPA
Because Edusfere is a tool for educators rather than students, the platform does not trigger the parental consent requirements that COPPA places on operators of child-directed services. Schools using Edusfere to plan and align curriculum are not directing student data to us; they are using a professional tool for internal instructional work.
If your district has a policy requiring COPPA compliance documentation for all edtech vendors, we are happy to provide written documentation of our data practices and discuss any additional assurances your procurement process requires.
Contact
For compliance inquiries or vendor review documentation, contact us at hello@edusfere.com.
For authoritative guidance on COPPA, visit the FTC's COPPA resource page.