Reference

Legal details for your doyanqq account

doyanqq Legal sets out how we handle account access, personal data, cookies, wallet records and policy requests for Indonesia.

Account conditionsData and cookiesPolicy contact
doyanqq Legal details for your doyanqq account
POLICY CONTACT

Where to ask about Legal matters

A direct support route helps you resolve a policy question without guessing which team handles it.

Account access If phone verification or a login check blocks your account, use our account support channel and describe the exact screen or step that stopped you. We can check the account path without asking you to reveal a password, wallet PIN or one-time security code.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, send the transaction date and reference shown in your account. We use that detail to trace the status while keeping the request tied to your verified account.
Policy requests To ask about Legal wording, data use, cookies or a correction to your account record, label the request clearly and state the change you seek. We will explain whether identity confirmation is needed before the request can be processed.
DATA PRACTICE

How our Legal process handles records

Legal is also about what happens after your account is opened. We separate login details, verification records and wallet status checks so a support request can be reviewed against the right account…

Data handling

We use registration and verification details to administer your account, confirm requested changes and protect access. Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity are used for status checks and account reconciliation.

Cookie controls

Our cookies can support a signed-in session, remember selected preferences and help us understand whether a page loads correctly. You can manage browser cookie settings, but removing required cookies may interrupt login, phone verification or movement between account pages.

Account security

Keep your phone, password and verification messages private, and sign out on shared devices. We do not need your wallet PIN or one-time code in a support message. If you see an unfamiliar account step, stop there and contact support.

Record retention

Some account, security and payment records need to remain available for administration, dispute checks or legal duties. When a record may be removed or corrected, we assess the request against those needs and tell you the outcome through the account support path.

Change requests

You can ask us to correct an account detail, clarify data use or explain a cookie purpose. Include the phone number linked to the account and a precise description of the requested change. We may ask for verification before updating personal records.

Local eligibility

Account access depends on local law. We may restrict or pause access where local law permits, and we will use the account contact route to explain the next available step when a policy or eligibility check affects you.

Answers about doyanqq Legal

These Legal answers focus on the questions you may ask before opening an account or when you need a policy decision explained. We keep the process tied to your verified account, the records involved and the local access rule that applies to your location.

doyanqq Legal covers account conditions, phone verification, data handling, cookies, security, payment records, retention and requests to correct or clarify account details. It also explains that account eligibility depends on local law, so you should check the policy before opening or using an account.

Yes. Legal covers how we use payment references to check account ownership, match a status and respond to a support request. A request about DANA, OVO, GoPay or QRIS should include the account phone number, transaction date and visible reference, never a PIN.

Phone verification helps connect account activity and policy requests to the correct account before access is granted. It also gives us a safer route for account support. Keep verification messages private, and contact support if a code arrives when you did not request an account action.

You can request a correction through the policy support route. State which detail is wrong, provide the phone number linked to the account and explain the requested change. We may confirm your identity first, then tell you whether the record can be updated or must be retained.

Cookies may keep a mobile browser session active, remember preferences and help us identify loading problems between login and the lobby. You can change cookie settings in your browser. Removing required cookies may interrupt phone verification or account access until the setting is restored.

Yes. Account access depends on local law, and we may restrict or pause access where local law permits. If a policy or eligibility check affects your account, use the support route with your registered phone number so we can explain the applicable next step.

Use our account support channel and label the message as a Legal request. Describe the policy subject, account phone number and relevant date, but do not include a password, wallet PIN or one-time code. We can then explain verification, correction or retention steps.