Information processed
When enabled, the client sends the relay a Minecraft username and temporary account-authentication proof, Minecraft UUID, one-way-hashed server identity, approximate in-game coordinates, dimension, visible-player identifiers, voice state, and live Opus audio while transmitting. Connection services also process IP address, request timing, and standard network metadata.
Purpose and sharing
This information is used only to authenticate players, scope voice to the correct server and lobby, route proximity audio, prevent abuse, operate the relay, and deliver signed updates. NSSVC does not sell this information. Cloudflare and network providers necessarily process connection traffic to deliver the service.
Storage and retention
Account, room, position, visibility, and audio state are held in relay memory only while connected. Normal relay logs contain startup and error information—not voice recordings, coordinates, usernames, or message contents. Aggregate health samples are retained for up to 30 days by default and contain no usernames, UUIDs, IP addresses, room identifiers, coordinates, or audio. Minecraft UUIDs may be retained in a ban list when needed to protect the service.
Your controls
You can decline the first-run notice, disable NSSVC, use push-to-talk, mute while continuing to listen, deafen both directions, block individual players, or remove the mod. Saved settings and blocked UUIDs are stored only in your local NSSVC configuration.
Contact and changes
NSSVC is operated by Foxinauci as an independent public beta. Privacy, security, and abuse requests should be sent through the distribution community while a direct public support address is prepared. Material notice changes require a new in-game acknowledgement.