Reference

den33 Privacy Policy for Your Account

den33 Privacy Policy explains what we collect when you create an account, enter the lobby, or check DANA and QRIS status.

Account detailsDevice signalsCookie choicesWallet references

Explore Our Lobby Read FAQ

How Wallet And Account Data Is Used

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

Our Privacy Policy gives you a practical view of data use from account creation through wallet checks. We collect the details needed to create and protect your account, such as contact details, verification records, login events and device information. When you use DANA, OVO, GoPay or

1
QRIS, we may receive a payment reference, status response and timing data rather than your wallet password. We use those records to match a cashier action, resolve a pending status and detect unusual account activity. Bank transfer and virtual account references may also be retained for
2
reconciliation. Service access depends on local law, and we only handle requests within the rights and limits that apply to your location.

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

PRIVACY HELP PATH

Where To Ask About Your Privacy Policy

A clear contact path matters when a data question affects your account or wallet status.

Privacy request Choose the privacy subject in the signed-in support area when you want to ask what account data we hold, why it is used, or which records relate to your den33 account. We may ask for an account identifier before releasing details so a request does not expose another person’s data.

Wallet record For a DANA, OVO, GoPay or QRIS question, provide the wallet name, transaction reference and approximate time shown in your account. Our support path uses those fields to compare the cashier event with the stored payment status while keeping your wallet credentials outside the request.

Device concern Tell us if a login alert, browser cookie or phone session does not look familiar. We can review the account event connected with that device path and explain the next account step. Do not send a password, one-time code or complete wallet login details in a support request.

DATA CONTROL

Inside den33 Privacy Handling

We keep the Privacy Policy tied to real account actions rather than broad statements. A login creates security records, a wallet action creates payment references, and a cookie choice affects how your…

Account records

During account creation, we store the contact and verification details needed to identify the account and protect the sign-in path. Login attempts, session changes and verification events can be checked when you report an unfamiliar sign-in. We do not need your wallet password to match a payment reference.

Cookie choices

Cookies help the browser remember a session setting and help us understand whether a page request completed. You can manage available cookie choices in your browser or the consent control presented on the site. Turning off some cookies can affect sign-in continuity, but it does not erase account records by itself.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use references and status responses to reconcile the account action. These records can show an amount status, reference code and time, while wallet credentials remain with the payment service you used.

Account security

We use verification steps before changing sensitive account details or answering a personal-data request. Keep your password and one-time code private, and sign out on a shared device. If a phone session looks unfamiliar, contact the support area with the account event and device context.

Retention timing

We retain each data group for the period needed for its stated purpose, account security, dispute handling or a legal requirement that applies to us. When a record no longer needs to be kept, we remove it or separate it from direct account identification according to our retention process.

Change requests

You can request a copy, correction or eligible deletion of personal data through the privacy contact path. State the account email or identifier, the requested action and the relevant date. We verify ownership first, then explain what we can change and any record we must retain under applicable law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions you are most likely to have before using den33 from Indonesia. They cover the data connected with sign-in, cookies, local wallets and privacy requests. For an account-specific answer, use the signed-in support path and include the relevant reference or device event. Access to any service depends on local law, so the applicable result can vary by location.

It covers account creation details, verification records, login and device events, cookie choices, support requests, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security controls and the process for requesting access, correction or eligible deletion.

Device and login signals help us keep your account session consistent and identify unusual sign-in activity. We may use browser type, device context, login time and session events when investigating a security alert. These signals support account protection and are handled under the Privacy Policy.

No. When you use DANA, OVO, GoPay or QRIS, our records are built around payment references, status responses and timing needed to reconcile the account action. Your wallet password and one-time code should remain with the payment service, and you should never place them in a support request.

Open the signed-in support area, choose the privacy or account-data subject, and state the account identifier plus the request you want handled. We verify that you control the account before responding. The Privacy Policy request may cover a copy, correction or eligible deletion, subject to applicable law.

Yes, send a correction request through the privacy contact path and identify the field that needs changing. Include the current account identifier and the accurate replacement detail. We may need an ownership check, and some verification or payment records may need to remain available for security or legal reasons.

We keep payment references for the time needed to reconcile wallet or bank events, investigate disputes, protect accounts and meet any legal duty that applies. The exact period can differ by record type and circumstance. We remove or de-identify records when the relevant purpose and required retention period end.

Yes. The policy applies when you use a phone, tablet or desktop to create an account, sign in, select cookies or check a wallet status. A phone browser may store session cookies and device signals, so sign out on shared hardware and use the privacy support path for questions.

den33 Privacy Policy for Your Account

Where To Ask About Your Privacy Policy

Inside den33 Privacy Handling

Account records

Cookie choices

Payment references

Account security

Retention timing

Change requests

Privacy Policy Answers For Indonesia

01 What does the den33 Privacy Policy cover?

02 Why does den33 collect device and login data?

03 Does den33 store my DANA or OVO password?

04 How can I request my personal data from den33?

05 Can I ask den33 to correct account information?

06 How long does den33 keep payment references?

07 Does the Privacy Policy apply on a phone in Indonesia?

Related Pages