Student and School Privacy Policy

This policy is for schools, districts, teachers, parents and students. It covers only the education service: class logins, student accounts, teacher accounts, lesson projects, and the pages for classes, teachers and lessons. It is written from the code that runs Mokxi. Mokxi is run by Mokxi LLC of Colorado Springs, Colorado. The general privacy notice covers everyone else who uses mokxi.com.

1. What this policy covers

• Student accounts. Any account that has joined a class as a student, including a class login a teacher made from a login card, which has no email address at all.
• Teacher accounts. A teacher’s account, for the classes it runs and the student information in them.
• Lesson projects and class work. The projects students save, the work they hand in, the teacher’s notes back, and lesson progress.
• The class pages. The pages for joining and working in a class (/class), the pages for teachers and schools (/classroom, /teachers), and the lessons (/lessons).

On /classroom, /teachers and /lessons, what happens depends on who is reading. For a student signed in to an account that is in a class, no analytics or advertising tag loads on those pages or on any other page (section 4). Anyone else, such as a teacher looking at plans or a student who has not signed in, reads them as public pages, and the general privacy notice’s rules on measurement apply, as on the rest of mokxi.com. A school that wants no measurement on any of its devices can block the measurement domains listed on the IT setup page. Mokxi works with them blocked.

2. The short version

• The simulator, the CPU cores and the compiler run in the browser. A student’s circuit is never uploaded to be run.
• A student can use the editor and the lessons with no account at all. An account is only needed to save work, join a class and hand in work.
• We collect only what the class needs, and use it only to provide Mokxi to the school. Student data is never sold, never used for advertising, and never used to build a profile of a student for any other purpose.
• There are no ads on Mokxi. No analytics or advertising tag loads on the class pages, on the sign-up that leads into a class, or on any page for an account that is in a class as a student, whatever is chosen on the cookie bar.
• A student in a class is never on our mailing list, never on the public leaderboard, and never shown an invite offer.
• When a teacher closes a class, its roster and submissions are deleted right away. A school can have its students’ data exported or deleted by asking us.

3. What we collect, and why

From a student

That is the whole list. We do not ask for or keep a date of birth, gender, ethnicity, home address, phone number, school ID number, grades from the school’s own systems, location finer than the country and state above, photos, audio or video. A student who signs up through a class join code is not offered our newsletter.

From a teacher

4. No ads, no ad tracking, no selling

• Mokxi shows no ads to anyone.
• We never sell, rent or trade student data or school data.
• No analytics or advertising tag loads on the class pages (/class), on the sign-in page while it carries a class join code, or on any page at all for a signed-in account that is in a class as a student. Our server never reports anything about a class student to an advertising platform either. The same holds for a child under 13 whose account we hold with a parent’s consent.
• On the pages written for students, such as /students, /student-discount, a project embedded in another site (/embed) and this policy, measurement never starts on its own, in any country. It waits until the visitor chooses “Allow cookies”, and a signed-in class student never gets it at all.
• Teacher accounts are adult accounts. When a teacher browses our public pages, the general privacy notice’s measurement rules apply to them as to any adult visitor, and they can opt out at any time. That measurement never includes a roster, a student’s name, a class name, a project or any other student data.

5. No profiling of students

• We do not build a profile of a student for any purpose other than running Mokxi for their school, and we make no automated decisions about a student.
• Learning progress (lessons done, points, level and badges) is shown to the student and their teacher. A student in a class never appears on the public leaderboard and cannot join a weekly league.
• Our activity record keeps only account and class actions for a student in a class, such as signing in or handing in work. How a student uses the editor is recorded only if the teacher turns on usage stats for the class, which is off by default, and then only for that teacher to see.
• Every project a student in a class makes is private: it cannot be opened by link or put in the public gallery.

6. Who can see it

• The teacher of a class sees its roster (names, email addresses and when each student joined), everything handed in to it, and can open, but never change, a project owned by a student in the class.
• Classmates see each other’s names on the class page, never each other’s email addresses or work.
• In a live collaboration room, the people in the room see each other’s names or handles and each other’s edits.
• A project the student made public before October 1, 2026 can still be seen by anyone who has its link, with no name, handle, picture or account id on it, and the student can make it private at any time.
• Mokxi staff see account data only to support the school or keep the service running, and only the owner and named staff have that access.

7. Who handles it for us

These companies process data so that Mokxi can work. Each is bound by a contract with us that limits its use to running our service and does not let it sell the data. We tell schools with a signed agreement before we add one.

For teacher and school accounts only:

Mokxi AI, Mokxi’s helper in the editor, is off for every class until its teacher turns it on, and always off for younger children and class logins. With it on, a student’s question and the project text with it (the circuit, the open code, serial output and compiler messages, never the student’s name, email or school) pass through our Worker to Anthropic, which runs the model; we keep no questions or answers, only counts. "What is sent" in the panel shows the exact text before anything leaves.

8. How long we keep it, and deleting it

• A student’s own account and projects stay until the account is closed, by the student from their account page or at the school’s request.
• When a teacher closes a class, the class, its roster, its assignments and every submission, note and check result are deleted at once. The students keep their own projects in their own accounts.
• When a student leaves a class, or the teacher removes them, their membership and their submissions to that class are deleted at once.
• When an account is closed, its profile, projects, learning progress, class memberships, submissions, Mokxi AI counts are deleted at once, and the copies in our backups are gone within 30 days.
• A live collaboration room keeps its own working copy of the circuit, a short log of recent edits and the raised hands with Cloudflare. That copy is deleted automatically when the project is deleted or its owner’s account is closed, including on a school’s deletion request.
• A support conversation is kept for two years from its last message, or deleted sooner when the account it came from is closed. Request logs are kept a short time by Cloudflare.
• Each entry in the account activity record is deleted after 13 months, and all of it when the account is closed.
• Billing records for a teacher or a school are kept as long as tax law requires.
• Where a signed agreement sets a different schedule, the agreement wins.

9. The laws we work under

FERPA: Mokxi as a school official

When a school uses Mokxi, we act as a school official with a legitimate educational interest, under the direct control of the school for the use and upkeep of student records. The student data stays the school’s. We use it only to provide Mokxi to the school, we do not disclose it except to the processors above or where the law compels us, and if we are compelled we tell the school first unless the order forbids it.

COPPA: children under 13

A child under 13 may use a Mokxi account only with consent. Through school, the school gives that consent on the parents’ behalf, for the school’s educational purpose and no other, under its Student Data Privacy Agreement with us or, until one is signed, under our terms and this policy. The teacher who sets up the class acts for the school in doing so. Outside school, a parent or guardian gives it by writing to us from their own email address, and we confirm it with them before the account is used. If we learn that a child under 13 has an account without consent, we delete it.

SOPIPA and state student privacy laws

California’s Student Online Personal Information Protection Act (SOPIPA), and the state laws modeled on it, forbid an education service from using student data for targeted advertising, building a profile of a student for anything but school purposes, selling student data, or sharing it beyond what the service needs. Mokxi does none of those things, keeps student data secure (section 11), and deletes it when the school asks. The same commitments are how we meet other state student privacy laws, such as Colorado’s Student Data Transparency and Security Act. We will sign a school’s or district’s data privacy agreement, including the SDPC National Data Privacy Agreement and the state agreements based on it (section 12).

10. Requests from schools, parents and students

Email privacy@mokxi.com with the subject “Student data request”, or use the support page. A person answers, and we act on a request within 30 days.

• Export. A teacher can download a class roster as a spreadsheet from the class page at any time, and a student can export any project as a file from the editor. For everything we hold on a school’s students, we send the school a file of it.
• Deletion. A teacher can remove a student from a class or close the class, which deletes the class data at once. For a full deletion, send us the students’ email addresses (or the class) and we delete their accounts and everything in them, then confirm in writing.
• Parents. A parent can ask to see what we hold about their child, have it corrected or deleted, or stop any further collection. For a child using Mokxi through school, we pass that request to the school, which decides, unless the school has asked us to answer parents directly.
• Students and education records. A parent’s or eligible student’s request to review or correct education records goes to the school, and we help the school answer it.

11. Security and breach notification

What is actually in place today:

• Every connection is encrypted (HTTPS).
• Passwords are salted and hashed with PBKDF2-SHA256 and never stored or logged in the clear. A student who signs in with their school Google account has no Mokxi password at all.
• Sessions are signed cookies that scripts cannot read, sent only over HTTPS, and they expire after 30 days.
• Sign-in and verification links are single use, expire on their own, and are stored only as hashes.
• Any account can turn on two-factor sign-in with an authenticator app.
• Every rule about who may see what is checked on our server, not in the browser: a class you are not in does not exist to you, a student sees only their own work, and a teacher can read but not change a student’s project.
• Changes are only accepted from mokxi.com itself, our pages refuse to be framed by other sites, and a bot check and rate limits guard sign-up and sign-in.
• Card numbers never reach our systems, and our keys live in Cloudflare’s secret store, not in our code.

If student data is ever exposed, we tell the affected schools without undue delay, and within 72 hours of confirming it, with what happened, what data was involved and what we are doing about it, so the school can tell families. How to report a security problem is on the security page.

12. Data privacy agreements

We will sign the Student Data Privacy Consortium’s National Data Privacy Agreement (NDPA), or your state’s version of it, with any school or district that asks, and we answer security questionnaires. Once a school has signed one with us, it governs that school’s student data and wins over this policy where the two differ. To start one, email privacy@mokxi.com from a school address. Your IT team will find the domains to allow, the Google Workspace setting for students under 18, and an email to forward on the IT setup page.

13. Changes

When this policy changes, the date at the top changes. We tell schools with a signed agreement before a change that affects how student data is used, and we do not start using student data in a new way without the school’s agreement.

14. Contact

Mokxi LLC. Email privacy@mokxi.com, call (719) 246-1726, or use the support page. A person answers.