Last updated: February 2026
This Privacy Policy explains how Code4Kids collects, uses, stores, shares, and protects personal information when you use our website, platform, curriculum, software, tools, and related services (collectively, the “Services”).
Code4Kids is operated by LESSONSPACE, Inc. DBA Code4Kids (“Code4Kids,” “we,” “us,” or “our”).
Our mailing address is:
LESSONSPACE, Inc. DBA Code4Kids
2035 Sunset Lake Road
Newark, DE 19702
United States
This Privacy Policy applies to our public website, our learning platform, and our related services. Where Code4Kids has entered into a separate written agreement with a school, school district, or organization, including a data privacy agreement, data sharing agreement, order form, purchase order, or master services agreement, that agreement may include additional privacy and data protection terms.
If there is a conflict between this Privacy Policy and a signed written agreement with a school, district, or organization, the signed written agreement will control to the extent of the conflict.
This Privacy Policy applies to information we collect from or about:
Students may only use Code4Kids through access authorized by a school, district, teacher, administrator, parent, guardian, or other authorized adult, as applicable.
Code4Kids is designed for school-authorized educational use.
When a school or district uses Code4Kids, the school or district controls the student data it provides or makes available to Code4Kids. Code4Kids processes student data on behalf of the school or district to provide, support, secure, maintain, and improve the educational Services.
Code4Kids does not:
Schools and districts are responsible for determining whether and how student use of Code4Kids is authorized under applicable law and their own policies.
Code4Kids follows a data-minimization approach. We aim to collect only the information needed to provide, support, secure, maintain, and improve the Services.
The information we collect depends on how the Services are used and what information a school, district, organization, or user chooses to provide.
We may collect information about schools, districts, and organizations, including:
For administrators, teachers, and staff, we may collect:
Code4Kids can operate with minimal identity data, such as a unique user identifier, role, and optional display name. When users use the platform, Code4Kids also generates learning and operational data needed to provide the service, such as class membership, lesson progress, activity completion, assessment/reporting data, and workspace content.
Student information may include:
Student email addresses are not required for non-SSO access. Student names and usernames can be anonymized.
Code4Kids does not require sensitive student information such as demographic profiling, health information, discipline records, or IEP/504 information to provide the core platform. Schools, districts, and users should not upload sensitive information unless specifically authorized by the school or district.
When users visit our public website or use our Services, we may collect technical information, including:
Google Analytics is used on the public Code4Kids website. Google Analytics is not used on the authenticated Code4Kids platform where students, teachers, and administrators sign in and access learning content.
If you contact us, request support, complete a form, attend training, or communicate with our team, we may collect:
We collect information in several ways, including:
Where SSO or rostering is used, the school or district controls what user fields are shared with Code4Kids through its identity or rostering configuration.
Code4Kids uses information to provide, support, secure, maintain, and improve the Services.
We may use information to:
We do not use student personal information for targeted advertising, advertising profiles, or sale to third parties.
Student data is used only for educational and service-related purposes.
Code4Kids may use student data to:
Student data may be visible to authorized teachers, administrators, or district users within the relevant school or district, depending on their role and permissions.
Code4Kids does not provide student-to-student messaging, student-to-student comments, or student-to-student sharing functionality.
Code4Kids supports district-controlled access through SSO and rostering integrations where configured.
These may include:
When a district uses an SSO or rostering provider, the district controls what information is shared with Code4Kids through that provider’s permissions and configuration.
Code4Kids can operate with a minimum-field configuration. In many cases, the core platform only requires:
Code4Kids does not require student email addresses for non-SSO access. Student names and usernames can be anonymized.
Code4Kids does not sell student personal information.
We may share information only as needed to provide, support, secure, maintain, and improve the Services, or as otherwise described in this Privacy Policy or an applicable written agreement.
We may share information with:
We may make information available to authorized teachers, administrators, school staff, and district users according to their roles and permissions.
For example, teachers may be able to view student progress, activity completion, and student work for students in their classes.
We may use trusted service providers to help us operate, host, secure, maintain, support, and improve the Services.
These service providers may support functions such as:
Service providers may only access information as needed to provide their services to Code4Kids and are not permitted to use student data for their own advertising purposes.
Code4Kids can provide additional information about relevant service providers to schools and districts upon request.
Where configured by a school or district, we may exchange necessary information with SSO, rostering, or authentication providers such as Clever, ClassLink, or Google Single Sign-On.
We may disclose information if we reasonably believe it is necessary to:
The Code4Kids platform does not use artificial intelligence or machine learning tools to process customer data or student data.
Code4Kids does not use district data, student data, prompts, interactions, or metadata for AI training, model training, model fine-tuning, or AI-based profiling.
Code4Kids does not use AI chatbots in the student platform.
Cookies are small text files placed on a device to help websites and services function, remember preferences, understand usage, and improve performance.
Code4Kids may use cookies or similar technologies on the public website for:
Code4Kids uses Google Analytics on the public website to understand website traffic and improve the website experience.
Google Analytics is not used on the authenticated Code4Kids platform where students, teachers, and administrators sign in and access learning content.
Code4Kids does not use cookies to target advertising to students.
Users can control cookies through their browser settings. Disabling some cookies may affect website functionality.
Code4Kids uses reasonable administrative, technical, and organizational safeguards to protect information against unauthorized access, loss, misuse, alteration, or disclosure.
Platform data is hosted using AWS infrastructure in Europe.
We use HTTPS/TLS encryption to protect data in transit.
We also use safeguards such as access controls, account security practices, infrastructure protections, firewall protections, monitoring, and internal review processes to help protect the Services.
Access to production systems and data is restricted to authorized personnel who need access to perform their role.
No method of transmission or storage is completely secure. While we work to protect information, we cannot guarantee absolute security.
If we become aware of a confirmed security incident affecting school or district data, we will work to identify, contain, investigate, and remediate the incident and notify affected schools or districts without undue delay in accordance with applicable law and any contractual notification requirements.
We retain information for as long as needed to provide the Services, comply with legal or contractual obligations, maintain security, resolve disputes, support school or district requirements, and operate our business.
For school and district customers, student data is retained according to the applicable agreement with the school or district, unless deletion is requested earlier and permitted by law and contract.
Code4Kids supports appropriate access, export, return, and deletion processes, including at the end of a pilot or contract term, consistent with district requirements and the parties’ agreement.
Some information may remain in backups, logs, or archival systems for a limited period before being deleted according to ordinary retention and security practices.
Schools and districts may request deletion or return of school or student data by contacting: privacy@c4k.io
Schools and districts may request access to, correction of, export of, or deletion of school or student data, subject to applicable law and any written agreement.
Parents, guardians, and students who want to access, correct, or delete student data associated with school-authorized use should usually contact the relevant school or district first. Because Code4Kids processes student data on behalf of schools and districts, we may need to work with the school or district to respond to the request.
Users may also contact us at: privacy@c4k.io
We will respond to privacy requests as required by applicable law and any applicable written agreement.
Code4Kids is designed to support school-authorized educational use.
Where a school or district authorizes student use of Code4Kids, Code4Kids processes student information as directed by the school or district and for the purpose of providing the educational Services.
Code4Kids supports schools and districts in meeting their obligations under applicable student privacy laws, including FERPA, COPPA, and applicable state student privacy requirements.
Where applicable, schools or districts may authorize student use of Code4Kids and provide any required consent consistent with their legal obligations and policies.
Code4Kids does not knowingly collect personal information from children outside school-authorized use. If we learn that a child has provided personal information outside school-authorized use and without appropriate authorization, we will take reasonable steps to delete the information or obtain appropriate authorization.
If you believe a child has provided personal information to Code4Kids outside school-authorized use, please contact us at: privacy@c4k.io
Code4Kids is intended for use in educational settings under the direction of schools, districts, teachers, administrators, parents, guardians, or other authorized adults.
For non-SSO access:
Students should not provide unnecessary personal information when using Code4Kids.
Schools and districts are responsible for supervising student use of the Services and ensuring that use is consistent with their policies and applicable law.
Code4Kids is a non-collaborative learning platform.
Code4Kids does not provide:
Schools and districts remain responsible for supervising students and applying their own safeguarding, child protection, acceptable use, and classroom policies.
Code4Kids may retain certain access, security, and usage logs for safeguarding, security, support, legal, and operational purposes.
Safeguarding-related requests can be sent to: safeguarding@c4k.io
Code4Kids may process information in countries where Code4Kids, its affiliates, team members, or service providers operate.
Platform data is hosted using AWS infrastructure in Europe. Depending on the Services used and the support required, information may also be accessed or processed from the United States, South Africa, the United Kingdom, or other countries where Code4Kids or its service providers operate.
Where required, Code4Kids uses appropriate safeguards for international data processing and transfer.
School and district agreements may include additional terms related to data location, processing, and transfer.
Depending on your location and the type of information involved, you may have rights to access, correct, delete, restrict, object to, or receive a copy of certain personal information.
For school-authorized student data, requests should generally be directed to the relevant school or district. Code4Kids will work with the school or district to support applicable requests.
To make a privacy request, contact: privacy@c4k.io
We will respond to requests as required by applicable law and any applicable written agreement.
The Services may include links to third-party websites, resources, or tools.
Third-party websites and services are not controlled by Code4Kids and may have their own privacy policies, terms, and data practices.
Code4Kids is not responsible for the privacy practices of third-party websites or services that are not controlled by Code4Kids.
Schools and districts should review any third-party requirements relevant to their own technical environment, integrations, and policies.
Code4Kids may update this Privacy Policy from time to time.
When we make changes, we will update the “Last updated” date at the top of this page. Material changes may also be communicated through the Services, by email, or through other reasonable means.
Your continued use of the Services after an updated Privacy Policy becomes effective means that you acknowledge the updated Privacy Policy.
For school, district, or organizational customers, any signed written agreement, data privacy agreement, data sharing agreement, order form, or purchase order will continue to control where it conflicts with this Privacy Policy.
For privacy questions, requests, or concerns, please contact us at:
Code4Kids
LESSONSPACE, Inc. DBA Code4Kids
2035 Sunset Lake Road
Newark, DE 19702
United States
Privacy: privacy@c4k.io
Legal: legal@c4k.io
Support: support@c4k.io
Safeguarding: safeguarding@c4k.io
Accessibility: accessibility@c4k.io
.svg)
