Reference

Open via123 With Clear Privacy Controls

via123 Privacy Policy explains how we handle the account details, device signals and wallet references used when you open an account and reach the lobby.

Account data explainedWallet records coveredCookie choices availablePolicy requests supported
Explore Our Lobby Read FAQ
via123 Open via123 With Clear Privacy Controls
CONTACT ROUTES

Contact Us About Your Privacy Policy

A clear contact route helps you ask what we hold, why we use it or how to correct an account detail. Start from the support path linked in your account area and identify the phone number or login email connected with your request. If your question follows a DANA or QRIS transaction, include the payment reference without sending your wallet PIN. We use the same route for policy questions from Surabaya and other Indonesian locations.

Team online

Account privacy request

Use the account support route to ask for a copy of personal data, a correction to your phone or email, or clarification about a Privacy Policy section. Include the account identifier that lets us locate the right record.

Wallet record question

For DANA, OVO, GoPay or QRIS references, share the transaction date and reference shown in your payment history. We can explain how that record is matched to your account without asking for a wallet PIN or one-time code.

Sign-in data concern

If a device, browser or phone-verification event looks unfamiliar, contact us through the account help path and change your sign-in details. We can review the security event and explain the related handling under our Privacy Policy.

DATA PRACTICE

Explore How We Handle Your Records

Privacy depends on practical handling, not vague promises. We separate account details from payment references where our systems allow, limit internal access to operational needs, and use device signals to help identify…

Account details

We use your phone number, login email and verification status to create and protect your account. Check the account details page before sending a correction request, so we can connect your request to the correct profile.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile account activity. We do not need your wallet PIN or banking password for this process, and you should never include either in a support message.

Device signals

When you sign in from a mobile browser or desktop, we may record device and browser signals, session time and security events. These records help us identify an unfamiliar path from login to the lobby.

Cookies

Cookies can keep a session active, remember selected settings and help us understand page errors. Your browser controls can remove or block cookies, although some account and Privacy Policy request functions may then need another sign-in.

Retention

We keep records only for the operational, security and legal purposes connected with the account or request. Retention can differ by record type and local requirement; ask through support if you need the period for a specific item.

Changes and requests

You can ask us to access, correct or explain personal data through the account support route. We may verify your identity before responding, and the available action depends on local law and the type of record involved.

Find Privacy Policy Answers Before Opening

These answers address the privacy searches we hear most often before an account is opened. They focus on the records created during sign-in, phone verification, wallet matching and support contact, so you can understand the practical route before sharing account details.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and requests for access or correction.

We do not ask you to send a DANA or QRIS wallet PIN, banking password or one-time code through support. Our records may contain a payment reference needed to match activity with your account, but confidential wallet credentials should remain with you.

Device type, browser signals, session time and sign-in events help us spot an unfamiliar route into your account. This can support a security check when you move between a mobile browser and desktop, and the handling is described in the Privacy Policy.

Use the privacy or account support route connected to your profile and state whether you want access, correction or an explanation. Include your account phone number or login email, but leave out wallet PINs and one-time codes. Identity checks may apply.

Yes, send a correction request through the account support path and identify the phone number or email currently attached to the profile. We may ask for verification before changing a record, and the available action depends on local law.

Retention varies by record type and the operational, security or legal reason for keeping it. Account, payment-reference and support records can follow different periods. Ask through the policy contact route for the period connected with a specific record.

You can open this Privacy Policy page from the website footer and from relevant account support paths. Check the page before submitting a request because we may update wording when our data handling or applicable local requirements change.

Related Pages

via123 Indonesia About Us Account information via123 Casino Access guide