From the Public Safety edition of October 29, 2026
Colleges begin to "de-Flock": Emory removed campus plate readers and Cornell and Penn State are ending contracts, as a study counts at least 150 institutions using Flock and one college could not cancel
Campus police departments (Emory University, Cornell University, Penn State, Elgin Community College, University of Delaware and others) · Policing / campus police automated license plate readers · United States
- Publisher
- Inside Higher Ed
- Original publication
- Inside Higher Ed, Oct. 29, 2026
- Source retrieved
- 2026-10-30
- Event date
- 2026-10-29
What happened
Inside Higher Ed reports that Emory University removed about a dozen Flock automated license plate readers in September and did not renew, Cornell did not renew, and Penn State plans to end its contract, amid student campaigns. A recent study identified at least 150 colleges and universities using Flock as of May, including large publics and two-year colleges; Flock declined to give a current count. Contract costs cited include $33,974 a year at Old Dominion University and $15,000 a year for five cameras at East Tennessee State. Elgin Community College tried to cancel after a student was detained by ICE, but Flock refused; staff covered the cameras with trash bags, the bags were removed, and Flock uninstalled the cameras when the contract expired in April. The University of Delaware says its campus police have strong policies limiting ALPR access, use, retention and sharing; students there want no replacement with other vendors such as Axon or Motorola Solutions. Flock has changed some default sharing settings.
Why it matters
Campus police are a large, little-noticed part of the ALPR market, and their exit problems (contract lock-in, data sharing defaults) mirror those facing cities.
Evidence and measured results
Opened the Inside Higher Ed article and read it in full; the cited study of institutional Flock use was not opened; contract figures are as reported.
Limitations and uncertainty
News feature centred on student activism; institution-level reasons for non-renewal partly as reported; underlying study not opened; no data on ALPR effectiveness on campus.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Universities face student pressure over campus plate readers and may be unable to exit contracts or control data sharing.
- Stakeholders
- Campus police chiefs
- General counsel
- University IT security and privacy offices
- Student government
- Discovery questions
- Who can search campus plate data today?
- What are the termination and data deletion terms?
- Is there a public ALPR policy?
- Value hypothesis
- A contract and configuration review gives leadership a defensible keep, fix or exit decision.
- Potential engagement
- ALPR contract, policy and sharing-configuration review.
- Unsupported claims
- Campus crime reduction from ALPR
- That alternative vendors reduce risk
Pre-sales engineering
Role takeaway
- Fit
- Fits campuses with ALPR contracts up for renewal.
- Architecture and integration
- Vendor cloud with network sharing; audit logs and sharing settings in the vendor portal.
- Prerequisites
- Admin access to vendor portal
- Contract documents
- Campus ALPR policy
- Constraints
- Mid-term cancellation may be refused
- Vendor-controlled defaults
- Security
- Restrict outside sharing; enforce retention; verify deletion at exit.
- Proof of value
- One-month audit-log review of outside-agency searches against policy.
Delivery
Role takeaway
- Work
- Review contract, sharing, retention and logs; produce remediation or exit plan.
- Dependencies
- Vendor cooperation
- Counsel review
- Leadership decision
- Ownership
- Campus police chief with general counsel and IT security
- Skills and adoption
- Campus police trained on audit-log review and policy limits.
- Governance checkpoints
- Leadership decision on renewal
- Counsel sign-off on terms
- Post-exit deletion verification
- Acceptance criteria
- Sharing limited to approved agencies
- Audit report delivered
- Exit clause in any renewal
- Risks
- Contract lock-in
- Replacement vendor with same capability
- Reputational harm from undisclosed sharing
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Campus readers often join wider Flock sharing networks; default sharing settings determine whether campus data reaches outside agencies.
Governance
Who approves, reviews and stays accountable for outcomes?
Decisions sit with university administrations and campus police, often with less public process than city councils; student pressure is the main trigger.
Security and privacy
What data, permissions and controls need testing?
Concern about immigration enforcement access to plate data; institutions point to access, retention and sharing policies as controls.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed beyond student and campus police roles.
Procurement
What should contracts, pricing and exit terms secure?
Elgin’s inability to cancel mid-term shows the need for termination-for-convenience and data-sharing exit clauses.
Operating model
Which teams own the service once it runs?
Some campuses see readers as essential for investigations, others are exiting; replacements from other vendors may continue the same capability.
Publication history
- 2026-10-29Public Safety · Issue 537 resources
Stable resource ID: colleges-de-flock-campus-police-alpr-exits-emory-cornell-penn-state-20261029