Reference

demen303 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you create an account, complete phone verification, use the mobile browser, or connect DANA, OVO, GoPay and QRIS.

Account detailsWallet activityDevice choicesPolicy requests
demen303 demen303 Privacy Policy for Your Account
HELP WHEN NEEDED

Get Privacy Policy Help Near Your Account

A clear contact path matters when your account or wallet record looks unfamiliar. We route privacy questions through the account support area, so you can identify the relevant login, receipt or verification event without sending the same details across unrelated channels. If you are in Bandung or elsewhere in Indonesia, use the contact path shown inside your account and describe the request in plain English.

Team online

Account privacy request

Ask us to explain the account details connected with your phone verification or login record. Include the account identifier shown to you, but never send a password or wallet PIN.

Wallet record check

For a DANA, OVO, GoPay or QRIS record, send the visible reference and date through account support. We compare the receipt status with the account event before replying.

Access and correction

Use the same support route to request a copy, correction or deletion review. We may ask for a phone verification step so the response reaches the correct account holder.

HANDLING YOUR RECORDS

Privacy Controls From Login To Lobby

We keep this policy practical: you should know why a record exists, where to ask about it and what account step may be needed before we change it.

Account security

We use phone verification before account access and inspect login events for unusual patterns. Keep your password private, sign out on shared devices and contact us if an account event does not match your activity.

Cookie choices

Cookies can remember a session and help us understand whether a page loads correctly. You can manage browser cookie settings, although removing them may require you to sign in again before reaching your account.

Payment references

We retain the reference and status needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. We do not need your wallet PIN to investigate a receipt.

Device information

Our records may include browser type, device class, connection details and access time. This helps us compare a new mobile browser with prior login events without reading unrelated files on your device.

Retention choices

We keep records only for the operational, security or legal period that applies to the request. When a retention period ends, the record is removed or separated from direct account details.

Request changes

To ask for access, correction, restriction or deletion review, contact account support with the relevant event and your preferred reply route. We verify identity first and explain any limit under local law.

Privacy Policy Answers For demen303

These Privacy Policy answers focus on the records you are most likely to ask about before opening an account. We explain the account step, payment reference, device path and contact process in direct terms. If your question is not listed, send it through account support and include only the minimum detail needed to locate the relevant event.

It covers account details, phone verification, login events, device and browser data, cookies, wallet references, support messages and retention. It applies to our handling of your information where local law permits.

Phone verification helps us connect a login request with the correct account and reduce mistaken access. It also lets us confirm a privacy request before changing account details or sharing a record.

Yes. We may keep the reference, amount status and timing needed to reconcile a DANA or QRIS request. The same approach applies to OVO, GoPay, bank transfer and virtual account records.

We may record your browser type, device class, connection details and login time. We use these signals for session operation and account security, not to inspect unrelated files, photos or messages.

Contact us through the account support route and describe the record you want copied or corrected. Include the relevant receipt date or login event, then complete any identity check we request.

You can submit a deletion review through account support. We assess the request against operational and legal retention needs, explain any records we must keep and remove eligible details when permitted.

Access and eligibility depend on local law. A local requirement may change the timing, identity check or scope of a request, and we will explain the applicable route instead of promising an outcome.