Before contacting support
- For connection commands and authentication, see the installation guide.
- For what is collected and sent, see trust and data flow.
- For personal-data questions, retention and choices, see the privacy notice.
- For model review expectations and limits, see the second-opinion guide.
What to include
Include the client name—Codex, Claude Code or Hermes—the step that failed, the exact error text with secrets removed, and whether you used guest or account access. For an opinion or billing question, include the request reference displayed by the service. Do not attach repository contents unless support explicitly provides a safe, necessary process.
Privacy and deletion requests
State the right or request you want to exercise and include enough information to locate the relevant guest or account records. Khimba may need to verify that the records belong to you. Some transaction, abuse-prevention or legal records may need to be retained.
Security and corrections
Report suspected vulnerabilities privately by email with reproducible, non-destructive detail. Do not test against other users or access data that is not yours. If a public page contains an inaccurate product claim, include its URL and the specific correction. Material corrections are recorded in the changelog.
AI and emergency limitations
Khimba support cannot validate an AI opinion as professional medical, legal, financial or safety advice. The product is not an emergency service. Contact the appropriate qualified professional or local emergency service when real-world safety is at risk.