Reference

Open sio4d Privacy Policy Before Access

Our Privacy Policy explains what we collect when you create an account, verify your phone and move between the lobby and wallet area.

Clear data purposesPhone check detailsCookie choicesPayment record context
Browse Our Lobby Read FAQ
sio4d Open sio4d Privacy Policy Before Access
PRIVACY HELP

Find Support For Data Questions

A clear contact path helps when a Privacy Policy question affects your account or wallet status. We ask you to include the account phone number, the relevant request and any payment reference without sending a password or one-time code. Our support route can then match the request to the right account record and explain what we can change. If access is discussed, the outcome depends on local law.

Team online

Account data request

Use the contact route shown in your account help area to ask for a copy of personal data linked to your sio4d account. Include your verified phone number and request type so we can distinguish a data question from a normal login or wallet-status issue.

Payment record query

For a DANA, OVO, GoPay or QRIS record, send the visible reference and date rather than your wallet password. We use those details to locate the relevant entry, explain its privacy purpose and avoid exposing unrelated account activity.

Correction pathway

If your phone, name or account detail needs correction, contact us through the same account help path. We may request a phone verification step before changing protected fields, and any access decision depends on local law.

DATA PRACTICE

Browse Our Privacy Handling Steps

Privacy work follows the account journey rather than sitting apart from it. We separate identity details, device signals, cookie preferences and payment references by purpose, then apply account checks before discussing protected…

Data collection

We collect details you provide for an account, including contact data used for phone verification. We may also receive device, browser and session signals needed to keep login activity secure and connect a signed-in account to the correct lobby page.

Cookie controls

Cookies help retain session settings and support page functions across mobile and desktop browsers. You can manage browser cookie controls, although switching them off may affect login continuity or the way account privacy choices are saved.

Account security

A phone check can be required before account access or a protected detail is changed. We do not ask you to disclose a password or one-time code through a privacy request, and unusual device activity may trigger an additional account check.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match payment status with the correct account. We use the minimum transaction context needed for reconciliation and do not need your wallet password for a data request.

Retention choices

We retain account, security and transaction records only while they support the stated operational or legal purpose. When you ask about removal, we explain which records can be deleted and which may remain where local law permits continued retention.

Contact and changes

Send a privacy request through the account help route, naming the right to exercise and the detail concerned. We may verify ownership by phone before responding, then explain the result, any limits and the next step available to you.

Check Common Privacy Policy Answers

These Privacy Policy answers focus on the questions that arise before account access, during wallet activity and when you want control over your personal data. We keep the wording practical so you can identify the right request without sending unnecessary credentials. For account eligibility or access questions, the result depends on local law and the location connected with your account.

It covers account details, phone verification, cookies, device and browser signals, lobby session activity, payment references and requests to access, correct or remove eligible data. It explains why each category is used and how to contact us about a protected account record.

We use your phone number to create and protect the account path, including a clear phone verification step before account access or selected changes. Keep the number current, and never send a password or one-time code when asking a Privacy Policy question.

Yes. It covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use the relevant date, amount and status to match a transaction with your account and handle payment questions without requesting your wallet password.

Use the contact route in your account help area and state which detail is wrong, such as a phone number or account name. We may verify ownership by phone before making a protected change, and the available action depends on local law.

You can ask us to explain deletion options for your account data. Some records may need to remain for security, transaction reconciliation or legal reasons, so we will identify those limits rather than remove data without checking the applicable rule.

Cookies can keep a mobile browser session working, retain selected settings and support the path from phone verification to the lobby. Your browser controls can limit them, but doing so may interrupt login continuity or prevent privacy choices from being saved.

Send a request through the account help route with your verified phone number, the records you want and a clear request for access. We may confirm account ownership first, then explain the available data, format and any lawful limits.

Related Pages

sio4d Indonesia Live Football Odds FAQ levisslot About Us