Privacy
You decide what leaves the community
Residents post anonymously. The AI only ever sees infrastructure and area-level counts. Nothing is shared outside without a person reviewing a Data Sharing Preview and approving it.
What the system knows
| Information | Stored | AI sees | Can be shared | Rule |
|---|---|---|---|---|
| Report title & description | Yes, anonymous | Never leaves the app | ||
| Report location | Approximate pin | Only area names are used | ||
| Report counts per area & category | Computed | Included after your approval | ||
| Confirmations (“me too”) | Hashed device id only | Never readable, even by admins | ||
| Community notes & added info | Yes, anonymous | Only the count is used | ||
| Infrastructure names, types & links | Yes | Included after your approval | ||
| Device security status (demo) | Yes | Used for analysis only | ||
| Impact estimates (demo) | Computed | Included after your approval |
Who can receive a report
- County emergency management
- Water / power / internet operators
- County Public Works
- Farm co-op & extension office
- Clinic & school administrators
- Community IT volunteer
Only organizations and roles — never private individuals. The AI picks recipients per plan; you see them before approving.
Requires your permission
- Creating a case from any AI plan
- Sharing the case summary with any recipient
- Changing report status or deleting reports (admin passcode)
AI Activity Log
- Case created · 10/4/2026, 4:17:54 AM · Custom scenario
Approved by user; tracking started.
- Approved · 10/4/2026, 4:17:53 AM · Custom scenario
User approved the plan and data sharing preview.
- Asking for your approval · 10/4/2026, 3:30:41 AM · Custom scenario
Waiting for a person to review the plan and data sharing preview.
- Preparing the report · 10/4/2026, 3:30:41 AM · Custom scenario
Data sharing preview built: 22 systems, counts only, no resident text.
- Explaining the reasoning · 10/4/2026, 3:30:40 AM · Custom scenario
The supplied chains identify Substation, Cell Tower, and Village Mesh Router as shared upstream dependencies, making safe verification and essential-service continuity priorities. Simulated device weaknesses guide targeted hardening, while demo counts and community reports justify checks rather than conclusions about compromise.
- Creating the response plan · 10/4/2026, 3:30:39 AM · Custom scenario
7 steps (6 high priority), citing 3 sources.
- Determining possible impact · 10/4/2026, 3:29:59 AM · Custom scenario
~545 people (demo estimate), 12 services, urgency critical.
- Checking cybersecurity implications · 10/4/2026, 3:29:58 AM · Custom scenario
12 connected digital systems in the chain (Internet, Routers, Cameras, Smart irrigation, Networks, Sensors, Farm equipment, Laptops). Treated as simulated risk, not confirmed compromise.
- Retrieving trusted resources · 10/4/2026, 3:29:58 AM · Custom scenario
Matched tags [cyber, privacy, power, water, internet, community, agriculture, home, router, camera, irrigation, network, sensor, equipment, laptop] → 6 sources (5 official).
- Finding related community reports · 10/4/2026, 3:29:57 AM · Custom scenario
13 related reports and 1 note on affected places (only counts are passed on).
- Analyzing dependencies · 10/4/2026, 3:29:56 AM · Custom scenario
Substation → Cell Tower → Village Mesh Router → Orchard Router → Orchard Cooperative · Substation → Cell Tower → Village Mesh Router → Smart Irrigation Controller → Grain Fields · Substation → Cell Tower → Village Mesh Router → Farm Network → Soil Moisture Sensors
- Identifying affected systems · 10/4/2026, 3:29:55 AM · Custom scenario
23 systems across 8 areas: Village Center, South, Central East, North, South East, Central West, South West, North West.
- Understanding the incident · 10/4/2026, 3:29:54 AM · Custom scenario
Cybersecurity incident at Substation (simulated).
- Status changed · 10/4/2026, 3:27:51 AM · Custom scenario
Case marked Resolved.
- Status changed · 10/4/2026, 3:27:49 AM · Custom scenario
Case marked In Progress.
- Status changed · 10/4/2026, 3:27:48 AM · Custom scenario
Case marked Resolved.
- Approved · 10/4/2026, 3:09:55 AM · Custom scenario
User approved the plan and data sharing preview.
- Case created · 10/4/2026, 3:09:54 AM · Custom scenario
Approved by user; tracking started.
- Asking for your approval · 10/4/2026, 2:48:52 AM · Custom scenario
Waiting for a person to review the plan and data sharing preview.
- Preparing the report · 10/4/2026, 2:48:52 AM · Custom scenario
Data sharing preview built: 22 systems, counts only, no resident text.
- Explaining the reasoning · 10/4/2026, 2:48:51 AM · Custom scenario
The dependency chains identify power and shared connectivity as the main cascade pathways, while demo security weaknesses guide targeted checks rather than prove intrusion. The plan prioritizes operator safety, essential-service continuity, evidence preservation, and staged restoration because report counts and impact estimates remain unverified.
- Creating the response plan · 10/4/2026, 2:48:50 AM · Custom scenario
8 steps (7 high priority), citing 6 sources.
- Determining possible impact · 10/4/2026, 2:48:10 AM · Custom scenario
~545 people (demo estimate), 12 services, urgency critical.
- Checking cybersecurity implications · 10/4/2026, 2:48:09 AM · Custom scenario
12 connected digital systems in the chain (Internet, Routers, Cameras, Smart irrigation, Networks, Sensors, Farm equipment, Laptops). Treated as simulated risk, not confirmed compromise.
- Retrieving trusted resources · 10/4/2026, 2:48:08 AM · Custom scenario
Matched tags [cyber, privacy, power, water, internet, community, agriculture, home, router, camera, irrigation, network, sensor, equipment, laptop] → 6 sources (5 official).
- Finding related community reports · 10/4/2026, 2:48:07 AM · Custom scenario
10 related reports and 1 note on affected places (only counts are passed on).
- Analyzing dependencies · 10/4/2026, 2:48:06 AM · Custom scenario
Substation → Cell Tower → Village Mesh Router → Orchard Router → Orchard Cooperative · Substation → Cell Tower → Village Mesh Router → Smart Irrigation Controller → Grain Fields · Substation → Cell Tower → Village Mesh Router → Farm Network → Soil Moisture Sensors
- Identifying affected systems · 10/4/2026, 2:48:06 AM · Custom scenario
23 systems across 8 areas: Village Center, South, Central East, North, South East, Central West, South West, North West.
- Understanding the incident · 10/4/2026, 2:48:05 AM · Custom scenario
Cybersecurity incident at Substation (simulated).
- Status changed · 10/4/2026, 2:44:44 AM · Custom scenario
Case marked Resolved.
- Approved · 10/4/2026, 1:31:54 AM · Custom scenario
User approved the plan and data sharing preview.
- Case created · 10/4/2026, 1:31:53 AM · Custom scenario
Approved by user; tracking started.
- Asking for your approval · 10/4/2026, 1:31:49 AM · Custom scenario
Waiting for a person to review the plan and data sharing preview.
- Preparing the report · 10/4/2026, 1:31:49 AM · Custom scenario
Data sharing preview built: 22 systems, counts only, no resident text.
- Explaining the reasoning · 10/4/2026, 1:31:48 AM · Custom scenario
The supplied dependency chains identify shared power and connectivity bottlenecks, while demo posture findings identify potential security weaknesses rather than evidence of compromise. The plan therefore prioritizes authorized verification, safe containment, essential-service fallbacks, and staged recovery before preventive hardening.
- Creating the response plan · 10/4/2026, 1:31:47 AM · Custom scenario
8 steps (6 high priority), citing 6 sources.
- Determining possible impact · 10/4/2026, 1:31:06 AM · Custom scenario
~545 people (demo estimate), 12 services, urgency critical.
- Checking cybersecurity implications · 10/4/2026, 1:31:05 AM · Custom scenario
12 connected digital systems in the chain (Internet, Routers, Cameras, Smart irrigation, Networks, Sensors, Farm equipment, Laptops). Treated as simulated risk, not confirmed compromise.
- Retrieving trusted resources · 10/4/2026, 1:31:04 AM · Custom scenario
Matched tags [cyber, privacy, power, water, internet, community, agriculture, home, router, camera, irrigation, network, sensor, equipment, laptop] → 6 sources (5 official).
- Finding related community reports · 10/4/2026, 1:31:03 AM · Custom scenario
7 related reports and 1 note on affected places (only counts are passed on).
- Analyzing dependencies · 10/4/2026, 1:31:02 AM · Custom scenario
Substation → Cell Tower → Village Mesh Router → Orchard Router → Orchard Cooperative · Substation → Cell Tower → Village Mesh Router → Smart Irrigation Controller → Grain Fields · Substation → Cell Tower → Village Mesh Router → Farm Network → Soil Moisture Sensors
- Identifying affected systems · 10/4/2026, 1:31:01 AM · Custom scenario
23 systems across 8 areas: Village Center, South, Central East, North, South East, Central West, South West, North West.
- Understanding the incident · 10/4/2026, 1:31:01 AM · Custom scenario
Cybersecurity incident at Substation (simulated).
- Status changed · 10/4/2026, 1:12:31 AM · Custom scenario
Case marked Resolved.
- Status changed · 10/4/2026, 1:12:21 AM · Custom scenario
Case marked Resolved.
- Approved · 10/4/2026, 1:12:06 AM · Custom scenario
User approved the plan and data sharing preview.
- Case created · 10/4/2026, 1:12:06 AM · Custom scenario
Approved by user; tracking started.
- Asking for your approval · 10/4/2026, 1:11:50 AM · Custom scenario
Waiting for a person to review the plan and data sharing preview.
- Preparing the report · 10/4/2026, 1:11:50 AM · Custom scenario
Data sharing preview built: 22 systems, counts only, no resident text.
- Explaining the reasoning · 10/4/2026, 1:11:50 AM · Custom scenario
The dependency chains identify the Substation, Cell Tower, and Village Mesh Router as shared upstream dependencies. Demo posture weaknesses justify targeted security checks, while unverified reports and impact estimates support cautious triage rather than incident claims.
- Creating the response plan · 10/4/2026, 1:11:49 AM · Custom scenario
8 steps (7 high priority), citing 5 sources.
- Determining possible impact · 10/4/2026, 1:11:08 AM · Custom scenario
~545 people (demo estimate), 12 services, urgency critical.
- Checking cybersecurity implications · 10/4/2026, 1:11:07 AM · Custom scenario
12 connected digital systems in the chain (Internet, Routers, Cameras, Smart irrigation, Networks, Sensors, Farm equipment, Laptops). Treated as simulated risk, not confirmed compromise.
- Retrieving trusted resources · 10/4/2026, 1:11:06 AM · Custom scenario
Matched tags [cyber, privacy, power, water, internet, community, agriculture, home, router, camera, irrigation, network, sensor, equipment, laptop] → 6 sources (5 official).
- Finding related community reports · 10/4/2026, 1:11:05 AM · Custom scenario
6 related reports and 1 note on affected places (only counts are passed on).
- Analyzing dependencies · 10/4/2026, 1:11:04 AM · Custom scenario
Substation → Cell Tower → Village Mesh Router → Orchard Router → Orchard Cooperative · Substation → Cell Tower → Village Mesh Router → Smart Irrigation Controller → Grain Fields · Substation → Cell Tower → Village Mesh Router → Farm Network → Soil Moisture Sensors
- Identifying affected systems · 10/4/2026, 1:11:04 AM · Custom scenario
23 systems across 8 areas: Village Center, South, Central East, North, South East, Central West, South West, North West.
- Understanding the incident · 10/4/2026, 1:11:03 AM · Custom scenario
Cybersecurity incident at Substation (simulated).
- Status changed · 10/4/2026, 1:05:42 AM · Custom scenario
Case marked Resolved.
- Case created · 10/4/2026, 1:05:02 AM · Custom scenario
Approved by user; tracking started.
- Approved · 10/4/2026, 1:05:01 AM · Custom scenario
User approved the plan and data sharing preview.
- Asking for your approval · 10/4/2026, 1:04:40 AM · Custom scenario
Waiting for a person to review the plan and data sharing preview.
- Preparing the report · 10/4/2026, 1:04:40 AM · Custom scenario
Data sharing preview built: 22 systems, counts only, no resident text.
- Explaining the reasoning · 10/4/2026, 1:04:39 AM · Custom scenario
The supplied graph identifies Cell Tower and Village Mesh Router as shared dependencies, so their failure could propagate across several services. Demo posture concerns justify preventive hardening, not a cyber-incident conclusion. Unverified reports and estimates make operator checks essential before escalation or recovery claims.
- Creating the response plan · 10/4/2026, 1:04:38 AM · Custom scenario
8 steps (5 high priority), citing 6 sources.
- Determining possible impact · 10/4/2026, 1:03:54 AM · Custom scenario
~545 people (demo estimate), 12 services, urgency critical.
- Checking cybersecurity implications · 10/4/2026, 1:03:53 AM · Custom scenario
12 connected digital systems in the chain (Internet, Routers, Cameras, Smart irrigation, Networks, Sensors, Farm equipment, Laptops). Treated as simulated risk, not confirmed compromise.
- Retrieving trusted resources · 10/4/2026, 1:03:53 AM · Custom scenario
Matched tags [power, water, internet, community, agriculture, home, router, camera, irrigation, network, sensor, equipment, laptop, cyber] → 6 sources (4 official).
- Finding related community reports · 10/4/2026, 1:03:52 AM · Custom scenario
4 related reports and 1 note on affected places (only counts are passed on).
- Analyzing dependencies · 10/4/2026, 1:03:51 AM · Custom scenario
Substation → Cell Tower → Village Mesh Router → Orchard Router → Orchard Cooperative · Substation → Cell Tower → Village Mesh Router → Smart Irrigation Controller → Grain Fields · Substation → Cell Tower → Village Mesh Router → Farm Network → Soil Moisture Sensors
- Identifying affected systems · 10/4/2026, 1:03:50 AM · Custom scenario
23 systems across 8 areas: Village Center, South, Central East, North, South East, Central West, South West, North West.
- Understanding the incident · 10/4/2026, 1:03:49 AM · Custom scenario
Power outage at Substation (simulated).
- Case created · 10/4/2026, 12:45:19 AM · Custom scenario
Approved by user; tracking started.
- Approved · 10/4/2026, 12:45:17 AM · Custom scenario
User approved the plan and data sharing preview.
- Asking for your approval · 10/4/2026, 12:45:06 AM · Custom scenario
Waiting for a person to review the plan and data sharing preview.
- Preparing the report · 10/4/2026, 12:45:05 AM · Custom scenario
Data sharing preview built: 22 systems, counts only, no resident text.
- Explaining the reasoning · 10/4/2026, 12:45:05 AM · Custom scenario
The supplied chains identify the Cell Tower and Village Mesh Router as shared dependencies, supporting upstream-first restoration and critical-service fallbacks. Demo posture concerns justify preventive security work, not a compromise finding. Sparse community counts and unverified backups require operational checks before declaring impacts.
- Creating the response plan · 10/4/2026, 12:45:04 AM · Custom scenario
8 steps (6 high priority), citing 6 sources.
- Determining possible impact · 10/4/2026, 12:44:19 AM · Custom scenario
~545 people (demo estimate), 12 services, urgency critical.
- Checking cybersecurity implications · 10/4/2026, 12:44:18 AM · Custom scenario
12 connected digital systems in the chain (Internet, Routers, Cameras, Smart irrigation, Networks, Sensors, Farm equipment, Laptops). Treated as simulated risk, not confirmed compromise.