Get help & contribute
Start with the project's usage and troubleshooting guides. Check its README and release notes for requirements, known limitations, and recent fixes. You can find each project in the Cat Ninth organization on GitHub.
Report a problem
Open the project's GitHub repository and select Issues. Search for an existing report before creating a new one. For mistakes in these guides, use Documentation issues.
Include your app version, operating system, installation format, the steps that trigger the problem, what you expected, and the exact error. A screenshot is useful when the problem is visual.
Add relevant settings, logs, or hardware details requested by the project's troubleshooting guide. Keep the steps short enough for someone else to repeat.
Remove access tokens, passwords, private files, and personal information from screenshots or logs before sharing them.
Privacy and licenses
Both projects now publish privacy notices and code-signing policies alongside their source. Their own source code is licensed under MPL-2.0; third-party components retain their own licenses and notices.
| Application | Privacy notice | License |
|---|---|---|
| GitCat | Local data, credentials, network requests, and controls | GitCat license |
| ClipCat | Recording data, storage, network requests, and controls | ClipCat license |
Local processing does not mean no network activity. GitCat contacts configured Git hosts and services used by enabled features; both apps check for updates automatically. See package signatures for the distinction between updater verification and Windows publisher identity.
Improve a guide
Use Edit this page below any article to propose a correction on GitHub. Small fixes, clearer examples, and updated screenshots are welcome. The documentation README explains local development and the Docusaurus translation workflow.
Work on the applications
Choose a repository from Cat Ninth on GitHub, then read its README and any contribution instructions. Follow that project's setup and validation steps before opening a pull request. For a larger change, discuss the idea in an issue first.