Reference

rem4d Privacy Policy for Indonesia Accounts

Your account name, login device, DANA, OVO, GoPay, and QRIS records are covered by this Privacy Policy before you open an account.

DANA recordsOVO checksGoPay wallet dataQRIS privacy trailCookie choices
rem4d rem4d Privacy Policy for Indonesia Accounts
PRIVACY HELP

Contact Us About Your Privacy

A privacy request should reach the team that can read account logs and wallet trails, not a generic inbox. We handle privacy messages through live chat, email, and account help forms, with human support from 10:00 to 22:00 WIB. Include your username, registered phone number, and the payment rail involved, such as QRIS or DANA, so we can find the record without asking you to repeat sensitive details.

Team online

Live chat

Use the chat button after login for urgent privacy questions about recent access, cookie sessions, or wallet records. We may ask you to confirm your username and registered phone before discussing account details.

Email [email protected]

Send account privacy requests to [email protected] if you need a written reply about correction, deletion, or access to records. Add the transaction channel name, not your full wallet balance or PIN.

Account help form

Open Profile, choose Help, then select Privacy Request when you want us to check saved contact details or device sessions. The form attaches your account ID so we can trace the issue cleanly.

DATA PRACTICE

How We Handle Your Data

Privacy controls work better when you know the exact account step involved. We connect login records, payment references, cookie settings, and support messages to your profile so the…

Account setup

When you open an account, we store your username, registered phone, login time, and account status.

Payment records

DANA, OVO, GoPay, and QRIS activity is logged with channel name, timestamp, and reference code.

Cookie settings

Cookies keep your session active and remember basic display choices.

Game session data

If you open Live Dealer Lobby, Galactic Gems, Basketball Betting, or Rocket Crash, we may record session time and account…

Retention checks

Some records stay longer because wallet checks, security reviews, or legal duties require them.

Change requests

You can ask us to correct a phone number, update contact details, or check saved device sessions.

Privacy Questions Before You Join

Before you open an account, you should know what data is requested, how wallet records are handled, and who answers privacy requests. These answers focus on the Privacy Policy for your account, payment trails, cookies, device access, and support messages. If your question involves a specific transaction, contact us with the channel name and reference time so we can check the right record.

We collect your username, registered phone number, login time, device signals, and account status. If you use DANA, OVO, GoPay, or QRIS, we also store payment references needed to match wallet activity.

We keep payment references so wallet updates can be traced, checked, and explained if you contact support. The record usually includes channel name, timestamp, transaction reference, account ID, and related status.

Yes. Contact live chat or [email protected] and confirm your username plus current registered phone. We verify identity before changing contact details, because phone access affects account recovery and privacy requests.

Cookies keep you logged in, remember basic display choices, and help us notice unusual access. You can manage them in your browser settings, but blocking all cookies may force repeated login checks.

We share only the details needed to process or verify DANA, OVO, GoPay, and QRIS activity. We do not send your game session history to a payment provider for marketing use.

Retention depends on the record type. Support messages may be removed earlier than payment references, while wallet and security records may stay longer when needed for checks, disputes, or legal duties.

Use live chat from 10:00 to 22:00 WIB for urgent access questions, or email [email protected] for written requests. Include your username, payment channel, and request type, but never send your PIN.