Reference

Legal clarity before you open an account

durian66 Legal explains how we handle account access, wallet records, site cookies and requests about your personal data.

Account termsData requestsLocal-law accessWallet records
durian66 Legal clarity before you open an account
CONTACT POLICY DESK

Get a clear route for Legal questions

A direct support route helps when a Legal question affects your account, data request or wallet record. Sign in first where possible, describe the issue in plain English, and include the relevant account step without sending a password or full payment credentials. We can then identify whether the matter concerns access, cookies, retention, phone verification or a DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference. If access is restricted, we will explain the available account path where local law permits.

Team online

Account access

Use the support path after login when a Legal question concerns phone verification, account access or a restriction. Tell us which screen stopped you, and we can check the account step without asking you to disclose your password.

Wallet status

For a DANA, OVO, GoPay or QRIS record, send the transaction reference shown in your account rather than private wallet credentials. We use that reference to separate a payment-status question from a wider Legal request.

Data request

Ask through account support when you want to request access, correction or removal of personal details. We may need to confirm your account identity before discussing records, so the request reaches the correct account holder.

DATA CONTROL

How durian66 handles policy duties

We treat Legal work as an operating process rather than a footer link. Account access starts with a clear phone-verification step, payment checks use transaction references, and security questions stay within the…

Account security

Phone verification is part of the access check before you enter the account. Keep your login details private and contact us through the account route if you see an access issue, rather than sharing credentials in a message.

Personal data

You can ask what personal details are connected with your account and request a correction when something is inaccurate. We may verify your identity first, then direct the request to the team handling account records.

Cookies

Cookies can preserve sign-in status, language choices and basic site settings during your visit. If you ask about a cookie, tell us the device path you used, such as mobile browser or desktop browser, so we can respond precisely.

Record retention

We retain account and payment references only as needed for account operations, security checks, dispute handling and applicable legal duties. A request about retention should identify the record type, such as QRIS receipt or phone-verification history.

Policy changes

When a Legal term changes, the current wording is the version you should read before using the account. We encourage you to check the policy page after a material account or payment-process change affecting DANA, OVO, GoPay or QRIS.

Request ownership

Start with account support and state whether you need access, correction, deletion, clarification or a restriction check. We will explain the next account step, any identity check and whether the request depends on local law.

Questions about durian66 Legal

These Legal answers cover the questions we expect before an account is opened or a policy request is sent. They explain how access, data, cookies and payment references connect to the account path without replacing the current terms. If your circumstances are specific, contact us after signing in and include the relevant step. We will keep the response focused on your account and the rules that apply to your region.

durian66 Legal covers account access, phone verification, personal data, cookies, retention, payment references and requests to change account records. It also explains regional access wording. Before opening an account, read the current terms and confirm that access is permitted where you are.

Access depends on local law. If local rules permit use, follow the account path, complete phone verification and review the applicable terms before entering the lobby. We cannot tell you that access is permitted in every location, so you remain responsible for checking your position.

We use the transaction reference connected with your account to investigate a DANA or QRIS status question. Do not send a password, wallet PIN or full private credentials. Contact account support with the reference and the payment step shown on your screen.

Yes, you can ask for access to personal details connected with your account or request a correction. Start through account support, describe the record, and complete any identity check we require. We will explain the next step and any local-law condition.

Cookies may keep your sign-in state, language choice and basic site settings while you move through the Legal page and account path. If you want a cookie question checked, tell us whether you used a mobile browser or desktop browser.

Retention depends on the purpose of the record, account security needs, dispute handling and applicable legal duties. Ask us about a specific item, such as a virtual account reference, bank transfer record or phone-verification event, and we will explain the request path.

Use the support path inside your account where possible and state the request type: access, correction, deletion, cookie query or policy clarification. Include only the details needed to locate the issue. We may verify account ownership before discussing personal records.