Code signing policy
Last updated: November 1, 2026
This page explains how Sentry Six signs the desktop apps you download from us, who can change the code, and who approves each signed release.
What is signed
- Sentry Studio for Windows: we have applied to the SignPath Foundation for free code signing of the Windows installer and app. Until that is approved, Windows releases are unsigned, so Windows SmartScreen may show a warning on first install.
- macOS builds of Sentry Studio and Sentry Drive are signed with an Apple Developer ID and notarized by Apple.
How releases are built
- Every release is built by GitHub Actions from the public source code at github.com/Sentry-Six/Sentry-Six, from the tagged commit for that version. The build scripts and workflow are part of the repository and are reviewed like any other code.
- Bundled open-source components, such as FFmpeg and Electron, come from their upstream projects at pinned, checksum-verified versions. Their licences ship with the app.
- Each signed release is approved by hand by one of the approvers below before it is signed.
Team roles
- Committers and reviewers: members of the Sentry Six GitHub organization with write access: Scottmg1, ChadR23, JeffFromTheIRS and chufleco. Changes from anyone else arrive as pull requests and are reviewed before merging.
- Approvers: Scottmg1 (Scott Vandereems) and ChadR23 (Jhoan Romero).
- Every team member uses two-factor authentication on GitHub; the Sentry Six organization requires it.
Privacy
What Sentry Studio sends over the network, and when, is described in our Privacy Policy.