> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/security.md). # Security Policy ## Supported versions KlassApp is actively developed on the `main` branch of this repository. The hosted product runs on Laravel Cloud at . Security fixes are applied to current `main` and deployed through the project's normal release path. Older forks or unofficial mirrors are out of scope. ## Reporting a vulnerability **Do not open a public GitHub issue for an undisclosed security vulnerability.** Email **** with: * A short description of the issue and its impact * Steps to reproduce, or a proof of concept if you have one * Affected URL, environment (production / staging / local), and approximate discovery date * Your preferred contact method for follow-up Please keep the report confidential until we confirm a fix is available or we agree otherwise. ## What to expect We will acknowledge security reports sent to **** and work with you on next steps. We do not publish a fixed response-time SLA here. If the report is accepted, we will coordinate disclosure timing with you when a fix is ready. If it is declined (for example, out of scope or not reproducible), we will say so clearly. ## Safe harbor We welcome good-faith security research against KlassApp. Do not access or modify other schools' data, disrupt service, or exfiltrate personal information beyond what is needed to demonstrate the issue. Use demo or your own test accounts whenever possible. ## Non-security bugs Product bugs, UX issues, and feature requests belong in GitHub Issues (see `.github/ISSUE_TEMPLATE/`) or can be emailed to ****. --- # 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://klassdocs.gitbook.io/klassapp-documentation/security.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.