Reference

Privacy Policy for Your metro555 Account

Our Privacy Policy explains what we collect when you open a metro555 account, sign in from your phone, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesRequest access
Explore The Lobby Read FAQ
metro555 Privacy Policy for Your metro555 Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact route matters when you want to understand a Privacy Policy request or check an account record. We keep privacy questions separate from ordinary lobby questions, but our support team can route you when a login, wallet status or receipt record is part of the request. Include the email or phone number linked to your account, the request you want handled and any relevant date. Do not send a wallet password, full card secret or one-time verification code.

Team online

Privacy request

Use our support contact path to ask for the personal data linked to your metro555 account. We may ask you to confirm the registered phone or email before disclosing account details, so a request cannot be redirected to another person.

Correction route

If your contact detail or account record is inaccurate, tell us what needs changing and why. We compare the request with the account step and phone verification record, then explain any additional check needed before applying an update.

Receipt check

When a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference appears in a privacy question, send the transaction date and reference only. We use that limited detail to locate the record without asking for your wallet sign-in data.

HANDLING DETAILS

How We Manage Privacy In Practice

Privacy is handled through account steps rather than a vague promise. We limit access to records according to the task being performed, separate wallet references from login credentials and use device signals…

Account collection

At account opening, we collect the contact details needed to create your profile and complete phone verification. We do not need your DANA, OVO or GoPay password. Payment references are used to connect a cashier event with the correct account record.

Device signals

A mobile browser or desktop session can create technical records such as device type, browser version, language setting and login time. These signals help us spot a session that does not match your normal access pattern without reading private content from your device.

Cookie controls

Cookies may remember a session choice, support account access and help us understand whether a page loads correctly. You can adjust cookie settings in your browser. Blocking some cookies may require you to repeat an account step or sign in again.

Account protection

We use phone verification and session checks before account access, especially when a sign-in or cashier action looks unusual. Keep your verification code private and contact support if your account opens from a device you do not recognise.

Retention period

We keep account, payment-reference and support records for as long as needed for account operation, security checks, dispute handling and applicable legal duties. When a record is no longer needed for those purposes, our handling process moves it toward removal or restricted storage.

Your request

You can ask what personal data we hold, request a correction, ask about deletion or question a processing purpose through support. We may verify your identity first, then explain the result, any limits and the next step under local requirements.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account and payment records you are most likely to ask about before opening metro555. We explain the practical route for access, correction, cookies, retention and contact requests, including what we need from you to locate a record. If your question involves a specific account event, include its date and the registered contact detail through our support path.

The metro555 Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, support messages and payment references. It explains why we use each type of data, how long records may remain and how you can ask for access or a correction.

We may store a payment reference, status, amount and time needed to match a DANA or QRIS event with your account. We do not ask for your wallet password. The same principle applies to OVO, GoPay, bank transfer and virtual account records.

Contact our support path and state that you want a copy of the personal data linked to your account. Include your registered email or phone number and the type of record you need. We may complete an identity check before sending account details.

Yes, you can ask us to correct an inaccurate contact or account detail. Tell us the current entry, the correct entry and the reason for the change. We compare the request with your account and phone verification step before updating the record.

Cookies can remember a session choice, support sign-in and help us see whether a mobile page loads as expected. Your browser settings control many cookie choices. If you block required cookies, you may need to repeat login or phone verification.

We retain records while they support account operation, security checks, dispute handling or legal duties. A payment reference from DANA, OVO, GoPay, QRIS or a bank rail may therefore remain after the related cashier step, subject to the applicable retention need.

Yes. Access to the service and some data requests depend on local law. Where local law permits, you may ask about the data we hold, its purpose, correction or deletion. We explain any verification step or legal limit that affects your request.

Related Pages

metro555 Indonesia About Us Tennis Grand Slam Account information Access guide