Incident Response Policy
Last updated: July 27, 2026
Version: 1.0
Effective Date: July 27, 2026
On this page 8 sections
1. PURPOSE
This policy describes the framework Saees uses to identify, contain, investigate, recover from, and learn from security incidents and material service incidents.
2. INCIDENT TYPES
Incidents may include unauthorized access, credential compromise, data exposure, malware, service outage, data integrity issue, abuse, marketplace integration compromise, or material provider failure.
3. DETECTION AND TRIAGE
Reports may come from monitoring, personnel, Customers, researchers, providers, or authorities. Saees validates reports, assigns an owner, assesses severity and scope, preserves relevant evidence, and determines whether escalation is required.
4. RESPONSE PHASES
Response may include preparation, identification, containment, eradication, recovery, communication, evidence preservation, post-incident review, and corrective action tracking.
5. COMMUNICATION
Saees communicates with affected Customers, authorities, providers, and other parties when required by law, contract, or risk. Notices are sent through appropriate channels and may include known impact, mitigation steps, and recommended Customer actions.
6. CUSTOMER COOPERATION
Customers should report suspected incidents to security@saees.ai, preserve relevant logs, protect credentials, avoid deleting evidence, and follow containment instructions. Customers should not include passwords or complete secret values in reports.
7. POST-INCIDENT REVIEW
Material incidents may receive a documented review covering timeline, impact, cause, mitigation, corrective actions, and prevention. Enterprise Customers may request a report where permitted by contract, confidentiality, security, and legal restrictions.
8. CONTACT
Security incidents: security@saees.ai
Amazon-related security information may also require reporting under applicable marketplace requirements.
Saees LLC, 4730 University Wy NE, Seattle, WA 98105
