code.org - Githubissues

milonmaze / privacy-terms-observatory

Privacy Terms Observatory is an archive of published privacy and terms of popular websites.

3 stars 3 forks source link

6c55aea2222c60dadb0b3f28a52b2ca3c71318b7: https://code.org/privacy @ 2021-11-13

difference captured:

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 d682827..c66661c 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 f8da02d..f586d0a 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: 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,15 +188,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 or the Hourofcode.com 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

milonmaze / privacy-terms-observatory

code.org #42