Reference

Open with level789 Privacy Policy

Your account details, wallet records and device data are explained clearly in the level789 Privacy Policy.

Account clarityWallet recordsDevice choicesContact path
level789 Open with level789 Privacy Policy
CONTACT WHEN NEEDED

Find policy help beside cashier

A clear contact route matters when a wallet reference or account detail needs attention.

Account access If your phone verification or login record looks incorrect, send the account contact detail…
Wallet status For DANA, OVO, GoPay or QRIS questions, include the payment reference and status shown…
Policy requests Ask us to access, correct or remove eligible personal data through the account support…
DATA CONTROL POINTS

Explore our data handling controls

We handle privacy requests through practical account steps rather than vague promises. Your information is separated by account records, payment references and device events, while access checks help…

Account creation

When you open an account, we use the phone number and verification details you provide to create a sign-in record.

Cookie settings

Cookies and similar browser storage help keep your session active, remember selected settings and detect unusual sign-in activity.

Device signals

We may record device type, browser version, network indicators and sign-in time for security checks.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match a payment event with your account.

Retention choices

We keep personal data for account operation, payment reconciliation, support history and applicable legal duties.

Change requests

To request access, correction or deletion, contact us through the account support route with your registered contact detail.

Browse Privacy Policy answers

These Privacy Policy answers address the account, wallet and device questions you may have before opening access. They also explain the practical route for correcting records or asking what data is held. If your situation is not covered, send the account reference through support and we will direct the request to the right policy path.

It covers account details, phone verification, login events, device signals, cookies, payment references and support messages. It also explains why we use each category and how you can request access or correction.

No. We may store the transaction reference, amount, status and time for DANA or QRIS matching, but you should never send a wallet password, PIN or full security code to support.

Device type, browser details, network indicators and sign-in time help us identify unusual account access. These signals support security checks and are not a request for access to your private files.

Use the account support route and provide your registered contact detail plus the field that needs correction. We may complete an account verification step before changing the stored record.

Yes. Send an access request through support with your account contact detail. We will explain the available record categories and may verify your identity before sharing information linked to the account.

We retain payment references for account operation, reconciliation, support handling and applicable legal duties. Once the relevant period ends, records are deleted, anonymised or restricted from routine use.

Yes. Some access, correction or deletion rights depend on local law. Where local law permits, we will process a valid request after confirming that it comes from the account holder.