Code signing policy
Last updated 7 November 2026
How ClipTrail's installers are signed, who can sign them, and what the signature promises.
Status: Windows code signing through SignPath Foundation has been applied for. Until it is approved, Windows installers are unsigned and Windows shows "Windows protected your PC" (click More info → Run anyway). This page will say when signed builds start.
Windows
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
- Only the Windows installers (
-setup.exeand.msi) built from this repository's source are signed. - They are built by GitHub Actions from a tagged commit on
main, with the release workflow. Nothing is built or signed on a personal machine. - Every release is approved by hand in SignPath before it is signed.
Team roles
| Role | Who | What they do |
|---|---|---|
| Committers and reviewers | abhijitdalal26 (all contributors) | Changes reach main only through reviewed pull requests that pass CI. Contributions from anyone else are reviewed before they are merged. |
| Approvers | abhijitdalal26 | Approves each signing request in SignPath. |
Everyone with these roles uses multi-factor authentication on GitHub and SignPath.
Privacy
This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it. Sync between your own devices, the optional relay and the optional update check only run when you turn them on. See the privacy policy for details.
Other platforms
- Android: the APK is signed with the project's release key, so updates install over each other.
- macOS: the app is ad-hoc signed but not notarized yet; see install notes.
- Desktop updates are additionally signed with the ClipTrail updater key and verified before they install.