This Policy explains how the Co-Star donation platform collects, uses, retains, and protects personal data when providing account, Google sign-in, YouTube channel linking, creator application, donation, membership, and customer support services.
1. Scope
This Policy applies to the Co-Star donation platform website, the platform’s Google account center, each creator’s donation and membership pages, and the related management, Co-Star Bot, and customer support features provided by the platform. Third-party services and external websites provided by creators themselves are governed by their own privacy policies.
2. Data we collect
2.1 Account and identity data
- Sign-in ID, display name, email address, account role, password hash, and two-factor authentication settings.
- Creator application data, such as contact information, channel or social media links, application status, and consent records.
- The Google account identifier (sub), verified email address, Google display name, and avatar URL obtained when you sign in with Google.
- The Twitch user ID and display name obtained when you sign in with Twitch or link Twitch on a channel. When a new account is created through Twitch sign-in, the email verified by Twitch is also obtained and used as the account email.
Google sign-in requests only the openid, email, and profile scopes. The platform doesn’t store access tokens or refresh tokens from Google sign-in, and never automatically merges different accounts based on email alone. YouTube channel linking is a separate authorization, described in item 5 below.
Twitch sign-in and linking request only the openid and user:read:email scopes. Tokens are revoked right after the account details are read and are never stored, and separate accounts are never merged automatically based on email alone. A linked Twitch account is also used to make up that channel’s Twitch chat check-ins on the donation page.
2.2 Donation and transaction data
- Donation recipient, supporter name, amount, message, payment method, payment status, transaction identifier, environment, and time.
- Membership redemptions, points, and other transaction-related records necessary to provide the platform’s services.
- If a creator turns on “Block by IP” under “Block donors”, the IP address of each donation is stored as a one-way hash using a key specific to that channel (IPv6 per /64), and is used to check the block list on donations and paid song requests; the creator and other viewers cannot learn the IP from it. Hashes in donation records are deleted after 90 days, and also when the creator turns the feature off; blocked ones are kept until unblocked.
Credit card numbers, security codes, and other full payment credentials are processed by the payment provider you select. The platform does not ask users to enter full credit card details in forms on this site.
2.3 Device, cookie, and security records
- IP address, browser or device information, request time, referring page, request path, sign-in results, and security event identifiers.
- Cookie or session data required for maintaining sign-in status, CSRF protection, remembering your sign-in, and light/dark theme preferences.
2.4 Customer support and user-provided content
When you use customer support, complaint, or assistance features, we may collect ticket details, contact information, correspondence, and attachments that users choose to upload.
5. YouTube channel linking and Co-Star Bot
Creators who use Co-Star Bot’s YouTube chat feature can authorize the platform with their Google account to link their own YouTube channel (the youtube.force-ssl scope). This service uses YouTube API Services, and this authorization is used only to:
- Identify the authorizing user’s channel and obtain its channel ID and name.
- Confirm that a live stream belongs to that channel and obtain its live chat ID.
- Post command replies, and announcements the creator sets up (such as progress-bar milestones reached, queue calls and automation rules), in that channel’s live chat, as configured by the creator, as the channel itself or the platform bot the creator selects.
- When the creator turns on “Per-stream analytics”, periodically read the concurrent viewer count and title of that channel’s current live stream.
The platform stores the channel ID, channel name, live chat IDs of recent streams, and encrypted access and refresh tokens. The platform does not use this authorization to edit or delete videos, ratings, comments, or captions.
Once linked, Co-Star Bot reads the public live chat messages of that channel’s streams to match commands. The content of messages that don’t match a command is not stored (except for the chat features in item 7 and the chat log, if the creator turns it on).
When a viewer uses a command, the platform records the viewer’s YouTube channel ID, display name, the command, and the result for about 30 days, so the creator can review them and cooldowns can be applied. If a command triggers an OBS animation or the wheel, the display name also appears on screen and in the wheel history.
Channel data and command records are available only to that creator, the managers they authorize, and platform administrators, and are not provided to other creators or third parties. Tokens are not shown to anyone.
6. Viewers linking Discord roles
When a creator turns on “Discord roles”, viewers can sign in with Discord on the link page (only the identify scope), then sign in with Twitch, YouTube (the youtube.readonly scope) or their member account on that channel to confirm it’s them.
- The platform stores the viewer’s Discord user ID and name, the linked Twitch user ID and login, YouTube channel ID and name, their member account on that channel, and the roles Co-Star has given.
- Each platform’s authorization is revoked once the account ID is obtained; no tokens are stored.
- The platform periodically checks whether the viewer is still a Twitch subscriber or YouTube member of that channel, to give or remove roles.
- When a creator sets a “Donors” condition, the platform totals the donations the viewer made to that channel while signed in to their linked member account, to decide whether to give the role. If “Keep for how many days after qualifying” is set, the last time the condition was met is recorded.
- Viewers can press “Remove all links” on the link page at any time; the link data is deleted and the roles Co-Star gave are removed.
7. Co-Star Bot chat features (Twitch, YouTube)
When a creator turns on these features, messages in Twitch and YouTube live chat are used as follows:
- First chatter, newcomers and viewer achievements: the viewer’s channel ID, display name, message count, first-chatter count and unlocked achievements are recorded (message content is not stored) to determine first chatters, newcomers and achievements.
- Multi-platform chat overlay: the latest ~100 messages (display name and content) are kept temporarily on the server for the OBS overlay; older ones are overwritten as new messages arrive.
- Chat log: when the creator turns on “Record the chat log”, the viewer’s platform account ID, display name, role (streamer, moderator), message content and time are stored on the server so the creator can search them by stream, date, chatter or keyword. They are deleted automatically after 30 days, and immediately when the creator turns the feature off.
- Per-stream analytics: when the creator turns on “Record per-stream analytics”, the platform periodically records the channel’s concurrent viewers, title and category during streams, and lists that stream’s supporters from the donation records. Deleted automatically after 30 days, and immediately when turned off.
- Automation rules: chat messages are matched against keywords the creator sets, and matching ones trigger the rule (for example, a chat reply or an OBS animation). Run records (rule name, viewer display name, a summary of the matched message and the result) are kept for 30 days.
8. Queue
When a viewer joins a creator’s queue with a chat command or the queue page, the platform stores the viewer’s platform account ID (or their member account on that channel), display name, the game ID they enter, and when they joined. The display name and game ID are shown on that channel’s queue page and OBS overlay. Entries are deleted 30 days after they end (called, left or removed).
9. OBS backups uploaded by creators
OBS scene collections and profiles that creators upload (which may include stream keys) are stored encrypted on the server and can only be downloaded by the channel owner after signing in (not by the channel’s other managers or company/group accounts). The platform does not read or use their contents. The latest 10 are kept per channel, and creators can delete them at any time.
3. Purposes of use
- Creating, verifying, and maintaining platform, creator, and supporter accounts.
- Processing donations, payment notifications, membership benefits, points, and transaction record lookups.
- Providing donation history across creators, retrieved only through account links already established under the same Google sub.
- Providing Co-Star Bot’s chat commands and replies.
- Depending on the creator’s settings, sending thank-you emails to members who donated while signed in, and giving or removing roles in the creator’s Discord server.
- Provide queues, automation rules, chat logs and per-stream analytics, as configured by the creator.
- Handling creator applications, customer support, disputes, refunds, or billing matters.
- Preventing fraud, unauthorized access, and other security incidents, and keeping the service stable.
- Fulfilling accounting, tax, judicial, or regulatory authority requirements that the platform is legally obligated to meet.
4. Production and staging environments
5. Third-party services and data sharing
To provide the services, necessary data may be shared with the following types of service providers:
- Google: handles Google OAuth sign-in. Google’s processing of data is also governed by its Privacy Policy.
- YouTube (Google): this service uses YouTube API Services. By using YouTube channel linking, you agree to the YouTube Terms of Service. Google’s processing of data is governed by its Privacy Policy.
- Payment providers: for example ECPay, NewebPay, OPay, OenTech, and PayUni, used to create transactions and return payment results.
- Discord and Twitch: when viewers link Discord roles, used to confirm their identity by sign-in, check whether they subscribe to the channel, and have Co-Star Bot give or remove roles in the creator’s server (the viewer’s Discord user ID is sent).
- The creator’s own software: when a creator sets up a webhook, that channel’s donation data (donor name, amount, currency, message, payment method) is sent to the URL the creator specifies, and the creator is responsible for how it is handled from there.
- Email, hosting, network protection, or other technical service providers needed to keep the platform running.
- Judicial, regulatory, or law enforcement authorities legally entitled to obtain the data.
Except for the purposes above, with consent, or as otherwise required by law, the platform does not sell personal data.
6. Cookies and sessions
Essential cookies are used for sign-in status, security verification, and protection against cross-site request forgery; preference cookies are used to remember interface settings such as the light or dark theme. Blocking essential cookies may prevent sign-in, payment, or account features from working properly.
7. Data retention
Personal data is retained for as long as necessary to provide the services, maintain accounts, conduct security audits, handle disputes, and fulfill legal obligations. Once the purpose of retention no longer exists or the necessary period has passed, the platform will delete, anonymize, or restrict the use of the data as circumstances require, except where retention is required by law or for billing, dispute, or security investigation purposes.
YouTube channel data and tokens are kept until the link ends. When a creator selects “Unlink”, the platform revokes the authorization with Google and immediately deletes the tokens, channel ID, and channel name. The platform also periodically checks that the authorization is still valid; if it has been revoked or has expired on Google’s side, the related data is deleted within 30 days. The record of linking a channel, including its channel ID and name, remains in the security audit log.
8. Data security
The platform takes measures including encryption in transit, password hashing, access control, session renewal, CSRF protection, Google OAuth state/nonce/PKCE verification, and security audits. Online services cannot guarantee absolute security; if you notice any suspected unauthorized use, please stop what you are doing immediately and notify the platform.
9. Your rights
Under applicable law, you may request to inquire about or review your personal data, obtain copies of it, supplement or correct it, stop its collection/processing/use, or delete it. Some requests may be limited where the law requires retention, where exercising the right may harm the rights and interests of others, or where the platform still has a lawful need to process the data.
You can also revoke the platform’s access in Google security settings; revoking access does not automatically delete existing data that the platform retains as required by law or for transactions.
You can also revoke the YouTube channel authorization by selecting “Unlink” in the creator dashboard. Unlinking deletes only the data stored by the platform and does not affect your channel, videos, or comments on YouTube.
10. Minors
When a minor uses this service, their legal representative or guardian should read and agree to this Policy and the related Terms of Service, and follow each payment provider’s age and payment rules.
11. Policy updates and contact
The platform may update this Policy due to changes in its services, laws, or security measures, and will publish the new version and its effective date on this page. To exercise your personal data rights or ask about this Policy, please contact us through platform support, and provide the information necessary to verify your identity and process your request.