Reference

selayar88 Privacy Policy for Your Account

Your account data stays connected to clear choices about login, phone verification and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
selayar88 selayar88 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact route helps when a privacy request and a wallet record appear together. We keep privacy assistance close to the account support path beside the cashier area, so you can identify the relevant DANA, QRIS or bank transfer reference without sending unnecessary details. Use the account support route to ask about access, correction, deletion or a cookie choice.

Team online

Account support path

Open the support route from your signed-in account and describe the Privacy Policy request. Include the affected email or phone detail, but never send a password or wallet PIN.

Payment record check

If your request concerns DANA, OVO, GoPay, QRIS or a bank transfer, share the payment reference and date. We use those details to locate the record without requesting full wallet credentials.

Access request

Ask us for the account data connected with your sign-in. We may ask for phone verification before responding, helping us avoid releasing personal details to the wrong person.

DATA PRACTICES

Security Steps Behind Your Account Record

Privacy protection works through practical account steps rather than vague promises. We limit internal access to account and payment records, check unusual sign-in signals, and use the details…

Collected account details

We may handle your name, contact detail, phone verification result, sign-in history, device signals and support messages.

Wallet and bank references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references may appear in payment records.

Cookie controls

A necessary cookie can keep your browser session active on Android or desktop.

Account security

Phone verification takes place before account access, and we may compare sign-in and device signals when activity appears unusual.

Retention approach

We retain account, payment and support records only for the period needed for the stated purpose, account administration, dispute handling…

Changes and questions

You can ask us to correct inaccurate details, explain a record or request deletion where available.

Privacy Policy Answers Before Account Opening

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the account step, device data, payment references, cookies and request path in plain English for Indonesian customers. If your situation depends on a local rule, we will assess it under the applicable requirement.

It covers account details, phone verification, sign-in events, device signals, cookies, payment references and support messages. It also explains your choices to access, correct or request removal of eligible data.

We use phone verification before account access to connect the request with the correct account and reduce mistaken disclosure. The result can be recorded as part of account security and access handling.

Yes. The Privacy Policy covers DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account status. We use these records to match payment activity, not to request your wallet PIN.

We may record browser, device and sign-in signals from your Android phone or desktop session. These indicators help protect account access and investigate unusual activity without needing the contents of your personal device.

Use the signed-in account support path and ask for an access request. Identify your account email or phone detail, complete any identity check we require, and avoid sending passwords or verification codes.

You can request correction of inaccurate details or removal where available. Send the request through account support, explain which record is affected, and understand that some records may remain when a legal duty applies.

Account access and privacy choices depend on local law. Where local law permits, we apply the requests and controls described here; a local requirement may change how a request is handled.