School Workbench is designed around one principle: read the least, keep it safe, and put the school and student in control of it. Here's exactly how.
Access is granted through Google's own consent screen, read-only. Any other system — Rediker, Blackbaud, ClassLink or Clever — is connected only if the school's own administrator chooses to, and only to read. School Workbench cannot post, send, or change anything in a student's account or the school's systems — it has no ability to, by design.
A district's Google Workspace administrator approves the app for their domain, and can revoke it at any time. It's a dedicated education service — student data is isolated and encrypted, and the AI runs through Amazon Bedrock inside our AWS account, never a consumer AI service, and is never trained on student data.
Each student's data is stored separately and every query is scoped to that one student. There is no path in the system by which one student's information can surface for another.
The keys that let the app read a student's account, and the keys a school enters to connect its other systems, are encrypted before they're stored, with the encryption key held outside the database — so the stored data alone can't be used to reach anyone's account.
A student or school can disconnect and erase all of that student's stored data. Access can also be revoked instantly from the Google account or the school's admin console, and a school can disconnect any integration from its School Workbench admin panel at any time.
Student data is used only to provide the service to that student. It is never sold, never used to target advertising, and never repurposed.
School Workbench is designed to support a school's obligations under FERPA and student-data-privacy laws: data minimization (read-only, least scope), the school as the controlling party, no secondary use, and a clear deletion path. The school's Workspace administrator approves and can revoke access, student data is isolated and encrypted, and the AI runs through Amazon Bedrock inside our AWS account — never a consumer AI service, and never trained on student data.
We're glad to complete a district's security review, sign a data-privacy agreement, and walk your IT team through the architecture in detail. Get in touch and we'll start that conversation.
This page describes how the software is built and intended to be operated. It is not legal advice, and specific compliance obligations depend on your district's policies and applicable law.