Reference

rupiahbet Privacy Policy For Your Account

The rupiahbet Privacy Policy explains how we handle the details connected with your account, mobile browser, wallet references and support requests.

Account dataWallet referencesMobile browser useLocal-law access
rupiahbet rupiahbet Privacy Policy For Your Account
REQUEST ROUTES

Privacy Policy Help For Account Requests

A clear support route helps you ask about the Privacy Policy without sending sensitive wallet credentials.

Account access For a privacy question after phone verification, send your account contact and describe the sign-in issue through our support route. We may ask for safe account details to confirm that the request comes from you.
Wallet status If a DANA, OVO, GoPay or QRIS reference appears in a data request, share the receipt reference only. We can use it to locate the record without requesting your wallet password or full banking credentials.
Data changes To correct a phone number, account detail or contact record, state the old and new information clearly. We review the request against your account record before making a permitted change.
SIX DATA CONTROLS

Six Privacy Policy Controls We Apply

We apply the Privacy Policy at each practical account step, from the first mobile-browser visit through phone verification and a later support request.

Account details

When you open an account, we record the details needed to create your profile and confirm phone verification. We use them to connect your requests to the correct account rather than exposing data to another person.

Device signals

A mobile browser may send device type, browser version, network address and login time. We use these signals to spot unusual access and investigate why a session cannot reach the lobby.

Cookie choices

Cookies and similar browser storage can retain session state and basic preferences. Clearing them may sign you out or remove saved settings; your browser controls remain the first place to manage them.

Payment records

We retain transaction references, status results and reconciliation details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us check receipts without storing wallet passwords.

Security use

Login events, verification results and support history help us protect your account and resolve an access dispute. We limit internal use to the account, security or service purpose connected with the record.

Retention requests

We keep records for security, dispute handling and applicable legal duties, then assess deletion or correction requests where permitted. Send the request with your account contact so we can identify the relevant record.

Privacy Policy Questions About Your Data

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet receipt is checked. If your situation is different, use the support route with a limited description and no wallet password. We will assess the request under applicable rules and local access conditions.

It covers account details, phone verification, device and browser signals, cookies, login records, payment references and support messages created while you use rupiahbet. Processing depends on local law.

We collect the account details needed for setup and the phone verification result used for account access. A mobile browser can also provide device type, browser version, network address and session time.

No wallet password is needed to match DANA, OVO, GoPay or QRIS activity. We use payment references, status results and receipts for reconciliation, and you should never send a wallet password.

Use our support route and include your account contact, the field that needs correction and the replacement detail. We verify the request against your account before changing data where local law permits.

You can send a removal request through support. We identify the relevant records and assess what can be removed, subject to security needs, dispute handling, legal duties and local law.

We retain payment references and related status records for the period needed for account security, receipt checks, disputes and applicable legal duties. After that, records are removed or handled as required.

Stop using that session, clear the browser session if needed and contact support with your account contact and device details. Do not send wallet credentials; account ownership checks come first.