Privacy Policy for OneStarLive

Effective Date: September 22, 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 — if you join our beta or mailing list. It is stored encrypted and used to contact you about the Service. You can ask us to remove it 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.
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 about once a minute; 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.
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. See "Chat moments" below.
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, unless the Broadcaster has turned this off. We split each message into single words and emotes and discard the message immediately; we never save a message, a sentence, or who sent it. A word or emote is kept only if at least 3 different people used it in the same minute, and only as a count (for example, "KEKW — 14 people"). Before anything is kept we leave out the Broadcaster's own messages, bots and chat commands, messages the channel's moderators delete or clear, profanity, and words that describe a person (such as where someone lives, studies or works). Viewers who switch off "Include my chat in stream summaries" are left out entirely. Words chat uses all stream long are not treated as the reaction to a moment. The result is a short phrase such as "Chat surge — KEKW and 'clutch' (19 messages a minute)"; it never says who said anything and never states facts about a person.

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 two back-to-back Events, attendance is recorded for whichever Event is live at that moment; if the second Event lasts only a few minutes, its entries are moved to the first. A Viewer can remove themselves from an Event's list, revoke the permission in their Twitch settings, or ask us to remove an entry.

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 about once a minute. 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.
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, marked themselves going, or was counted in attendance; 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; how many follows, subscriptions and chat messages the channel received during the stream (counts, not who); and counts such as peak viewers and how many OneStarLive viewers took part.
Shown only to the Broadcaster unless they make it public — 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 AI-written event analysis prepared for the Broadcaster.
The Broadcaster's switches — a Broadcaster can make the live Catch Up, the event statistics, the recap, the recap's viewer-count graph, the follows/subscriptions/chat counts, the chat surge (what chat reacted to at its busiest moments), or the clips and past broadcasts private, for one Event or as a default for their Events. A private section is shown only to the Broadcaster; when the chat surge is private, the recap still notes that chat surged but not the words.

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.
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; word an Event's recap after it ends (the same wording may appear in the Event's link preview and on the Broadcaster's other event pages); and write a private analysis of the Event, with a suggestion for next time, shown only to the Broadcaster. We send the model only the Event's details (title, description, category, goal), the Broadcaster's display name, the Event's aggregate statistics (for the private analysis, also the counts that only the Broadcaster sees, such as follows, subscriptions and promotion results), the titles of the Event's public clips, and the crowd words described in Section 1(B) — never Viewers' identities and never chat messages. The model is instructed never to include personal information about anyone. Every line it writes is checked before it is shown, and a line is discarded if it contains personal information (such as a real name, location, age, family details or contact details), content that is not PG-13, a name or place it was not given, or a number not in our data. The numbers are calculated by us; the model only phrases them. These features are marked as beta.
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.
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:

Activity and automation logs are automatically deleted after approximately 60 days.
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.
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.
Viewer-count samples are deleted automatically after 14 days. The totals calculated from them are kept with the event record.
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) 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.

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, subject to platform and technical limits. Some logs or historical records may remain for security and auditing.
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, and may ask us to remove an attendance entry associated with them.
Chat moments. A Viewer can switch off "Include my chat in stream summaries" in their OneStarLive settings (or email 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 chat surge switch (or the whole recap with the recap switch), for one Event or as a default.
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.
Mailing list. If you gave us an email address you can ask us to remove it, and every message we send includes a way to unsubscribe.
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 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 anonymous 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), Amazon Web Services (hosting; S3 for stored images; Rekognition for the automated image checks described in Section 1(A)), OpenRouter and the AI model providers it routes to (the optional AI text described in Section 2 — they receive only the Event details, aggregate statistics, public clip titles and crowd words listed there, never chat messages), and Sentry (error monitoring — it receives technical error reports which may include your browser details and the page you were on). 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

Discord Terms Privacy policy