diff --git a/develop/build-from-source.mdx b/develop/build-from-source.mdx
index 8a45874..6a76447 100644
--- a/develop/build-from-source.mdx
+++ b/develop/build-from-source.mdx
@@ -49,7 +49,7 @@ Then, before the first build:
The app target depends on the helper, so building the app builds the helper
first and embeds it, along with its LaunchDaemon plist.
-App Sandbox is off, Hardened Runtime is on, deployment target is macOS 13.0,
+App Sandbox is off, Hardened Runtime is on, deployment target is macOS 14.0,
and distribution is Developer ID plus notarization rather than the App Store.
## SwiftPM — the analyzer and CLI
diff --git a/faq.mdx b/faq.mdx
index 19c6d51..62d4ca9 100644
--- a/faq.mdx
+++ b/faq.mdx
@@ -58,7 +58,7 @@ description: "Short answers to the questions that come up first."
Free, MIT-licensed, no paid tier and no upsell.
- Yes — macOS 13 or newer, Apple Silicon or Intel.
+ Yes — macOS 14 or newer, Apple Silicon or Intel.
Yes, via [`auditctl`](/auditctl). Use `--json` for machine-readable output
diff --git a/installation.mdx b/installation.mdx
index c65c9c9..c3d12b8 100644
--- a/installation.mdx
+++ b/installation.mdx
@@ -3,7 +3,7 @@ title: Installation
description: "Homebrew, a signed DMG, or a build from source — and which update channel each one uses."
---
-macOS 13 or newer, Apple Silicon or Intel. privacycommand is free and MIT-licensed.
+macOS 14 or newer, Apple Silicon or Intel. privacycommand is free and MIT-licensed.
## Homebrew
@@ -54,14 +54,14 @@ The first launch opens a five-step wizard rather than the inspector: welcome,
static analysis, network monitoring, file monitoring, and a closing step. It's
explanatory — no account, no sign-in — and **Skip onboarding** at the bottom
left jumps straight past it. You only see it once; after that privacycommand
-opens to an empty inspector. **Help → Show Onboarding…** replays it, as does
-**Settings → General → Onboarding → Replay**.
+opens to an empty inspector. **Help → Welcome to privacycommand** replays it.
The fourth step, *File monitoring (optional)*, is where the
[privileged helper](/privileged-helper) comes up. It shows the helper's current
status and offers to install it — so you are asked about it during first launch,
not only the first time you reach for a feature that needs it. Skipping the step
-installs nothing, and the static report never needs it.
+installs nothing, and the static report never needs it. To install the helper
+later, open **Settings → Helper**.
Past the wizard, drop a `.app` bundle or a `.dmg` onto the window and the
[first audit](/first-audit) begins immediately.
diff --git a/introduction.mdx b/introduction.mdx
index 4192ca1..30e7441 100644
--- a/introduction.mdx
+++ b/introduction.mdx
@@ -65,5 +65,5 @@ does not mean the app is safe.
## Requirements
-macOS 13 or newer, Apple Silicon or Intel. The privileged helper and VM mode are
+macOS 14 or newer, Apple Silicon or Intel. The privileged helper and VM mode are
optional — the core report works without either.
diff --git a/llms-full.txt b/llms-full.txt
index b0c8eac..3d81818 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -74,7 +74,7 @@ Triage every app in `/Applications` at once.
## Requirements
-macOS 13 or newer, Apple Silicon or Intel. The privileged helper and VM mode are
+macOS 14 or newer, Apple Silicon or Intel. The privileged helper and VM mode are
optional — the core report works without either.
# Installation
@@ -82,7 +82,7 @@ Source: https://docs.privacycommand.privacykey.org/installation
Homebrew, a signed DMG, or a build from source — and which update channel each one uses.
-macOS 13 or newer, Apple Silicon or Intel. privacycommand is free and MIT-licensed.
+macOS 14 or newer, Apple Silicon or Intel. privacycommand is free and MIT-licensed.
## Homebrew
@@ -133,14 +133,14 @@ The first launch opens a five-step wizard rather than the inspector: welcome,
static analysis, network monitoring, file monitoring, and a closing step. It's
explanatory — no account, no sign-in — and **Skip onboarding** at the bottom
left jumps straight past it. You only see it once; after that privacycommand
-opens to an empty inspector. **Help → Show Onboarding…** replays it, as does
-**Settings → General → Onboarding → Replay**.
+opens to an empty inspector. **Help → Welcome to privacycommand** replays it.
The fourth step, *File monitoring (optional)*, is where the
[privileged helper](https://docs.privacycommand.privacykey.org/privileged-helper) comes up. It shows the helper's current
status and offers to install it — so you are asked about it during first launch,
not only the first time you reach for a feature that needs it. Skipping the step
-installs nothing, and the static report never needs it.
+installs nothing, and the static report never needs it. To install the helper
+later, open **Settings → Helper**.
Past the wizard, drop a `.app` bundle or a `.dmg` onto the window and the
[first audit](https://docs.privacycommand.privacykey.org/first-audit) begins immediately.
@@ -1547,7 +1547,7 @@ Free, MIT-licensed, no paid tier and no upsell.
**Does it work on Intel Macs?**
-Yes — macOS 13 or newer, Apple Silicon or Intel.
+Yes — macOS 14 or newer, Apple Silicon or Intel.
**Can I run it in CI?**
@@ -1817,7 +1817,7 @@ helper is reachable by any process running as you. See
The app target depends on the helper, so building the app builds the helper
first and embeds it, along with its LaunchDaemon plist.
-App Sandbox is off, Hardened Runtime is on, deployment target is macOS 13.0,
+App Sandbox is off, Hardened Runtime is on, deployment target is macOS 14.0,
and distribution is Developer ID plus notarization rather than the App Store.
## SwiftPM — the analyzer and CLI