FERPA-defensible AI for K-12
Stop the leak at the source.
Names, emails, and IEP details get tokenized in the browser — before anything reaches ChatGPT. The AI sees placeholders. We never see the real values.
When the base model misses something
Add your own dictionary. Nothing leaves the browser.
District-specific terms — uncommon surnames, internal codes, building names — always get tokenized. The list lives on the device. We never see it.
Built by a school technology leader who needed this for his own faculty.
- ✓ FERPA, COPPA, CCPA, and state postures in plain English.
- ✓ Signs your state's SDPC/NDPA without redlines.
- ✓ Browser-side code open for inspection.
- ✓ No customer logos yet — we'd rather say that than fake it.
The problem
Your faculty is already pasting student names into ChatGPT.
Every day, regardless of policy. The question isn't how to stop it. It's where the names went.
Teachers switch to personal phones. PII still reaches ChatGPT — just off your network.
PII leaves your network to reach the vendor's tokenizer. Trust them not to log it.
Browser-side. Names never leave the device. Where did they go? Nowhere.
Who it's for
Three audiences, one product.
IT Directors
Hosted web app. No install, no MDM, no SSO project. Verify the architecture in DevTools in 30 seconds.
Superintendents
The leak is architecturally impossible. Even a pasted IEP is tokenized before the request leaves the device.
Teachers
Type like you would into ChatGPT. Scrubbing happens in the background. You do nothing differently.
Trust & compliance
Built for the district procurement checklist.
Honest about what's audited and what's still in-progress.
Verify it yourself
Two minutes. Your own browser.
send to [[EMAIL_1]]"
Watch the wire in DevTools
Tokens go out. Names don't.
Turn off Wi-Fi
Type a name. It still gets tokenized — locally, on the device.
Read the code
A few hundred lines of commented JS, public repo.
Architecture, side-by-side
Follow the PII.
We see tokens. AI sees tokens. A breach of our server reveals tokens.
PII leaves your network to reach the vendor. Trust required.
Faculty open ChatGPT on a personal phone. PII goes anyway.
red = PII present. green = tokens only.
Pricing
Two ways to buy. Same product.
Bring your own AI key, or we manage one for you. District plans start at 5 seats; individuals and small teams use the Individual tier below.
For schools & districts — 5 seat minimum
Use your district's existing OpenAI, Anthropic, or Google account. Starts at $50/mo (5 seats).
Start free trialOne invoice. No upstream vendor setup. Starts at $70/mo (5 seats). Best when you don't already have an AI relationship.
Start free trialFlat monthly rate, no per-seat math. The District plan above starts at 5 seats, so 1–4 users get a better deal here. Max is the busy-season tier (rec letters, report cards) — 20 files per message, unlimited files per month, $1,000/mo bundled AI included. Switch between plans any month; Stripe prorates.
Your faculty will use AI tomorrow.
Decide where the names go.
No setup call. The trial works the moment you create the account.