User agreements
and data disclosure

Plain-language summary

• THC is a Minecraft client mod that renders audio-reactive visuals and supports synchronized audio and parties.
• The relay is optional and disabled by default.
• External audio tools are optional. Each supported loader and Minecraft target has one canonical, feature-complete THC JAR; the direct download is the release source and any third-party mirror must distribute that same build unchanged.
• Every distributed JAR uses the same explicit consent, pinned-version, and SHA-256 verification rules, and downloads tools only after you press the download button.
• Official-site builds may fetch a small THC update manifest at startup. The check is non-blocking, sends no Minecraft identity or playback data, and never downloads a mod jar.
• Local caches and managed tools stay inside the active Minecraft instance under thc/.
• Features that contact audio, lyric, cover-art, Mojang, or relay services necessarily send network requests to those services.

Your audio, your responsibility

THC is a playback and visualization tool. It does not sell, license, endorse, provide, or grant permission to access any audio selected by a user. You are solely responsible for what you choose to open, resolve, cache, play, share, or synchronize through THC.

• You must have any permission or rights required to access and use the selected audio.
• You must follow applicable copyright law, local law, the rules of the Minecraft server you join, and the terms of each audio or metadata provider.
• THC and its contributors are not responsible for user-selected links or files, unauthorized downloads, provider account action, copyright claims, server moderation, lost files, or other consequences of user content choices.
• The availability of a resolver or playback feature does not mean a provider permits every use of that feature. Provider restrictions remain in effect.
• Do not use THC to distribute audio to people who are not authorized to receive it.

Optional audio tools

Provider-link playback can use external programs to resolve a link and decode audio. THC does not download anything merely because Minecraft starts, this page opens, or playback notices a missing tool.

• Canonical JAR: only pressing Download now installs managed copies. Exact versions are pinned and verified before use, and each loader and Minecraft target has one release JAR.
• Distribution timing: a third-party platform may mirror the canonical release after its moderation completes; there is no separate platform-specific or reduced-feature variant.
• yt-dlp: pinned to version 2026.07.04 from the official GitHub release. Expected SHA-256: 52fe3c26dcf71fbdc85b528589020bb0b8e383155cfa81b64dd447bbe35e24b8.
• FFmpeg, FFprobe, and FFplay: pinned to Gyan FFmpeg 9.0 essentials. The immutable versioned GitHub release is the primary source and gyan.dev is the byte-identical fallback. Expected SHA-256: e6b54767a6065919048f1a098eb27211ca4e12b4348a05d88777a5855d0b6e71.
• Manual sources: you may instead install the exact official yt-dlp release and either the versioned FFmpeg 9.0 GitHub release or its gyan.dev fallback yourself.
• Downloads are checked against the expected hash before extraction or execution. Installed tools are stored under <Minecraft instance>/thc/bin, and the verified FFmpeg archive remains in a version-and-hash-addressed local cache so missing tools can be repaired without trusting a replacement download.
• The tools run as child processes only when needed to resolve, decode, or play provider audio. Declining leaves dependent provider-link playback unavailable while other THC features remain usable.

Optional relay and verified identity

When enabled in Settings, THC connects over encrypted WebSocket to thc.alcoholicwizards.com/relay. The relay exists to synchronize verified players across Minecraft servers.

• The service can receive your connection IP address, Minecraft UUID and username, Mojang session proof, current server and dimension context, party actions and party chat, and the track or visualizer state needed for synchronization.
• Nearby multiplayer effects may use player position data so visual and spatial audio state can be associated with the correct in-world player.
• Your Minecraft access token is used by the client to create Mojang session proof. It is sent to Mojang's session service for verification and is not sent to the THC relay.
• Account-linking codes are minted only after the relay verifies the live Minecraft session with Mojang. The raw code is returned only to that client and is never stored by the site; the service stores only a keyed hash needed to validate a claim.
• The raw code appears in a private HUD card rather than chat or notifications. The client clears it after no more than five minutes and immediately dismisses it when any non-chat Minecraft or THC screen opens.
• A verified Minecraft-to-site link persists until it is unlinked from Connect. Live badges still require the linked player to be actively connected through THC Relay.
• Persistent account identity, party membership, roles, bans, and related party state may be stored so parties survive reconnects.

Storage, caches, and retention

THC separates local client files from relay records.

• Local: downloaded tools, song cache, cover cache, lyric data, and related client files stay under the active instance's thc/ folder. The regular mod configuration remains in the instance configuration directory.
• Migration: version 0.1.8 retains the migration introduced in 0.1.5 and can copy THC-owned bin, audio-cache, and cover-cache data from the legacy user-home .thc folder. Existing instance files are not overwritten, symbolic links and unknown files are ignored, and the legacy folder is not automatically deleted.
• Relay: verified account and party records may persist as described above. Inactive parties and unreferenced player records become eligible for cleanup after 12 hours.
• Capacity: relay database storage is capped at 20 GiB. Cleanup is restricted to THC relay records and does not delete operating-system or unrelated service files.
• Supporter events: Ko-fi and Patreon webhook event IDs are retained for retry deduplication. Provider identities are HMAC-hashed before storage; payment amounts, billing details, and raw Patreon member IDs are not displayed publicly.
• Ko-fi receipt sign-in: both the transaction ID and the email from the same webhook-observed receipt are required. Each value is normalized and stored only as a keyed HMAC; the raw transaction ID and receipt email are not stored, and a transaction ID by itself is never accepted.
• Supporter access: an inactive Patreon membership and a verified one-time Ko-fi tip can retain login access but grant no supporter permissions. Each verified Ko-fi subscription payment sets or extends paid-through by one calendar month, later subscription webhooks renew it, and every entitlement read enforces expiry even without a cleanup job.

Third-party services

Depending on the feature you choose, THC may contact:

• Mojang or Microsoft session infrastructure for Minecraft identity verification, including the live-session proof required before an account-linking code can be issued.
• GitHub and gyan.dev when you explicitly use the audio-tools installer or follow the manual download links. The versioned GitHub FFmpeg asset is tried first and gyan.dev is the fallback.
• Modrinth when you visit its THC project page. The Modrinth build uses the same official dependency sources and contacts them only after explicit consent.
• thc.alcoholicwizards.com when you enable the relay, visit this website, or an official build checks the small version manifest.
• The audio, lyric, metadata, or cover-art provider associated with a submitted link or configured API key.
• Patreon when you explicitly start OAuth sign-in, and Ko-fi and Patreon when supporter webhooks report payments or membership changes. Ko-fi receipt sign-in verifies keyed hashes against webhook-observed data rather than exposing the receipt publicly. Public names and tiers are shown only when the applicable public flag or explicit Patreon allowlist permits it.

Those services operate under their own terms and privacy practices. THC does not control third-party availability, content, or policies.

Your controls

• Enable or disable the relay in THC Settings.
• Choose Later on the audio-tools screen to perform no download.
• Install or reinstall managed tools explicitly from the canonical JAR's audio-tools controls, or follow the manual instructions. Any authorized mirror uses the same JAR and controls.
• Unlink a verified Minecraft profile from the Connect account panel.
• Show or hide the official-site watermark from the Style settings. Clicking the mark asks for confirmation before opening the website.
• Choose Later on an update notice to dismiss it for the current session, or Don't ask again to ignore that specific version until a newer release exists.
• Open and clear local song, cover, and other THC cache areas from Settings.
• Mute individual players, hide their particles, adjust other-player volume, or disable other-player visualizers globally.
• Review this disclosure again from the client or this website.

Acceptable use

THC does not provide or host audio. You are responsible for the links, files, chat, and other content you choose to access or transmit, and for following applicable law and each provider's terms.

• Do not use party chat or relay features to harass others, distribute unlawful material, or interfere with the service.
• Do not attempt to overload, probe, bypass access controls, or disrupt the relay, website, database, or other users.
• Access may be limited or removed where necessary to protect users or service reliability.

Changes and contact

Features and disclosures may change with later THC releases. Material changes should be reflected in the in-game disclosure and on this page. The effective date and applicable mod version appear at the top.

Questions about the client, relay behavior, or stored THC data can be raised through the project's published support channel. Do not send Minecraft access tokens, account passwords, or other authentication secrets in support messages.

Read feature questions, return to The Harmonic Client, or download the current release.