Your people. Your choices. Your data.
Privacy notice · beta service · updated 27 October 2026. This describes the current web app. It is not a claim of worldwide legal compliance.
What the service uses
Native sign-in supplies account identity for hosts. The app stores host profiles, credit transactions, account preferences, owned knowledge packs and game designs. Rooms contain player nicknames, choices, scores and game state. Guests can join without accounts. Use nicknames and avoid health, financial, explicit sexual or other sensitive personal information.
Why data is used
Room data runs multiplayer games and enforces access. Account identity protects hosting and authoring. Credit records prevent duplicate charges and grants. Explicit tastes rank games. General game activity counts support lifecycle review, human-group completion and same-room replay measures; these do not identify unique returning people. optional post-game feedback supports human review. These are product purposes, not a completed jurisdiction-specific lawful-basis assessment.
Competitive scores and leaderboards
Completed general-audience competitive games save participant nicknames, computer labels, team assignments, scores, placings and scoring settings to a host-private record book. These records remain after a room expires; they are not public global rankings. Guests may optionally sign in and save only their own result while their session is available. Personal bests separate game settings, field size, computer difficulty, custom formats and team mode; late-join results are excluded from best-score boards. Practice and private adult sessions do not create these records. Scores do not include raw answers, secret roles, knowledge source text or authentication tokens. Account exports include bounded hosted and saved result records. Removing an account score link does not remove the host event result. Complete account deletion and a defined cleanup schedule remain operational launch requirements.
Private couples sessions
A single-use invitation, host approval and two player sessions restrict entry. Each person sets comfort limits; the lower limit applies. Both confirm readiness. Either can pause, skip or end and erase. Couples sessions are excluded from gameplay popularity and feedback collection and do not call an AI provider. They are server-stored, not end-to-end encrypted. Someone can still copy content from their screen.
Payments and credit records
Stripe processes one-time credit payments through the connected BollyWeds billing account. Veytrix stores an opaque checkout reference, your internal account identifier, pack quantity, amount, currency and confirmed payment identifier. Card numbers are entered in Stripe checkout and are not stored by this app. Billing and security records can be retained when you delete application content to support payment reconciliation, fraud prevention and applicable retention duties.
AI and service providers
Optional AI game generation sends the selected knowledge and creative direction to OpenAI using store:false. That flag does not promise zero infrastructure retention or no provider processing. Native Sites hosting, identity and storage process service data. Optional general-room audio/video uses LiveKit when configured; it is unavailable when configuration is missing. Provider agreements, regions, transfer safeguards and retention must be confirmed by the operator before broader launch.
Optional controllers and motion
Gamepad input stays local until converted into ordinary game actions. Phone tilt requires the player to enable it and approve any browser motion prompt. Raw orientation readings are not stored or sent to game servers; only the same steering commands used by touch are sent in shared racing rooms. Choosing Touch disables motion listeners. Backgrounding, missing sensor readings or controller disconnect stop accessory steering. Optional vibration is performed locally when available. Hardware identifiers are used only in page memory to distinguish reconnects and are not added to gameplay telemetry.
Storage and retention
Rooms stop being accessible after 12 hours of inactivity. Expiry is not deletion: expired records may remain until cleanup. End-and-erase deletes the couples room and associated app feedback and session records, revoking player sessions. It does not guarantee physical backup or provider-log deletion. Knowledge packs, designs, ledger and account preferences persist until an applicable deletion process runs; archiving is reversible and does not erase prior exports or generated content. Fixed operational retention and backup schedules remain a launch requirement.
Device storage and tracking
The app uses browser storage for player sessions, appearance, saved games and recent rooms. Private couples host sessions stay in session storage. The app does not add advertising pixels or marketing analytics, and interface fonts use local/system fallbacks rather than a Google Fonts request. Native authentication and infrastructure can use their own cookies and logs. Clearing this device does not erase server records. No newsletter or marketing consent is bundled into play.
Your controls and requests
The data-controls page offers a scoped account export, account-preference deletion and device-data clearing. A couples participant can end and erase the shared session. These controls are not complete account deletion or a complete legal access response. The operator must publish its legal identity, monitored privacy contact, request verification and escalation process before broad commercial launch. Those details are not configured in this beta. Applicable rights can include access, correction, erasure, restriction, objection, portability and regulatory complaint, depending on location.
Young people and sensitive content
Adult collections require an 18+ declaration, not verified identity or robust age assurance. Family-friendly describes game content, not a child-directed service or a completed parental-consent system. The app has no verified parental-consent workflow. Do not collect children’s information or use it as a child-directed service without the necessary safeguards and review. Hosts must have capacity to agree to terms in their location.