Because ClearTone is an offline-first desktop executable running locally on your workstation, data handling is strictly limited to user-initiated actions:
| Data Category | How It Is Handled | Where It Stays |
|---|---|---|
| Highlighted Text | Captured in system memory solely when you click the badge or press Alt + G. Sent directly to Groq Cloud API for tone/grammar inspection. |
Never stored. Cleared from memory immediately after the suggestion card is displayed or dismissed. |
| Groq Cloud API Key | Entered by you during first-time launch setup. Used to authorize direct TLS inference requests with Groq. | Stored locally in your Windows user profile at %APPDATA%\ClearTone\config.json. Never transmitted to Bossrod. |
| Application Logs | Diagnostic execution timestamps and status codes generated for troubleshooting (e.g., rate limits or API connectivity). | Stored locally at %APPDATA%\ClearTone\logs\cleartone.log. Automatically capped at 6MB. Never uploaded anywhere. |
| Keystrokes / Typing | ClearTone does not contain keyloggers or background typing trackers. | N/A (Not tracked or captured). |
Traditional writing assistants route every keystroke through their own centralized backend servers. In contrast:
https://api.groq.com/openai/v1/chat/completions).ClearTone includes hard-coded, client-side safety guardrails that run locally before any request is assembled:
control.IsPassword == True. If so, ClearTone suppresses itself and immediately aborts capture.Pass: or Pass=) are blocked from being sent to the AI engine.Because ClearTone does not store any of your data on remote servers:
%APPDATA%\ClearTone.ClearTone.exe. No residual services or background daemons are left behind.If you have questions regarding ClearTone's architecture, security implementation, or this privacy policy:
• Email: contact@bossrod.com
• Releases & Issue Tracker: github.com/roddan-hue/cleartone-releases/issues