Trust Centre · Incidents
Incidents & reporting
One address, two subject tags and a stated acknowledgement target, and how affected customers hear from us after an incident.
Reporting
Report a vulnerability or a privacy incident
| Channel | Detail |
|---|---|
| Contact | hello@axforge.ai, the operational, privacy and security contact. |
| Subject tag | SECURITY for vulnerability reports · PRIVACY for privacy incidents. The tag routes your report to the right review. |
| Acknowledgement target | 2 business days. |
| PGP key | Not published. For a sensitive report, ask for an encrypted channel in your first email. |
| Public status page | Not published. Service-affecting incidents are communicated directly to affected customers. |
- Include what you found, where, and how to reproduce it. Please do not include personal data or live customer content in a report.
Breach notification
Our commitment as a processor
Where AxForge processes personal data on a customer's behalf and a personal-data breach occurs, AxForge notifies the affected controllers without undue delay after becoming aware of it, as GDPR Article 33(2) requires. The controller/processor split (which data falls on which side) is set out in the privacy policy and the Data Processing Agreement.
After an incident
How we communicate afterwards
Affected customers are notified directly, not via a blog post they have to find. The notification covers a timeline of what happened, the impact on their data and service, and the remediation taken.
Related
Nearby in the Trust Centre
Version 1.0 · Effective 2026-09-04 · Last reviewed 2026-09-04
- 2026-09-04, version 1.0: contact routing and communication commitments stated as current practice.
- 2026-08-26: first published version of this page.