Reference

winslot303 Privacy Policy For Your Account

winslot303 Privacy Policy explains how we handle the details connected with your account, including login records, device signals and wallet references for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesRequest access
winslot303 winslot303 Privacy Policy For Your Account
PRIVACY SUPPORT

Check Privacy Help Through Our Account Path

A clear contact route helps when a privacy question sits beside a login or wallet record.

Privacy request Ask us to access, correct or clarify personal data through the privacy contact route.
Account context If your question concerns a login, phone check or wallet reference, tell us which…
Safe contact Never place a password, one-time code or complete bank detail in a privacy message.
DATA PRACTICE

Browse How We Handle Your Data

We treat this policy as an account control, not a general platform statement.

Account details

We use the details you provide during account creation, including contact data and phone verification status, to maintain sign-in access…

Wallet references

A DANA, OVO, GoPay or QRIS selection can create payment-reference records.

Device signals

When you move from login to the mobile lobby, we may record browser, device and session signals.

Cookie choices

Cookies can remember session settings and help us understand whether a policy page or account step opens correctly.

Retention process

We keep account, security and payment-reference records for the period needed for service operation, dispute handling or legal duties.

Change requests

You may ask us to correct inaccurate data, explain a record or remove data where applicable.

Explore Answers About Privacy Policy

These questions cover the searches we hear most often about account data, wallet references, cookies and requests. Read them before opening an account, then use the privacy contact path if your situation needs a record-specific answer.

It covers data linked with account creation, phone verification, sign-in activity, device sessions, cookies, payment references and privacy requests. It also explains retention, security checks and the route for asking about your records.

Phone verification helps connect the right person with an account and supports sign-in protection. We record the verification result and related security events, not your private one-time code.

Yes. It covers payment references created when you choose DANA, OVO, GoPay or QRIS. We use those references to check account status and payment matching, without asking for wallet passwords.

We may receive browser type, device signals, session timing and page events when you sign in on a phone. This supports security checks and helps us diagnose a failed move into the lobby.

Yes. Send a request through the privacy contact route with your account identifier and the field you believe is wrong. We may confirm your identity before changing the record.

Retention depends on the account purpose, security needs, disputes and legal duties. We remove or anonymise records when those needs end, subject to access requirements that depend on local law.

Use the privacy contact path shown on our site and describe the cookie or access issue. Do not send passwords or one-time codes; we will request only limited verification when needed.