Effective date: 10 September 2026. This policy describes the behavior of this Mozart deployment as currently implemented. The operator should update the effective date and contact details when its deployment-specific practices change.
Information processed
- Discord profile details returned by Discord OAuth.
- OAuth/session state needed to authenticate the dashboard.
- Cached Discord guild relationships and permission indicators used to scope server access.
- Music playback history, including requester, server, track, and playback outcome.
- Support tickets and replies you submit, including category, subject, message text, status, and assignment history.
- Dashboard role assignments and operational records for moderation and administration.
Use and sharing
Data is used to authenticate users, apply server permissions, provide music and account features, investigate abuse, and operate the bot. Discord provides OAuth and Discord API services; MongoDB stores durable application data when configured; Lavalink transports audio playback. Shared dashboard views only show information relevant to the current viewer.
Retention
Session, music, audit, and cached authorization retention follows the deployment’s configuration and database behavior. We keep information only as long as it is useful for the service, support, moderation, or operational records.
Deletion
Authenticated users can request deletion from My Account → Privacy & data. The workflow removes the account record, cached guild authorization, requester music history, support tickets, and user-linked moderation records where supported. Some minimal operational records may be retained or anonymized when needed to operate the service.
Your choices
You may stop using the dashboard, revoke the Discord application authorization through Discord, or use the in-dashboard deletion workflow. Questions about this deployment should be directed through the configured Support destination.