Reference

indo6d Privacy Policy For Your Account

Clear handling for your account, wallet records and device visits is what this indo6d Privacy Policy sets out.

Account clarityWallet recordsCookie choicesRequest access
indo6d indo6d Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help For Wallet And Login

A privacy question should not get lost beside a wallet issue, so we keep a direct route from your account support area to our team. Tell us whether your request concerns a phone verification, a DANA receipt, a QRIS status, a cookie choice or a record linked to a game such as Lightning Roulette. Include the email or phone attached to your account, but never send a password or wallet PIN.

Team online

Account support route

Use the support path shown after account login for a Privacy Policy question. We can match your request to the verified phone step and ask for only the details needed to locate your record.

Wallet record check

For DANA, OVO, GoPay, QRIS or bank transfer questions, send the transaction reference and visible status. We use those fields to separate a payment record from unrelated account activity.

Privacy request

Ask us to access, correct or remove eligible personal data through the same support route. We may verify account ownership before changing a phone, email, device record or saved preference.

CONTROL AND RETENTION

What Our Privacy Process Keeps Clear

We handle this policy area through practical account controls rather than vague promises. Phone verification helps us connect a request to the right account, while device and session records help protect access…

Account data

We may hold your phone number, email, verification result, sign-in history and preferences so we can identify your account and respond to a Privacy Policy request about it.

Payment references

A DANA, OVO, GoPay or QRIS record can include a reference, status and time. These details help reconcile activity without asking us to store your wallet password or PIN.

Device signals

Browser type, device changes and failed sign-ins can be logged for account protection. We use these signals to investigate access concerns, not to read private files on your device.

Cookie settings

Session cookies help keep you signed in during a visit, while measurement cookies help us understand page use. Your browser controls can limit cookies, although some account steps may then stop working.

Retention steps

We retain records for account operation, payment reconciliation, dispute handling, security checks or legal needs. When a record is no longer needed, our process removes it or makes it non-identifying.

Change requests

You can ask about a copy, correction or eligible removal through support. We verify the account first, explain any legal reason for keeping a record, and confirm the action taken.

Privacy Policy Answers For indo6d

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. We keep the wording practical: what is recorded, how identity is checked, which payment references appear, and where to send a request. If your situation is different, use the account support route and describe the exact record or access step you want us to inspect.

It covers account details, phone verification, sign-in and device records, cookies, support messages, payment references and retention. It also explains your route to ask for access, correction or eligible removal.

No. Our payment record can show a reference, amount, status and time for DANA or QRIS reconciliation, but your wallet PIN and password should remain with the wallet provider.

Phone verification helps us connect account requests to the correct person and reduce mistaken changes. We may use the result when you ask about login history, wallet records or a saved contact detail.

Use the support path inside your account and state that you are making a Privacy Policy data request. Include your account phone or email, then complete any ownership check we send.

Yes, you can request a correction for an eligible phone, email or account detail through support. We compare the request with your verified account before changing the stored record.

We keep payment references only as long as needed for account operation, reconciliation, disputes, security or legal needs. After that period, records are removed or changed so they no longer identify you.

Send the question through your account support route and mention cookies, browser data or a device record. We can explain the relevant purpose and the available browser or account control.