{"version":"2.1.321","anchor":"new-user-privacy-prompt-section-and-stricter-email-wording-b","canonical_anchor":"new-user-privacy-prompt-section-and-stricter-email-wording-b","heading":"Stricter instructions about your email address, and email checks now block","tier":"notice","area":"Privacy","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/new-user-privacy-prompt-section-and-stricter-email-wording-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Stricter instructions about your email address, and email checks now block\n\nClaude can get a new privacy section and stricter wording about keeping your email private, and the built-in email check now blocks instead of asking\n\n**Unclear.** What decides which version of the email wording a given session gets is not known.\n\n**What**\n\nClaude Code's instructions to Claude gain a new section named `user_privacy`. The text that tells Claude your email address now has two versions, chosen by a condition:\n\n- New version: tells Claude to treat the address as private information and never share it with outside services without your explicit approval.\n\n- Old version: the earlier wording, which mentions the User-Agent.\n\nSeparately, the built-in check that looks for an email address in what Claude sends to a tool now blocks the action instead of asking you. It also now spots `%40`, the encoded form of @ used in web addresses.\n\n**Why**\n\nClaude handles your email address more carefully, and an email address in a tool's input is now refused outright rather than put to you as a question.\n\n- Area: Privacy\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}