{"version":"2.1.321","anchor":"privacy-settings-command-can-redirect-to-claudeai-behind-an","canonical_anchor":"privacy-settings-command-can-redirect-to-claudeai-behind-an","heading":"Privacy settings can open on claude.ai, and hosts can record a privacy checkup","tier":"soon","area":"Privacy","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/privacy-settings-command-can-redirect-to-claudeai-behind-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Privacy settings can open on claude.ai, and hosts can record a privacy checkup\n\nBehind a switch, `\/privacy-settings` can send you to claude.ai, and apps embedding Claude Code can record a privacy checkup as shown or dismissed\n\n**What**\n\n- The `\/privacy-settings` command can now, behind a switch, print \"Review your privacy settings on claude.ai\", name your account and open your browser instead of showing the in-terminal privacy dialog. Before, it always showed the dialog.\n\n- Apps that embed Claude Code through its SDK (a toolkit for building on it) can send a `privacy_checkup_record` event reporting a privacy checkup as shown or dismissed. This works only for SDK clients.\n\n- New `privacyCheckup` and `privacyCheckupReports` hooks back these.\n\n**Why**\n\nWhere the switch applies, you review privacy settings on the web rather than in the terminal, and embedding apps can show their own privacy checkup.\n\n- Area: Privacy\n- Names: `\/privacy-settings`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}