Reference

surgagacor Privacy Policy And Account Data

surgagacor Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA and QRIS for account funding.

Account clarityWallet recordsMobile accessRequest options

Explore Our Lobby Read FAQ

How DANA And QRIS Records Are Used

surgagacor Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to account details, verification records, device signals, session activity, and payment references connected with your use of the service. When you choose DANA, OVO, GoPay, or QRIS, we may receive a transaction reference and status result needed to match the wallet event

1
to your account; we do not need your wallet password for that step. A bank transfer or virtual account can also create a reference used for reconciliation. We use these records to provide account access, investigate failed status updates, protect sign-in, and meet applicable legal duties.
2
Access or eligibility depends on local law, and our handling can vary when Indonesian rules require a different process. The current policy applies to the mobile browser path and desktop browser path, including activity around Fortune Mouse, Live Dealer Lobby, and other account-linked areas.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH REQUESTS

Where To Ask About Privacy Policy

A clear contact route helps when you want to ask about a record, correction, or account-data request.

Account help path Open the account help area when you need a Privacy Policy answer. Share your registered phone number and request type; keep DANA, OVO, GoPay, or QRIS passwords private.

Cashier status route If a data question relates to a pending wallet status, provide the transaction reference shown beside the cashier record. We can compare the reference without requesting your wallet login.

Correction request Ask us to correct an account detail through the same support route. We may verify account ownership before changing a phone number, identity field, or contact preference.

HANDLING YOUR RECORDS

What Our Privacy Process Covers

We keep the policy practical by connecting each data use to an account action you recognise, from phone verification to a QRIS status check.

Account details

We use your registered phone number and account fields to create sign-in continuity, complete phone verification before account access, and respond to a request about the correct account record.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account events may produce reference data. We use it to match status, investigate mismatches, and maintain a payment audit trail.

Device signals

When you move from login to the lobby on a phone or desktop browser, we may record device and session signals to detect unusual sign-in activity and keep the account path secure.

Cookie choices

Cookies and similar browser storage can remember session settings and help us understand whether a page request belongs to an active account. You can manage browser permissions on your device.

Storage period

We retain account, payment-reference, and security records only for the period needed for service operation, dispute handling, fraud checks, and legal duties, then remove or restrict them when appropriate.

Request verification

Before releasing, correcting, or deleting eligible data, we may confirm ownership through your registered account path. This protects your records when a request comes from an unknown device.

Privacy Policy Answers For Your Account

These common Privacy Policy questions focus on the records you create through account access, mobile browsing, and Indonesian wallet activity. Each answer points you toward a practical next step while keeping requests within applicable law and account-security checks.

It covers account details, phone verification, device and session signals, cookies, payment references, support requests, retention, and the reasons we use those records for access, safety, service operation, and legal duties.

No. We may receive a transaction reference and status result from DANA, QRIS, OVO, or GoPay, but you should never provide a wallet password through an account or support request.

Phone verification helps connect you to the correct account before access and protects against an unknown person changing account details. We may use the registered number when checking a privacy request.

You can ask through the account help path and describe the records you need. We may verify ownership first, then respond according to the Privacy Policy and applicable local law.

Send a correction request from the account help area with the affected field, such as a phone number or contact preference. We may ask for account verification before making the change.

We keep payment references for the period needed to match wallet status, handle disputes, protect accounts, and meet legal duties. After that, records are removed or restricted when appropriate.

Yes. The Privacy Policy covers the mobile browser route from login to the lobby as well as desktop browsing, including device signals, session records, cookies, and account-linked activity.

surgagacor Privacy Policy And Account Data

Where To Ask About Privacy Policy

What Our Privacy Process Covers

Account details

Wallet references

Device signals

Cookie choices

Storage period

Request verification

Privacy Policy Answers For Your Account

01 What does the surgagacor Privacy Policy cover?

02 Does Privacy Policy collect my DANA or QRIS password?

03 Why does surgagacor need phone verification?

04 Can I request a copy of my account data?

05 How do I correct an error in my Privacy Policy data?

06 How long does surgagacor keep payment references?

07 Does the policy apply on a mobile browser?

Related Pages