Skip to content

Compliance

Scope

SuperDash is a local-network monitoring tool for broadcast device state. It does not appear to process personal data or payment information.

Findings

  • No PII/PHI detected in code paths or configuration templates.
  • Operational data exposure: /health and WebSocket provide device IPs and states; treat as sensitive operational data.

Compliance Implications

  • GDPR/CCPA/HIPAA/PCI are likely not applicable unless device names or filenames contain personal data.
  • If used in environments with sensitive content, access controls and audit logs should be considered.

Attestation

# Identity
agent_id: audit-compliance
agent_version: "1.0"
protocol_version: "2.0"
# Timing
timestamp: 2026-01-31T17:03:38Z
duration_seconds: 180
# Context
git_ref: e4bb0098264f90d3afc7b5d0f3b5e425d1825761
git_branch: main
working_directory: /Users/david/Documents/GitHub/superdash
# Artefact metadata
artefact: COMPLIANCE.md
phase: 3
status: COMPLETE
# Confidence assessment
confidence: MEDIUM
confidence_notes: "No evidence of PII in code; actual runtime data may vary based on device names/filenames."
# Inputs consumed (with integrity hashes)
inputs_consumed:
- path: README.md
hash: sha256:789f12ded488dcd86fe2c6868edd796a14ae561632a0ce6e974b861b9a4c93d8
- path: server/server.js
hash: sha256:4d09f4acde1032a407f67943d0cd93be1fe10b79a9c07aa3b430cf6dd27b31bb
- path: config.example.json
hash: sha256:84d7cd97ca20377c204fa04038ff90b5bc08eb1855cdee0ded54f061677cb49a
# Commands executed
commands_executed:
- seq: 1
cmd: "sed -n '1,200p' README.md"
exit_code: 0
purpose: "Identify product scope and data types"
output_summary: "Broadcast device monitoring"
- seq: 2
cmd: "nl -ba server/server.js | sed -n '320,380p'"
exit_code: 0
purpose: "Inspect /health data exposure"
output_summary: "Device list includes IPs and states"
# Findings summary
findings:
critical: 0
high: 0
medium: 0
low: 1
info: 1
# Blocking issues
blocking_issues: []
# Handoff
handoff:
ready: true
next_agents:
- report-writer
dependencies_satisfied:
COMPLIANCE.md: COMPLETE
context_for_next: |
No formal compliance obligations detected; operational data should be protected on internal networks.