Voice bridge privacy policy

Last updated: 2026-10-29. This policy covers the hosted Nether Voice Bridge service, which relays live voice between Discord voice channels and Matrix rooms (Element Call). It does not cover Discord or any Matrix homeserver themselves, which have their own policies.

Operator: Dark Collective (“we”), operating from the United States · Contact:

What the bridge processes

What the bridge does NOT do

Where data goes

Relayed audio and identity data flow between Discord’s infrastructure and the Matrix homeserver/SFU serving the linked room (for this instance: nether.im and its LiveKit media server). Members of the linked Matrix room and the bridged Discord channel can see and hear the relayed participants — that is the service’s purpose. All processing takes place in the United States: the LiveKit media server runs on Akamai/Linode in North Carolina, and the Matrix homeserver runs on a Florida-based host (Sepfy); Cloudflare provides network/TLS proxying. These providers act as processors.

Age

This service is intended for users who meet Discord’s minimum age (13, or older where local law requires) and any age requirement of the Matrix room or community it is used in (the nether.im community is 18+). We do not knowingly process data from anyone under these ages.

Retention and deletion

Linked identities (optional)

If you choose to pair your Matrix account with a Discord account (pair / /bridge pair), the bridge stores that mapping — your Matrix user ID, the Discord user ID, an optional delegate account you name, and when it was created — so it can recognize you as one person when both accounts are present. It is created only by you, from both accounts, and unpair deletes it immediately. Room moderators may likewise record that a specific Matrix account is a service account in their room (relay allow); relay deny deletes that record.

Companion tools and your own devices (optional)

Instances may offer an interface for companion tools (it is off unless the operator enables it). People with authority over a bridged room may issue keys to companion tools for that room. For each key the bridge stores its issuer (a Matrix user id), its scope, a hash of its secret (never the secret itself), its label and when it was created; the personal permissions you grant with /bridge companion allow (your Discord user id, the key and when); and audit lines for each lease (the key id, the room, the Discord user id and ghost it represents, the consent basis, and timestamps). A room’s authorized companions may learn which Discord members the bridge represents in the call (Discord user id, display name and ghost), whether you are streaming on Discord and whether your ghost is present. In a room without media encryption, a companion holding a lease can receive the call’s audio while the lease lasts. The bridge never carries a companion’s media.

If you enroll a listen-only device of your own Matrix account, the bridge stores your Matrix user id and the device id you chose as a key (and, until you confirm the enrollment from your account, the direct-message room the confirmation code was sent to), until you unlink or revoke the device or enroll it again; plus audit lines of the enrollment, your confirmation and each connection (room, device, time). The one-time sign-in token your device presents is checked once with your homeserver and is never stored or logged. When the device enrolls and while its event stream is open, the bridge sees its network address; it is kept only briefly in memory for rate limiting, not with the key or in the audit log. The bridge sends that device only your own media key, your own call state and whether your paired Discord account is in the channel — never anyone else’s key, and never audio.

Your rights (GDPR/UK GDPR/CCPA)

Where these laws apply to you, you may request access to, correction of, or deletion of personal data we hold (practically: link records, audit entries, pairings, companion permissions, enrolled devices and deny-list entries naming you), and you may lodge a complaint with your supervisory authority. Contact ; we respond within 30 days. We process the data above to provide the service you or your community requested (legitimate interest / performance of the service).

Governing law

Dark Collective operates from the United States, and all data is processed in the U.S. This policy is governed by the laws of the United States. The GDPR / UK GDPR / CCPA rights described above are honored regardless of where you live.

Changes

We will update this page when the service’s data handling changes; the “last updated” date reflects the current revision.