Reference

pgs288 Privacy Policy For Your Account

The pgs288 Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Baccarat Prestige or use DANA Wallet Topup, and how we…

Account dataWallet recordsCookie choicesPrivacy requests
pgs288 pgs288 Privacy Policy For Your Account
PRIVACY CONTACTS

Get Help With A Privacy Request

A clear contact route matters when a name, phone number or wallet reference needs attention. We ask you to start from the support link connected to your account so we can match the request with the correct profile instead of asking you to send private details through an unrelated channel. Include the email or phone used for access, the type of request and any relevant receipt reference. Our support path also helps when a privacy question appears beside a login or wallet-status issue.

Team online

Account access route

Use the support link after login and identify the account step involved, such as phone verification or a changed contact detail. We use that context to locate the right record without asking you to disclose a password or full payment credentials.

Wallet record request

For a DANA, OVO, GoPay or QRIS query, send the receipt reference and approximate transaction date through the account support path. We can then check the stored payment reference while limiting the request to the wallet record that concerns you.

Policy clarification

If a paragraph in this Privacy Policy is unclear, quote the relevant wording in your support message and tell us what you want confirmed. We will keep the discussion focused on data use, cookies, retention or an account privacy request.

DATA HANDLING

What We Do With Your Personal Data

Our privacy process follows the account journey rather than treating every record the same way. Login details support access, payment references support reconciliation, and device signals help us identify a session that…

Account collection

When you open an account, we collect the details needed for access and phone verification. We use the submitted contact route to connect you with your profile, send account-related messages and handle a request to correct an inaccurate name or number.

Payment references

A DANA Wallet Topup record may contain a payment reference, amount status and time, rather than your wallet password. Similar checks apply to OVO, GoPay, QRIS, bank transfer and virtual account records when we investigate a receipt or account ledger.

Cookies and settings

Cookies can keep a session choice, remember a language or device setting and show whether a page loaded correctly. You can manage cookie controls in your browser; changing them may require another login or remove a saved preference from the device.

Device security

We may record browser type, operating system, session time and security events to help identify unusual access. These signals do not replace your password or phone verification, and they help us investigate an interrupted login without reading unrelated files on your device.

Retention decisions

We keep account, support and payment records for as long as they serve access, dispute handling, security or a legal requirement. When a record no longer has a valid purpose, we assess deletion, restriction or anonymisation rather than keeping it indefinitely.

Change or deletion

You can ask us to correct account data, explain a processing purpose, provide eligible stored details or remove information where allowed. We may need to verify the account before acting, and access depends on local law and any applicable retention duty.

Privacy Policy Answers For pgs288

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is queried. They explain the practical route for account data, device activity, cookies and contact requests without replacing the full policy text. If your question concerns a specific receipt or phone number, use the account support path and include only the details needed to locate that record.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer activity. It also explains why we use each category, how retention is assessed and how you can request a change.

We do not need your DANA or QRIS password to match a payment reference with an account record. Send receipts through the account support path only, and never include a wallet password, one-time code or full banking credential in a privacy request.

Start with the account support link and state whether the phone number, name or contact route is incorrect. We may verify that you control the account before changing the record, because access depends on local law and account-security requirements.

The policy can cover browser type, operating system, session time, approximate technical signals and security events. We use these details to recognise an interrupted or unusual login, not to read unrelated files, photos or messages stored on your phone.

You can adjust cookies through your browser controls. Essential session settings may be needed for login or phone verification, while other cookies may support preferences or page performance. Refusing them can remove saved settings and require you to sign in again.

Retention depends on the purpose: access, security, support, payment reconciliation, dispute handling or a legal duty. We assess whether records can be deleted, restricted or anonymised when that purpose ends, subject to local requirements.

Use the support link connected to your account and describe the request, such as access, correction, deletion or a purpose clarification. Include the relevant payment reference only when needed. We may ask for account verification before responding.