Reference

Open the sumpah jitu Privacy Policy

The sumpah jitu Privacy Policy explains what we collect when you create an account, sign in from a mobile device, browse titles such as Rocket Crash, or check…

Account dataCookie choicesWallet recordsAccess requests
sumpah jitu Open the sumpah jitu Privacy Policy
CONTACT ROUTES

Ask about Privacy Policy support

A clear contact route helps you ask what we hold, why we use it, or how to correct an account detail. Use the support path shown after sign-in and include the email or phone detail attached to your account, without sending a password or wallet PIN. We may ask for an account step or receipt reference before discussing records. This helps us direct a Privacy Policy request to the right account while access depends on local law.

Team online

Account data requests

Use the signed-in support path to ask for a copy of account details connected with your profile. We may verify your phone before answering, so a request about a DANA or QRIS record reaches the correct account.

Correction requests

Tell us which profile field needs correction and explain the change clearly. If the request relates to a bank transfer or virtual account reference, include that reference rather than sending banking credentials.

Cookie questions

Ask through the same support route if a cookie setting or device signal is unclear. Include your device type and the page where the issue appeared, such as the login screen or Rocket Crash title page.

DATA HANDLING

Explore how Privacy Policy choices work

We keep the Privacy Policy practical by separating account operation from optional device preferences. Your sign-in record, verification result and wallet reference help us protect account access, while cookie controls help explain…

Account security

We use sign-in events, device signals and phone verification before discussing account records. If access looks unusual, we may pause the request and ask you to complete the account step again rather than disclose details to an unverified contact.

Cookie controls

Cookies can keep a session open and remember a setting on your browser. Our Privacy Policy explains their role, while you can clear browser storage through your device settings when you want to remove locally saved session data.

Payment references

DANA, OVO, GoPay and QRIS records are handled as transaction references and status details, not as wallet passwords. Bank transfer and virtual account references may be retained to match a receipt with the related account request.

Game activity logs

When you open bola54, bingototo or Mega Fishing, technical logs may show the title, session time and device context. We use these details to maintain access and investigate a support question, not to request private wallet credentials.

Retention choices

We keep personal data only while it serves the purpose described in the Privacy Policy or a required account record. If you ask about removal, we explain which data can be deleted and which reference must remain temporarily.

Change requests

To request access, correction or clarification, use the account support route and identify the relevant email or phone detail. We may confirm ownership first, then record the request and explain the next step under local law.

Browse Privacy Policy answers

These Privacy Policy answers address the account and device questions you may have before opening access from Indonesia. We keep the wording tied to actual steps, including phone verification, cookie settings, wallet references and requests made through the signed-in support path. If your situation is not covered, contact us through the account route and mention the specific record or page involved.

It covers account details, sign-in events, device signals, phone verification, cookies, game-session records and payment references. It also explains how we handle requests to access, correct or clarify data connected with DANA, QRIS, bank transfer and virtual account activity.

DANA and QRIS can create reference and status records when you connect an account request with a local wallet. We use those details to match the transaction path, while wallet passwords and PINs should never be sent through our support route.

Sign in and use the support path attached to your account. State that your request concerns the Privacy Policy and identify the relevant phone or email detail. We may complete phone verification before explaining which records can be provided.

Yes. It explains how cookies can keep a session open or remember a browser setting when you move from login to a title such as Live Football Odds. You can also clear browser storage through your phone settings.

You can request a correction through the signed-in account support route. Name the field that is wrong and provide the corrected detail without sending a password. We may verify ownership before changing the account record, where local law permits.

We retain each record for the time needed for its stated purpose or an applicable account obligation. The Privacy Policy explains the categories involved. If you ask for removal, we will tell you what can be deleted and what must remain temporarily.

Yes. Access and eligibility depend on local law. Where local law permits, we process a verified request through the account support route and explain any restriction before taking action. We may ask for a phone check to protect your records.