Updated October 17, 2026

Privacy Policy

What the game uses, why it needs it, and your choices.

1. Scope

This policy covers data processed by the developer of Ruckado to operate this browser game and Discord Activity. Google/YouTube, Twitch, Discord, Stripe and Cloudflare also process data under their own policies. This policy does not cover their services or our other games.

2. Information the game processes

• Identity and room access: your chosen browser display name or Discord user ID and display name, an internal player ID, the Activity instance identifier, room code and session credentials. Discord authorization is used to verify your identity and membership in the Activity.
• Streamer accounts: Google account identifier, verified email address and display name; streamer profile and show settings; invitation redemption records; and a private login session. Google sign-in requests basic identity information only. The game does not request access to Gmail, contacts or Google Drive. Tokens used only for Google sign-in are not retained. Connecting a YouTube broadcast is a separate authorization described below.
• Connected broadcasts: when a creator connects Twitch or YouTube, we store the authorized channel ID and name and encrypted access/refresh tokens to read live interaction events and respond to supported chat commands. We process verified paid-event IDs, amounts in native units, gift combo counts, viewer platform IDs and names, effect selections, and delivery status. Short-lived command, link and rate-limit records support votes, queues and account linking; ordinary chat history is not saved. Disconnect a channel in Creator Studio to remove its saved tokens and request revocation. You can also revoke access at Google account permissions or Twitch Connections. Existing game-account links can be removed in Player access. Disconnecting does not erase transaction records.
• Gameplay: your selected character and level, room membership, connection status, movement, role, health, carried item, puzzle progress and room win totals.
• Purchase access: Stripe checkout, payment and receipt identifiers and Discord product and entitlement identifiers; paid, free and test coin balances; purchase and spending records; item inventory; and creator attribution used to maintain the common wallet and earnings ledger. Stripe or Discord handles payment details. Ruckado does not receive your full payment-card number or bank details.
• Technical information: network requests and errors needed to operate and protect the service. Cloudflare processes connection information, which may include IP address, request time, URL and browser information. Operational logs may be retained under the hosting configuration.
• Support: any information you voluntarily send through the developer’s support channel.

3. Voice, messages and tracking

The game does not record voice conversations or read Discord channel messages. The Microphone of fire protection can use Discord speaking-status events, with voice-read authorization, to activate its fire effect. Where those events are unavailable, an Enable microphone button requests device access. Sound level is processed locally; only an active/inactive signal is sent to the game server. Audio samples are never recorded, stored or uploaded by the game. Dropping the item, leaving the match or closing the tab stops the device microphone listener. Discord handles voice chat separately. The game does not include advertising trackers, third-party marketing analytics or a sale of player data.

The browser stores the room code, player ID, display name and session token in sessionStorage so your tab can reconnect. Leaving the expedition removes the game’s saved session. Browser settings can also clear it; doing so may end your ability to reconnect to that browser room. Streamer sign-in also uses an HttpOnly login cookie that expires after 28 days and a short-lived Google sign-in cookie that expires after ten minutes. Sign out to invalidate the streamer login and host game session. A separate HttpOnly audience login cookie lasts up to 30 days and links your verified Discord identity to your website wallet. Hosting, Google, Discord and Stripe may use their own storage or cookies under their own policies.

4. Why information is used

We use this information to join you to the correct room, run multiplayer matches, synchronize play, display room results, restore purchase access, prevent unauthorized access and respond to support requests. Where a legal basis is required, this includes providing the service you request, our legitimate interests in security and reliable operation, and compliance with applicable legal obligations. We do not use game data for targeted advertising.

5. What other people see

The public show directory displays streamer display names, show titles and welcome messages, current rides, live status, audience counts and recent gameplay thumbnail images. Registered streamer profiles remain discoverable while offline. These thumbnails capture the rendered game world, not account settings or wallet dialogs. Streamer email addresses and login credentials are not included in the directory.

Other players in your room see your display name, character, health, readiness and room win totals, host branding, purchased participation roles and gameplay announcements. Audience members can choose a host or cast camera. Private wallet balances and item inventories are not shared with other viewers. Gameplay information is limited according to the selected camera and role. The phantom receives additional player-location information as part of the game. Private clues and hidden roles are only sent according to the game’s rules. Do not use sensitive personal information as your display name or share it in a public support channel.

6. Service providers and sharing

Cloudflare hosts the game, static assets and multiplayer room state. Google verifies streamer sign-in. Connected YouTube and Twitch channels provide live chat and paid interaction events; the app can post replies to supported commands as the connected creator. These integrations use the YouTube API Services and Twitch APIs. Discord provides audience sign-in, Activity membership, voice and purchase verification. Stripe provides website Checkout, Link and payment verification; the checkout shares an internal order and wallet reference with Stripe to credit the correct account. Information is shared with these providers as necessary to provide those functions, and may be disclosed if required by law or necessary to protect users and the service. Providers may process information outside your country under their own applicable safeguards.

Read Stripe’s Privacy Policy, Twitch’s Privacy Notice, Google’s Privacy Policy, Discord’s Privacy Policy and Cloudflare’s Privacy Policy for their processing practices.

7. Retention and security

Room state, sessions, cached ownership and scores are stored in Cloudflare Durable Objects. Ruckado keeps show snapshots, host preferences, wallet balances, item inventory and transaction records across sessions. Leaving a show does not delete these records. Streamer login sessions expire after 28 days, pending sign-in state after ten minutes, and unused streamer invitations after 14 days. Apart from expiring authentication records, no automatic retention expiry is currently configured for this preview; contact the developer for an access or deletion request.

Stripe and Discord maintain their payment records separately. Removing a room does not remove those records. Technical logs, provider backups and support correspondence may have different retention periods. We use HTTPS and hashed server-side session tokens; no online service can guarantee absolute security.

8. Your choices and requests

You can stop playing, leave a room, clear browser session storage, and manage the app’s authorization in Google or Discord. Depending on your location, you may have rights to access, correct, delete, restrict or object to processing of your information, or receive a portable copy, and to complain to a relevant privacy authority.

To make a privacy request, contact the developer and identify this game, the request and your Discord user ID or room code if relevant. We may need to verify that the request relates to your account. Do not send passwords, bot tokens, payment-card details or OAuth secrets. Requests concerning Discord’s own account or billing records must also be directed to Discord.

Contact game support · hollandomauricio@gmail.com

9. Children and policy changes

The game is not intended for children under 13 or anyone below the applicable minimum age for Discord in their location. If you believe a child has provided personal information through the game, contact the developer. We may update this policy as the game changes; the date above identifies this version, and material changes will be communicated through the app or support channel.