Skip to content
Mahjong Bareng

Privacy policy

Updated 16 November 2026

This policy explains the data used by the Mahjong Bareng operator at mahjongbareng.com to provide gameplay, social features, security and support.

Google login is optional; you can play as a guest.

Account data

After successful login, the server stores your Google account identifier (sub), internal account ID, profile name, email verified by Google, and creation/update times. A table nickname is not your account identity. Profile photos, Google passwords, Google access tokens and refresh tokens are not stored.

Player profile

Each account has a permanent random public player ID, distinct from the Google identifier and internal account ID. The server stores your chosen nickname, revision and update time. Names need not be unique. Changing a profile name does not change your Google account, existing tables, earlier chat or older results. The profile name is used when creating or joining future tables. Your ID and name are used for friends and the Ranked leaderboard.

Friends and invitations

The server stores friendships, requests, blocks and temporary lobby invitations. Search requires an exact player ID and reveals only the public ID and nickname. Online status is shared with friends while an account tab is connected and is updated periodically. Blocking removes the friendship and prevents further requests or invitations. Invitations last 2 minutes; the table code is given to the recipient only after acceptance. Private messages and Ranked are described below.

Sessions and games

Account sessions have no automatic server expiry and are revoked on logout. Account cookies use Secure, HttpOnly and SameSite, last up to 400 days and are refreshed when you open the site while signed in, subject to browser limits. Clearing site data or browser cookie removal may require you to sign in again. The server stores the session-token hash, site origin and creation time. One-use login challenges last 5 minutes. Closing a tab does not log you out.

Guest table sessions are separate from accounts. Your browser stores a resume token and result copies; the server stores tables, recent chat and temporary results. Login/logout does not move seats, synchronize tables across devices or delete results. Voice uses WebRTC; the app does not record audio.

Site activity statistics

A random visit cookie lasts for 24 hours after the latest activity to combine repeat visits and tabs in the same browser. Signed-in accounts are combined across devices; guest visits are merged with the account when the visitor signs in. Temporary online status expires after 75 seconds without an update. For 24-hour statistics, the server stores pseudonymous identifiers and the latest visit and play times; records without a visit for 24 hours are automatically removed. Statistics survive service restarts. The private operator dashboard displays only visitor, player, table, and Ranked queue counts, not email addresses, names, IP addresses, or chat content.

Services and storage

The login button loads Google Identity Services. Google handles authentication according to the information it displays. The app verifies ID tokens on the server. Data is stored on this service’s server. Account data has no automatic deletion schedule. Operational backups are stored separately and managed by the operator. There is no public data-reset button.

Data questions: mahjongbareng@gmail.com. This page describes the current implementation; it is not a promise of permanent storage or service.

Private messages between friends

Text messages are stored on the server so history remains available after you log in again. Only the two participants can read them through the app. Messages are not end-to-end encrypted. Sending requires an active friendship; after removal or blocking, history remains readable as an archive and notifications stop. Messages are limited to 1,000 characters and 4,096 bytes; sending limits help prevent spam.

Ranked and season history

Ranked requires an account and four human players from the solo queue. The server stores matches, the four participant accounts, recovery snapshots (including private hands and seat tokens), final scores, exact point ledgers, season history, and audits of bot assistance and opponent pair frequency. Snapshots are not shared through the leaderboard. The leaderboard shows public ID, name, tier, points and completed-match count; it does not display emails or Google identifiers.

Points restart at zero on the 1st of each month at 00:00 Asia/Jakarta; previous season history is kept. Ongoing matches count toward the season in which they started. Leaving a page does not delete results. The same account can resume active Ranked after logging back in. Temporary queues are lost on server restart, but active matches are recovered. Ranked history has no automatic deletion schedule.

Match history policy

Only Ranked history is recorded. Public and private casual matches are no longer added to account or browser history. This change does not delete older saved data. Round results and the latest result copy for resuming a table session may still be available.

Missions, Jade and cosmetics

The server stores your Jade balance, cosmetic ownership and equipment, mission progress, achievements, and reward and purchase records. Eligible casual and Ranked round results are recorded to calculate rewards and prevent duplicate grants. These records are separate from Ranked match history. Jade cannot be purchased with money, transferred, cashed out, or exchanged for prizes of monetary value.

Cookie keamanan acak dipakai untuk mengenali browser peserta undangan, termasuk tamu, dan membatasi hadiah berulang. Cookie ini berlaku hingga satu tahun; tautan penanda pengundang berlaku paling lama tujuh hari dan hanya untuk meja asal. Identitas browser tidak ditampilkan kepada pemain lain. Menghapus data browser dapat menghilangkan pengenalan undangan. Data hadiah dan kepemilikan disimpan bersama akun; riwayat yang terlihat memuat 150 aktivitas terakhir. Permintaan penghapusan dapat disampaikan melalui Kontak & laporan.

Frames appear on lobby seats, tile backs on concealed tiles, and the table theme follows the host. An equipped badge appears when a player profile is opened. Jade balances and history are available only to the account owner.

Browser storage and connections

The browser stores language, sound and display preferences, guest names, tile order, table-resume tokens and the latest result copy. You can clear them in your browser’s site-data settings; doing so may prevent resuming a table session.

The server receives IP addresses and connection information to handle requests, limit abuse and diagnose errors. Voice uses WebRTC through voice and relay services; audio is processed for delivery to players at the table. The application does not provide audio recording.

Google AdSense and ad choices

The site does not currently display Google AdSense ads. Google sign-in is a separate service from advertising.

If Google ads are enabled, Google and advertising partners may place or read cookies and use web beacons, IP addresses and device or browser identifiers to serve, measure and, where permitted, personalize ads. Information may be processed with advertising service providers according to applicable policies and consent choices.

If ads are enabled, visitors in regions requiring consent will be offered privacy choices before advertising cookies or processing that requires consent are used. Those choices must also be available to change later. This applies to non-personalized ads too when consent is required.

Data requests and reports

Use Contact & reports for questions, corrections or account-data deletion requests. The operator needs to verify account ownership. Data still needed for security or dispute resolution, and operational backup copies, may require separate handling. No automatic retention period is currently set for account and Ranked data.

When you email a report, the sender address and report contents are used to investigate and respond. Avoid unnecessary sensitive information. Material changes to data practices will be reflected on this page with an updated date.