Last updated: 21 November 2026

Privacy Policy

Pyre.Studio ("we", "us", "our") operates Pyre.Chat — the web app at pyre.chat, the Pyre.Chat desktop application, and the Pyre.Chat browser extension. This Privacy Policy explains what information we collect, how we use it, and your rights. It covers the same platform account as Pyre.Stream; the two policies describe one system from two products.

/ 01

Information We Collect

Account Information

When you create an account, we store your chosen username and a securely hashed password. You may also provide an email address — for example, for account recovery and important account notices — which we store if you choose to add it. Providing an email is optional, and we do not collect your real name.

Platform OAuth Tokens

When you authenticate with Twitch, YouTube, or Kick, we receive and store OAuth access tokens and refresh tokens. These tokens are used solely to interact with each platform's API on your behalf to provide Pyre's features, such as reading and sending chat, performing moderation actions and listing channels. We do not access your platform account for any other purpose. The Google & YouTube Data section below lists exactly what we use a Google or YouTube connection for.

Chat Data

Chat messages pass through our server in real time to be delivered to your browser. We maintain a short-lived message buffer for session continuity (so you don't lose messages on page refresh). By default, chat messages are not retained beyond that buffer.

Chat History (off by default, enabled by the streamer)

A streamer can switch on chat history for a channel they own. While it is on, we store the messages sent in that channel and the moderation actions taken there (bans, timeouts, unbans and message deletions), together with the sender's platform username and ID, the channel, a timestamp, and — for a moderation action — the acting moderator, duration and stated reason.

Who decides, and who is responsible. The streamer decides whether history is on for their channel, for how long it is kept, and who may read it. For this data the streamer is the data controller; Pyre.Studio acts as their processor and stores it on their instruction. Chat history is never on by default and we never enable it on a streamer's behalf.

Purpose. Chat history exists so a streamer and their moderators can make an informed moderation decision — seeing what a viewer actually said before acting on them, and seeing what a previous moderator did and why. We do not use it to build advertising profiles, we do not sell it, and we do not share it with third parties.

Who can read it. The streamer; anyone the streamer has explicitly granted moderator access to in their Pyre account; and, on Twitch, anyone who is currently listed as a moderator of that channel. Nobody else — history is not public and it is not visible to other viewers.

How long we keep it. The streamer chooses 7, 30 or 90 days (30 by default). Messages older than that window are deleted automatically by a daily job. We also cap storage at 250,000 messages per account, so a very high-volume channel may hold less than the full period. This is a hard ceiling on what we hold in the cloud.

Imported history. When a streamer first switches history on, we may fetch that channel's recent public messages (roughly the last few hundred lines) from a third-party public service so the feature is useful immediately rather than days later. Those messages were already publicly broadcast in that channel. They are stored under the same retention window as everything else and are labelled “Imported” wherever they are displayed, so it is always clear which lines we recorded ourselves and which we were handed.

Long-term copies live on the streamer's and their moderators' own devices. The Pyre.Chat and Pyre.Stream desktop applications keep an archive on the local computer, and that archive is not time-limited. A streamer's app archives the channels they own; a moderator's app archives the channels they are authorized on. If the streamer revokes a moderator's access — or that person stops being a moderator of the channel — their app stops receiving new messages immediately, but the copy already on their device remains. We have no ability to reach into a private computer and delete it. In practical terms: a moderator may retain a local copy of the chat history from the period they moderated your channel. If you want a local copy removed, that request has to go to the person holding it.

If you are a viewer and you do not want to be recorded. Type !nolog in that streamer's chat. From that moment we stop recording new messages from you in that channel. Moderation actions taken against you — a ban, a timeout, an unban, a deleted message, together with the acting moderator and the stated reason — are still recorded, because those are the streamer's own record of a decision the streamer made, and a moderation log that the moderated party can erase is not a moderation log. To have data we already stored deleted, email privacy@pyre.studio with your platform username and the channel — we will erase it from our servers, and this also covers the other per-viewer data we hold for that channel. Note that this cannot reach copies already downloaded to a streamer's or moderator's own device (see above).

Channels the bot joins without a sign-in. The Pyre.Bot chat bot can join a Twitch channel when its broadcaster types !join in the bot's own channel, or when our team adds it, either at the request of the streamer or a moderator, or to read the channel quietly. In those channels the bot reads public chat and stores the messages, and counts from them, in that channel's chat history, to run commands and the public Pyre stats. The broadcaster can type !pyreoptout in their chat (or in the bot's own channel) to take the channel's name off every public Pyre page and to stop 7stats tracking; the counts stay, without the name. Banning the bot removes it. Any viewer can type !optout in any channel where the bot is present: we then stop tying anything to their name and delete the stored text of their messages, while their messages still count in totals.

Public bot stats

Pyre.Bot shows what it does in the channels it is in, at pyre.bot/stats and on its 24/7 stream:

Someone who plays the fishing game also gets a public fishing profile: gear, titles, totals, biggest fish and the channels they fished in. We never publish the text of any message and never publish fishing odds.

To keep your name off all of it, type !optout and then !confirmoptout in any chat with the bot (!optin brings you back). After that:

A streamer can keep their channel's name off it in Pyre.Bot, under Public profile, Public bot stats. The channel is then still counted in the totals but never named.

Connection & Preference Data

We store which channels you've connected to and your saved channel lists so your setup persists between sessions.

In-App Usage Statistics

For logged-in users of the Pyre.Chat desktop app, we collect in-app usage statistics — such as device operating system and app version — to understand how Pyre.Chat is used and to improve the product. This data is kept first-party and is not shared with third-party analytics services.

/ 02

Cookies & Sessions

We use a session cookie to keep you logged in. This cookie is HTTP-only and secure. We also use Google Analytics (GA4) to understand how Pyre.Chat is used so we can improve it. Analytics and advertising cookies are off by default and load only if you accept them in our cookie banner. You can decline and we keep them off, enforced through Google Consent Mode. We never sell your data.

/ 03

Third-Party Services

Pyre.Chat integrates with the following third-party platforms via their official APIs:

Each platform has its own privacy policy. By authenticating with these platforms through Pyre.Chat, you are also subject to their terms.

/ 04

Google & YouTube Data

Pyre.Chat uses YouTube API Services. When you sign in with Google or connect a YouTube channel, you are also agreeing to the YouTube Terms of Service, and Google's own handling of your data is covered by the Google Privacy Policy. Pyre.Chat, Pyre.Stream and Pyre.Bot share one Pyre account and one YouTube connection: a channel you connect in one is connected in all three.

What we access

Signing in with Google and connecting YouTube currently ask Google for the same permissions, and signing in with Google also connects that account's YouTube channel. In Pyre.Chat, that access is used to read or act on:

The same connection also lets Pyre.Stream and Pyre.Bot run your live broadcasts, stream title and schedule, make the Pyre bot a moderator of your chat, and show your subscriber count, live viewer count and YouTube Analytics figures (views, minutes watched, and the average and peak viewers of each stream). The Pyre.Stream privacy policy describes those uses in full. Pyre does not upload, edit or delete your videos, comments or playlists, and does not read your channel's revenue.

How we use it

We use this data only to provide the features listed above, to you and to the people you give access to in Pyre, such as your moderators. Messages from YouTube chat pass through our server to reach your screen; if the streamer turns on chat history they are kept as described under Chat History above. If a streamer turns on text to speech or the bot's AI replies, the text those features read out or answer is sent to the speech or AI provider that produces the result. We do not sell Google user data, we do not use it for advertising, and we do not share it with anyone else except as needed to provide these features or when the law requires it.

How we store and protect it

Your Google access and refresh tokens are stored encrypted (AES-256-GCM) in our database. Your channel ID, channel name, Google account ID and email address are stored alongside them so Pyre can show them and find your account. All traffic to and from Pyre uses HTTPS.

Your tokens, channel ID, channel name and Google account ID are kept until you disconnect YouTube or delete your account, and your email address until you change it or delete your account. The list of channels you subscribe to is held in memory for up to five minutes and is not saved to our database. How long Pyre.Stream keeps analytics figures is set out in its privacy policy.

How to remove Pyre's access

In Pyre.Chat, open Settings with the gear button and select Disconnect next to YouTube under Platform Accounts. In Pyre.Stream, the same button is under Settings, Connections. Disconnecting deletes your stored YouTube tokens from Pyre and stops every YouTube feature in all three products at once.

Disconnecting in Pyre.Chat also withdraws Pyre's permission on Google's side. You can also remove Pyre from your Google account yourself: open your Google Account's third-party access page and remove Pyre. You can do this at any time, whether or not you disconnect in Pyre.Chat first. If you remove access only on Google's side, the tokens we hold stop working, and they are deleted when you disconnect or delete your account. If you sign in to Pyre.Chat with Google, signing in again connects YouTube again, because sign-in asks for the same permissions.

How to delete your data

Deleting your Pyre account deletes the Google and YouTube data tied to it. In Pyre.Chat, open Settings with the gear button and use Delete Account. Deleting in the app asks for your password. If you signed up with Google and never set one, Pyre.Stream asks you to sign in again instead; you can also email privacy@pyre.studio and we will delete the account for you. Our Account Deletion page explains both routes and how backups are handled. Deleting your account withdraws Pyre's permission on Google's side as well. Questions or complaints about how we handle Google user data can go to privacy@pyre.studio.

Limited Use

Pyre's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

/ 05

Data Storage & Security

Data is stored in an SQLite database on our server. Session secrets and OAuth tokens are protected with industry-standard practices. The server runs behind HTTPS and uses secure, HTTP-only cookies with SameSite protection. Where a streamer has enabled chat history, that data is stored in the same database under the same protections, and is additionally subject to the automatic retention limit described above. Copies held in a streamer's desktop application live on that streamer's own device and are outside our infrastructure. Both Pyre desktop apps (Pyre.Chat and Pyre.Stream) keep this copy in one shared folder named "Pyre" in your account's application-data directory, organized by your Pyre account, so if you run both apps you keep a single archive rather than two partial ones.

/ 06

Browser Extension

The Pyre.Chat browser extension stores your server URL and authentication token in the browser's synced storage. It communicates only with the Pyre server you configure. The extension does not collect browsing history, inject ads, or track your activity outside of supported streaming platforms.

/ 07

Data Retention

Your account data and OAuth tokens are retained as long as your account is active. If you delete your account or an admin removes it, all associated data (tokens, connections, preferences) is deleted. See our Account Deletion page for how to request deletion and what is removed; residual copies in encrypted backups are purged within 90 days. Chat history, where a streamer has enabled it, is deleted automatically after the retention window that streamer selected (7, 30 or 90 days). In channels the bot joined without the streamer signing in, chat history is kept with no automatic deletion until the streamer signs in and picks a window, opts the channel out, or asks us to delete it. A local archive held in a streamer's desktop application is retained for as long as that streamer keeps it, on their own device. The counters behind the public bot stats, including the yearly counters kept per chatter, have no automatic expiry. A chatter who opts out has theirs deleted. To request deletion or ask data questions, email privacy@pyre.studio.

/ 08

Your Rights

You can:

/ 09

Contact

If you have questions about this privacy policy, email us at privacy@pyre.studio.