Open the editorEditor
Legal

Privacy

This is what Mokxi collects about you, why, who else sees it and how to get it deleted.

Last updated November 10, 2026.

Using Mokxi in a school? Read the Student and School Privacy Policy. It covers class logins, student and teacher accounts, lesson projects and the class pages.

Mokxi is run by Mokxi LLC, of Colorado Springs, Colorado, which is the controller of this information. It is written by the people who wrote the code, from the code. There are no ads on this site. The measurement tools we use to see whether our own ads work are named below. In the European Union and the European Economic Area, the United Kingdom, Switzerland and Brazil, and wherever we cannot tell which country you are in, they stay off until you allow them. In every other country, the United States included, they are on unless you opt out, with the "Do Not Sell or Share My Personal Information" link at the foot of every page or your browser's Global Privacy Control, and they never load by default on children's or student pages (section 7). We never sell your information for money.

1. What the simulator sends out

Nothing. The simulation kernel, the CPU cores, every part and the compiler run in your browser. A circuit is never uploaded to be simulated or built. The only time a project leaves your machine is when you ask for it to: saving it to your account, sharing a link, opening a collaboration room, submitting it to a class, asking Mokxi AI a question, or pressing Explain in the Mokxi AI check.

Mokxi AI, Mokxi’s helper in the editor and the corner of every page, answers a question only when you send one. Each question carries your circuit (the parts and how they are wired), the open code, recent serial output, compiler messages, live readings, the top help articles for the question and the last six messages of the chat (on a site page, the page you are on in place of the project), and "What is sent" in its menu shows exactly that text. It goes through our Worker to Anthropic, which runs the model; your name, email, account, school and address are never sent. We keep no questions or answers: your browser keeps your last ten chats for seven days, and Clear or signing out removes them. We keep counts only (how many questions, and what they cost, by plan and model), under a code that cannot be turned back into your account or address. When our AI costs for the day run far over, a question can instead be answered by a small model on Cloudflare Workers AI, on Cloudflare's own network, from the same text. Mokxi AI is off for younger children and class logins, and for a class student unless the teacher turns it on. Bring-your-own-key Ask is gone: keys saved for it on accounts are deleted, and a key kept in your browser is deleted the first time you open Mokxi AI.

The Mokxi AI check (the Circuit Doctor) looks over your wiring and code in your browser and sends nothing. Its Explain button is the one exception, and only when you press it: it asks Mokxi AI about the findings, as described above, and uses one of your questions for the day.

2. Using Mokxi with no account

You can use the editor, the lessons and every page signed out. Your browser keeps a few things locally so they survive a reload: your theme, the parts you placed recently, your learning progress and badges, and the id of any support conversation you start (reading it needs you to be signed in with the address you wrote from). None of that reaches us until you sign in and ask to keep it on your account. Our host, Cloudflare, keeps ordinary request logs (the address your connection came from, the page asked for, the browser) for a short time for security and to keep the service up. Whatever you choose about analytics, our server adds each page you open to a daily tally so we know roughly how many people visit: the number of pages opened that day, how many visits started, the website or campaign name that sent a visit, the kind of page it started on (the home page or a simulator page, say, never the full address), the country Cloudflare reports, and how many accounts were made that day, grouped the same way. It uses no cookie and stores no address, browser details, page address or identifier, so nothing in it can tell one visitor from another or be linked back to you. Class pages and students in a class are never counted. If the compiler itself crashes while building code (it fell over, not your code being wrong), the page tells our server which board it was and that the compiler crashed, signed in or not and for every account: no code, no message, no account id and nothing else, so we see crashes nobody reports. To show us how many people are on the site right now, an open tab also tells our server about once a minute whether it is on the editor or another page and whether you are signed in, along with a random code your browser makes for that tab and forgets when the tab closes. Signed-in accounts are counted this way without storing which account; signed-out visitors are counted only after they allow cookies (where tags are on by default, unless they opt out or send a Global Privacy Control signal; section 7). Our server keeps a tab's code for five minutes at most and keeps only the totals, one number per minute, for about a day. Students in a class, children under 13 and class pages are never counted. We count page views with Sporetag (sporetag.com), which sets no cookie and stores nothing in your browser, so it runs without asking: it is told the page address, the address of the page that sent you, your screen width, how long the page was open and any ad click id in the address, and, like any website, sees your connection's address. It does not run if you choose Necessary only, opt out, or your browser sends a Global Privacy Control signal. If you allow cookies (where tags are on by default, unless you opt out), Sporetag also remembers which link or ad brought you, so we can tell which ones work: it keeps a random visitor id and any ad click ids from the address (such as gclid or fbclid) for 90 days in this site's cookies and storage, and reads the Meta Pixel's _fbp and _fbc cookies. With cookies allowed, while you are signed in, Sporetag (our analytics) is also given your account's email address, name and account id, to link your visits to your account, and when you make an account our server reports the sign-up to Sporetag with your account's email address and account id, under the same consent as the server-side copies below, and never for a student in a class or a child under 13. If you allow cookies, we also use Google Analytics to count page views; until you do, it does not load at all and nothing is sent to Google. Where tags are on by default, as section 7 explains, Google Analytics and the tags below are on unless you opt out. We also use the measurement tag of each place we advertise, to tell whether one of our ads brought anyone here: Google Ads conversion tracking when we advertise on Google, the Meta Pixel when we advertise on Facebook and Instagram, the Pinterest Tag when we advertise on Pinterest, and the LinkedIn Insight Tag when we advertise on LinkedIn. The ad platforms in use now: Google Ads, Meta and Pinterest. A platform that is not on that list receives nothing from Mokxi, from your browser or from our server. The tags in use are told about a page view, a press on a sign-up button, a new account (by which method), a checkout, the start of a free trial, a school quote request and a paid plan with its price. With a new account and a paid plan, Google Ads and Pinterest, when in use, also receive your email address as a hash (a one-way code made in your browser, never the address itself) so they can match the conversion to an ad. For a new account and a completed paid checkout, our server also sends each of Meta, Pinterest and LinkedIn that is in use a server-side copy of the same event, with the same event id, so each counts it once; for the start of a free trial and a school quote request it sends Meta the same kind of copy. A new account made with an email link is counted when the link is first followed, not when it is asked for. Those server-side copies are sent only for an account whose browser allowed cookies when it did the thing counted (where tags are on by default: had not opted out, sent no Global Privacy Control signal, and was not on a children's or student page), never for a student in a class or a child under 13, and they name you only by hashed values. After you allow cookies, while you are signed in, the Meta Pixel is also given the same hashed values (Meta's advanced matching). Hashed means scrambled one way: the platform can compare it with what it already holds but cannot turn it back into the original. The hashed values are your email address, your account id and your approximate location (the country, region, city and, in the United States, the ZIP code that our host, Cloudflare, places your connection in; we do not store the city or ZIP code). They are shared with Meta and Pinterest (LinkedIn gets the hashed email address only) to measure our ads, never for a student in a class or a child under 13. We have no phone number for you and never send one. The page address sent with a server-side copy never includes anything after a question mark. Apart from Sporetag above, none of these tags loads until you choose Allow cookies (where tags are on by default, unless you opt out, and never by default on a children's or student page), none of them is ever used for a student in a class or for a child under 13 whose account we hold with a parent's consent, and none loads on a page whose address is a private link (a password reset, an unsubscribe or support link, a school quote, a live room). There is no other third-party tracker.

3. What an account stores

  • Sign-in: the id your provider gives us and the provider's name if you sign in with GitHub, Google, Microsoft or Apple, or your email address and a salted hash of your password if you sign in by email. Never the password itself.
  • Devices you sign in from: the kind of browser and system (such as "Safari on iOS"), when it first and last signed in, and a scrambled code made from those two words so we can tell it again. When you sign in from one we have not seen on your account, we email you its kind, the time, your connection's IP address and the approximate place it maps to, but we do not keep the IP address or the place. You can see the list on the Security page. Not kept for students in a class or children under 13, who get no such email.
  • Where you signed up from: we record the country (and US state) you sign up from, from your connection, to see where Mokxi is used. Never your IP address or city.
  • What brought you, if you allowed cookies, or, where tags are on by default (section 7), did not opt out: the campaign fields on the first link that brought your browser here (such as utm_source and utm_campaign), the ad click id on it if there was one (Google's gclid, gbraid or wbraid, Meta's fbclid or Microsoft's msclkid), the page you landed on and the site that linked to it. We keep it with your account, for our own use only, to see which ads and pages bring people who stay; it is not sent to Google or anyone else, except that a Meta click id (fbclid) from the last 90 days is sent back to Meta, in Meta's own _fbc format, with the server-side copies described in section 2, so Meta can tell which of its ads it was. We also note that you allowed cookies when you signed up, with the random event id of your sign-up, which is the only part shared with the ad platforms so they count the sign-up once. With Necessary only, none of it is kept, and it is never kept for a student in a class: joining a class as a student deletes it.
  • Profile: your name, email address and avatar as your provider gave them, or a photo you upload yourself instead, and whatever you fill in on your account page: a handle, a short bio, links to your own pages, and whether your learning progress is shown publicly.
  • Profile photo, only if you upload one: your browser crops it and redraws it as a 512 by 512 picture before it is sent, which leaves out the camera details and location a photo file can carry, and our server checks again that none are left. It is stored with our host, Cloudflare, shown wherever your avatar shows, and deleted when you remove it, upload another or close the account; your provider's picture then shows again if it gave us one. Students in a class and children under 13 cannot upload one.
  • Projects: the circuits and code you save, their saved versions, whether each is public, and the projects you favorite.
  • Learning: which lessons you have done, your points, level, streak, daily quests and badges, a record of what earned each point (a short name for the action, such as a board you ran for the first time, and the day), whether you are on the leaderboards and whether you joined a weekly league. You are on the leaderboards unless you untick the box "Show me on the public leaderboard" on /leaderboard or the learn page; they show a name or handle, your level, your XP and the streak you are on, and never your email. Untick it and you are taken off at once and stay off. Students in a class and children under 13 are never shown.
  • Classes: for a teacher, the classes they made, the join codes, the roster of accounts that joined, the assignments and the submissions. For a student, which classes they are in and what they submitted.
  • Plan and billing: which plan you are on, and the customer and subscription ids Stripe gives us. Stripe holds your card details; we never see the card number.
  • Student discount: the school email address you verified with, when it was verified, and the outcome.
  • Invites: your invite link, which accounts signed up through it or which account invited you, whether that sign-up led to a reward, and the Pro days it earned. We never ask for or store the email addresses, phone numbers or contacts of people you invite, and we never email them on your behalf: the link is the whole invite. Accounts in a class as a student take no part.
  • Shared links: if you sign up after opening a project somebody shared, we note with your account that it came from a shared link (or an embed), how the link was handed on (copied, the phone's share sheet, a QR code) and which project it was. It travels in the sign-up page's own address, with no cookie and nothing stored in your browser, and we use it only to count how many people sharing brings, for our own use; it is not sent to anyone else. We also count each opening of a shared link and each press of its remix button, with no account, address or cookie in the count. None of it is kept for a student in a class, and joining a class as a student deletes it.
  • Activity: a dated record of what your account does in Mokxi, kept in our own database so we can see which features people use, where they get stuck and what to build next. It lists actions, not content: that you signed up, signed in or out, confirmed your email, turned two-factor on or off, created, saved, shared or deleted a project, hit a plan limit, started a checkout or changed a plan, made or joined a class, handed in or reviewed work, made an API token, or sent a question to Mokxi AI (that it was Mokxi AI, nothing of the question), or gave one of its answers a thumb up or down (the thumb, the kind of question and the model, nothing of the answer), or opened the Mokxi AI check (which kind of problem it showed and which fix you applied, as a short rule name). In the editor and on the site it also lists that you opened the editor, pressed Run, whether a build worked or failed (the kind of error, how long the build took, and when the error is a call the board does not have, that call's name if it is one of the Arduino, ESP32 or Pico names on a fixed list we keep, so we learn what our boards are missing; a name of your own is never sent), the compiler's first error line and its line number, an error box the editor showed you, and a page that crashed, each with its error message cut down to 160 characters before it leaves your browser: file names lose their folders, and quoted text (any string in your code), web addresses, email addresses and runs of seven or more digits are taken out, so we can fix what went wrong; which board, parts, examples and guides you picked, which pages you opened, what you exported from the share sheet, settings you switched, and short words you typed into the parts search. Each entry holds your account id, the action, the time and a few short labels such as a board or part name. It never holds your code, your circuits, your messages, your keys, your IP address or your email address. It is not shared with anyone and not used for advertising.

4. Collaboration rooms

When you open a room on a project, the edits and cursors of everyone in it pass through our Worker so they reach each other. The room keeps the project's current state in memory while it is open and writes it to your saved project. We do not keep a log of who edited what once the room is closed. People in a room see each other's names or handles.

5. Product email and the newsletter

Mokxi sends three lists of email. Account and billing notices (your trial or plan starting, ending or ended, receipts and security mail) go to every account with an email address and cannot be turned off, because they are about your account; closing the account stops them. Tips and Offers are marketing. Where the law allows it, including the United States, an account with a confirmed email address gets them unless it unsubscribes: what shipped, tips as you build, new plans and the odd discount, and the other lists on your email settings. In the European Union and EEA, the United Kingdom, Switzerland and Canada, and where we cannot tell the country, we send them only if you check the box when you sign up or turn them on in Notifications. The Circuit challenges list is never on by default; it comes only if you ask for it. Every marketing email has a one-click unsubscribe and a link to a page that lists each list with a switch, and you can also change them anytime from Notifications on your account page. Your address is confirmed by your sign-in provider or by a link we sent you, so there is no separate confirmation email. Student accounts in a class and accounts of children under 13 never get it, and an address that unsubscribed or bounced is not added again. If you subscribe from the newsletter form without an account, you are subscribed right away and get a welcome email with a one-click unsubscribe, so if somebody else typed your address you can leave at once. We store your email address, which lists you are on and whether you confirmed. Every marketing email carries an unsubscribe link, and the unsubscribe page lets you drop one list or all of them. Marketing and product emails from Mokxi record whether they were opened and which link was clicked, to learn which emails help. Sign-in, receipts and support replies are never tracked. That record is kept in our own database, by a small image and by links that pass through mokxi.com on their way, and is never shared; student accounts in a class and children under 13 never get these emails, so they are never tracked. The list is ours; the sending is done through Resend.

6. Support

When you write to us through the help panel or the support page, we store your message, the email address you gave and our replies, so that you can read the conversation later on any page of the site. Replies come to you by email, sent through Resend. A support thread is tied to a token in your browser, not to an account, so a signed-out person can use it.

When you press Report a problem in the editor, or Tell us beside an error, the sheet shows you everything it would send before anything leaves your browser, and nothing is sent until you press Send. It can include a technical log: the last build output, the last 200 or so lines of the serial monitor, recent errors from the page's console, the board and the types of parts on the canvas (not their settings), your browser, system and screen size, the version of Mokxi, and the address of the page without anything after the ? or #. Email addresses, cookies and tokens are taken out of it in your browser and again on our server, and you can edit or untick the log. If you are signed in with a saved project, you can also include a copy of it, which only we can open (the owner and the support assistant, with every opening recorded and shown on your ticket); it is deleted when the ticket is, and you can stop sharing it sooner. For a student in a class, and for a child under 13 whose account we hold with consent, the log and the project copy start unticked and are left out unless the student ticks them. We keep a report like any support conversation, for two years from the last message.

7. Cookies

Two necessary cookies are ours and appear only when you use them: a signed session cookie that says which account you are signed in to, and a short-lived cookie that remembers which page to come back to after sign-in. If you arrive through an invite link, another cookie remembers the invite code for up to 30 days, until you sign up, so the invite can be counted for both of you. A cookie named mokxi_consent remembers your choice on the analytics bar. Analytics that uses cookies stays off until you choose Allow cookies, except where tags are on by default (section 7). Once it is on, a first-party cookie named mokxi_src keeps the campaign fields and ad click id of the first link that brought you, for up to 90 days, so an account you make can record what brought you; Google Analytics sets cookies named _ga and _ga_ followed by an id; Sporetag sets cookies whose names start with _st_ (a random visitor id and the ad click ids that brought you, for up to 90 days, with a copy in this site's local storage); and each ad platform in use now (listed in section 2, and only those) may set its own: Google Ads conversion tracking may set _gcl_au and _gcl_aw to keep the Google ad click that brought you; the Meta Pixel may set _fbp and _fbc (if you arrived from a Meta ad before choosing, your browser holds its click id, fbclid, in this tab's session storage only, sends it nowhere, and writes it as _fbc when you choose Allow cookies, or deletes it when you choose Necessary only); the Pinterest Tag may set _pin_unauth and _epik; and the LinkedIn Insight Tag may set li_fat_id and other LinkedIn cookies. Right after you sign up, a cookie named mokxi_signup_eid holds your sign-up's random event id for up to 15 minutes, until the page reads and deletes it; after a sign-up by email link, a cookie named mokxi_signup_new tells the page you land on that the account is new, for up to 15 minutes, until the page reads and deletes it. When you sign up or buy a plan, the Meta values, the Pinterest _epik value and the LinkedIn li_fat_id value can be sent from our server, to those of Meta, Pinterest and LinkedIn in use, with a hashed email, account id and approximate location, the browser name and connection address so each can match the sign-up or purchase to an ad without counting it twice. You can decline with Necessary only, and you can change your choice by clearing this site's data in your browser. None of these analytics or advertising tags is loaded 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, and none of the hashed values above is ever sent for a child under 13.

In every country except the ones that ask first (the European Union and EEA, the United Kingdom, Switzerland and Brazil, and where we cannot tell your country), the choice works the other way around, in the United States and everywhere else. When you first visit, the analytics and advertising tags above are already on, and a small notice at the foot of the page says so, with an Opt out link and a link to this notice. The notice shows once. After that, the link "Do Not Sell or Share My Personal Information" at the foot of every page opens the choice again, at any time. Opting out stops the tags on the page you are on, deletes the ad cookies this site set in your browser (_fbp, _fbc, _ga and _ga_ cookies, _gcl_ cookies, the Pinterest and LinkedIn cookies set under our name, Sporetag's _st_ cookies, and mokxi_src), and is remembered in the mokxi_consent cookie, so no tag loads on later pages and our server sends none of the server-side copies described in section 2. If you are signed in, the opt-out is also kept with your account, so a purchase you had already started is not reported either. If your browser sends the Global Privacy Control signal, we treat it as that same opt-out without you doing anything, and the notice tells you the signal was honored. Children's and student pages never load these tags by default, in the United States or anywhere else: the student pages at /students, the student discount at /student-discount, the class pages and class join pages, projects embedded in other sites, and the student data privacy notice. The student plan is treated the same way wherever you buy it: its checkout and purchase are measured only if you chose Allow cookies. On those pages the tags load only if you chose Allow cookies, and they never load for a student in a class, a child under 13 whose account we hold with a parent's consent, or a page whose address is a private link. In the countries that ask first, nothing changes: the tags stay off until you choose Allow cookies.

8. Why we use it

To run Mokxi, sign you in, save and share your work, run your classes, bill you for a plan you chose, answer you when you write, send you product email you can unsubscribe from and what you subscribed to, keep the service up and keep it safe. The activity record in section 3 is for deciding what to fix and build next, and it stays with us. With your analytics choice, we also measure and improve Mokxi's own ads. We do not show third-party ads on Mokxi, and we do not sell or rent your information.

9. Who else sees it

The companies below process some of your information so that Mokxi can work. Each one is bound by its own privacy terms and by a contract with us that limits its use to running our service.

  • Cloudflare hosts the site, the Worker, the database and the file storage. Everything above is stored there.
  • Stripe handles payments. Your card details go to Stripe directly and we receive the plan, the customer id and the subscription id.
  • Resend sends our email: sign-in links, receipts, support replies and the newsletter.
  • GitHub and Google, only if you choose to sign in with them, tell us your id, name, email address and avatar. Microsoft, only if you choose to sign in with it, tells us your id, name and email address. Apple, only if you choose to sign in with it, tells us your id and email address, and your name the first time; if you choose Hide My Email, the address is a private one Apple forwards to you, and we never use it to join your sign-in to another account.
  • Cloudflare Workers AI answers a question to Mokxi AI only when our AI costs for the day run far over, from the text described in section 1. It runs on Cloudflare's own network and is not used to train models.
  • Anthropic, PBC runs the models behind Mokxi AI, Mokxi’s helper. It receives a question and the project text with it, as described in section 1, only when you send one, and never your name, email address or account (only a code that cannot be turned back into it). Under its commercial terms it does not train its models on them and keeps them only for a limited time for trust and safety.
  • The ad platforms in use now: Google Ads, Meta and Pinterest. A platform that is not on that list receives nothing from Mokxi, from your browser or from our server.
  • Sporetag (sporetag.com) counts page views for us without cookies, unless you choose Necessary only, opt out or send Global Privacy Control, and, only if you allow cookies, remembers for 90 days which link or ad brought you: it receives the page address, the address of the page that sent you, your screen width, how long the page was open and any ad click id in the address, sets no cookie and stores nothing in your browser.
  • Google, only after you allow cookies, counts page views for us through Google Analytics and, when we advertise on Google, tells us which Google ads led to a sign-up or a paid plan through Google Ads conversion tracking. A sign-up and a paid plan are reported with your email address hashed in your browser (Google's Enhanced Conversions), which Google uses only to match them to an ad, and a paid plan also with its price and an order number. Google Tag Manager, which we also use, loads only after you allow cookies too. Google processes those under its own terms; you can opt out of Analytics with the browser add-on at tools.google.com/dlpage/gaoptout and limit ads at adssettings.google.com.
  • Meta (Facebook and Instagram), when we advertise there and only after you allow cookies, receives page events from the Meta Pixel (a page view, a new account, a checkout, the start of a free trial, a school quote request, a paid plan) and a server-side copy of the new account, the start of a free trial, a school quote request and a completed paid checkout, for an account whose browser allowed cookies. While you are signed in, the Pixel and the server reports include your hashed email address, hashed account id and hashed approximate location (country, region, city and US ZIP code), Meta cookie values (_fbp, and _fbc, the Meta ad click) when present, and the server reports also the browser name and connection address and, for a purchase, the value and plan. None of it is sent for a student in a class or a child under 13. It never includes a circuit, project, class name or student data. Meta processes it under its own terms; you can limit it in your Facebook ad settings.
  • Pinterest, when we advertise there and only after you allow cookies, receives events from the Pinterest Tag (a page visit, a new account, a paid plan with its price and an order number), with your email address hashed in your browser while you are signed in (Pinterest's Enhanced Match), and a server-side copy of the new account and of a completed paid checkout, for an account whose browser allowed cookies. The server reports include hashed email, account id and approximate location (country, region, city and US ZIP code), the Pinterest cookie value when present, browser name and connection address, and for a purchase the value and plan. It never includes a circuit, project, class name or student data. Pinterest processes it under its own terms; you can limit it in your Pinterest privacy and data settings.
  • LinkedIn, when we advertise there and only after you allow cookies, receives events from the LinkedIn Insight Tag (a page view, a new account and a paid plan) so we can tell whether our LinkedIn ads reach teachers and schools, and a server-side copy of the new account and of a paid plan, for an account whose browser allowed cookies, with a hashed email address, the LinkedIn li_fat_id cookie value when present, and for a purchase its value. No circuit, project, class name or student data goes to it. LinkedIn processes it under its own terms; you can limit it in your LinkedIn ad settings.
  • None of the analytics or advertising tags above is ever loaded for a student in a class, on a class page or on the sign-up that leads into a class, whatever was chosen on the cookie bar.
  • Where tags are on by default (section 7), "only after you allow cookies" above means unless you opt out or your browser sends Global Privacy Control, and never by default on a children's or student page.

Beyond that, we disclose information only when the law requires it, to protect someone's safety, or to protect Mokxi from attack or fraud. If Mokxi is ever sold or merged, your information goes with it under this same notice, and we tell you first.

10. What other people can see

A project in the gallery is visible to everyone, with your handle or name on it. Every new project starts public, on every plan: it is in the gallery and on your profile page, with your handle or name on it, and anyone can find it. On a paid plan you can then make it private or link-only. A project that was already private or link-only stays that way, whatever your plan. A project of a student in a class is always private, and a project of a child under 13 outside a class is always private too: it cannot be made public or opened by link, and one that was public before is closed to everyone else; neither costs anything. Your profile page is public if you make it public. The public leaderboards at /leaderboard show your name or handle, level, XP and current streak unless you untick the box to leave them, and never show a student in a class or a child under 13. A weekly league shows the others in it a nickname made up for you from two words and a number, your level and your XP that week, only if you join it; a student in a class cannot join one. A project you submit to a class is visible to that class's teacher. Everything else is private to you and to the people you share a link with.

11. Children and schools

Mokxi is not directed at children under 13, and we do not knowingly let a child under 13 make an account on their own. A child under 13 may have an account with consent: through school, the school gives it on the parents' behalf under its Student Data Privacy Agreement with us (or, until one is signed, through the teacher who sets up the class for the school) and stays in charge of the student's information; outside school, the child presses "ask a parent" under the sign-up form and gives only a first name and a parent's email address, and the parent approves from the email we send (a parent may also write to us, and we confirm it with them first). Until the parent approves we keep only that first name and address, and we delete both if the link is not used within 7 days. Once the parent approves, we keep their address and the time they approved as our record of consent, and use the address for nothing else: no newsletter, no product email. It is also how the child gets back in on another device, by asking again. For such a child we collect only what the service needs, we never use it for advertising or anything commercial, no analytics or advertising tag loads for them, their name is never in the gallery, on the leaderboards or on a shared project, nobody is invited to remix their projects, the activity record keeps only account, class and billing actions (never how they use the editor), the child never gets product email or the newsletter, and the school or a parent can see it or have it deleted by asking us. If you believe a child has given us information without that consent, tell us and we delete it. Students in a school class are covered in full by the student data privacy notice at /privacy/students: what we collect, the companies that process it, how long it is kept, and how a school has it exported or deleted.

Kids mode. An account that is not in a class, has no paid plan or card on file, runs no class and is not on our staff can turn on Kids mode, from the welcome question in the editor or from About you on the account page. We do not ask for or keep an age or a birthday; from that question we keep the one word "kid" and nothing else. From then on the account is treated as a child's account in everything this notice says about one, and we keep only the minimal record for it: the activity record keeps account, class and billing actions (such as the account being made and signing in and out), and what it already held about how the editor was used is deleted; the product email that came with signing up is switched off; and a GitHub connection, if the account had one, is revoked and removed. Kids mode keeps projects private: none can be made public or opened by link, and one that was public before is closed to everyone else. It is shown no prices, plans or offers. Kids mode is not consent and does not replace it: a child under 13 still needs a school's or a parent's consent, as described above, to have an account. Kids mode cannot be turned off from inside the account. A parent or guardian can write to us to have it turned off or to have the account deleted.

12. How long we keep it

For as long as your account exists. An account whose email was never confirmed and that has no saved work is deleted after 7 days. The activity record is the exception: each entry is deleted after 13 months. When you close your account from your account page, your profile, projects, learning progress, class memberships, referrals, Mokxi AI counts and activity record are deleted right away, and so are the support conversations you started from the account or from its confirmed email address; a report you made about a project stays, so we can act on it, but no longer names you. The copies in our backups go within 30 days. Billing records are kept for as long as tax law requires. Any other support conversation is kept for two years from the last message. A closed class's roster and submissions are deleted when it closes. A newsletter address is removed when you unsubscribe, apart from a note that says not to send to it again.

13. Your rights

Wherever you live, you can ask us what we hold about you, have it corrected, have it deleted, get a copy of it, or object to a use of it. Most of it you can see and change on your account page, any project can be exported as a file, and Download my data on your account page gives you a copy of everything your account holds as one file. For the rest, write to us and we answer within 30 days; we may ask you to prove the account is yours. If you are in the European Economic Area, the United Kingdom or Switzerland, these are your rights under the GDPR and its UK and Swiss equivalents, our legal basis is the contract with you for the service and consent for analytics, and you can complain to your local data protection authority. In Brazil we also measure only after you allow cookies. California and other US state privacy laws may call ad measurement a sale or sharing even though no money changes hands. Choosing Necessary only prevents that measurement, and we do not discriminate against anyone for using that choice or another privacy right.

Do Not Sell or Share My Personal Information

Wherever the tags are on by default, the United States included, you can opt out of that sale or sharing at any time with the "Do Not Sell or Share My Personal Information" link at the foot of every page, or by writing to us. Opting out turns off the analytics and advertising tags, deletes the ad cookies this site set, and stops the server-side copies sent to ad platforms (section 7). We honor the Global Privacy Control signal as a valid opt-out request for the browser that sends it. The tags never load by default on children's or student pages, and never at all for a student in a class or a child under 13 whose account we hold with a parent's consent.

14. Security

Everything travels over TLS. Sessions are signed cookies. Passwords are salted and hashed and never stored in the clear. Card numbers never touch our systems. Secrets live in Cloudflare's secret store, never in our code. No system is perfectly secure, and if we learn that your information has been exposed we tell you and, where the law requires, the authorities, without undue delay. If you think your account has been compromised, tell us right away.

To report a security problem in Mokxi, email security@mokxi.com or see Report a security problem.

15. Where it is stored

We are in the United States and Cloudflare stores the data on its network, which spans many countries. If you are outside the United States, your information is transferred there and handled under this notice; for people in the EEA, the UK and Switzerland the transfer to our processors rests on the standard contractual clauses in their contracts with us.

16. Changes

When this notice changes, the date at the top changes. If a change means we collect something new or use something differently, account holders hear about it by email before it happens.

17. Contact

Questions about any of this go to the support page at /support, by email to privacy@mokxi.com, or by phone on (719) 246-1726. A person answers.

By post:

Mokxi LLC
5142 N Academy Blvd PMB 1021
Colorado Springs, CO 80918
United States