> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/trust-security-compliance/incident-response-and-vulnerability-reporting.md). # Report a Vulnerability Report a security vulnerability in Kilo or Chirp software: where to send it, what to include, what testing is allowed. Email **info \[at] kiloiot.de** (replace `[at]` with `@`). We welcome reports of security vulnerabilities in our products and services, and we will work with you to understand and resolve the issue. ## What should the report include? As far as you can: 1. The affected product and version. 2. What the issue is. 3. The steps to reproduce it. 4. The impact you think it has. 5. The name you would like to be credited under, if any. Leave sensitive personal data out of the report. We keep the information about you to the minimum needed and handle it under our privacy and evidence procedures. ## Which products does this cover? Software and services supplied or operated by CHIRP USA LLC, including the Kilo and Chirp platform and the IoT Alerts app. If you report a problem in a product we may not make, we still read and triage it, but that doesn't mean CHIRP USA LLC makes that product. ## What testing is allowed? * Test only against your own account or your own deployment. * Don't access, change or delete anyone else's data. * Don't slow down or disrupt the service. * Don't use social engineering, phishing or physical attacks against our people, buildings or infrastructure. * Give us a reasonable chance to fix the issue before you disclose it publicly. ## What happens after I report? We receive and assess reports sent to that address and work with you to understand the issue. Depending on the product, the company responsible and the event, the law may require the accountable manufacturer or another obligated party to report it to an authority. We protect the sensitive information you shared and coordinate any legally required reporting and user communication. There is no set time for an acknowledgment, a response, a fix, disclosure, support or credit. Don't attach proof-of-concept material to the first email; ask for a protected way to send it. ## Is there a bug bounty? No. There is no bug bounty or payment. This policy does not authorize access to any system or data, and it is not a safe-harbor, non-enforcement or immunity promise. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kiloiot.io/trust-security-compliance/incident-response-and-vulnerability-reporting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.