Send a security concern to Dynamic Dialects.
Last updated 2026-09-25. Use this page to report a suspected issue involving client data or service availability. The facts of the incident, the engagement terms, and applicable law determine the response and any notification duties.
- Last updated
- 2026-09-25
- Report concerns to
- info@dynamicdialects.com
- Notification
- Based on confirmed impact, engagement terms, and applicable law.
1. What to report
- 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. Information that helps assessment
Include when you noticed the issue, which DD service or project may be affected, and any error messages or other evidence you can safely share. A client report, system alert, or third-party notice may require checking the affected systems, data, and service impact before the next steps are known.
3. Containment
Depending on the verified issue, containment may involve isolating a system, revoking credentials, preserving relevant records, or limiting access to affected files.
4. Notification
Whether a client, individual, or regulator must be notified, and when, depends on the confirmed impact, DD's role, the engagement terms, and applicable law. Any notice should distinguish confirmed facts from matters still under investigation and explain actions the recipient may need to take.
5. Recovery and review
Recovery depends on what was affected. It may involve restoring a verified backup, fixing the cause, rotating credentials, and recording what needs to change to reduce the chance of recurrence.
6. Reporting a concern
If you suspect a security issue involving Dynamic Dialects, email info@dynamicdialects.com with "Security" in the subject. For sensitive details or files, request a suitable transfer method before sending them.