Reference

Open sgpslot Privacy Policy Before Access

sgpslot Privacy Policy shows how we handle your account details, phone verification, device signals and payment references before you enter the lobby.

Account dataWallet recordsCookie choicesAccess requests
sgpslot Open sgpslot Privacy Policy Before Access
CONTACT YOUR WAY

Reach Support About Privacy Policy

A clear support route matters when a privacy question appears beside login or wallet status.

Account data question Ask us to explain the account details, phone verification record or sign-in event connected…
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send its date and…
Privacy request For access, correction or deletion requests, identify the account email or phone number and…
HOW WE HANDLE DATA

Explore sgpslot Data Handling Steps

We keep the Privacy Policy practical by tying each data use to an account action you can recognise.

Account security

Phone verification is recorded with the account access event so we can distinguish a confirmed sign-in from an uncompleted attempt. Do not share your password or verification code with anyone contacting you.

Mobile device signals

When you open the lobby in a mobile browser, we may receive browser type, device settings and sign-in timing. These signals help identify unusual access without reading unrelated content on your device.

Cookie controls

Cookies can keep an account session working and remember selected page settings. Our Privacy Policy explains their role and how you can adjust browser controls, though some access steps may then need repeating.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps can create transaction references. We use those references for matching, status checks and support rather than storing your wallet secret.

Retention periods

We retain account, security and transaction records for as long as needed for the stated purpose, support history or legal duties. The applicable period can depend on the record and local requirements.

Requesting changes

You can ask about access, correction or deletion through the support route connected to your account. We verify the request before making changes and explain any record that cannot be removed.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers cover the account steps most relevant to Indonesian customers, from phone verification and mobile cookies to wallet references and data requests. Read them before opening an account, then use the support route if your circumstances need a specific answer.

It covers data collected during account creation, phone verification, sign-in, mobile browsing, support contact and payment status checks. It also explains cookies, retention, sharing purposes and your available data requests.

We use phone verification to confirm that an account access step belongs to you and to help detect unusual sign-ins. The verification status may be retained with related security records.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS activity may create transaction references, timestamps and status details used to match receipts and answer wallet questions.

When you use a mobile browser, we may receive browser type, device characteristics, cookie status and sign-in timing. These details support session continuity and account security, not access to unrelated device content.

You can request access to data connected with your account through the support route. Provide the account phone or email, and we may complete an account check before releasing the relevant records.

Send a correction or deletion request through the account support path, describing the record and requested change. We verify ownership first, then explain any retention duty that prevents full removal.

Yes. Some rights, retention duties and access conditions depend on local law. Where local law permits, we process access, correction or deletion requests while keeping records required for security or legal purposes.