Teachers and staff want AI for lesson plans, letters and paperwork. AILeakShield shows you which AI tools are in use and keeps student records out of the ones your school hasn't approved.
Sample data shown. Select the image to enlarge it.
Staff are usually trying to help a student or finish paperwork.
A plan is pasted in to rewrite goals or draft a note to a family.
A spreadsheet is uploaded for analysis or to draft feedback.
A student's details are included to draft a recommendation or a report comment.
Health and counseling details are among the most sensitive items in a file.
Family financial details are pasted in to explain an award or draft a reply.
A student information system password ends up in a shared prompt.
Schools can share education records with an outside provider without consent under the school official exception only when the provider performs a service staff would otherwise do, is under the school's direct control for the use and maintenance of those records, and follows FERPA's limits on use and redisclosure. A free AI account that a teacher signed up for alone has none of that in place. The U.S. Department of Education's model terms of service guidance also warns about terms that let a provider change the agreement without notice, so read each vendor's terms before you approve it. State student privacy laws may add to this.
A way to say yes to useful tools and show how they're governed.
Blocks personal identifiers, health information and credentials, and warns on financial aid and family financial data.
See AI sites, extensions and desktop apps in one list, with each vendor's risk.
Review each tool, approve the ones your district or college has vetted, and restrict the rest.
A warning explains the risk to the person about to send it, and written reasons are recorded.
Set different rules for teachers, counselors, administrators and other staff groups.
Blocked sends are recorded by category, without the student's information.
Nothing changes for staff until you decide.
On Microsoft 365, start with the free report. On Google Workspace, go straight to the next step.
Deploy to managed staff browsers in monitor mode. Nothing is blocked.
Approve the tools you trust, restrict the rest, and turn on your data rules.
Decisions, overrides and sign-offs are recorded for your next review.
No. No single tool does. AILeakShield enforces one control and records the evidence. Your policies, annual notice and staff training stay with you.
No. That depends on your contracts and policies. AILeakShield helps you see each vendor's terms and enforce the decision you make.
Yes. Staff text going to an AI tool is checked by our service first, so review us the same way you review other vendors. Blocked content is never stored, and other prompt text is cleared at the end of each day (UTC).
Yes for the browser protection in managed Chrome and Edge. The free report reads Microsoft 365 only, so Google Workspace schools start with browser discovery instead.
No. Numbers and labeled records are the strongest case. A name in a plain sentence can get through, so it works alongside training and your AI policy.
We suggest starting with staff, who handle education records. Student devices are a separate decision, and your state student privacy rules and vendor agreements apply.
Coverage is managed browsers and the secure workspace. Records moving through email, your learning management system or personal phones are outside it.
On Microsoft 365, start with a free report that doesn't read any email, files or chats. On Google Workspace, book a demo and we'll show you the browser route.