Reference

sekar4d Privacy Policy, Clearly Explained

sekar4d Privacy Policy shows what we collect when you open an account, check Live Roulette Grand or use DANA and QRIS, why each data point is needed, and…

Account dataWallet recordsDevice choicesYour requests
sekar4d sekar4d Privacy Policy, Clearly Explained
REQUEST HELP

Get A Direct Privacy Support Path

A privacy question should not be mixed with a stalled login or wallet status. We give you a clear route to ask what data is attached to your account, why a security check appeared, or how a payment reference is stored. Include your account identifier and the relevant date, but never send a password, one-time code or full banking credential. Our support route can also help you reach the right privacy contact when your request concerns DANA, QRIS, a device change or an account record.

Team online

Account data request

Use the privacy contact route linked to your account help area when you want to ask which account details, verification records or device signals we hold. We may request an account step to confirm that the request comes from you.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, send the date, amount reference shown to you and account identifier through the stated contact route. We will explain the record without asking for your wallet password or access code.

Correction or removal

If a detail is wrong or you want to ask about deletion, tell us the exact field and reason through our privacy contact path. We assess the request against account security, dispute handling and any duty that still requires retention.

DATA HANDLING

What We Do With Account And Device Data

Privacy starts at the account form and continues when you move between a mobile browser, the lobby and wallet status.

Account creation

When you open an account, we collect the fields needed to create access and send account messages.

Payment references

A wallet or bank record can include a reference, status, time and account link so we can match the transaction…

Cookies and devices

Cookies and device signals help preserve a login session, detect unusual access and remember settings on mobile or desktop.

Account protection

We use account identifiers, verification events and access signals to reduce unauthorised entry.

Retention periods

We retain records only while they support account access, payment matching, security review, dispute handling or a legal requirement.

Your privacy contact

You can ask for access, correction, restriction or deletion through the privacy contact route named on this page.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. They explain the practical effect of our rules for Indonesian access, mobile devices, payment references and account requests. If your situation is not listed, use the privacy contact route with the smallest useful set of details. Never include a password, one-time code or complete bank login in a request.

The sekar4d Privacy Policy covers account fields, phone verification, device and session signals, cookies, support messages, game browsing records and payment references. It applies when you use the website on mobile or desktop, including account access, wallet status checks and requests to change your stored data.

Phone verification helps us confirm that an account access request comes from the account holder and helps reduce unauthorised entry. We may store the verification event and related security signal. We do not ask for your wallet password, bank password or one-time code in a privacy request.

Yes. The Privacy Policy covers the payment reference, status, time and account link created when you use DANA, OVO, GoPay or QRIS. It does not give us access to your wallet credentials. Bank transfer and virtual account references are handled in the same account-matching manner.

We may collect browser type, device signals, session timing, security events and settings needed to keep account access working. If you move from a mobile browser to desktop, these signals can help us identify an unusual change and request another verification step before showing private account data.

Use the privacy contact route connected to your account and state whether you want access or correction. Name the specific field or record, provide your account identifier and complete any identity check we request. We may withhold data that would expose another person or weaken account security.

We keep each record while it serves account access, payment matching, security, dispute handling or a legal requirement. When the purpose ends, we seek deletion or anonymisation where practical. Some payment and security records may remain longer when a legal, fraud or dispute reason applies.

Where local law permits, you can ask us to delete account data through the privacy contact route. We first verify the request and check whether a payment, security, dispute or legal duty requires retention. If deletion is limited, we explain which record must remain and why.