Breach Response & Reporting

1. Incident Response Overview

Opimatic maintains a rigorous, 24/7 Security Incident Response Plan (SIRP) designed to detect, contain, investigate, and remediate any potential security event affecting personal data or platform infrastructure.

In accordance with GDPR Article 33 and 34, as well as global regulatory standards, Opimatic is committed to absolute transparency and rapid notification in the unlikely event of a confirmed personal data breach.

2. Detection, Monitoring & Triage

Our security team utilizes automated monitoring tools, web application firewalls (Cloudflare WAF), and anomaly detection agents across our AWS and containerized environments:

• Continuous Telemetry: Real-time logging of authentication attempts, database access queries, and API gateway traffic.
• Severity Triage: Incidents are immediately categorized upon detection (Low, Medium, High, Critical) based on data sensitivity, volume of affected records, and system exposure risks.

3. Containment & Eradication

Upon confirming a security incident or data breach, our incident response engineers execute immediate containment protocols:

• Access Revocation: Immediate termination of compromised API tokens, user sessions, or compromised IAM credentials.
• Isolation: Quarantine of affected microservices or database clusters to prevent lateral movement or further data exposure.
• Forensic Preservation: Secure capture of server logs, memory dumps, and network traffic traces for root-cause analysis.

4. Regulatory Notification (Within 72 Hours)

As a Data Processor, Opimatic will notify affected Customers (Data Controllers) without undue delay upon becoming aware of a confirmed personal data breach:

• 72-Hour Window: In alignment with GDPR Article 33, notifications are dispatched to controllers well within the 72-hour statutory window to enable timely reporting to supervisory authorities.
• Incident Details Provided: Notifications include the nature of the breach, categories of data subjects impacted, approximate record counts, likely consequences, and remediation steps already taken.

5. Customer & End-User Communication

Where a data breach is likely to result in a high risk to the rights and freedoms of natural persons, Opimatic works in direct coordination with the Customer (Controller) to facilitate clear, direct notifications to affected end-users via email, platform alerts, or other appropriate communication channels.

6. Post-Incident Review & Hardening

Following the resolution of any security event, Opimatic conducts a mandatory Post-Incident Review (PIR) within 14 business days:

• Root cause analysis (RCA) report distributed to executive and compliance stakeholders.
• Implementation of additional technical safeguards, firewall rules, or code patches to prevent recurrence.
• Updates to our security documentation and team response training modules.

7. Reporting a Security Vulnerability or Incident

If you are a security researcher, customer, or partner who has discovered a potential security vulnerability or suspects a data breach involving Opimatic, please report it immediately to our Security Operations Center: