Privacy

A short, true answer to "where does student work go, and who can see it?"

In general

• Python runs on the student's own computer, in their browser. We run no server that executes code.
• PyPad has no accounts, no tracking and no analytics, and sets no tracking cookies.
• The page loads its own files from pypad.dev. Maths rendering uses MathJax from a pinned public CDN.

In a quiz question

A student's work is saved with their answer in your learning system (for example Moodle), exactly as any other answer is. It is visible to whoever can see quiz answers there. PyPad does not send it anywhere else.

In a live lecture

The presenter's notebook is shared through a small room service (live.pypad.dev). It holds the document while a lecture runs and deletes it after a time limit once the room is empty. Followers can read it; only the presenter can change it. A follower's own changes while they branch stay in their browser.

In a handout

A link contains the notebook itself, so nothing is stored on our side. "Make my copy" keeps the copy in the student's own browser.

Limits

Code that runs on a student's computer cannot be made tamper-proof. PyPad's rules stop mistakes and casual changes, not a determined person, so for assessment that matters a marker should re-check the work.