PRIVACY AT THE TABLEYour cards.
Your boundaries.
MonkeyTable is designed to limit what other players learn about you. It cannot promise complete anonymity, prevent someone from recording a screen, or guarantee protection against every online attack.
Google sign-in and your table name
An account is required to play. Google verifies sign-in; MonkeyTable uses an opaque, keyed hash of your Google account identifier to recognise your account. The app does not persist your Google name, email address, or profile photo. Your opponent sees a randomly assigned table nickname and a random player identifier.
A cookie keeps you signed in for up to seven days. Production sessions use secure, HttpOnly cookies, and the server stores a hash of the session token. Signing out revokes that session.
Private cards and game records
The server deals cards and evaluates hands. Every player receives only their own hole cards, including after a result. The server’s database contains the full hand state for game recovery and settlement; authorised operators with database access can read it.
Game actions, chip settlements, account cosmetics, blocks, and private reports are stored on the service. Pseudonymous analytics associate events and timings with random player or match identifiers. Avoid putting personal details in report descriptions.
Your camera and microphone
Live tables require camera and microphone permission before matchmaking. Permission is requested after your action. Your preview stays on your device until a match begins. During a match, media is sent through the configured LiveKit service. The app does not record calls. Mute and camera pause controls remain available.
Your face, voice, surroundings, or things you say may identify you. Another player can capture what they see or hear. Filters change the picture’s appearance; they do not make you anonymous. The media and hosting providers process connection data, including network addresses. Media uses a managed relay rather than a direct connection between opponents.
Cosmetics and payments
Card skins, chip skins, and camera filters are cosmetic. Play chips cannot be bought, transferred, redeemed, or converted into prizes. Payments are entered on the configured provider’s hosted checkout; MonkeyTable does not handle payment card numbers.
Checkout screens, receipts, and bank statements can show the merchant’s business identity or support information as configured with the provider. The operator must verify those details before enabling paid purchases. Payment processors may need customer and business information; complete anonymity cannot be promised.
Safety, retention, and support
Use report and block controls when someone behaves unsafely. The app limits requests and protects access to matches and account items. Those measures reduce exposure; they cannot stop a player from sharing personal information or prevent every denial-of-service attack.
This installation has not yet published an operator support address, retention schedule, or account deletion process. Those details, restricted moderator access, and a response workflow must be provided before public launch. No personal contact details are invented here.