See how Dynamic Dialects responds to incidents.
Last updated 2026-09-05. This page describes how Dynamic Dialects detects, assesses, and communicates security incidents and service disruptions that may affect client data or service availability.
- Last updated
- 2026-09-05
- Breach notification
- Within 72 hours of confirmed breach (GDPR aligned)
- Response contact
- info@dynamicdialects.com
1. What we consider an incident
- Unauthorized access to client data or production systems.
- Loss or corruption of client files or project data.
- Service outage affecting delivery timelines or availability.
- Confirmed malware or ransomware presence in production.
- Third-party processor breach affecting DD client data.
2. Detection and assessment
Incidents are detected through hosting monitoring, access-log review, client reports, and third-party alerts. Upon detection, the incident is triaged within 4 hours to assess scope, data affected, and client impact.
3. Containment
Immediate steps include isolating affected systems, revoking compromised credentials, and preserving forensic logs. Client file access is suspended for affected projects until the scope is confirmed.
4. Notification
Affected clients are notified within 72 hours of confirmed breach or significant service disruption. Notification includes: incident summary, data affected, steps taken, and recommended client actions. Regulatory notifications are made where required by applicable law.
5. Recovery and review
Systems are restored from clean backups. A post-incident review documents root cause, remediation steps, and preventive measures. Lessons learned are applied to access controls, retention policies, and vendor review.
6. Reporting a concern
If you suspect a security issue involving Dynamic Dialects, email info@dynamicdialects.com with "Security" in the subject. For sensitive reports, request PGP encryption or a secure call.