- On June 3, 2026, the Utah State Board of Education (USBE) announced Google Gemini for Education for Utah public schools. News reports and USBE say each district decides whether to use it.
- Tooele County School District signed the Google Data Processing Agreement (DPA) on June 11, 2026.
- USBE’s records response showed no documentation for three state-law requirements. The H.B. 273 requirements took effect July 1, 2026, after the signing.
- The contract lets Google change what is covered, and which companies can see student data, by updating its own webpages. It also lengthens the data-deletion window from 60 to 180 days.
- No Tooele board agenda item or minutes naming Google, Gemini or the DPA has been found for the June 9 or June 16 meetings.
Education pages (7) · tap to open
- Education docketEvery district we track, searchable
- In plain wordsThe short, simple version of the case files
- Tooele County SD: The Gemini deploymentGoogle AI contract, June 2026
- What 100 apps actually sendThe BYU study and H.B. 55
- Box Elder SD: three ways to borrowA failed bond, a petition, then certificates of participation
- How a book gets pulled from every schoolH.B. 29, the Aug. 6 board vote, and political giving
- Book removals in plain wordsThe short version of the book-removal case file
New here? In June 2026, Utah's State Board of Education rolled out Google Gemini to roughly 680,000 K-12 students — without a vote from the elected 15-member Board, and without the safety review, parental notice, or audit terms state law requires. Tooele County School District signed the underlying Google contract on June 11.
This case file covers what the contract itself says, what state law required at the time, and what the district's own records do — and don't — show.
What happened
On June 3, 2026, State Superintendent Molly Hart and USBE AI Specialist Matt Winters announced Google Gemini for Education would be made available across Utah's public schools — without informing or getting a vote from the elected Board, and without a procurement process, privacy review, or parental-notification framework in place beforehand. Tooele County School District signed the Google Data Processing Agreement (DPA) governing the deployment eight days later, on June 11.
The timeline
Tap a date to see what happened and where it comes from. Filled dots mark the two dates this case file turns on.
- Senate Floor Amendment 5 changed the standard from software “designed specifically for instructional use” to software “demonstrated to have significant educational value.” The Senate passed the bill 17-9-3.Source: Hive Bill-Tracker, H.B. 273 case file
- Its safety-review and parent-notice rules were set to take effect July 1, 2026.Source: Hive Bill-Tracker, H.B. 273 case file
- The board’s agenda lists “Revised Policy 5031, Personal Technology and Communication Devices, 1st Read.” This is the student device and AI-glasses policy, not the Google contract.Source: Tooele board agenda, Apr. 21, 2026
- Agenda item 7.9.Source: Tooele board agenda, May 12, 2026
- USBE said local education agencies “maintain full discretion over whether to implement” it, for about 680,000 students.Source: USBE news release
- The posted agenda lists no item naming Google, Gemini, AI or a data privacy agreement (searched as text).Source: Tooele board agenda, June 9, 2026
- Tooele County School District signed the Google Data Processing Agreement covered on this page.Source: Signed Google Data Processing Agreement, June 11, 2026
- The safety-review and written parent-notice requirements apply from this date.Source: Hive Bill-Tracker, H.B. 273 case file
- St. George News quoted board member Joann Brinton saying the contract was first developed for one district that wanted a stronger privacy agreement with Google. The article does not name the district.Source: St. George News
- The rule carries out H.B. 273. It requires districts to adopt technology and AI policies and train educators.Source: USBE Board Summary, Aug. 6, 2026
- Preliminary approval for a model AI policy for districts and an AI Student Task Force. Final board action not yet checked.Source: USBE Board Summary, Sept. 3–4, 2026
- KSL: Canyons turned Gemini on for teachers, staff and high school students; Provo kept it off student Chromebooks while writing its AI policy.Source: KSL, Oct. 7, 2026
What state law required
Three statutes bear on a rollout like this. Records USBE released in response to a records request show none of the required documentation existed for any of them:
- §53G-7-228(2)(a) — requires an evidence-based safety review before instructional technology is deployed.
- §53G-7-1402(2)(j) — requires written parental notification before generative AI use, including a link to the district's metadata dictionary.
- §53E-9-309(2)(a) — requires specific audit and termination provisions in a district's contract with a third-party technology vendor.
What the contract itself does
The Tooele DPA's terms consistently favor Google over the district that signed it:
- Covered services are defined by reference to a Google-controlled webpage — meaning Google can expand what's covered, including adding Gemini features, without a new contract or a board vote.
- The same mechanism governs which subprocessors can access student data — Google can add companies by updating its own site.
- The contract's data-deletion window was extended from 60 days to 180 in a Google-authored amendment.
- The 72-hour breach-notification requirement was replaced with vaguer "promptly and without undue delay" language, and "Data Breach" was relabeled "Data Incident."
- Google may charge for any audit of its own compliance, and may reject an auditor it deems "manifestly unsuitable" — a standard that functions as a veto over who audits it.
- No geographic limit exists on where student data may be stored — the contract allows processing "in any country where Google or its Subprocessors maintain facilities."
Explore the contract, clause by clause
Tap a clause to see what the contract says and why it matters.
What the contract covers
What the contract saysCovered services are defined as the Google Workspace for Education products listed on a Google webpage “(or a successor URL).” (Exhibit A)
Why it mattersGoogle controls that webpage. Products added to it, such as new Gemini features, can fall under the contract without a new contract or a board vote.
Where it isGoogle Data Processing Agreement, Exhibit A
Which other companies can see the data
What the contract saysThe list of subprocessors, the other companies that may handle student data, is also kept on a Google webpage. (Exhibit G, Section 2)
Why it mattersGoogle can change who has access to student data by updating its own page.
Where it isGoogle Data Processing Agreement, Exhibit G
How long before student data is deleted
What the contract saysA Google-written amendment changed the deletion window after the contract ends. (Exhibit H, Section 4.6)
Before and afterStudent data can stay with Google three times as long after the district ends the contract.
Where it isGoogle Data Processing Agreement, Exhibit H
When the district is told about a breach
What the contract saysThe fixed 72-hour notice was replaced with notice “promptly and without undue delay.” (Exhibit H, Section 5.4)
Before and afterThere is no longer a set deadline in the contract.
Where it isGoogle Data Processing Agreement, Exhibit H
Who can check Google’s compliance
What the contract saysGoogle “may charge a fee” for any audit and may object to an auditor who is a competitor or “manifestly unsuitable.” (Exhibit G, Section 1)
Why it mattersThe district pays to check, and Google can object to who checks. The state rule (R277-487-7(5)) also lets vendors self-assess.
Where it isGoogle Data Processing Agreement, Exhibit G; R277-487
Where student data can be kept
What the contract saysStudent data may be processed “in any country where Google or its Subprocessors maintain facilities.”
Why it mattersThe contract sets no geographic limit.
Where it isGoogle Data Processing Agreement
The state’s side
What the contract saysUSBE says data and conversations in Gemini for Education are not used to train AI models, and schools keep administrative control of their data.
Why it mattersThis is the protection USBE points to. It is stated in USBE’s release, not in the clauses above.
Where it isTooele's own board record
No agenda item or minutes entry naming Google, Gemini, or the DPA has been found around Tooele's June 9 or June 16, 2026 board meetings — the deployment may have gone through administratively rather than as a board agenda item.
Tooele's Policy 5031 (Personal Technology and Communication Devices), rewritten in 2026, separately added AI-glasses regulation. Its definition of "AI glasses" closely mirrors the definition later written into state code by H.B. 44 — consistent with district staff aligning the policy to state code, as the district's own stated rationale holds.
Questions worth asking
- Have other Utah school districts signed this same Google DPA, a variant of it, or nothing at all? So far only Tooele's has been confirmed.
- A Washington County board member described "the option of a state contract" districts can opt into — is that Tooele's own agreement functioning as the statewide template, or a separate master agreement that hasn't been obtained yet?
- If your own district hasn't formally signed anything, are students there still using Gemini in the classroom under a teacher's personal Google login, a school-level pilot, or informal use that wouldn't show up in a board record at all?
- Does your district's board have a public record of voting on, or even discussing, a Gemini/Google AI deployment? Tooele's doesn't appear to.
Updates since this was posted
News and records found online, with dates. Earlier entries are not changed.
- Oct. 18, 2026Page redone to match the other Utah Hive Politics repos: new colors, short version, plain-words page, dated updates and reader questions. No earlier text was removed.Source: The Weber County Hive
- Oct. 18, 2026 (record check)Tooele County School District board agendas on the Utah Public Notice Website for April 21, May 12, June 9 and Aug. 11, 2026, and the Aug. 11 minutes, list no item naming Google, Gemini, artificial intelligence or a data privacy agreement. Policy 5031 had its 1st read April 21 and 2nd read May 12, 2026. Read by text search of the posted PDFs; the July 28 work session and the meetings after Aug. 11 have not been checked yet.Source: Apr. 21 agenda, May 12 agenda, June 9 agenda, Aug. 11 agenda, Aug. 11 minutes
- Oct. 7, 2026KSL reported that Canyons School District turned Gemini on for teachers, staff and high school students only, with a red-yellow-green rule for when AI may be used on assignments. Provo City School District told parents Gemini and other AI chatbots are not available on student Chromebooks while it finishes its AI policy.Source: KSL, Eric Cabrera, Oct. 7, 2026
- Sept. 4, 2026 (record found Oct. 18, 2026)The board’s Standards and Assessment Committee gave preliminary approval to a “Utah Instructional Technology and Artificial Intelligence Model Policy” for districts to use when writing their own AI policies, and to creating an Artificial Intelligence Student Task Force. The final full-board action on both has not been checked yet.Source: USBE Board Summary, Sept. 3–4, 2026
- Aug. 6, 2026 (record found Oct. 18, 2026)The State Board of Education approved a new rule, R277-334, Classroom Technology, to carry out H.B. 273. Per the board’s meeting summary, it requires districts and charter schools to adopt policies on technology and AI use, train educators and “ensure parent transparency and student protections.”Source: USBE Board Summary, Aug. 6, 2026
- July 2, 2026 (found Oct. 18, 2026)St. George News reported that USBE says no district is required to take part. State board member Joann Brinton said the contract “was first developed for a district that wanted a stronger privacy agreement with Google”; the article does not name that district. Washington County School District said no students there have Gemini access at school; staff use it under District Policy 3750.Source: St. George News, Nick Fiala, July 2, 2026
- June 11, 2026 (found Oct. 18, 2026)KUER reported that a USBE spokesperson called Gemini for Education “an option, not a requirement,” and that the state board signed a data privacy agreement with Google meant to apply to every school and district that opts in. How that statewide agreement relates to the Tooele DPA on this page has not been confirmed here.Source: KUER, Martha Harris, June 11, 2026
- June 2–3, 2026 (record found Oct. 18, 2026)USBE’s own news release, updated June 3, says local education agencies “maintain full discretion over whether to implement Google Gemini for Education” and puts the number of students at about 680,000.Source: USBE news release (PDF), June 2, 2026, updated June 3
Questions to ask, and whom to ask
Connected Hive work
Behind this piece
Posted Sept. 9, 2026. Redone Oct. 18, 2026 with news reports and public records added; nothing earlier was removed.
Sources
- Google Data Processing Agreement, signed by Tooele County School District, June 11, 2026
- USBE public records response confirming no documentation exists for §53G-7-228(2)(a), §53G-7-1402(2)(j), or §53E-9-309(2)(a) compliance
- USBE press release, "USBE Adopts Gemini for Education," schools.utah.gov, June 2-3, 2026
- Utah H.B. 273 (2026), Classroom Technology Amendments
- Utah H.B. 44 (2026) / S.B. 69 (2026), coordination clause on device restrictions
- Tooele County School District Policy 5031, Personal Technology and Communication Devices (2026 revision)
- Tooele County School District board meeting records, June 9 and June 16, 2026
Links and news added Oct. 18, 2026
- USBE news release, “USBE adopts Gemini for Education,” as posted by Utah Policy
- USBE news release, original PDF on schools.utah.gov
- USBE Board Summary, Aug. 6, 2026 (R277-334)
- USBE Board Summary, Sept. 3–4, 2026
- KSL, “How Utah students use AI in school depends on where they go,” Oct. 7, 2026
- Tooele County School District board agendas and minutes, Utah Public Notice Website: Apr. 21, May 12, June 9, Aug. 11 agenda, Aug. 11 minutes
- H.B. 273 (2026), Classroom Technology Amendments, le.utah.gov
- H.B. 44 (2026), le.utah.gov
- KUER, “Utah schools face a choice: Do they want to use Google’s Gemini AI?” June 11, 2026
- St. George News, “‘A lot of misinformation’: What Utah’s Google AI agreement means for Washington County schools,” July 2, 2026

