Reference

Open sketer88 Privacy Policy Before Account Access

The sketer88 Privacy Policy explains what account, device and wallet details we handle when you open an account or enter the lobby.

Account dataWallet recordsDevice controlsPrivacy requests
sketer88 Open sketer88 Privacy Policy Before Account Access
CONTACT ROUTES

Check Your Privacy Contact Path

A clear support path helps you ask about personal data without explaining the whole account history again.

Account help Use the account help path when you need to ask which phone, sign-in or…
Wallet query For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference and…
Data request Ask for a copy, correction or removal through the same support route.
CONTROL DETAILS

Explore Account And Device Safeguards

Privacy protection is handled through everyday account controls rather than a separate device application.

Data handling

We group account details by purpose: phone verification supports access, sign-in records help protect the account, and wallet references connect a payment status to the correct profile. We do not describe a game choice, such as Live Roulette Elite, as permission to collect unrelated personal content.

Cookie use

Cookies and similar device signals help keep your selected page, sign-in state and security checks working. On mobile, the same browser path can carry you from account access to the lobby; clearing cookies may require phone verification again before private account pages open.

Account security

Phone verification is required before account access, and sign-in activity may be checked when a device or location changes. If a login seems unusual, we may pause the requested account action until ownership is confirmed through the account support path.

Retention periods

We retain each category only for the operational, security or legal purpose connected to it. A DANA status record, a phone verification event and a support exchange may therefore follow different retention periods; we can explain the applicable period when you make a specific request.

Who handles requests

Our privacy support team handles questions about account records, device signals and wallet references. Give us your linked phone number, request type and account reference, then we can confirm ownership before disclosing, correcting or removing eligible data.

Change requests

You can ask us to correct an inaccurate phone or account detail, request a copy of eligible records, or ask about deletion. We first check identity and the legal basis for the request, so the result depends on local law and the record involved.

Find Privacy Answers Before Opening

These Privacy Policy answers address the questions we expect before an account is opened from Indonesia. They cover the records connected to phone verification, wallet status, cookies, account access and privacy requests. Where the answer depends on local law, we say so directly, so you know what to include when contacting our support path.

The sketer88 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support exchanges and payment references. It explains why we use each category, how it supports account security or wallet matching, and how you can ask about eligible access, correction or removal.

When you use DANA, OVO, GoPay or QRIS, we store the payment reference and status needed to connect that event with your account. Bank transfer and virtual account references follow the same process. We do not need your wallet password or unrelated device files.

Phone verification confirms account ownership before private account pages open and helps us respond to a data request safely. A verification event may also help investigate an unusual sign-in. The specific use and any required retention depend on local law and the account action involved.

Yes. Use the account help path and identify the record you believe is inaccurate, such as a phone number or account detail. Include your account reference, and we may confirm ownership before making a change. The available correction process depends on local law.

Cookies and device signals help maintain your sign-in state, page selection and security checks in a mobile browser. Clearing them can end the current session and may trigger phone verification again. The Privacy Policy explains the purpose of these signals rather than treating them as access to private files.

There is no single period for every record. Phone verification, wallet status, sign-in activity and support exchanges can have different operational, security or legal purposes. Ask through the privacy support path with a specific account reference, and we will explain the applicable period where local law permits.

Start with the account help route and state whether you want a copy, correction, deletion request or explanation of a data category. Add your linked phone number and account reference so we can verify ownership. We will assess the request according to the Privacy Policy and local law.