Elementary school cameras

Flock Is Now in Your Elementary Schools

On May 4, 2026, City Council voted to approve connecting existing Casa Grande elementary school cameras to the Flock ecosystem through Flock gateways.

Nowhere did the contracts or agenda items clearly say Flock. We believe that omission was deceptive because naming Flock plainly would likely have brought far more parents and residents into the room.

Contact the Mayor and Council Sign the Petition Read the Documents

Serious concern

Parents should not learn after the vote that school cameras are being connected to a private surveillance ecosystem.

This is about public notice, parental rights, enforceable limits, and whether elementary school children should be folded into a massive AI camera network without clear public debate.

What happened

The public deserved plain language before the vote.

The City Council approval connects existing cameras at Casa Grande elementary schools to the Flock ecosystem through gateway hardware. That makes this more than a routine school camera agreement. It creates a pathway for school camera access inside a broader surveillance network.

If Flock had been named in the agenda or agreements, many residents may have understood the stakes sooner and demanded stronger limits before their children's schools were connected.

Public safety and child safety matter. So do transparency, parent notification, clear access limits, independent auditing, and explicit bans on invasive AI uses.

Source documents

Read the agreement and resolution for yourself.

These documents are the basis for the concerns on this page. Residents should review the actual language and ask why Flock was not named plainly.

PDF source

Data Sharing Agreement

Agreement language governing access to Casa Grande Elementary School District campus monitoring systems.

Open document

PDF source

Resolution 5909 / IGA with CGESD

City Council resolution and intergovernmental agreement materials tied to the school camera access arrangement.

Open document

Broad contract language

The agreement leaves too many questions unanswered.

The concern is not just that school cameras can be viewed. The concern is that the agreement uses broad terms while failing to clearly restrict remote access, AI analytics, data retention, third-party integrations, auditing, and parent notification.

1

Contract concern

"Authorized Users" is extremely broad and undefined

The agreement repeatedly allows access by "Authorized Users," but does not clearly define who qualifies, how many users there can be, what training they need, or whether contractors and vendors can receive access.

Questions still unanswered

  • Who can become an authorized user?
  • Are access logs reviewed?
  • Can contractors or vendors qualify?
2

Contract concern

Remote access to school cameras

The agreement says the district will provide access on premises and through secure technology, with the option for authorized users to view campus monitoring systems remotely.

Questions still unanswered

  • Is access live-only or can recordings be viewed?
  • Can footage be downloaded, copied, or exported?
  • Can third-party systems integrate with the footage?
3

Contract concern

"Community incidents near District property" is vague

The agreement allows access when police respond to community calls proximate to district property. Terms like "community issue," "near," and "proximate" are subjective and not limited to direct school threats.

Questions still unanswered

  • What counts as near district property?
  • Who decides when a community issue qualifies?
  • Could neighborhood calls trigger school camera access?
4

Contract concern

No explicit ban on facial recognition or AI analytics

The agreement does not expressly prohibit facial recognition, gait analysis, demographic classification, object tracking, behavioral analytics, or integration with external intelligence systems.

Questions still unanswered

  • Are AI analytics forbidden?
  • Can searchable metadata be created?
  • Can person re-identification tools be applied later?
5

Contract concern

No independent auditing or transparency requirements

The agreement does not require public reporting, parent-visible access logs, annual audits, misuse investigations, disciplinary consequences, or transparency reports.

Questions still unanswered

  • How often were cameras accessed?
  • Who viewed the feeds?
  • What incident justified each access?
6

Contract concern

No clear retention limits for video footage or derived data

The agreement discusses destruction of student data but does not clearly set retention limits for surveillance footage, exported clips, screenshots, copied recordings, or downstream analytical data.

Questions still unanswered

  • How long can exported footage exist?
  • Can movement patterns or location histories be retained?
  • Are screenshots and copied clips destroyed?
7

Contract concern

"Public safety purposes" is too open-ended

The access standard says use is for public safety purposes only. Without strict definitions, that can expand beyond emergencies into routine surveillance over time.

Questions still unanswered

  • Is access limited to emergencies?
  • Are warrants or written justifications required?
  • Who reviews whether the stated purpose was valid?
8

Contract concern

The agreement anticipates identifiable student information being viewed

The agreement acknowledges that officers may observe personally identifiable student information on historical footage, then directs them to stop viewing and request footage officially.

Questions still unanswered

  • Why is historical footage access broad enough for this to happen?
  • What happens after identifiable children have already been viewed?
  • Are parents told when this occurs?
9

Contract concern

No parent notification requirement

The agreement does not require notifying parents when footage involving their child is accessed, after incidents, after misuse, or after breaches except where other rules may require it.

Questions still unanswered

  • Will families know when their child appears in accessed footage?
  • Will parents be told after misuse?
  • What rights do parents have to review access records?
10

Contract concern

Security language is generic

The agreement uses broad phrases like industry best practices, reasonable safeguards, and secure technology, but does not specify end-to-end encryption, MFA, immutable audit logs, third-party audits, or breach penalties.

Questions still unanswered

  • Is multi-factor authentication mandatory?
  • Are audit logs immutable?
  • Are there outside cybersecurity audits or penalties?

What parents should ask for

Do not connect children's schools to Flock without enforceable limits.

Casa Grande leaders should pause this connection, put Flock on the public agenda by name, disclose exactly who can view school cameras, and adopt clear rules before any school footage becomes part of the Flock ecosystem.

Take action

Contact the mayor and council, then add your name to the petition.

Ask for public notice, explicit AI prohibitions, independent audits, retention limits, parent notification, and clear consequences for misuse.

Contact the Mayor and Council Sign the Petition