Reference

Privacy Policy For Your surya123 Account

Our Privacy Policy explains what we collect when you open a surya123 account, how we use your phone verification, and how we protect details connected with DANA, OVO…

Clear data purposesWallet detail handlingAccount access choicesPolicy contact path
surya123 Privacy Policy For Your surya123 Account
CONTACT ROUTES

Privacy Questions Have A Clear Route

A direct support route helps you ask about the Privacy Policy without searching through unrelated account screens.

Policy questions Ask our support team why your phone number, device signal or sign-in record appears…
Wallet records If a DANA, OVO, GoPay or QRIS receipt does not match your account, contact…
Access assistance For a locked sign-in, phone verification question or policy access problem, use the support…
DATA PRACTICES

Six Ways We Handle Your Details

We handle this Privacy Policy area through practical account controls rather than broad statements.

Account creation

When you open an account, we collect the details needed to create your login and carry out phone verification.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be recorded with a payment event.

Cookies

Cookies can preserve your sign-in session, remember a policy page choice and help us understand whether a page loads correctly…

Account security

We use phone verification, sign-in signals and account checks to reduce unauthorised entry.

Retention periods

We retain account, support and payment records only for the period needed for the stated purpose, security checks or a…

Your requests

You may ask us to access, correct or delete personal details where local law permits.

Privacy Policy Questions About surya123

These answers address the Privacy Policy searches we hear most often before account creation. They cover phone verification, wallet records, cookies, retention, account access and contact steps, so you can decide what to do with your details before using the site. If your situation is specific, contact us through the secure route and mention the relevant account step.

The Privacy Policy explains that we use your phone number to create and protect your account, complete phone verification and connect support requests to the correct record. We may ask for another check when access looks unusual, and you should submit verification details only through the account screen.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use these details to match receipts, check wallet status and investigate a transaction issue; we do not request wallet credentials through public messages.

After sign-in, open the policy or legal link in the account area and choose Privacy Policy. On a mobile browser, the link is available from the account menu; on desktop, it appears in the site footer. Where local law permits, you can read it before completing account access.

You can contact support to request access to personal data held about your account or ask for a correction where local law permits. Include the registered phone number through the secure route, explain the requested change and complete identity checks before we disclose or amend a record.

The Privacy Policy explains that retention depends on the record and its purpose. Account, support and payment data may remain while needed for access, security, transaction checks or a legal duty. Ask support about a particular record, and we will explain the reason for its retention.

You can restrict or remove cookies through your browser settings. Cookies may keep a sign-in session active, remember a policy choice or help us identify loading problems on your device. If you block them, you may need to sign in again or complete an account step another time.

Use the support contact shown after account access and describe the Privacy Policy concern without posting personal or wallet details in an open chat. We can explain data use, locate a policy version, check a receipt record or route a correction and deletion request for handling.