As student-led coding initiatives like the upcoming December 2026 Scratch Design Camp prepare to launch, parents and educators are getting a closer look at how students collaborate online. While these peer-led events help build leadership skills, they also highlight the digital safety and data privacy challenges in student-moderated spaces. Understanding how these communities operate can help families support young coders while keeping their data secure.
What Happened
In preparation for the December 2026 session of Scratch Design Camp, youth organizers have begun coordinating roles for virtual "cabins" named Candy, Cookie, and Gummy. According to the official Scratch forum post, camp leaders are tasked with recruiting co-leaders and setting up digital studios before camper sign-ups open on November 1.
However, the coordination process highlights the informal workarounds students use to communicate. To invite co-leaders without spoiling the event for other users, organizers instructed leaders to share forum links in "discreet" locations and ask recipients to delete the comments once read. While intended to prevent spoilers, these practices bypass standard communication transparency and show how young users handle platform limitations on their own terms.
The Bigger Picture
For parents and educators, Scratch is a collaborative, ad-free digital playground run by a nonprofit foundation. However, understanding the rules of this platform is not always straightforward. Users have noted that Scratch’s official guidelines and safety policies are fragmented across multiple pages, making them difficult for children to find and read.
This lack of clarity extends to data privacy. As we previously reported, Scratch collects basic user details like usernames, email addresses, and parental contact information. While the platform is free of commercial ads, it still tracks user behavior using analytics tools like Google Tag Manager.
Families should also know what happens to their child's creative work. Under Scratch’s Terms of Service, shared projects are licensed under a Creative Commons framework. This allows other users to remix work, but it also grants the Scratch Team a perpetual license to use these creations for various purposes, including training AI models.
If a student decides to leave the platform, deleting their account may not completely erase their digital footprint. Because of a technical flaw known as the "Remaining Data Bug", some comments and forum posts can remain publicly visible even after an account has been converted into a blank, GDPR-compliant profile.
What This Means for Families
The informal communication habits seen in youth-led camps, such as deleting comments to keep links quiet, show that students are highly resourceful. However, these behaviors also show that children do not always recognize how their actions affect digital footprints and moderation.
When students delete comments to hide coordination, they may inadvertently make it harder for automated filters or human moderators to flag inappropriate interactions. For educators and parents, this emphasizes the need to teach students that online safety rules apply even during harmless, community-run events.
What You Can Do
Parents can help protect their children by encouraging anonymous accounts. When setting up a Scratch profile, make sure your child chooses a username that does not reveal their real name or personal details, as recommended by privacy advocates.
It is also helpful to discuss communication boundaries. Teach children that deleting comments or using "discreet" threads to bypass standard sharing practices can undermine online safety, even if done for a harmless camp.
If your child decides to close their Scratch account, have them manually clean up their profile first. Deleting projects and comments beforehand prevents the "Remaining Data Bug" from keeping public posts online.
Finally, review AI licensing terms together. Talk with your student about the fact that any public project they share on Scratch may be used to train AI models, and decide together which projects are appropriate to publish.