Reference

slot 77 Privacy Policy for Indonesian accounts

Our Privacy Policy shows what we collect, why we use it and how you can ask for changes before opening an account.

Account clarityWallet recordsDevice controlsPolicy requests
slot 77 slot 77 Privacy Policy for Indonesian accounts
ASK ABOUT PRIVACY

Get help with account data requests

A clear support path helps when a Privacy Policy question concerns your login, wallet status or a phone verification record. Tell us the account contact you used and describe the request without sending a password or wallet PIN. We may ask for an account step that confirms you are the person making the request. Our support route can also connect a payment receipt or status check to the right account record.

Team online

Account request

Ask us to locate, correct or explain account data by giving the registered phone detail and the specific record you want checked. We will use that detail to identify the request safely.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction reference and date. Never include your wallet PIN, password or full authentication code.

Security concern

If a device or phone number no longer belongs to you, tell our support route promptly. We can explain the account-security step needed before discussing stored records or changing access details.

HOW WE HANDLE DATA

Explore six privacy controls we apply

We keep this policy practical by linking each privacy choice to an account action you recognise.

Account details

We use your registered contact details to identify the account, send account-related responses and complete the phone verification step before discussing protected records with you.

Wallet references

Payment records can contain a rail name such as QRIS or DANA, a reference, amount and status. We use those fields to match receipts and resolve account questions.

Device signals

A mobile browser may provide device, browser and connection signals that help us detect unusual access. These signals support account protection and are not a substitute for your password.

Cookies

Cookies can keep an account path working and remember selected settings. You can adjust browser cookie controls, but switching them off may interrupt verification or require you to repeat a step.

Retention period

We keep personal records for the period needed to provide support, protect accounts, reconcile payment references or meet a valid legal requirement, then remove or restrict them where appropriate.

Change requests

To request access, correction or deletion where local law permits, contact us with your registered account detail and the exact change sought. We may verify identity before acting.

Browse answers about your Privacy Policy

These Privacy Policy answers focus on the account steps you are most likely to search for before joining slot 77. They explain wallet records, mobile access, cookies, retention and the request path in plain English, while keeping eligibility tied to local law.

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

Phone verification helps us confirm that an account request comes from the account holder. It also gives our support route a safer way to discuss stored details without exposing a password or wallet PIN.

Yes. The policy covers transaction references and status details linked to QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity when those records are connected to your account.

Where local law permits, you can ask for access to eligible account data. Include your registered contact detail and describe the records sought; we may complete an identity check before responding.

Send a clear request through our support path, naming the data you want corrected or deleted. We assess the request under applicable rules, and some security or payment records may need to remain.

We may use browser, device and connection signals from your mobile or desktop path to help identify unusual access and protect account sessions. These signals support security checks around login and verification.

Retention depends on why a record exists. We keep details for account support, security, payment reconciliation or a valid legal requirement, then remove or restrict them when that purpose ends.