Reference

Privacy Policy for Your dojo77 Account

Our Privacy Policy explains how we handle the details connected with your dojo77 account, including phone verification, device access and wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
dojo77 Privacy Policy for Your dojo77 Account
ACCOUNT HELP ROUTE

Contact Us About Privacy Policy

A clear support path helps you ask what we hold, why we use it or how an account record was created. Start from the account help area while signed in so we can connect your request with the correct dojo77 profile. Include the phone number linked to the account, the subject of your request and any relevant payment reference, while leaving out passwords, wallet PINs and full banking credentials. We can then check the request against the account and payment records available to us.

Team online

Data access request

Ask us to identify the personal data connected with your account, such as your phone verification status, login records, device signals and payment references. We may need an account step to confirm that the request comes from you before sharing or changing any record.

Wallet record question

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the date, amount reference and wallet name through account help. We use those details to locate the relevant status record without asking you to disclose a wallet password or banking PIN.

Policy clarification

For a question about cookies, retention, account security or access where local law permits, contact us through the signed-in support path. Keeping the request inside your account helps us reduce mistaken changes and provide a response tied to the right profile.

SIX DATA CONTROLS

What Our Privacy Policy Covers

We keep the Privacy Policy practical by connecting each data use with an account action you can recognise.

Data handling

We handle contact, verification, login and transaction details for account operation, security checks, support responses and payment reconciliation. For example, a QRIS reference can help us match a status question to the correct account without treating your QRIS access code as information we need to collect.

Cookie controls

Cookies and browser storage can keep you signed in, remember a selected setting and help us recognise a session on mobile or desktop. You can manage browser cookie settings on your device, although limiting required storage may affect login or the path from account access to the lobby.

Account security

We use phone verification and account checks to reduce mistaken access. Keep your login details private, sign out on a shared device and contact account help if a device you do not recognise appears in your access history. Never send us your wallet PIN or banking password.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear as payment context in a transaction record. We use the reference, status and timing needed to investigate an account question, while the payment provider remains responsible for credentials held inside its own service.

Retention choices

We retain account and support records only for the period needed for the purpose described in this policy, account protection and applicable legal duties. If you ask about deletion or correction, we first check whether a record must remain available for a payment, security or legal reason.

Change requests

You can ask us to correct inaccurate account details, explain a processing purpose or consider a deletion request through the signed-in support route. Tell us which field or record concerns you, and complete any identity check we reasonably need before making a change.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions we hear most often from people preparing to use dojo77 in Indonesia. They cover what we collect, how access works, what appears in wallet records and how to ask for a change. If your situation involves a local restriction, access depends on local law, so contact us through account help with the details we need to check your request.

It covers personal data connected with your account, including phone verification, login activity, device signals, cookies, support records and payment references. It also explains how we use, retain, protect and respond to requests about that data where local law permits.

Phone verification helps us connect an account request with the correct person and reduce mistaken access. It can support login checks, security questions and account changes. We use the verification status for those purposes and do not need your wallet PIN or banking password.

Yes. When you use DANA, OVO, GoPay or QRIS, we may retain the payment reference, status and timing needed to match a wallet question with your account. The payment provider handles credentials inside its own service, so do not send those credentials to us.

Open the account help path while signed in and ask for the data connected with your profile. Include the phone number linked to the account and describe the records you want us to locate. We may complete an identity check before responding where local law permits.

You can ask us to correct an inaccurate field or consider deletion through account help. We assess the request against payment reconciliation, security and legal retention needs. Some records may need to remain available for a defined period, depending on the purpose and local law.

Cookies and browser storage help maintain your session, remember settings and support security checks on mobile and desktop. You can adjust cookie controls in your browser. Blocking required storage may prevent normal account access, so check the browser path before assuming a login problem is a data issue.

Use the signed-in account help route and label the request as a Privacy Policy concern. Explain whether it involves data access, a wallet reference, cookies, security or a correction. Do not include passwords, wallet PINs or full banking credentials in your message.