Reference

Open dooo0t Privacy Policy Clearly

Our Privacy Policy explains what we collect when you open a dooo0t account, sign in on mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataPayment statusDevice accessPolicy requests
Explore Our Lobby Read FAQ
dooo0t Open dooo0t Privacy Policy Clearly
CONTACT YOUR WAY

Find Policy Help From Your Account

A clear contact path matters when you need a copy of your data or want to question a payment record.

Account privacy request Use the support route after signing in to ask about stored account details, phone…
Payment record question If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, open the cashier status…
Access concern For a sign-in or device concern, tell us which device path you used and…
DATA HANDLING

Explore Our Account Data Practices

The Privacy Policy is practical: it connects account activity with the steps needed to provide access and resolve payment status questions.

Account records

We may hold your registration details, verified phone number, sign-in history and selected account settings so we can provide access and respond when a login step stalls. We use only the details needed for that operational purpose.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event with your account. We do not ask you to place a wallet PIN or banking password in a support request.

Cookies and devices

Cookies and device signals can preserve a session and help identify unusual sign-in behaviour. You can manage browser permissions, although changing them may affect account access or require another phone verification step.

Security checks

We use account-security controls around sign-in, phone verification and payment status. If a device path looks unusual, we may ask for an account check before discussing records or changing access details.

Retention choices

We retain records for the period needed to operate the account, resolve payment questions, meet applicable requirements and handle disputes. When a record is no longer needed for those purposes, our process addresses its removal or restriction.

Policy changes

When this Privacy Policy changes, we update the policy page and identify the revised subject in clear language. Check the page before using a new device or payment rail, especially where local law affects access.

Ask About dooo0t Privacy Policy

These Privacy Policy answers cover the searches that usually arise before account access: what data we use, how payment references are handled, how to request a change, and what happens when you switch devices. The account support route is the starting point for a personal request. We may need to verify ownership before sharing private records, and any eligibility question depends on local law.

It covers data connected with account creation, phone verification, sign-in, device sessions, lobby activity, support requests and payment references. That can include DANA, OVO, GoPay, QRIS, bank transfer and virtual account records used to match a cashier event with your account.

We use the phone number supplied during registration to complete the account access step, support sign-in checks and connect a request with the correct account. Keep one-time codes private. We will not ask you to place a verification code in a support message.

The Privacy Policy treats DANA and QRIS references as payment context used to check status, reconcile an account event and answer a receipt question. Your wallet provider or bank keeps its own records, so its privacy terms also apply to the transaction.

Yes. Sign in and use the account support route, stating whether you want access to a record or a correction. Add your registered phone number and a useful date, but omit passwords, wallet PINs and one-time codes. We may verify account ownership first.

Send a deletion request through the account support path and identify the account concerned. We assess which records can be removed or restricted while considering payment reconciliation, disputes and applicable requirements. Where local law permits, we will explain the result and any remaining record.

Cookies and device signals are tied to browser sessions rather than a permanent promise of access on every device. A new phone, cleared browser or changed permission may require another sign-in or phone verification. You can manage browser settings, subject to their effect on account access.

Use the signed-in account support route for a personal data request, or the cashier status path for a payment-reference question. Include the relevant date and reference where available. Do not send a password or wallet PIN, and remember that access depends on local law.

Related Pages

dooo0t Indonesia FAQ Access guide Account information About Us