Reference

Privacy Policy For Your moto66 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your moto66 account, including phone verification, device access and payment records.

Clear data purposesWallet record controlsIndonesia access wordingPhone verification context
moto66 Privacy Policy For Your moto66 Account
CONTACT PATHS

Where To Ask About Privacy Policy

A direct account route helps you raise a privacy question without explaining your entire history again. From the signed-in account area, send a request about a data copy, correction, deletion review or wallet record. We may ask for the phone number linked to your account so we can separate your request from another account. If a receipt or sign-in issue is part of the question, include the relevant DANA, OVO, GoPay, QRIS or bank transfer reference.

Team online

Account privacy request

Open the support path from your signed-in account and state whether you want access, correction or deletion review. We use the account phone verification step to confirm that the request concerns your records before discussing details.

Wallet record query

For a payment-related privacy question, include the payment rail and reference visible in your account. DANA, OVO, GoPay and QRIS records may need separate matching before we can explain what was stored or correct an entry.

Device access concern

Tell us if your phone, tablet or desktop browser shows an unfamiliar sign-in or cookie behaviour. We can use the account access details you provide to investigate the event and explain the next account-security step.

DATA HANDLING

Privacy Policy And Your Blackjack Account

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We use the details you submit during account opening and phone verification to create access, respond to account requests and connect activity with the correct account. We do not need a second account profile to handle a normal Privacy Policy request.

Cookies and browsers

Cookies can remember a session choice, help the mobile lobby load correctly and support basic security checks. You can review browser cookie controls on your device, although changing them may affect sign-in continuity or require another account verification step.

Payment references

A DANA, OVO, GoPay or QRIS reference is used to match a payment event with your account and resolve a status question. Bank transfer and virtual account records may be retained for reconciliation, disputes or a legal requirement.

Account security

We examine sign-in details such as device and session signals when needed to protect your account. If access looks unusual, we may pause a request and ask for the phone verification step before discussing personal records.

Retention period

We keep personal data for the period needed for the purpose stated in this Privacy Policy, including account support, payment reconciliation, dispute handling or legal duties. When that need ends, we review the record for deletion or suitable restriction.

Your change request

You can contact us through the signed-in support route to request access, correction or a deletion review. Describe the change clearly and provide the phone-linked account detail so we can verify ownership without exposing another person’s data.

Privacy Policy Questions For Indonesia Accounts

These answers focus on the searches we hear most often before an account is opened. They cover the moto66 Privacy Policy, wallet references, mobile access, account verification and requests to see or change personal data. If your situation involves a specific payment receipt, include its reference when you contact us through the account support path.

The moto66 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references and support requests. It explains why we use each category, how we protect access and when records may be retained for reconciliation, disputes or legal duties.

The Privacy Policy treats DANA and QRIS references as payment-event details linked to your account. We use them to match a deposit request, check a status question or investigate a receipt mismatch. A reference does not give us permission to use unrelated personal data.

Yes. Use the support path inside your signed-in account and ask for a copy of the personal data connected with your account. We may confirm the phone verification detail first, so we do not disclose records to somebody using another device or account.

Send a correction request through account support and identify the record that appears wrong, such as a phone detail or wallet reference. Include enough context for matching, but do not send another person’s information. We will assess the request against the Privacy Policy.

Cookies may keep a browser session, remember a selected setting and support security checks when you move from login to the lobby. The same Privacy Policy applies on phone, tablet and desktop browser access. Your device controls can restrict cookies, though sign-in may need repeating.

Retention depends on the purpose and any applicable legal or dispute-handling need. Account, support and payment records can remain while reconciliation, security review or a request is open. We then review whether deletion or restriction is appropriate under this Privacy Policy.

You can ask us to review deletion through the signed-in support route, and we will assess it under the Privacy Policy. Some records may need to remain for an open payment reconciliation, dispute, security matter or legal duty. Access or eligibility depends on local law.