Reference

Privacy Policy For Your dima99 Account

DANA, OVO, GoPay and QRIS account steps are covered by the dima99 Privacy Policy, so you can see what we collect before opening access to the lobby.

Account clarityWallet contextDevice awarenessContact path

Explore The Lobby Read FAQ

What Our Privacy Policy Covers

dima99 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy sets out how we handle details connected with your dima99 account, including your phone verification step, login records, device signals and requests involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account status. We use these details to connect the right account with

1
the right wallet record, investigate an unclear payment receipt and protect access when a sign-in pattern changes. The policy also explains cookies used by the mobile browser and how long records may remain available for account, payment or legal reasons. Access and eligibility depends on local
2
law; where local law permits, you can open the policy before completing your account path.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear support route helps when you want to understand a Privacy Policy clause or ask about data connected with your dima99 account.

DATA HANDLING

How dima99 Applies This Policy

We apply the Privacy Policy to practical account events rather than treating every visit the same way.

Account records

We may connect your phone verification result, login event and account settings so the correct person reaches the correct dima99 account. These records help us identify an access request without requiring you to repeat private details in every support message.

Wallet references

When you use DANA, OVO, GoPay or QRIS, we handle the account-linked payment reference needed to check status and match a receipt. The Privacy Policy explains this purpose so you can distinguish wallet metadata from the contents of your personal device.

Browser cookies

Cookies can keep a mobile browser session connected to the page you requested and help us remember relevant account state. You can manage browser cookie settings on your device, although changing them may affect the path from login to policy or cashier pages.

Security checks

Device signals and login records may be checked when an account request looks different from the recent session. This can include a new mobile browser or an unusual verification step. We use that context to protect account access, not to create a separate public profile.

Retention timing

We retain account, payment and support records only for the period needed for the purpose described in the Privacy Policy, account administration or applicable legal duties. A retention request can be assessed against the record type and any continuing reason to keep it.

Change requests

To ask for correction, access or deletion of eligible personal details, contact us through the privacy route and identify the account step involved. We may ask for a matching verification detail before changing records, so another person cannot alter your account data.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the account and wallet questions we expect from people checking dima99 before opening access. They cover what is collected, why device and payment references matter, how to request a change and what local access wording means. If your case is specific, use the privacy support route with the smallest useful set of account details.

The dima99 Privacy Policy explains how we collect, use, protect and retain account, device, cookie, support and wallet-reference data. It also describes your available requests, our verification steps and how access or eligibility depends on local law.

Phone verification links an account request to the contact detail you provide and helps us respond to access concerns. We may use the verification result with login context to protect your account, as described in the Privacy Policy, where local law permits.

Yes. The Privacy Policy covers account-linked references from DANA, OVO, GoPay and QRIS, including details needed to check a receipt or payment status. It does not mean we receive the private contents of your wallet or device.

We may handle limited device and mobile browser signals connected with login, cookies, phone verification or account protection. The Privacy Policy explains the purpose for each category. You can also manage cookies through your browser settings, subject to page behaviour.

Send a request through the privacy contact route and state whether you need access, correction or deletion of eligible details. Include the relevant account step, such as phone verification or a QRIS receipt, and we may verify ownership first.

Retention depends on the type of record and the reason it was collected. We may keep account, payment or support details for account administration, security checks or legal duties. The Privacy Policy explains how to ask about a particular record.

Yes. You can read the Privacy Policy before completing phone verification or using the wallet path. This lets you understand account and device handling in advance. Access and eligibility depends on local law, including for Indonesian locations.

Privacy Policy For Your dima99 Account

Three Ways To Ask About Your Data

How dima99 Applies This Policy

Account records

Wallet references

Browser cookies

Security checks

Retention timing

Change requests

Privacy Policy Questions About Your Account

01 What does the dima99 Privacy Policy explain?

02 Why does dima99 need phone verification data?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device data can dima99 handle?

05 How do I request a change to my personal data?

06 How long does dima99 keep account information?

07 Can I read the Privacy Policy before opening an account?

Related Pages