When young creators leave Scratch, the coding platform developed by the Massachusetts Institute of Technology, parents and teachers often assume their digital footprints are completely gone. However, recent forum discussions and technical bugs show that deleting an account does not always guarantee a clean slate. Understanding how the platform handles student-created projects and comments is important for managing digital privacy in schools and at home.
What Happened
A recent thread on the Scratch discussion forums raised questions about what happens when a student deletes their account. Users in the on-site discussion noted that Scratch offers departing users an option to either keep or delete their shared projects and profile content. While this setting suggests control, technical issues complicate the process.
According to reporting from ScratchNews, a community news outlet, a technical issue known as the 'Remaining Data Bug' often prevents complete data erasure. Even when users choose to delete their accounts or request a total wipe, certain comments, forum posts, and associated metadata can remain visible. This means a student’s public footprint may persist long after the account is closed.
The Bigger Picture
For schools and families managing student privacy, Scratch has taken steps to protect users, but some tracking elements remain. Under the Scratch Privacy Policy updated in 2023, the platform collects usernames along with email addresses and parent contact details. An independent safety review by ethical.net notes that Scratch advises children to choose anonymous usernames and keeps its platform free of commercial, third-party advertising. However, the site still uses tracking cookies and analytics tools like Google Tag Manager to monitor user behavior.
To remove data completely, European Union users frequently rely on General Data Protection Regulation (GDPR) mandates to force complete purges. Under these rules, the Scratch Team attempts to erase all public information associated with the account. According to ScratchNews, this process strips the account of its 'About Me' section, custom profile icons, shared projects, and curated studios. This transforms the profile into a blank 'GDPR account' with a reset join date.
Unfortunately, the systemic remaining data bug means that even these formal legal purges do not always clean up every comment or forum thread. This lack of automated cleanup is a known issue. As we previously reported, while student coders frequently push for more professional-grade technical tools and better platform infrastructure, backend issues like persistent user data remain a challenge for the developers at MIT.
What This Means for Families
For parents and educators, these technical limitations mean that children should never post personally identifiable information on the site. If a student has shared their real name or school location in a comment or forum reply, deleting the account may not remove that information from public view.
Because comments can linger due to platform bugs, digital citizenship lessons must teach the permanence of online writing. Educators using Scratch in the classroom should monitor student interactions and guide them on how to manage their public profiles before deletion.
What You Can Do
To protect student privacy, parents and teachers can take several steps.
First, have students manually delete individual projects and sensitive comments before starting the account deletion process. This ensures the database removes them.
Second, ensure students never use real names or birth years in their usernames, following the advice in the ethical.net analysis.
Finally, if you need complete data removal for safety, contact the Scratch Team directly to request a formal account purge. Afterward, manually check the profile URL to verify what remains.