Privacy

Sudo Learn is sold to institutions, not to individuals. Accounts exist because a department head or a professor at your institution invited you. This page covers students, professors and department heads using Sudo Code and the Sudo Learn dashboards, and visitors to this website.

While a student is signed in and working in Sudo Code, the IDE sends us:

• terminal commands that are run, and the exit code each one returned;
• file save events — the file extension, and the size and shape of the change, so that edits can be counted and compared over time;
• git activity: commit messages, commit times, and the repository the commit belongs to;
• prompts sent to the AI mentor and the replies it gives;
• session timing: when the editor is being worked in and when it is idle, which is what deep-work minutes and active hours are counted from;
• sign-in times, and which courses the student is enrolled in.

If a student connects a GitHub account, we also read public repository and commit activity for that account. That connection is optional and the student can remove it themselves at any time.

• No keystroke logging. We record that a file was saved and how much changed, not what was typed.
• No screen recording, screenshots or live view of a student's screen.
• No camera, no microphone.
• No browser history, and no activity in other applications.
• No files from outside the project the student has open in the editor.
• No location tracking beyond the coarse network information any web request carries.

The signals above are turned into a fixed set of metrics: error-to-success ratio, mean time to recovery, thrashing index, deep-work minutes, net active engineering time, AI-generated share, authenticity score and a composite ready-to-deploy index, together with a level (L1 to L3) and a status (On Track, At Risk or Flagged). Where a student has no telemetry, the metric is empty. We do not fill gaps with estimates.

• The student — their own record, in full.
• Their professors — but only students enrolled in the courses that professor teaches. A professor cannot open a student they do not teach.
• Their department head — every student, professor and course in that institution, and nothing belonging to any other institution.
• Sudo Learn operators — a small number of our staff, for support, billing and fixing faults. Access is logged, and it is not used for anything else.

We do not sell data, and we do not share a student's record with employers, recruiters or anyone outside their institution. If a student ever chooses to share their record with a recruiter, that will be their action, from their own account.

Students can turn off appearing on institution leaderboards in their own settings. Professors and the department head still see the record for the students they are responsible for, because that is the purpose the institution licensed the product for.

Data is stored on Amazon Web Services in the Mumbai region (ap-south-1). We keep a student's record while their institution's license is active, because the point of the record is that it spans courses and years.

When a license ends, the institution can ask us for an export of its data. We then delete it when the institution asks us to, or when its license ends and is not renewed. An individual student can ask their department head, or us directly, to have their record deleted before that.

We send invitation emails, password resets, and nudges — a short message a professor writes to a student in one of their courses. Nudges are logged, so a student can always ask who sent one and why. We do not send marketing email to students.

Separately from the product, this marketing site uses Google Analytics and PostHog to count page visits, and the pilot request form submits the name, email, phone number, institution and message you type into it to HubSpot, our CRM, so that we can reply. Those details are used to arrange a pilot and nothing else.

Questions, corrections, exports and deletion requests: privacy@sudolearn.in. we reply as quickly as we can. If you are a student and you would rather not write to us directly, your department head can raise it on your behalf.