Privacy
How Muzes handles your data.

This policy explains what we collect, how we protect it, and which rights you can use at any time.

Effective Date

January 20, 2025

Company

Muzes Team

Location

Warsaw, Poland

Contact

support@muzes.xyz

Highlights

Designed for clarity

Data minimization

We only collect identifiers required for playback and safety—never raw chat logs.

Security-first

Encryption, least-privilege access, and recurring audits guard the cluster.

User control

Exports, corrections, and deletions are honored wherever the law allows.

Table of Contents

Introduction

Reference

Muzes Music Bot (“the Bot”) lets Discord communities stream audio from YouTube, Spotify, SoundCloud, Apple Music, and more. This Privacy Policy explains how we collect, use, and safeguard your data while operating those capabilities. By using the Bot, you agree to this Policy. If you disagree, discontinue use and contact us for support.

Supported Platforms

Stable

The Bot can play audio from a broad catalog of sources. Every platform enforces its own privacy policy, so be sure to review their documentation alongside ours.

  • YouTube
  • Spotify
  • SoundCloud
  • Apple Music
  • Deezer
  • Twitch
  • Tidal
  • Bandcamp
  • Mixer
  • Nico Nico Douga
  • Vimeo
  • Clyp.it
  • GetYarn
  • Mixcloud
  • OC ReMix
  • Pornhub
  • Reddit
  • Soundgasm
  • TikTok
  • FloweryTTS
  • Slider.kz
  • PixelDrain
  • JioSaavn
  • Yandex Music
  • HTTP/HTTPS sources
  • Local audio files uploaded to Discord

What Data We Collect

Reference

We only process the data required to deliver reliable playback and keep the network safe.

1. Data you provide

  • Discord account identifiers: username, user ID, and avatar.
  • Server context: guild name/ID, channel name/ID, message interactions when you call commands.
  • Optional support details you send to us through email or support channels when reporting a problem.

2. Automatically collected data

  • Playback signals: command history, requested song URLs, and timestamps.
  • Platform metadata: song title, artist name, duration, or similar tags from third-party APIs.
  • Technical diagnostics: IP addresses, user agents, and error logs for debugging and anti-abuse.
  • Performance metrics such as queue latency, node health, and failure reports used to keep playback reliable.

How We Use Your Data

Details

Data keeps queues stable, moderation predictable, and abuse under control.

  • Stream and process audio from supported platforms without buffering.
  • Manage queueing, playback, filters, and volume inside Discord servers.
  • Monitor usage trends to improve infrastructure and capacity planning.
  • Identify bugs, crashes, or regressions in real time.
  • Detect abuse, prevent unauthorized use, and enforce Discord’s Terms of Service.
  • Validate compliance with regional laws and licensing requirements.
  • Respond to support requests, investigate reported issues, and explain service decisions when appropriate.
  • Maintain service analytics that help us decide where to scale nodes or improve response times.

How We Share Data

Reference

We do not sell personal data. Data is only shared where it is necessary to operate or protect the service.

  • With infrastructure or hosting providers that process operational data on our behalf.
  • With third-party APIs when a playback request requires metadata or media resolution from that provider.
  • With legal authorities if disclosure is required by law or necessary to respond to abuse, fraud, or security incidents.
  • With trusted service operators strictly on a need-to-know basis for debugging, moderation, and uptime management.

How We Protect Your Data

Stable

Security is layered through encryption, access controls, and audits.

  • Data encryption ensures secure transmission between users, Discord, and our servers.
  • Access restrictions limit who can inspect operational data.
  • Regular audits verify compliance with security best practices.
  • Sensitive operational logs are scoped to limited personnel and retained only for as long as necessary.
  • Abuse-prevention systems help detect suspicious traffic, repeated failures, or misuse of playback endpoints.

Third-Party Integrations and Their Policies

Reference

Playing audio from platforms like YouTube or Spotify means you are also subject to their privacy policies. We have no control over changes they introduce, but we surface the most common references here.

Each link opens the official privacy documentation for that provider.

Those services may process requests under their own rules, regions, retention schedules, and analytics practices.

International Transfers

Important

Because Discord bots and third-party audio services operate globally, some processing may involve systems located outside your country.

  • We try to use providers with appropriate safeguards and commercially reasonable security controls.
  • By using the Bot, you understand that metadata or operational signals may cross regional boundaries when a source or node requires it.
  • Where required, we rely on contractual safeguards or comparable transfer mechanisms supported by applicable law.

Your Rights

Reference

Depending on your jurisdiction, you may be able to exercise the following rights:

  • Request a copy of the data we store about you.
  • Request correction of any inaccurate records.
  • Request deletion of data where applicable.
  • Object to processing in specific scenarios.
  • Withdraw consent for data processing at any time.
  • Ask for clarification about the categories of data we hold and why they are retained.
  • Lodge a complaint with a relevant supervisory authority if local law grants that right.

Children's Privacy

Important

The Bot is not intended for audiences under 13. We do not knowingly collect data from children. If you believe a minor’s data was captured, contact us immediately so we can delete it.

Data Retention Policy

Details

We retain data only as long as necessary to fulfill the purposes outlined here and to meet legal obligations. When it is no longer needed, we securely delete it.

  • Short-lived playback and diagnostics data may be kept temporarily for stability, abuse review, and incident response.
  • Support correspondence may be retained longer where needed to resolve an open request or document a service decision.
  • Retention periods can vary depending on legal obligations, security needs, and the type of system involved.

Contact Us

Stable

Questions or concerns about this Privacy Policy? Reach out to support@muzes.xyz and we will respond as quickly as possible.

Email support@muzes.xyz for privacy requests, or drop into the support server.

Updates to This Policy

Action required

We may update this Privacy Policy at any time. Changes take effect immediately once published here, so review the effective date regularly.