Privacy policy

Information an instance handles

• Discord user, server, role, voice-channel, and profile identifiers needed for login and permissions.
• Private audio uploads, titles, artist metadata, ownership, storage use, group grants, invitations, and queue requests.
• Server settings, web sessions, terms acceptance, and limited security or audit events.
• Operational logs that may include identifiers and request metadata when an error occurs.

Private libraries and groups

Tracks are visible to their owner by default. Owners may grant access to invite-only groups. Group members may browse and queue granted songs but receive no download endpoint. An instance administrator can inspect metadata and delete content for moderation because the operator controls the underlying server and database.

Storage and retention

Uploaded audio is converted to Ogg Opus and stored on the instance's persistent volume until its owner or an administrator deletes it. Accounts, groups, settings, invitations, and audit records remain until removed under the operator's policy. Active Discord queues are held in memory and reset when a session ends or VTune restarts.

Third parties

VTune communicates with Discord for OAuth, bot operation, and voice playback, and may use YouTube extraction tooling for public URLs. Those providers process data under their own terms. VTune does not sell member information.

vtune.app

The public product site does not host member libraries and does not provide public accounts. It uses no analytics, advertising cookies, tracking pixels, remote scripts, or third-party fonts. Standard server logs may temporarily contain IP address, path, user agent, and timestamp.

Requests

Members should contact their instance operator to request access, correct metadata, or remove an account or upload. Self-hosters are responsible for their own privacy notices, backups, and legal obligations.