Reference

dinasti33 Privacy Policy In Plain Terms

dinasti33 Privacy Policy explains what we collect when you open an account, use the mobile lobby and connect DANA, OVO, GoPay or QRIS.

Account recordsWallet activityDevice controlsContact choices
dinasti33 dinasti33 Privacy Policy In Plain Terms
HELP WITH RECORDS

Three Ways To Ask About Privacy

A clear support route helps when your account record, wallet reference or device session needs checking. We ask you to use the support path connected to your account rather than sending private details through an unrelated channel. Include your registered phone number, the affected date and a short description; never include a wallet password or one-time code. We will use the request to locate the relevant Privacy Policy process.

Team online

Account access

If your phone verification or login record looks wrong, contact support from the account path and describe the device used. We can check the session without asking for your wallet password.

Wallet status

For DANA, OVO, GoPay or QRIS questions, share the payment reference and timestamp from your receipt. We use those details to locate a status record while limiting unrelated account data.

Privacy request

Ask us to correct, access or delete an eligible record through the support route. State the request clearly so our team can confirm identity and apply any local-law conditions.

DATA CONTROL

How We Handle Your Account Data

We keep our handling steps tied to practical account needs: confirming who is signing in, matching a wallet reference and investigating a security event.

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification before account access. We use those fields to connect later privacy requests to you.

Device signals

Your browser and device may generate session, language and security signals. On mobile, these help us spot an unfamiliar login and separate a fresh session from a returning one.

Cookie controls

Cookies can keep the lobby session available and remember selected settings. You can manage browser storage through your device or browser controls, though some account steps may then need repeating.

Wallet matching

DANA, OVO, GoPay and QRIS references, along with bank transfer or virtual account details, help us reconcile a receipt. We do not ask you to disclose a wallet password.

Account protection

We use phone verification, session checks and sign-out controls to reduce unauthorised account use. If a login looks unusual, support may ask for identity details before discussing records.

Retention requests

You can ask what eligible records we hold, request a correction or ask for removal. We explain any record we must retain for a dispute, security matter or local-law requirement.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions we expect before you open access from Indonesia. They cover the details most often needed for a phone-verified account, a mobile session or a wallet receipt. If your situation is not listed, send a focused request through the support path with your registered phone number and relevant reference, while keeping passwords and one-time codes private.

The Privacy Policy covers account details, phone verification status, device and browser signals, session events, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

Device and browser signals help us recognise an unusual login, connect a mobile session to your account and investigate access problems. They do not replace the phone verification step required for account access.

No. We may retain a DANA, OVO, GoPay or QRIS reference, receipt time and status needed for account matching, but you should never send us a wallet password or one-time code.

Use the account support path, identify the registered phone number and describe the incorrect record. We may confirm your identity first, then explain the correction route and any conditions that depend on local law.

You can request removal of eligible records through support. Some details may remain for a payment dispute, security investigation or legal duty, and we will explain the reason when that applies.

Retention depends on the record type and its purpose. Account, wallet and security entries may be kept while needed for access, reconciliation, dispute handling or a local-law requirement.

Start through the support route linked to your account and include a concise request, registered phone number and relevant receipt or session date. We will direct the request to the privacy handling process.