Privacy Policy

Effective Date: October 14, 2026

1. Introduction

PixelyChat ("we," "our," or "us") is a free desktop application for live streamers. This Privacy Policy explains what data PixelyChat's desktop application and this website (pixelychat.com) handle, and how.

PixelyChat is built as a local desktop application by design. We do not operate a backend service that stores or processes your chat data, and we don't want to — your streaming data is yours.

2. Information the Desktop App Handles

All of the following stays on your own device, in your operating system's application data folder:

• Authentication tokens: When you connect Twitch, YouTube, or Kick, PixelyChat stores the resulting OAuth access/refresh tokens locally. In installed (non-development) builds, these are encrypted using your operating system's own secure credential storage (Keychain on macOS, DPAPI on Windows, and the equivalent secret storage on Linux where available) via Electron's safeStorage API, so PixelyChat itself never handles the encryption key directly.
• Chat data: Live chat messages, usernames, and related event data (follows, subs, gifts) are fetched from each connected platform solely to display them in the app and in your on-stream overlay. This data is not written to a persistent log or database — it exists in memory while the app is running.
• Settings: Your app preferences (overlay style, TTS voice, translation languages, and so on) are saved to a local configuration file.

None of the above is sold or shared for advertising. It stays on your device, except that chat messages are sent to other services when you turn on a feature that needs them, such as translation, text-to-speech or AI replies (see Section 4).

3. A Note on Our OAuth Relay

Twitch, Google, and Kick's login flows all require a confidential client secret at one step (exchanging or refreshing a token) that a desktop app cannot safely store on its own. To handle just that one step, PixelyChat calls a small relay service we operate. The relay forwards the token request to the relevant platform and returns the result — it does not store access tokens, refresh tokens, or display names. Optionally, on a successful first login it may store an irreversible hash of your platform account id (not the id itself) so we can show approximate unique connected-account counts on our website. Re-logins and token refreshes are not stored again. It exists primarily so a secret value never has to ship inside the app itself.

At most once a day when you use PixelyChat, the app also sends a small usage ping to the relay so we can count how many people use it. It contains a random install id that PixelyChat creates on your computer and that isn't linked to you or any of your accounts, plus your operating system, PixelyChat version and app language. The relay stores only an irreversible hash of the install id together with those details, the day, and your approximate country as determined by Cloudflare. Your IP address is not stored. We only use these numbers in aggregate, for example to show how many people use PixelyChat.

4. Google OAuth & YouTube API Services

PixelyChat uses YouTube API Services. By connecting YouTube to PixelyChat, you agree to be bound by the YouTube Terms of Service. How Google itself handles your data is described in the Google Privacy Policy. PixelyChat's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

When you connect YouTube, PixelyChat requests these scopes:

• openid — identifies your Google account when you sign in. It gives no access to your YouTube channel.
• youtube.readonly — reads information about your own channel, your own broadcasts and your own live chat.
• youtube.force-ssl — lets PixelyChat act in your own channel when you ask it to: posting chat messages, deleting chat messages, banning or timing out chatters, adding moderators and changing your stream title. Google does not offer a narrower scope for these actions.

If you connect a separate YouTube account for the chat bot, PixelyChat requests only youtube.force-ssl for that account and uses it only to post the bot's replies in your chat.

What YouTube data PixelyChat accesses, stores and uses

• Your sign-in tokens: OAuth access and refresh tokens, used to make YouTube requests on your behalf. Stored on your device, encrypted (see Section 2), until you disconnect YouTube.
• Your channel details: channel ID, channel name, handle and profile picture URL. Shown in PixelyChat and used to find your live broadcasts. Stored on your device, refreshed from YouTube at least every 30 days, and deleted when you disconnect YouTube.
• Your Google account ID: read once when you first sign in, so our OAuth relay can count unique connected accounts. Only a one-way hash is kept (see Section 3); the ID itself is not stored.
• Your live broadcasts: video ID, live chat ID, title, category, viewer count and start time. Shown on the Dashboard, in Pilot and in your widgets. Kept in memory only while PixelyChat is running, and not saved.
• Your live chat: the text and type of each message (such as chat messages, Super Chats, Super Stickers and memberships), and each chatter's display name, channel ID, profile picture and badges (such as owner, moderator, member or verified). Shown in PixelyChat and in your overlays and widgets, and used by the features you turn on, such as the chat bot, alerts, text-to-speech and translation. Kept in memory only while PixelyChat is running, and not saved.
• A chatter's channel creation date: fetched only when you open that chatter's profile, and kept in memory until PixelyChat closes.
• Actions you take: the messages you send, messages you delete, chatters you ban or time out, moderators you add and stream titles you change are sent to YouTube. PixelyChat does not keep a record of them.

PixelyChat's log files on your device can include your channel name and stream title. They are deleted automatically after at most 30 days.

PixelyChat never uploads or deletes videos and never changes anything else on your channel.

When YouTube data is shared

PixelyChat only sends chat messages to other services when you turn on a feature that needs them, and only the message text and, where the feature uses it, the chatter's display name:

• Translation: messages are sent to Google Translate or MyMemory to be translated.
• Text-to-speech: messages that are read aloud are sent to Microsoft's online voices, or to ElevenLabs if you connect your own ElevenLabs account. System and offline voices stay on your device.
• AI Chat and Companion: the messages the AI replies to are sent to the AI provider: through our relay to Groq or Google Gemini for the included PixelyChat AI (the relay does not store them), or directly to a provider you connect yourself.

YouTube data is never sold, and never shared for advertising or any other purpose.

Deleting your data

Disconnect YouTube in PixelyChat under Setup → Accounts to delete the stored YouTube tokens and channel details from your device straight away. Uninstalling PixelyChat and removing its application data folder deletes everything else (see Section 7).

You can also revoke PixelyChat's access in your Google Account permissions page. PixelyChat then deletes the stored YouTube tokens and channel details as soon as it next connects to YouTube and finds that access was revoked.

Deleting data stored by PixelyChat does not affect anything stored by YouTube. To delete data on YouTube itself, such as your videos or chat messages, use YouTube or YouTube Studio.

5. Twitch, Kick, and TikTok

Each of these uses a different login mechanism, and we want to be precise about how each one actually works:

• Twitch: Uses Twitch's official OAuth flow, opened in your system's default web browser. PixelyChat never sees your Twitch password.
• Kick: Uses Kick's official OAuth flow, loaded in a login window inside the app that points directly at Kick's own login page. PixelyChat never sees your Kick password — the window is only used to complete Kick's own authorization step, and the resulting session may be remembered for your next login the same way a browser would.
• TikTok: TikTok does not offer a public OAuth flow for third-party apps. PixelyChat opens an in-app window pointed at TikTok's own login page; once you've signed in there, PixelyChat reads your public username to identify your account for connecting to your LIVE chat. PixelyChat never sees your TikTok password.

Chat messages, usernames and related event data from all three are processed on your device to show your unified chat feed. As with YouTube, chat messages are only sent to other services when you turn on translation, text-to-speech or AI replies (see Section 4).

6. Website Data

This website (pixelychat.com) uses Cloudflare Web Analytics to count visits. It doesn't use cookies, doesn't store anything in your browser and doesn't track you across sites or visits. It records aggregate data such as the pages viewed, the referring site, your approximate country and the type of browser and device. The website uses no other analytics, tracking scripts or cookies.

7. Data Retention & Deletion

The daily usage entries and account hashes described in section 3 are stored on the relay's database; they contain no names, account ids, tokens or IP addresses and can't be linked back to you. Nothing else described above is retained on any server we operate. Uninstalling PixelyChat and removing its local application data folder (shown in-app under Logs → Open Logs Folder, or your OS's standard application data location) permanently deletes all locally stored settings and tokens.

8. Security

All communication with platform APIs (Google, Twitch, Kick, TikTok) uses HTTPS/TLS. Locally stored tokens are encrypted using your operating system's own secure storage mechanism via Electron's safeStorage API in installed builds, as described in Section 2.

9. Children's Privacy

PixelyChat is a tool for streamers and is not directed at children under 13. We do not knowingly collect data from children under 13.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected here with an updated Effective Date.

11. Contact Us

Questions about this policy or our data practices are welcome at:

Email: [email protected]