Trust & Compliance
Incidents
Responsible incident management and communications during pilot.
Purpose
This page explains how UmamiMind detects, manages, and communicates incidents impacting availability, security, or data integrity, balancing transparency with responsible disclosure.
Severity levels
- Low — no customer impact, internal issue only
- Moderate — limited or degraded functionality
- High — material impact to service or data
- Critical — widespread or severe impact requiring immediate action
Response process
- Detection and triage
- Assessment of scope and impact
- Containment and mitigation
- Communication to affected parties as appropriate
- Resolution and recovery
- Post-incident review and remediation tracking
Pilot communication
During pilot, incident communication is targeted to affected design partners. Public summaries may be limited; detailed reports and evidence are shared under NDA via the Trust Pack process.
Reporting issues
Security findings should be reported through Responsible Disclosure. Operational concerns should be routed through designated support channels.
Pilot-stage notice
Formal public incident histories and SLA-backed reporting are introduced at General Availability.