For macOS applications distributed outside the Mac App Store, two terms appear frequently: code signing and notarization. Both help macOS evaluate an application's origin and security state, but they serve different purposes.
What code signing does
A signed application contains a cryptographic signature from the developer. macOS can verify whether the application has been modified since signing and which developer signed it.
What a Developer ID is
For applications distributed outside the Mac App Store, Apple uses Developer ID certificates. A registered developer can use one to sign software for direct distribution.
What notarization means
During notarization, the signed application or distribution package is submitted to Apple. Apple performs automated checks and issues a notarization ticket when the submission passes.
What stapling means
The notarization ticket can be attached to the application or installer. That allows macOS to verify notarization even when Apple's online service is temporarily unavailable.
Signed does not automatically mean safe
A valid signature primarily confirms origin and integrity. It does not prove that the application contains no vulnerabilities or problematic behavior.
Direct downloads can still be trustworthy
A correctly signed and notarized application can be distributed outside the store while still being evaluated by macOS.
Priviot
For directly distributed Priviot macOS applications, signing and notarization should be part of the release process. Acceptance for a particular build should separately confirm signature validation, notarization, and Gatekeeper checks.
For more information about data flows, limitations, and product status, see the transparency overview.
Evidence belongs to a specific version
A previously verified build does not automatically prove the state of a later download. Version number, signature, notarization status, and any published checksum need to match the artifact actually being distributed. Priviot changelogs therefore document these claims for specific versions.
Conclusion
Code signing confirms origin and integrity while notarization adds Apple's automated review. Both strengthen the distribution path without replacing secure software development.