Reference

rumahplay Privacy Policy for wallet data

Clear privacy choices sit beside your account path, so the rumahplay Privacy Policy tells you exactly why we ask for phone verification, wallet status and device cookies.

Phone verificationDANA and QRIS recordsCookie controlsAccount change requests
rumahplay rumahplay Privacy Policy for wallet data
CONTACT PATHS

Three ways to ask privacy questions

Privacy questions should not send you around the site. We keep contact paths close to the account and cashier screens because most privacy requests start with phone verification, wallet status or a receipt check. Use the signed-in help form for identity-related changes, the cashier status screen for DANA or QRIS records, and the policy contact path for cookie or retention questions.

Team online

Signed-in help form

After login, open Account, choose Help, and describe the Privacy Policy request with your registered phone number. We ask for one account detail before discussing records, so we do not expose your data to another person.

Cashier status check

For DANA, OVO, GoPay or QRIS questions, attach the receipt ID from the cashier screen. We compare wallet status with your account record before explaining what data was saved.

Policy contact path

For cookies, retention or correction requests, use the privacy contact link shown at rumahplay.xyz/privacy-policy/. Include the date, device browser and account email so we can locate the relevant log.

ACCOUNT CARE

Six privacy controls inside your account

Account privacy works when each data point has a job. We use phone verification to protect account access, cookies to keep your session stable, and wallet records to reconcile DANA, QRIS and…

Phone verification

Your phone check confirms that the account path belongs to you before lobby access. If the number changes, support records the request time and asks for matching account details before any update.

Wallet record scope

DANA, OVO, GoPay, QRIS, virtual account and bank transfer records are used for cashier matching, receipt checks and accounting retention. We do not use those wallet records to publish public activity.

Cookie choices

Cookies keep login state, remember language display and help the lobby load the last category you opened, such as Blackjack or Football Betting. You can clear them in your browser settings.

Session security

If we see repeated failed login attempts, we may pause account access and ask for another verification step. This protects the privacy of your wallet status, balance screen and profile data.

Retention requests

When you ask us to correct or remove data, we check whether cashier, bank transfer or account-security records must be kept for reconciliation. We then explain what can be changed.

Support privacy

Support replies are limited to the account details needed for your question. A Bingo result, Fishing God session or Crash Games history is discussed only after identity confirmation.

Privacy Policy questions before account access

You may arrive here before you open an account or after a wallet status does not match what you expected. These answers keep the Privacy Policy practical: what we collect, why we collect it, how you ask for changes, and how local wallet records are handled. They also explain how mobile cookies affect the path from login to the lobby.

We collect the details needed to create and protect your account: phone number, login credentials, account email, device browser data and verification time. We use those records to confirm access and support later privacy requests.

For DANA and QRIS, we keep cashier references such as receipt ID, wallet status, amount, time and account match. These records help us trace payment questions without asking for unrelated wallet details.

Yes. Send the request through the signed-in help form and include the field you want corrected. We verify your identity first, then update eligible account data or explain why a record must remain.

We use availability wording because access depends on local law, but we do not ask for extra location data unless it is needed for account security, payment checks or a support request.

Cookies help keep your login session active, remember display choices and reopen the last lobby category you used. You can clear cookies in Android Chrome or iOS Safari settings, then log in again.

Only support staff handling your verified account question can check relevant activity, such as Blackjack, Football Betting or Crash Games history. We use it to answer the request, not for public display.

Retention depends on the record type. Account changes, wallet receipts, QRIS scan references and bank transfer logs may be kept for reconciliation, security checks and required accounting periods before removal is considered.