# Contact > How to reach the people behind Ragmux — for questions, bug reports, security issues and licensing. Source: https://ragmux.com/contact/ Updated: 2026-10-10 Project: https://github.com/ragmux/ragmux (AGPL-3.0-or-later) --- ## Email — general questions, licensing, anything that does not belong in a public issue. ## Bugs and feature requests Open an issue in the [project repository](https://github.com/ragmux/ragmux/issues). A report that includes the Ragmux version, the provider involved and the request that failed is worth three that do not. Please do not include API keys, `SECRET_KEY`, database URLs or document contents in an issue. Redact them first. ## Security If you believe you have found a vulnerability, do not open a public issue. Use [GitHub private vulnerability reporting](https://github.com/ragmux/ragmux/security/advisories/new) or email . We acknowledge reports within 3 business days and aim to ship a fix or a documented mitigation within 30 days for high and critical issues. Please give us that window before disclosing it. The full policy is on the [security page](/docs/security/). Include what you did, what happened, and the version you tested. A proof of concept helps; please keep it to systems you own or are authorised to test. ## What to expect Ragmux is built by a small team, in the open. Issues are triaged as we get to them, and there is no support contract behind this address. If you need a response on a schedule, say so and we will tell you honestly whether we can meet it.