← All news

October 26, 2026 · orangejuiceplz

NibbleCode and Cyber Security

When you build a learning site for kids and teens, keeping it safe is part of the job from day zero. Security has shaped how we've built NibbleCode since the very first line of code, and we want to show you what that looks like.

Meet the people on watch

Brandon Kralich, Cyber Defense and Child Safety Lead. Including writing content for us, Brandon keeps an eye on our defenses and on anything that touches student accounts or privacy. His focus is making sure every feature we ship keeps students safe.

Shiven Kishore, Internal Penetration Tester. Shiven's job is to break into NibbleCode before anyone else can. He attacks our own systems on purpose, hunting for weak spots so we can fix them before they turn into real problems.

Shiven here -- Now, you may note that we said "we". I built those systems! So my job, including being president, is to break the same stuff I made! How fun.

How we protect your account

  • No passwords! You log in with a one-time code sent to your email. Codes expire, only allow a few tries, and are stored scrambled so they can't be read even from our own database.
  • You control your devices. Your account settings show every device you're logged in on, and you can log out of one or all of them at once.
  • Extra locks for our team. Even our admins need a fresh code from their email before they can manage student accounts, and that access shuts off again after a few minutes.

How we keep students safe

  • Learners can't see each other's names or pictures if they're under 13,
  • No private messaging
  • During the pilot program, accounts are invite-only and open to learners 13 and up.
  • The terminal you use in lessons runs in its own box. You get your own little Linux computer with strict limits on memory, time, and what it can affected, separate from other students and from parts of NibbleCode's infrastructure.
  • We're writing a formal youth protection policy that sets clear rules for how adults, volunteers, and students interact on NibbleCode.

AI Disclosure

We use AI tools in some parts of our security work, like helping review code and spotting possible problems faster. AI speeds things up, and a person on our team always reviews what it finds before anything changes.

Getting certified

Checking our own work only goes so far. We're looking into cybersecurity certifications and outside reviews so that someone independent can confirm we're doing this right. We'll share updates here as that moves forward.

Our promise

No website is perfectly secure, and we won't pretend otherwise. What we can promise is that we take this seriously, we keep testing, and we fix problems as fast as we can.

Thanks for reading,

The NibbleCode Team