code.org - Githubissues

diff --git a/code.org/privacy.md b/code.org/privacy.md index 7d9fef5..f8da02d 100644 --- a/code.org/privacy.md +++ b/code.org/privacy.md @@ -2,7 +2,7 @@ Sign in Privacy Policy -Date of Last Revision: July 19, 2021 +Date of Last Revision: November 11, 2021 You can review the previous Privacy Policy here. @@ -104,12 +104,14 @@ Students may “remix” (copy and then change or improve upon) projects made by Students age 13 or over can also, at their discretion, post their projects to their social media accounts. -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. Some text provided by Students in these tools is automatically analyzed and moderated to help prevent sharing of personal data like email addresses and phone numbers. +In our elementary school courses, Students create stories, games, or art using tools, such as Play Lab and Sprite Lab, which are generally limited to using artwork and sounds provided by Code.org or uploaded by their teacher. Where we do allow custom uploads by Students in these tools (e.g., uploading an image for a Student-created storyboard), Students are advised never to upload any media containing Personal Information and we implement controls that block Student sharing of projects to the Code.org public gallery that contain custom uploads. Students can write dialogues for these projects. Some text provided by Students in these tools is automatically analyzed and moderated to help prevent sharing of personal data like email addresses and phone numbers. -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) Collected if a Student chooses to upload custom files. Creating apps with these programming tools is part of our courses for grades 6+. Only Students age 13 and older, or Students under 13 who are working in a classroom whose Teacher has added the Student to a class section, can choose to upload custom images, sounds, and videos to the Code.org platform to use within apps or games that they create. Students under 13 are advised never to upload any media containing Personal Information. +Our middle school and high school courses teach Students to make more complex apps and games, such as App Lab, Game Lab, and Web Lab. These tools allow the Students to upload custom photos, sounds and/or videos. (See below) +Student-uploaded images, sounds, or videos Collected if a Student chooses to upload custom files. Only Students age 13 and older, or Students under 13 who are working in a classroom whose Teacher has added the Student to a class section, can choose to upload custom images, sounds, and videos to the Code.org platform to use within apps or games that they create in programing tools as part of our courses for grades 6+ (App Lab, Game Lab, and Web Lab). Students under 13 are advised never to upload any media containing Personal Information and we do not allow Students under the age of 13 to share projects created using these tools to the Code.org public gallery. -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. +Similarly, where custom uploads are allowed for programming tools intended for younger students (e.g, Play Lab and Sprite Lab), Students are advised never to upload any media containing Personal Information and we implement controls that block Student sharing of projects that contain custom uploads. + +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 described. Data collected by Student-created apps Collected if users of a code project created by the Student choose to enter data into the app. 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. @@ -199,7 +201,7 @@ Custom Content Student and Teacher profiles cannot be customized with a photo. -As part of “App Lab,” “Game Lab,” or “Web Lab” (in-browser programming tools available on Code.org), Students 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, but are not used by Code.org for any purpose other than within the applications created by Users. +As part of certain in-browser programming tools available on Code.org (such as “App Lab,” Game Lab,” “Web Lab,” and “Sprite Lab”), Students 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, but are not used by Code.org for any purpose other than within the applications created by Users. When we allow uploads of images, sounds or videos by Students under age 13, we implement controls that block Student sharing of such projects as described in the table above. Internet Simulator and Other Messages @@ -347,8 +349,8 @@ We do not support online messaging between Students (except for the Internet Sim We encourage the use of screen names that are first name or first name and last initial only. We only display a Student’s first initial when we display projects on our Services. We only provide a mechanism for Students age 13 or over to post projects to their social media accounts. -We automatically monitor some text entered in projects for elementary school courses, such as PlayLab, to help prevent sharing of personal data such as email address and phone number. -We only allow uploads of custom content, images, sounds, and videos by Students age 13 or older unless under the supervision of a Teacher’s section. +We automatically monitor some text entered in projects for elementary school courses, such as Play Lab and Sprite Lab, to help prevent sharing of personal data such as email address and phone number. +When we allow uploads of custom images, sounds, and videos by Students under age 13, we implement controls that block Student sharing of such projects. 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 and delete any hashed email address or inadvertently collected Personal Information or Persistent Identifiers. To make such a request, please email us at support@code.org or enter a request at https://code.org/contact. Before processing your request, we may verify your identity and your relationship with the Student.

diff --git a/code.org/tos.md b/code.org/tos.md index d6828276..c66661c8 100644 --- a/code.org/tos.md +++ b/code.org/tos.md @@ -1,7 +1,7 @@ Sign in Terms of Service -Date of Last Revision: March 9, 2021 +Date of Last Revision: April 13, 2022 Code.org is a 501(c)(3) nonprofit 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://www.k12cs.org, https://codeprojects.org, https://hourofcode.com, https://curriculum.code.org, https://advocacy.code.org, other websites, information, text, curricula, videos, graphics, photos, APIs, email notifications and other materials and related products and services (the “Services”). @@ -98,7 +98,7 @@ Code.org’s library of videos may be redistributed freely on the express condit The celebrities and video “cast“ members appearing in Code.org tutorials and 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 © 2016 Cartoon Network. +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 © 2022 Electronic Arts Inc. Plants vs. Zombies and PopCap are trademarks of Electronic Arts Inc. Angry Birds are © 2022 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 © 2022 Disney. Star Wars is a trademark and © 2022 Lucasfilm and Disney. Minecraft is a trademark and © 2022 Microsoft. The Amazing World of Gumball is a trademark and © 2022 Cartoon Network. DreamWorks The Bad Guys © 2022 DreamWorks Animation LLC. The software powering Code.org tutorials is governed by an open source license which is posted as part of the source code repository.

diff --git a/code.org/privacy.md b/code.org/privacy.md index f8da02db..9e3fd413 100644 --- a/code.org/privacy.md +++ b/code.org/privacy.md @@ -2,7 +2,7 @@ Sign in Privacy Policy -Date of Last Revision: November 11, 2021 +Date of Last Revision: October 3, 2022 You can review the previous Privacy Policy here. @@ -187,15 +187,9 @@ Technical Information To provide a personalized learning and high-quality experience for our Users, we may use various technologies that automatically record certain technical information from the User’s browser or device, including browser language settings, standard log files, web beacons, or pixel tags. This technical information may include Internet Protocol (IP) address, browser type, internet service provider (ISP), referring or exit pages, click stream data, operating system, and the dates and times the User visited the Services. This information assists us in providing the Services and understanding how our Users are using the Services. -To assess information about use of our Services, we use various technological tools. For example, whether or not a User is a registered member, we may send one or more cookies to the User’s browser when they visit our Services. We may use: +To assess information about use of our Services, we use various technological tools. For example, whether or not a User is a registered member, we may send one or more cookies to the User’s browser when they visit our Services. For more information, see the Code.org Cookie Notice. -Essential cookies: these ensure the Services work properly for Users. As one example, when a User authenticates and logs in, thanks to essential cookies they aren’t prompted to re-enter their password on every single page they visit during their browsing session. -Functional cookies: these help us personalize the Services and make it faster or more user-friendly. For example, thanks to functional cookies the Services may remember the device’s language setting (e.g., English, Spanish, etc). -Analytical cookies: these are used to collect technical information to help us optimize the Services and our courses. For example, thanks to analytical cookies, we can identify which lessons are most popular among students. - -Code.org may use both session cookies and persistent cookies. A session cookie disappears automatically after the User closes their browser. A persistent cookie remains after the browser is closed and may be used by the browser on subsequent visits to the Services. 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 capabilities and features on the Services. - -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 recipient has displayed that page or opened that email. We may allow third-party service providers to place and read their own cookies, pixel tags, and similar technologies to collect information through the Services to perform the service we’ve requested. This technical information is collected directly and automatically by these third parties. +We may also use pixel tags (also known as a “clear GIF” or “web beacon”), which are tiny images – typically just one pixel – that can be placed on a Web page or in an email to tell us when the recipient has displayed that page or opened that email. We may allow third-party service providers to place and read their own cookies, pixel tags, and similar technologies to collect information through the Services to perform the service we’ve requested. This technical information is collected directly and automatically by these third parties. Custom Content

diff --git a/code.org/tos.md b/code.org/tos.md index c66661c8..78b09677 100644 --- a/code.org/tos.md +++ b/code.org/tos.md @@ -1,7 +1,7 @@ Sign in Terms of Service -Date of Last Revision: April 13, 2022 +Date of Last Revision: December 14, 2022 Code.org is a 501(c)(3) nonprofit 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://www.k12cs.org, https://codeprojects.org, https://hourofcode.com, https://curriculum.code.org, https://advocacy.code.org, other websites, information, text, curricula, videos, graphics, photos, APIs, email notifications and other materials and related products and services (the “Services”). @@ -82,9 +82,11 @@ You are solely responsible for User Content you post to the Services and the con 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. +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, in our sole and final discretion. 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. +Our Services are intended for educational purposes. Although our Services (e.g., App Lab, Game Lab) enable users to create apps and projects with a wide range of functions to learn and explore computer science - including potential multi-user functions - you may not create chat apps or similar multi-user apps to be hosted on the Code.org platform outside of a legitimate classroom context. You also may not create apps that have a commercial purpose or aspect to be hosted on the Code.org platform. We reserve the right at all times (but will not have the obligation) to remove such apps and to suspend or terminate users who violate these terms in this or any other manner. + +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; (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; (vi) create chat apps or similar multi-user apps outside of a legitimate classroom context; (vii) create apps with any commercial purpose or aspect; or (viii) upload or create offensive, bullying, obscene, threatening, or other harmful Content (as determined in our sole and final discretion). 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. @@ -92,19 +94,31 @@ Code.org may, but is not obligated to, monitor or review any Services where Educ 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. -Your License to Use Code.org Videos, Tutorials, Data, and APIs +Your License to Use Code.org Software, Videos, Curriculum and Tutorial Materials, JSON API, and Conference Board Data + +The following table provides an overview of the licenses and restrictions governing Code.org software code, videos, curriculum and tutorial materials, and APIs, as well as data we publish from the Conference Board. More detailed descriptions are provided below. + +Code.org Materials Governing License and Restrictions +Code.org code-base on github Apache 2.0 license (code-base only; excludes videos, curriculum and tutorial materials, APIs, and other data described below) +Code.org videos Creative Commons BY-NC-ND 4.0 license (subject to express conditions below) +Code.org curriculum and tutorial materials (other than proprietary videos and third-party artwork) Creative Commons BY-NC-SA 4.0 licence (subject to express conditions below) +Celebrity and other video and tutorial “cast” members’ likenesses and names Not Applicable. Can be used only as incorporated into Code.org materials +Artwork in Code.org tutorials (including third-party artwork or any other IP licensed to Code.org) Not Applicable. Can be used only as incorporated into Code.org materials +JSON API Creative Commons BY-NC-SA 4.0 licence (subject to express conditions below) +Conference Board Data The Conference Board Terms of Use (at www.conference-board.org) +Code.org trademarks Not Applicable. Require express written permission from Code.org -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 code powering Code.org’s websites and tutorials is governed by an open source Apache License which is posted as part of the source code repository in github. + +Code.org’s library of videos is governed by and licensed to you for use under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 Unported License. More information about this license can be found at https://creativecommons.org/licenses/by-nc-nd/4.0/. Code.org 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 tutorials and 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 © 2022 Electronic Arts Inc. Plants vs. Zombies and PopCap are trademarks of Electronic Arts Inc. Angry Birds are © 2022 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 © 2022 Disney. Star Wars is a trademark and © 2022 Lucasfilm and Disney. Minecraft is a trademark and © 2022 Microsoft. The Amazing World of Gumball is a trademark and © 2022 Cartoon Network. DreamWorks The Bad Guys © 2022 DreamWorks Animation LLC. -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. +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. Except as set forth above, you may not otherwise use Code.org materials for commercial purposes. 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. +The Code.org JSON API and database of schools is also licensed via the 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/, which means you are free to use the data to make derivative works, as long as you give Code.org attribution. Any data provided by The Conference Board is provided “as is” with no warranty whatsoever, and is protected by United States and International Copyright laws. The data displayed are provided for informational purposes only and may only be accessed, reviewed, published, and/or used in accordance with, and the permission of, The Conference Board consistent with the Terms of Use displayed at www.conference-board.org. Such data may not be extracted for use in a database, used to create a derivative work, or otherwise misused by any means without express written permission from The Conference Board, except that you may make limited noncommercial use as consistent with Fair Use under Section 107 of the Copyright Act of 1976. The Conference Board® and The Conference Board Help Wanted OnLine® are registered trademarks of The Conference Board. The Conference Board reserves all rights in and to its trademarks. Further information regarding The Conference Board Help Wanted OnLine® can be found here.

diff --git a/code.org/privacy.md b/code.org/privacy.md index 9e3fd413..f586d0a6 100644 --- a/code.org/privacy.md +++ b/code.org/privacy.md @@ -2,7 +2,7 @@ Sign in Privacy Policy -Date of Last Revision: October 3, 2022 +Date of Last Revision: December 15, 2022 You can review the previous Privacy Policy here. @@ -130,6 +130,7 @@ Teachers can choose at account creation whether to receive non-transactional ema District and school name and/or school type (private, public, charter, homeschool, after school, organization, or other) and/or school address Optionally provided by the Teacher at account creation or after creating an account. At the Teacher's discretion and under their control, we will list their school in the Code.org map and database of schools that teach computer science courses. Code.org or our professional development 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. +Verified Teacher Identification Information Optionally provided by the Teacher when seeking “verified teacher” status if the Teacher’s status cannot be demonstrated through other proof - such as verification of the teacher’s position on a school website. At the Teacher's discretion, and under their control, they may provide a copy of an identification (such as a school-issued ID or a state-issued ID) to our support desk as part of demonstrating their teacher status. We recommend redacting data beyond name, photo, and issuing authority. All such images are deleted after the verification is complete. Student section data Collected if a Teacher decides to create a section on Code.org to manage their Students. The Teacher may create accounts for their students (and provide each Student’s display name and, optionally, their age and gender) or direct students to create accounts themselves, 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 Code.org document with Students and parents informing them about enrollment in a Code.org section, including the privacy implications. @@ -187,7 +188,7 @@ Technical Information To provide a personalized learning and high-quality experience for our Users, we may use various technologies that automatically record certain technical information from the User’s browser or device, including browser language settings, standard log files, web beacons, or pixel tags. This technical information may include Internet Protocol (IP) address, browser type, internet service provider (ISP), referring or exit pages, click stream data, operating system, and the dates and times the User visited the Services. This information assists us in providing the Services and understanding how our Users are using the Services. -To assess information about use of our Services, we use various technological tools. For example, whether or not a User is a registered member, we may send one or more cookies to the User’s browser when they visit our Services. For more information, see the Code.org Cookie Notice. +To assess information about use of our Services, we use various technological tools. For example, whether or not a User is a registered member, we may send one or more cookies to the User’s browser when they visit our Services. For more information, see the Code.org Cookie Notice or the Hourofcode.com Cookie Notice. We may also use pixel tags (also known as a “clear GIF” or “web beacon”), which are tiny images – typically just one pixel – that can be placed on a Web page or in an email to tell us when the recipient has displayed that page or opened that email. We may allow third-party service providers to place and read their own cookies, pixel tags, and similar technologies to collect information through the Services to perform the service we’ve requested. This technical information is collected directly and automatically by these third parties.

e1e96af00998e36f018d34650f60cdcc7b37a54c: https://code.org/privacy @ 2024-05-12

difference captured:

diff --git a/code.org/privacy.md b/code.org/privacy.md
index f586d0a6..ede55393 100644
--- a/code.org/privacy.md
+++ b/code.org/privacy.md
@@ -1,8 +1,6 @@
-Sign in
-
 Privacy Policy

-Date of Last Revision: December 15, 2022
+Date of Last Revision: April 4, 2024

 You can review the previous Privacy Policy here.

@@ -43,9 +41,9 @@ You can use the links below to quickly find information in our Privacy Policy
 How We Collect and Use Information
 How We Share or Transfer Information
 How We Protect Information
-Your Choices - How to Access, Update, or Delete Your Information
+Your Choices - How to Access, Correct, Update, or Delete Your Information
 School Users and Student Records
-Protecting Children's Privacy
+Children's Privacy Notice
 Links to Other Sites and Services
 We Do Not Allow Advertising on Our Services
 International Users
@@ -57,7 +55,9 @@ How We Collect and Use Information

 The sections below describe the ways Code.org collects and uses personal data, which refers to any information that Code.org can use to reasonably identify a User as an individual (directly or indirectly), as well as information that is or can be reasonably linked (directly or indirectly) to a User or a User’s device. This includes things like name, display name, email address, school name and address, telephone number, etc., provided by Users (“Personal Information”), persistent cookies or IP addresses automatically collected (“Persistent Identifiers”), as well as some of the non-Personal Information and technical information (described below) we collect that is associated with a User.

-We generally collect personal data in three ways: (1) information a User voluntarily provides to us by using the Services, (2) information we automatically collect as a User uses the Services, and (3) information from third-parties. The types and amounts of personal data collected vary depending on whether the User is a Student, Teacher, parent or other visitor, and on how they use the Services.
+We generally collect personal data in three ways: (1) information a User voluntarily provides to us by using the Services, (2) information we automatically collect as a User uses the Services, and (3) information from third parties. The types and amounts of personal data collected vary depending on whether the User is a Student, Teacher, parent or other visitor, and on how they use the Services, but can be generally categorized as (a) account registration data (such as username, password, email address), (b) demographic data (such as age, gender, race), (c) Technical data (such as browser or device, IP address, login times), (d) User uploaded data (such as images and sounds), (e) User response or feedback data (such as survey responses and notes to and from Teachers); (f) platform usage data (such as progress data, projects created), and (g) contact data for non-curriculum processes (such as email addresses for educators, parents, and others who wish to receive newsletters and other updates).
+
+We generally use personal data to (1) provide our Services, (2) personalize User experiences, (3) communicate with Users or others (such as donors or educators), (4) provide or facilitate professional development for CS teachers, (5) understand, improve, develop, and protect our Services, and (6) for legal, compliance, and safety reasons.

 Our goal is to minimize the personal data we collect. We do not require Users to create a Code.org account or otherwise provide Personal Information in order to participate in the Hour of Code tutorials or to try our courses. However, we cannot save a Student’s learning progress or a Teacher’s class records unless a User creates a Code.org account.

@@ -66,24 +66,23 @@ Code.org Student and Teacher Accounts
 The following table describes the data that Code.org collects and stores if a User creates a Code.org Student or Teacher account for use with Code.org courses.

 Data stored by Code.org if a User creates a Code.org Student account   How and when is the data collected? How this data is used
-Display Name (e.g., “Cool Coder” or “John”) and username (e.g., “coolcoder7”)  Required by User (or their Teacher) on account creation 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.
+Display Name (e.g., “Cool Coder” or “John”) and username (e.g., “coolcoder7”)  Required by User (or their Teacher) on account creation Display name is used to provide Students a welcoming login and to identify the Student in the Teacher’s roster view of student progress. Although not required, this may include - at the teacher’s or student’s option - student first and last name or initials.

 Usernames are generated based on the initial display name and can be used along with a password to sign into an account.
 Account passwords  Required by User (or their Teacher) on account creation.    Passwords are established by the User and can be updated through the User’s account settings or by a Teacher that manages a section in which the Student is enrolled. They are used for User authentication at sign-in.
 Secret words/pictures  System generated by Teacher when adding Student to section (if choosing not to use Student accounts with passwords).    Secret words or pictures are system generated, but can be reset by the Teacher.  They are used for User authentication at sign-in.
 Age (Not birthdate)    Required by User (or their Teacher) on account creation or first sign in before using the site. This data is used to understand the developmental stage of Students in order to offer an age-appropriate experience for each Student. We also 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)  Email address is required (but not stored) on account creation if a Student creates an account or a Teacher creates the account via a third-party rostering provider. 
+State (in US Only) Required by User on account creation or first sign in.  This data is used to identify the state in which a Student resides in order to apply state-specific laws (where applicable) and to allow aggregate analyses.
+One-way hash of student email address  Email address is required (but not stored) on account creation if a Student creates an account or if a Teacher creates the student account via a third-party authentication service or Learning Management Services (LMS) provider, or the Student later adds a personal login to a Teacher-created account. 

-Email address is not required if an account is created by a Teacher using a picture or secret word login for the section, though it can be optionally added by the Student later.  A Student's email address is only used for the purposes of login (along with the User’s password). 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 from their account. See Student Email Addresses below for more details.
-Parent or guardian email address   Can be optionally provided by a parent to receive updates or create a login for their child at home.    Parents or guardians can choose to link their email address to their Student’s account to receive updates from Code.org. (A student can also add the parent or guardian email address.)
+Email address is not required if an account is created by a Teacher using a picture or secret word login for the section, though it can be optionally added by the Student later.  Where a Student creates a personal login (i.e., the student creates a Code.org account using an email address and selecting their own password or through a third-party authentication service - or adds a personal login to an existing account created by the Teacher on behalf of the Student through rostering or using picture or secret word logins), the Student's email address is only used for the purposes of login (along with the User’s password). 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 from their account. See Student Email Addresses below for more details.
+Parent or guardian email address   Can be optionally provided by a parent to receive updates or create a login for their child at home. In some jurisdictions, we may require a Student under 13 to provide a parent or guardian email address for the purpose of obtaining consent to the creation of the Code.org account by the student.    Parents or guardians can choose to link their email address to their Student’s account to receive updates from Code.org. (A student can also add the parent or guardian email address.)

-A Student may want to create a personal login to access their account independently of their Teacher or school, especially if the Teacher decides to delete the classroom section that the Student belonged to or the Student signs in with a school-sponsored account like Google, Microsoft, Clever, or PowerSchool.
-
-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 or guardian email address for password recovery. The Student will then be able to sign in at home with a username and password.
+In some jurisdictions, we may require a parent or guardian email address for the purpose of consenting to the creation of a Student Code.org account for a Student under the age of 13. In those instances, the email address is used solely for that purpose and is linked to the Student account for purposes of allowing the parent to stay updated on their Child’s progress and projects - and the Parent email address can also be used for password recovery and to request support.
 Account Identifiers    System generated (separate identifiers may be provided by authentication services). This is NOT a student number assigned by a school.  These identifiers are used to maintain and operationalize accounts.
 Login time, IP address, and other technical data   Automatically collected as the Services are used.   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 Services updates with minimal service disruption. See Technical Information below for more details.
-Gender Optionally provided by the Student or their Teacher.    This information is only used in aggregate to measure the percentage of students that are “male/female/nonbinary/preferred term not listed” and measure how such Students respond to different computer science challenges, or track our aggregate progress towards reducing the gender gap in computer science.
-Race   Optionally provided by the Student (only requested from Students if their IP address is in the US). 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.
+Gender Optionally provided by the Student or their Teacher.    This information is only used in aggregate to measure gender distribution and how Students respond to different computer science challenges, or track our aggregate progress towards reducing the gender gap in computer science.
+Race   Optionally provided by the Student (only requested from Students 13 and over and only if their IP address is in the US).    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 racial and ethnic groups and their aggregate response to computer science challenges, and in order to track our aggregate progress toward improving diversity in computer science.
 Progress in the course
@@ -98,20 +97,21 @@ Student projects - apps, animations, stories, or code-art   Collected as a Student

 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 projects (e.g., in App Lab) to the Code.org public gallery when these projects allow for Student-uploaded content.
+Student projects and code creations each have a custom URL that Students can use to share with others. Where projects are selected for posting in the featured project gallery with a teacher’s or student’s consent, projects are displayed with only the first letter of the Student’s display name, along with their age, to protect Student privacy.

 Students may “remix” (copy and then change or improve upon) projects made by themselves or by other Users.

 Students age 13 or over can also, at their discretion, post their projects to their social media accounts.

-In our elementary school courses, Students create stories, games, or art using tools, such as Play Lab and Sprite Lab, which are generally limited to using artwork and sounds provided by Code.org or uploaded by their teacher. Where we do allow custom uploads by Students in these tools (e.g., uploading an image for a Student-created storyboard), Students are advised never to upload any media containing Personal Information and we implement controls that block Student sharing of projects to the Code.org public gallery that contain custom uploads. Students can write dialogues for these projects. Some text provided by Students in these tools is automatically analyzed and moderated to help prevent sharing of personal data like email addresses and phone numbers.
+In our elementary school courses, Students create stories, games, or art using tools, such as Play Lab and Sprite Lab, which are generally limited to using artwork and sounds provided by Code.org or uploaded by their teacher. Where we do allow custom uploads by Students in these tools (e.g., uploading an image for a Student-created storyboard), Students are advised never to upload any media containing Personal Information. Students can write dialogues for these projects. Some text provided by Students in these tools is automatically analyzed and moderated to help prevent sharing of personal data like email addresses and phone numbers.

 Our middle school and high school courses teach Students to make more complex apps and games, such as App Lab, Game Lab, and Web Lab. These tools allow the Students to upload custom photos, sounds and/or videos. (See below)
-Student-uploaded images, sounds, or videos Collected if a Student chooses to upload custom files.  Only Students age 13 and older, or Students under 13 who are working in a classroom whose Teacher has added the Student to a class section, can choose to upload custom images, sounds, and videos to the Code.org platform to use within apps or games that they create in programing tools as part of our courses for grades 6+ (App Lab, Game Lab, and Web Lab). Students under 13 are advised never to upload any media containing Personal Information and we do not allow Students under the age of 13 to share projects created using these tools to the Code.org public gallery.
+Student-uploaded images, sounds, or videos Collected if a Student chooses to upload custom files.  Only Students age 13 and older, or Students under 13 who are working in a classroom whose Teacher has added the Student to a class section, can choose to upload custom images, sounds, and videos to the Code.org platform to use within apps or games that they create in programing tools as part of our courses for grades 6+ (App Lab, Game Lab, and Web Lab). Students under 13 are advised never to upload any media containing Personal Information.

-Similarly, where custom uploads are allowed for programming tools intended for younger students (e.g, Play Lab and Sprite Lab), Students are advised never to upload any media containing Personal Information and we implement controls that block Student sharing of projects that contain custom uploads.
+Similarly, where custom uploads are allowed for programming tools intended for younger students (e.g, Play Lab and Sprite Lab), Students are advised never to upload any media containing Personal Information.

 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 described.
+Student Free Text Entries, which could include personal data   Collected if users enter data in free text fields, such as a response to a survey question or an AI tutor query.    In some cases, students may be able to enter free text data in various fields, which could include personal data despite warnings/instructions not to include such data. The free text fields may be processed and stored as part of the Code.org functionality, including in cases such as a query of an AI tutor feature.
 Data collected by Student-created apps Collected if users of a code project created by the Student choose to enter data into the app.  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.
@@ -127,11 +127,13 @@ Additional* data stored by Code.org if a User creates a Code.org Teacher account
 Email address  Email address is required at account creation (or when switching from a Student account to a Teacher account).  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 opportunities, etc.

 Teachers can choose at account creation whether to receive non-transactional emails (e,g., updates to our courses, local opportunities, or other computer science news). All non-transactional emails sent by Code.org contain an unsubscribe link and do not require typing a password to unsubscribe.
+First and Last Name    Collected at account creation.  Teacher names are used to customize communications and streamline processes such as enrolling in professional learning.
 District and school name and/or school type (private, public, charter, homeschool, after school, organization, or other) and/or school address Optionally provided by the Teacher at account creation or after creating an account.    At the Teacher's discretion and under their control, we will list their school in the Code.org map and database of schools that teach computer science courses.

 Code.org or our professional development 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.
+Teacher’s primary role (e.g., classroom teacher, librarian, etc.), grades taught, and subjects of interest Collected at account creation.  This data is used to better understand how teachers in different roles use Code.org and provide potential recommendations and tips based on the criteria.
 Verified Teacher Identification Information    Optionally provided by the Teacher when seeking “verified teacher” status if the Teacher’s status cannot be demonstrated through other proof - such as verification of the teacher’s position on a school website.  At the Teacher's discretion, and under their control, they may provide a copy of an identification (such as a school-issued ID or a state-issued ID) to our support desk as part of demonstrating their teacher status. We recommend redacting data beyond name, photo, and issuing authority. All such images are deleted after the verification is complete.
-Student section data   Collected if a Teacher decides to create a section on Code.org to manage their Students.    The Teacher may create accounts for their students (and provide each Student’s display name and, optionally, their age and gender) or direct students to create accounts themselves, 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.
+Student section data   Collected if a Teacher decides to create a section on Code.org to manage their Students.    The Teacher may create accounts for their students (and provide each Student’s display name which the Teacher can manage using full names or initials, and, optionally, their age and gender) or direct students to create accounts themselves, 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 Code.org document with Students and parents informing them about enrollment in a Code.org section, including the privacy implications.
 Survey and demographic data    Collected if a Teacher chooses to optionally fill out a survey. For the purposes of evaluating our own work and improving our education results, Code.org regularly sends surveys to Teachers.
@@ -154,15 +156,15 @@ Comment feedback provided to students Collected if a Teacher decides to give wri

 * 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.

-Teachers can create accounts on behalf of Students. When registering an account for a Student who is under the age of 13, the Teacher represents and warrants that they or the educational organization they work for has proper permission to register the Student for a Code.org account, and that they or the educational organization has obtained the necessary parental consent for collection of the Student’s Personal Information for the use and benefit of the school and for no other commercial purpose. In addition, the Teacher agrees to be bound by the Code.org Terms of Service and this Privacy Policy on behalf of the educational organization they work for, and that they are authorized to do so. See Protecting Children’s Privacy below for more information.
+Teachers can create accounts on behalf of Students. When registering an account for a Student who is under the age of 13, the Teacher represents and warrants that they or the educational organization they work for has proper permission to register the Student for a Code.org account, and that they or the educational organization has obtained the necessary parental consent for collection of the Student’s Personal Information for the use and benefit of the school and for no other commercial purpose. In addition, the Teacher agrees to be bound by the Code.org Terms of Service and this Privacy Policy on behalf of the educational organization they work for, and that they are authorized to do so. See Children’s Privacy Notice below for more information.

-Third Party Authentication Services
+Third-Party Authentication Services and Learning Management Services (LMS)

-If you register for a Code.org account through an authentication service (such as Google Accounts, Microsoft Accounts, Facebook Connect, Clever, or PowerSchool), you give Code.org permission to store and use information already associated with your authentication service consistent with this Privacy Policy and the table above. In these instances, Code.org only receives information from the authentication services - Code.org does not share information with such services.
+If you register for a Code.org account through an authentication service or identity provider (such as Google Accounts, Microsoft Accounts, or Facebook Connect) or through an LMS (such as Google Classroom, Clever, Canvas, or Schoology), we will store and use the information already associated with that service consistent with this Privacy Policy and the table above. In these instances, Code.org only receives information from these services - Code.org does not share information with such services. (Note: As Code.org develops further integration with LMS providers, limited information - such as Student scores on assignments and feedback already available to Teachers through their Code.org sections - may also be made available to Teachers through the LMS.)

-When using a third-party authentication service, Code.org may receive personal data (such as a Student's full name or gender) that is not required for use of the Services. For example, districts or schools that use Clever as an authentication service can permit Code.org to use existing Clever teacher and student account information to sign in to Code.org Services. Districts or schools may revoke Code.org’s access to this information in Clever at any time.
+When Code.org accounts are established using these third-party services, Code.org may receive personal data (such as a Student's full name or gender) that is not required for use of the Services. For example, districts or schools that use Clever can permit Code.org to use existing Clever teacher and student account information to sign in to Code.org Services. Districts or schools may revoke Code.org’s access to this information at any time.

-You may revoke Code.org’s access to your account on any authentication service at any time by disconnecting the respective authentication service from your account settings. You should check your privacy settings on each authentication service to understand and change the information sent to us through such service. Please review each authentication service’s terms of use and privacy policies carefully before connecting them to our Services.
+You (or your school) may revoke Code.org’s access to your account on any authentication service or LMS at any time by disconnecting the respective authentication service from your account settings. You should check your privacy settings on each service to understand and change the information sent to us through such service. Please review each service’s terms of use and privacy policies carefully before connecting them to our Services.

 Non-Curriculum Features and Other Services

@@ -178,7 +180,7 @@ If you use the Services to request that we send someone information about Code.o

 Location Information

-Code.org does not request or collect GPS or other precise location data. We may collect and store non-precise location information (e.g., the approximate geographic region of a computer or mobile device, as determined from the IP address) to help provide educational experiences or email updates that are tailored for that region.
+Code.org does not request or collect GPS or other precise location data. We may collect and store non-precise location information (e.g., the approximate geographic region of a computer or mobile device, as determined from the IP address, or state as entered by the User) to help provide educational experiences or email updates that are tailored for that region.

 Information from Other Sources

@@ -188,7 +190,7 @@ Technical Information

 To provide a personalized learning and high-quality experience for our Users, we may use various technologies that automatically record certain technical information from the User’s browser or device, including browser language settings, standard log files, web beacons, or pixel tags. This technical information may include Internet Protocol (IP) address, browser type, internet service provider (ISP), referring or exit pages, click stream data, operating system, and the dates and times the User visited the Services. This information assists us in providing the Services and understanding how our Users are using the Services.

-To assess information about use of our Services, we use various technological tools. For example, whether or not a User is a registered member, we may send one or more cookies to the User’s browser when they visit our Services. For more information, see the Code.org Cookie Notice or the Hourofcode.com Cookie Notice.
+To assess information about use of our Services, we use various technological tools. For example, whether or not a User has a Code.org account, we may send one or more cookies to the User’s browser when they visit our Services. For more information, see the Code.org Cookie Notice or the Hourofcode.com Cookie Notice.

 We may also use pixel tags (also known as a “clear GIF” or “web beacon”), which are tiny images – typically just one pixel – that can be placed on a Web page or in an email to tell us when the recipient has displayed that page or opened that email. We may allow third-party service providers to place and read their own cookies, pixel tags, and similar technologies to collect information through the Services to perform the service we’ve requested. This technical information is collected directly and automatically by these third parties.

@@ -202,15 +204,15 @@ Internet Simulator and Other Messages

 Code.org offers 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 select courses, such as the Code.org CS A AP course, Teachers may optionally enable peer review groups within their classroom sections to allow students to provide feedback on other students’ projects. The student feedback is visible only to the Teacher and to students within the group designated by the Teacher. The Teacher may disable the feature at any time and may also delete specific feedback.
+In select courses, such as the Code.org AP® CSA course, Teachers may optionally enable peer review groups within their classroom sections to allow students to provide feedback on other students’ projects. The student feedback is visible only to the Teacher and to students within the group designated by the Teacher. The Teacher may disable the feature at any time and may also delete specific feedback.

 In addition, Teachers may provide written feedback to their Students on coursework. Users may also send messages to Code.org for customer-support requests.

-Other than the above, the Services do not directly provide any other form of messaging among Users (although Users may use Code.org tools to create apps that support messaging among individuals).
+Other than the above, the Services do not directly provide any other form of messaging among Users (although Users could use Code.org tools to create apps that support messaging among individuals).

 Student Email Addresses

-When Students use an 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 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 address, which is used to send them a password reset link after we verify the email address through the same one-way hashing algorithm. We then delete the clear text email address. We will, however, store and use email addresses provided by Students when they choose to participate in Non-Curriculum Features and Other Services to the limited extent described above.
+Code.org does not store the email address provided by Users, authentication services, or LMS providers in a retrievable format. Instead, we 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 login, account management, and password recovery. An exception exists if a Student forgets their password and asks to reset it. At that point, the Student is prompted to enter their email address, which we must receive and use to send them a password reset link after we verify the email address through the same one-way hashing algorithm. We then delete the clear text email address. We will, however, store and use email addresses provided by Students when they choose to participate in Non-Curriculum Features and Other Services to the limited extent described above.

 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 is 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.

@@ -218,15 +220,19 @@ No Commercial Use of Student Personal Information

 Some laws, such as California’s Student Online Personal Information Protection Act (SOPIPA) and similar state laws, prohibit the gathering of the Personal Information of K-12 students for targeted advertising purposes. Code.org abides by such laws and shall not use, disclose, or compile Personal Information of Students on the Services for the purpose of marketing or advertising commercial products or services. We do not disclose Personal Information or other personal data of Students to third parties for marketing purposes.

+Service Improvement and Internal Operations
+
+We may use data (including personal data) we obtain or generate from the operation of our Services to (1) conduct internal research to improve, repair, or develop products, services, or technology; (2) identify and repair technical errors; (3) prevent, detect, protect against and respond to security threats or incidents; and (4) perform internal operations.
+
 How We Share or Transfer Information

 We do not rent or sell personal data 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 data 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. In particular, we do not share any personal data you provide with our donors or sponsors (only de-identified reports as described below) without your explicit consent.

-The sections below explain circumstances in which we may share personal data with third-parties. We may also share de-identified or aggregate data that does not reasonably identify any individual or User.
+The sections below explain circumstances in which we may share personal data with third parties. We may also share de-identified or aggregate data that does not reasonably identify any individual or User.

 We may share personal data with third-party service providers

-Code.org may use a variety of third-party service providers to support our operations. For example, we may use third parties such as email service platforms to send email, analytics companies to understand our Services usage and performance, and social networking platforms to host our videos. Similarly, we may use third-party service providers to implement and host our Services and associated services and features, provide teacher forums, process donations, provide contract and workflow management services, assist with customer support, and provide other functions in support of our organization. When we give service providers access to data, including personal data, they are only allowed to use the data to provide services for which we have contracted and based on our direction. They are not allowed to use personal data for any other reason without the user’s consent or at the user’s direction. You can find a list of third-party service providers we use here.
+Code.org may use a variety of third-party service providers to support our operations. For example, we may use third parties such as email service platforms to send email, analytics companies to understand our Services usage and performance, Large Language Model providers to support AI-supported curricula, and social networking platforms to host our videos. Similarly, we may use third-party service providers to implement and host our Services and associated services and features, provide teacher forums, process donations, provide contract and workflow management services, assist with customer support, and provide other functions in support of our organization. When we give service providers access to data, including personal data, they are only allowed to use the data to provide services for which we have contracted and based on our direction. They are not allowed to use personal data for any other reason without the user’s consent or at the user’s direction. You can find a list of third-party service providers we use here.

 We may share Student personal data with the Teacher and Teacher personal data with the Student

@@ -234,7 +240,7 @@ If a Student belongs to a Teacher’s section, we will share Student account inf

 We may share personal data on classroom usage and Student achievement with the school or school district

-In order to support school and district needs to oversee Code.org usage in their classrooms, we may allow a Student’s school or school district to access reporting data on student progress and achievement, presented on a student-level, classroom-level, teacher-level, grade-level or school-level basis for Students enrolled in a Teacher’s section. The reports available to school and district administrators will be based on the same data that is displayed on the Student progress report that is also shared with the Student's Teacher(s). If Teachers choose to give Students feedback on coursework and projects through Code.org, we may also share this with school or district administrators upon request. We may also share personal data in Student Records with third-parties as directed by a school or school district. For more information about the data we may be sharing with a Student's school or school district, please click here.
+In order to support school and district needs to oversee Code.org usage in their classrooms, we may allow a Student’s school or school district to access reporting data on student progress and achievement, presented on a student-level, classroom-level, teacher-level, grade-level or school-level basis for Students enrolled in a Teacher’s section. The reports available to school and district administrators will be based on the same data that is displayed on the Student progress report that is also shared with the Student's Teacher(s). If Teachers choose to give Students feedback on coursework and projects through Code.org, we may also share this with school or district administrators upon request. We may also share personal data in Student Records with third parties as directed by a school or school district. For more information about the data we may be sharing with a Student's school or school district, please click here.

 We may share Teacher personal data with the Teacher's training facilitators, our Local Partner, the school district, and other partners

@@ -305,17 +311,23 @@ We limit employee and authorized party access to personal data

 Code.org’s officers, directors, employees, agents and contractors must have a legitimate business reason (related directly to furthering our charitable, nonprofit, education-focused mission) to access personal data we maintain about Users or others (e.g., to assist in product support). Code.org provides staff privacy and security training and will require our officers, directors, employees, agents, and contractors to comply with this Privacy Policy, and to treat any personal data of Code.org Users as confidential information.

-Your Choices - How to Access, Update, or Delete Your Information
+Your Choices - How to Access, Correct, Update, or Delete Your Information
+
+If, at any point, you wish to access, correct, update, or delete your personal data on the Code.org learning platform, you may do so from your Code.org account settings page as described below. Alternatively, you can email us at support@code.org or enter a request at https://code.org/contact. We will promptly review all such requests in accordance with applicable laws after verifying your identity. For Student accounts with a personal login, we will authenticate the request by requiring an email from the email address used to establish the account - and we will run the same one-way hash algorithm to match the request to the student account. For requests from Teachers (related to either Student Accounts in the Teacher’s section or to the Teacher’s account), we will generally require an email from the email address used to establish the account, but may be able to authenticate the account through other methods where we have additional teacher information in our records.
+
+In the event you believe your request has been improperly denied or insufficiently processed, you may appeal that decision by submitting your request and the reasons you believe your request was improperly denied or insufficiently processed in an email to privacy@code.org. Within forty-five (45) days after receipt of an appeal, we will inform you of any additional action taken or not taken in response to the appeal, along with a written explanation of the reasons in support of the response.

-If, at any point, you wish to access, amend, or delete your personal data on the Code.org learning platform, you may do so from your Code.org account settings page as described below. Alternatively, if you wish to access, amend, delete, export, or object to or restrict the processing of your personal data, you can email us at support@code.org or enter a request at https://code.org/contact. We will promptly review all such requests in accordance with applicable laws after verifying your identity.
+Due to the nature of the Services, projects and other data created while using the Services are generally meaningful only in the context of the Services and it is not technically feasible to transmit such data to the user or other entities for use outside of Code.org. We will, however, consider specific requests for data portability on a case-by-case basis.

 Unless we receive a deletion request, we may retain your personal data as long as a User account is active, as long as the personal data is necessary or useful for operational purposes, or as required under any contract or by applicable law. We may indefinitely retain information which has been de-identified or aggregated such that it is no longer personal data.

+We do not engage in targeting advertising, the sale of personal data, or profiling in furtherance of decisions that produce legal or similarly significant effects concerning a User. Therefore, we do not process requests to “opt-out” of such processing.
+
 Managing and Deleting Code.org Accounts

-Code.org does not require an account to try our courses. However, Students and Teachers with an account may update, correct, or delete Personal Information and other personal data in their Code.org accounts at any time via the account settings page after logging into their account. Teachers can go to their section’s “Manage Students” tab to update the most common settings or to access and delete a Student’s login information. Teachers also have the ability to reset the password of any Student in their section who is not also a Teacher. A parent or legal guardian of a Student under the age of 18 may also review Personal Information and other personal data and correct erroneous information, if any, by asking the Student or Teacher to access the Student account.
+Code.org does not require an account to try our courses. However, Students and Teachers with an account may update, correct, or delete Personal Information and other personal data in their Code.org accounts at any time via the account settings page after logging into their account. Teachers can go to their section’s “Manage Students” tab to update the most common settings or to access and delete a Student’s login information. Teachers also have the ability to reset the password of any Student not using a personal email login in their section who is not also a Teacher. A parent or legal guardian of a Student under the age of 18 may also review Personal Information and other personal data and correct erroneous information, if any, by asking the Student or Teacher to access the Student account.

-Except as described below, personal data of any Student that is in a Teacher's section will be under the control of the Teacher. The Teachers for these sections get access to the Student’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’s account will no longer be managed by the Teacher and the Student may retain possession and control of the Student-Generated content by creating a personal email login. If a Teacher deletes their own Teacher account (and all sections under their account) or removes a Student from a section they manage, the Student account in the section will also be deleted unless the Student has created a personal email login for their Student account. If the Student has created a personal email login, the Student account will be removed from the Teacher’s section but the Student account will not be deleted.
+Except as described below, personal data of any Student that is in a Teacher's section will be under the control of the Teacher. The Teachers for these sections get access to the Student’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’s account will no longer be managed by the Teacher and the Student may retain possession and control of the Student-Generated content by creating a personal email login. If a Teacher deletes their own Teacher account (and all sections under their account) or removes a Student from a section they manage, the Student account in the section will also be deleted unless the Student has created a personal email login for their Student account. If the Student has created a personal email login, the Student account generally will be removed from the Teacher’s section but the Student account will not be deleted. However, we may be contractually obligated to delete, at a school’s request, all student accounts enrolled in a teacher’s section even if the student account uses a personal login. If a student wishes to maintain full control over a student account they use outside of school, the student should not use that account to enroll in a teacher’s section, and should instead create and use a separate student account for the teacher’s section.

 In order to allow Users to recover deleted accounts, we will save progress, code creations and other data for a short period of time after a User executes an online deletion request. A User can email support@code.org or enter a request at https://code.org/contact to request an immediate permanent deletion of their account and all the associated data. A Teacher may also request the immediate deletion of Student accounts or particular Student projects or Student personal data the same way. Deleting a Student’s project will not delete other Students’ creations that were previously remixed from the deleted project. As part of the deletion process, we may de-identify data by removing identifiers such that remaining data cannot reasonably be used to re-identify a user. We do this to allow for ongoing research or product improvement (e.g., retaining a gender identifier to help analyze ongoing efforts to improve discrepancies in computer science learning).

@@ -329,24 +341,62 @@ School Users and Student Records

 Code.org may be used in a classroom setting by schools, school districts, or teachers (collectively referred to as “Schools”). When the Services are used as part of a School’s educational curriculum, the personal data related to the School’s Student Users that is provided to Code.org by the School or collected by Code.org during the provision of the Services to a School, may include information defined as “educational records” by the Family Educational Rights and Privacy Act (“FERPA”) or be covered by other similar student data privacy laws, to which the School may be subject. In these cases, the Student’s personal data we collect, along with any other student records the school provides to us and any student-generated content is referred to as “Student Records” and we have implemented controls and procedures to help the Schools address their obligations under such laws. In some cases where we process Student Records, we may enter into separate agreements with Schools that supplement our Terms of Service, such as our Student Data Privacy Addendum.

-Because many of our Student accounts are used for both School and non-School purposes, only personal data relating to Code.org accounts that are (1) created by a School (for example, when a Teacher creates the user name, login and password to establish the Student account, or when the teacher rosters a class using Google Classroom, Clever, or similar authentication service), or (2) created by a Student at the direction of a School or Teacher, using a School email address and associated with a Teacher’s section, are “Student Records.” Student Records do not include information a Student or other individual may provide to Code.org independent of the Student’s use of the Services at the direction of the School.
+Because many of our Student accounts are used for both School and non-School purposes, only personal data relating to Code.org accounts that are (1) created by a School (for example, when a Teacher creates the user name, login and password to establish the Student account, or when the teacher rosters a class using Google Classroom, Clever, or similar service), or (2) created by a Student at the direction of a School or Teacher, using a School email address and associated with a Teacher’s section, are “Student Records.” Student Records do not include information a Student or other individual may provide to Code.org independent of the Student’s use of the Services at the direction of the School. However, if a Student User links their existing personal account to a Teacher’s section, information associated with the personal account may be considered Student Personal Data to the extent it contains data generated as part of the curriculum in the Teacher’s section. In such cases, the account may have hybrid qualities, with some control over the account shared by the Teacher (and school) and the Student. For example, refer to the data deletion discussion above under Managing and Deleting Code.org Accounts.

-Protecting Children’s Privacy
+Children’s Privacy Notice

-The Code.org Services are designed for 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. As a nonprofit entity, Code.org is not subject to the Children's Online Privacy Act (“COPPA”). However, Code.org takes numerous steps to minimize the collection and use of Personal Information from children under the age of 13 as described throughout this Privacy Policy, some of which go beyond COPPA requirements, including:
+This privacy notice supplements our full Privacy Policy and provides additional information about how we collect, use and share Personal Information from children under the age of 13 (a “Child” or “Children”). The Code.org Services are designed for Users of all ages, including Children with the involvement of and pre-authorization by their school, teacher, parent or legal guardian. As a nonprofit entity, Code.org is not subject to the Children's Online Privacy Act (“COPPA”). However, Code.org takes numerous steps to promote parental involvement in their Child’s use of Code.org and to minimize the collection and use of Personal Information from Children as described throughout this Privacy Policy, some of which go beyond COPPA requirements, including:

-We do not collect or maintain actual Student email addresses for Student accounts (even those for Students 13 or older). We only collect and maintain a one-way hashed version of the email address which we cannot reverse.
-We expect Teachers who create Student accounts as part of a School’s educational curriculum to represent that they or the educational organization have obtained any necessary parental consent to register a child under the age of 13.
+We do not store actual Student email addresses for Student accounts (even those for Students 13 or older). We only store a one-way hashed version of the email address which we cannot reverse.
 We do not collect full dates of birth, only age.
 We do not collect Student physical addresses or phone numbers.
 We do not generally support the display of public user profiles, except when we highlight or profile a user, with appropriate permission.
 We do not support online messaging between Students (except for the Internet Simulator function for classrooms).
-We encourage the use of screen names that are first name or first name and last initial only.
 We only display a Student’s first initial when we display projects on our Services.
 We only provide a mechanism for Students age 13 or over to post projects to their social media accounts.
 We automatically monitor some text entered in projects for elementary school courses, such as Play Lab and Sprite Lab, to help prevent sharing of personal data such as email address and phone number.
 When we allow uploads of custom images, sounds, and videos by Students under age 13, we implement controls that block Student sharing of such projects.

+We do not require Users to create a Code.org account or otherwise provide Personal Information in order to participate in the Hour of Code tutorials or to try our courses. However, we cannot save a Student’s learning progress or a Teacher’s class records unless the User has a Code.org account (whether an account with a personal login or an account created by a Teacher).
+
+Code.org account sign-up
+
+When a Child creates a Code.org account using a personal login, we request a username, age (not birthdate), password, and email address (although we retain only a one-way hash of Student email addresses). In some jurisdictions, we may seek the consent of a parent or legal guardian before establishing the account for a Child.
+
+A School may create a Code.org account for a Child
+
+When Code.org is used by a School in an educational setting in classrooms with Children, we strongly recommend that Teachers not ask their students to create Code.org accounts with personal logins. Instead, we recommend that Teachers use one of the account creation methods noted below.
+
+Teachers who have classrooms with Children can create Code.org accounts without personal logins by using either a rostering service like Google Classroom or Clever, or by creating Code.org logins with picture passwords or secret word passwords that Teachers set for each student in a Teacher section (in which case the School may avoid providing any Personal Information). When Schools create Code.org accounts in these manners, we rely on the Teacher/School to obtain required consent, if any.
+
+As previously noted, in some jurisdictions if a Teacher chooses to have Child students create accounts with personal logins, we may require parental consent for the account creation - which can result in delays and hinder classroom participation. Similarly, if a Child later seeks to add a personal login to access their Code.org account independently of their Teacher or School (e.g., they wish to maintain their account and projects for use outside of school or after the school year ends), we may require parental consent in some jurisdictions to create the personal login - however, the Child will continue to be able to use their existing School login credentials pending the parental consent for the personal login.
+
+How Parents can provide consent (where required)
+
+Although parental consent is not generally required, in those jurisdictions where we require such consent in connection with a Child account, the parent may provide consent by responding affirmatively to an email sent by Code.org to the Parent’s email address provided by the Child during registration. We will send a reminder email after a few days if no response is received, but if we do not receive consent within the time prescribed, the Child’s account will be closed and all account information (including the parent’s email information) will be deleted from our systems. If parental consent is received, the Parent’s email address will be automatically linked to their child’s account to stay updated on their Child’s progress and projects - and the Parent email address can also be used for password recovery and to request support (including account deletion at any time) for the Child’s account. Parents will need to ensure they know their child’s email address and username for support requests.
+
+How we restrict functionality for Child accounts
+
+As explained in more detail in the full Privacy Policy, Code.org attempts to restrict Child account access to certain features that could potentially increase the inadvertent disclosure of the Child’s personal information through the Service.
+
+What information we collect for a Child account, and how we use this information
+
+We collect a username, age (not birthdate), password, and email address (although we retain only a one-way hash of Student email addresses) when a Child registers for the Service and creates a personal login. We collect information about the Child’s use of the Service (e.g., course progress; project creations; technical information; etc.) as detailed in the table at the outset of our full Privacy Policy. We use this information to provide the Service and for the purposes described in the table.
+
+How we share or transfer information relating to a Child account
+
+We do not rent or sell information that we collect from Users (including Child accounts), or exploit it for financial gain in any other way. We take steps to restrict user-initiated sharing of Personal Information related to Child accounts. As outlined in more detail in our full Privacy Policy, we may disclose Personal Information related to Child accounts under limited circumstances, such as to service providers who we contract with to provide services to us, Teachers and Schools, and when required by law or when necessary or appropriate to protect Code.org or others.
+
+No Third Party Tracking and No Targeted Advertising
+
+Code.org does not display targeted advertising on the Service. We do not disclose personal information of Children for direct marketing purposes or for targeted advertising purposes - on our site or on other sites.
+
+How to access, modify and delete Children Accounts
+
+As a Parent, you have the ability to access and control information about your Child - including requesting deletion of the Child account - by either logging into their account with their credentials and using the self-help delete function or by contacting us from your Parent email address associated with the child’s account (if any) at support@code.org.
+
+In some cases, administrative controls including the ability to modify or delete the account, are held by the School and you will need to direct your request to the School. For more information, please review School Users and Student Records in the full Privacy Policy.
+
 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 and delete any hashed email address or inadvertently collected Personal Information or Persistent Identifiers. To make such a request, please email us at support@code.org or enter a request at https://code.org/contact. Before processing your request, we may verify your identity and your relationship with the Student.

 Links to Other Sites and Services
@@ -402,4 +452,4 @@ Where applicable, we will not make any material changes to the Privacy Policy th

 Contacting Code.org

-Please contact Code.org with any questions or comments about this Privacy Policy by emailing us at privacy@code.org or writing to us at Code.org (Attn. Privacy), 1501 Fourth Ave, Suite 900, Seattle, WA 98101. As set forth above, requests to access, update, or delete your personal data should be submitted by email to support@code.org or entered at: https://code.org/contact.
\ No newline at end of file
+Please contact Code.org with any questions or comments about this Privacy Policy by emailing us at privacy@code.org. As set forth above, requests to access, update, or delete your personal data should be submitted by email to support@code.org or entered at: https://code.org/contact.
\ No newline at end of file

diff --git a/code.org/privacy.md b/code.org/privacy.md index ede55393..f24f91b0 100644 --- a/code.org/privacy.md +++ b/code.org/privacy.md @@ -2,7 +2,18 @@ Privacy Policy Date of Last Revision: April 4, 2024 -You can review the previous Privacy Policy here. +Previous Privacy Policies: + +December 2014 +April 2016 +April 2018 +May 2018 +September 2020 +March 2021 +July 2021 +November 2021 +October 2022 +December 2022 About Code.org

diff --git a/code.org/tos.md b/code.org/tos.md index 78b09677..df0db83a 100644 --- a/code.org/tos.md +++ b/code.org/tos.md @@ -1,9 +1,8 @@ -Sign in Terms of Service -Date of Last Revision: December 14, 2022 +Date of Last Revision: April 4, 2024 -Code.org is a 501(c)(3) nonprofit 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://www.k12cs.org, https://codeprojects.org, https://hourofcode.com, https://curriculum.code.org, https://advocacy.code.org, other websites, information, text, curricula, videos, graphics, photos, APIs, email notifications and other materials and related products and services (the “Services”). +Code.org® is a 501(c)(3) education innovation nonprofit (“Code.org”) dedicated to the vision that every student in every school has the opportunity to learn computer science as part of their core K-12 education. As a part of that mission, Code.org operates the websites located at https://code.org, https://studio.code.org, https://www.k12cs.org, https://codeprojects.org, https://hourofcode.com, https://advocacy.code.org, and may provide 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. @@ -17,15 +16,15 @@ Some Services may be subject to additional posted guidelines, rules or terms of Children Under Age 13 -We take steps to minimize the collection of personal data from Users under the age of 13 as explained in the Code.org privacy policy. Users under the age of 13 will be able to use our App Lab, Game Lab, and Web Lab tools in the classroom with their teacher’s approval. Users under the age of 13 will not be permitted to use these tools for outside the classroom use. Users under 13 can try most tutorials and courses without creating an account, but their learning progress won’t be saved. Users under the age of 13 are required to to get the approval of a parent or legal guardian before creating an account on Code.org. Code.org allows certain representatives of school districts and schools, such as teachers, administrators, counselors, and other educators (an “Educator”) to connect with their students through the Services in order to provide tutorial, educational and similar services. If you are an Educator, you may register accounts on the Services for one or more of your students. +We take steps to minimize the collection of personal data from Users under the age of 13 as explained in the Code.org Privacy Policy. Users under the age of 13 will be able to use our App Lab, Game Lab, and Web Lab tools in the classroom with their teacher’s approval. Users under the age of 13 will not be permitted to use these tools for use outside the classroom. Users under 13 can try most tutorials and courses without creating an account, but their learning progress won’t be saved. Although we encourage parental oversight for all Users under 13, depending on jurisdiction, Users under 13 may be required to get the approval of a parent or legal guardian before creating an account on Code.org. Code.org allows certain representatives of school districts and schools, such as teachers, administrators, counselors, and other educators (an “Educator”) to connect with their students through the Services in order to provide tutorial, educational and similar services. If you are an Educator, you may register accounts on the Services for one or more of your students. -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 data 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 are an Educator and you register an account for a student who is under 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, that you have reviewed the Children’s Privacy Notice in the Code.org Privacy Policy and that you have obtained any necessary parental consent for Code.org’s collection of the Child’s personal data 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. Your Account 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. -Code.org may permit you to register an account for the Services through certain third party social networking services, such as Facebook Connect and Google (“Authentication Service”). By registering for the Services using an Authentication Service, you agree that Code.org may access your account information from the Authentication Service and you agree to any and all terms of use of the Authentication Service regarding your use of the Services via the Authentication Service. You are solely responsible for your interactions with the Authentication Service. +Code.org may permit you to register an account for the Services through certain third-party social networking services, such as Facebook Connect, Google, and Microsoft (“Authentication Service”). By registering for the Services using an Authentication Service, you agree that Code.org may access your account information from the Authentication Service and you agree to any and all terms of use of the Authentication Service regarding your use of the Services via the Authentication Service. You are solely responsible for your interactions with the Authentication Service. Privacy @@ -41,7 +40,7 @@ We help schools be compliant with the Family Educational Rights and Privacy Act User Generated Content - Management; License Grant; Representations and Warranties -The Services enable Users and Schools (as defined in our Privacy Policy) to provide, share or post certain content or information, including, but not limited to, computer code (including both source and object code), audio recordings, photographs, videos, documents, online educational resources, or other materials, and Feedback, (as defined below) (collectively, “User Content”). You should not include any Student’s Personal Information (which are defined in our Privacy Policy) or Student educational records, in any of the User Content you create. If you or a Student in your class accidentally includes any Student’s Personal Information, please contact us at support@code.org. User Content may be used by Code.org in connection with the Services and may be visible to or shared with Code.org, other Schools, and certain other Users. Please visit our Privacy Policy for additional information on the types of information different Users are able to provide. +The Services enable Users and Schools (as defined in our Privacy Policy) to provide, share or post certain content or information, including, but not limited to, computer code (including both source and object code), audio recordings, photographs, videos, documents, online educational resources, or other materials, and Feedback, (as defined below) (collectively, “User Content”). You should not include any Student’s Personal Information (as defined in our Privacy Policy) or Student educational records, in any of the User Content you create. If you or a Student in your class accidentally includes any Student’s Personal Information, please contact us at support@code.org. User Content may be used by Code.org in connection with the Services and may be visible to or shared with Code.org, other Schools, and certain other Users. Please visit our Privacy Policy for additional information on the types of information different Users are able to provide. Teachers may contribute educational content, create answers to assessments, create derivative works (e.g., completion of assignments, projects, etc.), and transmit said data and content within the School’s systems through the Services (collectively, “Teacher Content”). @@ -49,9 +48,9 @@ Schools and Users may submit feedback, comments or suggestions for improvements Ownership -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). +You (and/or your School) own your User Content. By submitting or distributing User Content through the Services or directly to Code.org staff, you hereby grant to Code.org a limited license as set forth below. -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. +In addition, by submitting or distributing User Content through the Services for public display, you hereby grant to each user of the Services a non-exclusive license to access and use your User Content. License to User Content User Content @@ -64,17 +63,17 @@ use and disclose metrics and analytics regarding the User Content in an aggregat use any de-identified User Content for any lawful purpose (such as product development, research or other purposes) subject, if applicable, to the Data Privacy Addendum or similar agreement; and use for other purposes permitted by the Code.org Privacy Policy and, if applicable, the Data Privacy Addendum or similar agreement. -Code.org will only share and use your personal data in accordance with Code.org's current Privacy Policy. When you upload or create User Content, this can be viewed by your Teacher and (under your control) by other Users and this means that you are allowing others to access and use that information and to associate it with you. +Code.org will only share and use your personal data in accordance with Code.org's current Privacy Policy. If you are enrolled in a Teacher section, User Content you upload or create can be viewed by your Teacher and (under your control) by other Users, which means that you are allowing others to access and use that information and to associate it with you. -By uploading, creating, submitting or distributing User Content through the Services, you hereby grant other Users a non-exclusive, transferable (only to a successor), royalty-free right and license to use, reproduce, create derivative works, publicly display and perform any of your User Content that is incorporated into that User's project, provided that Code.org shall not use or distribute your User Content on a stand alone basis if Code.org’s license grant has been terminated as set forth below. The foregoing license and restrictions does not limit Code.org rights under any third party or open source license in which your User Content may be licensed. +By uploading, creating, submitting or distributing User Content through the Services and consenting to their public display (e.g., in featured projects), you hereby grant other Users a non-exclusive, transferable (only to a successor), royalty-free right and license to use, reproduce, create derivative works, publicly display and perform any of your User Content that is incorporated into that User's project, provided that Code.org shall not use or distribute your User Content on a stand-alone basis if Code.org’s license grant has been terminated as set forth below. The foregoing license and restrictions does not limit Code.org rights under any third-party or open-source license in which your User Content may be licensed. Public Content -In addition to the rights, licenses and privileges referred to above, you agree that Code.org may use and refer to your User Content, first name and screenname that are posted publicly on the Code.org Website and not in private areas of our Service (“Public Content”) (including screenshots) in marketing materials, press releases, financial reports, presentations, website materials, customer lists and other media now known or hereafter discovered in connection with the marketing, advertising and promotion of the Service, and any products, goods, features, capabilities and/or services associated with the Service. This right will continue until your Public Content is deleted; provided however, that any Public Content previously printed in brochures, articles or other marketing materials that Code.org had prepared before any request for deletion was received will continue to be used. +In addition to the rights, licenses and privileges referred to above, you agree that Code.org may use and refer to your User Content that is posted publicly on the Code.org Website and not in private areas of our Service (“Public Content”) (including screenshots) in marketing materials, press releases, financial reports, presentations, website materials, customer lists and other media now known or hereafter discovered in connection with the marketing, advertising and promotion of the Service, and any products, goods, features, capabilities and/or services associated with the Service. This right will continue until your Public Content is deleted; provided however, that any Public Content previously printed in brochures, articles or other marketing materials that Code.org had prepared before any request for deletion was received will continue to be used. License Termination -The User Content license above will terminate when you or your School (i) delete any User Content containing intellectual property rights (like images or videos) or personally identifiable information (such as that in Student Data); or (ii) delete your account, unless your User Content has been shared with others, and they have not deleted it. Such termination may not apply to User Content or Teacher Content, including Student Data or in messages sent through Code.org, that may be deemed an “education record” under the Family Education Rights Act (FERPA) or various other student privacy laws, and which a school controls (“Education Record(s)”). We will delete any Education Record upon receiving a valid request for deletion from your school. Please see our FAQ for more information. Additionally, such termination will not affect the license rights granted to other Users to use your User Content if they previously copied your User Content and they have not deleted it. When you or your School delete User Content it is deleted in a manner similar to emptying the recycle or trash bin on a computer. However, you understand that any removed User Content may persist in backup copies for a reasonable period of time following deletion (but will not be available to others). Additionally, you understand and agree that User Content may continue to appear on Code.org, even after you have terminated your account or these Terms of Service, as portions of your User Content may have been copied by other users and/or incorporated into their coding projects. +The User Content license above will terminate when you or your School (i) delete any User Content containing intellectual property rights (like images or videos) or personally identifiable information (such as that in Student Data); or (ii) delete your account, unless your User Content has been shared with others, and they have not deleted it. Such termination may not apply to User Content or Teacher Content, including Student Data or in messages sent through Code.org, that may be deemed an “education record” under the Family Education Rights Act (FERPA) or various other student privacy laws, and which a school controls (“Education Record(s)”). We will delete any Education Record upon receiving a valid request for deletion from your school. Additionally, such termination will not affect the license rights granted to other Users to use your User Content if they previously copied your User Content and they have not deleted it. When you or your School delete User Content it is deleted in a manner similar to emptying the recycle or trash bin on a computer. However, you understand that any removed User Content may persist in backup copies for a reasonable period of time following deletion (but will not be available to others). Additionally, you understand and agree that User Content may continue to appear on Code.org, even after you have terminated your account or these Terms of Service, as portions of your User Content may have been copied by other users and/or incorporated into their coding projects. User Content Representations and Warranties @@ -92,23 +91,22 @@ Code.org has no obligation to monitor User Content or other materials. You are r 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. +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. -Your License to Use Code.org Software, Videos, Curriculum and Tutorial Materials, JSON API, and Conference Board Data +Your License to Use Code.org Software, Videos, Curriculum and Tutorial Materials, and Conference Board Data The following table provides an overview of the licenses and restrictions governing Code.org software code, videos, curriculum and tutorial materials, and APIs, as well as data we publish from the Conference Board. More detailed descriptions are provided below. Code.org Materials Governing License and Restrictions -Code.org code-base on github Apache 2.0 license (code-base only; excludes videos, curriculum and tutorial materials, APIs, and other data described below) +Code.org code-base on github Apache 2.0 license (code-base only; excludes videos, curriculum and tutorial materials, APIs, and other data described below) - subject to proprietary material notice as described below Code.org videos Creative Commons BY-NC-ND 4.0 license (subject to express conditions below) Code.org curriculum and tutorial materials (other than proprietary videos and third-party artwork) Creative Commons BY-NC-SA 4.0 licence (subject to express conditions below) Celebrity and other video and tutorial “cast” members’ likenesses and names Not Applicable. Can be used only as incorporated into Code.org materials Artwork in Code.org tutorials (including third-party artwork or any other IP licensed to Code.org) Not Applicable. Can be used only as incorporated into Code.org materials -JSON API Creative Commons BY-NC-SA 4.0 licence (subject to express conditions below) Conference Board Data The Conference Board Terms of Use (at www.conference-board.org) Code.org trademarks Not Applicable. Require express written permission from Code.org -The code powering Code.org’s websites and tutorials is governed by an open source Apache License which is posted as part of the source code repository in github. +The code powering Code.org’s websites and tutorials is governed by an open source Apache License which is posted as part of the source code repository in github. Please refer to the Proprietary Materials Notice referenced in the Apache License for limits related to the use, distribution, or access to certain proprietary material within the source code and assets. Code.org’s library of videos is governed by and licensed to you for use under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 Unported License. More information about this license can be found at https://creativecommons.org/licenses/by-nc-nd/4.0/. Code.org 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. @@ -118,8 +116,6 @@ The artwork used in our tutorials is copyrighted and use of these tutorials does 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. Except as set forth above, you may not otherwise use Code.org materials for commercial purposes. If you are interested in licensing Code.org materials for commercial purposes, contact us. -The Code.org JSON API and database of schools is also licensed via the 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/, which means you are free to use the data to make derivative works, as long as you give Code.org attribution. - Any data provided by The Conference Board is provided “as is” with no warranty whatsoever, and is protected by United States and International Copyright laws. The data displayed are provided for informational purposes only and may only be accessed, reviewed, published, and/or used in accordance with, and the permission of, The Conference Board consistent with the Terms of Use displayed at www.conference-board.org. Such data may not be extracted for use in a database, used to create a derivative work, or otherwise misused by any means without express written permission from The Conference Board, except that you may make limited noncommercial use as consistent with Fair Use under Section 107 of the Copyright Act of 1976. The Conference Board® and The Conference Board Help Wanted OnLine® are registered trademarks of The Conference Board. The Conference Board reserves all rights in and to its trademarks. Further information regarding The Conference Board Help Wanted OnLine® can be found here. Copyright Policy @@ -136,17 +132,17 @@ Code.org Intellectual Property Rights, and Your License to Use the Services All right, title, and interest in and to the Services (excluding User Content) 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. +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, and tutorials 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®, the CODE® logo, Code Studio®, Hour of Code®, Hora Del Codigo®, and CS Discoveries® are registered trademarks of Code.org. You may only use the Code.org trademarks 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. Other Entities’ Intellectual Property Rights -The Services may include intellectual property of other entities, which have provided Code.org limited use permission. Your use of the Services does not provide any right to copy, reproduce, or otherwise use such entities’ intellectual property except as explicitly stated herein. In addition to the trademarks and copyright limits set forth in the “Your License to Use Code.org Videos, Tutorial, Data, and APIs” section, other trademark and copyrights used on the Services include, but may not be limited to: Google Classroom is a trademark of Google Inc. © Google Inc. Amazon Web Services and the “Powered by AWS” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. +The Services may include intellectual property of other entities, which have provided Code.org limited use permission. Your use of the Services does not provide any right to copy, reproduce, or otherwise use such entities’ intellectual property except as explicitly stated herein. In addition to the trademarks and copyright limits set forth in the “Your License to Use Code.org Software, Videos, Curriculum and Tutorial Materials and Conference Board Data" section, other trademark and copyrights used on the Services include, but may not be limited to: Google Classroom is a trademark of Google Inc. © Google Inc. Amazon Web Services and the “Powered by AWS” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. Code.org Store and Support Forums @@ -197,13 +193,13 @@ The failure of Code.org to enforce any right or provision of these Terms will no 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 those of 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. +Except as described in the following paragraph, 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 those of 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). +If you are a federal, state, or local government entity, or a local education agency or school 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 any state or local government entities and local education agencies or schools in the United States, the laws of your state (without reference to conflicts of law provisions) shall apply. For any U.S. federal government entities, the laws of the United States of America (without reference to conflict of law provisions) and, in the absence of federal law and to the extent permitted under federal law, the laws of the State of Washington (without reference to conflicts of law provisions) shall apply. 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 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. D. Assignment

milonmaze / privacy-terms-observatory-beta

code.org #95