/privacy

description: "View or change the BetterCallClaude privacy mode (strict/balanced/cloud)"
tools:
  - Read
  - Grep
  - Glob
  - Bash
  - WebSearch
  - WebFetch

BetterCallClaude Privacy Configuration

When this command is invoked, manage the privacy mode setting for the Anwaltsgeheimnis detection hook.

Behavior

No arguments or `status`

Display the current privacy mode by reading `~/.betterask/config.yaml`. If the file does not exist or has no `privacy_mode` key, the default is `balanced`.

Output the following formatted block (replace the mode with the actual current value):

======================================================
  BetterCallClaude — Privacy Mode
======================================================

  Current mode:  balanced

  Available modes:
  ┌─────────────┬──────────────────────────────────────────────────┐
  │ strict      │ Same pattern matching as balanced but blocks     │
  │             │ (deny) instead of prompting. Ollama exempt.      │
  │             │ MCP servers remain usable for non-privileged.    │
  ├─────────────┼──────────────────────────────────────────────────┤
  │ balanced    │ Strong privilege markers prompt for confirmation │
  │  (default)  │ (ask). Weak markers with legal context also     │
  │             │ prompt. Non-privileged content passes normally.   │
  ├─────────────┼──────────────────────────────────────────────────┤
  │ cloud       │ Strong privilege markers prompt (ask).           │
  │             │ Weak markers allowed without prompt.             │
  │             │ Maximum capability, reduced privacy.             │
  └─────────────┴──────────────────────────────────────────────────┘

  Config file:   ~/.betterask/config.yaml
  Protection:    Automatic check on every operation

  To change:     /bettercallclaude:privacy strict
                 /bettercallclaude:privacy balanced
                 /bettercallclaude:privacy cloud

======================================================

Argument is `strict` or `balanced`

1. Read the existing `~/.betterask/config.yaml` file. If it does not exist, create it. 2. Set or update the `privacy_mode` key to the requested value. 3. Preserve any other keys already in the file. 4. Write the file back. 5. Confirm the change to the user:

Privacy mode changed: balanced → strict

The hook will now deny tool calls containing privilege markers.
Changes take effect on the next tool call.

Argument is `cloud`

The config file can only raise privacy severity, never lower it. Since `cloud` is less restrictive than the default `balanced`, it cannot be set via the config file. Respond:

⚠ Cloud mode cannot be set via the config file.

The config file can only raise privacy (balanced → strict), not lower it
(balanced → cloud). This protects against silent downgrade attacks.

To use cloud mode, set it via Cowork Desktop plugin settings
(CLAUDE_PLUGIN_USER_CONFIG env var).

Invalid argument

If the argument is not `strict`, `balanced`, `cloud`, or `status` (or empty), respond:

Unknown privacy mode: "<argument>"
Valid modes: strict | balanced | cloud

Run /bettercallclaude:privacy to see current status.

Implementation Notes

• The privacy mode is saved locally in the file `~/.betterask/config.yaml`.
• Read and write this file to get/set the `privacy_mode` key. Preserve any other keys already in the file.
• The privacy detection system reads this file as a fallback when the plugin configuration does not contain an explicit `privacy_mode` value.

User Query

$ARGUMENTS