Reference

Privacy Policy For Your sr400 Account

sr400 Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Browse Our Lobby Read FAQ
sr400 Privacy Policy For Your sr400 Account
CONTACT PATH

Where Privacy Requests Meet Account Help

A clear contact path helps you resolve a privacy question without repeating your account story. Open the account help route when you need a copy request, a correction, or clarification about a wallet receipt linked to DANA or QRIS. Include your registered phone number and the relevant reference, but never send a wallet password or full authentication code. Our team may ask for an account check before changing records, and we keep the request trail so the response can be followed from the same support path.

Team online

Account access

If your phone verification or sign-in record looks wrong, use Account Help and describe the exact step that stopped you. We check the account record before discussing personal data, so your request stays connected to the correct sr400 profile.

Payment receipt

For a DANA, GoPay or QRIS receipt question, attach the payment reference rather than wallet credentials. We compare that reference with the account record and explain which transaction details we retain for support and payment-status checks.

Privacy request

Ask through the same account help route for access, correction or deletion questions. Tell us which record concerns you, complete the account check if requested, and we will explain the available response where local law permits.

DATA PRACTICE

What We Do With Account Data

We keep this policy practical: account records support sign-in, phone verification, payment matching and responses to your requests.

Account security

Before we discuss or change personal account data, we may confirm your registered phone and recent sign-in details. This step helps prevent another person from using a support request to reach your account or alter its records.

Phone verification

The phone verification step connects your account to the contact detail you supplied. We use that check for account access and support identity matching, not as a reason to request your DANA, OVO or GoPay password.

Cookies

Cookies can retain session choices and help us understand whether a login continues on the same browser. You can manage browser cookie settings, though changing them may affect sign-in continuity and the way a policy request is submitted.

Payment records

A QRIS, bank transfer or virtual account reference may remain in our records after a payment-status question is closed. We use the reference to reconcile the account trail, not to collect your wallet password or full banking login.

Retention period

We retain account, security and payment records for the time needed to provide support, investigate disputes, protect access or meet legal duties. When a record no longer serves one of those purposes, our retention process can remove or separate it.

Request changes

You can ask us to correct an inaccurate phone detail, clarify a retained record or request deletion where local law permits. Send the request through Account Help with enough detail to locate it, then complete any identity check we require.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account steps you are most likely to ask about before opening an account. They explain the connection between sign-in data, local wallet references, cookies and support requests without asking you to share sensitive credentials. If your question is not covered, use Account Help and include the relevant account or payment reference.

It covers account details, phone verification, sign-in and device records, cookies, payment references and support requests. The policy explains why we use each category, how long records may remain and how you can ask for access or correction where local law permits.

No. Our payment checks use a transaction reference and account match rather than your DANA or OVO password. Never send a wallet password or full authentication code in Account Help. We may retain the payment reference needed for status checks or dispute handling.

Phone verification helps connect the account to the contact detail you supplied before account access. It also lets us check identity when you ask about personal records. If a verification record is inaccurate, request a correction through Account Help after the account check.

Cookies and related browser storage can keep a session connected when you move from login to the lobby on a phone. Browser settings can remove or block them, but that may interrupt sign-in continuity or require another account check during support.

Yes, you can send an access request through Account Help and identify the account record you want us to locate. We may verify your registered phone or recent sign-in details first. We respond with the available data where local law permits.

Use Account Help and provide the payment reference, date and account phone detail connected with the transaction. Do not provide banking passwords. We compare the reference with our account trail and explain whether a correction can be made or needs further checking.

Retention depends on the purpose of the record, such as account support, security checks, payment reconciliation, dispute handling or legal duties. When those needs end, the record can be removed or separated under our process where local law permits.

Related Pages

sr400 Indonesia sr400 Casino FAQ Monsoon Magic Slots Access guide