Your sound. Your devices.

Who provides AudioFlux

AudioFlux is a BBDX Labs project. For privacy questions or requests, contact hello@bbdxlabs.com.

Microphone input

When you grant permission and start live input, the Android app accesses your microphone to analyze sound. It calculates loudness, frequency bands, note-energy values, transient information and a reduced waveform preview. Short working buffers are held in memory while processing. The native Android capture path does not save microphone recording files.

The app sends these derived measurements to your paired Roku so it can render the visuals. Raw PCM audio and playable audio recordings are not sent by the live visualizer protocol. The core feature does not send microphone data to BBDX servers. Stop the microphone to end capture; native capture also stops when the app enters the background. Demo mode uses bundled analysis data and does not need the microphone.

Optional camera access

If you choose QR pairing, the companion uses the camera to read the code displayed by your Roku. The pairing feature does not save or upload camera images. Camera permission is not required for manual IP-address and PIN pairing.

Local connection and security

The apps exchange pairing information, visualizer measurements and control requests over your local network. Pairing creates a token that authorizes the phone to communicate with the Roku. Local HTTP traffic is unencrypted, including pairing and control messages. A pairing PIN is not end-to-end encryption.

Use AudioFlux only on a trusted network and do not expose its service to the public internet. AudioFlux does not require a BBDX account for this connection.

Preferences and retained data

The phone stores the Roku address, pairing state and token, and your companion preferences locally. The Roku stores its pairing token, selected visualizer and mode, input choice and visualizer preferences. These values let the apps reconnect and restore your setup after a restart.

Live analysis uses short-lived working state rather than an audio archive. Stopping or closing capture releases the native microphone session. Saved pairing and preferences remain until replaced, reset or removed from device storage. Device backup and restore features may also retain app data according to your operating-system settings.

Your controls and deletion

You can stop live input, revoke microphone or camera permission in Android settings, or use Demo without microphone input. Re-pair on Roku replaces the current pairing token and disconnects the old phone. This does not erase visualizer preferences.

Clear AudioFlux storage in Android settings to remove its locally stored connection and preferences. Check your device's backup settings if you do not want them restored. Contact us for help removing Roku-side preferences. BBDX does not have remote access to erase data stored on your devices.

Support messages and service providers

If you email us, we receive your email address, message and any details or attachments you choose to include. We use them to answer the request and investigate issues. Our email service provider processes that correspondence. We retain it for as long as reasonably needed to handle the request and meet applicable obligations; you can contact us to request deletion.

Visiting this website also sends ordinary request information, such as your IP address and browser details, to its hosting provider. Store operators and device platforms may process installation, diagnostic or backup information under their own policies. This is separate from AudioFlux's direct phone-to-Roku audio-analysis flow.

Changes

We will update this policy when AudioFlux's data practices change. The date above identifies the latest revision. Material changes should be reviewed before continuing to use the affected features.