SUPER COMPUTER Audience Privacy Notice

Last updated: October 11, 2026. Applies to the SUPER COMPUTER audience app, its show service, community chat and optional AI bot.

Who operates the app

SUPER COMPUTER operates this app. Contact contact@supercomputermusic.com for privacy questions, account assistance or moderation concerns.

Information the app uses

• Account information: a randomly assigned guest ID, nickname, sign-in credentials, account restrictions and blocked-user preferences. Choosing anonymous entry or beginning email verification can create a guest account even if you do not post. If email sign-in is available and you choose it, your email is used to deliver a verification code; the account database stores a hash for matching your email rather than a plaintext email address. Verified members can choose a curated 32-by-32 pixel avatar. Their selected avatar appears with community messages.
• Community messages: your text, nickname, message and account IDs, timestamps, delivery status, emoji reactions, reports and moderation decisions. Approved posts and reaction totals are visible to other people with access to that room. Messages can be copied by those people.
• Private bot conversations: your submitted text, the bot's replies, recent conversation context and request metadata. These conversations are not posted to community rooms. They are processed on our servers and by our AI provider; they are not end-to-end encrypted.
• Optional voice: while using push-to-talk, a short microphone recording is uploaded for transcription. The transcript is used as your bot message. Generated speech reads the bot's reply. The audience app does not require microphone access to watch shows or use text chat.
• Optional sound-reactive visuals: when you enable the local microphone effect, your phone measures sound level to change the brightness of its current visual. This processing stays on your phone; it does not save a recording or send microphone audio or sound levels to the show service. It stops capturing when you leave the viewer or put the app in the background.
• Show participation and performance: a separate participant ID, joined event, supported visuals, connection times, network latency, clock offset, frame rate, late cues, screen visibility, battery level, thermal state and nearby-device count. These help synchronize visuals, count participants and diagnose failures.
• Nearby-chat diagnostics: opted-in phones can report queued-operation counts, delivery-time estimates and errors to the service when connected. The host sees recent reported totals and their age, not a live count of isolated phones. These summaries do not contain message text.
• Network information: our hosting service receives connection information such as your IP address. The app's service also temporarily stores the connecting IP for guest-account rate limiting.
• Optional nearby features: choosing Nearby events sends the location coordinates supplied by your phone to the service to find events near you. Coordinates are not deliberately added to our event database, but they are included in the request URL. Optional Bluetooth diagnostics detect nearby app devices and signal strength; the show service receives the nearby-device count. When the host and you enable SUPER MESH, foreground phones exchange encrypted, service-signed show cues and clock replies over Bluetooth. A nearby online phone forwards read-only synchronization requests to the show service; it can see your event participant ID and approximate signal strength, but this visual-backup route receives no account credentials or chat messages. Media files use the internet cache rather than Bluetooth. Visual backup stops when you leave the Live viewer or background the app. Bluetooth proximity is not a precise distance measurement.
• SUPER MESH community chat: after online enrollment, if a room allows nearby posting and you enable it, participating phones can store and forward signed public-room text, deletion records and service decisions over encrypted Bluetooth links, including when all of them are offline. The app shares room/account IDs, public device keys, signed permissions and message identities; it does not share your account bearer token or private device keys. Forwarding is limited to four hops and a twelve-hour permission window. Authorized participants and relays can read room text, so this is not private end-to-end messaging against those participants. Nearby text may appear before cloud moderation; cached restrictions, local blocks and a local filter apply, but new bans or removals cannot instantly reach an isolated group. When an internet connection becomes available, a gateway can submit original signed messages for current account checks and cloud review, and relay the resulting decisions. Previously viewed or copied text cannot be recalled. Nearby chat excludes private bot conversations, voice, attachments and new offline emoji reactions.

The app stores sign-in credentials in iOS Keychain. It also keeps drafts, failed outgoing messages, preferences, cached show media and diagnostic reports on your phone. The selected idle and offline screens, including downloaded images or videos, are retained locally so they can appear without an internet connection. Replacing them releases the previous retained media after the new selection is ready. Diagnostic reports are saved automatically during use; sharing a report sends it through the destination you choose.

SUPER MESH is experimental and is offered during first-run setup. It starts only after you choose Enable SUPER MESH and allow Bluetooth; you can choose Not now instead. Your saved choices, including an earlier choice to turn it off, are preserved. Visual backup and nearby posting can also be controlled separately.

Ordinary backgrounding stops show rendering, video playback, microphone capture and visual Bluetooth backup. Optional Keep active while locked is a separate choice for community chat on iOS 26 and later, shown by a Live Activity. That session ends after 15 minutes in the background, including when the phone is locked, or when you use Stop or dismiss its activity. iOS may interrupt it sooner. It does not use microphone audio to stay active, and relaunching the app does not resume a locked session. Older systems use nearby chat in the foreground. The app does not promise delivery after force-quit or when Bluetooth or the session is unavailable.

Why information is processed

We use this information to deliver and synchronize shows, maintain accounts and conversations, respond through the bot, moderate the community, prevent spam and abuse, enforce usage limits and investigate technical problems. The current app has no advertising or advertising-tracking integration.

Community text and nicknames are screened automatically and may be reviewed by moderators. Avatars come from a curated set rather than custom uploads. Moderators can review held messages and reports, remove posts, clear account avatars and restrict accounts. If a room's bot is enabled, approved room messages may be used as its context. Private bot history is not included in that room context.

Service providers

Cloudflare hosts the service, stored application data and show media. See Cloudflare's privacy policy.

OpenAI processes bot prompts and recent context, replies, moderation inputs and, when voice is used, recordings for transcription and reply text for speech generation. Bot response requests use store: false; this does not mean the provider retains no data. OpenAI states that API data is not used to train its models by default unless the customer opts in. Its retention rules vary by endpoint, including default abuse-monitoring retention for text responses and generated speech. See OpenAI's API data controls.

Resend, when email sign-in is enabled, receives your email address and verification email to deliver the sign-in code. See Resend's privacy policy.

These providers operate infrastructure that may process data outside your country. Our app's deletion controls do not promise immediate erasure from provider infrastructure or copies other users have made.

Retention and deletion

Approved community posts remain until deleted. Deleting your own post removes its published text; a copy already included in a moderation report can remain for review. Held or rejected text, reports and moderation audit records become eligible for periodic cleanup after 30 days. Cleanup is scheduled rather than an exact deletion deadline.

Selected avatars and any earlier submitted avatars remain with your account until you replace or remove them, a moderator clears them, or you delete the account. Emoji reactions become eligible for cleanup after 30 days and are removed when their message or account is deleted.

The phone's bounded local chat cache keeps recent history for up to 30 days. Drafts and unsent operations remain available for retry rather than being silently discarded when a connection fails. Removal records can remain during the reconciliation window to prevent a deleted message reappearing. Other participating phones may retain their own cached copies until they receive a deletion or their cache is cleaned up.

Private bot context is limited to recent turns and is not reused for a new conversation after an hour of inactivity. Stored request text and generated speech become eligible for cleanup after approximately an hour. Request identifiers and usage records can remain longer for retry protection and accounting. This server cleanup does not automatically erase unsent drafts on your phone.

Deleting your community account removes its sign-in records, avatars, emoji reactions, private bot context and authored community text, and clears that account's drafts and outgoing queue on the current phone. Some message identifiers, hashes, timestamps, moderation records and technical metadata remain. Separate show-participation records and local show diagnostics are not removed by community account deletion. Continuing to use the app can create a new guest account.

The pilot does not yet have an automatic expiry for every category of show-participation metadata or local cached data. Provider retention follows the applicable provider policies and settings.

Your controls

You can edit your nickname, choose or remove your member avatar, add or remove member emoji reactions, delete your own messages, report or block another user, reset your private bot conversation and delete your account in the app. Anonymous entry retains show viewing, chat and bot access under the service's existing rules and availability settings. SUPER MESH nearby chat and visual backup can each be turned off; drafts and cached history remain usable when nearby permission expires. Account removal clears its local participation and state; remote revocation and removal reach other phones when they reconnect. You can revoke microphone, location or Bluetooth permission in iPhone Settings. Show codes provide an alternative to location-based discovery. You can use text instead of voice.

For access, correction, deletion or other privacy requests beyond those controls, contact contact@supercomputermusic.com. Include your nickname and the relevant event or message details; do not send your password, sign-in code or account token. Available privacy rights depend on where you live.

Notice updates

Changes to the app's data handling will be reflected in an updated notice and date.