Privacy policy

1. Scope and contact

This policy covers the Sanya Multichat local application and its informational website, chat.axelpx.ru. The developer and website operator can be contacted at me@axelpx.ru. The application runs on the user’s computer; this website does not host accounts, chats or platform access tokens.

2. Data the application accesses

Depending on the platforms and features you enable, the application may access and process:

• Connected channel identifiers, display names, avatars and broadcast details.
• Chat text, message identifiers and timestamps, author names, channel identifiers, avatars, badges and moderation or membership status.
• Stream events, supported donation or paid-message details, recent subscriber information available from the platform, viewer counts and likes.
• OAuth access and refresh tokens, connection settings, local viewer profiles, commands, points, logs, caches and backups.

Account data is accessed with permissions you grant. The app also processes chat and broadcast information available from the platforms. It does not receive your Google password.

3. Why data is used

Data is used to combine chats, display overlays, show stream events and statistics, find broadcasts, maintain local viewer features and carry out messages or moderation actions you request or configure. Connecting YouTube through Google enables the functions that require account permissions. It does not give the developer access to your account.

4. Storage and security

Application data and tokens are stored in files on your computer. Local profiles, settings, logs, caches and backups can remain until you delete them. The developer does not receive or maintain a central copy of these chats or tokens. Local storage is not a promise of encryption: protect the computer, its account and any exported backups. A backup exported with credentials can contain access tokens.

Connections to Google authorization and API services use HTTPS. Files copied to cloud backup or synchronization software are also subject to that software’s settings and policies.

5. External services and sharing

The application contacts the platforms you connect in order to retrieve data or perform your actions. Loading avatars, emotes or other remote media also contacts the relevant media host. Information you choose to show in OBS can be visible to your broadcast audience.

If you enable external AI features, the configured provider (DeepSeek in the current implementation) receives the request content needed for the feature. With chat context enabled, this can include selected chat messages, display names and platform labels. Those requests are sent directly from your computer, not through a developer-operated storage server. The provider processes requests under its own terms and privacy policy. Do not enable that integration if you do not want this transfer.

The developer does not sell Google user data or use it for advertising, credit decisions or training general-purpose AI models. Google-derived data is used for the disclosed user-facing functions, with transfers limited to what is needed to deliver those functions or meet applicable security and legal obligations. The use and transfer of data received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements.

6. Website and support

This website does not use analytics, advertising trackers, forms, cookies or local storage. All fonts and design assets are served locally. The hosting infrastructure may process technical request data such as IP address, time, requested URL and browser information for delivery, security and troubleshooting; these records do not contain your local chat database or platform tokens.

If you email support, your address, message and any attachments are processed through email to handle your request. Support messages are retained for the time needed to resolve the request and any applicable obligations. You can request deletion by email. Do not send passwords, tokens or unredacted chat logs.

7. Disconnecting and deleting data

You can revoke Google access at Google Account connections. Disconnecting inside the app removes the current local YouTube token file, but does not automatically erase other local records or exported backups. Stop the application and remove the relevant local files and copies to erase them. Follow the data deletion instructions.

The developer cannot remotely erase files on your computer. For data held by YouTube, other platforms, an AI provider or your email service, use that provider’s privacy controls. Google’s processing is described in the Google Privacy Policy.

8. Changes

Changes will be published on this page with an updated date. Material changes to how Google data is used must be disclosed before the changed processing begins, with renewed consent when required. For privacy questions, contact me@axelpx.ru.