Reference

Privacy Policy for Your metro666 Account

Your metro666 Privacy Policy explains what we collect when you open an account, verify your phone, browse Andar Bahar or use DANA and QRIS at the cashier.

Account clarityWallet recordsCookie choicesRequest access
Explore Our Lobby Read FAQ
metro666 Privacy Policy for Your metro666 Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact path helps when a Privacy Policy question concerns a login record, wallet reference or phone verification detail.

Account request Use the account support route to ask what personal details are connected with your metro666 account. Include your registered phone number and the subject of your request, but leave out passwords, one-time codes and DANA, OVO or GoPay security credentials.
Wallet record If a QRIS, bank transfer or virtual account reference appears incorrect, send the receipt reference through the available support contact. We can use that identifier to locate the relevant record without requiring you to share a full wallet password or private security code.
Privacy change For a correction, deletion question or cookie preference request, select the privacy subject in our contact form or account help route. We will explain any identity check needed before changing records and tell you when a legal or operational retention rule applies.
DATA PRACTICE

How metro666 Handles Your Records

We keep this policy practical by tying each data use to an account action you can recognise, such as phone verification, a wallet status check or a sign-in attempt.

Account details

We may collect the details you enter during account creation, including contact data needed for phone verification. These records help us connect your sign-in with your account and respond when you ask us to correct, access or explain personal details.

Payment references

DANA, OVO, GoPay and QRIS activity can create transaction references, while bank transfer and virtual account use can create matching records. We use those references for status checks, receipt questions and account reconciliation rather than requesting your wallet credentials.

Device signals

When you sign in from a phone or desktop browser, technical details such as device type, browser version and connection signals may be recorded for security and fault diagnosis. These signals help us investigate repeated login errors without reading private content on your device.

Cookies

Cookies may keep a session active, remember a selected setting or show us where a page is failing. You can manage cookie controls in your browser, although removing some cookies may require you to repeat the phone verification or sign-in step.

Retention

We retain account, security and payment references only for the period needed for the stated service, dispute handling, security checks or a legal requirement. If you ask when a record will be removed, we will explain the applicable retention reason rather than promise an instant deletion.

Your request

Where local law permits, you can request access, correction, deletion or clarification through the support contact shown on this site. We may verify account ownership before acting, and we will explain if a record must stay because of security, payment reconciliation or legal duties.

Privacy Policy Answers for metro666

These Privacy Policy answers focus on the records you are most likely to ask about before opening an account: phone verification, wallet references, cookies, device access and requests for changes. We keep the route direct through account support, and our response may depend on the identity checks and local rules that apply to your request.

The metro666 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and how to request access or correction.

We use the phone verification step to connect account access with the contact detail you provide and to investigate sign-in issues. The Privacy Policy explains how that record is handled. Do not send one-time codes or passwords when contacting us about your account.

Yes. The Privacy Policy covers transaction references and wallet status details linked to your account when you use QRIS or DANA, as well as OVO, GoPay, bank transfer and virtual account references. We use these records for reconciliation, receipt questions and security checks.

Use the account support route or contact form shown on metro666 and identify the account detail you want to access. We may verify ownership before responding. Where local law permits, we will explain the available record, any limits and the next step.

You can ask for correction or deletion through the privacy contact route. We first check that the request comes from the account holder, then assess whether the record can be changed. Some security, payment or legal records may need to remain for a stated reason.

On a phone browser, cookies may preserve your session, remember a setting or help us diagnose a page issue. You can adjust them in your browser controls. If you remove required cookies, the Privacy Policy notes that sign-in or phone verification may need to happen again.

Yes. Access and eligibility depend on local law, and privacy rights can vary by where you are located. Where local law permits, you can ask about access, correction, deletion or retention through our support route, and we will explain any applicable restriction.

Related Pages

metro666 Indonesia giobola Account information metro666 Casino About Us