Reference

antri88 Privacy Policy for Your Account

Your account, wallet and device choices are explained clearly in the antri88 Privacy Policy.

Account recordsWallet activityDevice choicesPrivacy requests
antri88 antri88 Privacy Policy for Your Account
HELP WITH RECORDS

Where To Ask About Privacy

A clear support path helps when a login record, wallet reference or device entry needs explanation. Open your account menu, choose the support route, and include the email or phone detail connected to your account. We use the request to locate the relevant Privacy Policy matter without asking you to send wallet passwords or private security codes.

Team online

Account access

If your phone verification or login record looks unfamiliar, contact us through the account support path. Tell us the approximate date and device type so we can check the relevant access event.

Wallet records

For a DANA, OVO, GoPay or QRIS reference, send the payment date and visible transaction code through support. We can explain how that reference is linked to your account record.

Privacy requests

To ask for a copy, correction or retention explanation, select the privacy request route in support. We may ask you to confirm account ownership before sharing personal records.

DATA PRACTICES

Six Privacy Checks Behind Your Account

We keep the Privacy Policy practical by connecting each rule to an account action you can recognise.

Data we receive

We may receive your account contact details, phone verification result, login timestamps, device type, support messages and wallet references. We use only the records needed for account access, security, payment matching and policy requests.

Cookies and storage

Cookies and local device storage can remember a session, language choice or security signal. You can clear them in your browser settings, although doing so may require another login or phone verification.

Account security

We check sign-in activity and phone verification before allowing sensitive account actions. Never send us a password, wallet PIN or one-time security code through support or a policy request.

Retention periods

Records remain while needed for account operation, payment matching, fraud checks, dispute handling or legal duties. When a record is no longer needed, our handling follows the applicable retention requirement.

Access requests

You can ask which personal records are connected to your account by using the support route. Include your registered contact detail and request type so we can verify ownership before responding.

Corrections and changes

If your contact detail or account record is inaccurate, tell us what needs changing and why. We may retain the earlier entry where payment, security or legal records require an audit trail.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers focus on the records and account steps you are most likely to ask about before opening an account. We keep the wording tied to DANA, QRIS, phone verification, device access and the support path used for privacy requests.

It covers account contact details, phone verification, login events, device signals, support messages and payment references. It also explains cookies, retention, security checks and how to request access or corrections.

A DANA or QRIS reference helps us match a cashier action to the correct account and investigate an unclear status. We do not need your wallet PIN or one-time security code.

Yes. The Privacy Policy covers OVO and GoPay references used with your account, along with DANA, QRIS, bank transfer and virtual account records where those rails appear in your account activity.

Open your account menu, select the support route and ask for an account data copy. Include your registered phone or email so we can confirm ownership before providing records where local law permits.

You can ask us to correct an inaccurate contact or account entry through support. Device history may remain unchanged when it is needed for security checks, payment matching or a legal record.

We retain records for as long as needed for account access, wallet matching, security checks, dispute handling or legal duties. The applicable requirement determines when a record can be removed.

Use the support route inside your account and describe whether you need access, correction, deletion details or a retention explanation. Do not include passwords, wallet PINs or one-time security codes.