Reference

pgbet login Privacy Policy for Your Account

pgbet login Privacy Policy explains how we handle the account details you provide before access, including your phone verification, wallet records and support messages.

Phone verificationWallet record clarityCookie choicesLocal access rules
pgbet login pgbet login Privacy Policy for Your Account
HELP WITH RECORDS

Privacy Policy Support From Login To Wallet

A clear support path matters when your Privacy Policy question starts with a login event or a wallet reference.

Account access If your phone verification does not match, send the registered number and device path…
Wallet records For DANA, OVO, GoPay or QRIS references, share the receipt code, payment date and…
Change request When you want a record corrected or a stored detail clarified, state the field…
HANDLING YOUR DATA

What We Do With Account Privacy

We keep the Privacy Policy practical by connecting each data use to an account task you can recognise.

Account data

We use your registered phone number and verification result to associate account access with the correct profile.

Device signals

Login time, browser or device details can help us identify an unusual access attempt.

Cookies

Cookies can keep a session active, remember a basic setting or help us understand which policy page was opened.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored to match a receipt with your…

Retention period

We keep account, security and payment records for the period needed for the stated account task, dispute handling or applicable…

Your request

You can ask what personal data we hold, request a correction, question its use or ask about removal through account…

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the searches we hear around pg bet login access, phone verification and local wallet records. They explain what to send, what we may check and where local law affects the result. If your question concerns a specific login or receipt, use the account support route and provide the smallest useful set of details. Do not send passwords, wallet PINs or full card credentials in a message.

It covers account details, phone verification, login and device signals, cookie use, payment references and support messages connected with your account. It also explains why we use those records, how long they may remain available and how you can ask for access, correction or removal.

Phone verification helps us connect an account request with the right account and investigate an unfamiliar login. If the number does not match, contact account support with the registered number and device path. Never send your password or wallet PIN when asking us to check the record.

We may store a payment reference, amount status or receipt detail needed to match DANA, OVO, GoPay or QRIS activity with your account. These records help resolve a wallet question, but they are not your wallet PIN. Ask support which reference is linked to your request.

Yes, you can ask account support which personal data is held for your profile and request a copy where applicable. Include your registered phone number and the request type. We confirm ownership first, then explain the available response, format and any local-law limits.

Send the field that appears incorrect, the corrected value and a short reason through the account support route. We may ask for phone verification before changing it. Payment references and security records can require an additional check so that an update does not create an inaccurate account history.

Retention depends on the record and its purpose. We may keep phone verification, login security, payment references or support messages while needed for account operation, a dispute or an applicable legal duty. After that period, we remove or anonymise the record where our systems allow.

You can submit a removal request through account support, and we will assess which records can be deleted. Some security, payment or legal records may need to remain for a defined period. Any access or eligibility decision depends on local law and where local law permits.