{"version":"2.1.323","anchor":"privacy-consents-settings-scope-is-registered-in-code-but-sw","canonical_anchor":"privacy-consents-settings-scope-is-registered-in-code-but-sw","heading":"A settings area for privacy consents exists but is switched off everywhere","tier":"soon","area":"Privacy","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/privacy-consents-settings-scope-is-registered-in-code-but-sw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A settings area for privacy consents exists but is switched off everywhere\n\nClaude Code now contains a settings area for privacy consents, but it is turned off in every configuration and does nothing yet\n\n**What**\n\nClaude Code stores settings in separate areas, or scopes, such as one for plugins and one for projects. This build contains a new scope for privacy consents, meaning your choices about privacy. Every one of Claude Code's built-in environment configurations has it turned off, so the scope is never set up and has no effect in this build.\n\n**Why**\n\nNothing changes for you now. A later release could switch the scope on by changing one value.\n\n- Area: Privacy\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"}