Case: Privacy Guard Config Read

Star on GitHub Compare Workflows Case Library

When to Use

Use this before sharing config files that may include keys, tokens, cookies, or session-like data.

Run

Check status:

aios privacy status

Read sensitive file via redaction path:

aios privacy read --file config/browser-profiles.json

Optional local model enhancement:

aios privacy ollama-on

Evidence

1. Output is redacted and does not expose raw secrets.
2. Config intent remains readable for troubleshooting/review.
3. privacy status confirms strict mode is enabled.

Why This Matters

Teams often leak secrets by pasting raw config into prompts. Privacy Guard turns risky reads into a repeatable safe default.

Star on GitHub