Reference

Open surga22 Privacy Policy for Your Account

Our surga22 Privacy Policy explains what account, device and wallet data we collect, why we use it, and how you can ask for changes.

Account dataWallet recordsDevice choicesContact route

Explore Our Lobby Read FAQ

Check How Wallet Data Is Used

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

When you open an account, we use the details you submit to create your profile, complete phone verification and help you regain access if login details fail. Payment records can show a selected rail, such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, along

1
with the status needed to match a transaction. We do not treat a wallet name as permission to use unrelated data. Device signals may help us recognise an unusual sign-in and protect your account. Cookies can remember preferences and help us understand which policy pages load
2
correctly. Access to surga22 depends on local law, and our handling of data may change when a legal request requires it. You can contact us through the account help route beside the cashier path to ask what we hold or why a record is retained.

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

PRIVACY CONTACT

Contact Us About Your Privacy Request

A clear contact route helps when you need to ask about account data, a wallet receipt or a device record.

DATA HANDLING

See Our Data Handling Steps

We keep this policy practical by linking each data type to an account action: registration, phone verification, wallet matching or sign-in protection.

Account creation

We use your submitted registration details to create and maintain the account.

Payment matching

A DANA, OVO, GoPay or QRIS reference may be stored with its status so we can match the payment to…

Cookie choices

Cookies can retain sign-in preferences and measure page loading for policy access.

Account security

We may compare device and sign-in signals when an access attempt looks unusual.

Data retention

We retain records only for the account, payment, security or legal purpose that requires them.

Change requests

Ask us to correct profile data, explain wallet records or request deletion through account help.

Find Answers in the Privacy Policy

These Privacy Policy answers cover the questions you may have before opening an account or sending a wallet payment. If your case involves a specific DANA, OVO, GoPay, QRIS or device record, use the contact path above so we can check the relevant entry.

It covers account details, phone verification, device signals, cookies and payment records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps confirm that the account belongs to you before access and lets us match privacy requests to the correct profile without relying on a password.

Yes. We may keep the payment reference and status needed to match DANA or QRIS activity to your account. The same purpose applies to OVO, GoPay and bank rails.

Use the account help route beside the cashier path, provide your registered phone number and describe the records requested. We may ask for account details to confirm ownership.

You can request correction or deletion through account help where local law permits. Tell us which record is wrong or no longer needed, such as a device or wallet entry.

Cookies may remember sign-in preferences and help policy pages load correctly. You can change browser cookie controls, but disabling them may require you to repeat some account steps.

Yes. Access and some data requests depend on local law. If a legal requirement affects retention or account handling, we apply that requirement and explain the relevant route when possible.

Open surga22 Privacy Policy for Your Account

Contact Us About Your Privacy Request

See Our Data Handling Steps

Account creation

Payment matching

Cookie choices

Account security

Data retention

Change requests

Find Answers in the Privacy Policy

01 What does the surga22 Privacy Policy cover?

02 Why does the Privacy Policy ask for phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 How can I request a copy of my surga22 data?

05 Can I ask surga22 to correct or remove data?

06 How does the Privacy Policy handle cookies?

07 Does access under this Privacy Policy depend on local law?

Related Pages