Reference

Privacy Policy for Your moto3 Account

Your account details, wallet records and device access are covered in the moto3 Privacy Policy, so you can see what we collect and why before opening an account.

Account dataWallet recordsDevice accessPolicy requests
moto3 Privacy Policy for Your moto3 Account
REQUEST ROUTES

Get Help With Privacy Requests

A clear request route helps you resolve a privacy question without repeating your account story.

Account privacy request Ask for a copy of the personal data linked to your account through the available support route. Include your registered phone number in the request, but do not include your password or verification code.
Wallet record question For a DANA, OVO, GoPay or QRIS record, tell us the date, amount reference shown in your account and status label. We use those details to locate the relevant payment event without requesting your wallet password.
Access and correction If your name, phone detail or account record needs correction, identify the field and explain the change. We may confirm account ownership before editing data, especially when the request affects access or a payment receipt.
DATA PRACTICE

How We Handle Your Account Data

Privacy controls work best when they match the steps you actually take. We connect account records to login and verification events, keep wallet references separate from secret credentials, and use device signals…

Collected account details

When you open an account, we collect the details needed to create your profile and complete phone verification. Login history, account settings and support messages can also be linked to that profile so we can answer a request accurately.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may produce a reference, status or receipt record. We use those records to reconcile your account, but we do not ask for your wallet password or banking secret.

Cookies and browser data

Cookies and similar browser data can keep a signed-in session working and remember basic display choices. You can clear or restrict cookies in your mobile or desktop browser, although some account steps may then need to be repeated.

Security checks

Phone verification, login events and device signals help us detect an unusual sign-in or protect an account during a sensitive request. We may pause disclosure until ownership is confirmed, and we will not ask you to share a one-time code.

Retention approach

We retain personal data for as long as it supports account security, payment reconciliation, support handling or a legal requirement. When a record is no longer needed for those purposes, we remove it or keep it in a form that does not directly identify you.

Policy changes

If our collection or use of personal data changes, we revise this Privacy Policy and place the new version on this page. Check the page before opening an account or continuing after a material change, especially when using a new device.

Privacy Policy Questions Answered

These answers focus on the questions you may have before creating an account or asking us to handle your data. We keep the wording practical: what we collect, how wallet records appear, how to make a request and what may happen when local rules apply. For a case-specific answer, use the account support path and avoid sending secret login or payment credentials.

The moto3 Privacy Policy covers account details, phone verification, login events, device and browser data, cookies, support messages and payment references. It also explains retention, security checks, your request options and the conditions that apply where local law permits.

We do not ask you to send a DANA, OVO, GoPay or QRIS password. Our records may show a payment reference, status or receipt connection so we can reconcile your account, but secret wallet credentials should remain with you and the payment service.

Use the available account support route and ask for access to the personal data linked to your profile. State your registered phone detail and the records you want, such as login history or payment references. We may verify ownership before releasing anything.

Yes, you can ask us to correct an inaccurate account detail by identifying the field and the required change. For phone or payment-related records, we may request an ownership check first so a third party cannot alter your access or receipt history.

Send a removal request through the account support path and specify the data involved. We assess the request against account security, payment reconciliation and applicable retention duties. Some records may need to remain for a stated period before removal or anonymisation.

Yes. The policy covers access from a mobile browser as well as desktop use, including cookies, device signals and login events. If you clear browser storage, you may need to complete phone verification again before account access is restored.

It can. Account access and eligibility depends on local law, and the handling of a data request may also depend on rules applying to your location. We assess each request under the relevant conditions and explain the next step through support.