Reference

impor88 Privacy Policy For Your Account

impor88 explains how we collect, use and protect details connected with your account, mobile browser access and wallet activity.

Account dataWallet recordsCookie choicesPrivacy requests
impor88 impor88 Privacy Policy For Your Account
PRIVACY HELP ROUTE

Get Privacy Answers Near Your Cashier Path

A privacy question should not leave you searching through unrelated pages. We keep the account support route close to the cashier path so you can ask about a wallet record, phone detail…

Account request Use the support route linked from your signed-in account to ask for a copy, correction or explanation of personal data connected with your impor88 profile.
Wallet record If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include the receipt reference and date so our team can check the matching account record.
Access concern For a privacy concern after phone verification, tell us whether it began on mobile browser or desktop and we can narrow the relevant sign-in and cookie records.
HANDLING YOUR DETAILS

How Mobile Legends Data Stays Account-Bound

We keep personal data tied to a defined account purpose rather than copying every activity into a broad profile.

Collected details

We may hold your phone number, account identifiers, device signals, browser settings, support messages and payment references needed to operate account access and respond to privacy requests.

Cookie choices

Cookies can remember consent, session status and language or display settings on your mobile browser. You can review browser controls, though removing session cookies may require another account sign-in.

Account security

Phone verification, sign-in records and unusual-device checks help us protect your account. Never send a password or one-time code in a support message requesting privacy assistance.

Retention timing

We keep account, payment and support records for as long as needed for security, dispute handling, service duties or applicable legal requirements, then review them for removal.

Correction requests

You can ask us to correct an inaccurate phone detail, account identifier or contact record. We may request an account check before changing information that affects access or payment matching.

Who to contact

Send privacy questions through the signed-in support path and describe the record involved. Include your account identifier, but omit passwords, one-time codes and unnecessary payment credentials.

Privacy Policy Answers For impor88

These Privacy Policy answers address the searches we hear most often before account access. They explain what happens with device data, cookies, payment references and correction requests, while keeping the route practical for an Indonesian account holder using mobile or desktop.

It covers account details, phone verification, device and browser records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to support account verification, sign-in protection and recovery. Before discussing private records or changing account details, we may ask you to confirm ownership.

Yes. The Privacy Policy explains that cookies can remember consent, session status and selected settings. You can adjust browser controls, but removing session cookies may require you to sign in again.

We use payment references, amounts and status details to match a transaction with your account, check a receipt and resolve wallet questions. We do not ask support messages to include passwords or codes.

Yes, where local law permits. Send a request through the signed-in support path with your account identifier and the specific record you want copied, corrected or explained.

Retention depends on the reason for collection. We may keep account, payment and support records for security, disputes, service duties or legal requirements, then review records that no longer need storage.

Yes. Tell us whether you used a mobile browser or desktop, the approximate access date and your account identifier. We can then check relevant session, device and cookie records.