claude-local-privacy-reset

name

claude-local-privacy-reset

description

Back up, inspect, and clean local Claude, Claude Code, Claude Desktop, and browser claude.ai state for privacy, troubleshooting, or clean reinstall workflows. Use when the user asks to save Claude data, remove local Claude traces, reset local Claude/Claude Code state, clean Claude Desktop storage, clear browser claude.ai site data, audit Claude local identifiers, or produce path-only cleanup manifests. Do not use to help evade account bans, platform enforcement, fraud/risk systems, or identity detection; keep the work framed as local privacy and device cleanup only.

Claude Local Privacy Reset

Use this skill for cautious local cleanup of Claude-related files. Treat it as privacy/troubleshooting support, not an account-linkage bypass. Never promise that cleanup prevents account association, detection, enforcement, or risk scoring.

Workflow

1. State the boundary: local backup/cleanup only; no evasion guarantees.
2. Ground in the current machine before deleting anything:
   • identify Claude/Claude Code/Claude Desktop paths,
   • check whether Claude or browsers are running,
   • list candidate paths, sizes, and keyword-hit files without printing secret values.
3. Create a timestamped backup folder under the user-selected output directory.
4. Back up user data and state before cleanup.
5. Generate path-only audit files such as manifest.tsv, delete-candidates.tsv, and verification reports.
6. Ask for explicit confirmation before destructive cleanup unless the user has already approved a precise plan.
7. Clean in phases, from safest to more disruptive:
   • Claude Code auth/session/cache state,
   • Claude Desktop cookies/storage/logs/caches,
   • browser claude.ai cookies and origin-named IndexedDB,
   • browser Session Storage only after confirmation,
   • browser Local Storage only after a separate explicit confirmation.
8. Run fresh verification before claiming completion.

Reusable Helper

Prefer the bundled helper for repeatable scans and fixture-safe cleanup:

python3 scripts/claude_local_cleanup.py --backup-root /path/to/output --scan --backup
python3 scripts/claude_local_cleanup.py --backup-root /path/to/output --scan --backup --apply
python3 scripts/claude_local_cleanup.py --backup-root /path/to/output --scan --backup --include-browser-site-data
python3 scripts/claude_local_cleanup.py --backup-root /path/to/output --scan --backup --apply --include-browser-site-data --include-browser-session-storage

The helper intentionally does not delete browser Local Storage. If a user requests that, explain the risk first and require a separate explicit decision.

Detailed Targets

Read references/cleanup-workflow.md before live cleanup. It contains target categories, browser storage decision rules, and verification expectations.

Safety Rules

• Quit relevant apps before deleting state.
• Back up first, delete second, verify third.
• Report paths and counts, not token values, user IDs, OAuth secrets, or cookies.
• Keep app binaries, VS Code extensions, Keychain items, and third-party configs as review-only unless the user explicitly names them.
• If a command needs filesystem or process-list access outside the sandbox, request approval with a narrow justification.