Reference

Privacy Policy For Your rubi8000 Account

Our Privacy Policy explains what rubi8000 collects when you create an account, sign in, use a mobile device or check wallet status through DANA, OVO, GoPay and QRIS.

Account clarityWallet data contextPolicy access
rubi8000 Privacy Policy For Your rubi8000 Account
HELP WITH YOUR DATA

Three Ways To Ask About Privacy

A clear contact path matters when a phone verification record, wallet reference or login event needs checking. Use the support route shown beside the account and cashier areas to ask about this Privacy Policy, request a correction or clarify how a particular record was used. Tell us the account email or phone number connected with your request, and we will use it to locate the right record.

Team online

Policy questions

Ask us which account details, device signals or payment references are covered by the Privacy Policy. Include the subject of your question and the account contact used during phone verification so we can direct the request correctly.

Correction requests

If your account name, phone detail or wallet reference appears inaccurate, send the relevant record through the support path beside the cashier area. We may ask for account verification before changing personal data.

Access concerns

When a login event or account record needs investigation, contact support with the device path you used, such as mobile browser or desktop browser. We use those details to distinguish your request from another account.

SIX DATA PROMISES

What We Do With Your Personal Data

We keep the Privacy Policy practical by linking each data use to an account action you recognise.

Account records

We use account details to create and maintain your sign-in record, connect your phone verification step and respond to a Privacy Policy request. The account contact you provide helps us confirm that a request belongs to you.

Device signals

When you move from a mobile browser to a desktop browser, we may record technical login signals such as device type, session time and browser context. These details help us identify unusual access without describing your device as a person.

Cookies

Cookies can keep a session connected to the right account and remember necessary access settings. Our Privacy Policy treats these files as operational data, and your browser controls can be used to inspect or restrict them.

Payment references

DANA, OVO, GoPay and QRIS may appear as payment references linked to account activity. We use the reference, amount status and transaction time to trace a record, while the payment provider remains responsible for its own data handling.

Account security

Phone verification, session checks and account contact confirmation help us protect personal data from an unrelated request. We may ask you to confirm account details before discussing a login event or changing stored information.

Retention and changes

We retain records for the period needed for account operations, security checks, payment reconciliation and requests connected with this Privacy Policy. You can ask what remains on file, why it is retained and whether a correction is available.

Privacy Policy Answers For Indonesia

These questions cover the points you are most likely to check before opening a rubi8000 account. Each answer stays focused on personal data, access records, cookies, payment references and the steps available when you want clarification. Where access or eligibility is discussed, it depends on local law.

It covers data connected with your account, phone verification, login sessions, device signals, cookies and payment references. This includes records associated with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity when those records are linked to your account.

Phone verification helps us connect an account request to the correct contact detail and protect account access. We may use the verification result when you sign in, ask about a record or request a change under the Privacy Policy.

Yes. The policy explains how we handle DANA and QRIS references shown in account-linked payment records. These references can help us trace a status or transaction time, while DANA, QRIS and other providers apply their own privacy rules.

We may record technical details such as browser type, device category, session time and login context when you use a mobile or desktop browser. The purpose is to support account security, session continuity and investigation of unusual access.

Retention depends on the record and the reason it was created. Account, security and payment references may remain while needed for account operations, reconciliation or a privacy request. You can contact us to ask what remains and why.

Use the support route beside the account or cashier area and identify the data you believe is incorrect, such as a phone detail or wallet reference. We may request account verification before making a change to protect your records.

Yes. Send a privacy question through the support path and mention whether the record concerns a mobile browser, desktop browser or cookie setting. We will use your account contact to locate the request and explain the relevant policy treatment.