Notarization is not a security audit and not App Review. Apple's security guide says Gatekeeper checks that downloaded software is notarized "to be free of known malicious content", comes from an identified developer, and has not been altered. That is a floor, and users and developers should not read it as a guarantee.
Myth: notarized means Apple approved the app
Fact: Apple's documentation describes notarization as a check for known malicious content. We could not fetch the developer page that lists what the service examines, so avoid describing its internals. What Apple does say is that App Store review and the notarization pipeline are both meant to ensure apps contain no known malware.
Myth: Gatekeeper protects against everything you download
Fact: Gatekeeper verifies three things for downloaded software: identified developer, notarization status and no alteration. It asks for your approval before first launch. Apple also says users can override policies unless a device management service restricts them, and Gatekeeper can be turned off entirely. So the protection is a default, not a wall.
Myth: no warning means safe
Fact: Software can be signed, notarized and still behave in ways you would not want, including after a legitimate developer account is abused. The check looks for known bad content at submission time. It cannot predict later behaviour or what a server tells the app to do after install.
Myth: only malware authors hit Gatekeeper warnings
Fact: Legitimate developers hit them when something in the pipeline is wrong. A file modified after signing, an unsigned helper tool inside a bundle, or a missing notarization ticket on a downloaded copy are common causes. Treat a warning on your own build as a bug in your release process.
What developers should do
- Sign and notarize every release, including installers and the apps inside them.
- Test the download as a user would, from a browser, on a clean Mac.
- Do not modify files after signing.
- Document how users can verify your download, and publish the hash.
- Keep your signing identity protected. A notarized app signed with a stolen identity is still your problem. See where to keep code signing keys.
For the details of what Gatekeeper covers, read what macOS Gatekeeper and notarization check.
What users should do
Download from the official source, read the first launch prompt, and keep Gatekeeper on. If a vendor tells you to disable it to install their app, ask why, and consider walking away.
Why the distinction matters
If your marketing says notarized and users hear approved, you have set up a gap that attackers and critics will use. Be precise in the words on your site. Say signed and notarized, and say how to verify. Pair it with an honest description of what your app does with data. Trust is built from accurate claims, not from badges.
Quick check
Does notarization replace code review?
No. Apple describes it as a check against known malicious content, not a review of your design or code quality.
Can users switch Gatekeeper off?
Per Apple, yes, unless a device management service restricts it.
Sources
Last reviewed: 19 October 2026.
