- Researchers at BYU and Internet Safety Labs tested 100 EdTech apps used in Utah classrooms (2023–25) and recorded what each app actually sent.
- 52% of apps with a signed data privacy agreement (44 of 85) collected at least one piece of data their contract did not allow.
- 61% of tested apps share data with third parties; 36% share with advertisers.
- H.B. 55 (Rep. Tiara Auxier, primary sponsor) took effect July 1, 2026. It adds stricter privacy terms, audits and contract termination for vendors that break the rules.
- The state rule still lets vendors meet the audit requirement with a self-assessment. A true onsite audit happens only if the vendor agrees.
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 2023-25, researchers at BYU and Internet Safety Labs tested 100 EdTech apps used in Utah classrooms, capturing what each one actually sent over the network — not what its contract said it would send. The report sat largely unnoticed for a year until it became the basis for H.B. 55, which took effect July 1, 2026.
This case file covers what the testing found, the law that followed, and how it connects to the broader student-data-privacy picture, including the separate Google Gemini/Tooele story.
The timeline
Tap a date to see what happened and where it comes from. Filled dots mark the key dates.
- The study’s Table 1 uses each district’s app count as of summer 2023. Researchers found more than 3,000 unique apps statewide and picked 100 to test.Source: “Utah EdTech App Data Collection and Sharing: 2023-25 Investigation”
- USBE funded the work. Test accounts posed as students under 13; researchers recorded what each app sent.Source: “Utah EdTech App Data Collection and Sharing: 2023-25 Investigation,” schools.utah.gov/studentdataprivacy
- Rep. Tiara Auxier is the primary sponsor. The law adds stricter privacy terms, audits and contract termination for vendors that break the rules.Source: H.B. 55, le.utah.gov
- KSL reports a contract must be ended if a violation is not fixed within 30 days.Source: KSL, Aug. 18, 2026
- KSL reports vendors could fix problems through a USBE reconciliation process, after which their names came off the non-compliance list.Source: KSL, Aug. 18, 2026
- R277-487 still lets vendors meet the audit requirement with a self-assessment or an industry audit report. Its last change is listed as July 8, 2025.Source: USBE, R277-487 rule page
The study
"Utah EdTech App Data Collection and Sharing: 2023-25 Investigation" was a joint project between the Utah State Board of Education (USBE) and researchers Mark Keith and Justin Giboney at BYU, working with Lisa LeVasseur and Bryce Simpson at Internet Safety Labs. USBE itself funded the work.
Researchers identified more than 3,000 unique EdTech apps in use statewide, then selected 100 for deep testing based on usage frequency, authentication requirements, and contract status. They created test accounts mimicking students under 13, used each app for 15-20 minutes, and captured all outgoing network traffic — comparing what left the app against the 79 student data elements Utah's own contract template allows vendors to collect.
What they found
- 52% of apps with a signed DPA (44 of 85) collected at least one data element they weren't contractually permitted to collect.
- 61% of tested apps share data with third parties; 36% share specifically with advertisers.
- Three unnamed apps — anonymized in the report as "005," "041," and "026" — shared data with 32, 33, and 54 advertisers respectively. USBE's policy lets vendors who "respond adequately" to inquiry have their names redacted, meaning the worst-sharing but cooperative vendors stay anonymous; only Loom (owned by Atlassian) was named specifically, for not cooperating.
- The most commonly shared data element with advertisers is a UUID — a persistent tracking identifier. The state's own contract form has no checkbox for vendors to disclose UUID sharing, so most never did.
- CoolMathGames.com was separately found running location-based behavioral advertising on a kids' site, ignored a private disclosure from researchers for months, and only fixed it after public exposure.
The findings, in pictures
Percent of the 100 tested apps unless noted. Tap a bar for details.
EdTech apps each district reported (2023)
Longer bar = more apps. Tap a bar for details.
H.B. 55 — the resulting law
Rep. Tiara Auxier (R-Morgan) is the primary sponsor of H.B. 55, "Privacy Compliance for Education Technology Vendors," effective July 1, 2026. It mandates stricter privacy terms, audits, and contract termination for vendor non-compliance, and amended §53E-9-309(2)(a) — the same statute already flagged in the Gemini/Tooele DPA case file.
The loophole underneath both stories
Utah's implementing rule, R277-487-7(5), lets vendors satisfy the audit requirement through self-assessment, a district questionnaire, or a SOC2/SOC3 report — a true onsite audit only happens if the vendor agrees to it. That's a structural gap independent of any single vendor, and it applies equally to the hundreds of EdTech apps in this study and to Google's own Gemini contract.
District app counts from this study
The report's own Table 1 lists how many EdTech apps each Utah LEA reported using as of summer 2023. These are the source for the app counts shown on the Education docket:
| District | Apps reported |
|---|---|
| Provo City SD | 2,386 |
| Jordan SD | 954 |
| Granite SD | 694 |
| Weber SD | 580 |
| Tooele County SD | 77 |
How this connects to the Gemini/Tooele story
Google Gemini does not appear anywhere in this study's tested apps or app list — data collection ran 2023 through August 2025, before Gemini for Education existed in Utah schools (June 2026). Other Google products (Classroom, Workspace, Drive, Docs, Slides, Forms, Sites, Sheets) do appear, confirming Tooele and other districts were already Google Workspace customers before the Gemini rollout. See the Tooele County SD case file for that separate story.
Questions worth asking
- Why does USBE's own policy let a vendor's name be redacted just for "responding adequately" to an inquiry — protecting the worst data-sharing vendors from public identification while only naming the one that didn't cooperate?
- If the average signed DPA specifies only 3 of 79 possible data elements, what is a district actually agreeing to when it signs one?
- Does your own district's app list overlap with any of the three anonymized apps sharing data with 32, 33, or 54 advertisers?
- If a vendor's DPA only covers its paid tier, how would a parent or teacher know their students are using the unprotected free version instead?
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)The state rule R277-487 still lets a vendor meet the audit requirement with a self-assessment or an industry audit report such as SOC2 or SOC3. USBE’s rules page lists its last change as July 8, 2025, before H.B. 55 took effect July 1, 2026; no amendment was listed.Source: USBE, R277-487 rule page
- 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
- Aug. 18, 2026 (found Oct. 18, 2026)KSL reported that vendors found out of compliance could fix problems through a reconciliation process with USBE, after which their names came off the non-compliance list. KSL also reported that H.B. 55 requires a contract to be ended if a privacy violation is not fixed within 30 days.Source: KSL, Logan Stefanich, Aug. 18, 2026
Questions to ask, and whom to ask
Connected Hive work
Behind this piece
Posted Sept. 9, 2026. Redone Oct. 18, 2026 with one news report and three public records added; nothing earlier was removed.
Sources
- "Utah EdTech App Data Collection and Sharing: 2023-25 Investigation," USBE/BYU/Internet Safety Labs, dated August 20, 2025 — schools.utah.gov/studentdataprivacy
- H.B. 55 (2026), Privacy Compliance for Education Technology Vendors, Rep. Tiara Auxier, primary sponsor
- Utah Student Data Protection Act (2016), §53E-9-303, §53E-9-308, §53E-9-309
- R277-487, Public School Data Confidentiality and Disclosure (USBE implementing rule)
- August 2026 press coverage of the report's public release, incl. vendor follow-up statements
- askbeforeyouapp.com/ecosystem/ut — public tracking resource for Utah's EdTech statutory scheme
Links and news added Oct. 18, 2026
- H.B. 55 (2026), Privacy Compliance for Education Technology Vendors, le.utah.gov
- KSL, “How a BYU study led Utah lawmakers to pass a student data privacy law,” Aug. 18, 2026
- USBE, R277-487 rule page (checked Oct. 18, 2026)
- USBE Board Summary, Aug. 6, 2026
- USBE Board Summary, Sept. 3–4, 2026
- USBE Student Data Privacy page, schools.utah.gov/studentdataprivacy

