Reference

Open skor7 Privacy Policy with clarity

skor7 Privacy Policy explains how we handle the account details connected with Live Roulette Wheel, Spaceman Crash Play and local wallet activity.

Account dataWallet recordsCookie choicesContact requests
Explore Our Lobby Read FAQ
skor7 Open skor7 Privacy Policy with clarity
CONTACT OUR TEAM

Contact us about Privacy Policy

A clear contact path helps you ask about the Privacy Policy without sending account details through an unrelated channel.

Policy questions Send a Privacy Policy question through the signed-in support contact. Tell us whether your request concerns account access, cookies, a DANA record or another data category, and we will use the account details you provide to locate the relevant record.
Wallet record check For an OVO, GoPay or QRIS record, include the transaction reference and approximate date rather than sharing a wallet password or security code. We compare the reference with our account ledger so a payment-status question stays tied to the correct account.
Account change request If you want to correct, access or remove eligible account data, use the same support route and explain the requested change. We may ask for phone verification before acting, which helps prevent another person from changing your privacy records.
HOW WE HANDLE DATA

Switch to clear Privacy Policy controls

The Privacy Policy is applied through practical account and browser controls rather than broad promises.

Account details

When you create an account, we handle the contact details and phone-verification result needed for sign-in. We do not need your wallet password for this step. Keeping your phone number current helps us identify the correct account when you ask about Privacy Policy records.

Payment references

DANA, QRIS, bank transfer and virtual account activity can create reference data, status updates and reconciliation entries. We use these details to connect a receipt with your account or investigate a cashier discrepancy, not to request secret wallet credentials.

Cookies and browser use

Cookies and similar browser storage can remember sign-in choices, protect account sessions and help us understand whether a page loads correctly. You can adjust browser settings, although removing necessary cookies may interrupt the sign-in path or require another verification step.

Security events

We may record device type, browser version, connection markers and failed sign-in events to protect your account. A new device can trigger an additional phone check. These records help us investigate suspicious access without treating normal device changes as proof of wrongdoing.

Retention period

We retain account, payment and support records only for the operational, dispute or legal period that applies to them. When a record is no longer needed, we delete it or remove identifying parts according to our retention process.

Requesting changes

You can ask what eligible data we hold, request a correction or ask about deletion through the signed-in support contact. Include your account email or phone and the relevant reference; we may verify your identity before making a change.

Ask skor7 Privacy Policy questions

These Privacy Policy answers focus on the account questions you are most likely to ask before using skor7 in Indonesia. We explain what may be collected, why payment references appear, how cookies affect sign-in and how to contact us about a correction or deletion. If a request involves eligibility or access, the outcome depends on local law.

The skor7 Privacy Policy covers account details, phone verification, browser cookies, device and security events, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, access requests and ways to contact us.

A DANA or QRIS transaction can create a reference, amount, selected rail and status entry linked to your account. We use that data to match receipts, answer wallet questions and resolve account discrepancies. We do not need your wallet password or security code for this purpose.

The Privacy Policy allows us to record practical access details such as device type, browser version, connection markers and failed sign-in events. These details help protect sessions and investigate unusual access. A new phone or browser may require phone verification before account data is disclosed.

Use the signed-in support contact and state which account detail is incorrect, such as an email or phone number. Add the relevant payment reference when needed. We may ask you to complete phone verification so we change the correct record and protect your account.

You can send a deletion request through the support contact. We assess which records can be removed and which must remain for account administration, disputes or legal duties. Any eligible removal follows our retention process, and access to the account may depend on local law.

Cookies can keep a sign-in session active, remember a browser choice and help us detect page or security problems. You can adjust them in your browser, but disabling necessary cookies may interrupt account access. The Privacy Policy explains why those technical records are used.

Where local law permits, you can ask for eligible account data through the signed-in support contact. Include your account email or phone and describe the data category, such as wallet references or support messages. We verify the request before sharing records connected with your account.

Related Pages

skor7 Indonesia About Us FAQ QRIS Withdraw Guide Liga 1 Over Under