← OneStarLive

Privacy Policy for OneStarLive

Effective Date: November 6, 2026

OneStarLive is a livestream event platform — web services, a Twitch Extension, creator profiles, public event pages, integrations and related tools — operated by OneStarLive ("OneStarLive," "we," "us," "our"). This Privacy Policy explains what information we collect, how we use it, how we share it, how long we keep it, and the choices you have.

This policy applies to OneStarLive, including our Twitch Extension, panels, overlays, shareable event pages, APIs, chat and notification tools, scheduling tools, and related services (collectively, the "Service"). It should be read together with our Terms of Service.

A note on Bits and payments: OneStarLive does not process payments and never receives your payment-card or banking information. Bits transactions are handled by Twitch. When Bits are used through OneStarLive, Twitch gives us a verified record of the transaction so we can update goal progress and provide the feature. Twitch may also pay OneStarLive a developer revenue share out of Bits used through the Extension. See Section 1(D).


1. Information We Collect

A) Information Broadcasters Provide

When you use OneStarLive as a Broadcaster, you may provide:

  • Event content and configuration — event titles, descriptions, goal type and amount, schedule times and timezones, categories, uploaded images, vote options/outcomes, reaction settings, and related metadata.
  • Automation configuration — message templates and, if you enable Discord delivery, a Discord webhook URL you supply. (This webhook URL points to your own Discord channel and is stored so we can post to it on your behalf. It is encrypted, and we use it only to send the messages you asked us to send.)
  • Creator profile content — if you set up a public creator profile: your biography, social handles (YouTube, Kick, TikTok, Instagram, X), custom links and labels, featured media, colour theme, and any profile picture you upload. You choose all of it, and it is shown publicly.
  • Email address — asked for when you set up OneStarLive. It is stored encrypted and used to contact you about your account, changes to the Service and product updates. Every email we send has an unsubscribe link; unsubscribing stops product-update emails (we may still send rare account or legal notices). You can ask us to remove the address at any time.
  • Feedback and support content — messages, bug reports, survey responses, screenshots, or links you submit.
  • Agreement records — when you accept our Terms and this Policy we record which version you accepted, when, and where (the Extension or the website), as proof of agreement. See Section 1(C) for Viewers.
  • Share page privacy settings — which sections of your event pages you have made private, per Event and as defaults on your profile (see Section 1(G)).

Uploaded event images and profile pictures are scanned by an automated moderation service (Amazon Rekognition) for disallowed content. An image that fails the check is rejected rather than stored.

B) Information We Receive From Twitch

When you authenticate or interact with OneStarLive through Twitch, we may receive and store:

  • Broadcaster identity and channel data — Twitch User ID, display name, channel/broadcaster identifiers, profile image, and profile description, used to associate Events, overlays, chat, and features with the correct channel.
  • Twitch OAuth tokens — where you grant permissions (for example, to sync your Twitch schedule or send chat messages on your behalf), we store the resulting access and refresh tokens and their scopes so the Service can act with your authorization. They are encrypted, and we use them only for what you authorised. The permissions we ask for, and what each one is for: managing your schedule (syncing your events to your Twitch schedule); managing your broadcast (setting your stream title and category for an Event, and adding stream markers); creating clips (`!moment` and, if you turn it on, Smart Moments); managing your clips (using your channel's clips, including clips viewers make, on your recap page and in your Moment video, and turning them into captions if you turn on AI summarization); sending chat messages, managing chat settings and sending announcements (posting, pinning and announcing event messages in your chat); reading followers and reading subscriptions (counting new follows and subscriptions during your Events); and reading chat / acting as a chat bot (so chat commands work, and to count chat activity if Chat activity is on). Separately, if you choose to import who you follow, Twitch asks you for permission to read who you follow; we use it once to follow, on OneStarLive, the creators you follow on Twitch who are on OneStarLive (your following list is public, Section 1(F)), keep which creators were imported and when, and do not keep that permission. We do not ask for permissions a feature does not use. You can remove OneStarLive's access at any time in your Twitch settings (Settings → Connections).
  • Viewer interaction identity — for Viewers who interact with an Event, we receive a Twitch Viewer identifier, display name, and avatar (as Twitch makes them available to the Extension).
  • Stream data while an Event is live — whether the channel is live, and its viewer count, sampled from Twitch periodically while the Event is live; the clips made during or from the stream, including clips cut from its recording afterwards (title, who made it, when, and its place in the broadcast); and the stream's past broadcasts (recordings) that belong to the Event. When a clip is deleted on Twitch we remove it from the Event's page. For what we do with a clip's content, see "Clip content" below.
  • Clip content — only while "AI summarization" is on — it is turned on when a Broadcaster taps "Yes, I'm in!" or later in their settings, and can be turned off at any time; we record that choice (when, where, and which version of our Terms and this Policy was in force), and nothing is processed until it is on. While it is on, we process the clips made during a Broadcaster's Events, including clips made by viewers, to write captions and short highlights for the Event's page, its recap and its Moment video, and to let the Broadcaster search their own Moments by what was said. The voice in a clip is transcribed into captions by a speech-recognition model that runs on our own servers (Amazon Web Services, Section 12). The audio is processed on our servers only to make the captions; it is never sent to an AI provider and is not kept. The captions are filtered for personal information, and only that filtered text is sent to the AI providers in Section 12 to summarize it into highlights and the recap's story. How a clip sounds: our servers also measure how loud it is, how its pitch moves, and whether there is laughing, shouting or excitement, and the AI notes the mood of its words (for example funny, tense or sad). We use these only to rank which Moments to show first and which parts to use in a Moment video; they are never shown to anyone, are not used to identify anyone, and are deleted at once if the Broadcaster turns AI summarization off. Working files on our servers are deleted as soon as the captions are made, and automatically within 14 days if that fails. Those highlights and summaries appear on the Event's page and recap — publicly whenever the Broadcaster's recaps are public (Section 8) — and are kept with the Event until it is deleted; captions appear in the Moment video (Section 4). The Broadcaster can turn this on or off at any time in their settings (Section 8). If guests or others speak on a stream, the Broadcaster is responsible for letting them know their speech may be processed this way.
  • Clips from the recording — only while Smart Moments is on — after an Event ends, the Service may create a few clips from the stream's recording on Twitch (public clips on the Broadcaster's own channel) and treat them like the clips above. We also read from Twitch which parts of a recording Twitch muted for music, only to leave those parts out of Moment videos.
  • Channel activity, only with the Broadcaster's permission — if a Broadcaster grants the matching Twitch permissions, we receive follow, subscription and gifted-subscription events for their channel (including the Twitch user ID of the person who followed or subscribed) and a per-minute count of chat messages. We do not store chat messages or who sent them (the exceptions are a chat command's records, the moderators recently seen in the channel's chat, and, when someone the Broadcaster added saves a Moment, that person's Twitch login — see below). See "Chat moments" below.
  • Event activity log — the measurements above (viewer counts, follows, subscriptions, Bits, votes, chat-activity counts and crowd words) are kept as a timeline with each Event so the live Catch Up, the recap and the Broadcaster's analytics can be shown. It contains counts and crowd words, never chat messages or Viewer identities, and is deleted when the Event is deleted.
  • Chat moments (crowd words), only while an Event is live — so an Event's recap can say what chat reacted to at its busiest moments, we read the channel's chat messages in memory while a OneStarLive Event is live. This "Chat activity" is part of "Track my streams"; the Broadcaster can hide it from any recap with the Event timeline switch, and it stops if they revoke the chat permission. What we keep is a per-minute count of messages, and single words and emotes that several different people used in the same minute, each stored only as a count of how many people used it (for example, "KEKW — 14 people"). We never save a message, a sentence, or who sent it, and nothing one person said on their own is ever kept. Messages from the Broadcaster and from bots, messages the channel's moderators delete, clear or time out, and messages from Viewers who asked us to leave their chat out are left out before anything is counted; profanity and words that describe a person (such as where someone lives, studies or works) are never kept. The result is a short phrase naming the words and how busy chat was; it never says who said anything and never states facts about a person.
  • Automatic clips — only if the Broadcaster has it on — a Broadcaster can ask OneStarLive to create Twitch clips on their own channel during a live Event, using the clip permission they granted. Chat is read in memory only to spot busy moments; no chat message and no Viewer identity is stored, and Viewers who asked us to leave their chat out are not counted. On quiet streams it may also clip a few moments an hour, within the number the Broadcaster chose ("How often"). The clip itself is an ordinary, public Twitch clip on the Broadcaster's channel, created on and governed by Twitch, and belongs to the Broadcaster; we store it exactly as we store any other Event clip (see above). Twitch does not let us delete clips: the Broadcaster deletes a clip on Twitch, or hides it from OneStarLive's pages with "Remove from OneStarLive". We post a short line in the channel's chat saying a clip was made; that line never names anyone. The Broadcaster chooses it when they set up OneStarLive and can turn it on or off at any time.
  • Stream markers — only when the Broadcaster adds one — a Broadcaster can ask OneStarLive to add a marker to their stream's recording on Twitch during a live Event, using the Twitch permission they granted. OneStarLive does not add markers automatically. A marker is a timestamp and a short label on the Broadcaster's own recording, visible to the Broadcaster in Twitch's tools; it contains no chat message and no Viewer identity. Twitch only allows markers when the Broadcaster keeps past broadcasts. We keep our own record of each marker we created — the Event it belongs to, its label, its position in the stream and when it was made — and it is deleted with its Event, or when the account is deleted.
  • Moment videos — when a Broadcaster asks, we make a short video of an Event from its clips and Moments (a beta: within a monthly limit, one per Event, made within 7 days after the Event ends); we do not make one unless asked. To make it, we fetch the Event's clips from Twitch and edit them together on our servers, hosted by Amazon Web Services in the United States; if the Broadcaster has "AI summarization" on, the video carries captions. We keep the finished video files, the caption data for its clips, and a record of each request (which Event, when, its length and whether it finished). A video is visible only to the Broadcaster (Only me) unless they choose Everyone; a video set to Everyone can be watched on the Event's page but not downloaded, and when it is ready we post one message in the Broadcaster's chat, with its link only if it is set to Everyone. How long each of these is kept is in Section 4.
  • Chat commands — the Service reads the Broadcaster's chat (where they granted that permission, above) for its commands, and replies publicly in that chat.

- `!recap` — while an Event is live, anyone in the chat can type it (or, if the Broadcaster chooses, only them and people they add in their settings) and the Service replies with a short catch-up of what has happened so far (written by AI when the Broadcaster has AI recaps on) and a link to the Event's page. For 24 hours after the Event ends, it replies with a link to the recap, if the recap is public. Replies are rate-limited per channel, however many people type it; otherwise nothing is sent. - `!startevent` and `!endevent` — the Broadcaster's own message counts, and so does one from someone the Broadcaster added for it in their settings. `!startevent` creates and starts a new Event from the stream's current Twitch title and category; `!endevent` ends it. When a Broadcaster goes live with no Event, the Service may also post one line in their chat, once per stream, inviting them to use it; ignoring that line is how they decline. - `!moment` — the Broadcaster, and anyone they added for it in their settings, can type it while an Event is live to save that point of the stream as a Moment, with an optional name. It may create a clip and a stream marker on the Broadcaster's channel, using the permissions they granted. - `!link` — anyone can type it; the Service replies with the Event's page link. `!osl` — the Broadcaster only; the Service replies with the list of commands. What we keep: the Twitch message identifier, so the same command is not answered twice, and a record that the command was answered — which Event it was for, when, whether the reply was sent as the Extension or as the Broadcaster, and a scrambled code for whoever typed it, which lets us count unique and repeat users without knowing who they are. These records are deleted automatically after about 13 months. For a Moment, we keep its name and when it was saved, and, when someone the Broadcaster added saved it, that person's Twitch login, as the record of who saved it. The Broadcaster's list of people they added is kept as their Twitch logins, display names and identifiers until the Broadcaster removes them. To suggest people to add, we also keep the moderators recently seen in the Broadcaster's chat — up to 30 per channel, each as a Twitch login, display name, identifier and when they were last seen — shown only to the Broadcaster in their settings. Otherwise we do not store the message or the name of who typed it.

C) Viewer Interaction Data

When Viewers interact with an Event, we collect and store:

  • Contribution records — the fact and amount of Bits contributed toward an Event's goal (received from Twitch; see 1(D)), and any attributed outcome.
  • Votes and reactions — vote selections and reaction choices tied to an Event.
  • "Going" status — whether a Viewer marked themselves "going" for an Event.
  • Points and Promotion Credits — the points you earn (for example from challenges or from Bits used on events) and the Promotion Credits you receive or spend, each as a history of entries tied to your Twitch identifier.
  • Live attendance — we record attendance only for Viewers who have shared their Twitch identity with the OneStarLive Extension. That is a Twitch permission: a Viewer who has not shared it is not recorded, and is offered a "Count me in" button that asks Twitch for it. Once a Viewer has shared it, having the OneStarLive panel open during a live Event records an attendance entry automatically (Viewer ID, display name, avatar, the time they were first seen, and the last time they were seen while the Event was live — used to confirm they stayed, for example for points), and they appear in that Event's attendance list as one of its OneStarLive viewers. When one continuous stream covers more than one Event, each attendance entry is recorded against the Event the stream belonged to at the time, and entries may be consolidated onto one of those Events. A Viewer can remove themselves from an Event's list, revoke the permission in their Twitch settings, or ask us to remove an entry.
  • Chat-summary preference — whether you have asked us to leave your chat out of stream summaries (Section 8), stored against your Twitch identifier so we can honour it.
  • Agreement records — when a signed-in Viewer accepts our Terms and this Policy we record which version they accepted, when, and where (the Extension or the website). Earlier acceptances are kept as a dated history, as proof of agreement.

D) Bits / Contribution Records (from Twitch)

When a Viewer uses Bits, Twitch processes the transaction and sends us a verified record that it occurred (via Twitch's webhook), which we use to update goal progress and contribution tallies. We do not receive, store, or process payment-card data, banking details, or funds. All financial data and processing belong to Twitch. Twitch may also pay OneStarLive a developer revenue share associated with Bits used through the Extension — currently 20%. We receive a record of the transaction, never the payment itself.

E) Usage, Device, and Log Data

We may automatically collect limited technical and usage data, such as:

  • Interaction events — event page views, clicks, scheduling actions, vote and reaction interactions, and goal-state transitions.
  • Device/browser info — device type, browser type, and language settings.
  • Server and hosting logs — which may include IP address, timestamps, request metadata, and error logs, used for security, debugging, and abuse prevention. These logs are handled through our hosting and monitoring providers.
  • Share page visits — when someone opens a shareable event page we record that a visit happened, so the Broadcaster can see how the page performed. A visitor who is not signed in is identified only by a random visit ID in a cookie (Section 7); a signed-in visit is recorded against the visitor's Twitch identifier.
  • Explore activity — which events Explore showed you, and what you react to, vote on, mark Going, dismiss, and which creators you add to a lineup, so Explore can show you events you are likely to want and not repeat the ones you hid.
  • Viewer-count samples — while an Event is live we sample the stream's viewer count from Twitch periodically. These are deleted automatically after 14 days; the totals calculated from them (such as the peak) are kept with the Event.
  • Cookies and browser storage — see Section 7.

F) Public Profile, Following, and Rankings

Some information about a Broadcaster's activity is public by design. It appears on the creator profile, on shareable event pages, and on our public leaderboard, and can be seen by anyone without signing in:

  • Creator profile — the profile content in Section 1(A), your follower and following counts and lists, and the events you have scheduled and run.
  • Your name with your Events — your Twitch display name and avatar are always shown with the Events you create, on the panel, on event pages, in Explore and in chat messages the Service sends for you.
  • Activity statistics — number of events, categories played, hours live, current and best streak, how many scheduled events you kept, attendance and reaction counts, and clips created.
  • Trophies and medals — achievements derived from that activity, their tier, and progress toward the next one.
  • Leaderboard position — your rank among other creators. We store periodic snapshots of rankings so positions can be compared over time.
  • Region — for regional comparisons we use only your continent. We do not publish your timezone or any more precise location.

Following is a public relationship: if you follow another creator, that is visible on both profiles.

G) What an Event's Page Shows, and to Whom

Each Event has a public page. What it shows is set by the Broadcaster:

  • Shown to everyone unless the Broadcaster makes it private — the Event's details; its vote, "going" and attendance lists, including the display name and avatar of each Viewer who voted, reacted, cheered Bits, marked themselves going, or was counted in attendance — what a Viewer does on an Event is shown with their name (clips carry Twitch's own credit to whoever made them); the live Catch Up and the recap after the stream (what happened and when, the viewer-count graph, highlights, and what chat reacted to at its busiest moments — the crowd words described in Section 1(B), never messages or names); the Event's clips and past broadcasts; its Moment video (to watch, not download); and counts such as peak viewers and how many OneStarLive viewers took part. A Viewer who wants their name removed from an Event's page can ask us at contact@onestarlive.com.
  • Shown only to the Broadcaster unless they make it public — how many follows, subscriptions and chat messages the channel received during the stream (counts, not who), and the chat-activity line on the recap's graph; and the Event's promotion results: how many times its promoted card was shown on OneStarLive Explore, and how many people RSVP'd, reacted, liked or showed up, in total and after seeing the promoted card (counts, never who). A Broadcaster can make these public for one Event or as a default for their Events.
  • Shown only to the Broadcaster, always — how many of the people who followed or subscribed had first found the Event through OneStarLive's promotion; and the event analysis prepared for the Broadcaster.
  • The Broadcaster's switches — on "Yes, I'm in!" a Broadcaster chooses who can see their recaps (Public or Only me), which sets all of the following at once except the Moment video, which stays Only me until they choose Everyone; afterwards, in their settings and on each Event's page, they choose Everyone or Only me for: Event recap (the live Catch Up, the statistics and the recap); Event timeline (the viewer-count graph, the clips and past broadcasts, and the crowd words — what chat reacted to at its busiest moments); Moments; the Moment video; and Follows, subs & chat (Only me unless they choose otherwise). A choice can be made for one Event or as a default. A private section is shown only to the Broadcaster; when the crowd words are private, the recap still notes that chat was busy but not the words. Making the Event timeline private does not stop Smart Moments: its clips stay public on Twitch.

2. How We Use Your Information

We use the information we collect to:

  • Provide and operate the Service — create and display Events across panels, overlays, and shareable pages; enable scheduling, votes, reactions, attendance, and goal tracking; and, where you opt in, send chat messages and deliver notifications to your Discord webhook.
  • Show analytics — provide Broadcasters with statistics about their own Events and engagement.
  • Create clips and stream markers on your channel, where you ask for them — use the Twitch permissions you granted to create clips on your channel during a live Event (automatic clips are off until you turn them on), add a marker to your stream's recording when you ask for one, and post a line in your chat when a clip is made.
  • Write captions and highlights, where a Broadcaster has "AI summarization" on — for the Event's page, its recap and its Moment video (Section 1(B)). They are checked for personal information before they are used.
  • Make Moment videos — after each Event, or when a Broadcaster asks, edit an Event's clips into a short video, with captions where they have "AI summarization" on (Section 1(B)).
  • Build your public creator profile — we take the Events you run and derive statistics from them (events scheduled and kept, hours live, streaks, categories, attendance and reaction counts, clips), calculate trophies and a leaderboard position from those statistics, and publish the result on your public profile and on our public leaderboard, together with your follower and following relationships. See Section 1(F) for exactly what is public.
  • Write optional text with AI — suggest an event description or a short line for an event page when a Broadcaster asks; and, while AI summarization is on (turned on with "Yes, I'm in!"; it can be turned off at any time), word an Event's recap, its Moment titles and stories, `!recap` replies and the share line (the same wording may appear in the Event's link preview and on the Broadcaster's other event pages). We send the model only the Event's details (title, description, category, goal), the Broadcaster's display name, the names given to saved Moments, the Event's aggregate statistics, the titles of the Event's public clips, the crowd words described in Section 1(B), and the captions described in Section 1(B) — never Viewers' identities and never chat messages. The model is instructed never to include personal information about anyone. Everything it writes is checked automatically before it is shown and is withheld when our checks find personal information (such as a real name, location, age, family details or contact details), hurtful or unsuitable content, or claims our data does not support; automated checks can miss things. The numbers are calculated by us; the model only phrases them. These features are marked as beta. The private analysis of an Event shown to the Broadcaster, with a suggestion for next time, is written by our own rules from the Event's figures, not by AI. The notable points in a stream that the Catch Up and the recap describe are worked out by OneStarLive from the measurements in Sections 1(B) and 1(E). We do not download or analyse the stream's video or its past broadcasts; the only media we process is a clip's content, as described in Section 1(B).
  • Check uploaded images — screen event images and profile pictures with an automated moderation service before they are stored or displayed, so disallowed content is rejected.
  • Maintain safety and security — prevent abuse and fraud, troubleshoot, and enforce our Terms.
  • Improve the Service — performance, reliability, and features.
  • Support you — respond to inquiries and handle data and deletion requests.

We do not use your information for third-party advertising, and we do not sell your personal information.


3. How We Share Information

We do not sell your personal information. We share information only in these limited circumstances:

  • Service providers — trusted vendors that help us operate the Service (for example, cloud hosting, image storage, automated image moderation, and logging/monitoring), only to the extent necessary to run and secure the Service.
  • AI providers — the AI providers named in Section 12 receive the Event details, aggregate statistics, public clip titles, crowd words and the filtered captions described in Section 2. They never receive audio, chat messages or Viewer identities, and receive this only to produce the text described there. Not for AI training: every request is sent only to providers that commit not to keep it and not to use it for training.
  • At your direction — when you enable a feature that sends data on your behalf, such as posting to a Discord webhook you provide or sending messages to your Twitch chat. Public-facing content (like an Event's title, image, its vote, "going" and attendance lists with each Viewer's display name and avatar, and its recap) is displayed to the audience by design — see Section 1(G).
  • Publicly, by design — your creator profile, the statistics and trophies derived from your Events, your leaderboard position, your follower and following lists, and the recap page for each completed Event are published on the open web and can be read by anyone without signing in.
  • Legal and safety — to comply with law, regulation, subpoena, or legal process; to protect the rights, property, or safety of OneStarLive, our users, or the public; or to prevent fraud, abuse, or security incidents.
  • Business transfers — if OneStarLive is involved in forming a company, a merger, acquisition, financing, reorganization, bankruptcy, or asset sale, information may transfer as part of that transaction.

4. Data Retention

We retain information only as long as reasonably necessary to operate the Service, comply with legal obligations, resolve disputes, enforce agreements, and maintain security. Some data has specific retention limits:

  • Automation logs and raw activity records (the per-minute inputs an Event's activity log is built from) are automatically deleted after approximately 60 days; viewer-count samples after approximately 14 days. The Event activity log built from them is kept with its Event and deleted when the Event is deleted.
  • Server/HTTP logs are retained for a limited period (on the order of weeks) for security and reliability.
  • Event and contribution records are ordinarily kept for as long as the Event remains available through OneStarLive, because they are what the Event's public recap page is made of.
  • Attendance entries are kept with their Event until the Viewer asks us to remove theirs, the Broadcaster deletes the Event, or we no longer need them to provide the Service.
  • When a Broadcaster deletes an Event, its recap, its notable points and saved Moments, its activity log, its captions and sound measurements, its Moment video, its automatic-clip and marker records, and its vote, reaction, "going", attendance and page-visit records are deleted. For an Event that had already finished and been counted, the totals it contributed to the Broadcaster's public statistics, trophies and leaderboard position may be kept as aggregate figures that identify no Viewer, together with a statistics record of the Event (its Moments and figures, without any words said or typed), which is used only for those statistics and trophies and is deleted when the account is deleted.
  • Account records are generally kept while your account is active. If you ask us to delete your account, we delete or de-identify the personal information associated with it, subject to limited retention where necessary for legal compliance, security, fraud prevention, dispute resolution, or enforcing our agreements.
  • Moment videos are deleted 7 days after they are made, or sooner if the Broadcaster deletes one; if that deletion fails, our storage removes the files automatically within 10 days. Each Event can have one video. Working copies of clips made while a video is edited are deleted within 1 day; caption data, within 14 days; the instructions sent to our video servers, within 7 days; and those servers' technical logs, after 3 days. The record of each request (which Event, when, its length and whether it finished) is kept so we can show the Broadcaster their videos and monthly limit, and is deleted, with any remaining video files, when the account is deleted.
  • What was said in clips (the exact words) is deleted within 24 hours after the Event ends (within 48 hours of being captioned, if we have no recorded end for the Event), except the Moment search copy: while "AI summarization" is on, we keep a searchable copy of the words said in your clips and when they were said, so that you, and only you, can find your Moments by what was said and make videos from them. It is never shown on a public page, is not sent to AI providers and is not used to train AI models, and it is deleted when you turn "AI summarization" off, when its Event is deleted, or when your account is deleted. The short highlights written from it stay with the Event until it is deleted, and the clips themselves are not kept for them. Sound measurements and mood notes (Section 1(B)) are kept with the Event until it is deleted, and are deleted at once if the Broadcaster turns AI summarization off. Saved Moments are kept until their Event or the account is deleted.
  • Channel activity records (follows, subscriptions, chat-message counts, and the per-minute crowd words described in Section 1(B)) are deleted automatically after 60 days; the totals and the short chat-moment phrases calculated from them are kept with the event record. Chat messages themselves are never stored.
  • Share page visits by visitors who are not signed in are deleted automatically after 60 days.
  • Records of which events Explore showed you are deleted automatically after 90 days.
  • Points and Promotion Credit histories are kept while your account is active, because your balance is calculated from them.
  • Agreement records (which version of our Terms and this Policy you accepted, and when, and each time "AI summarization" is turned on or off) are kept as proof of agreement for as long as your account exists and for a reasonable period after, where needed to resolve disputes or meet legal obligations.
  • Ranking snapshots are retained so leaderboard positions can be compared over time.

5. Where Data Is Stored

Information is stored on systems operated by or for OneStarLive, including our hosting and cloud-storage infrastructure. We generally process and store information in the United States.


6. Security

OneStarLive is operated as a small, independently run service. We take reasonable measures designed to protect the information we process, including access controls and network restrictions, and we store sensitive credentials (such as Twitch OAuth tokens) with restricted access.

Twitch OAuth tokens, any email address you give us, and your Discord webhook URL are encrypted where we store them.

We collect as little as the Service needs and keep it only as long as it is useful.

However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security. You use the Service at your own risk. If we become aware of a breach affecting your personal information, we will notify affected users and any regulator where the law requires it.


7. Cookies and Similar Technologies

We use a small number of strictly functional cookies and browser storage:

  • Session cookies on app.onestarlive.com, so you stay signed in after signing in with Twitch.
  • A visit cookie on shareable event pages — a random ID with no personal information in it, so a repeat visit is counted once.
  • Browser storage used to remember your interface preferences.

Our authentication cookies are set with the Secure, HttpOnly and SameSite attributes.

We do not use advertising cookies. We do not sell your personal information, and we do not share it with advertising networks.

If you block or disable the functional cookies described above, you may be signed out and parts of the Service may not work correctly.

Twitch's embedded player. On recap pages, clips play in Twitch's own player, embedded in the page. When you rest your pointer on a clip or open one, your browser loads that player from Twitch, which receives your IP address and may set or read its own cookies under Twitch's privacy policy. We do not control those cookies, and nothing loads from Twitch until you rest on or open a clip.


8. Your Choices and Rights

  • Access and deletion. You may request access to or deletion of data associated with your Twitch identity by emailing contact@onestarlive.com. We may need to verify your request, and we may retain limited information where necessary for legal compliance, security, or fraud prevention.
  • Broadcaster controls. Broadcasters may edit or delete Events they created from the Event's page. What deletion removes, and which aggregate figures may be kept, is described in Section 4. Server logs (Section 1(E)) are retained for their normal period.
  • Attendance. You can ask us to remove an attendance entry associated with you through the controls in the product or by contacting us at contact@onestarlive.com.
  • Viewer controls. Viewers may stop interacting with an Event at any time.
  • Chat moments. Chat is never shown with names. A Viewer can ask us to leave their messages out of stream summaries by emailing contact@onestarlive.com; from then on their messages are left out before anything is counted. Crowd words already kept are counts that are not linked to anyone, so there is nothing individual to remove. A Broadcaster can turn chat moments off for their channel, and can hide them from an Event's page with the Event timeline switch (or the whole recap with the Event recap switch), for one Event or as a default.
  • Automatic clips and AI summarization. Smart Moments and "AI summarization" are turned on when a Broadcaster taps "Yes, I'm in!" to set up OneStarLive (the screen names anything this turns back on that they had turned off), and the Broadcaster can turn each off or on at any time in their OneStarLive settings. Turning "AI summarization" off stops new clips from being captioned and deletes the clip words (including the Moment search copy), sound measurements and mood notes we hold at once; short highlights already written stay with the Event until the Event is deleted or the Broadcaster asks us to remove them. It also replaces AI-written text with plain text.
  • Tracking your streams, and pausing. With "Track my streams" on (the default), we start an Event when you go live and make its recap. We do this only while the OneStarLive panel is active on your channel and you have accepted the current Terms and this Privacy Policy. Until then nothing is tracked, and any recap that is made is visible only to you.
  • Moment videos. A video is made after each Event (or when the Broadcaster asks), is public unless the Broadcaster chooses Only me, and can be deleted by them at any time.
  • Keeping events out of discovery. Broadcasters can opt an Event out of public discovery listings, so it is not surfaced to people who do not already follow you.
  • Your profile is yours. You can edit or remove your biography, links, social handles and uploaded picture at any time in your profile settings.
  • Email. Every email we send includes an unsubscribe link. Unsubscribing stops product-update emails; we may still send rare account or legal notices. If you gave us an email address you can ask us to remove it.
  • Revoking Twitch access. You can revoke OneStarLive's Twitch permissions at any time through your Twitch account settings; doing so may disable features that rely on those permissions.
  • Depending on your location (for example, the EEA/UK or California), you may have additional rights, such as to access, correct, delete, or restrict processing of your personal information, and to lodge a complaint with a supervisory authority. Contact us to exercise these rights.

9. Children's Privacy

OneStarLive is not intended for children under 13 (or the minimum age required by your local law, and in no case younger than Twitch's minimum age). We do not knowingly collect personal information from children. If you believe a child has provided personal information, contact us and we will take appropriate steps to delete it.


10. Legal Bases for Processing

Where the GDPR or UK GDPR applies, we rely on the following legal bases, as applicable to the processing in question:

  • Contract — to provide the features you ask us for, such as creating and running an Event.
  • Consent — for optional features and communications where consent is the appropriate basis, including being counted in an Event's attendance, AI summarization (captions, sound measurements and mood notes, Section 1(B)), and joining our mailing list. You can withdraw consent at any time.
  • Legitimate interests — to keep the Service secure, prevent fraud and abuse, debug problems, and improve reliability, and to summarise, as aggregate crowd counts, what an Event's chat reacted to (Section 1(B)), balanced against your rights.
  • Legal obligation — where we must keep or disclose records to comply with the law.

11. International Users

OneStarLive is operated from the United States, and information may be transferred to, stored in, and processed in the United States and in other countries where our service providers operate. Data-protection laws in those countries may differ from those in your own. Where applicable data-protection law requires safeguards for international transfers, we rely on legally recognised transfer mechanisms or other permitted safeguards.


12. Third-Party Services

The Service integrates with third parties, including Twitch (identity, Bits, chat, schedule, webhooks), Discord (delivery to a webhook you provide, and our own internal alert channels, which receive a Broadcaster's display name or channel identifier and what happened — for example "went live", "recap sent" or a request for AI summarization — the display name of a Viewer who used Bits and the amount, and error reports), Amazon Web Services (hosting; S3 for stored images and Moment videos; the servers that make Moment videos and the servers that turn clips into captions, described in Sections 1(B) and 2; Rekognition for the automated image checks described in Section 1(A)), OpenRouter and the AI model providers it routes to (the AI-written text and the captions described in Sections 1(B) and 2 — they receive the Event details, aggregate statistics, public clip titles, crowd words and the filtered captions listed there; they never receive audio, chat messages or Viewer identities, and every request goes only to providers that agree not to keep it or train on it). Their privacy practices are governed by their own policies, and we are not responsible for them. We encourage you to review Twitch's and any other relevant provider's privacy policy.


13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will post the updated version and revise the Effective Date. If we make material changes to how we collect, use, or share personal information, we will give additional notice where that is required or appropriate.


14. Contact Us

OneStarLive Email: contact@onestarlive.com

© 2026 OneStarLive