Terms of Service
Date of Last Revision: February 22, 2018
Code.org is a 501(c)(3) non-profit organization (“Code.org”). Our mission is to give every student the opportunity to learn computer science. As a part of that mission, Code.org operates the websites located at https://code.org, https://studio.code.org, https://csedweek.org, https://www.k12cs.org, https://hourofcode.com, https://curriculum.code.org, other websites, information, text, curricula, videos, graphics, photos, APIs, email notifications and other materials and related products and services (the “Services”).
Please read these Terms of Service (“Terms”) carefully before accessing or using the Services. Accessing or using any part of the Services or clicking on an “I Agree” or “Sign Up” button that may be made available to you means that you agree to be bound by these Terms without modification.
These Terms are a legal contract between you and Code.org regarding your use of the Services. You may use the Services only if you can form a binding contract with Code.org and are not a person barred from receiving the Services under the laws of the United States or other applicable jurisdiction. If you are accepting these Terms and using the Services on behalf of a company, organization, school, government, or other legal entity, you represent and warrant that you are authorized to do so. You may use the Services only in compliance with these Terms and all applicable local, state, national, and international laws, rules and regulations. Note: If you are a teacher creating an account on behalf of your students, you agree to be bound by this Terms of Service on behalf of the educational organization you work for, and are authorized to do so.
These Terms are subject to change. You are agreeing to be bound by such changes if you continue to use to the Services after these Terms change, so please check these Terms for changes periodically.
Some Services may be subject to additional posted guidelines, rules or terms of service (“Additional Terms”) and your use of such Services will be conditioned on your agreement to the Additional Terms. If there is any conflict between these Terms and the Additional Terms, the Additional Terms will control for that Service, unless the Additional Terms expressly state that these Terms will control.
Children Under Age 13
If you are an Educator and you register an account for a student who is under the age of 13 (a “Child”), you represent and warrant that you or the educational organization you work for has proper permission to register the Child for Code.org, and that you have obtained the necessary parental consent for Code.org’s collection of the Child’s personal information for the use and benefit of the school and for no other commercial purpose. In addition, you agree to be bound by these Terms on behalf of the educational organization you work for.
If you create an account for Services, you are responsible for the security of your account and for keeping your own password safe. If you are using an account assigned to you by an Educator, your Educator may be able to access and disable your account.
If you are a student that uses an account registered for you by a Educator or otherwise connected to an Educator, you agree that Code.org may disclose your information to the Educators associated with your account. If you are a Educator, you agree not to share student information you receive from Code.org with anybody other than authorized agents of the classroom, school district, or other educational establishment you represent. Code.org does not use student data for any targeted or behavioral advertising, profiling, or onward disclosure.
The Family Educational Rights and Privacy Act (“FERPA”)
We help schools be compliant with the Family Educational Rights and Privacy Act (FERPA) by facilitating a school’s access to student data in response to a request from a parent. Email us at email@example.com for assistance.
User Generated Content - Management; License Grant; Representations and Warranties
Code.org has no obligation to monitor User Content or other materials. You are responsible for evaluating all User Content including for accuracy, completeness and reliability, and you bear all risk of using such User Content. Code.org will not be responsible for any damages that you may incur as a result of the submission or use of any User Content.
Code.org may, but is not obligated to, monitor or review any Services where Educators communicate solely with each other, including but not limited to chat rooms, live chats, bulletin boards or other user forums, and the content of any such communications. You assume the risk of such communications, and Code.org has no liability related to the content or use of any such communications.
Users may include links to third party websites in User Content as long as the content of such websites does not violate these Terms. Clicking on such links is at your sole risk. Code.org is not responsible for the availability or the content of linked websites, including the advertising, products or other materials thereon.
By submitting or distributing User Content through the Services or directly to Code.org staff, you hereby grant to Code.org a worldwide, non-exclusive, transferable, assignable, fully paid-up, royalty-free, perpetual, irrevocable right and license to host, transfer, display, perform, reproduce, modify, distribute and redistribute, adapt, prepare derivative works of, use, make, have made, import, and otherwise exploit your User Content (which should not contain any Student’s Personal Information), under all intellectual property rights therein, in whole or in part, in any media formats and through any media channels (now known or hereafter developed).
In addition, by submitting or distributing User Content through the Services, you hereby grant to each user of the Services a non-exclusive license to access and use your User Content.
User Content Representations and Warranties
You are solely responsible for User Content you post to the Services and the consequences of posting or publishing them. By uploading, submitting, creating, or publishing your User Content to or through the Services, you represent, and warrant that: (1) you are the creator and owner of your User Content and that you have the authority to use or have the necessary licenses, rights, consents, and permissions to publish the User Content you submit; (2) your User Content does not and will not: (a) infringe, violate, or misappropriate any third-party right, including any copyright, trademark, patent, trade secret, moral right, privacy right, right of publicity, or any other intellectual property or proprietary right or (b) slander, defame, libel, or invade the right of privacy, publicity or other property rights of any other person; (3) your User Content does not contain any viruses, adware, spyware, worms, or other malicious code.
Restrictions on Content and Use of the Services
We reserve the right at all times (but will not have an obligation) to remove or refuse to distribute any User Content on the Website and to suspend or terminate users, without liability to you. We also reserve the right to access, read, preserve, and disclose any information as we reasonably believe is necessary to (i) satisfy any applicable law, regulation, legal process or governmental request, (ii) enforce the Terms, including investigation of potential violations hereof, (iii) detect, prevent, or otherwise address fraud, security or technical issues, (iv) respond to user support requests, or (v) protect the rights, property or safety of Code.org, its users and the public.
You may not do any of the following while accessing or using the Services: (i) access, tamper with, or use nonpublic areas of the Services, Code.org’s computer systems, or the technical delivery systems of Code.org’s providers; (ii) probe, scan, or test the vulnerability of any system or network or breach or circumvent any security or authentication measures; (iii) access or search or attempt to access or search the Services by any means (automated or otherwise) other than through currently available, published interfaces that are provided by Code.org (and only pursuant to those terms and conditions), unless you have been specifically allowed to do so in a separate agreement with Code.org (NOTE: crawling the Services is permissible if done in accordance with the provisions of the robots.txt file, however, scraping the Services without the prior consent of Code.org is expressly prohibited); (iv) forge any TCP/IP packet header or any part of the header information in any email or posting, or in any way use the Services to send altered, deceptive or false source-identifying information; or (v) interfere with, or disrupt, (or attempt to do so), the access of any user, host or network, including, without limitation, bullying or harassing, sending a virus, overloading, flooding, spamming, mail-bombing the Services, or by scripting the creation of Content in such a manner as to interfere with or create an undue burden on the Services.
Your License to Use Code.org Videos, Tutorials, Data, and APIs
Code.org’s library of videos may be redistributed freely on the express conditions that (1) the videos are redistributed AS-IS in their entirety, using the embedded video player provided, or by downloading the original video file IF a download link is provided, and with clear attribution to Code.org, (2) the videos are not incorporated into any mashups, (3) the videos are used for computer science education purposes, (4) the use of the video does not constitute an endorsement of a 3rd party brand, service or product and (5) if access to such redistributed Content or Services is provided free of charge.
The celebrities and video “cast“ members appearing in Code.org tutorial videos reserve all rights to their likeness and name. By allowing you to redistribute these videos or tutorials AS-IS, Code.org does not grant any additional rights to use of the likeness or name of these individuals.
The artwork used in our tutorials is copyrighted and use of these tutorials does not grant you any rights to use the artwork in any other manner. Plants vs. Zombies are © 2016 Electronic Arts Inc. Plants vs. Zombies and PopCap are trademarks of Electronic Arts Inc. Angry Birds are © 2016 Rovio Entertainment Ltd. Angry Birds is a trademark of Rovio Entertainment Ltd. Scrat and Ice Age are trademarks and © Twentieth Century Fox Licensing and Merchandising. Frozen is a trademark and © 2016 Disney. Star Wars is a trademark and © 2016 Lucasfilm and Disney. Minecraft is a trademark and © 2016 Microsoft. The Amazing World of Gumball is a trademark and © Cartoon Network.
The software powering Code.org tutorials is governed by an open source license which is posted as part of the source code repository.
Other than the proprietary videos and artwork mentioned above, all curriculum and tutorial materials developed by Code.org are licensed to you for use under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 Unported License. More information about this license can be found at: http://creativecommons.org/licenses/by-nc-sa/4.0/. Code.org grants you a non-exclusive, transferable, non-sublicensable, limited right and license to access, view, use, and display the Code.org curriculum and tutorial materials. The Code.org curriculum and tutorial materials may only be used for noncommercial, computer science educational purposes. You may use these Code.org resources in a classroom where you charge students a fee to cover such costs as instructor compensation, venue, snacks, etc., so long as you do not represent the Code.org resources as your own creation or restrict access to the resources behind a paywall. If you are interested in licensing Code.org materials for commercial purposes, contact us.
The Code.org JSON API and database of schools is licensed via the Creative Commons attribution license, which means you are free to use the data to make derivative works, as long as you give Code.org attribution.
Code.org respects the intellectual property rights of others and expects users of the Services to do the same. We will respond to notices of alleged copyright infringement that comply with applicable law and are properly provided to us. If you believe that your work has been copied in a way that constitutes copyright infringement, please provide us with the following information: (i) a physical or electronic signature of the copyright owner or a person authorized to act on their behalf; (ii) identification of the copyrighted work claimed to have been infringed; (iii) identification of the material that is claimed to be infringing or to be the subject of infringing activity and that is to be removed or access to which is to be disabled, and information reasonably sufficient to permit us to locate the material; (iv) your contact information, including your address, telephone number, and an email address; (v) a statement by you that you have a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law; and (vi) a statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
Digital Millennium Copyright Act
It is Code.org’s policy to respond to notices of alleged copyright infringement that comply with the Digital Millennium Copyright Act.
We reserve the right to remove Content alleged to be infringing without prior notice, at our sole discretion, and without liability to you. In appropriate circumstances, Code.org will also terminate a user’s account if the user is determined to be a repeat infringer. To report a copyright violation, please contact us. Our copyright agent for notice of claims of copyright infringement can be reached by directing an e-mail to the copyright agent at firstname.lastname@example.org.
Code.org Intellectual Property Rights, and Your License to Use the Services
All right, title, and interest in and to the Services (excluding Content provided by users) are and will remain the exclusive property of Code.org and its licensors. The Services are protected by copyright, trademark, trade dress, patent and other laws of the United States. The content, information, data, designs, code, and materials associated with the Services (“Content”) are protected by intellectual property and other laws. You must comply with all such laws and applicable copyright, trademark or other legal notices or restrictions. Nothing in the Terms gives you a right to use the Code.org name or any of the Code.org trademarks, logos, domain names, and other distinctive brand features. Any feedback, comments, or suggestions you may provide regarding Code.org, or the Services is entirely voluntary and we will be free to use such feedback, comments or suggestions as we see fit and without any obligation to you.
Subject to these Terms, you may access and use the Services only for your own personal, noncommercial use. We reserve all other rights to the Services and Content, and otherwise you may not copy, reproduce, distribute, publish, display, perform, or create derivative works of the Services or Content without our permission, except with respect to Code.org’s library of videos, curriculum, tutorials, and API as set forth above.
Upon request, we may expressly authorize you to redistribute certain Content for personal, noncommercial use. We will identify specifically the Content that you are authorized to redistribute and describe ways you may redistribute it (such as via email, blogs, or embedded players). We may revoke this authorization at any time. If you redistribute Content, you must be able to edit or delete such publicly posted Content and you must edit or delete it promptly upon our request. In addition, notwithstanding any of the foregoing, use of Content or Services will NOT be permitted if such use constitutes an endorsement of a 3rd party brand, service or product or if access to such redistributed Content or Services is not provided free of charge.
The CODE® logo design is a registered trademark of Code.org. You may only use the Code.org logo or trademark with the permission of Code.org, and only in reference to Code.org. Mash-ups or combinations of the Code.org logo or name with other logos or names are specifically prohibited.
Code.org does not represent or warrant that the Services will be error-free, free of viruses or other harmful components, or that defects will be corrected. We do not represent or warrant that the information available on or through the Services will be correct, accurate, timely or otherwise reliable. We may make changes to the features, functionality or content of the Services at any time. We reserve the right in our sole discretion to edit or delete any Content, information or other materials made available as a part of the Services.
Code.org Store and Support Forums
Our teacher forum, located at https://forum.code.org, allows teachers to share resources, ask questions, and get responses from Code.org staff or other members of the community. Teachers may not use the forum to promote external paid resources. Code.org reserves the right to monitor and take down any inappropriate content posted on the forum.
Code.org encourages software engineers to volunteer as mentors in the classroom to assist teachers in computer science education.
Code.org’s platform does not connect students directly to volunteers or mentors. Instead, Code.org provides Educators information about potential volunteers without any warranty, references, or background checks. If you are an Educator who chooses to ask for the assistance of a volunteer sourced via Code.org’s database, it is entirely your responsibility to thoroughly check references or perform the necessary background checks. Code.org provides no warranty or information other than the ability to contact a potential volunteer, and all liability in any use of volunteers rests only with you. Code.org does not guarantee the accuracy or completeness of any information provided by volunteers and we neither adopt nor endorse, nor are we responsible for, the accuracy or reliability of any opinion, advice, or statement made by any party other than Code.org. Under no circumstances is Code.org responsible for any loss or damage resulting from any person's reliance on information or other content posted on the Service or transmitted by others.
Pledges, Donations and Payments
A. Pledges and Donations. If you make a pledge or donation on this website, You agree to pay all pledges and donations specified.
B. Payment Methods. Code.org will charge the pledge or donation you authorized, if any, to the PayPal account or credit card you designate. You authorize the credit card or PayPal account you designate to pay any amounts described herein and authorize Code.org, or any other company that acts as a billing agent for Code.org, to continue to attempt to charge all sums described herein to your credit card or PayPal account until such pledge or donation are paid in full.
C. Credit Card Authorization. If you use a credit card to pay for any pledge or donation related to the Website, You will be asked to provide Code.org with a credit card number from a card issuer that we accept. Code.org may seek pre-authorization of your credit card account to verify the credit card is valid and/or has the necessary funds or credit available to cover your pledge or donation. These pre-authorizations will reduce your available balance by the authorization amount until it is released or reconciled with the actual charge. Please contact your credit card issuer if you have additional questions regarding when an authorization amount will be removed from your statement.
Disclaimers and Limitations of Liability
Please read this section carefully since it limits the liability of Code.org and its parents, subsidiaries, affiliates, related companies, officers, directors, employees, agents, representatives, partners, and licensors (collectively, the “Code.org Entities”). Each of the subsections below only applies up to the maximum extent permitted under applicable law. Some jurisdictions do not allow the disclaimer of implied warranties or the limitation of liability in contracts, and as a result the contents of this section may not apply to you. Nothing in this section is intended to limit any rights you may have which may not be lawfully limited.
A. The Services are Available “AS-IS”
Your access to and use of the Services or any Content are at your own risk. You understand and agree that the Services are provided to you on an “AS IS” and “AS AVAILABLE” basis. Without limiting the foregoing, to the maximum extent permitted under applicable law, THE CODE.ORG ENTITIES DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The Code.org Entities make no warranty and disclaim all responsibility and liability for: (i) the completeness, accuracy, availability, timeliness, security or reliability of the Services or any Content; (ii) any harm to your computer system, loss of data, or other harm that results from your access to or use of the Services or any Content; (iii) the deletion of, or the failure to store or to transmit, any Content and other communications maintained by the Services; and (iv) whether the Services will meet your requirements or be available on an uninterrupted, secure, or error-free basis. No advice or information, whether oral or written, obtained from the Code.org Entities or through the Services, will create any warranty not expressly made herein.
The Services may contain links to third-party websites or resources. You acknowledge and agree that the Code.org Entities are not responsible or liable for: (i) the availability or accuracy of such websites or resources; (ii) the content, products, or services on or available from such websites or resources; or (iii) the protection of the privacy of personal information. Links to such websites or resources do not imply any endorsement by the Code.org Entities of such websites or resources or the content, products, or services available from such websites or resources. You acknowledge sole responsibility for and assume all risk arising from your use of any such websites or resources.
You may provide links to the code.org site, provided (a) that you do not remove or obscure, by framing or otherwise, the copyright, trademark service mark notices or other notices on the site, (b) your site does not engage in illegal or pornographic activities, and (c) you discontinue providing links to the site immediately upon request by us.
C. Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE CODE.ORG ENTITIES SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOOD-WILL, OR OTHER INTANGIBLE LOSSES, RESULTING FROM (i) YOUR ACCESS TO OR USE OF OR INABILITY TO ACCESS OR USE THE SERVICES; (ii) ANY CONDUCT OR CONTENT OF ANY THIRD PARTY ON THE SERVICES, INCLUDING WITHOUT LIMITATION, ANY DEFAMATORY, OFFENSIVE OR ILLEGAL CONDUCT OF OTHER USERS OR THIRD PARTIES; (iii) ANY CONTENT OBTAINED FROM THE SERVICES; OR (iv) UNAUTHORIZED ACCESS, USE OR ALTERATION OF YOUR TRANSMISSIONS OR CONTENT. IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE CODE.ORG ENTITIES EXCEED THE GREATER OF ONE HUNDRED U.S. DOLLARS (U.S. $100.00) OR THE AMOUNT YOU PAID CODE.ORG, IF ANY, IN THE PAST SIX MONTHS FOR THE SERVICES GIVING RISE TO THE CLAIM. THE LIMITATIONS OF THIS SUBSECTION SHALL APPLY TO ANY THEORY OF LIABILITY, WHETHER BASED ON WARRANTY, CONTRACT, STATUTE, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, AND WHETHER OR NOT THE CODE.ORG ENTITIES HAVE BEEN INFORMED OF THE POSSIBILITY OF ANY SUCH DAMAGE, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE.
SOME STATES OR OTHER JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSIONS MAY NOT APPLY TO YOU.
A. Waiver and Severability
The failure of Code.org to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. In the event that any provision of these Terms is held to be invalid or unenforceable, then that provision will be limited or eliminated to the minimum extent necessary, and the remaining provisions of these Terms will remain in full force and effect.
B. Controlling Law and Jurisdiction
These Terms and any action related thereto will be governed by the laws of the State of Washington without regard to or application of its conflict of law provisions or your state or country of residence. All claims, legal proceedings or litigation arising in connection with the Services will be brought solely in the federal or state courts located in King County, Washington, United States, and you consent to the jurisdiction of and venue in such courts and waive any objection as to inconvenient forum.
If you are a federal, state, or local government entity in the United States using the Services in your official capacity and legally unable to accept the controlling law, jurisdiction or venue clauses above, then those clauses do not apply to you. For such U.S. federal government entities, these Terms and any action related thereto will be governed by the laws of the United States of America (without reference to conflict of laws) and, in the absence of federal law and to the extent permitted under federal law, the laws of the State of Washington (excluding choice of law).
C. Entire Agreement
These Terms are the entire and exclusive agreement between Code.org and you regarding the Services (excluding any services for which you have a separate agreement with Code.org that is explicitly in addition or in place of these Terms), and these Terms supersede and replace any prior agreements between Code.org and you regarding the Services. No other person or company will be third party beneficiaries to the Terms.
These Terms and any rights and licenses granted hereunder, may not be transferred or assigned by you, but may be assigned by Code.org without restriction. Any assignment attempted to be made in violation of these Terms shall be null and void.
You agree, to the extent permissible by law, to indemnify, defend, and hold harmless Code.org, its affiliated companies, contractors, employees, agents and its third-party suppliers, licensors, and partners (“Code.org Indemnitees”) from any claims, losses, damages, liabilities, including legal fees and expenses, arising out of any use or misuse of the website, the Services, any violation of the Terms, or any breach of the representations, warranties, and covenants made herein, whether by You or by any Child associated with you if you are a Parent. Code.org reserves the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify Code.org, and you agree to cooperate with Code.org’s defense of these claims. Code.org will use reasonable efforts to notify you of any such claim, action, or proceeding upon becoming aware of it.
We may revise these Terms from time to time, the most current version will always be at code.org/tos. If the revision, in our sole discretion, is material we will notify you via an e-mail to the email associated with your account. By continuing to access or use the Services after those revisions become effective, you agree to be bound by the revised Terms.
If you have any questions about these Terms, please contact us.
Date of Last Revision: February 22, 2018
Code.org® is a nonprofit dedicated to expanding participation in computer science by making it available in more schools, and increasing participation by women and underrepresented students of color.
Code.org Privacy Principles
- We’re deeply committed to creating a safe and secure learning environment for our students and teachers. We take the protection of this information seriously.
- We do not require you to provide any Personal Information in order to try our courses, most of which are accessible without a User account. However, learning progress won't be saved without creating an account.
- The only reason we collect any data from Students or Teachers is to better succeed at our mission of providing a great computer science education for every student in every school.
- We do not sell your Personal Information or exploit it for financial gain; we do not sell ads. We are a charitable 501(c)(3) nonprofit and our revenue comes from donations. We established ourselves as a nonprofit so our mission and your trust will not be in conflict with a for-profit motive.
- Any student academic data provided by us or by our school district partners to third party evaluators for the purpose of evaluating our courses in meeting our mission will be de-identified (per standard industry practice).
- We strive to provide you with access to and control over the information you give us (as detailed below), and we take the protection of your information very seriously.
- When student Personal Information is provided to Code.org by a school or school district, Code.org agrees to retain such information as directed by the school or school district.
- We hold our partners to privacy and security practices no less stringent than our own.
We are committed to creating a safe and secure environment for learners of all ages on our websites located at https://code.org, https://studio.code.org, https://csedweek.org, https://hourofcode.com, https://curriculum.code.org, https://forum.code.org, https://codeprojects.org, other websites, application programming interface (our “API”), and online services (collectively, our “Website”). Visitors and users of the Website and participants in our education programs are referred to individually as “User” and collectively as “Users”. Any User that creates a student account is referred to as “Student” even if they are using the Code.org Website outside of a school setting. Similarly, any User that creates a teacher account is referred to as “Teacher.” As a not-for-profit, 501(c)(3) organization, we use the data we receive only insofar as it helps our mission of providing a great computer science education for every student in every school. We established ourselves as a not-for-profit organization so that a for-profit motive will not interfere with our mission of providing a trusted educational resource.
Collection and Use of Your Information
The sections below describe the ways Code.org collects and uses the name, display name, email address, school name and address, telephone number, etc. from Users (“Personal Information”), persistent cookies or IP addresses (“Persistent Identifiers”), as well as some of the non-Personal Information and technical information (described below) we collect. We collectively refer to any of this data we collect from Students, along with any Student information, Student records, and Student-generated content as “Student Data.”
The Hour of Code: Code.org does not collect any Personal Information from students participating in the Hour of Code. The Hour of Code tutorials do not require login to use.
Code.org accounts: The following table describes the data that Code.org collects from registered Users of Code.org courses. You can also try Code.org courses without creating an account, but your learning progress won't be saved.
|Data stored by Code.org if you create a Code.org Student account
||How this data is used
|Display Name (e.g., “Cool Coder” or “John”) and username (eg "coolcoder7")
||Display name is used to provide Students a welcoming login and to identify the Student in the Teacher’s view of student progress. We recommend using first names only to increase privacy.
Usernames are generated based on the display name and can be used to sign into an account. Students have the option to update the username when creating a personal login that uses usernames.
|Age (Not birthdate)
||This data is used to understand the developmental stage of Students in order to offer an age-appropriate experience for each Student. We use this field to ensure we don’t allow Students under age 13 to access age-restricted features (such as sharing their coding projects on social media). We store ages (e.g., 16), as opposed to birth dates (e.g., Feb 13, 2001).
|One-way hash of student email address (NOT the actual email address, which is collected in the web browser but never transmitted to Code.org and thus never stored by us)
||Optional if account created by Teacher; Mandatory if Student signs up directly
||A Student's email address is only used for the purposes of login. It is NOT stored by Code.org in a retrievable format. To protect Student privacy, we only store a one-way hash of the email address. We do not have any way of sending email to Students or retrieving their actual email addresses. See section on "Student Email Addresses" below for more details.
|Parent or guardian email address
||Optional - parent can use their email to create a login for their child at home
||A Student may want to create a personal login to access their account independently of their Teacher, especially if the Teacher decides to delete the classroom section that the student belonged to.
If the Student is under 13 or doesn’t have a personal email address and wants to create a personal login, we require a parent email address for password recovery. The Student will then be able to sign in at home with a username and password.
|Login time, IP address, and other technical data
||This data helps Code.org troubleshoot any problems Users experience. It also helps Code.org understand usage patterns, ensure the service can support all Users, and enable site updates with minimal service disruption. See section below on “technical information” for additional details.
||This information is only used in aggregate to measure the percentage of students that are male or female or to measure how male or female Students respond to different computer science challenges, or to track our progress towards reducing the gender gap in computer science.
||Students aged 13 and over have an option to indicate their race. For Students under age 13 we do not ask individual race, but we ask the Teacher to optionally estimate the racial distribution of the entire classroom.
This information is only used in aggregate, to measure the percentage of Students from underrepresented minorities and their aggregate response to computer science challenges, in order to track our progress toward improving diversity in computer science.
|Progress in the course
1- Date/Time each lesson is tried
2- Number of tries to solve a level, and whether it was solved successfully or optimally
3- Information on how the Student solved the level including time to completion and whether they used hints
4- The code that the Student submitted
5- Student-provided answers to simple assessments (e.g., multiple-choice questions)
|Automatic (for Students who work through a tutorial or course progression)
||This information is displayed to Students and their Teachers to see their progress in a course, to see the code they’ve created, and to identify topics they need help with. It also lets Students pick up where they left off if they sign out and sign in later. See example progress report, and see section below on “technical information” for additional details.
This data, in de-identified form, also helps Code.org improve course effectiveness. For example, if a level is too hard, Code.org may take action (like providing better hints) to improve the learning process.
|Student projects - apps, animations, stories, or code-art
||Automatic (for Students who create such projects)
Creating apps and projects is part of our course progressions.
|The code and underlying assets for these apps are stored by Code.org, so that Students can retrieve their projects each time they log in.
When Students work in the context of a classroom, their Teacher also has access to view the projects created by any Students in the classroom.
Student projects and code creations each have a custom URL that Students can use to share with others, or post to the Code.org public gallery. On the public gallery, projects are displayed with only the first letter of the Student’s display name to protect Student privacy as well as their age. We do not allow Students under the age of 13 to share App Lab, Game Lab, and Web Lab projects to the Code.org public gallery as these projects allow for Student-uploaded content.
Students may “remix” (copy, change, or improve upon) projects made by themselves or by other Users.
Students over age 13 can also, at their discretion, post their projects to social media.
In our elementary school courses, Students create stories, games, or art using tools, such as Play Lab, which are limited to using artwork and sounds provided by Code.org. Students can write dialogues for these projects. Text provided by Students in these tools is automatically analyzed to help prevent sharing any email addresses, phone numbers, or street addresses.
Our middle school and high school courses teach Students to make more complex apps and games. These tools allow the Students to upload custom photos, sounds and/or videos. (See below)
|Student-uploaded images, sounds, or videos (for App Lab, Game Lab, and Web Lab Projects)
||Automatic (if content is uploaded). Creating apps with these tools is part of our courses for grades 6+.
Uploading custom files is optional.
These files are not used by Code.org for any purpose other than within these projects. These projects may be shared and remixed as described above, subject to those restrictions imposed on Students under 13.
|Data collected by Student-created apps
||Students may use Code.org to create their own apps. Depending on the app author’s design, a Student-created app may in turn collect data by prompting other Users (anybody who tries using the Student-created app) to enter information, such as a favorite movie.
If a Student creates an app that collects and stores data in this fashion, all data entered by Users of the app may be accessed and possibly shared publicly by the app author, the app itself, and potentially anybody with a link to view the app. Code.org does not itself use or share this data outside of the app.
Before using a Student-created app that collects data, Users are shown a clear warning that any data they enter may be shared publicly and that they should not share anything personal to them or to others.
|Written comments in response to curricular/educational prompts within Code.org courses
||Within some of our courses, Students in a classroom are prompted to answer a question. Their answers are shared with any Teacher with whom the Student is affiliated on Code.org and are used by Code.org in de-identified form to improve the curriculum.
|Student-provided responses to surveys (e.g., multiple choice and free response questions)
||We may ask for responses to attitudinal questions (to assist the Teacher in understanding their classroom’s reaction to learning computer science and, in de-identified form, to help Code.org improve our curriculum). Students are informed that answers to these attitudinal questions are shared with the Teacher anonymously without their name attached. We may, however, share a Student’s identity, answer, and other information related to a given question with their teacher or appropriate authorities if we are prompted to do so, and upon investigation, we have a good-faith and reasonable belief that the answer indicates the Student may harm themselves or others, among a few other limited scenarios outlined in the section titled “How We Share or Transfer Data.” However, we are not monitoring student answers for such issues. If you are a teacher, please contact email@example.com so we can help you if your Student indicates they may be unsafe.
|Additional* data stored by Code.org if you create a Code.org Teacher account
||How this data is used
||Email addresses are used to send emails to the Teacher with updates about their classroom or Student progress, send notices when new course-work is available, and provide updates on curriculum, tools, professional learning options, etc.
All non-transactional emails sent by Code.org contain an unsubscribe link and do not require typing a password to unsubscribe.
|District and school name and/or school type (private, public, charter, homeschool, after school, or other) and/or school address
||At the Teacher's option and under their control, we would list their school in the Code.org map and database of schools that teach computer science courses.
Code.org or our Regional Partners** may also use this information to reach out to the Teacher's school or district to discuss broader education partnerships or participation in special events.
|Student section data
||The Teacher may create accounts for their students (and provide each Student’s display name and optionally their age and gender), and organize these Students into sections. The Teacher may assign each section a display name, a course assignment, and grade level. The section grouping data is used to simplify their view of Students across multiple sections.
Teachers are encouraged to share a document with Students and parents informing them about the Code.org course, including the privacy implications.
|Survey and demographic data
||For the purposes of evaluating our own work and improving our education results, Code.org regularly sends surveys to Teachers.
These surveys are completely optional. The data provided by Teachers in these surveys is saved and used for analysis by Code.org, our Evaluator, our Regional Partners, or facilitators. Any survey data shared with external parties will be de-identified and aggregated.
|Attendance at professional learning workshops
||Participation in professional learning programs is optional.
For Teachers who participate, this attendance data will be stored.
|Attendance of Teachers at our professional learning workshops is stored and associated with the Teacher’s account on Code.org.
This data may be shared (along with the Teacher’s identity) with any other parties involved in the Teacher’s professional learning, such as the in-person facilitator who led the workshop, or the professional learning organization hosting the workshop, or the school district of the Teacher. In some cases, the school district may use the workshop attendance data to compensate Teachers for participating in the Code.org professional learning program.
|Progress, answers, documents, projects, and peer reviews for online professional learning.
||Participation in professional learning programs is optional.
For Teachers who participate, this data will be stored.
|Progress and answers in online professional-learning courses for Teachers are stored in their Teacher account in order to allow Teachers to pick up where they left off.
This includes the lesson plans, documents, and other projects Teachers create as part of finishing the online learning courses. After submitting a document or project, Teachers receive peer feedback from each other which is also stored so that they can read it.
Teachers also take a self-assessment survey to create a custom learning plan. The results of this survey are stored with the Teacher’s account along with their custom plan.
|Forum posts and profiles
||For Teachers who choose to participate in the Teacher support forums at forum.code.org, posts and replies are shared publicly. Teachers may also optionally supply additional information for their forum profile, including their profile picture, location, website, and “about me” text. This information is used in no other way beyond the forum itself.
* A Teacher account on Code.org has all the functionality of a Student account, and as a result the data collected and stored for a Teacher account is a superset of the data stored for a Student account.
Students and Teachers may update, correct, or delete Personal Information in their Code.org accounts at any time via the account settings page. Teachers can go to their section’s “Manage Students” tab to update the most common settings or to access a Student’s login information. Teachers also have the ability to reset the password of any Student in their section. A parent or legal guardian of a Student under the age of 18 may also review Personal Information and correct erroneous information, if any, by asking the Student or Teacher to access the Student account.
Student Data of any Student that is in a Teacher's section will continue to be under the control of the Teacher. If a Student over the age of 13 or a parent of a Student of any age attaches a personal email login to a Student account, the Student can add or remove themselves from a Teacher's section. Users over the age of 13 who use email or a third party login such as Clever, Google Account or Microsoft Account can also add or remove themselves from as many sections as they want (unless the section is synced with Google Classroom or Clever). The Teachers for these sections get access to the User's course progress and display name, but not their email address. If a Student is no longer associated with a Teacher’s section, that means the Student Data will no longer be managed by the school or Teacher and the Student may retain possession and control of the Student-generated content.
In order to allow Users to recover deleted accounts, we will save progress, code creations and data for a period of time. A User can email firstname.lastname@example.org to request permanent deletion of their account and all the associated data. A Teacher may also request the deletion of Student accounts or particular Student projects or Student Data the same way. Deleting a Student’s project will not delete other Students’ creations that were previously remixed from the deleted project.
Information from Authentication Services like Facebook or Google
Other Services Provided by Code.org
When you use certain other features of our Website, such as signing forms or petitions to help advocate for Code.org, providing information to put your school on the map of schools teaching Computer Science, participating in a workshop, bringing Code.org programs to your school or district, donating to Code.org, purchasing t-shirts or other items, or participating in online surveys, Code.org may ask you to provide Personal Information including your full name, email address, school name, and postal code or school street address, as well as your billing and/or shipping information when necessary to complete a purchase or make a donation. The information is used to enable your participation in the relevant feature and to send you occasional emails with information about Code.org that we feel may interest you. All non-transactional emails we send include an “unsubscribe” link. The one exception to this paragraph is when a User under the age of 13 signs our online petition supporting Code.org’s mission, any name or email address they provide is deleted from our servers and thus never used.
If you enter your name to print a certificate of completion upon finishing our courses, we save the name you enter in order to let you share your certificate digitally.
We may also survey Users to provide us with optional demographic information (such as gender, age, ethnicity), which we use in aggregate to better understand our User base.
Computer science educators may provide a school or classroom street address, along with a description of course offerings, in order to allow students or parents to find local schools, summer-camps, or workshops that teach computer science in their neighborhood.
Lastly, for teachers, educators, and partners who participate in our computer science training programs, we may ask for information that is required for compensating or acknowledging you for your work (such as a mailing address to send a check, the name of the school/district that employs you, or a tax form containing your social-security number for IRS reporting purposes).
We may collect and store information about your location to provide you with educational experiences or email updates that are tailored for your region. The location information we have access to may include: (1) your ZIP or postal code, if you provide one to us; (2) the approximate geographic region your computer or mobile device is located in, as determined from your IP address (You may be able to change the settings on your computer or mobile device to prevent it from providing us with such IP information); (3) your school or classroom location, if you (as a teacher) provide it to us, in order to allow us (with your permission) to display the classroom location on a map or in search results for parents looking for schools that teach computer science. Code.org does not request or collect your exact GPS location, and your billing and shipping addresses are not used for these purposes.
Information from Other Sources
To provide a personalized learning and high-quality experience for our Users, we may use various technologies that automatically record certain technical information from your browser or device, including browser language settings, standard log files, web beacons, or pixel tags. This technical information may include your Internet Protocol (IP) address, browser type, internet service provider (ISP), referring or exit pages, click stream data, operating system, and the dates and times that you visit the Website. This information assists us in understanding how our Users are using our Website.
To track information about use of our Sites, we use various technological tools. For example: Like most websites, whether or not you are a registered member, we may send one or more cookies – small text files containing a string of alphanumeric characters – to your computer. Cookies remember information about your activities on a website and enable us to provide you with a more personalized learning experience. Code.org may use both session cookies and persistent cookies. A session cookie disappears automatically after you close your browser. A persistent cookie remains after you close your browser and may be used by your browser on subsequent visits to the Website. You can, however, remove a persistent cookie at any time. Please review your web browser Help file, Tools menu, or other similar menu options to learn the proper way to modify your cookie settings, or visit www.allaboutcookies.org. Please note that without cookies you will not have access to certain services and features on the Website.
A pixel tag (also known as a “clear GIF” or “web beacon”) is a tiny image – typically just one pixel – that can be placed on a Web page or in an email to you to tell us when you have displayed that page or opened that email.
Third Party Service Providers
Code.org may use a variety of third-party service providers, such as email services to send email, analytics companies to understand our Website usage, and social networking platforms to host our videos. We may allow third-party service providers to place and read their own cookies, web beacons, and similar technologies to collect information through the Website. This technical information is collected directly and automatically by these third parties.
We use third party services to implement our Website and all of its associated services and features, including Amazon Web Services, Pardot, VoterVoice, and MailChimp (for sending email), and Twilio (for sending User code-creations to phones). Personal Information or Persistent Identifiers will be used and stored by these third parties solely in context as an implementation services provider to Code.org, but these third parties will not receive any ownership or have any other rights to access or use this Personal Information or Persistent Identifiers. In particular, when we use Twilio to send text messages to deliver User code-creations to phones, Code.org does NOT store the phone number, and further instructs Twilio to delete the phone number after delivering the text message, but it is possible that underlying phone-service providers may retain this information.
Code.org does not allow advertising on our Website, and we do not have the ability to collect your web search history across third-party Internet websites or search engines. However, if you navigate to the Code.org Website via a web search, your web browser may automatically provide to us the web search term you used in order to find Code.org. Because Code.org doesn’t display advertising or track browsing on third party sites, we do not do anything different in response to “do not track” signals transmitted by web browsers. Certain third-party entities that we use to provide website functionality or social sharing – such as embedded YouTube videos or Facebook or Twitter sharing buttons – may collect Non-Personal Information for the purposes of online behavioral advertising, but our Website is designed to continue functioning in schools that disable access to YouTube, Facebook, or Twitter. We encourage you to visit the following links if you would like to opt out of online behavioral advertising: http://www.networkadvertising.org/choices or http://www.aboutads.info/choices/. If you do want to opt out from using these tools, you may need to opt out separately for each of your devices and for each Web browser on each device.
Uploading Custom Content
Student and Teacher profiles can NOT be customized with a photo.
As part of “App Lab,” “Game Lab,” or "Web Lab" (in-browser programming tools available on Code.org), Users 13 years of age and older as well as Students under the age of 13 in a classroom managed by a Teacher can upload custom images, text, sound, and videos to the Code.org platform to use within applications or “apps” that they create. These files are stored by Code.org, and are not used by Code.org for any purpose other than within the applications created by Users.
Message Sending Between Users
Code.org has created a tool called the “Internet Simulator” for use in High School classrooms to model how the Internet functions. With this tool, Students participating in a Teacher-supervised classroom activity can send text-based messages to their Teacher and to other Students in their specific classroom section. Message contents are visible to the classroom Teacher and are not accessed or used by Code.org for any purpose other than in this educational tool. All messages are deleted after two hours of class inactivity, or upon a manual reset by the Teacher.
In some courses, Students are asked to provide written responses or reflections to prompts within Code.org courses. These written responses are accessible by any Teacher that the Student is currently affiliated with on Code.org.
In addition, Users may send messages to Code.org for customer-support requests.
Other than the above, the Website supports no other form of messaging among Users.
Testing and Staging web sites
Information We Do NOT Collect
Code.org does not directly collect or store payment instruments. Donations to Code.org or purchases from the Code.org store are processed via third parties, and although Code.org receives a receipt for donations (for tax purposes), we never receive the payment instrument (such as credit card or wallet information).
Student Email Addresses
When User accounts use a Student email address for login, Code.org does not store the email address provided by those Users in a retrievable format. Instead, we immediately create and store only a one-way hashed version of the email address (which cannot be converted back into the original address), and use it only for the purposes of login, account management, and password recovery. In fact, when creating or signing into a Student account, the actual account email address is never even transmitted to Code.org's servers. The only circumstance when Code.org's servers receive a Student's Code.org email address is if the Student forgets their password and asks to reset it. At that point, the Student is prompted to enter their email, which is used to send them a password reset link.
If a User contacts us via our customer support pages, we will store and use their email address in order to respond to them. If a User over the age of 13 signs our online petitions, or a User creates a Teacher account on Code.org or offers to help us as a software industry volunteer, we will store and use their email address just as we do for other advocates of our nonprofit mission.
For a small minority of our Students, and only if they are over the age of 18, we may offer the opportunity to participate in a "longitudinal" study to understand the multi-year impact of learning computer science. Participation in such a study would be entirely optional. Students who receive an offer and choose to participate will be asked to provide their contact information (email address and optionally other forms of contact that may be more convenient for the Student). This contact information will not be shared with third parties, nor used in any way outside the purpose of such a study – to ask Students to participate in surveys. If we learn that we have inadvertently collected this information from a Student under 18, we will delete such information immediately.
Children Under Age 13
Code.org courses are designed to be used by Users of all ages, including children under the age of 13 with the involvement of and pre-authorization by their school, teacher, parent or legal guardian. In order to use features that involve uploading custom media files or sending messages within the school, we obtain prior consent from the Student’s teacher, other authorized school representative, or, in some cases, the parent or legal guardian.
When children under the age of 13 attempt to sign our online petition supporting Code.org’s mission, the email addresses and names are discarded and are not stored on our server.
If Code.org learns that it has inadvertently collected Personal Information or Persistent Identifiers from children under the age of 13 without prior parental or teacher consent, Code.org will take appropriate steps to delete this information. If you are a teacher, parent or legal guardian of a Student on Code.org, you can ask us to deactivate the Student’s account, delete any hashed email address or inadvertently collected Personal Information or Persistent Identifiers, and request that we no longer allow the Student to submit their information to Code.org. To make such a request, please contact us at https://code.org/contact. Before processing your request, we may verify your identity and your relationship with the Student.
Student Academic Data from School Districts
As is common in education research, to measure how well our programs perform and how well students are learning from them, Code.org engages experienced independent third parties (“Evaluators”) to do a thorough evaluation of our work in select partner school districts.
If a district chooses to participate in an evaluation, the school district is asked to provide student academic or demographic data from education records directly to the Evaluator, and they are only authorized to provide data that has been completely de-identified. The data enables the Evaluators to perform an independent study about our work, in compliance with all applicable Federal and local laws respecting student privacy. Neither Code.org nor the Evaluators will know the personal identity of individual students. When it comes to student assessments and academic results, Code.org will only allow districts to provide the Evaluators de-identified data, which will then be aggregated by the Evaluators across thousands of students from hundreds of schools to publish an independent study. Besides the de-identification of this student academic data, our historic contracts with school districts (in 2014-16) also specify very strict limits on who may access this data. You may read the template we used for contractual language governing student-data in our district agreements at https://code.org/educate/template-district-agreement. This language is historical in nature – as of 2017, Code.org is no longer signing direct partnership agreements with school districts.
Limitations on Access to your Personal Information by Employees and Authorized Parties
How We Share or Transfer Data
We do not rent or sell Personal Information, Persistent Identifiers, or any other information that we collect from Users, or exploit it for financial gain in any other way. Code.org will never share or grant rights to Personal Information with other third-party organizations to use without your consent, except as part of a specific program or feature for which you will have the explicit ability and choice to opt-in.
Whenever we share Student personal data, we hold our partners to privacy and security practices no less stringent than our own.
In particular, we do not share any Personal Information you provide with our donors or sponsors (other than the "Public Reporting" of de-identified reports as described below).
We may share Student achievement data with your school or school district
If your use of the Code.org Website is in the context of a partnership with your school or school district, we may allow the school or school district to access the same Student progress report that is also shared with your Teacher(s).
We may share teacher information with the teacher's training facilitators, Regional Partner, and school district, as well as other partners
Part of our educational program is to offer professional learning workshops to prepare teachers to offer computer science courses. If you are a Teacher participating in one of these workshops, your name and contact information will be shared with the facilitator and/or the local Code.org Regional Partner who runs the professional learning program in your area. In addition, the facilitator, Regional Partner, and your school district will have the opportunity to access your continued progress in our in-person and online professional learning courses in order to coach you, facilitate your additional learning, and follow your professional development progress. (In some cases, your school district may require this information in order to compensate you for workshop attendance). They may also be able to see your overall class progress to support your classroom. The Regional Partner and facilitator will not have any data on specific Students, but they will be able to see the overall number of students and class demographics. If Code.org is paying for your travel to our professional learning workshops for Teachers, we will - with your explicit permission - share your name and contact information with our travel partner to facilitate booking your travel. We may also share the list of schools (solely the school identities, without any information about teachers or students) that have participated in our professional learning program with select partners, such as a local government department of education, so long as such partners agree to treat the information as confidential.
We also provide teachers other opportunities (such as when adding their school to the map of schools teaching Computer Science) to share their contact information (name, school, email) — at their option and under their control — with a Code.org Regional Partner so that teachers can be contacted about local professional learning workshops, resources, and events.
We may share de-identified information on school or district usage with our Regional Partners
Our Regional Partners will be able to see de-identified demographic information and usage of courses and professional learning programs for schools and districts in their area. They will not see names or contact information of any Teacher unless that Teacher chooses to share it as part of signing up for a local professional learning workshop or joining their professional learning program.
You (entirely under YOUR control) may share data with social networks
Some of our Users choose to post their code-creations to social networks. This functionality is entirely optional. When you post content to social networks, the actual content posted is entirely at your control, and never posted automatically on your behalf. Typically this content includes only the code (app or animation or game or other) that you wrote, posted alongside any other remarks you may choose to add to it.
We may share limited information when you contact us for support
When you contact us with a support request, you may provide Personal Information, which is shared with a Code.org support representative in order to process your request. Code.org support representatives are either employees or independent contractors of Code.org, and will always have signed a contract requiring them to protect and not disclose confidential information including Personal Information of Users, and to use it only in the context of resolving your product support requests.
If you are chosen to be profiled on our site
Code.org promotes Student and Teacher work on our site and social media channels. These profiles and similar testimonials are always published with the permission of the participating Student or Teacher and, if applicable, their parent or legal guardian, or teacher, and may include Personal Information such as the name, likeness and photo or video of the person being profiled.
Public reporting on Student use and performance
We may publish de-identified information about Student performance on our tutorials and Websites, however, we will never publicly disclose your Personal Information in these reports. Data about Student performance will remain de-identified. However, aggregated, de-identified data over large populations of Students may be reported by demographic criteria such as age, general location, gender, ethnicity, and socioeconomic status.
We may share de-identified or aggregate data to improve our services and learn more about our Users
In certain occasions, Code.org may work with third parties (such as universities and education research organizations) to improve our services or offerings. We may disclose automatically collected and other aggregated and de-identified non-Personal Information to authorized partners to conduct research on online education or assist in understanding the usage, viewing, and demographic patterns for certain programs, content, services, promotions, and/or functionality on the Website. We require any research partner that receives de-identified data from us to agree in advance that they will not attempt to use this data to identify our Users.
We will share data when required by law
Code.org may also disclose User data including Personal Information or Persistent Identifiers if required to do so by law, or if we have a good-faith belief that such action is necessary to comply with local, state, federal, international, or other applicable laws or respond to a court order, judicial or other government order, subpoena, or warrant, or administrative request. In some cases, we may make such disclosures without first providing notice to Users, Teachers, schools, parents or legal guardians.
We may share data when necessary or appropriate to protect Code.org or others
Code.org may disclose User data including Personal Information or Persistent Identifiers that we believe, in good faith, is appropriate or necessary to: take precautions against liability; protect Code.org from fraudulent, abusive, or unlawful uses; investigate and defend ourselves against any third-party claims or allegations; assist government enforcement agencies; protect the security or integrity of the Website; or protect the rights, property, or personal safety of Code.org, our Users, or others.
We may share data in the context of a change of business, including a merger or acquisition
Our Approach to Data Security
Website security is important to you, and to us
To protect your privacy and security, we take reasonable steps to verify your identity before granting you account access or making corrections to your Personal Information.
Data we choose not to store
Although you may provide it to us, we intentionally choose NOT to store email addresses for Code.org Student accounts, or phone numbers used in our send-to-phone feature. The data we do not store cannot be stolen from us.
We will delete Student display names, coding projects, apps, uploaded images and other assets associated with Student accounts that have remained unused and inactive for a period of time, in accordance with our data retention policy.
We try to ensure that our Website and information sent to us are safe, but no security measures are perfect
Code.org uses certain physical, administrative, and technical safeguards designed to reasonably protect the confidentiality, availability, integrity and security of your Personal Information, Student Data, and other information we maintain in connection with the Website. These safeguards include restrictions on physical access to the data center, hardened system configuration, two-factor authentication, patch management, disaster recovery process, employee security and privacy training, and employee background checks. We cannot, however, ensure or warrant the security of any or all of the Personal Information and other information you transmit to Code.org, and you do so at your own risk. Once we receive your transmission of information, Code.org maintains and enforces commercially reasonable efforts to ensure the security of our systems. However, please note that this is not a guarantee that such Personal Information and other information may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, technical, or managerial safeguards.
If we learn of a data security incident that compromises or appears to compromise your Personal Information or that of your Students, then we will attempt to notify you electronically so that you can take appropriate protective steps.
Our Website is operated and managed on servers located within the United States. If you choose to use our Website from the European Union or other regions of the world with laws governing data collection and use that differ from U.S. law, then you acknowledge and agree that you are transferring information, including your Personal Information, outside of those regions to the United States and that, by providing your Personal Information on the Website, you consent to that transfer.
Conditions of Use and Notices
No Commercial Use of Student Data and How to Delete Student Data
Some laws, such as California’s Student Online Personal Information Protection Act (SOPIPA), prohibit the gathering of the Personal Information of K-12 students. Code.org abides by such laws and shall not use, disclose, or compile any student Personal Information for the purpose of marketing or advertising commercial products or services. We do not disclose any student Personal Information to third parties for marketing purposes. A student may request to have their Personal Information deleted from the Code.org database at any time.
For additional information about our privacy practices, please contact us at https://code.org/contact. You can also send us a request to review and/or delete any Personal Information you have shared with us.
Date of Last Revision: August 24, 2016
Code.org® is a non-profit dedicated to expanding participation in computer science by making it available in more schools, and increasing participation by women and underrepresented students of color.
1. Authorization from the School
With regard to school-based activities, COPPA allows teachers and school administrators to act in the stead of parents to provide consent for the collection of personal information from children.
Code.org wishes to provide students under the age of 13 with full access to Code Studio, including App Lab and Game Lab, if the student is part of a section supervised by a teacher who is also using Code Studio. Full access will allow the students to use tools where students can create and/or upload custom content (images, sounds, and text) in a classroom. Students under the age of 13 cannot use these tools unless they are part of a teacher’s Code Studio section.
Providing access to students under the age of 13 means that they can create and share simple apps that use custom images, sounds and freeform text. This gives them the ability to share personal and non-personal information. We need your explicit prior consent before we enable this app-creation functionality for your students, because the code and the data for these apps would be stored by Code.org and would be accessed by anybody with whom the student shares their app.
2. Information We Collect and Use
Code.org only collects information from students for the use and benefit of the school, and for no commercial purpose. Code.org does not create marketing profiles and online behavioral advertising campaigns using information collected from or created by students.
In any instance that we collect personal information from a student, we will retain that information only so long as reasonably necessary to fulfill the educational activity request or allow the child to continue to participate in the educational activity, and ensure the security of our users and our services, or as required by law. Code.org will delete student display names, coding projects, apps, uploaded images, and other assets associated with student accounts that have remained unused and inactive for a period of time in accordance with our data retention policy. We do not require a child to provide more information than is reasonably necessary in order to participate.
In the event we discover we have collected information from a child in a manner inconsistent with the requirements of COPPA or any other national or local laws, we will either delete the information or immediately seek the parent or the school’s consent for that collection.
Hour of Code
Code.org does not collect any personal information from students participating in the Hour of Code. The Hour of Code tutorials do not require login or parental consent to use.
At Code.org, we collect limited personal information from registered users of the Code Studio tutorial platform. Users can also try Code Studio tutorials without creating an account, but their learning progress won't be saved.
The following table describes the personal data that Code.org collects from registered students on the Code Studio tutorial platform:
|Data stored by Code.org if you create a Code Studio student account
||How this data is used
|Display Name (eg “Cool Coder” or “John”)
||To provide students a welcome upon login and to identify the student in the teacher’s view of student progress. We recommend using first names only to increase privacy.
|Age (Not birthdate)
||To understand the developmental stage of students to offer an age-appropriate experience for each student. We use this field to ensure we don’t allow students under age 13 to access age-inappropriate features (such as sharing their coding projects on social media). We collect ages (e.g. 16), as opposed to birthdates (e.g. Feb 13, 1998).
|1-way hash of email address (NOT the actual email addresses, which are collected in the web browser but never transmitted to Code.org and thus never stored by us)
||Optional if account created by teacher or parent; Mandatory if student signs up directly
||If a student creates an account directly, an email address is required. If the account is created by a teacher or parent, it is optional.
|Login time, IP address, and other technical data
||This information is only used in aggregate, to measure the percentage of students that are male or female or to measure how males or females react to different computer science challenges, to track our progress towards reducing the gender gap in computer science.
||Students ages 13 and over have an option to indicate their race. For students under age 13 we do not ask individual race, but we ask the teacher to optionally estimate the racial distribution of the entire classroom.
This information is only used in aggregate, to measure the percentage of students from underrepresented minorities and their aggregate reaction to computer science challenges, in order to track our progress toward improving diversity in computer science.
|Progress in the course
1- Date/Time each stage is tried
2- Number of tries to solve a puzzle, and whether it was solved successfully or optimally
3- Information on how the student solved the puzzle including time to completion and whether they used hints
4- The code that the student submitted
5- Student-provided answers to simple assessments (e.g. multiple-choice questions)
This data also helps Code.org improve the course effectiveness. For example, if a puzzle is too hard, Code.org may take action (like providing better hints) to improve the learning process.
|Student Projects - apps, animations, stories, or code-art
||Automatic (for students who create such projects)
Creating apps and projects is part of our course progressions.
|The code and underlying assets for these apps are stored by Code.org, so that students can retrieve their projects each time they log in.
When students work in the context of a classroom, their teacher also has access to view the projects created by any students in the classroom.
Student projects and code creations each have a custom URL that students can use to share with friends or their teacher, or post to the Code.org public gallery. On the public gallery, projects are displayed with only the first letter of the student’s name to protect student privacy.
Students may “remix” (and change or improve upon) projects made by themselves or by other students.
Students over age 13 can also, at their discretion, post their projects to social media.
In our elementary school courses, students create stories, games or art using tools, such as Play Lab, which are limited to using artwork and sounds provided by Code.org. Students can write dialogues for these projects. Text provided by students in these tools will be automatically analyzed to prevent sharing any personal email addresses, phone numbers, or street addresses.
Our middle school and high school courses teach students to make more mature apps and games. These tools allow the students to upload custom photos, sounds and/or videos. (see below)
|Student-uploaded images, sounds, or videos (for App Lab and Game Lab Projects)
||Automatic (if content is uploaded). Creating apps with these tools is part of our courses for grades 6+.
Uploading custom files is optional.
These files are not used by Code.org for any purpose other than within these projects. These projects may be shared as described above, subject to those restrictions imposed on students under 13.
|Data collected by student-created apps
||Students may use Code Studio to create their own apps. Depending on the app author’s design, a student-created app may in turn collect data by prompting other Users (anybody who tries using the student-created app) to enter information, such as a favorite movie.
If a student creates an app that collects and stores data in this fashion, all data entered by users of the app may be accessed and possibly shared publicly by the app author, the app itself, and potentially anybody with a link to view the app. Code.org does not itself use or share this data outside of the app.
Before using a student-created app that collects data, Users are shown a clear warning that any data they enter may be shared publicly and that they should not share anything personal to them or to others.
|Written comments in response to curricular/educational prompts within the Code Studio platform
||Within some of our courses, students in a classroom are prompted to answer a question. Their answers are shared with any teacher with whom the student is affiliated on Code Studio, and are not used by Code.org for any other purpose.
In some cases, these questions may be attitudinal (to assist the teacher in understanding their classroom’s reaction to learning computer science, and to help Code.org improve our curriculum). Students are informed that answers to these attitudinal questions are shared with the teacher anonymously.
In addition to the information that your students may give us directly, we may collect some non-personal information indirectly. To provide a personalized learning and high-quality experience for the students, we may use various technologies that automatically record certain technical information from their browser or device, including browser language settings, standard log files, web beacons, or pixel tags. This technical information may include the Internet Protocol (IP) address, browser type, internet service provider (ISP), referring or exit pages, click stream data, operating system, and the dates and times that the students visited the Website.
To track information about use of our Sites, we use various technological tools. For example, like most websites, whether or not the user is a registered member, we may send one or more cookies – small text files containing a string of alphanumeric characters – to the user’s computer. Cookies remember information about the user’s activities on a website and enable us to provide the user with a more personalized learning experience. Code.org may use both session cookies and persistent cookies. A session cookie disappears automatically after the browser is closed. A persistent cookie remains after the browser is closed and may be used by the browser on subsequent visits to the Website. Please note that without cookies, the students will not have access to certain services and features on the Website.
A pixel tag (also known as a “clear GIF” or “web beacon”) is a tiny image – typically just one-pixel – that can be placed on a Web page or in an email to tell us when the user has displayed that page or opened that email.
We may collect and store information about the school or classroom location to provide educational experiences or email updates that are tailored for your region. The location information we have access to may include: (1) a ZIP or postal code, if you (as the teacher) provide one to us in order to allow us to display the classroom location on a map or in search results for parents looking for schools that teach computer science; and (2) the approximate geographic region the computers or mobile devices are located in, as determined from the IP addresses (although you change the settings on the computers or mobile devices to prevent them from providing us with such IP information). Code.org does not request or collect exact GPS locations, and your billing and shipping addresses are not used for these purposes.
3. Disclosure of Information
Code.org does not rent or sell personal information that we collect from the students, or exploit it for financial gain in any way. Code.org will never share or grant rights to personal information with other third-party organizations to use without your express prior authorization, except as part of a specific program or feature for which you will have the explicit ability and choice to opt-in. In particular, we do not share any Personal Information you provide with our donors or sponsors.
However, Code.org may disclose anonymous or aggregate data to learn more about our users. In certain occasions, Code.org may work with third parties (such as educational researchers and universities) to improve our services or offerings. We may disclose automatically collected and other aggregate non-personal information to authorized partners to conduct research on online education or assist in understanding the usage, viewing, and demographic patterns for certain programs, content, services, promotions, and/or functionality on the Website. We may also publish anonymized information about student performance on our tutorials and Websites; however, we will never publicly disclose personal information in these reports. Data about student performance will remain anonymized, but aggregated, anonymized data over large populations of students may be reported by demographic criteria such as age, general location, gender, ethnicity, and socioeconomic status.
4. Administrative Choices and Controls
At any time, you (as the teacher) can refuse to permit us to collect further personal information from your students in association with a particular account, and can request that we delete from our records the personal information we have collected in connection with that account. Please keep in mind that a request to delete records may lead to a termination of an account, membership, or other service.
You may write us at http://code.org/contact or at 1501 4th Avenue, Suite 900, Seattle, WA 98101, to request access to review, change, or delete a student’s personal information.
5. Revoking and Deleting Your Consent
At any time, you may revoke your consent, refuse to allow us to further use or collect your students’ personal information, and direct us to delete the information. If you revoke your consent, we will no longer permit your students to participate in certain activities on Code.org. Your students will continue to have access to other activities on Code.org which do not require your students’ personal information.
To revoke your consent, write us at http://code.org/contact or at 1501 4th Avenue, Suite 900, Seattle, WA 98101.