Reference

rans jitu Privacy Policy and Your Account

Our rans jitu Privacy Policy explains what we collect when you create an account, verify your phone, browse Live Blackjack Diamond or use DANA and QRIS.

Clear data purposesWallet record detailsRequest access or changesMobile privacy path
rans jitu rans jitu Privacy Policy and Your Account
PRIVACY CONTACT

Where to Ask About Your Data

A direct support route helps when a privacy request is mixed with an account or wallet issue. Start from your signed-in account support area, describe the request clearly and include the phone number or transaction reference connected to it. If you cannot sign in, use the support chat entry shown on the access page and avoid sending a password, wallet PIN or full payment credentials. We use the details you provide only to identify the request and respond through the available channel.

Team online

Account access

If phone verification blocks your request, tell us the account step that stopped and the device type you used. We may ask for limited identity details before discussing account data, so another person cannot obtain your records through a simple chat message.

Wallet records

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and status shown in your account rather than a wallet PIN. Our support team can match the record, explain what we retain and direct you to the relevant privacy request path.

Policy requests

To request access, correction or deletion where available, write that the message concerns the Privacy Policy and state the exact record involved. We will confirm the request, check account ownership and explain any legal or security reason a record must remain.

DATA PRACTICES

What We Protect Across Your Account

Privacy is handled through practical account controls rather than a promise that removes every risk. We limit internal access to records needed for account support, payment matching, security checks or legal duties.

Collected account data

During account creation, we may receive your phone number, account details, verification outcome and basic access records. If you use Live Blackjack Diamond or another lobby title, activity may be linked to your account session so we can maintain security and answer a data request.

Cookies and sessions

Cookies can keep a browser session active, remember selected settings and help us detect repeated sign-in failures. On a mobile browser, clearing cookies may remove saved session details and require phone verification again; this behaviour is part of the access record we explain.

Security checks

We review sign-in timing, browser details, device signals and verification events when account access looks unusual. These checks are intended to protect your records and wallet references. Never share your password, one-time code or wallet PIN with support or another account.

Retention approach

We keep account, support and payment references only as long as needed for account operation, reconciliation, security investigation, dispute handling or legal duties. A deletion request may not remove records that must remain for these purposes, and we will explain the reason where required.

Requesting corrections

If your phone number, account detail or stored contact record is wrong, contact us through the support route and name the field to change. We may verify ownership before editing it, because changing identity details without a check could expose another person’s account.

Policy changes

When this Privacy Policy changes, we will publish the updated wording at /privacy-policy/ and show the revised date or notice where applicable. Read the page again before using the account, especially if the change concerns cookies, retention, wallet records or your request rights.

Privacy Policy Answers for Indonesian Accounts

These answers focus on the searches you may make before opening an account or sending a privacy request. We keep the examples tied to the actual account path, including phone verification, mobile browser sessions and local wallet references. If your question is not covered, use the support route and identify the relevant record without sending secret credentials.

The rans jitu Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, wallet references and retention. It also explains how to request access, correction or deletion where available, with eligibility and access depending on local law.

We keep the transaction reference, status and related account details needed to match a DANA or QRIS request, resolve a payment query and handle disputes. We do not need your wallet PIN for this process, so never include it in a support message.

Yes, you can ask for access to account data through the support path. State the phone number or account detail connected to the request, and we may verify ownership before responding. The result can exclude records restricted by security, legal or third-party obligations.

Cookies can retain a mobile browser session and selected settings. Clearing them may sign you out and trigger phone verification when you return. You can still open /privacy-policy/ in the browser to read the current wording before deciding whether to continue.

Use the account support route and name the specific detail that is inaccurate, such as a phone number or contact record. We check account ownership before making a change, then explain whether the correction is complete or requires an additional verification step.

Retention varies by record type and need. Account, security, support and wallet references may remain for operation, reconciliation, dispute handling or legal duties. If you request deletion, we explain which records can be removed and which must remain for a stated reason.

Open the signed-in support area, or use the support chat entry on the access page if you cannot sign in. Mark the message as a Privacy Policy concern, describe the record involved and omit passwords, one-time codes, wallet PINs and full payment credentials.