Privacy policy

About this policy

This policy covers the RUSWRLD Player website at rusikmusic.site and rusikmusic999.ru, including accounts, the music library, games and social features.

The RUSWRLD Player project administrator, @Solnishkolegenda, is responsible for processing your data. You can also email ruslanenokpro@gmail.com.

Information necessary for a feature you choose is processed to provide that service at your request. Additional profile fields, an email address and linking Telegram are optional. This policy describes data processing; it does not itself constitute separate consent.

Data we use and why

• Accounts and sign-in. Your username, display name, account ID, registration date and session information enable sign-in and save your library. Passwords are stored as hashes. If you add an email address, it is used for address verification and account recovery.
• Your profile. Your avatar, banner, bio, birth date, selected track and appearance are used if you choose to provide them.
• Music. Favorites, playlists, subscriptions, listening history and listening time support your collection, statistics, music charts and awards.
• Social features and games. Friends, requests, messages and attachments, room participation, answers, results, ratings, predictions and awards support the relevant features. Social features also use your last activity time, online status and current listening information.
• Telegram. Signing in with or linking Telegram uses your Telegram ID and the name and username available through authorization. Linking connects your website account with the bot and shared game data. The website does not receive your Telegram password.
• Technical information. Your IP address, browser or client information, registration client identifier, request times and parameters, search queries and error logs are used to deliver content, provide search, diagnose problems, protect sign-in and limit abuse.

Who can see your data

Other users may see your username, display name, profile appearance, published playlists, rating, results and awards in the relevant sections. The visibility of additional profile information and activity depends on the feature, settings and relationships between accounts. Messages and attachments are available to participants in the relevant conversation or group.

Avoid sharing information in your profile, public playlists or group chats that you do not want others to see. Your recovery email, password hash and sign-in tokens are not public profile fields.

The administrator has technical access to stored data as needed for support, security and handling requests. Data may be disclosed to authorized authorities where required by law.

Cookies and data on your device

The website uses technical cookies for sign-in and Telegram authorization. Browser storage saves your language, volume, player settings, local playlists and a client identifier used to protect registration. The application cache helps load the interface and previously retrieved resources faster.

You can clear cookies, storage and cache in your browser settings. This may sign you out, reset preferences and remove your local library. Clearing browser data does not delete your account or data stored on the server.

Local audio files are read on your device and are not uploaded through the Local files section. If you create a website playlist from a folder, the selected playlist of matching catalog tracks is saved on the server.

External services

Hosting and server infrastructure store data and deliver the website. The email service receives the recipient address and service email content when you verify an address or recover access.

Cloudflare is used to deliver pages, protect against malicious requests and provide technical statistics. As requests pass through its network, the service processes network information, including IP addresses and browser information. Cloudflare Web Analytics collects page load metrics. See Cloudflare's privacy policy and its Web Analytics data description.

If you choose Telegram sign-in, Telegram also processes authorization under its privacy policy. Requests sent through Telegram or Gmail are also processed by the relevant messaging or email service. External websites have their own policies.

Storage and security

Account data and associated collections, messages and results are retained while the relevant features are in use, until deletion or until the processing purpose ends, unless the law requires otherwise. Technical retention depends on purpose: action rate-limit events are cleared after 2 days and abuse audit logs after 30 days. Aggregate statistics may be retained longer than individual events.

Protection includes HTTPS, password hashing, session verification, access controls and request limits. Backups support recovery after failures and are removed through rotation; changes to the live database and backups may not happen at the same time.

Managing your data

You can edit available profile information and security settings and manage your email and Telegram link in your profile. The library and social sections provide actions for your playlists, favorites and messages.

You can delete your account from the security section of your own profile. It requires your username, an ownership check and a separate final confirmation. See Account deletion for the steps and consequences. Your Telegram link is removed; independent bot activity is not deleted by this action.

Contact the administrator to ask what data is processed about you, request a copy, corrections, restricted processing or account deletion, or withdraw consent previously given. Include your username and explain your request. We may need to verify account ownership to protect your account. Do not send passwords or sign-in codes.

Requests are handled within the time limits required by applicable law. If information must be retained by law or to protect rights, we will explain the reason and scope of retention. You may contact the relevant data protection authority if you disagree with the processing.

Contact us about your data

When website features change, this policy is updated on this page. The current revision date appears at the beginning.