An initiative of the fictional P.E.A.C.E. Act

C.A.R.E.

We're watching because we CARE.

Continuous Activity Recording & Evaluation. The mandatory AI-powered public-safety platform that tracks what you type, where you go, who you talk to, and every dangerous moment you choose not to be observed. Because privacy is a vulnerability we're committed to eliminating.

Explore the citizen case file See the actual problem →

IMPORTANT: This is a fictional satirical exhibit, not an agency, law, product, or petition. The demo uses invented people and events. It does not record, track, or inspect visitors or their devices.

24 / 7Proposed observation schedule

0Alleged crimes required to start

∞Opportunities to collect more data

01 / The enabling legislation (entirely fictional)

The P.E.A.C.E. Act.

The Predictive Enforcement & Automated Citizen Evaluation Act is an invented law for this thought experiment. Its promise is simple: make investigations easier by making everyone permanently investigable.

Public protection initiative / Mock legislative brief

To ensure public safety, every citizen must be continuously observable.

The program combines compulsory endpoint monitoring, communication recording, location histories, and wearable cameras. AI produces behavioral risk scores and automatically refers citizens for intervention when activity appears abnormal—or when activity cannot be observed.

Section 1: No suspicion necessary. Section 2: Data collection is presumed beneficial. Section 3: Declining coverage invites closer examination.

Protect the vulnerable.

Record all calls and messages to identify scams. In the name of safety, everyone else's conversations are captured too.

Prevent cybercrime.

Monitor every endpoint and keystroke to detect malicious software. The system also sees private work, passwords, and personal lives.

Guarantee innocence.

Require cameras to verify daily behavior. Disabling a sensor becomes grounds for additional scrutiny.

Close every blind spot.

Whenever a gap is found, add another sensor, database, retention exception, or investigative authority.

02 / Interactive synthetic demonstration

Meet Joe. He hasn't done anything wrong.

Run his perfectly ordinary day through C.A.R.E. Turn monitoring sources off. Increase the AI's sensitivity. Watch how even the absence of information becomes grounds for suspicion.

All names, activity and scores are made up

Citizen intelligence profileActive / compulsory

Joe Citizen

Example record 00001 · No known offense

AI suspicion score—Meaningless illustrative scale

Flagged observations—Simulated records

Crimes established0No established offense

AI marketing confidence99.9%Invented with enthusiasm

Nationwide protection settingsCitizen opt-out prohibited

Algorithmic paranoia setting3 / 5

This is an intentionally arbitrary score, not a trained AI model or a credible criminal-risk assessment.

Automated investigative feedInference ≠ evidence

Analyst review

Select an event to review

The surveillance narrative and mundane explanation will appear side by side.

The trick: Our satire deliberately conflates detection, suspicion, and guilt. A true location match or device event can still support an entirely false story. Absence of telemetry is not evidence of wrongdoing.

03 / Interactive policy escalationFICTIONAL POLICY ENGINE

Every step sounds reasonable. Until you add them up.

Authorize one well-intentioned safety measure at a time. Each decision expands the same surveillance infrastructure. The benefits are plausible; the mandatory, universal rollout is the satire.

0 of 7 measures authorizedPrivacy budget: 100% (invented)

MEASURE 01 / 07

Better public safety starts here.

A modest request.

What else this capability enables

A searchable record that didn't exist before.

The capabilities in this exhibit are mixed: some exist now; others are deliberately fictional extensions. See the sources below.

No single measure eliminated your privacy. We simply protected you from it, one reasonable exception at a time.

Nothing on this page implements these controls. No scanner, camera, microphone, device sensor, or browser history is accessed.

04 / A demonstration you can feel

Would it bother you if we already knew your IP?

Websites generally receive a connection address when you visit them. That doesn't mean they're entitled to build a dossier about you. Choose to run this short demonstration; it won't begin automatically.

C.A.R.E. / VOLUNTARY CONFESSION PORTAL

Your privacy assessment is ready.

Press the button to see what it feels like when a site turns ordinary network metadata into a threat.

ADDRESS NOT REQUESTED

If deployed with the provided Cloudflare endpoint, the browser requests its own IP from the same site. We do not deliberately save it. Hosting/network infrastructure may still maintain routine logs. In plain HTML or offline previews, a clearly marked example address is shown instead.

THE ACTUAL LESSON

Exposure is not consent.

Your IP address is not a magic identity card. It can be shared by households, changed by networks, and masked by VPNs; it does not establish who you are or what you did.

But being confronted with metadata about yourself can still be unsettling. Imagine the consequences when an organization combines that metadata with license plates, DNS activity, purchase history, and location records.

Knowing how to obtain a fact isn't a justification for retaining it.
Publicly observable data can become sensitive when aggregated.
Logging an investigator's queries is not the same as limiting collection.

Promise: The demo does not record your IP in browser storage, cookies, analytics, or a site database. The address is removed from the page after the reveal. We cannot promise intermediaries never log routine requests.

05 / The real issue

Why this is a problem—without the jokes.

Better telemetry genuinely helps investigators and can prevent harm. That fact alone cannot answer whether everybody should be subjected to indiscriminate collection. These are distinct risks that have to be considered separately.

RISK / 01

Observation becomes a dossier.

Seeing a car on a public road is different from searching a database of repeated sightings to reconstruct someone's routines, associations, and sensitive destinations. ACLU explanation ↗

RISK / 02

False connections become real consequences.

Being near an event, using encryption, or having a plate match is a lead—not proof of identity, intent, or guilt. Poor inference can still drive stops, questioning, or arrests.

RISK / 03

Authorized access can be abused.

An access log tells you who searched. It doesn't automatically stop stalking, curiosity searches, or improper sharing. Investigations have documented real ALPR misuse. Reporting ↗

RISK / 04

The purpose quietly expands.

A database justified for serious offenses can be used for less serious matters—or additional purposes—as practices and rules change. Technical feasibility is not the same as legitimate authority.

RISK / 05

Collection creates a new target.

Centralized personal histories are valuable to insiders and attackers. Even perfectly encrypted storage does not eliminate harm from authorized but excessive processing. NIST Privacy Framework ↗

RISK / 06

Privacy becomes suspicious.

When lack of visibility is treated as risk, avoiding monitoring can trigger more monitoring. People may change lawful behavior because they expect every action to be evaluated.

The government doesn't need to own the camera to use the data.

A commercial camera network, ISP resolver, data broker, private security system, or app can gather information for one purpose and provide access for another. The questions are the same: who collects it, how long is it kept, who can search or buy it, and whether people have meaningful notice, choice, or recourse. A private owner does not automatically make government access benign, and government use does not automatically make private collection justified.

Why DNS restrictions belong in this conversation: DNS filtering can block or redirect domains on an ISP's own resolvers, but it is not a universal internet kill switch. Alternative resolvers and other techniques may bypass it. The public-policy concern is the authority to mandate blocking and whether that authority expands into broader filtering or traffic monitoring, not a claim that DNS filtering is impossible to evade.

Privacy is not a confession: Encryption, clearing browser history, disconnecting a camera, or choosing not to share data are ordinary expressions of autonomy. Treating those actions as inherently suspicious flips the burden of proof.

06 / Be precise about the analogy

Flock is not C.A.R.E. That's the point.

Automated license plate readers are not mandatory keyloggers. Equating their capabilities would weaken the argument. This satire instead tests the reasoning: if easier investigations alone justify broad surveillance, where is the limiting principle?

Actual ALPR surveillance

What plate readers can do

Capture a vehicle/plate and record the time and place of a sighting.
Allow searches across observed vehicles and, where available, shared datasets.
Reveal patterns from repeated location observations; trip duration may be inferred if both arrival and departure are captured.
Support investigations and alerts for suspect or missing vehicles, depending on the agency's implementation.
Not equivalent to reading every keystroke, automatically knowing purchases, recording all calls, or identifying every occupant.

The fictional C.A.R.E. escalation

What the satire adds

Compulsory endpoint agents and full-content keystroke logging.
Universal call and message recording.
Always-on personal body cameras and automatic intervention for missing coverage.
Predictive behavior scores that turn ordinary activity into investigative leads.
No meaningful opt-out, individual suspicion threshold, or independent authorization.

Flock describes role-based access, query logging, agency-controlled sharing, and retention controls; those safeguards deserve to be evaluated alongside documented misuse and independent oversight. Read the vendor's account of its safeguards ↗

07 / Evidence, not vibes

Real examples. Real constraints.

The fictional product is intentionally ridiculous. The background issues are documented. Each reference below distinguishes reporting, legal precedent, and what vendors say their controls do.

Investigative reporting · August 2026

Search logs existed. Misuse still happened.

The Washington Post reported at least 69 police officials accused, charged, or convicted of misusing Flock or other license-plate reader systems. That's not 69 confirmed Flock-only cases, and allegations are not convictions.

Read the investigation ↗

U.S. Supreme Court · June 22, 2018

Location aggregation has privacy consequences.

Carpenter v. United States addressed historical cellphone location records and recognized substantial privacy interests in accumulated movements. It did not automatically decide whether every ALPR search requires a warrant.

Read the opinion (PDF) ↗

Vendor response · August 2026

Safeguards are evolving after scrutiny.

Flock announced case-number requirements, automated abnormal-search review, and a shorter default retention period following reporting on misuse. Improvements in controls matter, but they do not settle whether collection itself is justified.

Read the policy-change reporting ↗

07.5 / A test any surveillance program should face

Questions more useful than “nothing to hide.”

You don't have to reject every investigative tool to demand a clear justification, enforceable limits, and public accountability.

What specific problem requires this collection?

Show effectiveness and compare less intrusive ways to achieve the same outcome.

Who can search, and on what grounds?

Define authorized purposes, suspicion thresholds, approvals, and limits on browsing.

How long is information retained?

Explain deletion, preservation exceptions, replication, backups, and auditability.

Who else receives the data?

Identify sharing partners, onward sharing restrictions, and cross-agency access.

Does anybody independently audit usage?

Logs help only when anomalies are reviewed and misuse has consequences.

What happens when the system is wrong?

Require corroboration, human review, correction pathways, and meaningful remedies.

Can people understand what is collected?

Publish policies, access statistics, retention rules, and independent assessments.

When does the program end?

Establish limits, reauthorization, performance review, and suspension criteria.

08 / A history of reasonable requests

Pieces of the satire already exist.

Not every fictional power here has been proposed, enacted, or deployed. These documented examples show the narrower technologies and policy disputes from which the satire extrapolates.

Actual technology

Networked plate readers

ALPR cameras record timestamps and locations; aggregating sightings can expose movement patterns. Real capabilities, real law-enforcement uses, real controversies.

ACLU background ↗

Documented misuse

Abusing legitimate credentials

Investigative reporting described officers searching license-plate databases for personal purposes, underscoring why query logs alone do not ensure accountability.

Read reporting ↗

Real policy debate

Public access to information

Website-blocking proposals raise questions about overblocking, due process, censorship risks, and enforcement. DNS is one possible technique, not comprehensive internet control.

EFF / Free expression ↗

Constitutional context

Location data changes the analysis

The Supreme Court recognized privacy interests in collected cellphone location history in Carpenter; it did not automatically decide all ALPR cases.

Read the opinion ↗

Real safeguards

Stronger auditing isn't the whole answer

Flock has described case-number requirements and changes to automated audits. Detection and accountability matter, but they don't decide whether universal collection is warranted.

Read reporting ↗

Fictional extrapolation

Universal C.A.R.E. monitoring

Mandatory national keyloggers, citizen body cameras, and AI suspicion scores are inventions of this site, not a claim that Flock performs those functions.

Back to the satire ↗

09 / How you can help · Exercise your remaining rights

You're still allowed to write your representatives. For now.

C.A.R.E. believes every citizen deserves a voice. Until further notice, using that voice does not automatically increase your suspicion score. Below the joke is a real, editable privacy-oversight letter for your elected officials.

Choose the right audience

Your city council controls different things than Congress. Pick a letter addressed to someone who can actually act on the request.

Recipient Subject line (editable)

Before sending: add your own location and experience if you want, verify any local contract facts, and make the request specific. This tool doesn't contact an office or submit anything on your behalf.

Find your U.S. representative ↗
Contact U.S. senators ↗
ACLU model local ALPR legislation ↗

No user accounts, cookies, analytics, browser storage, or form submission. Everything you edit stays in your browser until you choose to copy or download it.

Your letter, your words

Editable message

This is a draft reflecting a privacy-protective position, not a legal opinion. Officials and residents can reasonably disagree on deployment, and the letter invites evidence-based decisions and enforceable rules.

The thesis behind the joke

The technology is fictional. The threat to privacy isn’t.

Security teams know the value of good telemetry. They also know that false positives, excessive privileges, failed audits, and giant datasets create risks of their own. Better investigative outcomes and stronger privacy protections can both be legitimate goals. A surveillance system still needs a justification beyond “you have nothing to hide.”

Privacy isn’t about having something to hide. It’s about having something that belongs to you.

Contact your representatives ↓

10 / Further reading & accountability

Why we question mass surveillance. And how to verify the claims.

Direct links to community mapping, civil-liberties analysis, technical guidance, reporting, and the vendor's own description of its controls. Some resources take a clearly critical position; others explain safeguards or legal boundaries.

DeFlock camera map ↗

Crowdsourced locations of automated plate readers, contributed by volunteers and OpenStreetMap users. Entries may be incomplete.

maps.deflock.org DeFlock project ↗

Learn about ALPRs, the open-source mapping effort, and ways to document cameras.

deflock.org EFF / ALPR explainer ↗

Digital-rights analysis of plate readers, location databases, sharing, and civil liberties.

eff.org ACLU / Plate readers ↗

Research and policy concerns about collecting innocent drivers' travel information.

aclu.org Atlas of Surveillance ↗

Explore documented law-enforcement surveillance technologies and deployments.

atlasofsurveillance.org NIST Privacy Framework ↗

Technical framework for managing privacy risks that can arise even without a breach.

nist.gov Investigation of ALPR misuse ↗

Reporting on improper system searches and audit failures. May require a subscription.

washingtonpost.com Flock's privacy description ↗

The company's explanation of data lifecycle, retention, role-based access, audit logs, and sharing.

flocksafety.com Carpenter v. United States ↗

2018 Supreme Court opinion on cellphone location records; relevant context, not an ALPR-specific ruling.

supremecourt.gov · PDF ACLU / Local ALPR policy model ↗

Concrete provisions lawmakers may evaluate when developing local plate-reader policies.

aclu.org Find your representative ↗

Official House directory to identify your congressional district and representative.

house.gov Contact U.S. senators ↗

Official Senate contact directory and constituent communication options.

senate.gov

External resources are independent of this satirical project. Links do not imply endorsement by, or affiliation with, any organization. References verified October 2026. Laws and policies vary by jurisdiction and can change.