{"version":"2.1.267","anchor":"new-compliance-policy-allow-stats-transcript-scan","canonical_anchor":"new-compliance-policy-allow-stats-transcript-scan","heading":"New compliance policy: allow_stats_transcript_scan","tier":"use","area":"Compliance","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-compliance-policy-allow-stats-transcript-scan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New compliance policy: allow_stats_transcript_scan\n\nA new policy can block the Usage stats view for HIPAA-regulated organizations\n\n**What**\n\nA new compliance policy, `allow_stats_transcript_scan`, controls whether the \"Usage stats\" breakdown is shown. This view is built by scanning session transcripts (records of your conversations) saved locally. The policy joins two existing ones, `allow_usage_transcript_scan` and `allow_skill_doctor_transcript_scan`, and is blocked by default for organizations under HIPAA (healthcare privacy regulation).\n\n**Why**\n\nScanning local transcripts to build usage statistics could expose sensitive information, so organizations subject to healthcare privacy rules now have this specific view disabled rather than left on by default.\n\n- Area: Compliance\n- Names: `allow_stats_transcript_scan`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}