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

InformationStoredAI seesCan be sharedRule
Report title & descriptionYes, anonymousNever leaves the app
Report locationApproximate pinOnly area names are used
Report counts per area & categoryComputedIncluded after your approval
Confirmations (“me too”)Hashed device id onlyNever readable, even by admins
Community notes & added infoYes, anonymousOnly the count is used
Infrastructure names, types & linksYesIncluded after your approval
Device security status (demo)YesUsed for analysis only
Impact estimates (demo)ComputedIncluded 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

  1. Case created · 10/4/2026, 4:17:54 AM · Custom scenario

    Approved by user; tracking started.

  2. Approved · 10/4/2026, 4:17:53 AM · Custom scenario

    User approved the plan and data sharing preview.

  3. 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.

  4. Preparing the report · 10/4/2026, 3:30:41 AM · Custom scenario

    Data sharing preview built: 22 systems, counts only, no resident text.

  5. 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.

  6. Creating the response plan · 10/4/2026, 3:30:39 AM · Custom scenario

    7 steps (6 high priority), citing 3 sources.

  7. Determining possible impact · 10/4/2026, 3:29:59 AM · Custom scenario

    ~545 people (demo estimate), 12 services, urgency critical.

  8. 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.

  9. 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).

  10. 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).

  11. 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

  12. 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.

  13. Understanding the incident · 10/4/2026, 3:29:54 AM · Custom scenario

    Cybersecurity incident at Substation (simulated).

  14. Status changed · 10/4/2026, 3:27:51 AM · Custom scenario

    Case marked Resolved.

  15. Status changed · 10/4/2026, 3:27:49 AM · Custom scenario

    Case marked In Progress.

  16. Status changed · 10/4/2026, 3:27:48 AM · Custom scenario

    Case marked Resolved.

  17. Approved · 10/4/2026, 3:09:55 AM · Custom scenario

    User approved the plan and data sharing preview.

  18. Case created · 10/4/2026, 3:09:54 AM · Custom scenario

    Approved by user; tracking started.

  19. 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.

  20. Preparing the report · 10/4/2026, 2:48:52 AM · Custom scenario

    Data sharing preview built: 22 systems, counts only, no resident text.

  21. 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.

  22. Creating the response plan · 10/4/2026, 2:48:50 AM · Custom scenario

    8 steps (7 high priority), citing 6 sources.

  23. Determining possible impact · 10/4/2026, 2:48:10 AM · Custom scenario

    ~545 people (demo estimate), 12 services, urgency critical.

  24. 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.

  25. 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).

  26. 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).

  27. 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

  28. 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.

  29. Understanding the incident · 10/4/2026, 2:48:05 AM · Custom scenario

    Cybersecurity incident at Substation (simulated).

  30. Status changed · 10/4/2026, 2:44:44 AM · Custom scenario

    Case marked Resolved.

  31. Approved · 10/4/2026, 1:31:54 AM · Custom scenario

    User approved the plan and data sharing preview.

  32. Case created · 10/4/2026, 1:31:53 AM · Custom scenario

    Approved by user; tracking started.

  33. 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.

  34. Preparing the report · 10/4/2026, 1:31:49 AM · Custom scenario

    Data sharing preview built: 22 systems, counts only, no resident text.

  35. 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.

  36. Creating the response plan · 10/4/2026, 1:31:47 AM · Custom scenario

    8 steps (6 high priority), citing 6 sources.

  37. Determining possible impact · 10/4/2026, 1:31:06 AM · Custom scenario

    ~545 people (demo estimate), 12 services, urgency critical.

  38. 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.

  39. 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).

  40. 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).

  41. 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

  42. 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.

  43. Understanding the incident · 10/4/2026, 1:31:01 AM · Custom scenario

    Cybersecurity incident at Substation (simulated).

  44. Status changed · 10/4/2026, 1:12:31 AM · Custom scenario

    Case marked Resolved.

  45. Status changed · 10/4/2026, 1:12:21 AM · Custom scenario

    Case marked Resolved.

  46. Approved · 10/4/2026, 1:12:06 AM · Custom scenario

    User approved the plan and data sharing preview.

  47. Case created · 10/4/2026, 1:12:06 AM · Custom scenario

    Approved by user; tracking started.

  48. 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.

  49. Preparing the report · 10/4/2026, 1:11:50 AM · Custom scenario

    Data sharing preview built: 22 systems, counts only, no resident text.

  50. 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.

  51. Creating the response plan · 10/4/2026, 1:11:49 AM · Custom scenario

    8 steps (7 high priority), citing 5 sources.

  52. Determining possible impact · 10/4/2026, 1:11:08 AM · Custom scenario

    ~545 people (demo estimate), 12 services, urgency critical.

  53. 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.

  54. 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).

  55. 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).

  56. 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

  57. 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.

  58. Understanding the incident · 10/4/2026, 1:11:03 AM · Custom scenario

    Cybersecurity incident at Substation (simulated).

  59. Status changed · 10/4/2026, 1:05:42 AM · Custom scenario

    Case marked Resolved.

  60. Case created · 10/4/2026, 1:05:02 AM · Custom scenario

    Approved by user; tracking started.

  61. Approved · 10/4/2026, 1:05:01 AM · Custom scenario

    User approved the plan and data sharing preview.

  62. 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.

  63. Preparing the report · 10/4/2026, 1:04:40 AM · Custom scenario

    Data sharing preview built: 22 systems, counts only, no resident text.

  64. 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.

  65. Creating the response plan · 10/4/2026, 1:04:38 AM · Custom scenario

    8 steps (5 high priority), citing 6 sources.

  66. Determining possible impact · 10/4/2026, 1:03:54 AM · Custom scenario

    ~545 people (demo estimate), 12 services, urgency critical.

  67. 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.

  68. 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).

  69. 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).

  70. 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

  71. 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.

  72. Understanding the incident · 10/4/2026, 1:03:49 AM · Custom scenario

    Power outage at Substation (simulated).

  73. Case created · 10/4/2026, 12:45:19 AM · Custom scenario

    Approved by user; tracking started.

  74. Approved · 10/4/2026, 12:45:17 AM · Custom scenario

    User approved the plan and data sharing preview.

  75. 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.

  76. Preparing the report · 10/4/2026, 12:45:05 AM · Custom scenario

    Data sharing preview built: 22 systems, counts only, no resident text.

  77. 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.

  78. Creating the response plan · 10/4/2026, 12:45:04 AM · Custom scenario

    8 steps (6 high priority), citing 6 sources.

  79. Determining possible impact · 10/4/2026, 12:44:19 AM · Custom scenario

    ~545 people (demo estimate), 12 services, urgency critical.

  80. 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.