Reference

berlianjitu Privacy Policy For Your Account

berlianjitu Privacy Policy shows how we handle your account details, phone verification, device signals and wallet references before you open the lobby.

Account dataWallet referencesMobile access
berlianjitu berlianjitu Privacy Policy For Your Account
ACCOUNT HELP

Privacy Help For Wallet Status

A clear contact path matters when you want to ask about personal data or a wallet reference. Start from the support channel shown inside your account and include the phone number used for verification, the relevant date and the payment rail involved. We use those details to locate the right record without asking you to send a wallet password.

Team online

Data request

Ask our account support channel what personal details are held for your profile, including phone verification records and device events connected with your berlianjitu login.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, share the transaction reference and date through the cashier support route so we can check the matching account record.

Policy change

To request a correction or raise a privacy concern, use the privacy contact route shown on the account page and describe the exact field or policy point involved.

CONTROL LAYER

Phone Verification And Data Controls

We keep this Privacy Policy practical by connecting each explanation to an account step you can recognise.

Collected details

We may hold your name or account identifier, verified phone number, login timestamps, device information and wallet references created when you use DANA, OVO, GoPay or QRIS.

Cookie choices

Cookies can keep your mobile browser session active and remember basic settings. You can clear them through your browser controls, although a new login may then be required.

Account security

Phone verification and unusual-login checks help protect account records. Never send a wallet password through support; our Privacy Policy does not ask you to disclose one.

Retention period

We keep account and payment-reference records for the period needed for security checks, support history and legal duties, then remove or limit them when those purposes end.

Correction request

If your phone number, account detail or contact record is wrong, tell us through the account privacy route. We may ask for verification before changing protected information.

Policy contact

Questions about this Privacy Policy belong with our support channel shown after account access. Include your account identifier and a precise request so we can respond to the right record.

Privacy Policy Questions For berlianjitu

These answers address the account and wallet questions we expect you to ask before opening access. Each response follows our Privacy Policy and points you toward a practical step, from checking cookies on your phone to requesting a correction through the account contact route.

It covers account details, phone verification, login and device records, cookies, wallet references, support requests, retention and the way we handle requests to inspect or correct your data.

We use your phone number for the account verification step and to help identify your profile during security or support checks. We do not ask for your DANA, OVO or GoPay password.

The policy allows us to retain a QRIS reference, date and status when needed to match a cashier event with your account. The reference helps us investigate status questions without wallet credentials.

Yes. Use the privacy contact route shown inside your account, identify the phone number used for verification and ask which personal records you want us to provide.

Send a correction request through the account support channel with the affected field and your account identifier. We may complete a phone verification check before changing protected details.

Open your mobile browser settings, find site data or cookies, and remove the relevant entry. Clearing them can end your session, so you may need to sign in again.

Yes. Certain access, data handling and retention duties depend on local law. If a regional rule applies to your account, we will follow the requirement relevant to that account path.