Reference

Open selat4d Privacy Policy Before Access

Clear data choices help you understand what happens when you open an account, use a mobile browser, or check DANA and QRIS status.

Account data explainedWallet references coveredCookie choices listedRequest path included
selat4d Open selat4d Privacy Policy Before Access
PRIVACY HELP PATH

Find Privacy Help Through Your Account

A direct support path keeps a Privacy Policy question from becoming a wallet-status problem.

Account request Use the account support form to ask for a copy, correction or deletion under…
Wallet question When a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference…
Access issue If phone verification or mobile-browser access fails, contact us through the support path beside…
DATA HANDLING DETAIL

Check How selat4d Handles Your Data

We keep this Privacy Policy practical by connecting each data use to an account step you can recognise.

Account details

We may hold the name, phone number, email and verification details you provide when opening an account.

Cookies and sessions

Cookies can keep your mobile-browser session connected while you move from account access to the lobby.

Device signals

Browser type, device details, approximate network data and sign-in time may help us identify unusual access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can be connected to your account record.

Retention choices

We keep data only for the period needed for the stated account, security, support or legal purpose.

Your requests

You can ask what personal data we hold, request a correction, ask about deletion or question a specific use.

Ask About Privacy Policy And Access

These Privacy Policy answers focus on the searches you may make before opening an account or while checking a data request. We explain the records connected to phone verification, mobile-browser use, cookies and local wallet references. For access or eligibility questions, the answer remains tied to local law, and account support can confirm the correct request path without asking for your secret wallet credentials.

It covers account details, phone verification, browser and device signals, cookies, support records, payment references and retention. It also explains how to ask for access, correction or deletion. Service access depends on local law, so that condition applies alongside the data rules.

Phone verification helps connect an account request to the person seeking access and helps us respond to account changes. We may retain the verification record for security or legal reasons. If the phone detail is outdated, request a correction through account support.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account references. We use those records to reconcile account activity or support questions, while wallet PINs and secret codes should remain private.

Sign in where possible, open the account support form and ask for a copy of the personal data connected to your profile. Add your linked phone or email and keep the request reference. We verify the request before sending account data.

You can request a correction or deletion through account support. We may retain records needed for security, dispute handling or legal duties, and we will explain that limitation. A mobile-browser request follows the same identity check as a desktop request.

Required cookies can keep your session active between phone verification and account support. Browser settings let you manage cookies, but disabling required ones may interrupt access or prevent a request form from working. Optional cookie choices are handled through the browser or displayed controls.

Use the support path shown in your account area and include a linked contact detail, request type and any relevant reference. For a DANA, QRIS or bank-transfer question, provide the transaction reference only. Never include passwords, one-time codes or wallet PINs.