The Wisconsin Flock Scandal: Protect Your Privacy Now

#flock #policesurveillance #wisconsin #english

Title:

The Wisconsin “Flock” Facial‑Recognition Scandal: What It Means for Your Privacy and How to Guard It

Introduction

When the Wisconsin State Patrol started feeding live body‑camera footage into Flock, a commercial facial‑recognition engine, the result was a 420 % jump in Google searches and a nationwide debate on AI‑driven policing. The scandal isn’t just a headline; it’s a warning that any agency with a camera can instantly turn you into a searchable data point. Below you’ll find a practical, step‑by‑step guide to understanding the technology, the legal fallout, and the concrete actions you can take today to protect your identity.

Quick‑Reference FAQ

Question	Answer (Practical Takeaway)
What is Flock and how was it used?	Flock is a facial‑recognition SaaS built by Flock Technologies, a spin‑off of Clearview AI. In early 2024 the Wisconsin State Patrol added a “Upload‑to‑Cloud” button to its body‑camera app. Officers could press the button, send a single video frame to Flock’s API, and receive an instant match against a scraped database of > 3 billion public images. The tool was deployed during traffic stops, protests, and routine patrols—often without a warrant or a clear policy.
Is its use legal?	The law is murky. Federal statutes do not expressly ban police facial‑recognition, but several states (IL, TX, WA) have enacted bans or consent rules. Wisconsin has no specific statute, so the patrol relied on a memorandum of understanding (MOU) with the vendor. Ongoing lawsuits argue the MOU violates the 4th Amendment (unreasonable searches) and Wisconsin’s constitutional privacy clause.
How can I reduce my exposure?	1. Limit public image exposure – Delete or privatize photos on Instagram, Facebook, TikTok. 2. Use privacy‑focused browsers (Brave, Tor) and a reputable VPN. 3. Opt‑out of facial‑recognition databases – many platforms (e.g., Clearview’s partner sites) offer an opt‑out form. 4. Blur faces before sharing – tools like `ffmpeg` or mobile apps can automatically mask faces. 5. Exercise data‑deletion rights – request removal under Wisconsin’s data‑privacy act or the EU GDPR if you reside abroad. A detailed checklist follows.

Why the “Flock” Story Matters Right Now

Search spikes & media frenzy – Google Trends recorded a +420 % surge in the term “Flock facial recognition” between March 15 and April 5 2024.
Social‑media amplification – #FlockScandal and #StopPoliceAI trended in multiple U.S. cities; the conversation even crossed language barriers, appearing on Spanish forums in Argentina and Mexico.
Precedent for nationwide roll‑outs – Wisconsin is the first U.S. state to run a real‑time, cloud‑based facial‑recognition engine on a statewide scale. A court ruling in favor of the patrol could give other jurisdictions a template for rapid deployment.

Hands‑On: How the System Works (and How to Test It Yourself)

Below is a minimal example of the HTTP request the patrol’s body‑camera app would have sent to Flock’s API. Do not use this against any system without permission—it’s shown only to illustrate the data flow.

# Install the HTTP client if you don't have it
pip install httpie   # or use curl

# Sample request (replace API_KEY and IMAGE_PATH)
http POST https://api.flocktech.com/v1/match \
    Authorization:"Bearer YOUR_API_KEY" \
    Content-Type:"application/json" \
    <<< '{
          "image": "$(base64 -w 0 IMAGE_PATH)",
          "confidence_threshold": 0.85
        }'

What happens:
1. The body‑camera app captures a single frame.
2. The frame is Base64‑encoded and sent over HTTPS.
3. Flock’s cloud service runs a deep‑learning model, compares the face to its indexed 3‑billion‑image library, and returns a JSON payload with any matches and a confidence score.

If you want to detect whether an image is being sent to a facial‑recognition service on your own device, you can monitor outbound traffic with a simple tcpdump filter:

sudo tcpdump -i any -nn -s 0 -w flock_traffic.pcap 'dst host api.flocktech.com and port 443'

Action Checklist: Guarding Your Digital Face

✅ Step	Description	Tools / Commands
1. Audit your public image footprint	Search yourself on Google Images; delete or set to private any unwanted photos.	`googlesearch-python` script, or manual search.
2. Enable browser privacy features	Turn on “Do Not Track”, block third‑party cookies, use anti‑fingerprinting extensions.	Brave → Settings → Shields; uBlock Origin.
3. Opt‑out of known facial‑recognition databases	Fill out opt‑out forms for Clearview, PimEyes, and any vendor that lists you.	`curl -X POST https://clearview.ai/optout -d "email=you@example.com"`
4. Blur faces before posting	Use `ffmpeg` to automatically blur faces in videos.	`ffmpeg -i input.mp4 -vf "cropdetect,boxblur=10:1" output.mp4`
5. Request data deletion	Submit a data‑access request to any platform that stores your facial data.	Sample request email template (see appendix).
6. Monitor network traffic	Run a lightweight packet capture on your phone/computer to spot suspicious uploads.	`sudo tcpdump -i wlan0 -w capture.pcap 'port 443'`
7. Stay informed	Subscribe to newsletters from the Electronic Frontier Foundation (EFF) and the ACLU’s privacy blog.	RSS feed URLs.

Legal Landscape at a Glance

Jurisdiction	Facial‑Recognition Policy	Key Cases / statutes
Federal (USA)	No blanket ban; guidance from DOJ and FBI encourages “risk‑based” use.	Carpenter v. United States (2018) – privacy expectations for digital data.
Illinois	Biometric Information Privacy Act (BIPA) – requires explicit consent before collecting facial data.	Rosenbach v. Six Flags (2020) – damages for BIPA violations.
Texas	2021 law restricts law‑enforcement use without a warrant or a court order.	–
Washington	2023 law bans facial‑recognition use by law‑enforcement unless a warrant is obtained.	–
Wisconsin	No specific statute; reliance on MOU. Ongoing state‑wide litigation (e.g., Doe v. Wisconsin State Patrol).	–

Bottom Line

The Wisconsin Flock episode shows how quickly a single vendor can turn ordinary police cameras into a state‑wide surveillance network. Until clear legal safeguards are in place, your best defense is proactive digital hygiene: limit what you share, use privacy‑enhancing tools, and demand transparency from any agency that wants to scan your face.

Appendix: Sample Data‑Deletion Request (Email)

Subject: Request for Deletion of Biometric Data Under Wisconsin Data Privacy Act

To Whom It May Concern,

I am writing to request the immediate deletion of all biometric data (including facial‑recognition templates, images, and associated metadata) that your organization has collected about me pursuant to Wisconsin’s data‑privacy statutes. Please confirm in writing that all such data have been erased and provide a copy of any remaining records that you claim are exempt from deletion.

Full Name: ______________________
Date of Birth: ____________________
Last Known Address: ______________
Relevant Incident/Reference (if known): ______________________

Thank you for your prompt attention to this matter.

Sincerely,
[Your Name]
[Contact Information]

Herramienta mencionada: Supabase

DEV Community