Shadow adoption
AI-enabled applications can enter the environment outside the normal purchasing process.
K12 Guardrail helps school districts identify AI-enabled tools connected to district accounts, understand what permissions those tools hold, and see where student data exposure deserves attention.
The problem
Teachers and students can authorize third-party applications through district Google or Microsoft accounts. Those connections may never appear on a traditional purchased-software list, even when they hold meaningful permissions.
AI-enabled applications can enter the environment outside the normal purchasing process.
Privacy policies, data processing terms, and AI training language change over time.
Small or shared technology teams may not have time to research every connected application and vendor clause.
The starting point
A plain-language review of which AI-enabled tools are connected to district accounts, what they can reach, what their vendors say about model training, and which governance frameworks may be relevant.
The goal is not to hand the district a generic risk score. It is to create an evidence-backed exposure map that helps district leadership decide what deserves attention first.
A list of the AI-enabled tools that staff or students have authorized through district accounts, including ones that never went through purchasing.
What each tool is allowed to read or change, and how many district accounts have granted it access.
The exact vendor language on model training, cited so your team can see what the finding is based on.
Tools ordered by the sensitivity of the data they can reach, so leadership knows where to look first.
Frameworks that may be implicated by the data a tool can access, such as FERPA, COPPA, and your state's AI requirements, for district counsel or advisors to evaluate.
Specific questions to raise with each vendor where terms are unclear or exposure is significant.
Simple process
Your Google Workspace or Microsoft administrator exports the district's third-party application authorizations. We can walk through the process together on a screen share.
K12 Guardrail reviews the vendor's terms, data processing agreement, privacy policy, and relevant AI language, recording the evidence behind each finding.
You receive a written report and a review session focused on what is exposed, what to address first, and what questions to ask each vendor.
Data minimization
The review is based on application authorization information: application names, permissions, and the number of accounts using them.
Who this is for
K12 Guardrail is being built around the reality that many school districts do not have a dedicated AI governance, privacy, or GRC function. The goal is to give district leaders a clear view of their current exposure without adding another major implementation project.
Free resources
Two guides we keep current for superintendents, technology directors, and school boards working on AI policy and student data privacy.
FERPA, COPPA, PPRA, CIPA, IDEA, the TAKE IT DOWN Act, Michigan's pupil privacy law, and data privacy agreements, with what each means when AI tools are connected.
Read the guideWhere all 50 states and D.C. stand on AI in K–12: which require district AI policies, which have issued guidance, and the deadlines that matter.
See every stateAbout K12 Guardrail
K12 Guardrail helps school districts make AI governance practical. The focus is not on slowing down teachers or blocking useful technology. It is on giving district leaders the visibility and evidence they need to understand what is already connected, where student data may be exposed, and what deserves attention first.
The company is being built specifically for K–12 environments, where technology decisions sit at the intersection of instruction, student privacy, vendor management, cybersecurity, policy, and limited staff capacity. The goal is to turn complicated technical and compliance questions into clear, usable information for superintendents, technology leaders, and school administrators.
FAQ
No. The AI Tool Exposure Review is an exposure map, not an audit, certification, or legal opinion. It identifies connected tools, relevant vendor terms, and areas that may warrant follow-up.
No. The report can identify which frameworks may be implicated by the data a tool can access, but district counsel or other qualified advisors make legal compliance determinations. For background, see our plain-language guide to student data privacy laws.
A growing number do. Ohio, Tennessee, Arkansas, Maryland, Oklahoma, Utah, Virginia, North Carolina, Idaho, Texas, and Florida now require districts to adopt AI policies through a law or state rule, and most other states, including Michigan, have issued voluntary guidance. See where your state stands in our state-by-state AI guidance tracker.
No direct system access is required for the review. The district administrator provides the relevant third-party application authorization export.
Vendor terms change. Each determination is tied to the source language, document version, and date reviewed so the district can see what evidence supported the finding at that point in time.
On a short video call, we walk your Google Workspace or Microsoft 365 administrator through creating the export. Before anything is sent, we review it together to confirm it contains only application names, permissions, and the number of authorized accounts. Your administrator then uploads it to a restricted folder that only K12 Guardrail can access. We do not accept export files by email.
It shouldn't, and we check together on the call before it is uploaded. If any column lists individual names or email addresses, we remove it first. If we ever receive more than we need, we delete the extra information right away and let you know.
Export files are deleted 30 days after we deliver your report, or sooner if you ask, and we confirm the deletion in writing. We keep a copy of the final report for one year so we can answer follow-up questions, then delete it. You can ask us to delete it earlier at any time.
No. The research and the analysis of your export are done by K12 Guardrail directly. AI writing tools may help draft or format the final report, using settings that keep the provider from training on that content. Your export files are never uploaded to an AI tool.
The report is designed to help the district prioritize next steps and identify the questions that should be taken back to the vendor. The purpose is visibility and informed action, not blame.
Pilot program
We are looking for a limited number of K–12 districts to participate in a no-cost pilot review. You receive the findings either way, with no obligation to continue afterward.
Prefer a quick introduction first? Email nick@k12guardrail.com.