Reference

Open cufflinks Privacy Policy Before Access

cufflinks Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between the casino and sports areas.

Account dataWallet checksCookie choicesContact routes
cufflinks Open cufflinks Privacy Policy Before Access
CONTACT THE POLICY DESK

Get Help With Privacy Policy Requests

A clear contact route matters when you want to ask about the Privacy Policy, correct an account detail or question a wallet record. Start from the support route linked beside the cashier so we can connect your request with the right account. Include your registered phone number, the subject of your request and any relevant payment reference, but do not send a full password or wallet PIN. We may ask for an account step to confirm that the request comes from you.

Team online

Account access

If you cannot enter your account or complete phone verification, send a support request with your registered phone number and device type. We use those details to locate the correct record without asking you to disclose a password or wallet PIN.

Wallet status

For a DANA, OVO, GoPay or QRIS question, include the payment rail, approximate time and reference shown in your cashier history. We compare that record with the account event before discussing transaction data.

Policy changes

To ask about a correction, deletion request or policy wording, identify the account email or phone path and describe the change you want. We may request a verification step before sending account-specific data or changing a record.

HOW WE HANDLE DATA

Explore Privacy Policy Handling Steps

The Privacy Policy is put into practice through ordinary account controls rather than a separate data portal.

Account records

We collect details you enter during account creation, including your phone number and selected account credentials. Login events and verification results help us confirm access, restore the correct account and answer a request about your Privacy Policy rights.

Payment references

A wallet or bank rail can provide a reference, amount status and processing time, but we do not need your wallet PIN. DANA, OVO, GoPay, QRIS and virtual account records are used to reconcile the cashier action with your account.

Device signals

Your browser, operating system, approximate network details and login time may be recorded for session operation and account protection. We use these signals to spot a change in access pattern, including a switch from mobile to desktop.

Cookies

Session cookies can keep your sign-in path and page choices working while you move through the lobby. You can adjust cookie controls in your browser, although disabling required cookies may interrupt account access or the cashier path.

Retention

We keep data for the period needed to operate the account, settle payment questions, investigate security events and meet applicable legal duties. When a record no longer serves those needs, we assess it for deletion or secure removal.

Your request

You can ask what account data we hold, request a correction, question a use or seek deletion assessment through support. We verify the request, explain any legal or operational reason for a limit and respond through the account contact path.

Check cufflinks Privacy Policy Answers

These Privacy Policy answers cover the searches we expect before you open an account or use a local wallet. They explain the data path in plain language, including account access, cookies, payment references, correction requests and contact checks. If your question concerns a specific record, use the support path beside the cashier and include only the details needed to locate it.

The cufflinks Privacy Policy covers data from account creation, phone verification, login activity, device use, cookies, support messages and cashier actions. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match a transaction with your account.

We may collect your phone number, account credentials, verification result, device details, login times and records of requests you send to support. We use these details to provide account access, check unusual activity, connect payment status and respond to your Privacy Policy questions.

Yes. Send a correction request through support with the account phone path, the field that appears wrong and the change you seek. We may ask you to complete phone verification before changing the record, then explain the result through the contact route linked to your account.

The Privacy Policy allows us to use payment references and status returned by DANA, OVO, GoPay or QRIS to reconcile a cashier action. We do not need your wallet PIN for this check. A reference may also help support investigate a missing or delayed account record.

Your browser usually provides cookie controls that let you remove or block some stored data. Required session cookies may be needed for login and cashier steps, so disabling them can interrupt access. The Privacy Policy distinguishes those operating cookies from optional measurement choices where available.

We retain account and transaction records for the time needed to operate the service, resolve payment disputes, protect account access and meet duties that apply where local law permits access. When those needs end, we assess the data for deletion, restriction or secure removal.

Use the support route beside the cashier and state whether you want access, correction, deletion assessment or an explanation of data use. Include your registered phone path and request details, but never send a password or wallet PIN. We verify identity before discussing account-specific data.