Bugs and feature requests
Open an issue at github.com/SamuelAlev/control-center/issues. Search the tracker first — the project is young and many reports are already in flight. A good bug report names your platform (macOS, Windows or Linux), the app version (cc_server --version prints the build and git SHA) and what you expected versus what happened.
Security reports
If you believe you have found a security vulnerability, open an issue at GitHub issues and say that it is security-sensitive in the title — the maintainers will arrange a private channel before details are posted. Please do not attach exploit material to a public issue.
Privacy requests
Questions about what the app stores and sends are answered in the privacy policy. For requests that involve personal information you would rather not post publicly, open an issue, say so, and a private channel will be arranged — the policy's contact section describes the process.
Before you write
Most operational questions are already answered in the manual: quick start, how-to guides and the reference section (routes, MCP tools, CLI flags, glossary). The changelog says what changed between versions.