Privacy Policy

Effective September 23, 2026

Syronius FRAME operates the Audio Bridge Discord bot and bridge.syroniusframe.com. This policy covers visitors, streamers, server administrators, and participants in voice channels connected to the bridge. Contact syronius@gmail.com for privacy questions or data requests.

The bridge processes voice in temporary memory to deliver live audio. It does not save audio recordings or create transcripts. A streamer, listener, OBS instance, or streaming platform receiving the output may record or publish it separately.

Data we process and why

• Live voice and channel information: audio from the connected voice channel, channel identifiers and names, bitrate, participants' Discord identifiers, display names, avatars, and speaking and audio-level activity. These support mixing, playback, overlays, and controls.
• Server and member access information: Discord server and user identifiers, membership, roles, and permissions. We use these to check who can configure the bot, start a mix, or use a private link. The bot requests the Server Members intent for these checks; it does not request Message Content or Presence intents.
• Saved setup: profile names and ownership, server administrator and operator settings, revoked-user identifiers, private access keys, mix delay, overlay preferences, participant identifiers and their volume, mute, and visibility settings, and creation/update times. These let setups persist between sessions and enforce access restrictions.
• Service and connection information: commands and control actions needed to operate the bridge, connection metadata such as IP addresses used for rate limiting, and operational events and errors. Application logs include request methods and redacted paths, and may include Discord identifiers and connection or audio-performance statistics. They do not contain audio recordings.
• Support correspondence: if you email us, we receive your email address, message, and any information you choose to include so we can handle the request.

We do not sell personal data, use it for advertising, or use voice or other Discord data to train AI models. The application does not read ordinary chat messages or ask for your Discord password.

Who receives data

The service receives voice from Discord and delivers mixes to connected audio listeners. Controls and overlays can expose participant names, avatars, and speaking activity to people with the relevant private links. Streamers can include audio and overlay information in their broadcasts. Anyone with a working private audio link may listen while its mix is active; protect these links like credentials.

Discord provides account, server, and voice services. Our hosting provider runs the application, and Cloudflare carries and protects web and WebSocket traffic. These providers process data necessary to deliver the service, including network/request metadata. Avatar images may load from Discord's CDN. Email to our Gmail support address is processed by Google. See the privacy information from Discord, Cloudflare, and Google.

Authorized operators may access stored settings and logs for support, security, and maintenance. We may disclose information when legally required. Service providers may process data in countries other than your own. Recordings and broadcasts made by other users or platforms are governed by their practices; we cannot delete copies we do not control.

Retention and security

Audio uses bounded memory buffers for live mixing and playback delay. Buffered audio is consumed or discarded as the session runs and is released when the relevant session ends. Active sessions do not survive an application restart.

Saved profiles and settings remain between sessions while needed for the service. There is currently no automatic inactivity expiry. Confirmed bot removal from a server removes that server's active application records. Revoking a streamer removes their owned profiles but retains an access-revocation record; participant settings in other profiles may remain. Neither action by itself erases historical backups or logs.

Application logs rotate by size. Database backups are maintained for recovery; routine maintenance retains the seven most recent verified backups and any older backup needed for the retained rollback version. Rotation depends on maintenance and deployment activity, not a fixed number of days. Data requests cover relevant records in the live store, backups, logs, and support correspondence; we handle these manually and remove data that is no longer needed, unless retention is legally required.

Public browser connections use HTTPS/WSS, and private links are checked before access. Voice is decrypted and mixed on the bridge server, so this is not end-to-end encryption between Discord participants and output listeners. No service can guarantee absolute security. Rotate exposed links with /frame reset-links and contact us about suspected unauthorized access.

Browser storage

The control panel uses local storage for theme, layout, and control-lock preferences. You can clear these through your browser's site-data settings. The application does not add advertising or analytics trackers. Infrastructure providers may use their own security cookies or process technical request information.

Your choices and data requests

Streamers must inform participants and obtain their permission before relaying them. If you do not want to be relayed, ask the streamer to stop; mute your microphone or leave the connected voice channel to stop sending voice. Muting one streamer's mix does not prevent other active mixes from receiving you. Server administrators can remove the bot to stop its access, or restrict channel permissions to prevent future connections.

Email syronius@gmail.com to request access, correction, or deletion, object to processing, or report a privacy concern. Include your Discord user ID, relevant server ID if known, and what you want changed. We may ask you to demonstrate control of the account or server before disclosing or deleting data. Do not send passwords, bot tokens, or private bridge links.

We handle verified requests promptly and within applicable legal deadlines. If some information must be retained by law, we will explain that limitation. Depending on where you live, you may have additional rights, including data portability, restriction of processing, and a complaint to your local privacy authority. Stop commands end live mixes but do not submit a deletion request.

Age requirements and updates

The service is not intended for anyone below Discord's minimum age, including anyone under 13 or a higher local minimum. Contact us if you believe we have received data from someone below that age.

We will update this page when data practices change and revise the effective date. Material changes will be announced on the service website before they take effect where practicable. See also our Terms of Service.