Privacy Controls
GDT keeps your data local and under your control. This page explains what's stored, where, and how to manage it.
Design Principles
Local first. All data stays on your computer. There's no cloud sync, no account system, no data uploaded anywhere except the LLM API calls themselves.
User control. You decide whether to save conversation history. You can disable it, clear it, or delete everything at any time.
Minimal collection. GDT doesn't track usage behavior or collect telemetry. The only data transmitted is what you send to the LLM during conversations.
What Gets Stored
All GDT data lives in ~/.gdt/:
~/.gdt/
├── config.json # Your settings
├── privacy.json # Privacy preferences
├── sessions/ # Conversation history
│ ├── current.json # Current session
│ └── <session-id>.json
├── task-context/ # Task analysis data
│ └── <task-uuid>.json
└── usage/ # API usage logs
└── <date>.json| Data Type | Contents | Can Disable |
|---|---|---|
| Conversation history | Your messages and GDT responses | Yes |
| Task context | Decomposition results, risk analysis | No |
| Configuration | Your preferences | No |
| Usage logs | API token counts | No |
Task data itself is stored by TaskWarrior in ~/.task/, separate from GDT.
Encryption
Conversation history is encrypted by default:
- Algorithm: AES-256-GCM
- Key derivation: PBKDF2
- Scope: Each session encrypted independently
Managing Privacy Settings
View current settings:
> /privacy
📋 Privacy Settings
Conversation history: Enabled
Encryption: Enabled
Data location: ~/.gdt/
Storage usage:
- Sessions: 2.3 MB (15 sessions)
- Task context: 156 KB (42 tasks)
- Usage logs: 12 KB
Commands:
/privacy disable history Stop saving conversations
/privacy enable history Resume saving conversations
/privacy clear history Delete all conversation history
/privacy clear all Delete all GDT data
/privacy status Detailed statusDisable conversation history:
> /privacy disable history
⚠️ Confirm disable conversation history?
After disabling:
- Each startup begins fresh
- Cannot continue previous conversations
- Existing history will be kept (not auto-deleted)
Confirm? [Yes/No]
> Yes
✅ Conversation history disabledClear all history:
> /privacy clear history
⚠️ This will delete:
- 15 session files
- Total 2.3 MB
This cannot be undone. Confirm? [Yes/No]
> Yes
✅ All conversation history clearedWhat Gets Sent to the API
Each LLM call transmits:
- System prompt (GDT's role definition)
- Current conversation messages
- Recent history (if enabled)
- Current task list (formatted summary)
Not transmitted:
- Your full TaskWarrior database
- Historical session files
- Local file contents
- System information
API Provider
GDT uses the Anthropic Claude API:
- Privacy policy: anthropic.com/privacy
- Training: Commercial API data is not used for model training
- Retention: See Anthropic's data retention policy
First-Run Consent
On first launch, GDT asks for explicit consent:
Welcome to GDT!
Before we start, please understand how GDT uses data:
1. Conversation History
GDT can save conversations to maintain context across sessions.
Conversations are encrypted and stored locally, never uploaded.
2. API Calls
Conversation content is sent to Anthropic API for responses.
See Anthropic's privacy policy for details.
Allow saving conversation history? [Yes/No]
> Yes
✅ Setup complete! You can change settings anytime with /privacy.Manual Data Management
View data files:
ls -la ~/.gdt/
ls -la ~/.gdt/sessions/
ls -la ~/.gdt/task-context/Delete all GDT data:
rm -rf ~/.gdt/Delete only sessions:
rm -rf ~/.gdt/sessions/Backup and restore:
# Backup
cp -r ~/.gdt/ ~/gdt-backup/
# Restore
cp -r ~/gdt-backup/ ~/.gdt/FAQ
Does GDT track my usage behavior?
No. GDT collects no analytics or telemetry.
Will my conversations train the AI?
GDT uses Anthropic's commercial API. Per their policy, API data is not used for model training.
How do I keep my data secure?
- Conversations are encrypted with AES-256-GCM
- Data stays on your machine
- Clear history regularly if concerned
Is it safe to use on a work computer?
GDT only transmits data to the Anthropic API. However:
- Conversation content is sent for AI responses
- Check your company's data security policies
- Consider disabling history to minimize local storage
Next Steps
- Configuration — More configuration options
- Commands Reference — Privacy-related commands