Reference

Privacy Policy For Your selat4d Account

selat4d Privacy Policy gives you a clear account of how we handle sign-up details, phone checks, wallet records and device signals.

Account clarityWallet recordsCookie choicesMobile access
selat4d Privacy Policy For Your selat4d Account
CONTACT PATHS

Where To Ask About Your Data

A direct support route helps you resolve a Privacy Policy question without sending account details through an unrelated channel.

Account support link Open the support link inside your account area for a Privacy Policy request. Tell us whether your question concerns sign-up data, phone verification, cookies, DANA, OVO, GoPay, QRIS or a bank transfer reference so we can route it correctly.
Privacy request details Send the account identifier connected to your request and describe the correction or access question in plain English. We may request an ownership check before showing personal records or changing details linked to your account.
Wallet record check If a wallet status appears incorrect, include the payment rail and reference shown in your account, such as QRIS or DANA. We use that context to locate the relevant record without asking you to share a wallet password.
HANDLING PRACTICES

How We Handle Account Data

Our Privacy Policy separates information needed to operate your account from signals used to keep access consistent across devices.

Phone verification

Before account access, phone verification links your sign-in step to the details you supplied. We use that check to reduce mistaken account matches and to help us respond to a data request from the correct account holder.

Payment references

DANA, OVO, GoPay and QRIS may return a reference, amount status and time stamp to the account flow. We use these records to match a wallet event, while the wallet password remains with the relevant payment service.

Device signals

When you move from a mobile browser to desktop, we may record device and session signals connected to access. These details help us examine unusual sign-in activity and do not replace the account ownership checks in this policy.

Cookie controls

Cookies can keep a session open, remember a language or preserve a security setting. You can manage cookies through your browser controls, although removing some cookies may require you to repeat the sign-in step.

Retention periods

We retain records only for the operational, security or account purpose that requires them, subject to applicable requirements. A request to remove or change data may be limited where a record is needed to resolve a transaction or account dispute.

Change requests

You can ask us to access, correct or clarify personal data through the support link in your account area. Include the specific field or record in question, and we will use an ownership check before discussing or updating it.

Privacy Policy Questions Answered

These Privacy Policy answers focus on the account actions you are most likely to take on selat4d. They explain what happens around phone verification, mobile cookies, wallet references and requests for access or correction. If your question is not covered, use the account support link and give us the smallest useful detail needed to locate your record.

It covers account details, phone verification, device and session signals, cookies, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, access requests, corrections and the local-law conditions attached to access.

Phone verification helps connect an account request to the correct account holder before access is given. It also supports account recovery and data questions. We may ask you to confirm ownership again before discussing personal records or changing a phone-linked account detail.

Yes. The policy covers payment references, status results and time stamps connected with QRIS, DANA, OVO and GoPay activity. We use those details to match an account event; payment passwords and wallet credentials remain with the relevant payment service.

Cookies may preserve a session, language choice or security setting when you use a mobile browser or desktop device. Your browser can remove or restrict them. If you do so, the next account visit may require another sign-in or verification step.

You can request access or a correction through the support link inside your account area. State the field or record you want checked and provide the connected account identifier. We may verify ownership first, and some records may need to remain for account or transaction handling.

Retention depends on why a record exists, its security value and applicable local requirements. Account and payment references may be kept while needed for reconciliation, dispute handling or account protection. You can ask support to explain the purpose of a particular record.

Access depends on local law and this policy applies where local law permits. Your location and account details may affect eligibility and the way a request is handled. If you are unsure, contact support through the account path before submitting personal or wallet details.