Who Operates CodeQuest
CodeQuest CS is a UK-based educational learning platform for GCSE and A Level Computer Science revision. TODO: Replace this section with the final legal operator name, postal details if required, and monitored privacy contact before public school rollout.
What Data We Collect
CodeQuest may collect username, email address, display name, account role, selected avatar, class membership, teacher-created classes, assignments, lesson progress, activity progress, quiz or challenge attempts, XP, levels, streaks, achievements, and timestamps such as account creation, completion dates, and recent activity.
Why We Collect It
This information is used to create accounts, keep users signed in, save learning progress, award XP and achievements, connect students to teacher classes, calculate assignment progress, and help authorised teachers support students in their own classes.
Lawful basis wording must be finalised before launch. TODO: Replace with final legal wording before public school rollout.
Who Can See Student Data
Students can see their own progress. Teachers can only see progress for students who have joined their class using a class join code. Public visitors cannot see student progress, class memberships, quiz attempts, XP, achievements, or assignment progress. Students cannot see other students' private progress.
Children And Students
CodeQuest may be used by students under 18, so privacy information should be clear, age-appropriate, and supported by school or parent context where needed. Students should not put personal information in usernames or display names. A simpler student version is available at Privacy explained for students.
Sharing And Advertising
Student data is not sold to advertisers. CodeQuest should only use student data to run the learning platform, support classes, improve safety, and respond to support, privacy, or safeguarding requests.
Cookies
CodeQuest uses essential cookies for login sessions, CSRF protection, and platform security. Analytics or marketing cookies should not be added without a cookie/privacy review, especially because the service may be used by children.
Third-Party Services
Hosting, source control, database, static asset, and email providers may process limited technical or account data where needed to operate CodeQuest. TODO: Replace with the final list of production providers, such as hosting, GitHub, database, and email services, before public school rollout.
Retention And Deletion
Class membership and progress are retained while an account is active unless deletion is requested and legally appropriate. Test or beta accounts may be deleted before the next rollout phase. Production retention periods must be finalised before school use at scale.
Security
CodeQuest uses Django authentication, password hashing, CSRF protection, role-based access checks, teacher class ownership checks, and production security settings such as secure cookies when DEBUG is disabled. Admin access should be restricted to trusted staff only.
Your Rights And Requests
Users, parents, guardians, teachers, or schools may request access, correction, deletion, or support through the contact page or by emailing admin@mycode.quest. The request-handling process should still be legally reviewed before school rollout.