Privacy policy

What we collect

When you have an account we store:

• Your account details — your email address, your username and the name you choose to display.
• A profile picture, if you upload one. If you sign in with Google or Microsoft, we copy the profile picture from that account when you first sign in.
• Sign-in details from Google or Microsoft, when you use one of those buttons. We store the account identifier that provider gives us, and the access token it issues, on your user record so we can recognise you next time.
• Your projects — the code you write, the files in each project, and any images or other assets you add to them.
• Your work in a course — assignment submissions, quiz and activity answers, which activities you have completed, your progress through a course, and how long you spend working on each activity, which your teacher can see.
• Feedback on your work — comments and code suggestions your teacher leaves on what you submit.

We do not sell any of this, and we do not use it for advertising.

Cookies

We set one cookie when you sign in. It keeps you signed in as you move between pages and it is what tells the site which projects and classes are yours. If you block it, you cannot stay signed in.

We do not use advertising or cross-site tracking cookies.

Who can see your work

If you are a student, the staff running your course can see the work you submit to it. That is not only the teacher who set the work: it is anyone who can manage that course's content, and anyone who owns or helps teach one of its classes. That is deliberate — a course usually has more than one teacher, and cover teachers need to be able to mark work too.

Site administrators — the people who run this installation of Python Classroom — can look up any account and see its projects. They need that to keep the service working and to deal with abuse reports.

Other students cannot see your work unless you choose to share a project with them.

Other services your browser talks to

Some parts of the site are served by other companies. When your browser loads them, that company can see your IP address and which page asked for the file.

• jsDelivr serves the Python engine that runs your code. Your code runs inside your own browser and is never sent to jsDelivr — but your browser fetches the engine from there, so jsDelivr sees a request every time you run a program.
• Cloudflare's cdnjs serves shared scripts and stylesheets used across the site.
• Google and Microsoft, if you choose to sign in with one of those accounts. From them we receive your name, email address and profile picture, along with the account identifier and sign-in token described above.
• Our email provider delivers messages such as password resets and email verification. Your email address is passed to them so the message can be sent.

Feedback you send us through the feedback button goes to a private Trello board, along with your username and email address so we can reply. If a page fails with an error, a report is filed on the same private board automatically, including the page address and your browser details.

If you attach a screenshot to that feedback, the image is sent to the private Trello board and nowhere else. We never store the screenshot on this site.

Where your data is stored

Accounts, projects, courses and submissions are stored in a MongoDB Atlas database hosted in Sydney, Australia. Uploaded files and images are stored in Cloudflare R2, which distributes them across Cloudflare's own network rather than pinning them to a single named region.

Deleting your account

You can delete your own account whenever you like. Sign in, go to account settings, then Delete account, and confirm.

Deleting your account removes your user record, the projects you own or created — including your assignment submissions — your folders, your exports, and any courses you own. It also removes you from courses you belong to but do not own. It cannot be undone.

To be straight with you about what deletion does not reach: your saved answers to activities, the record of which activities you completed, and any feedback you sent us are not removed by this, and neither are code-authenticity records if your school has those switched on. If you want those removed as well, email [email protected] and ask.

If your school created and controls your account, or you have a question about any of this, email [email protected].

Students under 18

Python Classroom is built for school use, and we expect most students using it to be children. Accounts are created in a school context: the school or teacher decides that their class will use the site, enrols the students, and is responsible for obtaining whatever consent their own policies and local law require. We do not seek consent from students directly.

If you are a parent or guardian and want to know what is stored about your child, or want it removed, please talk to their teacher or school first — they hold the class — or email [email protected].

Changes to this policy

If what we collect or who we share it with changes, we update this page and change the date at the top. There is no separate archive of older versions.

Contact

Questions about privacy, or about anything on this page, go to [email protected].