Effective Date: Sept 23, 2014
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.
Our Privacy Notice is fueled by our commitment to the following Privacy Principles:
We are committed to creating a safe and secure environment for learners of all ages on our web sites located at http://code.org, http://csedweek.org, http://computinginthecore.org, http://hourofcode.com, other websites, application programming interface (our “API”), and online services (collectively, our “Website”). Visitors and users of the Website are referred to individually as “User” and collectively as “Users”. 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 who wants it. 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.
Our Privacy Notice describes what information we gather from our Users and others who visit and use the Website, how we use that information, and what we do to protect it. Your use of the Website and any information you provide on the Website are subject to the terms of this Privacy Notice, which is incorporated into and subject to our Terms of Service. Any capitalized terms used but not defined within this Privacy Notice have the meaning given to them in our Terms of Service. By visiting or using our Website, you expressly consent to the information handling practices described in this Privacy Notice.
From time to time our Privacy Notice will change. Code.org will notify Users of any change to our Privacy Notice by posting the revised Privacy Notice with an updated date of revision on our Website. If we make any significant changes to the policy these will be called out with a short notice of the revision posted on the Website homepage. We may also contact Users and notify them of the changes if required by law. We stand behind the promises we make, and will not change how we use any Personal Information we have already collected from Users in any material way without also providing notice of the change via email, through this website, or through other means, and obtaining consent to any new uses. We take the information you provide to us very seriously, and we strive to put you in control of decisions around your information.
The sections below describe the ways Code.org collects and uses the name, email address, school name and address, or other personally identifiable information from Users (“Personal Information”), as well as some of the non-personal information and technical information (described below) we collect.
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 Studio: The following table describes the data that Code.org collects from registered Users of the Code Studio tutorial platform. You can also try all Code Studio tutorials without creating an account, but your learning progress won't be saved.
|Data stored by Code.org if you create a Code Studio student account||Required?||How this data is used|
|Display Name (eg “Cool Coder” or “JohnS”)||Mandatory||To provide students a welcome upon login, to identify the student in the teacher’s view of student progress, and when showcasing the student’s code-creations.|
|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- The code that the student submitted. (This includes art and games they create)
|Mandatory (automatic)||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 log out and login later. See example progress report, and see section below on “technical information” for additional details.
Student code creations (art, animations, apps) may be shared with friends or to a public gallery at the discretion of the student, along with the students’ display name.
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.
|Login time, IP address, and other technical data||Mandatory (automatic)||This data helps Code.org troubleshoot any problems users experience. It also helps Code.org understand usage patterns, to guide the build out of servers to support all users, and to enable updating the site while minimizing service disruption. See section below on “technical information” for additional details|
|Email Address||Optional if account created by teacher or parent
Mandatory if student signs up directly
|To inform the student or parent when new course-work is available. The student’s email address is optional when a teacher or parent creates a student account. If a student creates an account directly, an email address is required, to enable Code.org to help the student User retrieve their forgotten password.
If provided, the email can be used by the student as their Code.org login username and unique identity.
If provided, the student email address is private and not shared with anyone (not even the teacher)
Note: See section below for details on how we handle email addresses from children under 13.
|Gender||Optional||This information is only used in aggregate, to measure the total % of students that are male or female, to track our progress towards reducing the gender gap in computer science.|
|Age (Not birthdate)||Mandatory||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 store email information for students with age < 13. We collect ages (eg 16), as opposed to birthdates (eg Feb 13, 1998)|
|Any phone number||Optional||Users aged 13 or older can choose to share their app, art, or other code creations to a phone. To do this, they are asked to provide a phone number (their own or someone else’s). Code.org uses a 3rd party service (Twilio) to send a pre-written text message to this number. Code.org does not store any record of the number, however the phone number and message will be stored by Twilio and may also be stored by the phone service provider.|
|Additional data stored by Code.org if you create a Code Studio teacher account||Required?||How this data is used|
At your option and under your control, we would list your school in the Code.org map and database of schools that teach computer science courses.
Code.org may also use this information to reach out to your school or district to discuss broader education partnerships or participation in special events.
|School address||Optional||At your option and under your control, we would list your school (and relevant contact information, if you provide it) in the Code.org map and database of schools that teach computer science courses.|
|Student section data||Required||
You may create accounts for your students (and provide each student’s display name and optionally their age and gender), and organize these students into sections or groups. You may assign each section a display name, and a course assignment. The section grouping data is used to simplify your view of students across multiple sections.
Teachers are encouraged to share a document with students and parents informing them about the Code Studio course, including the privacy implications.
Students and teachers may update, correct, or delete Personal Information in their Code Studio profiles at any time via the account settings page (or the manage students page for teachers).
Under a student's control, they can dissociate or associate themselves with as many teachers as they want, (and those teachers get access to the student's course progress and display name but not their email address). Teachers who create User accounts on behalf of students can reset their “secret word” or “secret picture” (for young children who can’t read) for as long as the student leaves the teacher in control of the account.
If you decide to register for Code Studio through an Authentication Service (such as Facebook Connect or Google Accounts), you give Code.org the permission to store and use information already associated with your Authentication Service consistent with this Privacy Notice and the table above.
When you use certain other features of our Website, such as signing forms or petitions to help advocate for Code.org, 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, 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 emails we send include an “unsubscribe” link which will immediately unsubscribe you from all future email from Code.org.
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 you for your work (such as a mailing address to send a check, 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.
In certain situations, we may obtain information, including Personal Information, from third parties or sources other than the Website. For example, if you donate to Code.org via PayPal, we may obtain your name and mailing address to send a thank you note. If we combine or associate information from other sources with Personal Information that we collect through the Website, we will treat the combined information as Personal Information in accordance with this Privacy Notice. Your sharing of Personal Information with those third parties will also be subject to their privacy policies.
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 and 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 similar section 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.
Code.org may use a variety of third-party service providers, such as 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.
Code.org does not allow advertising on our Website, and we do not have the ability to collect your web search history across 3rd party Internet web sites or search engines. (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). However, certain third-party entities that we use to provide website functionality or social sharing may collect Non-Personal Information for the purposes of online behavioral advertising. Our website does not respond to “do not track” signals transmitted by web browsers, but 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 using these tools, you may need to opt out separately for each of your devices and for each Web browser on each device.
The Code.org Website does not offer private messaging among students, or between students and teachers. The only messaging that Users may engage in on the Website involves customer support requests.
The Code Studio platform does not provide Users a mechanism to upload photos. In particular, student and teacher profiles can NOT be customized with a photo.
Code.org does not directly collect or store payment instruments. Donations to Code.org or purchases of t-shirts 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).
The Code Studio learning platform is designed to be used by Users of all ages, including children under the age of 13 with the involvement of their school, teacher, parent or legal guardian. Certain features are disabled or inaccessible to accounts created by children under the age of 13, in order to provide greater protection to those Users.
When children under the age of 13 create accounts on Code Studio, Code.org does not store the email address provided by those Users in a retrievable format. Instead, we immediately create and store only a hashed version of the email address (which cannot be converted back into the original address), and use it only for the purposes of login and password recovery.
When children under the age of 13 attempt to sign the online petition supporting Code.org’s mission, the email addresses are discarded and are not collected or stored on our server.
If Code.org learns that it has inadvertently collected Personal Information from children under the age of 13 without prior parental consent, Code.org will take appropriate steps to delete this information. If you are a parent or legal guardian you can ask us to deactivate your child’s account, delete any hashed email address or inadvertently collected Personal Information, and request that we no longer allow your child to submit their information to Code.org. To make such a request, please contact us at http://code.org/contact. Before processing your request, we may verify your identity and your relationship with the child.
As is common in education research, to measure how well our programs perform and how well students are learning from them, Code.org engages an experienced independent 3rd party, Outlier Research & Evaluation (“Evaluator”) to do a thorough evaluation of our work in select partner school districts. Outlier is part of the University of Chicago’s Center for Elementary Mathematics and Science Education. For information about Outlier’s experience and track record evaluating education initiatives and student data, visit http://cemse.uchicago.edu/research-and-evaluation/.
To participate in the evaluation, these school districts are asked 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 anonymized (removing student Personal Information such as name and address). The data enables the Evaluator 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 Evaluator 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 Evaluator anonymized data, which will then be aggregated by the Evaluator across thousands of students from hundreds of schools to publish an independent study. Besides the anonymity of this student academic data, our contracts with school districts also specify very strict limits on who may access this data. You may read the template contractual language governing student-data in our district agreements at http://code.org/educate/template-district-agreement.
Code.org’s employees, agents and contractors must have a legitimate business reason (related directly to furthering our education-focused mission) to access Personal Information you provide to Code.org, for example to assist in product support. Code.org will require our employees, agents, and contractors to comply with this Privacy Notice, and to treat any Personal Information of Code.org Users as confidential information.
We do not rent or sell Personal Information that we collect from Users, or exploit it for financial gain in any other way. Code.org will never share Personal Information with other third-party organizations without your consent or except as part of a specific program or feature for which you will have the ability and choice to opt-in.
In particular, we do not share any Personal Information you provide with our donors or sponsors (other than the "Public Reporting" of anonymized reports as described below).
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).
Part of our educational program is to offer professional development 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 leading the workshop.
Some of our Users choose to post their code-creations with social networks. This functionality is entirely optional. When we 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.
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.
Code.org promotes a weekly Student of the Week and a monthly Teacher of the Month, along with prizes. 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.
We may publish anonymized 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 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.
In certain occasions, Code.org may work with third parties (such as 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.
Code.org may also disclose User Personal Information 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.
Code.org may disclose Personal Information that we believe, in good faith, is appropriate or necessary to take precautions against liability; to protect Code.org from fraudulent, abusive, or unlawful uses; to investigate and defend ourselves against any third-party claims or allegations; to assist government enforcement agencies; to protect the security or integrity of the Website; or to protect the rights, property, or personal safety of Code.org, our Users, or others.
In the event that Code.org is acquired by, combined or merged with another entity, we may transfer or assign the Personal Information that we have collected from Users as part of such merger, acquisition, sale, or other change of control. Our promise to you is that any Personal Information we have collected from Users would be safeguarded under the same level of safety and privacy as afforded by this Privacy Notice.
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. Because some schools block SSL-secures web sites, Code.org allows access with or without SSL protection, at the direction of those schools. If you would like an SSL encrypted connection in or to encrypt the data that you input while using the Website, use the HTTPS protocol by visiting https://code.org/.
Code.org uses certain physical, managerial, and technical safeguards designed to preserve the integrity and security of your Personal Information and other information we maintain in connection with the Website. 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 makes commercially reasonable efforts to ensure the security of our systems. However, please note that this is not a guarantee that such Personal 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, 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 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.
If you choose to visit Code.org, your visit and any dispute over privacy is subject to this Privacy Notice and our Terms of Service Agreement, including limitations on damages, arbitration of disputes, application of the law of the State of Washington and venue for all disputes in Seattle, Washington.
We do not disclose any personal information to third parties for marketing purposes. For additional information about our privacy practices, or to review and request to have deleted any personal information you have shared with us, please send a request to http://code.org/contact.
Please contact Code.org with any questions or comments about this Privacy Notice, your Personal Information, our third-party disclosure practices, or your consent choices by writing us at http://code.org/contact or at 1301 Fifth Avenue, Suite 1225, Seattle, WA 98101.