Last updated: July 30, 2026
CharlyTTS is a Windows desktop application designed for livestream creators. This Privacy Policy explains what information the application accesses, how it is used, and how it is protected.
CharlyTTS is designed to operate primarily on the user’s local computer. It is not a cloud service and does not maintain a centralized database of user accounts or streaming data.
CharlyTTS’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Depending on the streaming platform the user connects, CharlyTTS may access:
The application only requests the minimum permissions required for its functionality.
CharlyTTS does not:
When users connect supported platforms (such as YouTube or Kick), OAuth authentication is used.
Client secrets are not distributed with the desktop application.
A Cloudflare Worker is used only to securely exchange authorization codes for OAuth tokens. The Worker does not permanently store user access tokens or personal information.
OAuth tokens are stored locally on the user’s own computer.
Application settings, configuration files, OAuth tokens, and user preferences are stored only on the user’s local device.
Removing the application or deleting its configuration files removes this locally stored information.
Depending on the features enabled by the user, CharlyTTS may communicate directly with third-party services, including:
These services are governed by their own privacy policies.
Discord features do not use an OAuth consent flow. The streamer manually provides their own Discord bot token, created and authorized by themselves through Discord’s Developer Portal. This token is used only for the optional voice/TTS and notification features the streamer explicitly enables, and is stored locally like any other credential.
Some optional features use external AI providers.
When enabled by the user, chat messages may be sent directly to the AI provider selected by the user for moderation purposes.
The developer does not proxy, inspect, or permanently store these requests.
CharlyTTS has been designed to minimize the exposure of sensitive credentials.
Developer OAuth client secrets are kept outside the distributed application.
Users remain responsible for protecting their own computers and local configuration files.
Users may revoke OAuth permissions at any time through the corresponding platform’s account settings (for example, Google Account Permissions).
Users may also disconnect supported platforms directly from within CharlyTTS.
This Privacy Policy may be updated as the application evolves.
The latest version will always be available from this repository.
For questions regarding this Privacy Policy, please contact the developer at:
charylbotlabs@gmail.com