Built so faculty can use AI without losing student data.

ShroudFox exists because the alternative was banning ChatGPT, and bans don't work. Faculty will use AI. The question is whether student names go with it.

Our mission is narrow on purpose: be the privacy gateway K-12 schools trust between their staff and mainstream AI. We don't build an AI model. We don't compete with OpenAI, Anthropic, or Google. We build the one piece those three don't: the architecture where the student's name leaves the device only after it has stopped being a student's name.

We're a small team, deliberately. The founder is a school technology leader who built ShroudFox first for their own faculty and realized every district has the same problem. We say "we" in the plural ambitiously — for now it is mostly one person on evenings and weekends, plus the AI tools we ourselves want to make safe to use. (This paragraph will be replaced with the founder's real bio at launch.)

We tell districts in audit. We don't fabricate testimonials. We write our security claims with the same standard of honesty we'd want from a vendor handling our own children's data. If that means we lose a deal occasionally because we won't claim a SOC 2 Type II report we don't yet have, fine.

Tokens travel. Names stay.