ClearlySaid Privacy Policy
Effective August 2, 2026
What ClearlySaid processes
ClearlySaid processes your email address, account status, subscription entitlement, usage counts, and the text you ask it to improve. Microphone audio is converted to text by speech-recognition services available on your device or browser; ClearlySaid receives the resulting text.
How message text is used
Your text is encrypted in transit and sent through ClearlySaid's Web01 and API01 services to our privately hosted Ollama model solely to generate the improved response. If that service definitely fails, API01 may send the request to OpenAI as a fallback. ClearlySaid does not save message text in its account database after the response. The usage database records request identity, time, character and estimated token counts, provider, model, latency, fallback use, and outcome, but not the message contents.
Account and purchase information
Passwords are stored only as salted password hashes. Session tokens are stored as one-way hashes. Google Play processes Android purchases; ClearlySaid stores the resulting product and entitlement status, not payment-card information.
Retention and deletion
Account and usage records are retained while your account is active for security, quota, and support purposes. You can permanently disable and anonymize your ClearlySaid account from the account-deletion page. Limited records may be retained when legally required or needed to prevent fraud.
Sharing and security
Information is shared only with infrastructure and AI providers needed to operate ClearlySaid, or when required by law. ClearlySaid uses encrypted connections, restricted private services, rate limits, and access controls, but no online service can guarantee absolute security.
Contact
Privacy and support questions may be sent to [email protected].