THE FLOCK PACT · A PEOPLE-FIRST TECHNOLOGY INITIATIVE
THE FLOCK PACTTHE SHEEPLE FLOCK · GLOBAL MISSION
03 / Flock Watch

THE RIGHT TO ASK.
THE DUTY TO VERIFY.

An educational, neutral framework for asking how technology collects information, who controls it, and what safeguards actually exist.

◈ Interactive tools run in this browser only. Nothing is sent to a server.
Flock Watch / vendor-neutral

ASK BETTER
QUESTIONS.

Use this checklist when evaluating AI, surveillance cameras, mobile applications, data brokers, or connected devices. It is a question set, not an audit, vendor ranking, compliance finding, or accusation.

A missing public answer is not proof that a safeguard does not exist. Record whether information is claimed, independently verified, undisclosed, or unknown.

Purpose and necessity

  1. What specific public or customer benefit does the system provide?
  2. What evidence supports that benefit, and what are its limitations?
  3. What less-intrusive alternatives were considered?
  4. What uses are prohibited, including secondary or unrelated uses?

Collection and retention

  1. Which personal or sensitive data elements are collected?
  2. Are there ways to minimize collection or run analysis locally?
  3. How long is each data class kept, and who can extend retention?
  4. How are records deleted, and what lawful preservation exceptions apply?

Access and security

  1. Who can search or export data, and what approval is required?
  2. Does access require unique identity, strong authentication and role restriction?
  3. Are access and data-sharing events logged in tamper-evident systems?
  4. How fast are access rights revoked when staff leave or change roles?

Oversight and remedy

  1. Who audits the system independently, and how often?
  2. Can affected individuals contest errors and seek correction or remedy where lawful?
  3. Is a breach and misuse response process documented and tested?
  4. Are oversight findings, exceptions and corrective actions reported in appropriate aggregate form?

AI and downstream sharing

  1. Does automated inference affect consequential decisions, and is human review available?
  2. What testing has been performed for accuracy, bias, misuse and model drift?
  3. Which vendors, data brokers or agencies receive information, under what legal basis, and with what restrictions?
  4. What enforcement, public transparency and corrective measures address proven abuse while protecting responsible operators and fair process?

Evidence and fairness safeguards

Document each answer's source, date, speaker, jurisdiction, exceptions and verification level. Give affected organizations a fair opportunity to correct inaccuracies, and do not publish personal location histories or private credentials.

See NIST's AI Risk Management Framework for a separate, voluntary risk management reference.

APPLY THE QUESTIONS TO THE SYSTEM.

Cameras and license-plate readers

Ask about purpose, coverage, searchable location histories, sharing, retention and misuse audits. Seek aggregate policy records rather than individual movements.

Biometrics and AI

Ask what is inferred, error rates across affected groups, human review, contestability and limits on secondary use.

Smartphones and data brokers

Ask about consent, precise location, downstream sales, opt-outs and deletion verification.

Vehicle tracking

Ask about owner permissions, driver notice, remote access, retention and safeguards against stalking.

EVIDENCE, FAIR RESPONSE, CORRECTIONS.

Confirmed facts

Identify the original source, date, jurisdiction, exact supporting passage and corroboration. State the scope of what was actually verified.

Allegations

Attribute the claim, identify what has not been independently established, and avoid implying guilt.

Opinions

Label interpretation and values clearly. Explain the evidence and uncertainty underlying a judgment.

Unresolved questions

Record conflicting accounts, missing evidence and what would resolve uncertainty. Absence of a public answer is not proof of wrongdoing.

Fair-response procedure · proposed

Before a significant public claim, seek a response through an official organizational contact with a reasonable stated deadline; record the response fairly. Obtain qualified review where safety or legal duties affect disclosure.

Corrections · proposed

Publish dated corrections beside the affected claim, explain what changed and preserve a revision log. Use the general contact only for non-sensitive factual corrections; no protected evidence intake is active.

Independent of Flock Safety. The Sheeple Flock and The Flock Pact are not affiliated with or endorsed by Flock Safety. This is an educational framework, not an investigation service. No targeting, unauthorized investigations, publishing sensitive personal information, hacking or harassment is permitted.

Across all 20 questions, explicitly assess transparency, abuse prevention, cybersecurity and enforcement: who is responsible when safeguards fail, what corrective action follows, and who can independently review it?

Site updates → The Flock Pact