Privacy Policy

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 (reading chat, performing moderation actions, listing channels). We do not access your platform account for any other purpose.

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).

Game Detection & Screen Analysis (off by default, enabled by the streamer)

The Pyre desktop application can watch the game on a streamer's own screen to move ad breaks into quiet moments — between matches, on a halftime, on the countdown before a game starts. This analysis happens entirely on the streamer's own computer. Pyre reads small regions of the screen the game draws its end screens and scoreboards in, decides whether a match just ended, and forgets the frame. The frames themselves are never uploaded, never stored, and never sent anywhere. We do not analyse your webcam, your chat, or anything outside the game's own picture.

What can leave the machine, and only if the streamer asks. A streamer can switch on the detection recorder for a channel they own. While it is on, and only then, Pyre may send us small cropped strips of the game picture — the exact region it was reading — when detection nearly fires or visibly misses, so we can improve the detector for that game. Never the whole screen, never the webcam, never chat. It is off by default and we never enable it on a streamer's behalf; with it off, nothing about the picture ever leaves the computer. The streamer can see exactly what a strip looks like before turning it on.

Who decides, and who is responsible. The streamer decides whether the recorder is on for their channel. For the strips it sends, the streamer is the data controller; Pyre.Studio acts as their processor and stores them on their instruction, to build and improve game-detection packs. We do not use them to build advertising profiles, we do not sell them, and we do not share them with third parties.

How long we keep it, and how to remove it. Strips are capped per channel (a rolling daily limit and a hard total, with the oldest removed once it is reached) and every strip is deleted automatically after 90 days by a daily job. A streamer can delete everything they have sent at any time, immediately, from the Ads settings page — the "Delete what you have sent" button erases their strips from our servers. Turning the recorder off stops any new strip from being sent from that moment on.

Connection & Preference Data

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

Camera (Android Apps)

The Pyre app for Android uses your phone's camera and microphone to stream. What they capture is sent as your live stream to the destinations you choose, and only while you are live or running a test stream. The app also uses the camera to scan the QR code that signs you in; that image is processed on your device.

The Pyre.Chat app for Android uses the camera only to scan the QR code that signs you in. The image is processed on your device and is not uploaded or stored.

In-App Usage Statistics

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

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 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.

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

• Twitch — for chat, moderation, and channel data
• YouTube / Google — for live chat and channel data
• Kick — for chat and channel data
• 7TV — for loading third-party emotes
• Google Analytics — for usage analytics, loaded only with your consent

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

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.Stream and Pyre.Chat) 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.

The Pyre.Chat browser extension stores your server URL and authentication token in Chrome'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.

If a streamer runs the Pyre bot in their Discord server, and you choose to verify yourself with /verify, Pyre stores three things about you: your Discord user id, the Twitch and YouTube accounts Discord itself has verified as yours, and your level progress in that streamer's community. Your Discord display name is encrypted at rest. Pyre reads your Discord connections once, at the moment you approve it, and does not keep your Discord login — the access token is handed straight back to Discord.

No Pyre account is created and none is needed. Verifying does not give Pyre permission to post as you, to read your messages, or to see which other servers you are in.

This data is kept until you remove it or the streamer disconnects their server. You can remove it yourself at any time by running /forget in a server where the Pyre bot is present: Pyre deletes the accounts you linked and takes back the roles it gave you for them. Points, watch time and chat history in a streamer's channel are that streamer's records of their own channel and are covered by the sections above, not by /forget. To ask a question or request removal another way, email privacy@pyre.studio.

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). A local archive held in a streamer's desktop application is retained for as long as that streamer keeps it, on their own device. To request deletion or ask data questions, email privacy@pyre.studio.

You can:

• Request deletion of your account and all associated data
• Revoke Pyre's access from each platform's settings (Twitch, YouTube, Kick)
• Clear your saved channels and connections at any time
• Ask a streamer's channel to stop recording your messages by typing !nolog in their chat
• Request erasure of chat history we hold about you for a specific channel

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