> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keldyn.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Report a bug or security issue

> Where to send a security report or a bug report, how fast Keldyn responds first, and what you'll hear back.

There are exactly two addresses for reporting a problem with Keldyn — one for security issues, one for everything else. Both are live mailboxes monitored by the Keldyn team; use the one that fits so your report reaches the right person immediately instead of sitting in a general inbox.

| Report             | Address                                         | Use it for                                                                                                                                                                        |
| ------------------ | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Security issue** | [security@keldyn.ai](mailto:security@keldyn.ai) | Suspected vulnerabilities, unauthorized access, data exposure, or anything that looks like an active security incident — in the platform, the API, or the Keldyn MCP server (KC). |
| **Bug**            | [bugs@keldyn.ai](mailto:bugs@keldyn.ai)         | Incorrect behavior, broken workflows, or anything that doesn't look security-sensitive.                                                                                           |

If you're not sure which one applies, send it to `security@keldyn.ai` — a report that turns out to be a routine bug is easy to redirect; a security issue reported to the wrong place is not.

## Security reports (`security@keldyn.ai`)

* **First response:** acknowledged within **1 business day**.
* **What you'll hear back, and when:** an initial severity and triage assessment within **3 business days** of acknowledgment, then a status update at least every **5 business days** until the issue is resolved or the report is closed. If we need more information to reproduce or assess impact, we'll ask for it in that window rather than let the report go quiet.

Include what you found, how to reproduce it, and its apparent impact. Don't post it publicly or test against other customers' data while we triage.

## Bug reports (`bugs@keldyn.ai`)

* **First response:** acknowledged within **2 business days**.
* **What you'll hear back, and when:** a triage outcome — confirmed, can't reproduce, or not a bug — within **5 business days**, and a follow-up note when a fix ships or if the report is parked, so it doesn't just disappear.

Include what you expected, what happened instead, and enough detail (steps, use case, screenshots) to reproduce it.

## Monitoring

Both `security@keldyn.ai` and `bugs@keldyn.ai` are checked by the Keldyn team on business days. They're separate from general account or usage questions — for those, see [Need help?](/#need-help) or your Keldyn account contact.

## Related

* [Responsible use of the Keldyn Constitution](/responsible-use)
* [Security & privacy](/security-and-privacy)
* [Compliance](/compliance)