{"version":"2.1.314","anchor":"tengu-virtual-toast-now-feeds-a-new-isregulated-check","canonical_anchor":"tengu-virtual-toast-now-feeds-a-new-isregulated-check","heading":"Claude Code gains a check for HIPAA and zero data retention accounts","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/tengu-virtual-toast-now-feeds-a-new-isregulated-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Claude Code gains a check for HIPAA and zero data retention accounts\n\nClaude Code now checks whether an account has HIPAA or zero data retention settings, next to its server-controlled batch waiting setting\n\n**Unclear.** What the new regulated-account check changes for HIPAA or ZDR accounts is not known.\n\n**What**\n\nClaude Code now has a check that answers yes when an account has a HIPAA setting (for handling health data) or a zero data retention (ZDR) setting. It sits next to an existing setting, controlled by Anthropic's server, about whether Claude Code waits for batches. That setting falls back to off when the server sends nothing.\n\nThe batch waiting setting was compiled off by default in v2.1.312. Anthropic's server has answered on for this site's own account since 2026-10-28, which says nothing about any other account.\n\n**Why**\n\nIt suggests that the batch behaviour is being made to depend on whether an account is regulated, such as HIPAA or ZDR accounts.\n\n- Flag `tengu_virtual_toast`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.314; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}