baygus.You ask, we deliver

Privacy Policy

Last updated:

This policy explains how information is handled when you use baygus.net, Baygus Studio and the services connected to your account. It also covers information about viewers that streamers send to Baygus through these tools.

On this page

Who this policy covers

Baygus Studio provides the website, desktop application and related cloud services described here. For privacy questions or requests, use the contact address at the end of this policy.

Streamers choose which accounts to connect and which viewer interactions to display, read aloud or use in actions. If you are a viewer, tell us the streamer’s account and the relevant date when making a request; also contact the streamer about content they publish in their own broadcast.

Account and technical information

We store information you provide to create and manage an account, including your email address, account name, display name, linked TikTok handle, subscription status and support correspondence. Password-based accounts use password hashes rather than readable passwords.

Google or Discord sign-in supplies the profile and identity information needed to link your account, according to the permissions shown by that provider. Baygus does not receive your Google or Discord password. Session identifiers, app version, IP addresses, request times, usage counters and error records may be processed for authentication, security and troubleshooting.

Live-stream activity and cloud sync

Connected features can process public viewer names, usernames, profile images, chat messages, gifts, coin amounts and interaction times. Gift records and supporter totals are stored on our servers so they can be synchronized and used in overlays.

The app automatically synchronizes selected profile settings, widget settings, video-trigger rules and cloud video links. Authorized administrators can inspect these synchronized profiles and preview or copy available video-trigger configurations through the admin tools. This profile-sync mechanism excludes passwords, session cookies and local file paths. Local-only videos are not automatically uploaded by profile sync.

Public profiles, rankings and overlays

When the app connects to the TikTok account linked to your Baygus account, your public name, handle, avatar and app-reported connection status can appear automatically in the homepage streamer directory. A profile can remain listed as offline for up to 30 days after its last report.

The homepage rankings display aggregated synced gift coins, recorded connection time, active days and connected-session records. Daily, weekly and monthly periods use Baku time (UTC+4). These are Baygus activity records, not an independently verified statement of TikTok earnings. Missing or unsynchronized events may not be included.

Overlays and public support pages display the information you configure for them. Anyone with an applicable public page or overlay link may be able to view its content. Do not put confidential information in broadcasts, overlay text or shared links. Account email, login credentials and private settings are not published in the streamer directory or rankings.

Speech, AI and media features

Text-to-speech sends the text and necessary voice settings to the chosen speech service: Microsoft’s speech service for Standard TTS, or ElevenLabs when that option is available and selected. Speech request records can include the text, sender name or identifier, selected voice and generated-audio reference.

When AI co-host features are used, the request, selected context and instructions needed to generate a response are sent to OpenAI. Related requests and responses may be recorded to deliver the feature and manage usage. Do not submit sensitive personal information that is not needed for the feature.

Uploaded media, imported media references and widget content are processed to store or deliver what you request. YouTube and other linked platforms receive requests necessary to load their content; their own privacy policies also apply.

Subscriptions and viewer support

Stripe processes card payments for subscriptions and supported viewer-payment features. Baygus does not store full payment-card numbers. We store payment references, purchased plans, amounts, currencies, payment states and records needed to manage subscriptions, refunds and disputes.

Where creator support and withdrawals are available, we also process support orders, account balances, fees, withdrawal requests and the payout details supplied by the creator. Information shown to a creator or in a public support alert depends on the payment feature and the information entered for that payment.

Why information is used

We use information to provide the features you request, keep accounts and payments working, synchronize settings, answer support requests and maintain the service. Security and usage information helps investigate errors, prevent fraud and enforce service limits.

Where data-protection law requires a legal basis, the relevant basis depends on the activity: providing the requested service, meeting legal obligations, proportionate security and service-management interests, or consent where required. A public notice does not replace consent where the law requires it.

Service providers and international processing

Information needed for a feature may be handled by payment, sign-in, speech, AI, hosting, network-protection and delivery providers. These include Stripe, Google, Discord, Microsoft, ElevenLabs, OpenAI and our hosting partner Hostart, depending on the services you use. Authorized support and administrative staff may access information needed for their work.

Providers may process information in countries other than yours. Applicable provider arrangements and legal requirements govern that processing; the protection available in another country may differ. We may also disclose information when required by a valid legal request or when necessary to investigate misuse and protect users or the service.

Cookies and storage on your device

The website uses session cookies to keep you signed in and short-lived browser values to protect sign-in flows. A web session can last up to 30 days. Theme preferences are stored in your browser, and the desktop app keeps local settings and caches needed for its features.

You can remove browser cookies and local storage through your browser settings. This can sign you out or reset preferences. Removing local data or uninstalling the app does not, by itself, delete information already stored in your cloud account.

How long information is kept

Different records have different lifetimes. Account details, synchronized profiles, uploaded media and activity records do not all have a single automatic expiry; they remain stored until removed through an available control, an account-deletion process or a service-maintenance process. Billing, dispute and security records may need to remain longer for accounting, legal obligations or unresolved claims.

Generated speech files become eligible for routine cleanup after 24 hours. That cleanup does not itself erase separately stored speech-request text or metadata. The 30-day public-directory window is a display rule, not a promise that every underlying record is deleted after 30 days. Backup copies and records subject to a legal hold may remain after removal from the active service.

Access, correction and deletion

Contact us to request access to your information, correction, an export or deletion, or to raise an objection to public listing or other processing. Depending on the law that applies, you may also have rights to restrict processing, withdraw consent or complain to a competent data-protection authority.

Include the email or username associated with the account and enough detail to identify the issue. We may ask for proportionate verification before disclosing or changing account information. Do not send passwords or full card details. Requests are assessed under applicable law, including any records we are required to retain.

Security and updates

We use measures such as authenticated access, role restrictions, protected connections and service limits to reduce misuse. No online service or device can be guaranteed completely secure. Keep credentials and private overlay links confidential, and report suspected unauthorized access promptly.

This policy may be updated as features or processing practices change. The date above identifies the current version. Where law requires a further notice or consent for a change, publishing an updated policy alone does not replace that requirement.

Contact

Baygus Studio

support@baygus.net