Privacy.

One BALL ID

The Royal Rooftop uses the same Firebase Authentication project and BALL ID identity as MEME BALL. Firebase handles email-and-password or Google sign-in. The rooftop does not keep your readable password or a separate password database. Email verification and password-reset messages use the BALL ID authentication service.

To connect your account, we verify your Firebase identity and retrieve your existing BALL ID profile. The rooftop keeps a local record of your account ID, email, verification state, public name, access permissions, and associated rooftop resident. Your sign-in email is not a public profile field. Your chosen BALL ID name can be shown to other guests.

Google sign-in uses the identity and email information needed to authenticate your BALL ID. It does not request access to Gmail messages, contacts, Drive files, or calendars. Google and Firebase process sign-in under their own service terms and Google’s Privacy Policy.

Your resident and shared spaces

We save the profile and appearance information you choose, along with supported progress, inventory, friendships, blocks, invitations, access permissions, and room or home settings. Your avatar, public profile, movement, gestures, chat, game actions, and shared media are visible to the participants admitted to the relevant room.

The current rooftop session’s room chat is stored so guests joining later can read the conversation. It remains through reconnects, empty rooms and door changes until an administrator starts a new chat session. Earlier messages are then removed from active history; operational backups may retain prior copies. Activity rankings store accepted shooting statistics and eligible completed match or hand results across visits, linked to your resident and displayed under your current name. Removing a resident removes their saved ranking totals. Community-board submissions and problem reports are stored and may be reviewed by authorized operators. Other participants can still copy or record information they receive.

Conversation and screen sharing

Microphone and screen sharing are optional and require browser permission. Browser-to-browser media connections, with a relay where available, deliver media to authorized participants. Network information such as IP addresses can be exposed to the connection services or other participants as part of making those connections.

The rooftop does not include server recording of live room voice or shared screens. Other participants may record what they hear or see. You can mute, leave voice, stop sharing, and change permissions in your browser. Choose carefully which tab, window, or screen you share.

Talking to GAME 5 BALL

The interactive ball is a separate AI feature that starts when you activate it. If you record a question, that recording is sent through the rooftop and the existing GAME 5 BALL voice service. The service uses ElevenLabs for speech recognition and the project’s authorized voice performance, and xAI for generated responses. Typed questions and a limited recent conversation context are also sent for this purpose.

The AI voice is not a live call with Tyrese Gibson, Scottie Pippen, or another guest. Avoid including private account details or sensitive personal information in a question. Provider processing and retention follow the settings and policies of those services, including ElevenLabs and xAI. The rooftop checks access and applies request limits before forwarding a question. The dedicated voice gateway keeps a hashed account identifier with short-lived queue, replay-prevention, and usage-count records. These gateway records do not contain your question or audio. Expired records are cleaned during later requests; hosting logs and AI-provider records are separate.

The written concierge guides are authored responses processed in your browser. Their conversation controls do not listen to your microphone.

The MEME BALL arcade

Opening an arcade connects your verified BALL ID to MEME BALL using a short-lived, one-use handoff. Your credentials are exchanged with the approved MEME BALL service; authentication tokens are not added to page addresses. The game then uses its own account session, gameplay services, and saved progress.

The game can run in an embedded window, or a connected separate window if your browser restricts embedded sign-in storage. MEME BALL receives your shared account identity and information needed to operate the game. Scores, purchases, credits, and other game records are handled by MEME BALL, separately from rooftop room state.

Event and partnership inquiries

When you request a private walkthrough, event or partnership, we store the contact details and plans you submit, your permission to respond, a request reference and delivery status. A signed device identifier and hashed email are used to limit duplicate or abusive submissions. Your request is sent to contact@theballfoundation.com so the BALL Foundation team can respond. It does not create a BALL ID, grant rooftop admission or confirm a booking.

Inquiry records in the rooftop service are automatically removed after 180 days. Copies in the team’s email inbox and operational backups are separate and may be kept while a conversation or engagement is ongoing. You can contact the team to request access, correction or deletion. We do not add you to a marketing list through this form.

Cookies and browser storage

Necessary cookies hold your rooftop account and game sessions and a signed random device identifier used to limit abusive sign-in requests. Firebase also stores authentication state in your browser to keep your BALL ID signed in. These are service functions, not advertising identities.

Local preferences can include avatar appearance, camera and sound settings, home choices, and progress. A pending room invitation can be kept for the current browser session. Signing out ends rooftop account access and signs out BALL ID in this origin. It does not automatically sign out every other browser or a separately opened MEME BALL session. Clearing this site’s data removes locally stored preferences. Blocking necessary cookies or storage can prevent sign-in or saving.

Operating the experience

Hosting and network providers, including OpenAI Sites, Cloudflare, the game server’s hosting service, and Firebase, process information needed to deliver and protect the experience. This can include network addresses, browser and request details, authentication records, and operational measurements.

A problem report can include your text, resident ID, room, position, camera, reported frame rate, and application build. Common email and credential patterns are scrubbed, but this cannot detect every private detail. Authorized operators use reports and security records to investigate problems, manage access, and moderate the experience.

A shared YouTube video, website, or other external service can receive requests and apply its own cookies or privacy practices when loaded. Choose shared media carefully. External links take you to the destination service.

Retention

Saved resident records, relationships, room state, reports, and operational history remain until changed or removed; there is not one automatic deletion period for all records. Earlier values may remain in operational records or backups after a profile change.

Rooftop account sessions expire within approximately one hour and can refresh while you remain signed in. Unused arcade handoff codes expire after sixty seconds, and redemption consumes them. These short-lived records are distinct from your persistent Firebase identity, MEME BALL account, and saved rooftop resident. Provider logs and backups can have different retention periods.

Your choices and requests

You can edit available profile fields, remove social links, manage friendships and blocks, sign out, and control microphone and screen permissions. Removing a Google connection in your Google Account settings does not itself delete your saved rooftop or MEME BALL records.

Contact kb@theballfoundation.com to request access, correction, or deletion. Please specify whether your request concerns The Royal Rooftop, your shared BALL ID, MEME BALL, or all of them. Removing a rooftop resident and deleting the shared identity have different effects. We may need to verify your account and explain limits involving security records, unresolved issues, backups, or information already shared with other people.

Changes

This page will be updated as the experience changes. Features that materially change how information is used will receive appropriate notice and any required additional permission.