1. Operator and scope
The download4yt.live bot operator is responsible for the processing described in this policy. You can contact the operator through https://download4yt.live/contact. This policy covers the Discord bot and its information website. The connected download service and Discord also process information through their own infrastructure.
2. Information the bot processes
When you invoke a command, the bot receives Discord interaction information, including your user ID and username, the command and its options, and relevant server, channel, and permission information. Download commands process the submitted media URL, format, quality, and the resulting download URL and metadata. Ban and kick commands process the target member’s ID, username, roles and permissions, the supplied reason, and the moderator’s identity. Prune commands fetch recent messages and associated message information needed to delete the requested messages. The bot does not continuously monitor general conversations or request the Message Content gateway intent.
3. Why information is used
Information is used to carry out requested downloads, display command results, verify whether the bot can perform moderation actions, record moderation reasons in Discord, and diagnose failures. The bot code does not implement advertising, sale of personal information, user profiling, or AI model training. Where applicable privacy law requires a legal basis, processing needed to provide requested functionality is based on providing the service; operational troubleshooting and abuse prevention rely on legitimate interests, subject to applicable rights. Legal obligations may require separate processing.
4. Sharing and visible replies
For downloads, the bot sends the submitted URL, format, and quality to the configured download4yt.live API. Its download request does not include your Discord user ID or username. The API processes media and returns a download link. Discord receives command replies, moderation actions, and audit-log reasons. Download replies include the requester’s username and download link; ban and kick results include member and moderator information and may be visible to people with access to that channel. Help and prune confirmations are private interaction replies. Hosting providers may process operational logs. Information may also be disclosed where legally required.
5. Storage and retention
When the dashboard database is configured, MySQL stores server and member IDs, usernames, download format and quality, status, and timestamps. It does not store submitted media URLs or download links. Download records and dashboard setting-change logs are retained for 90 days and removed by daily maintenance. Server defaults, user overrides, and custom commands remain until removed by a server administrator or the operator. Download quota coordination records contain only server and user IDs and remain until removed by the operator. Dashboard moderation records include server, moderator and target IDs, the action, reason, result and warning DM delivery status, and are retained for 90 days. Warning messages may be sent to the target member through Discord. Successful dashboard logins also store your account ID, username, first and last login times, and a login count. These account records are retained for 90 days after your last login. Configured bot developers can view aggregate activity across servers, the server and member origins of tracked download requests, and authenticated account records to operate the bot. Request origins identify Discord servers rather than physical locations or IP addresses. Dashboard sessions contain Discord account details and an OAuth access token, are encrypted in MySQL, expire within one hour, and are removed periodically. Audit logs are fetched live from Discord rather than copied into MySQL. Interaction and member information is also held in memory while the bot operates. Errors are written to the process console and can include request URLs, API response information, or other command-related data; hosting infrastructure may retain those logs. Discord retains messages and moderation audit records under its own policies. The download service may store generated files and request records separately. This bot policy does not promise a fixed deletion period for hosting logs or download-service files. Contact the operator for the current retention periods and removal of records under their control.
6. This website and download links
The public information pages do not use analytics or advertising cookies. The admin dashboard uses an essential HttpOnly session cookie for Discord login and accepts settings and custom-command submissions from authorized server administrators. Login requests the identify and guilds permissions to identify your account and list servers you can manage; it does not request your email or Discord password. Administrators with current server-management permissions can see member download activity and change server policies. Audit-log viewers also need View Audit Log permission. You can end a session by logging out and revoke application authorization through Discord settings. Web requests necessarily expose connection information such as IP addresses and browser headers to the server; a hosting provider or reverse proxy may record them. Visiting the main website, contact page, or a download link involves separate services and their data practices. Treat download links as shareable access links and avoid submitting confidential URLs.
7. Your choices and privacy requests
You can stop using the bot at any time. Server administrators can remove it through Discord. To request access, correction, deletion, restriction, or to object to processing of information controlled by the operator, contact https://download4yt.live/contact and identify your request as a bot privacy request. Include your Discord user ID and relevant command date or message link where useful; do not send passwords or tokens. The operator may need proportionate information to verify the request. Applicable law determines your rights and response deadlines. Records may need to be retained where required by law. For information controlled independently by Discord, use Discord’s privacy controls or support. Where applicable, you can complain to your local data protection authority.
8. Security and international processing
The bot authenticates with Discord and the download API using service credentials; its default API requests use HTTPS. No service can guarantee complete security. Discord, hosting infrastructure, and the download service may process information in countries other than your own. The location and any required transfer safeguards depend on the providers and deployment; contact the operator for details.
9. Children and policy changes
The bot is intended for people who meet Discord’s minimum age requirements in their country. Do not provide children’s personal information through commands. If you believe information from a child who is not eligible to use Discord has been processed, contact the operator. Changes to this policy will be posted on this page with an updated date.
Questions? Contact the operator · Read the Terms of Service