Reference

map288 Privacy Policy For Your Account

map288 Privacy Policy shows what we collect, why we use it, and how you can ask us to correct or remove eligible account data.

Clear data purposesCookie choicesAccount access controlsContact for changes
Browse The Lobby Read FAQ
map288 map288 Privacy Policy For Your Account
ASK ABOUT DATA

Get Help With Privacy Requests

A clear contact route helps when your name, phone number, device record or wallet reference needs attention.

Account privacy desk Use the support path inside your account for a Privacy Policy request. Include your registered phone number, the record you are asking about, and whether you want access, correction or deletion where local law permits.
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount reference shown in your account and wallet name through support. We use those details to locate the relevant record without requesting your wallet PIN.
Access assistance When login or phone verification blocks a privacy request, explain the device path you used and the last successful account step. We can direct the request through the account help route while access depends on local law.
HOW WE HANDLE IT

Privacy Controls Across Your Account

The practical side of our Privacy Policy is visible in the account steps you already take: phone verification, wallet selection, device sign-in and support contact.

Account data

We use your submitted account details and phone verification result to recognise your account, route support replies and protect access. If a detail changes, contact us with the affected field so we can assess a correction request.

Payment references

Our records can include a wallet name, bank rail, virtual account reference, transaction status and receipt details. These entries help match activity to your account; they are not a request for your DANA, OVO or GoPay PIN.

Cookies and sessions

Cookies and session identifiers help remember a sign-in step, maintain a secure browser session and identify when a new device needs checking. You can clear browser data, although doing so may require phone verification again.

Device security

We may record device type, browser signals, session time and security events to detect unusual account access. If a mobile sign-in looks different from your usual path, we may ask you to complete an account verification step.

Retention choices

We keep records for the period needed for the purpose collected, account protection, transaction questions or legal duties. When a retention reason ends, we delete, anonymise or restrict the record where our process and local law allow.

Your requests

You can ask which personal data we hold, request a correction, question its use or seek deletion where local law permits. Send the request through account support, and include enough detail for us to locate the correct record.

Answers About map288 Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the account step, the device signals and payment references involved, plus the route for asking about your data. If a request concerns access, eligibility depends on local law; our support path can clarify which process applies to your account.

It covers data collected during account creation, phone verification, sign-in, wallet activity, device sessions and support contact. It also explains cookies, security checks, retention and your request options. The policy applies when you access our pages or account areas where local law permits.

We may handle your name and phone details, verification records, device and session signals, support messages, payment references and account activity. We use each category for a stated purpose, such as access control, transaction matching, security or answering a request about your account.

Our Privacy Policy does not ask you to send a DANA, OVO, GoPay or QRIS wallet PIN through support. We may retain a wallet name, receipt reference, status and related account details so a transaction can be matched and questioned without exposing your wallet password.

Cookies and session tools can keep a browser session active, remember a security step and show when a new device needs checking. Clearing them may sign you out or trigger phone verification again. Your browser settings control removal, while required session tools support account security.

Yes. Send an account support request stating whether you want access, correction, an explanation of use or deletion where local law permits. Include your registered phone number and the relevant record, such as a QRIS receipt or device session, so we can locate it.

We retain each record for the time needed for its stated purpose, account protection, transaction questions, dispute handling or legal duties. After that need ends, we may delete, anonymise or restrict it where our process and local law permit. Support can explain a specific retention question.

Use the support route inside your account and describe the Privacy Policy matter clearly. For a wallet question, include the payment name and reference; for a security question, include the device path and last account step. We may verify your identity before discussing personal records.

Related Pages

map288 Indonesia Bundesliga Handicap Odds Wheel of Fortune Spin Access guide FAQ