Scope
This notice describes the BlueBee 0.1.0 candidate for iPhone, iPad, Android and foreground web listening. BlueBee is free for now. It has no BlueBee user account, in-app purchases, subscriptions, advertising, analytics SDK or behavioural tracking integration. A listening room still sends the information needed to share audio and keep its participants on one timeline.
This notice is a draft for release review. A public store release is not announced by this page.
Shared audio
When you start device-audio sharing, BlueBee sends permitted playback audio through its Cloudflare-hosted relay to listeners who join your room. The relay forwards live audio in memory; the inspected implementation does not save an audio recording. Transport uses secure WebSockets to the configured public relay. This is not end-to-end encryption: the relay processes the audio and room messages.
iOS uses a ReplayKit broadcast extension and forwards app-audio samples. It ignores video and microphone samples delivered to the extension. Android uses MediaProjection permission and AudioPlaybackCapture to read playback audio from compatible source apps. The Android capture path does not create a video stream or send screen images. Both operating systems and source apps can prevent capture, including for protected content.
For a room using a direct audio link, the link and media title are shared with the relay and room participants. Each listener downloads that audio from its original provider. That provider receives the network information needed to serve it. Do not use a link containing credentials or content you do not intend to share. Built-in test audio is generated on each listener’s device.
Room information
The relay receives room identifiers and names, participant identifiers, chosen display and output-device names, platform information, playback state and timing/buffer diagnostics. Room members can see the participant and room information used by the listening interface. Room codes grant admission to the room; keep them within your intended group.
To recover interrupted rooms, the relay also writes a bounded room checkpoint to Cloudflare Durable Object storage. It includes room/media metadata, participant information, playback state, timing diagnostics and hashed recovery-token verifiers. It excludes live audio samples. Recovery tokens are used to restore the same participant and host authority; they are not BlueBee account credentials.
Room recovery data follows the relay’s room-expiry and cleanup rules. Expired checkpoints are removed by cleanup or when the relay next restores them. An expiry time is not a promise of immediate physical erasure from provider storage or backups. Operational-log and backup retention must be confirmed as part of release review.
On your device
BlueBee saves display/output names, preferences and manual timing profiles in app storage or browser storage. The iOS app and its broadcast extension share local broadcast configuration and status through an app group. Generated test audio and deliberately exported diagnostic files may remain in the app cache; browser exports are downloaded files. The current calibration interface is manual. The acoustic test instructions use a separate recording device or tool.
The app keeps a bounded diagnostic history in memory. Exporting it creates a file for you to review and share using the system share sheet or browser download. It is not automatically sent to support. Review diagnostic files for room, device or network details before sharing them.
Permissions
- Camera: optional, for scanning room QR codes. You can join by code instead. BlueBee does not upload camera frames.
- Android audio-recording permission: required by Android for playback capture. BlueBee’s capture source is compatible app playback, not the microphone.
- ReplayKit or MediaProjection consent: requested when you start device-audio sharing. The operating system displays and controls the capture session.
- Local network: used when connecting to a local development relay or an available local helper. Normal public rooms use the configured internet relay.
- Background audio and Android foreground services/notifications: support native playback or active capture while the app is not in front. Browser listening needs a foreground page and an explicit audio gesture; iOS browser background listening is not promised.
You can change permissions in system Settings. Denying an optional permission leaves the unrelated features available.
Services and logs
Cloudflare hosts the public relay and browser app. It processes connections, including IP addresses and ordinary service/request information. The relay uses network addresses for connection limits and abuse controls, and deployment configuration enables Cloudflare observability. These operational data flows are separate from advertising or behavioural analytics. Their exact deployed log settings and retention are still under release review; this notice does not promise that no connection logs exist.
The Netro Labs information website has its own website privacy notice. External media links, operating-system services and a support message you choose to send involve their respective providers. Desktop web code may check for a BlueBee helper on the same computer; Mac distribution is outside this mobile release candidate.
Your controls
Stop sharing to end capture; leave a room to end your participation. The host ending a room ends that shared session. You can remove saved timing profiles, clear app/browser storage, change permissions and delete downloaded exports. Removing local data does not erase a support email or provider operational logs. There is no BlueBee account to delete.
Contact
Netro Labs is operated by James Nettey. Privacy and support enquiries can be sent to support@zedipass.com. If you contact support, your address, message, attachments and delivery information are processed to receive and respond to your request. Existing Netro Labs support retention is only as long as needed to respond, support users, maintain necessary records, resolve disputes or meet legal obligations.
You may use that contact to ask about information held about you or request correction/deletion where applicable. Do not include active room codes, recovery tokens, passwords or private media links. This notice will be reviewed when BlueBee’s capture, relay, storage, SDKs or business model changes.