Privacy Policy
Updated October 29, 2026 · Applies to Cuebot, our games and techdaddydigital.com
- Cuebot runs on your computer. Tech Daddy Digital has no Cuebot server and does not automatically receive any of your Cuebot data. We only see what you choose to send us, such as a problem report.
- Cuebot has no analytics, telemetry, advertising or automatic crash reporting. We do not sell or share your data.
- Your sign-ins and API keys are stored encrypted, and are never included in backups.
- Cuebot connects to a service (Twitch, YouTube, Kick, a voice or AI provider…) only to do what you set up, and sends it only what that job needs. A few lookups happen on their own; they are listed below and can be switched off.
- Our games, including The Miki Komori Project, collect no data at all. This website sets no cookies and runs no analytics.
- Who we are
- What Cuebot keeps on your computer
- Connections Cuebot makes on its own
- Accounts you connect
- Google and YouTube data
- Other services you choose
- Your viewers’ data
- How long data is kept
- Problem reports and crashes
- Cuebot’s local servers
- Our games
- This website and email
- Your choices and deleting data
- Your rights
- Children, changes and contact
Who we are
Tech Daddy Digital makes Cuebot, a desktop app for streamers on Windows and Linux, and games such as The Miki Komori Project. “We” in this policy means Tech Daddy Digital. Contact us at [email protected].
Cuebot is software you run yourself. When it talks to Twitch, Google or any other service, it does so from your computer, on your behalf. None of that data passes through us.
What Cuebot keeps on your computer
Cuebot stores everything in its data folder: %APPDATA%\Cuebot on Windows, ~/.config/Cuebot on Linux (the Flatpak keeps it inside its own sandbox folder), or a folder you choose.
- Settings and your setup: actions, commands, timers, decks, variables and module settings.
- Sign-ins and keys: access tokens for the accounts you connect, and API keys, passwords and webhook secrets you enter. They are kept apart from the settings files, encrypted. The encryption key is protected by your operating system: Windows data protection for your Windows account, or your desktop keyring on Linux (GNOME Keyring, KWallet and similar). Where Linux has no keyring, such as a headless server, the key is kept in a file only your user account can read. Sign-ins and keys are never part of a backup.
- Information about your viewers (see Your viewers’ data).
- Logs: one log file per day, recording what Cuebot did. They occasionally contain a viewer’s user name and are deleted after 30 days.
- Backups: a zip of your settings and data (without sign-ins and keys) on every start and before imports. The newest 10 are kept.
- Caches: chat emote lists and images, and models or tools you choose to download (for example a speech-recognition model or Python).
Chat messages and stream events are kept in memory while Cuebot runs (the last 500 of each) and are not written to disk, unless an action you build saves them.
Cuebot test builds up to 0.1.0-rc.1 stored sign-ins unencrypted in the settings files; newer versions encrypt them the first time they start.
Connections Cuebot makes on its own
These happen without you connecting an account. Each sends your IP address to the service, as any internet request does.
| What | Where | What is sent | Turn it off |
|---|---|---|---|
| Update check, once a day | GitHub (api.github.com) | Cuebot’s version number. No identifier. | Support › Updates › “Check on start” |
| Chat emotes | 7TV, BetterTTV, FrankerFaceZ, and Twitch’s and Kick’s image servers | Your channel’s ID once you connect a platform, so your channel’s emotes load; emote IDs when images load | Each provider can be switched off in Cuebot’s emote settings |
Pronouns in chat (Alejo’s pronoun service, pronouns.alejo.io) are off by default. If you turn them on (Chat page › show pronouns), Cuebot sends the Twitch user names of chatters to that service to show the pronouns they set there.
Accounts you connect
When you sign in to a platform, Cuebot receives tokens from it and stores them, encrypted, on your computer. Cuebot signs in through apps registered by Tech Daddy Digital, so you do not need your own developer app; the tokens still go only to your computer. Under Advanced you can use your own developer app instead.
- Twitch: chat, follows, subscriptions, bits, raids, channel-point redemptions and moderation, with the permissions you choose on the Twitch settings page. An optional bot account can send chat and whispers.
- YouTube: see Google and YouTube data.
- Kick: your account, channel, chat, rewards and moderation, through Kick’s API. Live chat is read from Kick’s public real-time service.
- Rumble: your Live Stream API address, and for sending chat a sign-in with your Rumble user name and password. The password goes only to Rumble, as a hash, and Cuebot does not store it; Cuebot keeps Rumble’s session cookie.
- Donation and tip services (StreamElements, Streamlabs, TipeeeStream, TreatStream, Pally.gg, DonorDrive): the token or key you enter, used to receive your tips and events.
Signing out in Cuebot deletes the stored sign-in and, for Twitch, YouTube and Kick, also revokes Cuebot’s access on the platform. Each platform’s own privacy policy covers what it does with your account.
Google and YouTube data
Cuebot uses YouTube API Services. When you connect YouTube, Cuebot asks Google for access to your YouTube account (youtube and youtube.force-ssl). It uses that access only to run the features you use: reading your live chat and broadcast details, sending chat messages, moderating chat, running polls and updating your stream’s title and details. Cuebot does not ask for your email address or contacts.
YouTube data Cuebot keeps about your viewers (their channel IDs, names and the values your actions store for them) is deleted automatically when a viewer has not been seen in your chat for 30 days. Details of your own channel are refreshed each time Cuebot connects and deleted when you sign out.
When you turn on Google Drive backups, Cuebot asks for the drive.file permission. Google limits it to files Cuebot created or that you open with Cuebot; Cuebot only ever uses its own “Cuebot Backups” folder. It uploads its backup zips there, keeps the newest 10, and shows your Google account’s email address on the backups page so you know which account is connected. Backups contain your settings and data but no sign-ins or keys.
Data from Google stays on your computer, and in your own Drive for backups, except where you turn on a feature that needs it elsewhere: for example having a cloud voice read YouTube chat aloud, or letting the setup assistant look at recent chat. Then only what that feature needs goes to the service you chose. Tech Daddy Digital does not receive Google data, sell it or use it for advertising. Cuebot’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
By using Cuebot’s YouTube features you agree to the YouTube Terms of Service. Google’s Privacy Policy applies to what Google receives. You can remove Cuebot’s access at any time on your Google Account permissions page; signing out in Cuebot also revokes it.
Other services you choose
These are off until you set them up, and then send data only to the service you picked. What each service keeps, and whether it uses your data for training, depends on that service and your account settings with it.
- Cloud voices (ElevenLabs, Microsoft Azure, Google, Amazon Polly, IBM Watson, Acapela, CereProc, TTS Monster, Uberduck): the text to be spoken, which can include chat messages and user names you have Cuebot read aloud. Windows voices and espeak-ng run on your computer.
- The setup assistant (Anthropic, OpenAI, xAI or Google with your API key, or an AI app you have installed such as Codex or Claude Code): your messages, and the results of the Cuebot tools the assistant uses to answer. Those tools can show it your actions, commands, timers, global variables, run history and recent chat (including user names). They never give it your sign-ins, tokens or API keys, and nothing is sent until you send a message. An installed AI app runs on your computer but still sends what it receives to its own provider.
- Webhooks and the webhook relay: tips and purchases from Ko-fi, Patreon, Shopify, Fourthwall, Throne and similar services reach Cuebot through a relay you deploy to your own Cloudflare account. The relay holds undelivered events for at most 24 hours.
- Integrations you configure: OBS, Streamlabs Desktop and other stream apps, Elgato devices, Discord or IFTTT webhooks, HTTP requests and scripts in your actions. These send what you tell them to send.
- Downloads you start: Python from GitHub, Python packages from PyPI, speech-recognition models from Hugging Face.
Your viewers’ data
As a streamer you are responsible for your viewers’ data that Cuebot keeps for you. Cuebot stores on your computer:
- a list of chatters with their platform, user ID, names, roles, first and last seen time and message count (no message text);
- per-viewer values your actions keep, such as points and command counts;
- groups, quotes (with who said them) and per-viewer voice settings;
- end-of-stream credits (who followed, subscribed, tipped or raided), reset at the start of each stream.
Viewer information leaves your computer only through features you use: pronoun lookups if you turn them on (Twitch user names), cloud voices (text being read), the assistant (when it looks at chat), Drive backups and problem reports you choose to send.
To delete a viewer, select them on the Users page and choose Forget viewer. That removes them from the chatter list, their stored values, groups, command counts and voice settings, and their name from quotes. Older backups and logs keep what they already had until they are deleted (logs after 30 days, backups as newer ones replace them); restoring an older backup brings that data back.
How long data is kept
| Data | Kept |
|---|---|
| Settings, actions and sign-ins | Until you change them, sign out or delete Cuebot’s data folder |
| Viewers from Twitch, Kick and Rumble | Until you forget them |
| Viewers from YouTube | 30 days after they were last seen in your chat |
| Chat and events | In memory while Cuebot runs (last 500) |
| Logs, saved problem reports, cached emote images | 30 days |
| Crash files | The newest 20 |
| Local backups, Google Drive backups | The newest 10 each (adjustable) |
Problem reports and crashes
If Cuebot crashes it writes a crash file in its data folder; nothing is sent. Support › Report a problem builds a report you can read and edit first. It sends nothing on its own: you can save it, copy it, or open it as an issue on Cuebot’s GitHub repository, where it becomes visible to whoever can see that repository. Reports remove passwords, tokens, keys, email addresses and your account names by default, but not viewer names that appear in log lines, so read the preview before you send it.
Cuebot’s local servers
Cuebot can run servers for stream decks, OBS docks, other apps and AI tools. They listen only on your own computer unless you allow your local network. One is on by default: the AI tools server used by the setup assistant and AI apps you connect. It accepts connections only from your own computer, needs a key, and asks you before anything that deletes. You can turn it off on the Servers page.
Our games
Our games, including The Miki Komori Project, do not collect, store or send any personal data. They have no accounts, analytics, advertising or tracking, and once installed they need no internet connection to play. Anything a game saves, such as your progress, stays on your device.
The store you get a game from (Steam, itch.io, Google Play or the App Store) handles your purchase, download and any reviews you post under its own privacy policy. We see the store’s aggregate statistics, such as download counts and review scores, and public reviews and comments, which anyone can read. Stores do not give us information that identifies their customers.
This website and email
techdaddydigital.com is a static site hosted by Cloudflare. It sets no cookies, runs no analytics and loads nothing from other sites. Cloudflare processes the technical details of each visit (such as your IP address and browser) to deliver the site and protect it from attacks; see Cloudflare’s privacy policy.
If you email us, our email provider, Zoho Mail, handles the message. We use your email only to answer you and keep it only as long as needed for that conversation.
Your choices and deleting data
- Stop a connection: sign out on the service’s page in Cuebot, or revoke Cuebot on the service itself: Twitch connections, Google Account permissions, or your Kick and other account settings.
- Forget a viewer: Users page › Forget viewer (see Your viewers’ data).
- Delete everything: all that Cuebot keeps is in its data folder and backups. Delete those (and the “Cuebot Backups” folder in your Google Drive if you used Drive backups) to remove it all. On Linux, Cuebot’s key also sits in your keyring as “Cuebot stored sign-ins”; you can delete it with your keyring manager.
Your rights
The only personal data we hold ourselves is email you send us and GitHub issues you open. Depending on where you live, you may have the right to ask us for a copy of it, to correct it, to delete it, to restrict or object to how we use it, and to complain to your data protection authority. Write to [email protected]; we answer within 30 days. We use that data only to answer you and to improve our software, which is our legitimate interest. Our email provider (Zoho), GitHub and Cloudflare may process it in the United States and other countries under their own safeguards.
Data Cuebot keeps on your computer is under your control, not ours: use the steps above to see, change or delete it. Your viewers’ requests about their data go to you as the streamer.
Children, changes and contact
Cuebot and this website are not directed at children under 13, and we do not knowingly collect their data. Our games collect no data from anyone, including children.
We will update this policy when how we handle data changes; the date at the top shows the current version, and material changes are noted in Cuebot’s release notes.
Questions: [email protected] · Tech Daddy Digital