← Back to Home

Data Governance & Ethics Framework

ISS LLC / SecureAssure Platform Governance Documentation | Zero-Trust | CMMC 2.0 Level 2 | NIST CSF 2.0 | Last Updated: March 2026

1. Data Governance Charter

Purpose

This charter establishes the principles, policies, and procedures governing the collection, processing, storage, and sharing of data across all SecureAssure products (SHIELD PWA and ATLAS platform). Built on zero-trust architecture with MOSA-compliant data governance and mission-based cyber risk assessment (DoWM 5000.103). Our commitment is to responsible data stewardship that prioritizes user safety while respecting privacy and civil liberties. CMMC 2.0 Level 2 compliant.

Principles

Data Minimization: Collect only data essential for the specific safety function requested by the user. No persistent tracking. No behavioral profiling for advertising.
User Sovereignty: Users own their data. Full export and purge capabilities available through the Data Ownership Dashboard. No vendor lock-in.
Transparency: Every permission request explains what data is accessed, why it's needed, and how it's used. No hidden data collection.
Local-First Processing: Sensor data (accelerometer, microphone, Bluetooth, GPS) is processed on-device whenever possible. Raw sensor data is never transmitted to servers without explicit user action.
Proportional Response: Safety features escalate proportionally. Panic button shares location; passive features do not. Each feature clearly documents its data scope.

2. Privacy Impact Assessment Summary

Data Collection Matrix

Data Type	Purpose	Storage	Sharing	User Control
GPS Location	SafeWalk, panic alerts, geofencing	Local device only (unless shared via panic)	Emergency contacts only on trigger	Permission toggle, per-session
Accelerometer	Fall detection, gait analysis	Local device only	Never shared	Feature toggle
Microphone	SmokeGuard (3-4kHz alarm detection)	Not recorded; frequency analysis only	Never shared	Permission toggle
Bluetooth	Tracker detection (AirTag, Tile, etc.)	Scan results stored locally 24h	Never shared	Per-scan activation
Network Info	TravelSafe, signal monitoring	Local device only	Never shared	Feature toggle
Interaction Metrics	Cognitive overload protection	Local device only (localStorage)	Never shared	Full purge via Data Dashboard
Community Reports	CrowdShield safety intelligence	Server (PostgreSQL, 365-day retention)	Anonymized to community	Anonymous submission, no PII
Phone/URL Reputation	Misinformation filter, trust layer	Server (crowd-sourced database)	Aggregated scores only	Voluntary reporting

No biometric data is stored. Gait analysis computes cadence averages locally. Audio analysis extracts frequency patterns without recording. Bluetooth scans identify device signatures without pairing.

3. Abuse Prevention Framework

CrowdShield Moderation System

The community reporting system (CrowdShield) implements multiple layers of abuse prevention:

Rate Limiting

Maximum 10 reports per hour per IP address. Prevents spam flooding and automated abuse. Rate limits applied at the API gateway level.

Community Voting

Reports are subject to upvote/downvote by the community. Trust scores calculated as (upvotes - downvotes). Higher-scored reports surface; low-scored reports suppressed.

Automatic Flagging

Reports automatically flagged when: 3+ downvotes received AND downvotes outnumber upvotes by 3:1 ratio. Flagged reports removed from active feed.

IP Tracking

Reporter IP addresses recorded (not displayed publicly) for abuse investigation and potential IP-level blocking of persistent bad actors.

Misinformation Filter Governance

URL reputation checks use crowd-sourced database, not censorship lists
Brand impersonation detection uses fuzzy regex matching against known domains
Text analysis flags manipulation patterns (urgency, fear, authority exploitation) without content censorship
Users can dispute classifications and submit corrections
No automated content blocking; all results are advisory with color-coded risk indicators

4. Ethical Use Policy

Permitted Uses

Personal safety monitoring and emergency preparedness
Community safety reporting and awareness
Emergency management and disaster response coordination
Infrastructure resilience assessment and climate adaptation planning
Training exercises and readiness evaluation
Academic research with appropriate IRB approval

Prohibited Uses

Surveillance of individuals without their knowledge or consent
Harassment, stalking, or intimidation via community reporting features
Filing false safety reports or swatting
Discriminatory profiling based on race, religion, national origin, or protected characteristics
Commercial data harvesting or resale of platform data
Circumvention of access controls or security mechanisms

Violation Consequences: Users who violate the ethical use policy are subject to IP-level rate limiting, report flagging, and potential platform access restriction. False community reports are a violation of the Terms of Service.

5. Liability & Disclaimers

Emergency Services: SHIELD's panic button facilitates but does not replace calling 911. Users should always contact emergency services directly when possible.
Sensor Accuracy: Safety features (fall detection, smoke alarm detection, tracker scanning) use consumer device sensors with inherent limitations. They supplement but do not replace dedicated safety equipment.
Community Reports: CrowdShield reports are user-generated and unverified. SecureAssure does not guarantee the accuracy of community-submitted safety intelligence.
Navigation: Alternative navigation methods (celestial, dead reckoning) are decision-support tools. They supplement but do not replace professional navigation equipment.
Data Feeds: Federal data feeds (NASA, FEMA, USGS, NOAA, CISA) are provided by their respective agencies. SecureAssure does not guarantee their availability, accuracy, or timeliness.

6. Third-Party Data Handling

Third Party	Data Flow	Purpose	User Data Shared
NASA FIRMS	Inbound only	Active fire detection	None
USGS	Inbound only	Earthquake monitoring	None
NOAA NWS	Inbound only	Weather alerts	None
FEMA	Inbound only	Disaster declarations	None
CISA	Inbound only	Cyber threat intelligence	None
Stripe	Bidirectional	Payment processing	Email, payment info (Stripe-managed)
CDC PLACES	Inbound only	Community health data	None
US Census	Inbound only	Social vulnerability index	None

All federal data feeds are public APIs with no authentication required. No user data is transmitted to any federal agency. Stripe handles payment data under PCI DSS Level 1 compliance; SecureAssure never stores credit card numbers.

7. Community Moderation Board

Structure

As the platform scales, SecureAssure will establish a Community Safety Advisory Board with the following composition:

2 platform engineers (abuse detection, data integrity)
1 privacy/civil liberties advocate
1 emergency management professional
1 community representative (rotating, elected by active users)
1 legal advisor (liability, compliance)

Board Responsibilities

Review flagged content and moderation disputes quarterly
Approve changes to abuse detection thresholds
Evaluate ethical implications of new features before release
Publish annual transparency report (reports filed, flagged, removed, false positive rate)
Recommend policy updates to the data governance charter

8. Civilian/Defense Separation Governance

SecureAssure maintains strict separation between civilian and defense capabilities:

Default Mode: Civilian Resilience

All users see only civilian MOSA-compliant modules by default. No military terminology, no defense-specific features, no restricted content. This is the platform as presented to investors, grant reviewers, and the public. FEMA/NIMS aligned.

Defense Mode: Zero-Trust Access-Gated

Defense capabilities require zero-trust authentication via zero-trust access gate. JADC2-aligned, DDIL-capable. When activated, the interface clearly labels the operating mode. Defense features are additive with full-stack congruence; they do not modify civilian data or workflows. CMMC 2.0 Level 2 compliant.

Data Isolation & Congruent Architecture

Civilian and defense operations share MOSA-compliant infrastructure with zero-trust logical data separation and full-stack congruence. Defense-specific data (tactical overlays, mission plans) is stored in separate namespaces. Mission-based cyber risk assessment (DoWM 5000.103) governs classification boundaries.

Documentation

All public-facing documentation, marketing materials, grant applications, and investor communications use civilian framing exclusively. Defense documentation is maintained separately and distributed only to authorized stakeholders.

9. AI Governance & Federated Machine Workforce

Context: The Federated AI Imperative

The Pentagon, CIA, and DIA are building a federated machine workforce where AI agents operate as "coworkers" embedded in intelligence, cyber, planning, and mission execution workflows (April 2026). The core question is no longer "Can AI help?" but "Who owns judgment, authority, and responsibility once AI is embedded inside mission workflows?"

SHIELD/ATLAS addresses this through an AI audit engine (Anthropic Claude) and human-in-the-loop gates that maintain sovereign control over AI decision chains. The architecture supports multiple providers, but only Anthropic is currently active; pay-per-use providers (OpenAI/OpenRouter, Perplexity) are disabled per program directive 2026-04-23.

Human Judgment as Mission Assurance

"Appropriate human judgment" is now a formal Mission-Assurance requirement. As autonomy scales, governance must scale with it. SHIELD/ATLAS implements this through:

AI Cross-Validation Architecture

The audit framework supports independent validation by multiple AI providers. Currently only the Anthropic Claude lane is active; OpenAI, Gemini, and Perplexity lanes are off pending program reactivation. Human review is mandatory before any kill-chain promotion.

Cryptographic Audit Chain

SHA-256 hash chain records every AI decision, input, output, and human override. Tamper-evident governance chain-of-custody from sensor input to commander decision. Full accountability trail.

Human-in-the-Loop Gates

Kill chain transitions from TRAJECTORY to COUNTER-FIRE require explicit human authorization. AI recommends, humans decide. The gate cannot be bypassed programmatically.

Sovereign Federated Architecture

No single-vendor AI dependency. The multi-provider architecture ensures operational continuity even if one AI provider is compromised, sanctioned, or experiences outage. America needs a sovereign AI stack, not single-vendor dependency.

AGOS Decision Framework

The AI Governance Operating System (AGOS) provides real-time oversight of all AI agent actions within the platform:

Decision Logging: Every AI agent action is logged with timestamp, context, confidence score, and reasoning chain
Human Fallback Triggers: Automatic escalation when AI confidence drops below threshold, when providers disagree, or when the decision involves lethal force authorization
Export Control Screening: AI outputs are screened for ITAR/EAR compliance before distribution
Data Retention Policy: AI decision logs retained for 7 years per DoD 5015.02 records management requirements

Mission Assurance Rule: Governance must scale as autonomy scales. Every increase in AI agent authority requires a corresponding increase in audit depth, human oversight frequency, and accountability documentation. This is not optional — it is a Mission-Assurance requirement.

BRIEF CHEATSHEET

TF DAGGER · ONE FIGHT · 9 STEPS

UNCLASSIFIED // FOR OFFICIAL USE ONLY

Greg Funk Teams brief · 29 APR 2026 1000 EDT · ISS LLC / Dr. Terry Flood / CAGE 9VKK3

OPENING (30 sec)

"One fight, one screen. TF DAGGER, hostile UAS swarm bearing 270, 22km. PTDS-1 has it. ALPHA-1 through 8 are airborne, BRAVO-6 is C-RAM, CHARLIE-1 is on shore, LOG-1 is the tail. I'm going to walk you the kill chain end to end — sensor to shooter to BDA — in nine steps."

THE 9 STEPS · CLICK EACH

1. DETECT — Swarm C2

"PTDS-1 picks up 4 hostile UAS. ALPHA-1..8 receive cue at H+0."

2. CLASSIFY — CRAM Dashboard

"BRAVO-6 confirms hostile UAS, declares THREATCON RED at H+1."

3. FUSE — DoD Common Op Picture

"All four domains on one screen. Land/air/sea/cyber. No swivel-chair."

4. EXTEND — Maritime Domain

"CHARLIE-1 sees the surface threat. AIS + radar + visual cross-cue."

5. PRIORITIZE — Commander Dashboard

"Critical/High/Med/Low live counts. Commander sees the queue."

6. ASSESS — DIME-PMESII

"Operational Environment overlay. Diplomatic / Info / Mil / Econ options."

7. LOCATE — Peer Geolocation

"GPS-denied. Multi-node TDOA. Covariance ellipse on the map."

8. DECIDE — Intel Fusion

"AI never authors lethal numbers. Human-in-loop for every kinetic call."

9. ACT + BDA — Brief Runbook (full script)

"LOG-1 closes the loop. BDA back to PTDS-1. One fight, one screen."

SLIDE QUICK-JUMP · DEFENSE BRIEFING DECK

Echelon Break — Strategic / Op / Tactical / Edge

Navy / USMC — EABO, Stand-In Force, POSEIDON

Army — ADOC complement, BCT-down, ATAK

Air Force — ABMS, ACE, AOC-edge node

Space Force — SDA, LEO-PNT, Spectrum/EW

Firestorm Labs — xCell + Tempest + Swarm C2

Link 16 / J-Series / COMSEC posture (plain English)

This Week · What's Done / In Flight / On Deck

Single source of truth post-Greg-Funk brief. POC targets (Jaded Thunder Visceral, Booz Allen, EUD) tracked here, not as sales slides.

IF ASKED: LINK 16 / COMSEC — PLAIN ENGLISH

If you only remember one line:
"We don’t transmit on Link 16, and we don’t hold the secret keys. We read a translated unclassified copy that the unit’s government-owned translator box hands us."

If pressed for more:
• Link 16 is the military’s classified group-chat for jets, ships, ground — you need an encrypted radio (MIDS) and the day’s secret keys to talk on it. We have neither. We don’t need either.
• The unit’s person who safeguards those keys (the COMSEC custodian) keeps that job. We change nothing about their security setup.
• The unit also has a government-owned translator box that copies Link 16 messages to the unclassified side. We read from that box. We never write back into the secret side.
• What we add: we mix those tracks with our 9,500+ aircraft and 12,000+ ship feeds onto one map and give the commander a clean picture with a decision queue.
• If the translator goes dark we keep running on commercial feeds and clearly label the Link 16 picture as stale. No silent failures.

Why it matters to them: "Days to stand up, not 18 months. No new accreditation. No new keys. No new custodian. Their security chain is unchanged."

HARD RULES — SAY THESE

• "No FedRAMP, no IL-5, no CAC, no SIPRNET, no FIPS, no ATO — this is unclas commercial."
• "AI never authors ballistic numbers. Lethal calls are human-in-loop."
• "468 docs in the RAG corpus. No live web fetch."
• "SDVOSB-pending, CAGE 9VKK3."

CLOSING (15 sec)

"That's the kill chain. One screen, nine steps, every domain. Lattice gives you a map; we give you the fight. Cost? A fraction of a prime program. Standards? Open. Schedule? Today. Let me know what you want to drill into."

Press ESC or click X to close · Drawer is overlay-only, won't navigate away