Reference

surga898 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, use DANA or QRIS, and contact support.

Clear data purposesWallet record contextRequest routes
surga898 surga898 Privacy Policy For Your Account
PRIVACY HELP ROUTES

Contact Us About Your Privacy Policy

Privacy questions should reach the same support route used for account and wallet-status concerns.

Account contact Use the support contact route linked from your account area to ask about collected data, a correction, or a Privacy Policy request. We may verify your account before sharing personal details.
Wallet status If a wallet record appears under the wrong account, tell us the rail used, such as QRIS or DANA, and the relevant reference. We use those details to trace the record safely.
Login concern For an unfamiliar sign-in or device session, contact support through the account help path and describe when it occurred. We can review access records without asking you to send a password.
DATA HANDLING PRACTICE

Explore How Account Data Stays Protected

We treat account data as an operating record rather than a message for unrelated use. The Privacy Policy explains how cookies support sign-in and page settings, how security checks protect an account…

Collected details

We may handle your account contact details, verification outcome, sign-in events, device signals, wallet references, and support messages. Each category is tied to account access, security, service handling, or a stated legal need.

Cookies

Cookies can remember sign-in state, language choices, and security signals on your device. Clearing them may require another account check, but it does not erase records already retained for valid purposes.

Account security

Phone verification before account access helps connect a person to the correct account. We also examine sign-in and device patterns when an access event looks unusual, then ask for added confirmation.

Retention period

We keep records for the period needed to provide account support, reconcile wallet activity, protect against misuse, or meet a legal duty. After that need ends, we delete or de-identify them.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. Include the email or phone tied to your account so we can process the request securely.

Request review

We assess each Privacy Policy request against account security and local requirements. Where local law permits, we explain the result, any restriction, and the next contact step if action is limited.

Browse surga898 Privacy Policy Questions

These answers address the Privacy Policy questions most often raised before account access. They cover wallet records, mobile devices, cookies, retention, and the steps needed to contact us about personal data. If your situation is different, use the support route above and describe the specific record or request.

It covers account details, phone verification, device and sign-in records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use payment references to match a wallet or transfer status with the correct account and investigate receipts. The Privacy Policy explains this operational use without asking for your wallet password or PIN.

Where local law permits, you can request a copy or explanation of personal data connected with your account. Contact us through the account support route and provide details needed to confirm ownership.

We may record device and browser signals, sign-in times, and security events when you use a mobile path. These details help identify unusual access and protect your account from misuse.

Yes. Send a correction request through the account contact route, identify the inaccurate field, and provide the account phone or email. We verify the request before changing personal details.

Retention depends on the reason for keeping a record, such as account support, wallet reconciliation, security, or legal duties. When that reason ends, we delete or de-identify the data where permitted.

The policy is written for Indonesian account access, including use from Jakarta and other areas, but eligibility and access depends on local law. Contact us if a local requirement affects your request.