Reference

88 resmi Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your 88 resmi account, including login records and wallet activity.

Account data explainedWallet records coveredAccess depends on local lawContact path included
88resmi.xyz page image
CONTACT THE TEAM

Check Privacy Questions Through Support Chat

A direct support route helps when your Privacy Policy question concerns a login, wallet reference or account record.

Account contact Use the support chat from your account area for a data-access request, correction request…
Payment reference For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date rather…
Login concern If a login or phone-verification record looks unfamiliar, tell support through the account contact…
DATA HANDLING

Explore How We Handle Account Records

We keep the Privacy Policy practical by tying each data use to an account action you can recognise.

Collected details

We may receive your name, phone number, account credentials, verification result, device type, IP-related session detail and support messages. We collect these details when you create, use or ask us to service an account.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account check can leave a reference, amount, status and time. These records help match a payment event to your account without storing a wallet password.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, maintain page security and help us understand an account session. You can manage browser cookie controls, although some account functions may then need another sign-in.

Account protection

We use phone verification, sign-in records and device signals to reduce unauthorised account access. Never share your password or verification code; if a session seems unfamiliar, contact us through support chat.

Retention period

We retain account, payment and support records only for the period needed for account service, dispute checks, security work or legal duties. When a record is no longer needed, our handling follows our deletion process.

Your requests

You can ask what personal details we hold, request a correction, ask about deletion where applicable, or question a data use. We may verify account ownership before making a change or sharing account details.

Browse Answers About Privacy Policy

These Privacy Policy answers focus on the account questions Indonesian customers usually ask before registration. They explain payment references, cookies, phone verification, access requests and the contact route, while any access or eligibility question depends on local law. If your situation is different, send the relevant account detail through support chat without sharing secret credentials.

It covers account details, phone verification, login and device records, cookies, support messages, payment references and retention. It also explains how to ask for access, correction or another permitted account-data request.

No. A DANA or QRIS check may create a reference, amount, status and timestamp for account matching, but you should never send us a wallet password, PIN or one-time verification code.

Open support chat from your account area and ask for a data-access request. Include your registered phone number or email, then complete any ownership check needed before we release account details.

Yes, contact support chat with the detail that needs correction and the reason it is inaccurate. We may verify your account first, then update the record where the request is valid and permitted.

Cookies can maintain a sign-in session, while device and session signals help identify unusual access. These records support account protection and page operation; browser controls can remove cookies but may require another login.

We keep records for account service, payment matching, dispute checks, security work or legal duties for as long as needed. Retention can differ by record type, and support can explain a specific request.

Yes, the policy applies to account activity on a phone or computer, including a session from Bandung. Access and eligibility depend on local law, and phone verification may be required before account access.