Code signing policy
Who signs the Saba-chan Windows release files, how, and what the app sends.
Code signing policy
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
The Saba-chan Windows executables (saba-core.exe, saba-runner.exe, saba-chan-cli.exe, saba-chan-gui.exe, saba-chan-installer.exe) are signed with a code signing certificate issued to SignPath Foundation. Releases published before SignPath Foundation accepted the project are not signed.
How files are signed
- Only files built by GitHub Actions from the source in the public repository are signed. Files built on a personal PC are never signed.
- An approver checks and approves the signing request for every release by hand.
- Every signed file has the product name
Saba-chanand the product version of that release. - Modules and extensions (Python) that the app downloads, and files from other open source projects, are not signed with this certificate.
Team roles
All team members use multi-factor authentication on GitHub and SignPath.
Privacy
The only information the app sends to a system the user did not choose is:
- Update checks: an anonymous ID, the app version, the platform and the update channel are sent to the Saba-chan server (saba-chan.online). The same applies when the module and extension lists are loaded. The installer shows this notice, and automatic update checks can be turned off in the app settings.
The Discord integration, remote daemons and Saba-chan Web exchange data only after the user connects them. When you create a game server, its files are downloaded from that game's distributor (Mojang, Steam and so on), whose own privacy policy applies. See the Privacy Policy for details.
Contact
If you find a problem with a signed file or a security issue, please write to [email protected].